Methods, architectures, devices, and systems for relocating a server from a consumer node in a break-before-make pattern.

BR112025021674A2Pending Publication Date: 2026-09-08
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
BR112025021674
Authority / Receiving Office
BR · BR
Patent Type
Applications
Publication Date
2026-09-08

Smart Images

  • Figure 00000000_0000_ABST
    Figure 00000000_0000_ABST
Patent Text Reader
Need to check novelty before this filing date? Find Prior Art

Description

1 / 78 “METHODS, ARCHITECTURES, APPARATUS AND SYSTEMS FOR RELOCATING A CONSUMER NODE SERVER IN A BREAK-BEFOREMAKE PATTERN” CROSS-REFERENCE TO RELATED REQUESTS

[001] This application claims the benefit of Provisional Patent Application No. US 63 / 457,821, filed April 7, 2023, which is incorporated herein by reference. FIELD OF THE INVENTION

[002] The present disclosure is generally directed to the fields of communications, software and coding, including, for example, methods, architectures, devices and systems directed to the trusted edge enablement layer. BACKGROUND

[003] A key functionality offered by an edge enablement layer (EEL) can allow a wireless transmit / receive unit, WTRU, to be provisioned with edge connectivity information, discover available edge services, and maintain edge service while moving through the mobile network.

[004] A highly reliable edge enablement layer may be possible using edge configuration server (ECS) sets and / or edge enabler servers (EES). A server set may consist of predefined alternate servers to replace an active ECS and / or active EES that can be used by a WTRU, an edge enabler client (EEC), an edge application server (EAS), or an EES. The EEL of a 5G system does not support server sets.

[005] The current 5G system does not support mechanisms to provide Petition 870250091342, dated 07 / 10 / 2025, page 10 / 115 2 / 78 reliable edge computing.

[006] There is a need to introduce new functionalities in the edge enablement layer of the 5G system so that the EEL can use server sets to manage and make edge network behavior predictable in case of failure. SUMMARY

[007] In one embodiment, a method implemented in a wireless transmit / receive unit (WTRU) may comprise a step of receiving a server set configuration associated with an active server. The method may comprise a step of detecting / determining the unavailability of the active server. The method may comprise a step of determining / detecting the unavailability of the active server, which may be based on a communication timeout failure with the active server. The method may comprise a step of selecting an alternate server based on the received server set configuration. The method may comprise a step of transmitting a server switching request message to the alternate server, wherein the server switching request message may comprise initial information indicating a WTRU identifier.The method may comprise a step of receiving, from the alternate server, a server switching response message, wherein the server switching response message may include procedural information for communicating with the alternate server and resource mapping information related to the alternate server. The procedural information may comprise procedures for confirming successful server switching, wherein the procedures for confirming successful server switching may comprise a procedure for... Petition 870250091342, dated 07 / 10 / 2025, page 11 / 115 3 / 78 Update record with alternate server. Resource mapping information may include Uniform Resource Identifiers (URIs) or identifiers corresponding to resources on the active server. The method may comprise a step of mapping bindings based on the received resource mapping information; and a step of transmitting communication to the alternate server using the received procedure information.

[008] In another embodiment, a method, implemented on a server, may comprise a step of receiving a server switching request message from a wireless transmit / receive unit (WTRU), wherein the server switching request message may comprise a WTRU identifier. The method may comprise a step of determining resource mapping (e.g., identifying the mapping of passive and active resources) associated with the WTRU based on the WTRU identifier. The method may comprise a step of transmitting a server switching response message to the WTRU, wherein the server switching response message may include procedural information for communication with the server and the determined resource mapping. The method may comprise a step of receiving communication from the WTRU based on the procedural information provided / transmitted.

[009] In another embodiment, a method implemented in a wireless transmit / receive unit, WTRU, may comprise: receiving a server set configuration associated with an active server; receiving a server switching notification message from an active server, wherein the server switching notification message comprises information indicating an alternate server, procedures for communicating with the alternate server and Petition 870250091342, dated 07 / 10 / 2025, page 12 / 115 4 / 78 timing information indicating when to access the alternate server; establish connectivity to an edge data network of the alternate server; and communicate with the alternate server based on procedures.

[010] In another embodiment, a method implemented on a server may comprise: selecting an alternate server to transfer resources; transmitting a first server switching notification message to a WTRU, wherein the first server switching notification message comprises information indicating the alternate server; transmitting a server switching request message to the alternate server, wherein the server switching request message includes passive and active resources of the active server associated with the WTRU; receiving a server switching response message from the alternate server, wherein the server switching response message includes mappings of active server resources associated with the alternate server; and transmitting a second server switching notification to the WTRU associated with the resources transferred to the alternate server. BRIEF DESCRIPTION OF THE DRAWINGS

[011] A more detailed understanding can be obtained from the detailed description below, given by way of example in combination with the accompanying drawings. The Figures in such drawings, like the detailed description, are examples. Thus, the Figures and the detailed description should not be considered limiting, and other equally effective examples are possible and probable. Furthermore, similar reference numbers (“ref.”) in the Figures indicate similar elements, and in which:

[012] Figure 1A is a system diagram that illustrates an exemplary communications system; Petition 870250091342, dated 07 / 10 / 2025, page 13 / 115 5 / 78

[013] Figure 1B is a system diagram illustrating an exemplary wireless transmit / receive unit (WTRU) that can be used within the communications system illustrated in Figure 1A;

[014] Figure 1C is a system diagram illustrating an exemplary radio access network (RAN) and an exemplary central network (CN) that can be used within the communications system illustrated in Figure 1A;

[015] Figure 1D is a system diagram that illustrates an additional exemplary RAN and an additional exemplary CN that can be used within the communications system illustrated in Figure 1A;

[016] Figure 2 is an example of an architecture diagram for enabling edge applications;

[017] Figure 3 is an example of a message sequence graph of an edge system;

[018] Figure 4 is an example of a message sequence graph of an edge enabler server switch in a breakbefore-make first scenario;

[019] Figure 5 is an example of a message sequence graph of an edge configuration server switch in a second break-before-make scenario;

[020] Figure 6 is an example of a message sequence graph of an edge enabler server switch in a first makebefore-break scenario;

[021] Figure 7 is an example of a message sequence graph of an edge configuration server switch in a second make-before-break scenario; Petition 870250091342, dated 07 / 10 / 2025, page 14 / 115 6 / 78

[022] Figure 8 is a flowchart that illustrates an example of a method performed by a consumer node to relocate a server in a breakbefore-make manner:

[023] Figure 9 is a flowchart that illustrates an example of a method performed by an alternative server to reallocate an active server;

[024] Figure 10 is a flowchart that illustrates an example of a method performed by a consumer node to relocate a server in a make-before-break manner;

[025] Figure 11 is a flowchart that illustrates an example of a method performed by an active server to reallocate the active server in a make-beforebreak manner. DETAILED DESCRIPTION

[026] In the detailed description that follows, several specific details are presented to provide a complete understanding of the embodiments and / or examples disclosed in this document. However, it should be understood that such embodiments and examples may be practiced without some or all of the specific details set forth in this document. In other instances, well-known methods, procedures, components, and circuits have not been described in detail so as not to obscure the present invention. Furthermore, embodiments and examples not specifically described in this document may be practiced instead of, or in combination with, the embodiments and other examples described, disclosed, or otherwise explicitly, implicitly, and / or inherently provided (collectively “provided”) in this document. Although several embodiments are described and / or claimed in this document in which an apparatus, system, device, etc., and / or any element thereof performs a... Petition 870250091342, dated 07 / 10 / 2025, page 15 / 115 7 / 78 operation, process, algorithm, function, etc. and / or any part thereof, it must be understood that any embodiments described and / or claimed herein assume that any apparatus, system, device, etc. and / or any element thereof is configured to perform any operation, process, algorithm, function, etc. and / or any part thereof.

[027] The methods, devices and systems provided in this document are suitable for communications involving wired and wireless networks. An overview of various types of wireless devices and infrastructure is provided in relation to Figures 1A-1D, whereby various network elements can utilize, perform, be organized according to and / or be adapted and / or configured for the methods, devices and systems provided in this document.

[028] Figure 1A is a system diagram illustrating an exemplary 100 communications system in which one or more disclosed modalities can be implemented. The 100 communications system can be a multiple access system that provides content, such as voice, data, video, messaging, broadcasting, etc., to multiple wireless users. The 100 communications system can allow multiple wireless users to access this content by sharing system resources, including wireless bandwidth.For example, 100 communication systems may employ one or more channel access methods, such as code division multiple access (CDMA), time division multiple access (TDMA), frequency division multiple access (FDMA), orthogonal FDMA (OFDMA), single carrier FDMA (SC-FDMA), zero-tailed (ZT) single-word (UW) Discrete Fourier Transform (DFT) OFDM with scattering (ZT UW DFT-s OFDM), single-word OFDM (UW-OFDM), filtered feature block OFDM, filter bank multicarrier (FBMC), and the like. Petition 870250091342, dated 07 / 10 / 2025, page 16 / 115 8 / 78

[029] As shown in Figure 1A, the communications system 100 may include wireless transmit / receive units (WTRUs) 102a, 102b, 102c, 102d, a radio access network (RAN) 104 / 113, a central network (CN) 106 / 115, a public switched telephone network (PSTN) 108, the Internet 110 and other networks 112, although it is 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. For example, WTRUs 102a, 102b, 102c, 102d, any of which may be referred to as a “station” and / or a “STA”, may be configured to transmit and / or receive wireless signals and may include (or be) a user equipment (UE), a mobile station, a fixed or mobile subscriber unit, a subscription-based unit, a pager, a mobile phone,A personal digital assistant (PDA), a smartphone, a laptop computer, a netbook computer, 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, a medical device and applications (e.g., remote surgery), an industrial device and applications (e.g., a robot and / or other wireless devices operating in industrial and / or automated processing chain contexts), a consumer electronic device, a device operating on commercial and / or industrial wireless networks, and similar devices. Any of WTRUs 102a, 102b, 102c, and 102d may be referred to interchangeably as UE.

[030] Communication systems 100 may also include a base station 114a and / or a base station 114b. Each of the base stations 114a, 114b may be any type of device configured to wirelessly interact with at least Petition 870250091342, dated 07 / 10 / 2025, p. 17 / 115 9 / 78 minus one of the WTRUs 102a, 102b, 102c, 102d, for example, to facilitate access to one or more communication networks, such as CN 106 / 115, the Internet 110 and / or other networks 112. By way of example, base stations 114a, 114b can be any of the following: base transceiver station (BTS), a B-Node (NB), an eNode B (eNB), a Home B-Node (HNB), a Home eNode B (HeNB), a gNode-B (gNB), an NR-Node B (NR-NB), a site controller, an access point (AP), a wireless router and the like. Although base stations 114a and 114b are each represented as a single element, it will be understood that base stations 114a and 114b may include any number of interconnected base stations and / or network elements.

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

[032] Base stations 114a, 114b can communicate with one or more WTRUs 102a, 102b, 102c, 102d via an air interface 116, which can 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 can be established using any suitable radio access technology (RAT).

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

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

[035] In one mode, base station 114a and WTRUs 102a, 102b, Petition 870250091342, dated 07 / 10 / 2025, p. 19 / 115 11 / 78 102c can implement a radio technology, such as NR Radio Access, which can establish the 116 air interface using New Radio (NR).

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

[037] In one embodiment, base station 114a and 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 Evolution Enhanced Data Rates (EDGE), GSM EDGE (GERAN) and the like.

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

[039] RAN 104 / 113 may be in communication with CN 106 / 115, which may be any type of network configured to provide voice, data, application and / or voice over internet protocol (VoIP) services to one or more WTRUs 102a, 102b, 102c, 102d. The data may have varying quality of service (QoS) requirements, such as different throughput requirements, latency requirements, error tolerance requirements, reliability requirements, data throughput requirements, mobility requirements and the like. CN 106 / 115 may provide call control, billing services, mobile location-based services, prepaid calls, internet connectivity, video distribution, etc., and / or perform high-level security functions such as user authentication.Although not shown in Figure 1A, it will be understood that RAN 104 / 113 and / or CN 106 / 115 may be in direct or indirect communication with other RANs employing the same RAT as RAN 104 / 113 or a different RAT. For example, in addition to being connected to RAN 104 / 113, which may be using NR radio technology, CN 106 / 115 may also be in communication with another RAN (not shown) employing any of the following radio technologies: GSM, UMTS, CDMA 2000, WiMAX, E-UTRA, or WiFi. Petition 870250091342, dated 07 / 10 / 2025, p. 21 / 115 13 / 78

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

[041] Some or all of the WTRUs 102a, 102b, 102c, 102d in the communications system 100 may include multimode capabilities (for example, WTRUs 102a, 102b, 102c, 102d may include multiple transceivers for communication with different wireless networks via different wireless links). For example, WTRU 102c shown in Figure 1A may be configured to communicate with base station 114a, which may employ cellular-based radio technology, and with base station 114b, which may employ IEEE 802 radio technology.

[042] Figure 1B is a system diagram illustrating an exemplary WTRU 102.As shown in Figure 1B, the WTRU 102 may include a processor 118, a transceiver 120, a transmit / receive element 122, a speaker / microphone 124, a numeric keypad 126, a touch display / keyboard 128, non-removable memory 130, removable memory 132, a power supply 134, a global positioning system (GPS) chipset 136 and / or other elements / peripherals 138, among others. It will be understood that the WTRU 102 may include any subcombination of the foregoing elements, remaining consistent with an embodiment. Petition 870250091342, dated 07 / 10 / 2025, page 22 / 115 14 / 78

[043] Processor 118 may be a general-purpose processor, a special-purpose processor, a conventional processor, a digital signal processor (DSP), a plurality of microprocessors, one or more microprocessors in association with a DSP core, a controller, a microcontroller, application-specific integrated circuits (ASICs), field-programmable gate array circuits (FPGAs), any other type of integrated circuit (IC), a state machine, and the like. Processor 118 may perform signal encoding, data processing, power control, input / output processing, and / or any other functionality that allows WTRU 102 to operate in a wireless environment. Processor 118 may be coupled to transceiver 120, which may be coupled to transmit / receive element 122.Although Figure 1B depicts processor 118 and transceiver 120 as separate components, it will be understood that processor 118 and transceiver 120 can be integrated together, for example, in a single electronic package or chip.

[044] The transmit / receive element 122 can be configured to transmit signals to or receive signals from a base station (e.g., base station 114a) via the air interface 116. For example, in one embodiment, the transmit / receive element 122 can be an antenna configured to transmit and / or receive RF signals. In another embodiment, the transmit / receive element 122 can be a transmitter / detector configured to transmit and / or receive infrared, ultraviolet, or visible light signals, for example. In another embodiment, the transmit / receive element 122 can be configured to transmit and / or receive RF and light signals. It will be understood that the transmit / receive element 122 can be configured to transmit and / or receive any combination of wireless signals. Petition 870250091342, dated 07 / 10 / 2025, page 23 / 115 15 / 78

[045] Although the transmit / receive element 122 is represented in Figure 1B as a single element, the WTRU 102 may include any number of transmit / receive elements 122. For example, the WTRU 102 may employ MIMO technology. Thus, in one embodiment, the WTRU 102 may include two or more transmit / receive elements 122 (e.g., multiple antennas) to transmit and receive wireless signals over the air interface 116.

[046] Transceiver 120 can be configured to modulate the signals that are to be transmitted by the transmit / receive element 122 and to demodulate the signals that are received by the transmit / receive element 122. As noted above, WTRU 102 can have multimode capabilities. Thus, transceiver 120 can include multiple transceivers to allow WTRU 102 to communicate via multiple RATs, such as NR and IEEE 802.11, for example.

[047] The WTRU 102 processor 118 can be coupled to and can receive user input data from the speaker / microphone 124, the numeric keypad 126, and / or the display / touchpad 128 (e.g., a liquid crystal display (LCD) display unit or organic light-emitting diode (OLED) display unit). The processor 118 can also send user data to the speaker / microphone 124, the numeric keypad 126, and / or the display / touchpad 128. In addition, the processor 118 can access information and store data in any suitable type of memory, such as non-removable memory 130 and / or removable memory 132. Non-removable memory 130 can include random access memory (RAM), read-only memory (ROM), a hard disk, or any other type of memory storage device. Removable memory 132 can include a subscriber identity module (SIM) card, a card of Petition 870250091342, dated 07 / 10 / 2025, page 24 / 115 16 / 78 memory, a secure digital memory card (SD) and similar. In other embodiments, the 118 processor can access information and store data in memory that is not physically located in the WTRU 102, such as on a server or in a home computer (not shown).

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

[049] Processor 118 may also be coupled to GPS chipset 136, which may be configured to provide location information (e.g., longitude and latitude) relative to the current location of WTRU 102. In addition to or instead of GPS chipset 136 information, WTRU 102 may receive location information via air interface 116 from a base station (e.g., base stations 114a, 114b) and / or determine its location based on the timing of signals received from two or more nearby base stations. It will be understood that WTRU 102 may acquire location information by any suitable location determination method, remaining consistent with a mode.

[050] The processor 118 can also be coupled with other elements / peripherals 138, which may include one or more software and / or hardware modules / units that provide additional attributes, functionality and / or wired or wireless connectivity. For example, the elements / peripherals 138 can Petition 870250091342, dated 07 / 10 / 2025, p. 25 / 115 17 / 78 include an accelerometer, an electronic compass, a satellite transceiver, a digital camera (e.g., for photographs and / or video), a universal serial bus (USB) port, a vibration device, a television transceiver, a hands-free headset, a Bluetooth® module, a frequency modulated (FM) radio unit, a digital music player, a media player, a video game player module, an internet browser, a virtual reality and / or augmented reality (VR / AR) device, an activity tracker, and the like. Elements / peripherals 138 may include one or more sensors, which may be one or more of the following: gyroscope, accelerometer, Hall effect sensor, magnetometer, orientation sensor, proximity sensor, temperature sensor, time sensor; geolocation sensor; altimeter, light sensor, touch sensor, magnetometer, barometer, gesture sensor, biometric sensor and / or humidity sensor.

[051] The WTRU 102 may include a full-duplex radio for which the transmission and reception of some or all signals (e.g., associated with specific subframes for both the uplink (e.g., for transmission) and the downlink (e.g., for reception)) may be concurrent and / or simultaneous. The full-duplex radio may include an interference management unit to substantially reduce and / or eliminate self-interference by means of hardware (e.g., an inductor) or signal processing by means of a processor (e.g., a separate processor (not shown) or by means of processor 118). In one embodiment, the WTRU 102 may include a half-duplex radio for which the transmission and reception of some or all signals (e.g., associated with specific subframes for the uplink (e.g., for transmission) or the downlink (e.g., for reception)) are performed. Petition 870250091342, dated 07 / 10 / 2025, p. 26 / 115 18 / 78

[052] Figure 1C is a system diagram illustrating RAN 104 and CN 106 according to one mode. As noted above, RAN 104 can employ E-UTRA radio technology to communicate with WTRUs 102a, 102b, and 102c via air interface 116. RAN 104 can also be in communication with CN 106.

[053] RAN 104 may include eNode-Bs 160a, 160b, 160c, although it is possible that RAN 104 may include any number of eNode-Bs, remaining consistent with one embodiment. eNode-Bs 160a, 160b, 160c may each include one or more transceivers for communication with WTRUs 102a, 102b, 102c via air interface 116. In one embodiment, eNode-Bs 160a, 160b, 160c may implement MIMO technology. Thus, eNode-B 160a, for example, may use multiple antennas to transmit wireless signals to and receive wireless signals from WTRU 102a.

[054] Each of the eNode-Bs 160a, 160b, and 160c can be associated with a specific cell (not shown) and can be configured to handle radio resource management decisions, handover decisions, user scheduling on the uplink (UL) and / or downlink (DL), and similar tasks. As shown in Figure 1C, the eNode-Bs 160a, 160b, and 160c can communicate with each other via an X2 interface.

[055] The CN 106 shown in Figure 1C may include a Mobility Management Entity (MME) 162, a Service Communication Port (SGW) 164, and a Packet Data Network (PDN) Port (PGW) 166. Although each of the above elements is described as part of CN 106, it will be understood that any of these elements may be owned and / or operated by an entity other than the CN operator. Petition 870250091342, dated 07 / 10 / 2025, page 27 / 115 19 / 78

[056] MME 162 can be connected to each of the eNode-Bs 160a, 160b, and 160c in RAN 104 via an S1 interface and can serve as a control node. For example, MME 162 can be responsible for authenticating users of WTRUs 102a, 102b, 102c, carrier activation / deactivation, selecting a specific service communication port during an initial connection of WTRUs 102a, 102b, 102c, and similar. MME 162 can provide a control plane function to switch between RAN 104 and other RANs (not shown) that employ other radio technologies, such as GSM and / or WCDMA.

[057] SGW 164 can be connected to each of the eNode Bs 160a, 160b, 160c in RAN 104 via the S1 interface. SGW 164 can generally route and forward user data packets to / from WTRUs 102a, 102b, 102c. SGW 164 can perform other functions such as anchoring user planes during transfers between eNode B, triggering paging when DL data is available to WTRUs 102a, 102b, 102c, managing and storing contexts of WTRUs 102a, 102b, 102c and similar.

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

[059] CN 106 can facilitate communications with other networks. For example, CN 106 can provide WTRUs 102a, 102b, 102c with access to circuit-switched networks, such as PSTN 108, to facilitate communications between WTRUs 102a, 102b, 102c and traditional landline communication devices. For example, CN 106 can include, or communicate with, an IP communication port (e.g., an IP multimedia subsystem server). Petition 870250091342, dated 07 / 10 / 2025, p. 28 / 115 20 / 78 (IMS)) which serves as an interface between CN 106 and PSTN 108. In addition, CN 106 can provide WTRUs 102a, 102b, 102c with access to other 112 networks, which may include other wired and / or wireless networks that are owned and / or operated by other service providers.

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

[061] In representative modalities, the other 112 network can be a WLAN.

[062] A Basic Services Joint (BSS) infrastructure WLAN may have an access point (AP) for the BSS and one or more stations (STAs) associated with the AP. The AP may have access or an interface to a distribution system (DS) or other type of wired / wireless network that carries inbound and / or outbound traffic from the BSS. Traffic to STAs originating outside the BSS may arrive via the AP and be delivered to the STAs. Traffic originating from STAs to destinations outside the BSS may be sent to the AP for delivery to the respective destinations. Traffic between STAs within the BSS may be sent via the AP, for example, where the originating STA may send traffic to the AP and the AP may deliver the traffic to the destination STA. Traffic between STAs within a BSS may be considered and / or referred to as point-to-point traffic. Point-to-point traffic can be sent between (e.g., directly between) the source and destination STAs with a Direct Link System (DLS) configuration.In certain representative modes, DLS may use either 802.11e DLS or 802.11z tunneled DLS (TDLS). A WLAN using an Independent BSS (IBSS) mode may not have an AP, and the STAs (e.g., all STAs) within or using the IBSS may communicate directly. Petition 870250091342, dated 07 / 10 / 2025, p. 29 / 115 21 / 78 among themselves. The IBSS communication method may sometimes be referred to in this document as an “ad-hoc” communication method.

[063] When using the 802.11ac infrastructure operating mode or a similar operating mode, the AP can transmit a radio beacon on a fixed channel, such as a primary channel. The primary channel can have a fixed width (e.g., 20 MHz bandwidth) or a width dynamically defined through signaling. The primary channel can be the BSS's operating channel and can be used by STAs to establish a connection with the AP. In certain representative embodiments, carrier-sensing multiple access with collision avoidance (CSMA / CA) can be implemented, for example, in 802.11 systems. For CSMA / CA, STAs (e.g., each STA), including the AP, can sense the primary channel. If the primary channel is sensed and / or determined to be occupied by a specific STA, that specific STA can back off. An STA (e.g., only one station) can transmit at any time on a given BSS.

[064] High-throughput (HT) STAs can use a 40 MHz wide channel for communication, for example, by combining the 20 MHz primary channel with an adjacent or non-adjacent 20 MHz channel to form a 40 MHz wide channel.

[065] Very high throughput (VHT) STAs can support channels 20 MHz, 40 MHz, 80 MHz, and / or 160 MHz wide. 40 MHz and / or 80 MHz channels can be formed by combining contiguous 20 MHz channels. A 160 MHz channel can be formed by combining 8 contiguous 20 MHz channels or by combining two non-contiguous 80 MHz channels, which can be called an 80+80 configuration. For the 80+80 configuration, the data, after channel encoding, can be passed through a segment analyzer that can split the Petition 870250091342, dated 07 / 10 / 2025, page 30 / 115 22 / 78 data in two streams. Inverse Fast Fourier Transform (IFFT) processing and time-domain processing can be performed on each stream separately. The streams can be mapped to the two 80 MHz channels, and the data can be transmitted via a transmit STA. At the receiver of the receive STA, the operation described above for the 80+80 configuration can be reversed, and the combined data can be sent to the medium access control (MAC) layer, entity, etc.

[066] Operating modes below 1 GHz are supported by 802.11af and 802.11ah. Operating channel and carrier bandwidths are reduced in 802.11af and 802.11ah compared to those used in 802.11n and 802.11ac. 802.11af supports bandwidths of 5 MHz, 10 MHz, and 20 MHz in the TV white space spectrum (TVWS), and 802.11ah supports bandwidths of 1 MHz, 2 MHz, 4 MHz, 8 MHz, and 16 MHz using non-TVWS spectrum. According to a representative embodiment, 802.11ah can support meter-type control / machine-type communications (MTC), such as MTC devices in a macro coverage area. MTC devices may have certain capabilities, for example, limited capabilities, including support for (e.g., support only for) certain and / or limited bandwidths. MTC devices may include a battery with a lifespan exceeding a certain limit (e.g., to maintain a very long lifespan).

[067] WLAN systems, which can support multiple channels and channel bandwidths, such as 802.11n, 802.11ac, 802.11af, and 802.11ah, include a channel that can be designated as the primary channel. The primary channel can have a bandwidth equal to the highest common operational bandwidth supported by all STAs in the BSS. The bandwidth of the primary channel can be defined and / or limited by an STA, among all STAs operating in a BSS, that supports the mode of Petition 870250091342, dated 07 / 10 / 2025, page 31 / 115 23 / 78 Lower bandwidth operation. In the 802.11ah example, the primary channel may have a 1 MHz bandwidth for STAs (e.g., MTC-type devices) that support (e.g., only support) a 1 MHz mode, even if the AP and other STAs in the BSS support 2 MHz, 4 MHz, 8 MHz, 16 MHz, and / or other channel bandwidth operation modes. Carrier sense and / or network allocation vector (NAV) settings may depend on the primary channel status. If the primary channel is busy, for example, due to an STA (that only supports a 1 MHz operation mode) transmitting to the AP, all available frequency bands may be considered occupied, even if most frequency bands remain idle and may be available.

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

[069] Figure 1D is a system diagram illustrating RAN 113 and CN 115 according to a modality. As noted above, RAN 113 can employ NR radio technology to communicate with WTRUs 102a, 102b, 102c via air interface 116. RAN 113 can also be in communication with CN 115.

[070] RAN 113 may include gNBs 180a, 180b, 180c, although it is possible that RAN 113 may include any number of gNBs while remaining consistent with a mode. gNBs 180a, 180b, 180c may each include one or more transceivers for communication with WTRUs 102a, 102b, 102c via air interface 116. In a mode, gNBs 180a, 180b, 180c may implement the Petition 870250091342, dated 07 / 10 / 2025, p. 32 / 115 24 / 78 MIMO technology. For example, gNBs 180a and 180b can use beamforming to transmit signals and / or receive signals from WTRUs 102a, 102b, and 102c. Thus, gNB 180a, for example, can use multiple antennas to wirelessly transmit signals to and / or receive wireless signals from WTRU 102a. In one embodiment, gNBs 180a, 180b, and 180c can implement carrier aggregation technology. For example, gNB 180a can transmit multiple component carriers to WTRU 102a (not shown). A subset of these component carriers may be in unlicensed spectrum, while the remaining component carriers may be in licensed spectrum. In one embodiment, gNBs 180a, 180b, and 180c can implement Coordinated Multipoint (CoMP) technology. For example, WTRU 102a can receive coordinated transmissions from gNB 180a and gNB 180b (and / or gNB 180c).

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

[072] gNBs 180a, 180b, 180c can be configured to communicate with WTRUs 102a, 102b, 102c in a standalone and / or non-standalone configuration. In the standalone configuration, WTRUs 102a, 102b, 102c can communicate with gNBs 180a, 180b, 180c without also accessing other Petition 870250091342, dated 07 / 10 / 2025, p. 33 / 115 25 / 78 RANs (e.g., eNode-Bs 160a, 160b, 160c). In a standalone configuration, WTRUs 102a, 102b, 102c can use one or more gNBs 180a, 180b, 180c as a mobility anchor point. In a standalone configuration, WTRUs 102a, 102b, 102c can communicate with gNBs 180a, 180b, 180c using signals in an unlicensed band. In a non-standalone configuration, WTRUs 102a, 102b, 102c can communicate with / connect to gNBs 180a, 180b, 180c while also communicating with / connecting to another RAN, such as eNode-Bs 160a, 160b, 160c. For example, WTRUs 102a, 102b, 102c can implement DC principles to communicate with one or more gNBs 180a, 180b, 180c and one or more eNode-Bs 160a, 160b, 160c in a substantially simultaneous manner.In the non-standalone configuration, eNode-Bs 160a, 160b, 160c can serve as a mobility anchor for WTRUs 102a, 102b, 102c, and gNBs 180a, 180b, 180c can provide additional coverage and / or throughput to support WTRUs 102a, 102b, 102c.

[073] Each of the gNBs 180a, 180b, 180c can be associated with a specific cell (not shown) and can be configured to handle radio resource management decisions, handover transfer decisions, user scheduling in the UL and / or DL, network slicing support, dual connectivity, interoperability between NR and E-UTRA, user plane data routing to user plane functions (UPFs) 184a, 184b, control plane information routing to access and mobility management functions (AMFs) 182a, 182b and similar. As shown in Figure 1 D, the gNBs 180a, 180b, 180c can communicate with each other via an Xn interface.

[074] The CN 115 shown in Figure 1D may include at least one AMF 182a, 182b, at least one UPF 184a, 184b, at least one function of Petition 870250091342, dated 07 / 10 / 2025, page 34 / 115 26 / 78 Session Management Framework (SMF) 183a, 183b and possibly a Data Network (DN) 185a, 185b. Although each of the above elements is described as part of CN 115, it will be understood that any of these elements may be owned and / or operated by an entity other than the CN operator.

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

[076] SMF 183a, 183b can be connected to AMF 182a, 182b on CN 115 via an N11 interface. SMF 183a, 183b can also be connected to UPF 184a, 184b on CN 115 via an N4 interface. SMF 183a, 183b can select and control UPF 184a, 184b and configure traffic routing. Petition 870250091342, dated 07 / 10 / 2025, page 35 / 115 27 / 78 via UPF 184a, 184b. SMF 183a, 183b can perform other functions such as managing and allocating UE IP addresses, managing PDU sessions, controlling policy and QoS enforcement, providing downlink data notifications, and similar functions. A PDU session type can be IP-based, non-IP-based, Ethernet-based, and similar.

[077] UPF 184a, 184b can be connected to one or more gNBs 180a, 180b, 180c in RAN 113 via an N3 interface, which can provide WTRUs 102a, 102b, 102c with access to packet-switched networks, such as the Internet 110, for example, to facilitate communications between WTRUs 102a, 102b, 102c and IP-enabled devices. UPF 184, 184b can perform other functions such as packet routing and forwarding, user plane policy enforcement, support for multi-domestic PDU sessions, user plane QoS handling, downlink packet buffering, mobility tethering provision, and the like.

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

[079] In view of Figures 1A-1D, and the corresponding description of the Figures Petition 870250091342, dated 07 / 10 / 2025, p. 36 / 115 28 / 78 1A-1D, one or more, or all, of the functions described in this document with respect to one or more of the following: WTRUs 102a-d, base stations 114a-b, eNodeBs 160a-c, MME 162, SGW 164, PGW 166, gNBs 180a-c, AMFs 182a-b, UPFs 184ab, SMFs 183a-b, DNs 185a-b, and / or any other element(s) / device(s) described in this document, may be implemented by one or more emulation elements / devices (not shown). Emulation devices may be one or more devices configured to emulate one or more, or all, of the functions described in this document. For example, emulation devices may be used to test other devices and / or simulate network and / or WTRU functions.

[080] Emulation devices can be designed to implement one or more tests of other devices in a laboratory environment and / or in a carrier network environment. For example, one or more emulation devices may perform one or more, or all, of the functions while being wholly or partially implemented and / or deployed as part of a wired and / or wireless communication network to test other devices within the communication network. One or more emulation devices may perform one or more, or all, of the functions while being temporarily implemented / deployed as part of a wired and / or wireless communication network. The emulation device (e.g., a network node) may be directly coupled to another device for testing purposes and / or may perform tests using wireless communications over the air.

[081] One or more emulation devices may perform one or more functions, including all, without being implemented / deployed as part of a network node (e.g., wired and / or wireless communication network). For example, Petition 870250091342, dated 07 / 10 / 2025, page 37 / 115 29 / 78 Emulation devices can be used in a test scenario in a test laboratory and / or an undeployed wired and / or wireless communication network (e.g., test) to implement the testing of one or more components. One or more emulation devices can be test equipment. Direct RF coupling and / or wireless communications via an RF circuit array (e.g., which may include one or more antennas) can be used by the emulation devices to transmit and / or receive data.

[082] Referring to Figure 2, an architecture for enabling edge applications is shown. Thus, the SA6 architecture is defined in the document “3GPP TS 23.558 V18.1.0 (2022-12) “Architecture for edge application enabling”. The high-level architecture for enabling edge applications shown in Figure 2 describes an edge enabling layer, EEL, which can allow applications on a wireless transmit / receive unit, WTRU, to consume edge services from a mobile network. The core functionality offered by the EEL can allow a WTRU to be provisioned with edge connectivity information, to discover available edge services, and to maintain edge service while moving through the mobile network.

[083] An application client, AC, is a user application that resides in a WTRU that communicates with an EAS. A WTRU can use multiple ACs simultaneously.

[084] An edge application server, EAS, is an application server residing on an edge data network, EDN. It can be a software server running on generic hardware located at the edge and providing a service to the AC. In the context of a mobility / relocation use case, the originating EAS, S-EAS, is an instance of an EAS in an initial location and serving the AC before the Petition 870250091342, dated 07 / 10 / 2025, page 38 / 115 30 / 78 mobility / relocation occurs, and the target EAS, T-EAS, is an instance of an EAS in a target location and serving the AC after the mobility / relocation occurs. There can be multiple EAS instances per EDN. Each EDN can contain a different set of EAS instances of different types; an EAS can serve one or more AC instances that may reside in different WTRUs.

[085] An edge enabler client, EEC, can provide edge support to AC instances in the WTRU. There can be one or more EECs per WTRU. Each AC can use only one EEC.

[086] An edge enabler server, EES, can provide necessary support functions for EAS and EEC. In the context of a mobility / relocation use case, the source EES, S-EES, is the EES used before the mobility / relocation occurs, and the destination EES, T-EES, is the EES used after the mobility / relocation has occurred. There can be one or more EES instances per EDN or per data network name, DNN. There can be multiple EDN instances in the network.

[087] An edge configuration server, ECS, can provide support functions for an EEC or EES to discover EES instances that provide certain EAS. There may be one or more ECSs for the network.

[088] A notification management client, NMC, can provide support functions for an EEC to create a notification channel between the NMC and the NMS to receive notifications from the ECS or EES. Each EEC uses only one NMC.

[089] A notification management server, NMS, can provide support functions for an ECS or EES to send notifications to an EEC through a notification channel created between the NMC and the NMS. There may be one or more NMSs for the network. Petition 870250091342, dated 07 / 10 / 2025, page 39 / 115 31 / 78

[090] The main passive and active features of the SA6 architecture are described below.

[091] A passive resource can represent information stored on a server; a passive resource can primarily consume storage resources (e.g., memory, disk space) of the server. The information associated with the passive resource can be used internally by the server, can be accessed externally through an application programming interface, API, can change over time, can be information related to internal server states, or can be information related to external server clients.

[092] An active resource can represent actions performed on a server. An active resource can (for example, primarily) consume server processing and / or network resources. The actions associated with the active resource can be triggered by internal server operations, can be triggered by interaction with an external client via an API, can vary over time, can require temporary execution and communication, and can require constant or periodic execution and communication.

[093] Passive resources in EES may include the EEC context created when an EEC registers with an EES, the EAS profile created when an EAS registers with an EES, the various subscriptions created when EES clients (e.g., EEC, EAS, EES) subscribe to EES event notifications.

[094] Active features in EES may include the detection of events related to subscriptions created by EES clients (e.g., EEC, EAS, EES), the detection and processing of application context relocation (ACR) events that are initiated in EES and related to an application client. Petition 870250091342, dated 07 / 10 / 2025, p. 40 / 115 32 / 78 (AC) communicating with an EAS, the periodic events of 5GS (e.g., WTRU location) that can be requested from the 5GS by the EES.

[095] Passive resources in ECS may include the EES profile created when an EES registers with an ECS, the various subscriptions created when ECS clients (e.g., EEC, EES, ECS) subscribe to ECS event notifications.

[096] Active features in ECS may include the detection of events related to subscriptions created by ECS clients (e.g., EEC, EES, ECS), periodic 5GS events (e.g., EU location) that may be requested from 5GS by ECS.

[097] To enable server cluster support in the EEL, solutions are desired for the following aspects: The content of ECS / EES server cluster information and how it should be provisioned or managed and distributed throughout the EEL. The actions that should be triggered on an active ECS or an active EES and their related consumer nodes to support server switching in planned and unplanned service unavailability use cases.

[098] The terminology applicable to the description below is defined in this document:

[099] An active server is a server instance (for example, EES or ECS) associated with a server pool. The active server instance can be used by a consumer node.

[0100] An alternate server is a server instance (for example, EES or ECS) associated with a server pool. The alternate server instance cannot be used by a consumer node and can be considered a replacement server instance for an active server. Petition 870250091342, dated 07 / 10 / 2025, page 41 / 115 33 / 78

[0101] A consumer node is a node instance (for example, WTRU, EEC, EAS, EES) that can consume services from an active server instance associated with a server pool.

[0102] A Server Set Management Function, SSMF, is a network function that resides on a network node. An SSMF can provide functionality for managing server set configuration, generating server set events, and switching from an active server to an alternate server. The SSMF can be implemented on an active server, such as EES or ECS, or it can also be implemented on a standalone network node.

[0103] An SSMF client describes client-side functionality that resides on a node that consumes services from an active server (e.g., EES, ECS) associated with a server pool; the SSMF client can be implemented on a consumer node, such as WTRU, EEC, EAS, or EES, that consumes services from an active server.

[0104] The SSMF client and the consumer node can be used interchangeably in this document.

[0105] Below is a description of examples of provisioning and managing server sets.

[0106] Server collection configuration data is required to maintain the association between server instances included in a server collection. Server collection configuration data may include identifiers of server instances included in the server collection and an indication of the server collection type (e.g., for ECS, for EES).

[0107] For example, an EES server set may include an indication that the server set type is for EESs and the identifiers of Petition 870250091342, dated 07 / 10 / 2025, page 42 / 115 34 / 78 EES, EESIDs, identifying EES instances from the server set.

[0108] For example, an ECS server set may include an indication that the server set is for ECSs and configuration information for ECSs (e.g., an IP, URI, FQDN, and / or PLMN) identifying ECS ​​instances within the server set.

[0109] Server configuration data (or server(s)) can be enhanced with additional information to facilitate use or limit the scope of a server set. Additional configuration data may include active server identifiers (e.g., EESID or ECS-IP or ECS-URI or ECS-FQDN or PLMN) that identify active servers to which the server set applies, connectivity information (e.g., DNN / APN, SNSSAI) for each server instance in the server set that identifies how to establish connectivity with servers in the server set, EES endpoint information (e.g., EES-IP or EES-URI or EES-FQDN) that identifies the endpoint information associated with each EESID.Additional configuration data may include edge computing service provider (ECSP) information, information (e.g., ECSP identifier) ​​associated with the server set or each server in the server set indicating a validity condition based on the ECSP, service area information (e.g., topological, geographic) associated with the server set or each server instance in the server set indicating a validity condition based on geography or network topology, time period associated with the server set or each server in the server set indicating a validity condition based on time, and server priority information associated with each server in the server set. Petition 870250091342, dated 07 / 10 / 2025, page 43 / 115 35 / 78 servers, indicating the order of priority in which servers should be considered in the event of an active server failure.

[0110] Server set configuration data can be obtained by a consumer node following different scenarios. Server set configuration data can be pre-provisioned on a consumer node, or it can be provisioned to a consumer node when configuring the consumer node, or it can be provisioned to a consumer node when detecting a real-time event or predicting an anticipatory event that requires an active server to be replaced by an alternative server.

[0111] In any scenario, the consumer node can be informed or aware that a server set is being used to ensure that the consumer node's behavior conforms to the server set usage. The consumer node can be informed about server set usage through a static configuration on the consumer node indicating that server sets are always / never used, or through receiving a server set configuration indication that server sets are used for all or a subset of the ECS / EES servers, or implicitly by receiving server set configuration data.

[0112] For scenarios where the consumer node obtains server set configuration data from a source other than the active server (for example, pre-configured or configured by an external source), the consumer node may need to indicate to the active server that a server set is being used to ensure that the active server's behavior is compatible with the use of the server set. The active server can be informed about the use of the server set through a static configuration on the active server, indicating that the Petition 870250091342, dated 07 / 10 / 2025, page 44 / 115 36 / 78 server sets are always used / never used, either by receiving a server set configuration indication from the consumer node that the server sets are used for all or a subset of the ECS / EES servers, or implicitly by receiving server set configuration data or a subscription to server set events.

[0113] For a WTRU (e.g., EEC) as a consumer node of an ECS, the ECS server set configuration data may be preconfigured with the WTRU or EEC, or may be configured by an application client, AC, edge-aware, or may be configured by a user, or may be provisioned by a mobile network operator, MNO, via the 5GC procedure if the MNO has the capability to deliver ECS server set configuration data to the WTRU and the WTRU has the capability to deliver ECS server set configuration data to the EEC on the WTRU.In addition, ECS server set configuration data can be provided to WTRU or EEC via a service provisioning procedure with an ECS (including request / response or subscription / notification mechanisms), or it can be provided via a dedicated procedure with the ECS, or it can be provided via a notification event when the active server is replaced by an alternative server.

[0114] For a WTRU (e.g., EEC) as a consumer node of an EES, the EES server set configuration data can be preconfigured with the WTRU or EEC, or can be configured by an edge-aware AC, or can be configured by a user. Additionally, the EES server set configuration data can be provided to the WTRU or EEC. Petition 870250091342, dated 07 / 10 / 2025, page 45 / 115 37 / 78 through an EEC registration procedure with an EES, or they can be provided to WTRU or EEC through an EAS discovery procedure with an EES (e.g., including request / response or subscription / notification mechanisms), or they can be provided through a dedicated procedure with the EES, or they can be provided through a notification event when the active server is replaced by an alternative server.

[0115] For the EAS as a consumer node of an EES, the EES server set configuration data can be pre-configured with the EAS, or can be provided to the EAS via an EAS registration procedure with an EES, or can be provided via a dedicated procedure with the EES, or can be provided via a notification event when the active server is replaced by an alternate server.

[0116] For the EES as a consumer node of an ECS, the ECS server set configuration data can be pre-configured with the EES, or can be provided to the EES via an EES registration procedure with an ECS, or can be provided via a dedicated procedure with the ECS, or can be provided via a notification event when the active server is replaced by an alternate server.

[0117] When obtaining server set configuration data, the consumer node can validate the server set configuration to verify that it is associated with at least one server used by the consumer node, can store the server set configuration data and associate it with one or more active servers, can retrieve connectivity data (e.g., service provisioning procedure) based on alternate servers and validity conditions present in the server set configuration, can Petition 870250091342, dated 07 / 10 / 2025, page 46 / 115 38 / 78 establish connectivity with EDNs associated with alternative servers.

[0118] A consumer node can indicate a capacity to support server sets for a server that implements SSMF. SSMF can take into account the consumer node's capacity to determine whether the server set configuration should be provided to the consumer node.

[0119] The resource can be provided by the consumer node to the SSMF as part of the procedures mentioned above. For example, when the consumer node is a WTRU (e.g., EEC), the consumer node's capacity can be provided to an ECS that implements SSMF when the WTRU performs the service provision procedure; the consumer node's capacity can be provided to an EES that implements SSMF when the WTRU performs the EEC registration, EAS discovery, or EAS information provision procedures. For example, when the consumer node is an EAS, the consumer node's capacity can be provided to an EES that implements SSMF when the EAS performs EAS registration. For example, when the consumer node is an EES, the consumer node's capacity can be provided to an ECS that implements SSMF when the EES performs EAS registration.

[0120] Capacity can be implicitly provided by the consumer node to SSMF as part of the server-defined event subscription.

[0121] The consumer node can be notified of server set events when an active server needs to be relocated to an alternate server or when server set configuration data changes. For example, if an SSMF is configured to shut down, it can send a server set event to consumer nodes to indicate its impending unavailability. For example, if the SSMF is enrolled in a role of Petition 870250091342, dated 07 / 10 / 2025, page 47 / 115 39 / 78 Network Data Analysis (NWDAF) in a 5G system, the SSMF can be informed that connectivity to the SSMF is down or should be down and send server-defined events to consumer nodes accordingly.

[0122] To receive notifications related to server-defined events, the consumer node can subscribe with the network node that implements SSMF and can maintain a valid subscription (for example, the subscription must not expire).

[0123] In certain implementations, the subscription may be associated with an expiration time, and the consumer node may need to renew its subscription to extend its validity.

[0124] A consumer node can be notified of a server pool event when an active server needs to be replaced by an alternate server (for example, a server switch notification). The server switch notification sent to the consumer node can include information about the alternate server selection, can include any service pool configuration information, can include an indication that registration on the alternate server is required, can include timing information indicating when the alternate server will be ready (for example, when the transition from the active server to the alternate server will be complete), and can include subscription identifier information if the consumer subscription identifiers on the active server are changed after the transition on the alternate server.

[0125] Upon receiving a server switching notification, the consumer node can validate the notification to verify if it is associated with a server used by the consumer node, can perform an alternate server selection based on the server pool configuration if the alternate server is not indicated in the notification, and can retrieve connectivity information about the server. Petition 870250091342, dated 07 / 10 / 2025, page 48 / 115 The selected alternate server (40 / 78) can establish connectivity (e.g., PDU session with EDN) with the alternate server, can register with the alternate server, can store and use any server set configuration information provided in the notification to identify and access the alternate server, can replace any bindings to the active server with bindings to the alternate server, can set a timer based on the timing information provided to delay access to the alternate server, and can update existing subscription identifiers obtained from the active server with newly provided valid subscription identifiers on the alternate server.

[0126] As a result of the server switching notification being received and processed on the consumer node, it can be observed that the consumer node can interact with the alternate server.

[0127] A consumer node can be notified of a server set event when the server set configuration changes (for example, a server set configuration update); for example, if an alternate server suddenly becomes unavailable, it can be removed from the server set or replaced with another alternate server. The notification sent to the consumer node can include any server set configuration information or can indicate that the server set is no longer in use.

[0128] Upon receiving the server set configuration update notification, the consumer node can validate the notification to verify if the request is associated with a server used by the consumer node, can trigger a request to SSMF for new server set configurations, and can store and update its server set configuration according to the received server set configuration information. Petition 870250091342, dated 07 / 10 / 2025, page 49 / 115 41 / 78 and can perform any processing related to receiving a server set configuration.

[0129] Figure 3 shows examples of a message sequence graph for an edge system. Referring to Figure 3, an edge system is shown where the SSMF can be an EES or ECS and where the consumer node can be an EAS or EEC. Alternatives for provisioning the server set configuration for the consumer node are shown. Several server set provisioning modes can occur in the same system, for example, an ECS can provide ECS server set information to the EEC in the service provisioning procedure and an EES can provide EES server set information to both the EEC and the EAS in the EEC / EAS registration procedures.

[0130] Referring to 1, in one embodiment, a consumer node may send a server set provisioning request (1a) to an SSMF (e.g., EES, ECS) to obtain the server set configuration. The provisioning request may indicate to the SSMF the server set capacity so that the consumer node can support the server set functionality and may contain server set parameters that may include active server identifiers (e.g., EES and / or ECS identifiers) indicating for which servers the configuration is applicable. The provisioning request may additionally include ECSP identifier(s) indicating ECSPs for which the configuration is requested.The provision request may additionally include a service area (e.g., topological or geographic) indicating the service area for which the configuration is requested and may include a time period indicating the time during which the configuration should be valid.

[0131] After receiving and processing the request, the SSMF may identify or Petition 870250091342, dated 07 / 10 / 2025, page 50 / 115 42 / 78 create a server set configuration that meets the requirements for the server set parameters provided in the request and may send a server set configuration response, including the server set configuration, to the consumer node. If SSMF is unable to provide a server-defined configuration, SSMF may provide an error code and a reason for not providing a server-defined configuration.

[0132] Upon receiving the server pool provisioning response, the consumer node can perform server pool configuration processing.

[0133] Referring to 2, in one embodiment, a registration procedure may be performed when the consumer node is an EEC (e.g., UE) or EAS and the SSMF is an EES. The EEC registration procedure or the EAS registration procedure may be enhanced to provide, respectively, the EEC or EAS server set capability to the EES in the request message and to provide the server set configuration, respectively, to the EEC or EAS in the response message. The EEC may send an EEC registration request (2a) or the EAS may send an EAS registration request (2a) to the EES and the request may include an indication that the EEC or EAS supports server set functionality and may include server set parameters.

[0134] After receiving and processing the request, SSMF may provide a server pool configuration that meets the server pool parameters provided in the request and return it to EEC / EAS in the EEC / EAS registration response (2b). If SSMF cannot provide a server pool, it may indicate this to EEC / EAS in the EEC / EAS registration response. The response of Petition 870250091342, dated 07 / 10 / 2025, page 51 / 115 43 / 78 EEC / EAS record may include a cause and a reason for failure.

[0135] Referring to 3, in one embodiment, the registration procedure can be performed when the consumer node is an EEC (e.g., WTRU) and the SSMF is an EES. The EAS discovery procedure can be improved to provide the EEC server set capability to the EES in the request message and to provide the server set configuration to the EEC in the response message. The EEC can send an EAS discovery request (3a) to the EES and can include an indication that the EEC supports server set functionality and can include server set parameters.

[0136] After receiving and processing the request, SSMF provides a server set configuration that meets the server set parameters provided in the request and returns it to EEC in the EAS discovery response (3b). If SSMF is unable to provide a server set, it may indicate this in the EAS discovery response. The EAS discovery response may include a cause and reason for failure.

[0137] Referring to 4, in one embodiment, a service provisioning procedure may be performed when the consumer node is an EEC (e.g., WTRU) and the SSMF is an ECS. The service provisioning procedure may be enhanced to provide the EEC server set capability to the ECS in the request message and to provide the server set configuration to the EEC in the response message. The EEC may send a service provisioning request (4a) to the ECS and may include an indication that the EEC supports server set functionality and may include server set parameters. Petition 870250091342, dated 07 / 10 / 2025, p. 52 / 115 44 / 78

[0138] After receiving and processing the request, SSMF provides a server set configuration that meets the server set parameters provided in the request and returns it to EEC in the service provision request (4b). If SSMF cannot provide a server set, it may indicate this in the service provision response.

[0139] Referring to 5, the procedure can be performed when the consumer node is an EES and the SSMF is an ECS. The EES registration procedure can be improved to provide the EES server set capability to the ECS in the request message and to provide the server set configuration to the EES in the response message. The EES can send an EES registration request (5a) to the ECS and the request can include an indication that the EES supports server set functionality and can include server set parameters.

[0140] After receiving and processing the request, SSMF can provide a server set configuration that meets the server set parameters provided in the request and return it to EES in the EES registration response. If SSMF is unable to provide a server set, it may indicate this to EES in the EES registration response; the response may include a cause and reason for the failure.

[0141] Referring to 6, in one embodiment, the consumer node may send a server set subscription (6a) to SSMF to receive notifications related to server set events that may be detected on the network. The subscription request may include an indication for server switching related events and may include an indication to receive server set configuration update related events. Petition 870250091342, dated 07 / 10 / 2025, page 53 / 115 45 / 78

[0142] After receiving and processing the request, SSMF may include a subscription identifier in the server set subscription response (6b) and may initiate detection of server set subscription events. If SSMF is unable to allocate resources or perform server set event detection, SSMF may indicate a server set subscription / registration response failure and may include a reason.

[0143] Referring to 7, in one embodiment, after the detection of a server set event (7a), the SSMF may send a server set notification (7b) to the consumer node on the condition that a consumer node has subscribed to that event, indicating the detected event and providing additional information. After receiving the server set notification, the consumer node may perform event processing.

[0144] For all procedures mentioned in this clause, upon indication of failure, the consumer node may retry considering the cause of the failure; otherwise, the consumer node may wait a certain period before making another attempt. For example, the consumer node may start a timer associated with the failure cause code, and only after the timer expires may the consumer node make another attempt to send a server-defined subscription request.

[0145] In the description below, details about the “break-beforemake”, BBM, procedure are detailed.

[0146] In several modes, the replacement of an active EES server may not be planned. For example, an active server may lose power or connectivity and become inaccessible. Server switching can be performed in a “break-before-make” (BBM) manner, allowing the migration of consumer nodes (e.g., EAS, EEC) to an alternative EES server after the active server fails. Petition 870250091342, dated 07 / 10 / 2025, page 54 / 115 46 / 78 will be unavailable.

[0147] Figure 4 shows an example of a procedure for consumer nodes, active EES and alternative EES reconfiguration in a “break-before-make” scenario.

[0148] Prior to the BBM procedure, consumer nodes (e.g., EEC, EAS) may have discovered the active EES, may have been configured with an EES server set, and may have subscribed to events from the EES server set.

[0149] To support break-beforemake (BBM) server switching using a server set, a synchronization methodology can be pre-established between the servers in the server set. The synchronization methodology can be centralized and based on shared storage. Servers in the server set can continuously publish information about their passive and active resources to shared storage to make resource information available to other servers in the server set in case of unexpected unavailability.

[0150] Alternatively, the synchronization methodology can be distributed and based on a message scheme. Servers in the server set can continuously send information about their passive and active resources by sending messages to all other servers in the server set. Regardless of the synchronization mechanism, information provided by an active server (e.g., centralized or distributed) remains inactive on alternative servers until an alternative server is informed that a server switch is required.

[0151] Referring to 1, the active EES, active-EES and the alternative EESs, alt Petition 870250091342, dated 07 / 10 / 2025, page 55 / 115 47 / 78 EES, members of the same set of EES servers, can publish data about passive and active resources in a centralized or distributed manner.

[0152] Referring to 2, the consumer node (e.g., EEC or EAS) may make a request with the active EES, and the request may fail, indicating that the active EES is unexpectedly unavailable. For example, a consumer node may consider a request timeout failure to indicate that a server is unavailable, while a “forbidden” response indicates another problem. Alternatively, the consumer node (or nodes) may implement a watchdog mechanism to allow for consistent detection of active server unavailability. For example, the consumer node may periodically send a keepalive request to the active server to perform timely unavailability detection.

[0153] Referring to 3, the consumer node can perform a selection of an alternate EES based on the server pool configuration that was provisioned. The selection can be based on KPIs similar to those of the active EES or it can be based on other validity conditions such as ECSP, service area, time and alternate server priority.

[0154] Referring to 4, the consumer node can send a server switching request to the selected alternate EES, providing in the server switching request an EEC or EAS instance identifier. The EEC or EAS identifier can be used by the alternate EES to identify passive and active resources associated with the consumer node. Data about the passive and active resources may be available in a shared store or in the alternate EES, depending on whether a centralized or distributed synchronization mechanism is used.

[0155] Referring to 5, upon receiving the server switching request from Petition 870250091342, dated 07 / 10 / 2025, page 56 / 115 48 / 78 consumer node, the alternate EES can integrate the active, passive, and asset resources of the EES associated with the consumer node and can identify itself using the EEC or EAS instance identifier. The integration of received resources may require any of the following: (1) storing the data related to the identified resources in the alternate EES, (2) validating that the identified resources are compatible with the capabilities of the alternate EES, (3) regenerating resource identifiers or uniform resource identifiers, URIs, in the alternate EES for the identified resources, (4) initiating event detection in the alternate EES for the subscription resources, (5) initiating ACR detections in the alternate EES, and (6) requesting periodic 5GS events in the alternate EES.

[0156] Referring to 6, after completing the integration of the passive and active resources identified using the server switching request, the alternate EES may send a server switching response to the consumer node, which may indicate that the resource integration has been completed. The server switching response may additionally contain resource mapping information related to the newly integrated resources in the alternate EES and how these integrated resources are mapped to the resources originally found in the active EES. The server switching response may also contain an indication of procedures required with the alternate EES, which may indicate to the alternate EES that the server switch was successfully completed at the consumer node.For example, resource mapping information might include newly generated URIs or identifiers generated in the alternate EES that may match (e.g., map to) pre-existing resources in the active EES and can be used by the consumer node to retrieve migrated resources. Information about required procedures might be procedure-related information. Petition 870250091342, dated 07 / 10 / 2025, page 57 / 115 49 / 78 existing that the alternate EES requires the consumer node to perform before using the alternate EES, for example, the alternate EES may instruct an EEC to perform an EEC registration update with the alternate EES or the alternate EES may instruct an EAS to perform an EAS registration update with the alternate EES so that the alternate EES can confirm that the server switching was successful and may also allow the alternate EES to acquire endpoint information (e.g., IP address) from the consumer node if needed.

[0157] Referring to 7, upon receiving the server switching response, consumer nodes (e.g., EEC, EAS) may update their bindings with the active EES. To update the bindings, a consumer node may require any of the following: (1) replacing active EES endpoint information with alternate EES endpoint information, (2) performing service provisioning to acquire connectivity information about the alternate EES, (3) creating a PDU session for the EDN associated with the alternate EES, and (4) replacing URIs or identifiers associated with resources that were originally created with the active EES using the mapping information provided in the server switching notification.

[0158] Referring to 8, if the server switching response received in step 6 included an indication of a required procedure, the consumer nodes (e.g., EEC, EAS) can perform the required procedure with the alternate EES. For example, the alternate EES might indicate that updating the EEC or EAS record is required after updating the bindings. This required procedure can allow the alternate EES to confirm that the consumer node migration was completed correctly. Petition 870250091342, dated 07 / 10 / 2025, page 58 / 115 50 / 78

[0159] In several modes, the replacement of an active ECS server may not be planned, for example, an active server may lose power or connectivity and become inaccessible. Server switching can be performed in a “breakbefore-make” manner, allowing the migration of consumer nodes (e.g., EEC, EES) to an alternative ECS server after the active server becomes unavailable.

[0160] Figure 5 shows an example of a procedure for consumer nodes, active ECS and alternative ECS reconfiguration in a “break-before-make” scenario.

[0161] Prior to the BBM procedure, consumer nodes (e.g., EEC, EAS) may have discovered the active ECS, may have been configured with an ECS server set, and may have subscribed to events from the ECS server set.

[0162] To support break-beforemake (BBM) server switching using an ECS server set, a synchronization methodology can be pre-established between the ECSs in the server set. The synchronization methodology can be centralized and based on shared storage or distributed and based on a message scheme.

[0163] Referring to 1, the active ECS and the alternative ECSs, members of the same set of ECS servers, can publish data about passive and active resources in a centralized or distributed manner.

[0164] Referring to 2, the consumer node (e.g., EEC or EES) may make a request with the active ECS, and the request may fail, indicating that the active ECS is unexpectedly unavailable. For example, a consumer node may consider that a request timeout failure indicates that a server Petition 870250091342, dated 07 / 10 / 2025, page 59 / 115 51 / 78 is unavailable, while a “forbidden” response indicates another problem. Alternatively, the consumer node (or nodes) can implement a monitoring mechanism to allow for consistent detection of active server unavailability. For example, the consumer node can periodically send a keepalive request to the active server to perform timely unavailability detection.

[0165] Referring to 3, the consumer node can perform a selection of an alternate ECS based on the server pool configuration that has been provisioned. The selection can be based on KPIs similar to those of the active ECS or it can be based on other validity conditions such as ECSP, service area, time and alternate server priority.

[0166] Referring to 4, the consumer node can send a server switching request to the selected alternate ECS, providing in the server switching request an EEC or EES instance identifier. The EEC or EES identifier can be used by the alternate ECS to identify passive and active resources associated with the consumer node. Data about the passive and active resources may be available in a shared store or in the alternate ECS, depending on the use of a centralized or distributed synchronization mechanism.

[0167] Referring to 5, upon receiving the server switching request from the consumer node, the alternate ECS may integrate the active, passive, and active ECS resources associated with the consumer node and identified using the EEC or EES instance identifier. The integration of the received resources may require either of the following: (1) storing the data related to the identified resources in the alternate ECS, (2) validating whether the identified resources are compatible with the Petition 870250091342, dated 07 / 10 / 2025, pages 60 / 115 52 / 78 alternate ECS capabilities, (3) regenerate resource identifiers or URIs in the alternate ECS for the identified resources, (4) initiate event detection in the alternate ECS for the subscription resources, and (5) request periodic 5GS events in the alternate ECS.

[0168] Referring to 6, after completing the integration of the passive and active resources identified using the server switching request, the alternate ECS may send a server switching response to the consumer node, which may indicate that the resource integration has been completed. The server switching response may additionally contain resource mapping information related to the newly integrated resources in the alternate ECS and how these integrated resources are mapped to the resources originally found in the active ECS. The server switching response may also contain an indication of procedures required with the alternate ECS, which may indicate to the alternate ECS that the server switch was successfully completed at the consumer node.For example, resource mapping information might include newly generated URIs or identifiers generated in the alternate ECS that may match (e.g., map to) pre-existing resources in the active ECS and can be used by the consumer node to retrieve migrated resources. Information about required procedures might be information related to existing procedures that the alternate ECS requires the consumer node to perform before using the alternate ECS. For example, the alternate ECS might instruct an EEC to perform a service provisioning request with the alternate ECS, or the alternate ECS might instruct an EES to perform an EES record update with the alternate ECS so that the alternate ECS can confirm that the server switch was successful and may also allow the alternate ECS to acquire the... Petition 870250091342, dated 07 / 10 / 2025, pp. 61 / 115 53 / 78 endpoint information (e.g., IP address) of the consumer node, if necessary.

[0169] Referring to 7, upon receiving the server switch response, consumer nodes (e.g., EEC, EES) may update their bindings with the active ECS. To update the bindings, a consumer node may require any of the following: (1) replacing active ECS endpoint information with alternate ECS endpoint information, (2) performing service provisioning to acquire connectivity information about the alternate ECS, (3) creating a PDU session for the EDN associated with the alternate ECS, and (4) replacing URIs or identifiers associated with resources that were originally created with the active ECS using the mapping information provided in the server switch notification.

[0170] Referring to 8, if the server switching response received in step 6 included an indication of a required procedure, the consumer nodes (e.g., EEC, EES) can perform the required procedure with the alternate ECS. For example, the alternate ECS might indicate that the EEC should perform service provisioning with the alternate ECS or that the EES should perform an EES registration update after updating the bindings. This required procedure can allow the alternate ECS to confirm that the consumer node migration was completed correctly.

[0171] In several modes, the replacement of an active EES server can be planned, triggered, and managed to minimize service downtime. Server switching can be performed in a “make-before-break” manner, allowing the migration of consumer nodes (e.g., EAS, EEC) to an alternative EES before the active EES becomes unavailable. Petition 870250091342, dated 07 / 10 / 2025, page 62 / 115 54 / 78

[0172] Figure 6 shows an example of a procedure for reconfiguring a consumer node, active EES and alternative EES in a “make-before-break”, MBB scenario.

[0173] Prior to the MBB procedure, consumer nodes (e.g., EEC, EAS) may have discovered the active EES, may have been configured with an EES server set, and may have subscribed to events from the EES server set.

[0174] Referring to 1, an active EES implementing an SSMF may detect that it will become unavailable. For example, the SSMF may detect that an EES is configured to shut down in order to perform EES maintenance. For example, the SSMF may be enrolled in an NWDAF network role in the 5G system; the SSMF may detect unavailability when it is informed that connectivity to the SSMF will be down. The active EES may detect that it is configured to migrate consumer nodes to an alternate EES before becoming unavailable (for example, if the active EES deploys an SSMF and is configured with a server pool).

[0175] Referring to item 2, the active EES can cancel the ECS registration where it was originally registered, for example, to make the EES undetectable through the service provision procedure with the ECS.

[0176] Referring to 3, the active EES can perform a selection of an alternative EES based on the defined server configuration. The selection can be based on KPIs similar to those of the active EES or it can be based on other validity conditions such as ECSP, service area, time and alternative server priority.

[0177] Referring to 4, the active EES can send a notification of Petition 870250091342, dated 07 / 10 / 2025, page 63 / 115 55 / 78 Server Switching (4a) to consumer nodes (e.g., EEC, EAS) to provide an advance indication that server switching has begun. The server switching notification may include an identifier of the selected alternate server. Server switching may additionally include timing information that provides an expected duration for the server switching operation before it becomes available. The consumer node may use the information included in the advance notification to prepare for the server migration. For example, the consumer node may: (1) stop contacting the active server, (2) obtain connectivity information about the alternate server, (3) start a timer before contacting the alternate server.

[0178] The active EES can send a server switching request to the selected alternate EES (4b), providing in the server switching request the data relating to the passive and active resources present in the active EES.

[0179] Referring to 5, upon receiving the server switching request from the active EES, the alternate EES may integrate the passive and active resources of the active EES (5a). The integration of received resources may require any of the following: (1) storing data related to the received resources in the alternate EES, (2) validating that the received resources are compatible with the capabilities of the alternate EES, (3) regenerating resource identifiers or URIs in the alternate EES for the received resources, (4) initiating event detection in the alternate EES for the subscription resources, (5) initiating ACR detections in the alternate EES, and (6) requesting periodic events from 5GS in the alternate EES.

[0180] After sending the server switching request to the alternate EES, the active EES can remove all active and passive resources (5b) that Petition 870250091342, dated 07 / 10 / 2025, pp. 64 / 115 56 / 78 were sent to the alternate EES. Removing resources may require deleting data related to those resources in the active EES, or terminating any processing, such as event detection, or canceling requested periodic events from 5GS.

[0181] Referring to 6, after the integration of the passive and active resources received in the server switching request is complete, the alternate EES may send a server switching response to the active EES that may (1) indicate that resource integration has been completed, (2) contain resource mapping information, and (3) contain an indication of necessary procedures that consumer nodes must perform with the alternate EES.

[0182] Referring to 7, the active EES can send a server switching notification to all consumer nodes (e.g., EEC, EAS) that have subscribed to receive such an event. The server switching notification can contain information related to the alternate EES, for example, the IP address / URL / FQDN, the EES identifier, the EES profile, information about the resource mapping on the alternate server, information about the necessary procedures that consumer nodes must perform with the alternate server. The active EES can provide each individually subscribed consumer node with only a subset of the resource mapping on the alternate server that corresponds to the resources that were related to the specific consumer node.

[0183] Referring to 8, upon receiving the server switching notification, consumer nodes (e.g., EEC, EAS) can update their bindings with the active EES. To update the bindings, a consumer node may require either of the following: (1) replacing active EES endpoint information with alternate EES endpoint information, (2) performing the Petition 870250091342, dated 07 / 10 / 2025, pp. 65 / 115 57 / 78 provision of service to acquire connectivity information about the alternate EES, (3) create a PDU session for the EDN associated with the alternate EES, (4) replace URIs or identifiers associated with resources that were originally created with the active EES using the mapping information provided in the server switching notification.

[0184] Referring to 9, if the server switching notification received in step 7 included an indication of a required procedure, the consumer nodes (e.g., EEC, EAS) can perform the required procedure with the alternate EES. For example, the alternate EES might indicate that updating the EEC / EAS record is required after updating the bindings. This required procedure can allow the alternate EES to confirm that the consumer node migration was completed correctly.

[0185] The MBB procedure shown in Figure 6 does not depend on centralized or distributed synchronization between the servers in the server set.

[0186] It can be seen that the make-before-break, MBB, procedure of EES may depend on synchronization mechanisms with the following change in Figure 6: In step 4, the server switching request sent from the active EES to the alternate EES may contain consumer node instance identifiers (e.g., EEC, EAS) of all consumer nodes related to the active EES and for which the active EES selected the alternate EES. In step 5a, the alt-EES may retrieve from shared storage the passive and active resource data associated with the consumer node instance identifier. This is similar to steps 4 and 5 in Figure 4.

[0187] In several ways, replacing an active ECS server can Petition 870250091342, dated 07 / 10 / 2025, page 66 / 115 58 / 78 must be planned, triggered, and managed to minimize service downtime. Server switching can be performed in a "make-before-break" (MBB) manner, allowing the migration of consumer nodes (e.g., EAS, EES) to an alternate ECS before the active ECS becomes unavailable.

[0188] Figure 7 shows an example of a procedure for reconfiguring a consumer node, active ECS and alternate ECS in an MBB scenario.

[0189] Prior to the MBB procedure, consumer nodes (e.g., EEC, EES) may have discovered the active ECS, may have been configured with an ECS server set, and may have subscribed to events from the ECS server set.

[0190] Referring to 1, an active ECS implementing an SSMF can detect that it will become unavailable (for example, if an ECS is configured to shut down in order to perform ECS maintenance). The active ECS can detect that it is configured to migrate consumer nodes to an alternate ECS before becoming unavailable, for example, if the active ECS implements an SSMF and is configured with a server pool.

[0191] Referring to 2, the active ECS can perform a selection of an alternative ECS based on the configuration defined by the server. The selection can be based on KPIs similar to those of the active ECS or it can be based on other validity conditions such as ECSP, service area, time and alternative server priority.

[0192] Referring to 3, the active ECS can send a server switching notification (3a) to consumer nodes (e.g., EEC, EES) to provide early indication that server switching has begun. A Petition 870250091342, dated 07 / 10 / 2025, page 67 / 115 59 / 78 Server switch notification may include an identifier of the selected alternate server. The server switch notification may additionally include timing information, providing an expected duration for the server switch operation before it becomes available. The consumer node may use the information included in the advance notification to prepare for the server migration. For example, the consumer node may: (1) stop contacting the active server, (2) obtain connectivity information about the alternate server, and (3) start a timer before contacting the alternate server.

[0193] The active ECS can send a server switching request to the selected alternate ECS (3b), providing in the server switching request the data related to the passive and active resources present in the active EES.

[0194] Referring to 4, upon receiving the server switching request from the active ECS, the alternate ECS may integrate the passive and active resources of the active ECS (4a). The integration of received resources may require (1) storing data related to the received resources in the alternate ECS, (2) validating that the received resources are compatible with the capabilities of the alternate ECS, (3) regenerating resource identifiers or URIs in the alternate ECS for the received resources, (4) initiating event detection in the alternate ECS for the subscription resources, and (5) requesting periodic 5GS events in the alternate ECS.

[0195] After sending the server switching request to the alternate ECS, the active ECS can remove all active and passive resources (4b) that were sent to the alternate ECS. Removing resources may require deleting data related to the resources in the active ECS, or terminating any processing, such as event detection, or canceling periodic events. Petition 870250091342, dated 07 / 10 / 2025, pp. 68 / 115 60 / 78 requested from 5GS.

[0196] Referring to 5, upon completion of the integration of passive and active resources received in the server switching request, the alternate ECS may send a server switching response to the active ECS, which may indicate that resource integration has been completed. The server switching response may contain resource mapping information and may contain indication of procedures required with the alternate ECS. The details regarding the server switching response are the same as in step 6 of Figure 5.

[0197] Referring to 6, the active ECS can send a server switching notification to all consumer nodes (e.g., EEC, EES) that have subscribed to receive such an event. The server switching notification can contain information related to the alternate ECS, for example, the IP address / URL / FQDN, the ECS identifier, the ECS profile, information about the resource mapping on the alternate server, information about the necessary procedures that the consumer node must perform with the alternate server. The active ECS can provide each individually subscribed consumer node with only a subset of the resource mapping on the alternate server that corresponds to the resources that were related to the specific consumer node.

[0198] Referring to 7, upon receiving the server switching notification, consumer nodes (e.g., EEC, EES) can update their bindings with the active ECS. To update the bindings, a consumer node may require replacing endpoint information from the active ECS with endpoint information from the alternate ECS. The consumer node may require executing the service provision to acquire connectivity information about the alternate ECS. The consumer node may require creating a PDU session to Petition 870250091342, dated 07 / 10 / 2025, page 69 / 115 61 / 78 the EDN associated with the alternate ECS. The consumer node may require the replacement of URIs or identifiers associated with resources that were originally created with the active ECS using the mapping information provided in the server switch notification.

[0199] Referring to 8, if the server switching notification received in step 6 included an indication of a required procedure, the consumer nodes (e.g., EEC, EES) may perform the required procedure with the alternate ECS. For example, the alternate ECS may indicate that the EEC must perform a service provision with the alternate ECS and may indicate that the EES must perform an EES registration update with the alternate ECS after updating the bindings. This required procedure may allow the alternate ECS to confirm that the consumer node migration was completed correctly.

[0200] The procedure shown in Figure 7 does not depend on centralized or distributed synchronization between the servers in the server set.

[0201] It can be understood that the ECS make-before-break procedure may depend on synchronization mechanisms with the following change in Figure 7: in step 3, the server switching request sent from the active ECS to the alternate ECS may contain consumer node instance identifiers (e.g., EEC, EES) of all consumer nodes related to the active ECS and for which the active ECS selected the alternate ECS. In step 4a, the alt-EES may retrieve from shared storage the passive and active resource data associated with the consumer node instance identifier. This is similar to steps 4 and 5 in Figure 4.

[0202] Figure 8 is a flowchart illustrating an example of an 800 method performed by a consumer node to relocate a server in a breakPetition 870250091342, dated 07 / 10 / 2025, page 70 / 115 62 / 78 before-make. The consumer node can be a WTRU, an edge enabler client, an edge application server, or an edge enabler server.

[0203] Referring to Figure 8, method 800 may comprise a first step in which the consumer node (e.g., WTRU) may receive 810 a server pool configuration associated with an active server. Before receiving the server pool configuration, the consumer node (e.g., WTRU) may discover the active server, where the active server may have SSMF capability. More particularly, the SSMF capability may include functionality to manage the server pool configuration and switch from the active server to the alternate server.

[0204] The 800 method may comprise a step where the consumer node (e.g., WTRU) may determine 820 (e.g., detect) the unavailability of the active server. For example, unavailability may be determined due to the expiration of a timeout associated with communication between the active server and the consumer node or due to a communication timeout failure with the active server. In another example of determining active server unavailability, the method may comprise a step of receiving a message from the active server indicating that the active server will soon be unavailable.

[0205] Method 800 may comprise a step in which the consumer node (e.g., WTRU) may select 830 an alternate server based on the received server pool configuration. Method 800 may comprise a step in which the consumer node (e.g., WTRU) may transmit 840 a server switching request message to the alternate server, wherein the server switching request message Petition 870250091342, dated 07 / 10 / 2025, pp. 71 / 115 63 / 78 may include initial information indicating a consumer node identifier (e.g., WTRU).

[0206] Method 800 may comprise a step wherein the consumer node (e.g., WTRU) may receive 850, from the alternate server, a server switching response message, wherein the server switching response message may include procedural information for communication with the alternate server and resource mapping information related to the alternate server. The procedural information may comprise procedures for confirming successful server switching, wherein the procedures for confirming successful server switching may comprise a record update procedure with the alternate server. The server switching response message may comprise second information indicating that the integration of the active, passive, and active server resources associated with WTRU has been completed, and wherein the resource mapping information relates to the integrated resources.Resource mapping information may include URIs of uniform resource identifiers or identifiers corresponding to resources on the active server.

[0207] Method 800 may comprise a step of mapping 860 bindings based on received resource mapping information. Method 800 may comprise a step of replacing bindings to the active server with bindings to the alternate server, wherein replacing bindings may include active server endpoint information with alternate server endpoint information.

[0208] The 800 method may include a step where the consumer node (e.g., WTRU) may transmit 870 communication to the server. Petition 870250091342, dated 07 / 10 / 2025, page 72 / 115 64 / 78 alternative based on the procedural information received.

[0209] Figure 9 is a flowchart illustrating an example of a 900 method performed by an alternate server to reallocate an active server. The alternate server can be an edge enabler server or an edge configuration server that implements functionalities to manage server pool configuration and switch from an active server to an alternate server.

[0210] Referring to Figure 9, method 900 may comprise a step wherein the server (e.g., alternate) may receive 910 a server switching request message from a wireless transmit / receive unit, WTRU, wherein the server switching request message may comprise a WTRU identifier. The server switching message may additionally comprise passive resource information and / or active resource information. Method 900 may comprise a step of determining 920 resource mapping associated with the WTRU based on the WTRU identifier. Method 900 may comprise a step wherein the server (e.g., alternate) may identify passive and active resources associated with the WTRU based on the WTRU identifier.The server (e.g., alternative) can integrate the identified passive and active resources associated with the WTRU, where the integration of the identified passive and active resources can include any of the following: resource storage, resource validation, regeneration of URIs and resource identifiers, initiation of event detection associated with the resources, and request for periodic events associated with the resources (e.g., from a 5G system).

[0211] Method 900 may comprise a step in which the server (e.g., alternate) may transmit 930 to the WTRU a response message. Petition 870250091342, dated 07 / 10 / 2025, pp. 73 / 115 Server switching 65 / 78, where the server switching response message may include procedures for communication with the server and the determined resource mapping. Method 900 may comprise a step where the server (e.g., alternate) may receive 940 communication from the WTRU based on procedure information. More specifically, under the condition that information about server procedures (e.g., alternate) is provided in the server switching response message, the server (e.g., alternate) may wait for messages related to server procedures (e.g., alternate). The WTRU may be a consumer node.

[0212] Figure 10 is a flowchart that illustrates an example of a 1000 method, executed by a consumer node (e.g., WTRU) to relocate a server in a make-before-break manner. The consumer node can be a WTRU, an edge enabler client, an edge application server, or an edge enabler server.

[0213] Referring to Figure 10, method 1000 may comprise a step where the consumer node (e.g., WTRU) may receive 1010 a server pool configuration associated with an active server. Before receiving the server pool configuration, the consumer node may discover the active server, where the active server may comprise SSMF capabilities. More specifically, the SSMF capabilities may comprise functionalities for managing the server pool configuration and switching from the active server to the alternate server.

[0214] Method 1000 may comprise a step in which the consumer node (e.g., WTRU) may receive a server switching notification message from an active server, wherein the notification message Petition 870250091342, dated 07 / 10 / 2025, pp. 74 / 115 Server switching 66 / 78 comprises information indicating an alternate server, procedures for communicating with the alternate server, and timing information indicating when to access the alternate server. The notification message may additionally include an identifier for the alternate server, an endpoint for the alternate server, and active server resource mappings associated with the alternate server. The consumer node (e.g., WTRU) may configure a timer that indicates when to access the alternate server, based on the timing information.

[0215] Method 1000 may comprise a step in which the consumer node (e.g., WTRU) may establish connectivity 1030 with the alternate server (e.g., from an edge data network). Method 1000 may comprise a step in which the consumer node (e.g., WTRU) may communicate 1040 with the alternate server based on the communication procedures.

[0216] Figure 11 is a flowchart that illustrates an example of a 1100 method performed by an active server to relocate the active server in a make-before-break manner. The active server can be an edge enabler server or an edge configuration server that includes functionalities to manage the server pool configuration and switch from the active server to the alternate server.

[0217] Referring to Figure 11, method 1100 may comprise a step in which the active server may select 1110 an alternative server to transfer resources. Method 1100 may comprise a step in which the active server may transmit 1120 a first server switching notification message to a WTRU, where the first switching notification message Petition 870250091342, dated 07 / 10 / 2025, pp. 75 / 115 Server 67 / 78 may include information indicating the alternate server. The WTRU may be a consumer node. The first server switching notification message may additionally contain timing information indicating when to access the alternate server. Method 1100 may include a step where the active server may transmit a server switching request message to the alternate server, wherein the server switching request message includes active and passive resources of the active server associated with the WTRU. The method may include a step where the active server may receive a server switching response message from the alternate server, wherein the server switching response message may include mappings of active server resources associated with the alternate server.The alternate server's server switch response message may additionally include a list of procedures that the WTRU must perform with the alternate server. Method 1100 may comprise a step where the active server may transmit 1150 a second server switch notification to the WTRU associated with the resources transferred to the alternate server.

[0218] Although the attributes and elements are provided above in specific combinations, one with ordinary skill in the art will understand that each attribute or element can be used alone or in any combination with the other attributes and elements. The present disclosure should not be limited in terms of the particular embodiments described in this application, which are intended to be illustrations of various aspects. Many modifications and variations can be made without departing from its spirit and scope, as will become evident to those skilled in the art. No element, act, or instruction used in the description of the present application should be construed as critical or essential to the invention, unless Petition 870250091342, dated 07 / 10 / 2025, pp. 76 / 115 68 / 78 explicitly provided as such. Functionally equivalent methods and apparatus within the scope of the disclosure, in addition to those enumerated herein, will be evident to those skilled in the art from the foregoing descriptions. These modifications and variations are intended to be covered within the scope of the appended claims. The present disclosure shall be limited only by the terms of the appended claims, together with the full scope of equivalents to which such claims are entitled. It is important to understand that this disclosure is not limited to specific methods or systems.

[0219] The aforementioned modalities are discussed, for simplicity, with regard to the terminology and structure of infrared-capable devices, i.e., infrared emitters and receivers. However, the modalities discussed are not limited to these systems, but can be applied to other systems that use other forms of electromagnetic waves or non-electromagnetic waves, such as acoustic waves.

[0220] It should also be understood that terminology used in this document is for the purpose of describing particular embodiments only and is not intended to be limiting. As used in this document, the term “video” or the term “images” may mean any of a snapshot, single image and / or multiple images displayed over time. As another example, when mentioned herein, the terms “user equipment” and its abbreviation “UE”, the term “remote” and / or the terms “head-mounted display” or its abbreviation “HMD” may mean or include (i) a wireless transmitting and / or receiving unit (WTRU); (ii) any of the various embodiments of a WTRU; (iii) a device capable of wireless and / or wired connectivity (e.g., pluggable) configured with, inter alia, some or all of the features and functionalities of a Petition 870250091342, dated 07 / 10 / 2025, p. 77 / 115 69 / 78 WTRU; (iii) a device capable of wireless and / or wired connectivity configured with less than all the structures and functionalities of a WTRU; or (iv) similar. Details of an example of a WTRU, which may be representative of any WTRU cited herein, are provided herein with reference to Figures 1A-1D. As another example, several embodiments disclosed herein above and below are described as utilizing a head-mounted display. Experts in the field will recognize that a device other than the head-mounted display may be used and some or all of the disclosures and several embodiments disclosed may be appropriately modified without undue experimentation. Examples of other devices may include a drone or other device configured to transmit information to provide the adapted reality experience.

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

[0222] Variations of the method, apparatus and system given above are Petition 870250091342, dated 07 / 10 / 2025, pp. 78 / 115 70 / 78 possible embodiments without departing from the scope of the invention. Given the wide variety of embodiments that can be applied, it should be understood that the embodiments illustrated are merely examples and should not be considered as limiting the scope of the following claims. For example, the embodiments provided herein include portable devices, which may include or be used with any appropriate voltage source, such as a battery and the like, providing any appropriate voltage.

[0223] In addition, in the modalities provided above, processing platforms, computing systems, controllers, and other devices that include processors are observed. These devices may include at least one Central Processing Unit (“CPU”) and memory. According to the practices of persons skilled in the art of computer programming, reference to acts and symbolic representations of operations or instructions may be performed by multiple CPUs and memories. Such acts, operations, or instructions may be called “executed,” “computer-executed,” or “CPU-executed.”

[0224] An expert in the field will realize that the acts and operations or instructions symbolically represented include the manipulation of electrical signals by the CPU. An electrical system represents data bits that can cause a resulting transformation or reduction of electrical signals and the maintenance of data bits in memory locations within a memory system to thus reconfigure or alter the operation of the CPU, as well as other signal processing. The memory locations where the data bits are held are physical locations that have specific electrical, magnetic, optical, or organic properties corresponding to or representative of the data bits. It should be understood that the modalities are not limited to the platforms or CPUs mentioned above and that other platforms and Petition 870250091342, dated 07 / 10 / 2025, pp. 79 / 115 71 / 78 CPUs can support the methods provided.

[0225] Data bits can also be held on a computer-readable medium, including magnetic disks, optical disks, and any other volatile (e.g., random access memory (RAM)) or non-volatile (e.g., read-only memory (ROM)) mass storage system readable by the CPU. Computer-readable media may include cooperative or interconnected computer-readable media, which exist exclusively within the processing system or are distributed among multiple interconnected processing systems that may be local to or remote from the processing system. It should be understood that the modalities are not limited to the aforementioned memories and that other platforms and memories may support the methods provided.

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

[0227] There is little distinction between hardware and software implementations of system aspects. The use of hardware or software is generally (but not always, as in certain contexts the choice between hardware and software may become significant) a design choice that represents trade-offs between cost and efficiency. There may be several vehicles by which processes and / or systems and / or other technologies described herein may be affected (e.g., hardware, software, and / or firmware), and the preferred vehicle may vary depending on the context in which the processes and / or systems and / or other technologies are deployed. For example, if an implementer determines that speed and accuracy are paramount, Petition 870250091342, dated 07 / 10 / 2025, pages 80 / 115 72 / 78 The implementer may choose a primarily hardware and / or firmware vehicle. If flexibility is paramount, the implementer may choose a primarily software implementation. Alternatively, the implementer may choose some combination of hardware, software, and / or firmware.

[0228] The preceding detailed description has presented various embodiments of the devices and / or processes through the use of block diagrams, flowcharts, and / or examples. Insofar as such block diagrams, flowcharts, and / or examples include one or more functions and / or operations, it will be understood by those within the art that each function and / or operation within such block diagrams, flowcharts, or examples can be implemented, individually and / or collectively, by a wide range of hardware, software, firmware, or virtually any combination thereof. In one embodiment, various parts of the subject described herein can be implemented by means of Application-Specific Integrated Circuits (ASICs), Field-Programmable Gate Arrays (FPGAs), digital signal processors (DSPs), and / or other integrated formats.However, those skilled in the art will recognize that some aspects of the embodiments disclosed herein, in whole or in part, can be equivalently implemented in integrated circuits, as one or more computer programs running on one or more computers (for example, as one or more computer programs running on one or more computer systems), as one or more programs running on one or more processors (for example, as one or more programs running on one or more microprocessors), as firmware, or as virtually any combination thereof, and that designing the circuit assembly and / or writing the code for the software and / or firmware would be well within the ability of a person skilled in the art. Petition 870250091342, dated 07 / 10 / 2025, pp. 81 / 115 73 / 78 light of this revelation. Furthermore, experts in the field will understand that the mechanisms of the subject described herein can be distributed as a program product in a variety of forms, and that an illustrative embodiment of the subject described herein applies regardless of the specific type of signal carrier medium used to actually accomplish the distribution. Examples of a signal carrier medium include, but are not limited to, the following: a recordable medium, such as a floppy disk, a hard disk drive, a CD, a DVD, a digital tape, a computer memory, etc., and a transmission medium, such as a digital and / or analog communication medium (e.g., a fiber optic cable, a waveguide, a wired communication link, a wireless communication link, etc.).

[0229] Experts in the field will recognize that it is common in the field to describe devices and / or processes in the manner set forth herein and subsequently use engineering practices to integrate such devices and / or processes described into data processing systems. That is, at least some of the devices and / or processes described herein can be integrated into a data processing system through a reasonable amount of experimentation.Those skilled in the art will recognize that a typical data processing system may generally include one or more of a system unit housing, a video display device, memory, such as volatile and non-volatile memory, processors, such as microprocessors and digital signal processors, computational entities, such as operating systems, drivers, graphical user interfaces and application programs, one or more interaction devices, such as a touch keyboard or screen, and / or control systems, including feedback loops and control motors (e.g., feedback). Petition 870250091342, dated 07 / 10 / 2025, page 82 / 115 74 / 78 for position and / or speed detection, control motors to move and / or adjust components and / or quantities). A typical data processing system can be implemented using any suitable commercially available components, such as those normally found in data computing / communication systems and / or network computing / communication systems.

[0230] The subject matter described in this document sometimes illustrates different components included in or connected with other components. It is important to understand that such represented architectures are merely examples and that, in fact, many other architectures can be implemented to achieve the same functionality. In a conceptual sense, any arrangement of components to achieve the same functionality is effectively “associated” so that the desired functionality can be achieved. Therefore, any two components combined here to achieve a specific functionality can be seen as “associated” with each other, so that the desired functionality is achieved, regardless of the architectures or intermediate components.Similarly, any two components thus associated can also be seen as being “operationally connected” or “operationally coupled” to each other to achieve the desired functionality, and any two components capable of being thus associated can also be seen as being “operationally coupleable” to each other to achieve the desired functionality. Specific examples of operationally coupleable components include, but are not limited to, physically coupleable and / or physically interactive components and / or wireless interactive components and / or logically interactive components.

[0231] With regard to the use of substantially any plural terms Petition 870250091342, dated 07 / 10 / 2025, page 83 / 115 75 / 78 and / or singular in this document, those skilled in the art may translate from plural to singular and / or from singular to plural, as appropriate to the context and / or application. The various singular / plural permutations may be expressly set forth in this document for the sake of clarity.

[0232] It will be understood by those skilled in the art that, in general, the terms used in the present document, and especially in the appended claims (e.g., bodies of the appended claims), are generally understood as “unrestricted” terms (e.g., the term “including” should be interpreted as “including, without limitation”, the term “having” should be interpreted as “having at least”, the term “includes” should be interpreted as “includes, without limitation, etc.). It will further be understood by those within the art that if a specific number of an introduced claim recitation is intended, such intention will be explicitly stated in the claim, and in the absence of such recitation, such intention is not present. For example, when only one item is intended, the term “single” or similar language may be used.For the sake of clarity, the following appended claims and / or descriptions contained herein may include the use of the introductory phrases “at least one” and “one or more” to introduce recitations of claims. However, the use of such phrases should not be interpreted as implying that the introduction of a claim recitation by the indefinite articles “a” or “an” limits any particular claim including such introduced claim recitation to modalities that include only one recitation, even when the same claim includes the introductory phrases “one or more” or “at least one” and indefinite articles such as “a” or “an” (e.g., “a” and / or “an” should be interpreted as meaning “in at least one” or “one or more”). The same applies to the use of definite articles used to introduce recitations of. Petition 870250091342, dated 07 / 10 / 2025, pp. 84 / 115 76 / 78 claims. Furthermore, even if a specific number of an introduced claim recitation is explicitly recited, those skilled in the art will recognize that such recitation should be interpreted as meaning at least the number recited (e.g., the simple recitation of “two recitations,” without other modifiers, means at least two recitations, or two or more recitations). Additionally, in cases where a convention analogous to “at least one of A, B, and C, etc.” is used, this construction is generally intended in the sense that someone skilled in the art would understand the convention (e.g., “a system that has at least one of A, B, and C” would include, but not be limited to, systems that have A alone, B alone, C alone, A and B together, A and C together, B and C together, and / or A, B, and C together, etc.). In cases where a convention analogous to “at least one of A, B, or C, etc.”The phrase "is used" is generally intended to ensure that someone skilled in the art would understand the convention (e.g., "a system having at least one of A, B, or C" would include, but not be limited to, systems having A alone, B alone, C alone, A and B together, A and C together, B and C together, and / or A, B, and C together, etc.). It will also be understood by those within the art that virtually any disjunctive word and / or phrase presenting two or more alternative terms, whether in the description, claims, or drawings, should be understood as contemplating the possibilities of including one of the terms, any of the terms, or both terms.Furthermore, the terms “any of” followed by a listing of a plurality of items and / or a plurality of item categories, as used in this document, are intended to include “any of”, “any combination of”, “any multiple of”, and / or “any combination of multiples of” the items and / or item categories, individually or in combination with other items and / or others. Petition 870250091342, dated 07 / 10 / 2025, pages 85 / 115 77 / 78 item categories. Furthermore, as used in this document, the term “set” is intended to include any number of items, including zero. Additionally, as used in this document, the term “number” is intended to include any number, including zero. And the term “multiple,” as used in this document, is intended to be synonymous with “a plurality.”

[0233] Furthermore, when attributes or aspects of the revelation are described in terms of Markush groups, those versed in the technique will recognize that the revelation is also described in terms of any individual member or subgroup of members of the Markush group.

[0234] As will be understood by a person skilled in the art, for all and any purposes, such as in terms of providing a written description, all ranges disclosed in the present document also encompass all and any possible subranges and combinations of subranges thereof. Any listed range may be readily recognized as describing and sufficiently permitting the same range to be divided into at least equal halves, thirds, quarters, fifths, tenths, etc. As a non-limiting example, each range discussed in the present document may be readily divided into a lower third, middle third, and upper third, etc. As will also be understood by one skilled in the art, all language such as “up to,” “at least,” “greater than,” “less than,” and the like, includes the recited number and refers to ranges that may be subsequently divided into subranges, as discussed above.Finally, as will be understood by one skilled in the art, a range includes each individual member. Thus, for example, a group with 1 to 3 cells refers to groups with 1, 2, or 3 cells. Similarly, a group with 1 to 5 cells refers to groups with 1, 2, 3, 4, or 5 cells, and so on. Petition 870250091342, dated 07 / 10 / 2025, pp. 86 / 115 78 / 78

[0235] Furthermore, claims should not be construed as limited to the order or elements provided, unless stated otherwise. Additionally, the use of the terms “means to” in any claim is intended to invoke 35 USC §112, paragraph 6, or the means-plus-function claim format, and any claim without the terms “means to” is not intended to do so. Petition 870250091342, dated 07 / 10 / 2025, page 87 / 115

Claims

1 / 5 CLAIMS 1. A method implemented in a wireless transmit / receive unit, WTRU, wherein the method is CHARACTERIZED in that it comprises: receiving a server set configuration associated with an active server; determining the unavailability of the active server; selecting an alternate server based on the received server set configuration; transmitting to the alternate server a server switching request message, wherein the server switching request message comprises initial information indicating a WTRU identifier; receiving from the alternate server a server switching reply message, wherein the server switching reply message comprises procedural information for communication with the alternate server and resource mapping information related to the alternate server; mapping bindings based on the received resource mapping information;and transmit communication to the alternate server using the received procedural information.

2. Method, according to claim 1, CHARACTERIZED in that the procedural information comprises procedures for confirming the success of server switching.

3. Method, according to claim 2, CHARACTERIZED in that the procedures for confirming the success of the server switching Petition 870250091342, dated 07 / 10 / 2025, page 111 / 115 2 / 5 comprise a registration update procedure with the alternate server.

4. Method according to claim 1, CHARACTERIZED in that the server switching response message comprises secondary information indicating that the integration of the server's active, passive, and active resources associated with the WTRU has been completed, and in that the resource mapping information is related to the integrated resources.

5. Method, according to claim 1, CHARACTERIZED in that the resource mapping information comprises uniform resource identifiers, URIs, or identifiers corresponding to resources on the active server.

6. Method according to claim 1, characterized in that it comprises, before receiving the server set configuration: discovering the active server, wherein the active server comprises functionalities for managing the server set configuration and switching from the active server to the alternate server.

7. Method, according to claim 1, CHARACTERIZED in that it comprises replacing links to the active server with links to an alternative server.

8. Method according to claim 7, CHARACTERIZED in that replacing bindings comprises replacing active server endpoint information with alternate server endpoint information.

9. Method according to claim 1, CHARACTERIZED in that the WTRU is a consumer node.

10. Method, according to claim 1, CHARACTERIZED by the fact that Petition 870250091342, dated 07 / 10 / 2025, pp. 112 / 115 3 / 5 determines the unavailability of the active server based on a communication timeout failure with the active server.

11. Wireless Transmit / Receive Unit, WTRU, CHARACTERIZED in that it comprises any of the following options: a memory and a processor, configured to: receive a server set configuration associated with an active server; determine the unavailability of the active server; select an alternate server based on the received server set configuration; transmit, to the alternate server, a server switching request message, wherein the server switching request message comprises initial information indicating a WTRU identifier; receive, from the alternate server, a server switching response message, wherein the server switching response message comprises procedural information for communication with the alternate server and resource mapping information related to the alternate server;Map linkages based on received resource mapping information; and transmit communication to the alternate server based on received procedure information.

12. WTRU, according to claim 11, CHARACTERIZED in that the procedural information comprises procedures for confirming the success of server switching. Petition 870250091342, dated 10 / 07 / 2025, pp. 113 / 115 4 / 5 13. WTRU, according to claim 12, CHARACTERIZED in that the procedures for confirming the success of the server switching comprise a log update procedure with the alternate server.

14. WTRU, according to claim 11, CHARACTERIZED in that the server switching response message comprises second information indicating that the integration of the server's active, passive, and active resources associated with the WTRU has been completed, and in that the resource mapping information is related to the integrated resources.

15. WTRU, according to claim 11, CHARACTERIZED in that the resource mapping information comprises uniform resource identifiers, URIs, or identifiers corresponding to resources on the active server.

16. WTRU, according to claim 11, CHARACTERIZED in that it is configured to, before receiving the server set configuration: discover the active server, wherein the active server comprises functionalities to manage the server set configuration and switch from the active server to the alternate server.

17. WTRU, according to claim 11, CHARACTERIZED in that it is configured to replace bindings to the active server with bindings to the alternate server.

18. WTRU, according to claim 17, CHARACTERIZED in that being configured to replace bindings comprises being configured to replace active server endpoint information with alternate server endpoint information.

19. WTRU, according to claim 11, wherein WTRU is Petition 870250091342, dated 10 / 07 / 2025, page 114 / 115 5 / 5 CHARACTERIZED by the fact that it is a consumer node.

20. WTRU, according to claim 11, CHARACTERIZED by the fact that being configured to determine the unavailability of the active server comprises being configured to determine the unavailability of the active server based on a communication timeout failure with the active server. Petition 870250091342, dated 10 / 07 / 2025, p. 115 / 115