Methods, architectures, apparatuses, and systems for implementing wireless reliability and availability in multi-domain deployments

By coupling the processor and the transmitter receiver in the network element, sending request messages to the multi-domain network to establish a communication channel and monitor QoS, the problem of uncertainty in wireless communication signal transmission in multi-domain deployment is solved, and reliability and Availability communication.

CN118975209APending Publication Date: 2024-11-15INTERDIGITAL PATENT HOLDINGS INC
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
CN202380028255.6
Authority / Receiving Office
CN · China
Patent Type
Applications(China)
Current Assignee / Owner
Priority Date
2022-03-04
Filing Date
2023-03-03
Publication Date
2024-11-15

AI Technical Summary

Technical Problem

In multi-domain deployment, wireless communications are difficult to achieve reliability and availability due to factors such as uncontrolled interference and self-induced multipath fading.

Method used

By introducing processor-coupled transmitters and receivers in network elements, request messages are sent to another domain network to establish communication channels and to monitor the partitioning of quality of service (QoS) to ensure reliability and availability across multiple domains communication.

Benefits of technology

The reliability and availability of wireless communication in multi-domain deployment are realized. By dynamically adjusting channels and service quality, the use of resources is reduced and the certainty and reliability of communication is improved.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN118975209A_ABST
    Figure CN118975209A_ABST
Patent Text Reader

Abstract

Described herein are procedures, methods, architectures, apparatuses, systems, devices, and computer program products relating to implementing wireless reliability and availability in multi-domain deployments. In one embodiment, a network element may be configured to transmit, to a first network element of a first domain network, a first request message requesting towards one or more tracks of a second domain network, the first request message indicating a requested quality of service (QoS). The network element may be configured to receive a response message from the first network element, the response message indicating: (i) one or more second network elements of the second domain network, the one or more second network elements interconnecting the first domain network with the second domain network; and (ii) a QoS partition of the requested QoS to be applied to the first domain network and the second domain network.
Need to check novelty before this filing date? Find Prior Art

Description

[0001] CROSS-REFERENCE TO RELATED APPLICATIONS

[0002] This application claims priority to European patent application No. 22160335.0 filed on March 4, 2022, which is incorporated herein by reference in its entirety. Technical Field

[0003] The present disclosure relates generally to the fields of communications, software, and coding, including, for example, methods, architectures, apparatus, and systems related to achieving wireless reliability and availability in multi-domain deployments. Background Art

[0004] Wireless can work on a shared medium. Wireless transmissions may have uncertainty due to uncontrolled interference, including, for example, self-induced multipath fading. The embodiments described herein are designed in view of the above. Summary of the invention

[0005] Methods, architectures, devices, and systems related to achieving wireless reliability and availability in a multi-domain deployment are described herein. In one embodiment, a network element is described herein, the network element comprising a processor and a transmitter and a receiver (e.g., a transceiver), the transmitter and the receiver being operatively coupled to the processor. For example, the processor may be configured to transmit a first request message requesting one or more tracks toward a second domain network to a first network element of a first domain network, the first request message indicating the requested quality of service (QoS). For example, the processor may be configured to receive a response message from the first network element, the response message indicating: (i) one or more second network elements of the second domain network, the one or more second network elements interconnecting the first domain network with the second domain network; and (ii) QoS partitioning of the QoS of the request to be applied to the first domain network and the second domain network. For example, the processor may be configured to transmit one or more second request messages requesting to establish a communication channel across the first domain network and the second domain network to the one or more second network elements of the second domain network, the one or more second request messages indicating the QoS partitioning to be monitored on the first domain network and the second domain network via the communication channel. For example, the processor may be configured to receive a confirmation from the one or more second network elements of the second domain network indicating that the communication channel has been established.

[0006] In one embodiment, a method may be implemented in a network element. For example, the method may include transmitting a first request message to a first network element of a first domain network requesting one or more tracks toward a second domain network, the first request message indicating the requested QoS. For example, the method may also include receiving a response message from the first network element, the response message indicating: (i) one or more second network elements of the second domain network, the one or more second network elements interconnecting the first domain network with the second domain network; and (ii) a QoS partitioning of the requested QoS to be applied to the first domain network and the second domain network. For example, the method may also include transmitting one or more second request messages to the one or more second network elements of the second domain network requesting to establish a communication channel across the first domain network and the second domain network, the one or more second request messages indicating the QoS partitioning to be monitored on the first domain network and the second domain network via the communication channel. For example, the method may also include receiving a confirmation from the one or more second network elements of the second domain network indicating that the communication channel has been established. BRIEF DESCRIPTION OF THE DRAWINGS

[0007] A more detailed understanding can be obtained from the following detailed description, which is given by way of example in conjunction with its accompanying drawings. As with the detailed description, the figures in such drawings are examples. Therefore, the drawings (figures) and specific embodiments should not be considered limiting, and other equally effective examples are possible and contemplated. In addition, like reference numerals ("ref.") in the figures indicate similar elements, and wherein:

[0008] Figure 1A is a system diagram illustrating an example communication system;

[0009] Figure 1B is an example that can be Figure 1A A system diagram of an example wireless transmit / receive unit (WTRU) for use within the illustrated communication system;

[0010] Figure 1C is an example that can be Figure 1A a system diagram of an example radio access network (RAN) and an example core network (CN) used within the illustrated communication system;

[0011] Figure 1D is an example that can be Figure 1A A system diagram of another example RAN and another example CN used within the illustrated communication system;

[0012] Figure 2 is a diagram illustrating an example of communications involving two Reliable and Available Wireless (RAW) domains interconnected by a core network;

[0013] Figure 3is a diagram illustrating an example of multi-domain awareness and connectivity establishment;

[0014] Figure 4 is a diagram illustrating an example of RAW domain-aware link establishment;

[0015] Figure 5 is a diagram illustrating an example of a multi-domain RAW signaling flow;

[0016] Figure 6 is a diagram illustrating an example of communications involving two RAW domains interconnected by a wireless network; and

[0017] Figure 7 is a diagram illustrating an example of a multi-domain RAW communication method. DETAILED DESCRIPTION

[0018] In the following detailed description, many specific details are set forth to provide a thorough understanding of the embodiments and / or examples disclosed herein. However, it should be understood that such embodiments and examples can be practiced without some or all of the specific details set forth herein. In other cases, well-known methods, procedures, components and circuits are not described in detail to avoid blurring the following description. In addition, the embodiments and examples not specifically described herein can be practiced in place of the embodiments and other examples explicitly, implicitly and / or inherently described, disclosed or otherwise provided (collectively referred to as "provided") herein, or practiced in combination with these embodiments and examples. Although various embodiments are described and / or claimed herein, wherein devices, systems, equipment, etc. and / or any of their elements implement operations, processes, algorithms, functions, etc. and / or any part thereof, it should be understood that any embodiments described herein and / or protected by the claims assume that any device, system, equipment, etc. and / or any of its elements are configured to implement any operations, processes, algorithms, functions, etc. and / or any part thereof.

[0019] Example Communication System

[0020] The methods, devices, and systems provided herein are well suited for communications involving both wired and wireless networks. Figures 1A to 1D An overview of various types of wireless devices and infrastructure is provided, wherein various elements of the network can utilize the methods, apparatuses, and systems provided herein, perform the methods, apparatuses, and systems provided herein, be arranged according to the methods, apparatuses, and systems provided herein, and / or be adapted and / or configured for the methods, apparatuses, and systems provided herein.

[0021] Figure 1Ais a system diagram illustrating an example communication system 100 in which one or more disclosed embodiments may be implemented. The communication system 100 may be a multiple access system that provides content such as voice, data, video, messaging, broadcast, etc. to multiple wireless users. The communication system 100 may enable multiple wireless users to access such content through sharing of system resources (including wireless bandwidth). For example, the communication system 100 may employ one or more channel access methods such as code division multiple access (CDMA), time division multiple access (TDMA), frequency division multiple access (FDMA), orthogonal FDMA (OFDMA), single carrier FDMA (SC-FDMA), zero tail (ZT) unique word (UW) discrete Fourier transform (DFT) spread OFDM (ZT UW DTS-sOFDM), unique word OFDM (UW-OFDM), resource block filtered OFDM, filter bank multi-carrier (FBMC), etc.

[0022] like Figure 1A As shown, the communication system 100 may include wireless transmit / receive units (WTRUs) 102a, 102b, 102c, 102d, a radio access network (RAN) 104 / 113, a core network (CN) 106 / 115, a public switched telephone network (PSTN) 108, the Internet 110 and other networks 112, but it should be understood that the disclosed embodiments contemplate any number of WTRUs, base stations, networks, and / or network elements. Each of the WTRUs 102a, 102b, 102c, 102d may be any type of device configured to operate and / or communicate in a wireless environment. By way of example, the WTRUs 102a, 102b, 102c, 102d (any of which may be referred to as a “station” and / or “STA”) may be configured to send and / or receive wireless signals and may include (or may be) a user equipment (UE), a mobile station, a fixed or mobile subscriber unit, a subscription-based unit, a pager, a cellular phone, a personal digital assistant (PDA), a smart phone, a laptop, a netbook, a personal computer, a wireless sensor, a hotspot or Mi-Fi device, an Internet of Things (IoT) device, a watch or other wearable device, a head-mounted display (HMD), a vehicle, a drone, medical devices and applications (e.g., remote surgery), industrial devices and applications (e.g., robots and / or other wireless devices operating in an industrial and / or automated process chain environment), a consumer electronic device, a device operating on a commercial and / or industrial wireless network, etc. Any of the WTRUs 102a, 102b, 102c, and 102d may be interchangeably referred to as a UE.

[0023] The communication system 100 may also include a base station 114a and / or a base station 114b. Each of the base stations 114a, 114b may be any type of device configured to wirelessly interface with at least one of the WTRUs 102a, 102b, 102c, 102d to, for example, facilitate access to one or more communication networks (such as the CN 106 / 115, the Internet 110, and / or the network 112). By way of example, the base stations 114a, 114b may be any of a base transceiver station (BTS), a Node B (NB), an evolved Node B (eNB), a Home Node B (HNB), a Home evolved Node B (HeNB), a gNode B (gNB), a NR Node B (NR NB), a site controller, an access point (AP), a wireless router, and the like. Although the base stations 114a, 114b are each depicted as a single element, it should be appreciated that the base stations 114a, 114b may include any number of interconnected base stations and / or network elements.

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

[0025] The base stations 114a, 114b may communicate with one or more of the WTRUs 102a, 102b, 102c, 102d over an air interface 116, which may be any suitable wireless communication link (e.g., radio frequency (RF), microwave, centimeter wave, micrometer wave, infrared (IR), ultraviolet (UV), visible light, etc.). The air interface 116 may be established using any suitable radio access technology (RAT).

[0026] More specifically, as noted above, the communication system 100 may be a multiple access system and may employ one or more channel access schemes such as CDMA, TDMA, FDMA, OFDMA, SC-FDMA, etc. For example, the base station 114a in the RAN 104 / 113 and the WTRUs 102a, 102b, 102c may implement a radio technology such as Universal Mobile Telecommunications System (UMTS) Terrestrial Radio Access (UTRA), which may use Wideband CDMA (WCDMA) to establish the air interface 116. 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).

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

[0028] In one embodiment, the base station 114a and the WTRUs 102a, 102b, 102c may implement a radio technology such as NR radio access, which may establish the air interface 116 using New Radio (NR).

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

[0030] In one embodiment, the base station 114a and the WTRUs 102a, 102b, 102c may implement a radio technology such as IEEE 802.11 (i.e., Wireless Fidelity (Wi-Fi)), IEEE 802.16 (i.e., Worldwide Interoperability for Microwave Access (WiMAX)), CDMA2000, CDMA2000 1X, CDMA2000 EV-DO, Interim Standard 2000 (IS-2000), Interim Standard 95 (IS-95), Interim Standard 856 (IS-856), Global System for Mobile Communications (GSM), Enhanced Data rates for GSM Evolution (EDGE), GSM EDGE (GERAN), etc.

[0031] Figure 1A The base station 114b in may be, for example, a wireless router, a Home NodeB, a Home eNodeB, or an access point, and may utilize any suitable RAT to facilitate wireless connectivity in a local area, such as a business location, a home, a vehicle, a campus, an industrial facility, an air corridor (e.g., for use by drones), a road, and the like. In one embodiment, the base station 114b and the WTRUs 102c, 102d may implement a radio technology such as IEEE 802.11 to establish a wireless local area network (WLAN). In one embodiment, the base station 114b and the WTRUs 102c, 102d may implement a radio technology such as IEEE 802.15 to establish a wireless personal area network (WPAN). In one embodiment, the base station 114b and the WTRUs 102c, 102d may utilize a cellular-based RAT (e.g., WCDMA, CDMA2000, GSM, LTE, LTE-A, LTE-A Pro, NR, etc.) to establish any of a microcell, a picocell, or a femtocell. As Figure 1A As shown, base station 114b may have a direct connection to Internet 110. Thus, base station 114b may not need to access Internet 110 via CN 106 / 115.

[0032] The RAN 104 / 113 may be in communication with the CN 106 / 115, which may be any type of network configured to provide voice, data, applications, and / or Voice over Internet Protocol (VoIP) services to one or more of the WTRUs 102a, 102b, 102c, 102d. The data may have different quality of service (QoS) requirements, such as different throughput requirements, latency requirements, error tolerance requirements, reliability requirements, data throughput requirements, mobility requirements, etc. The CN 106 / 115 may provide call control, billing services, mobile location-based services, prepaid calls, Internet connectivity, video distribution, etc., and / or perform high-level security functions, such as user authentication. Although not described in detail in the specification, the CN 106 / 115 may be configured to provide voice, data, applications, and / or Voice over Internet Protocol (VoIP) services to one or more of the WTRUs 102a, 102b, 102c, 102d. Figure 1AAlthough not shown in the figure, it will be appreciated that the RAN 104 / 113 and / or the CN 106 / 115 may be in direct or indirect communication with other RANs that employ the same RAT as the RAN 104 / 113 or a different RAT. For example, in addition to being connected to the RAN 104 / 113, which may utilize NR radio technology, the CN 106 / 115 may also be in communication with another RAN (not shown) that employs any of GSM, UMTS, CDMA2000, WiMAX, E-UTRA, or Wi-Fi radio technologies.

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

[0034] Some or all of the WTRUs 102a, 102b, 102c, 102d in the communication system 100 may include multi-mode capabilities (e.g., the WTRUs 102a, 102b, 102c, 102d may include multiple transceivers for communicating with different wireless networks via different wireless links). Figure 1A The illustrated WTRU 102c may be configured to communicate with the base station 114a, which may employ a cellular-based radio technology, and with the base station 114b, which may employ an IEEE 802 radio technology.

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

[0036] The processor 118 may be a general purpose processor, a special purpose processor, a conventional processor, a digital signal processor (DSP), a plurality of microprocessors, one or more microprocessors associated with a DSP core, a controller, a microcontroller, an application specific integrated circuit (ASIC), a field programmable gate array (FPGA) circuit, any other type of integrated circuit (IC), a state machine, etc. The processor 118 may perform signal decoding, data processing, power control, input / output processing, and / or any other functionality that enables the WTRU 102 to operate in a wireless environment. The processor 118 may be coupled to the transceiver 120, which may be coupled to the transmit / receive element 122. Although Figure 1B The processor 118 and the transceiver 120 are depicted as separate components, but it is understood that the processor 118 and the transceiver 120 may be integrated together, such as in an electronic package or chip.

[0037] The send / receive element 122 may be configured to send a signal to a base station (e.g., base station 114a) or receive a signal from the base station via an air interface 116. For example, in one embodiment, the send / receive element 122 may be an antenna configured to send and / or receive an RF signal. In one embodiment, the send / receive element 122 may be a transmitter / detector configured to send and / or receive, for example, an IR, UV or visible light signal. In one embodiment, the send / receive element 122 may be configured to send and / or receive both an RF signal and an optical signal. It should be understood that the send / receive element 122 may be configured to send and / or receive any combination of wireless signals.

[0038] Although the transmit / receive element 122 Figure 1B Although depicted as a single element in the figure, 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) for transmitting and receiving wireless signals over the air interface 116.

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

[0040] The processor 118 of the WTRU 102 may be coupled to and may receive user input data from a speaker / microphone 124, a keypad 126, and / or a display / touchpad 128 (e.g., a liquid crystal display (LCD) display unit or an organic light emitting diode (OLED) display unit). The processor 118 may also output user data to the speaker / microphone 124, the keypad 126, and / or the display / touchpad 128. In addition, the processor 118 may access information from and store data in any type of suitable memory, such as a non-removable memory 130 and / or a removable memory 132. The non-removable memory 130 may include a random access memory (RAM), a read-only memory (ROM), a hard disk, or any other type of memory storage device. The removable memory 132 may include a subscriber identity module (SIM) card, a memory stick, a secure digital (SD) memory card, and the like. In other embodiments, the processor 118 may access information from and store data in a memory that is not physically located on the WTRU 102, such as on a server or a home computer (not shown).

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

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

[0043] The processor 118 may also be coupled to other components / peripherals 138, which may include one or more software modules / units and / or hardware modules / units that provide additional features, functionality, and / or wired or wireless connectivity. For example, the components / peripherals 138 may include an accelerometer, an electronic compass, a satellite transceiver, a digital camera (e.g., for photos and / or videos), a universal serial bus (USB) port, a vibration device, a television transceiver, a hands-free headset, module, a frequency modulation (FM) radio unit, a digital music player, a media player, a video game player module, an Internet browser, a virtual reality and / or augmented reality (VR / AR) device, an activity tracker, etc. Components / peripherals 138 may include one or more sensors, which may be one or more of the following: a gyroscope, an accelerometer, a Hall effect sensor, a magnetometer, an orientation sensor, a proximity sensor, a temperature sensor, a time sensor; a geolocation sensor; an altimeter, a light sensor, a touch sensor, a magnetometer, a barometer, a gesture sensor, a biometric sensor, and / or a humidity sensor.

[0044] The WTRU 102 may include a full-duplex radio for which transmission and reception of some or all signals (e.g., associated with specific subframes for both uplink (e.g., for transmission) and downlink (e.g., for reception)) may be concurrent and / or simultaneous. The full-duplex radio may include an interference management unit for reducing and / or substantially eliminating self-interference via hardware (e.g., a choke) or via signal processing performed by a processor (e.g., a separate processor (not shown) or via the processor 118). In one embodiment, the WTRU 102 may include a half-duplex radio for which transmission and reception of some or all signals (e.g., associated with specific subframes for both uplink (e.g., for transmission) or downlink (e.g., for reception)) may be concurrent and / or simultaneous.

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

[0046] The RAN 104 may include evolved Node-Bs 160a, 160b, 160c, though it will be appreciated that the RAN 104 may include any number of evolved Node-Bs while remaining consistent with an embodiment. The evolved Node-Bs 160a, 160b, 160c may each include one or more transceivers for communicating with the WTRUs 102a, 102b, 102c over the air interface 116. In one embodiment, the evolved Node-Bs 160a, 160b, 160c may implement MIMO technology. Thus, the evolved Node-B 160a, for example, may use multiple antennas to transmit wireless signals to, and receive wireless signals from, the WTRU 102a.

[0047] Each of the eNodeBs 160a, 160b, and 160c may be associated with a particular cell (not shown) and may be configured to manage radio resource management decisions, handover decisions, user scheduling in uplink (UL) and / or downlink (DL), etc. Figure 1C As shown, the eNode-Bs 160a, 160b, 160c may communicate with each other via an X2 interface.

[0048] Figure 1C The illustrated CN 106 may include a mobility management entity (MME) 162, a serving gateway (SGW) 164, and a packet data network (PDN) gateway (PGW) 166. While each of the foregoing elements is depicted as being part of the CN 106, it should be understood that any of these elements may be owned and / or operated by an entity other than the CN operator.

[0049] The MME 162 may be connected to each of the evolved Node-Bs 160a, 160b, and 160c in the RAN 104 via an S1 interface and may serve as a control node. For example, the MME 162 may be responsible for authenticating users of the WTRUs 102a, 102b, 102c, bearer activation / deactivation, selecting a particular serving gateway during an initial attach of the WTRUs 102a, 102b, 102c, etc. The MME 162 may provide a control plane function for switching between the RAN 104 and other RANs (not shown) that employ other radio technologies, such as GSM and / or WCDMA.

[0050] The SGW 164 may be connected to each of the evolved Node-Bs 160a, 160b, 160c in the RAN 104 via an S1 interface. The SGW 164 may generally route and forward user data packets to / from the WTRUs 102a, 102b, 102c. The SGW 164 may perform other functions, such as anchoring the user plane during inter-evolved Node-B handovers, triggering paging when DL data is available for the WTRUs 102a, 102b, 102c, managing and storing the context of the WTRUs 102a, 102b, 102c, and the like.

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

[0052] The CN 106 may facilitate communications with other networks. For example, the CN 106 may provide the WTRUs 102a, 102b, 102c with access to circuit-switched networks, such as the PSTN 108, to facilitate communications between the WTRUs 102a, 102b, 102c and traditional land-line communications devices. For example, the CN 106 may include, or may be in communication with, an IP gateway (e.g., an IP Multimedia Subsystem (IMS) server) that acts as an interface between the CN 106 and the PSTN 108. In addition, the CN 106 may provide the WTRUs 102a, 102b, 102c with access to other networks 112, which may include other wired networks and / or wireless networks owned and / or operated by other service providers.

[0053] Although the WTRU Figures 1A to 1D Although described as wireless terminals, it is contemplated that in certain representative embodiments, such terminals may (eg, temporarily or permanently) use a wired communications interface with a communications network.

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

[0055] A WLAN in infrastructure basic service set (BSS) mode may have an access point (AP) for the BSS and one or more stations (STA) associated with the AP. The AP may have access or an interface to a distribution system (DS) or another type of wired / wireless network that carries traffic to and / or carries traffic away from the BSS. Traffic originating from outside the BSS and going to the STA may arrive through the AP and may be delivered to the STA. Traffic originating from the STA and going to a target outside the BSS may be transmitted to the AP to be delivered to the corresponding target. Traffic between STAs within the BSS may be transmitted through the AP, for example, where the source STA may transmit traffic to the AP, and the AP may deliver traffic to the target STA. Traffic between STAs within the BSS may be considered and / or referred to as point-to-point traffic. Point-to-point traffic may be transmitted between the source STA and the target STA (e.g., directly between them) using a direct link setup (DLS). In certain representative embodiments, the DLS may use 802.11e DLS or 802.11z tunnel DLS (TDLS). A WLAN using an independent BSS (IBSS) mode may not have an AP, and STAs within or using the IBSS (eg, all STAs in the STA) may communicate directly with each other. This IBSS communication mode may sometimes be referred to herein as an "ad hoc" communication mode.

[0056] When using the 802.11ac infrastructure operation mode or a similar operation mode, the AP may send a beacon on a fixed channel (such as a primary channel). The primary channel may be a fixed width (e.g., a 20 MHz wide bandwidth) or a width dynamically set via signaling. The primary channel may be a working channel of the BSS and may be used by the STA to establish a connection with the AP. In certain representative embodiments, carrier sense multiple access / collision avoidance (CSMA / CA) may be implemented, for example, in an 802.11 system. For CSMA / CA, a STA (e.g., each STA) (including the AP) may listen to the primary channel. If the primary channel is listened / detected and / or determined to be busy by a particular STA, the particular STA may back off. One STA (e.g., only one station) may transmit at any given time in a given BSS.

[0057] High throughput (HT) STAs may communicate using a 40 MHz wide channel, for example, via a combination of a primary 20 MHz channel and adjacent or non-adjacent 20 MHz channels to form a 40 MHz wide channel.

[0058] Very high throughput (VHT) STA can support 20MHz, 40MHz, 80MHz and / or 160MHz wide channels. 40MHz channels and / or 80MHz channels can be formed by combining continuous 20MHz channels. 160MHz channels can be formed by combining 8 continuous 20MHz channels, or by combining two non-continuous 80MHz channels (this can be called 80+80 configuration). For the 80+80 configuration, after channel coding, the data can pass through a segment parser that can divide the data into two streams. Each stream can be processed by inverse fast Fourier transform (IFFT) and time domain processing separately. These streams can be mapped to two 80MHz channels, and data can be sent by sending STA. At the receiver of the receiving STA, the above-mentioned operations for the 80+80 configuration can be reversed, and the combined data can be transmitted to the medium access control (MAC) layer, entity, etc.

[0059] 802.11af and 802.11ah support operating modes below 1 GHz. Channel operating bandwidths and carriers are reduced in 802.11af and 802.11ah relative to those used in 802.11n and 802.11ac. 802.11af supports 5MHz, 10MHz, and 20MHz bandwidths in the TV White Space (TVWS) spectrum, and 802.11ah supports 1MHz, 2MHz, 4MHz, 8MHz, and 16MHz bandwidths using non-TVWS spectrum. According to a representative embodiment, 802.11ah may support meter type control / machine type communication (MTC), such as MTC devices in macro coverage areas. MTC devices may have certain capabilities, such as limited capabilities, including support for (e.g., only support for) certain bandwidths and / or limited bandwidths. MTC devices may include batteries with battery life above a threshold (e.g., to maintain very long battery life).

[0060] WLAN systems that can support multiple channels and channel bandwidths (such as 802.11n, 802.11ac, 802.11af, and 802.11ah) include channels that can be designated as primary channels. The primary channel may have a bandwidth equal to the maximum common operating bandwidth supported by all STAs in the BSS. The bandwidth of the primary channel may be set and / or limited by a STA (which supports the minimum bandwidth operation mode) from all STAs operating in the BSS. In the example of 802.11ah, for STAs (e.g., MTC-type devices) that support (e.g., only support) a 1MHz mode, the primary channel may be 1MHz wide, even if the AP and other STAs in the BSS support 2MHz, 4MHz, 8MHz, 16MHz, and / or other channel bandwidth operation modes. Carrier sensing and / or network allocation vector (NAV) settings may depend on the state of the primary channel. If the primary channel is busy, for example, because a STA (which only supports a 1MHz operation mode) is sending to the AP, the entire available band may be considered busy even if most of the band remains idle and may be available.

[0061] In the United States, the available frequency band for 802.11ah is 902MHz to 928MHz. In South Korea, the available frequency band is 917.5MHz to 923.5MHz. In Japan, the available frequency band is 916.5MHz to 927.5MHz. The total bandwidth available for 802.11ah is 6MHz to 26MHz, depending on the country code.

[0062] Figure 1D 1 is a system diagram illustrating the RAN 113 and the CN 115 according to one embodiment. As noted above, the RAN 113 may employ NR radio technology to communicate with the WTRUs 102a, 102b, 102c over the air interface 116. The RAN 113 may also be in communication with the CN 115.

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

[0064] The WTRUs 102a, 102b, 102c may communicate with the gNBs 180a, 180b, 180c using transmissions associated with a parameter set that may be scalable. For example, OFDM symbol spacing and / or OFDM subcarrier spacing may vary for different transmissions, different cells, and / or different portions of the wireless transmission spectrum. The WTRUs 102a, 102b, 102c may communicate with the gNBs 180a, 180b, 180c using subframes or Transmission Time Intervals (TTIs) of varying or scalable lengths (e.g., including varying numbers of OFDM symbols and / or varying absolute time lengths).

[0065] The gNBs 180a, 180b, 180c may be configured to communicate with the WTRUs 102a, 102b, 102c in a standalone configuration and / or a non-standalone configuration. In a standalone configuration, the WTRUs 102a, 102b, 102c may communicate with the gNBs 180a, 180b, 180c while not accessing other RANs (e.g., such as the eNodeBs 160a, 160b, 160c). In a standalone configuration, the WTRUs 102a, 102b, 102c may use one or more of the gNBs 180a, 180b, 180c as mobility anchor points. In a standalone configuration, the WTRUs 102a, 102b, 102c may communicate with the gNBs 180a, 180b, 180c using signals in an unlicensed band. In a non-standalone configuration, the WTRUs 102a, 102b, 102c may communicate / connect with the gNB 180a, 180b, 180c while also communicating / connecting with another RAN, such as the evolved Node-B 160a, 160b, 160c. For example, the WTRUs 102a, 102b, 102c may implement the DC principle to communicate with one or more gNBs 180a, 180b, 180c and one or more evolved Node-Bs 160a, 160b, 160c substantially simultaneously. In a non-standalone configuration, the evolved Node-B 160a, 160b, 160c may act as a mobility anchor for the WTRUs 102a, 102b, 102c, and the gNB 180a, 180b, 180c may provide additional coverage and / or throughput for serving the WTRUs 102a, 102b, 102c.

[0066] Each of the gNBs 180a, 180b, 180c may be associated with a particular cell (not shown) and may be configured to manage radio resource management decisions, handover decisions, scheduling of users in UL and / or DL, support of network slicing, dual connectivity, interworking between NR and E-UTRA, routing of user plane data towards a user plane function (UPF) 184a, 184b, routing of control plane information towards an access and mobility management function (AMF) 182a, 182b, etc. Figure 1D As shown, gNBs 180a, 180b, and 180c may communicate with each other via an Xn interface.

[0067] Figure 1DThe illustrated CN 115 may include at least one AMF 182a, 182b, at least one UPF 184a, 184b, at least one session management function (SMF) 183a, 183b, and at least one data network (DN) 185a, 185b. Although each of the foregoing elements is depicted as part of the CN 115, it should be understood that any of these elements may be owned and / or operated by an entity other than the CN operator.

[0068] The AMF 182a, 182b may be connected to one or more of the gNBs 180a, 180b, 180c in the RAN 113 via the N2 interface and may act as a control node. For example, the AMF 182a, 182b may be responsible for authenticating users of the WTRU 102a, 102b, 102c, supporting network slicing (e.g., handling different protocol data unit (PDU) sessions with different requirements), selecting a specific SMF 183a, 183b, management of registration areas, termination of NAS signaling, mobility management, etc. The AMF 182a, 182b may use network slicing to customize CN support for the WTRU 102a, 102b, 102c, for example, based on the type of services used by the WTRU 102a, 102b, 102c. For example, different network slices may be established for different use cases, such as services relying on ultra-reliable low latency (URLLC) access, services relying on enhanced massive mobile broadband (eMBB) access, services for MTC access, etc. The AMF 162 may provide a control plane function for switching between the RAN 113 and other RANs (not shown) that employ other radio technologies, such as LTE, LTE-A, LTE-APro, and / or non-3GPP access technologies, such as Wi-Fi.

[0069] The SMF 183a, 183b may be connected to the AMF 182a, 182b in the CN 115 via the N11 interface. The SMF 183a, 183b may also be connected to the UPF 184a, 184b in the CN 115 via the N4 interface. The SMF 183a, 183b may select and control the UPF 184a, 184b, and configure traffic routing through the UPF 184a, 184b. The SMF 183a, 183b may perform other functions such as managing and allocating UE IP addresses, managing PDU sessions, controlling policy enforcement and QoS, providing downlink data notification, etc. The PDU session type may be IP-based, non-IP-based, Ethernet-based, etc.

[0070] The UPF 184a, 184b may be connected to one or more of the gNBs 180a, 180b, 180c in the RAN 113 via the N3 interface, which may provide the WTRUs 102a, 102b, 102c with access to packet-switched networks, such as the Internet 110, for example, to facilitate communications between the WTRUs 102a, 102b, 102c and IP-enabled devices. The UPF 184, 184b may perform other functions, such as routing and forwarding packets, enforcing user plane policies, supporting multi-homed PDU sessions, handling user plane QoS, buffering downlink packets, providing mobility anchoring, etc.

[0071] The CN 115 may facilitate communications with other networks. For example, the CN 115 may include or may communicate with an IP gateway (e.g., an IP Multimedia Subsystem (IMS) server) that acts as an interface between the CN 115 and the PSTN 108. In addition, the CN 115 may provide the WTRUs 102a, 102b, 102c with access to other networks 112, which may include other wired networks and / or wireless networks owned and / or operated by other service providers. In one embodiment, the WTRUs 102a, 102b, 102c may be connected to local data networks (DNs) 185a, 185b via the UPF 184a, 184b via the N3 interface to the UPF 184a, 184b and the N6 interface between the UPF 184a, 184b and the DN 185a, 185b.

[0072] Given that Figures 1A to 1D as well as Figures 1A to 1D , one or more or all of the functions described herein with reference to any of the following may be performed by one or more simulation elements / devices (not shown): WTRU 102a-102d, base station 114a-114b, evolved Node B 160a-160c, MME 162, SGW 164, PGW 166, gNB 180a-180c, AMF 182a-182b, UPF 184a-184b, SMF 183a-183b, DN 185a-185b and / or any other element / device described herein. A simulation device may be one or more devices configured to mimic one or more or all of the functions described herein. For example, a simulation device may be used to test other devices and / or simulate network and / or WTRU functions.

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

[0074] One or more simulation devices can perform one or more (including all) functions without being implemented / deployed as part of a wired and / or wireless communication network. For example, the simulation device can be used in a test scenario in a test lab and / or a non-deployed (e.g., testing) wired and / or wireless communication network to implement testing of one or more components. One or more simulation devices can be test equipment. Direct RF coupling and / or wireless communication via RF circuits (e.g., which can include one or more antennas) can be used by the simulation device to send and / or receive data.

[0075] In all embodiments described herein, (e.g., configuration) information may be described as being received by a network element (e.g., WTRU) from the network, for example, through system information or via any kind of protocol message. Although not explicitly mentioned in all embodiments described herein, the same (e.g., configuration) information may be pre-configured in the network element (e.g., WTRU) (e.g., via any kind of pre-configuration method, such as, for example, via factory settings), such that the (e.g., configuration) information may be used by the network element (e.g., WTRU) without being received from the network.

[0076] Examples of reliable and available wireless

[0077] For example, deterministic networking can provide the ability to carry any of unicast and multicast data streams for real-time applications with either low data loss rate and bounded latency based on any of time, resource reservation, and policy enforcement of distributed shapers, so as to support any application that is time-sensitive and mission-critical, such as on a converged enterprise infrastructure.

[0078] Wireless can work on a shared medium. Due to uncontrolled interference, including, for example, self-induced multipath fading, wireless transmission may have uncertainty. Internet Engineering Task Force (IETF) Reliable and Available Wireless (RAW) can be considered as a system designed to provide deterministic networking through a path that may include wireless elements. For example, RAW can be considered as a system for providing high reliability and availability for IP connectivity over a wireless medium. Wireless media may pose challenges to achieving (e.g., obtaining, delivering) deterministic properties (e.g., any one of low packet error rate, bounded continuous loss, and bounded delay). RAW can be considered as extending the system described by the IETF DetNet working group to provide any high reliability and availability for any IP network that utilizes (e.g., scheduled) wireless segments and other media (e.g., frequency / time sharing physical media resources with random traffic, such as, for example, IEEE Standard 802.15.4 Time Slot Channel Hopping (TSCH), 3GPP 5G Ultra-Reliable Low Latency Communication (URLLC), IEEE 802.11ax / be, and L-Band Digital Aeronautical Communication System (LDACS), etc.). Similar to DetNet, RAW technology can be viewed as maintaining an abstraction of the underlying radio layer, thereby addressing layer three aspects of supporting applications associated with high reliability and availability.

[0079] The RAW architecture is described in "Reliable and Available Wireless Architecture / Framework" (draft-ietf-raw-architecture-02), November 2021. RAW can be viewed as distinguishing between longer and shorter forwarding time scales, where the longer time scale can be used for routing calculations and the shorter time scale is used for forwarding decisions on a per-packet basis. For example, RAW may operate on a (e.g., deterministic network) flow on a path at a forwarding time scale within the network plane, which path may be referred to herein as a "track." A track may include one or more network segments (e.g., which may be referred to herein as hops). For example, a track may be pre-established and configured using components that may be independent of the RAW system. For example, a track may be strict or loose, depending on whether each hop or (e.g., only) a portion of the hops may be monitored or controlled by the RAW system.

[0080] The embodiments described herein are not limited to (e.g., IETF) RAW networks. Any network capable of ensuring reliability and availability (such as, for example, any network capable of providing deterministic networking) may be applicable to the embodiments described herein. Any network element with reliability and availability capabilities may be referred to herein as a RAW network element.

[0081] In all embodiments described herein, the terms "Quality of Service (QoS)", "QoS metric", "SLA", "SLA level" may be used interchangeably to refer to one or more metrics representing the quality (e.g., attributes) of a network (e.g., segment), including but not limited to any of (e.g., bounded) latency, (e.g., guaranteed) bandwidth (e.g., throughput), availability metrics, (e.g., bounded) reliability (e.g., loss) metrics.

[0082] For example, the RAW system may be constructed as an "observe, direct, decide, act" OODA loop. For example, the RAW system may include a network plane measurement protocol for network management (such as, for example, operations, administration, and maintenance (OAM)) to observe the attributes (e.g., characteristics) of any one of one or more hops along the track and end-to-end packet delivery. For example, the RAW system may also include a controller plane element that may be configured to report (e.g., transmit information indicating) link statistics to a path computation element (PCE) in a centralized controller that may calculate and establish (e.g., determine) the track and may provide metadata to direct (e.g., assist) routing decisions. For example, the RAW system may also include a runtime distributed path selection engine (PSE) that may determine which sub-track to use for the next packet that may be routed along the track. For example, the RAW system may also include packet (hybrid) automatic repeat request (ARQ), replication, elimination, and sequencing data plane actions that may operate at the DetNet service layer to improve the reliability of end-to-end transmission. In cases where the decision-making node may be located on a path down the track from the PSE, the RAW system may (eg, also) include (eg, in-situ) signaling.

[0083] For example, the overall OODA loop may allow for improved use of redundancy to achieve desired reliability and availability service level agreements (SLAs) and reduce use of (eg, limited) resources such as spectrum and battery.

[0084] For example, RAW may be viewed as distinguishing (e.g., separating) a path computation timescale where a (e.g., complex) path (e.g., track) may be recomputed from a path selection timescale where a forwarding decision may be made for one or more packets. For example, a RAW system may operate at a path selection timescale. For example, a RAW system may decide (e.g., determine, select) which solution may be used for (e.g., each) packet among redundant solutions that may be proposed (e.g., indicated) by a path computation element (PCE) to provide reliable and available service while reducing the use of limited resources. For example, a RAW system may include one or more PSEs that may be viewed as PCE counterparts to perform fast local adjustments of forwarding tables within a diversity that the PCE may have selected for a track. For example, the PSE may allow for the utilization (e.g., use) of richer forwarding capabilities having any of packet (hybrid) ARQ, replication, elimination, and ordering (PAREO), and scheduled transmission at a faster timescale.

[0085] In all embodiments described herein, a network element that includes (e.g., runs) PCE functionality may be referred to herein as a "PCE". In all embodiments described herein, a network element that includes (e.g., runs) PSE functionality may be referred to herein as a "PSE". For clarity, embodiments are described herein using path computation network elements and path selection network elements. Embodiments described herein are not limited to either of path computation network elements and path selection network elements, and are applicable to any kind of network element.

[0086] In all embodiments described herein, dividing the (e.g., requested) QoS into two (e.g., possibly different) parts may be referred to herein as splitting the (e.g., requested) QoS into a first QoS share and a second QoS share. In all embodiments described herein, the terms "first / second QoS share" may be used interchangeably with "first / second QoS budget" and "first / second QoS portion" to refer to any share / portion / budget of the (e.g., requested) QoS (e.g., metric, target).

[0087] RAW Terminology

[0088] For example, a track may include a networking diagram according to which packets may be transmitted using the same processing (e.g., processing). For example, although a path may be linear, a track may not be linear. For example, a track may include one or more (e.g., linear) paths that may, for example, diverge and rejoin, for example, to implement RAW PAREO operations.

[0089] In the embodiments described herein, the track may have the following properties.

[0090] For example, a track may include an entry node and an exit node, which may operate as, for example, DetNet edge nodes.

[0091] For example, the tracks may be reversible, eg, packets may be routed reversely of the flow of data packets, eg, to carry network management information, such as any of OAM measurements and control messages, which may be sent back to the ingress node.

[0092] For example, the apex of the track may include the functionality of a DetNet relay node, which may operate in a DetNet service sublayer and may provide PAREO functionality.

[0093] For example, a topological edge of the graph may include one or more serial sequences of DetNet sending nodes that may operate at a DetNet forwarding sublayer.

[0094] For example, a sub-track may include (e.g., a portion of) a track within a track. For example, the RAW PSE may select a sub-track on a per-packet basis and a per-packet set basis (either one or the other) to provide (e.g., desired, requested) reliability (e.g., QoS) for the transmitted stream.

[0095] Overview

[0096] For example, in the manufacturing sector, a group (e.g., a large number) of devices may be interconnected and may generate data, which may be expected to be reliably delivered to a control and monitoring agent. For another example, in the field of home gaming, an extended reality (XR) application may be expected to reliably deliver data between different devices.

[0097] A domain that can be managed by a single PCE may be referred to herein as a "single-domain RAW," where, for example, nodes may be operated and managed by a single management entity (e.g., a network element). In the single-domain RAW example, tracks and paths that can be used by the PSE involve (e.g., only involve) nodes belonging to the RAW domain.

[0098] There may be examples where the WTRU may be connected to different RAW domains and may communicate with either level of reliability and availability (e.g., guarantees), such as in a large factory where networks may be organized into domains (by production lines or buildings / sites), in a residential environment where different networks may exist (e.g., one in the home and one in the garden), or in an in-vehicle example (e.g., the WTRU is connected to different vehicles).

[0099] In all embodiments described herein, the terms "RAW domain", "RAW domain network" and "domain network" are used interchangeably to refer to a network of network elements that may be managed by an entity that provides a set of functionality (such as, for example, RAW) between network elements.

[0100] Figure 2 2 is a diagram illustrating an example of communications involving two RAW domains 21, 22 interconnected by a core network 20 (such as, for example, a 5G core). For example, a first WTRU 211 may be connected to the first RAW domain 21, and a second WTRU 222 may be connected to the second RAW domain 22. In the illustrated multi-domain example, the first WTRU 211 may communicate with the second WTRU 222 through the core network 20. The multi-domain example may differ from the single-domain example in that a single PCE may calculate orbits at a longer time scale, while the PSE may perform sub-orbit selection and refinement at a shorter time scale using information available in the RAW domain. The embodiments described herein may allow the WTRUs 211, 222 connected to different RAW domains 21, 22 to communicate at a level of either reliability and availability (e.g., guarantees).

[0101] For example, adjacent RAW domains 21, 22 may not be (e.g., directly) connected and may communicate via (e.g., non-DetNet capable) network segments (e.g., network segments that may not provide deterministic networking). Without deterministic (e.g., DetNet / RAW) end-to-end paths, any type of reliability and availability may not be provided. The embodiments described herein may allow for on-demand and dynamic provisioning of inter-domain reliable and available links.

[0102] For example, in the case where different RAW domains 21, 22 are connected by links 2110, 2111, 2112, the RAW domains 21, 22 may operate independently of each other. For example, the inter-PCE method may allow the PCE of one RAW domain to learn some inter-domain paths. In such an example, the PSE of one RAW domain 21 may lack full visibility of another RAW domain 22, and may not be able to take action on the other RAW domain due to the lack of a multi-domain OAM mechanism, thereby limiting the ability of the PSE to guarantee any SLA. The embodiments described herein may allow the implementation of an inter-PSE coordination mechanism across RAW domains.

[0103] For example, multi-domain (e.g., inter-domain) paths may be determined (e.g., calculated) based on a hierarchical PCE (G-PCE) as described in IETF RFC 6805. For example, a parent PCE may maintain a domain topology map that may include sub-domains (represented as vertices in the topology) and their interconnections (represented as links in the topology). The parent PCE may not have information about the contents of the sub-domains. For example, the parent PCE may not have information about the availability of resources within the sub-domain, nor may it have information about the availability of cross-domain connectivity in order to protect the confidentiality of cross-domain information. The parent PCE may be used to calculate multi-domain paths based on domain connectivity information. The child PCE may be responsible for one or more domains and may be used to calculate intra-domain paths based on its (e.g., own) domain topology information. For example, G-PCE operations may include a path computation client (PCC) transmitting an inter-domain path computation request (PCReq) message (as described in IETF RFC 5440) to a child PCE that is responsible for (e.g., manages) its domain. For example, G-PCE operations may include the child PCE forwarding the request to the parent PCE. For example, G-PCE operations may include a parent PCE calculating (e.g., determining) a (e.g., candidate) domain path from an ingress domain to an egress domain. For example, G-PCE operations may include a parent PCE transmitting an intra-domain PCReq message (between domain boundary nodes) to a child PCE that may be responsible for (e.g., managing) domains along the domain path. For example, G-PCE operations may include a child PCE returning information describing the intra-domain path to a parent PCE. For example, G-PCE operations may include a parent PCE constructing an end-to-end inter-domain path based on the intra-domain path. For example, G-PCE operations may include a parent PCE returning information describing the inter-domain path to a child PCE. For example, G-PCE operations may include a child PCE forwarding information describing the inter-domain path to a PCC.

[0104] IETF G-PCE based mechanisms may not allow RAW applications to benefit from either reliability and availability attributes in a multi-RAW domain environment. Embodiments described herein may allow additional information that is sensitive to (e.g., reflects, copes with) transient changes to be exchanged between PSEs of one or more RAW domains, thereby allowing either reliability and availability to be provided in a multi-domain wireless heterogeneous mesh network.

[0105] In a single RAW domain system, the PCE may be responsible for determining (e.g., calculating) the path (e.g., track), while the PSE may decide on the sub-track to use in a shorter time. For example, the PSE may operate as either a distributed functionality (performed by the different RAW routers of the path, which may make forwarding decisions based on local and any available OAM information) and a centralized functionality (performed by the ingress (ingress) routers in the domain, which may perform source routing). In the case where there are multiple ingress nodes, there may be multiple PSEs.

[0106] In an example with multiple connected RAW domains, running uncoordinated RAW in the domain may not allow RAW applications to benefit from any of the reliability and availability attributes. The embodiments described herein may allow PSEs of multiple RAW domains to obtain, for example, global end-to-end information. The embodiments described herein may allow PSEs of multiple RAW domains to, for example, run OAM mechanisms to monitor the quality of selected paths. In all embodiments described herein, but not limited to all embodiments described herein, OAM mechanisms are used to describe any QoS metrics that can be used to monitor any data stream (e.g., stream, service, application) and any network parameter that can be used to change (e.g., update, adjust) the mechanism that affects the monitored QoS metrics. Any network management mechanism (e.g., protocol, framework) may be applicable to the embodiments described herein.

[0107] The embodiments described herein may allow coordination between network elements of multiple RAW domains to be achieved in different ways. For example:

[0108] Embodiments described herein may allow a PSE of a RAW domain to learn (eg, receive information indicating) any of the PSEs to connect to and the PSEs to coordinate with in other neighboring RAW domains.

[0109] The embodiments described herein may allow for establishing and releasing (any of) coordinated links between PSEs of different RAW domains on demand.

[0110] Embodiments described herein may allow for the establishment and release (any of them) of cross-domain RAW paths on demand, e.g., so that any (e.g., involved) PSE may take actions to provide (e.g., guarantee) the desired (e.g., requested) reliability and availability. For example, these actions may include (e.g., new) inter-PSE interfaces (e.g., message sets) to facilitate (e.g., enable) the partitioning (e.g., splitting) of OAM capabilities and fast notification (any of them) of changes, enabling responses to be made at the affected RAW domains.

[0111] The present invention describes (e.g., new) RAW-specific inter-PCE and inter-PSE interactions (e.g., a set of messages to be exchanged between PCEs and PSEs of different RAW domains). These interactions (e.g., messages) enable different RAW domains to be connected and coordinated together by allowing actions (e.g., processing) to be distributed between different network elements (PCEs and PSEs of different RAW domains). These interactions (e.g., messages and associated processing) may allow (i) (e.g., direct) inter-domain connectivity to benefit from PAREO operations between RAW domains (e.g., outside a single RAW domain); (ii) RAW operations at RAW domains to be coordinated by distributing OAM functions between RAW domains, enabling dynamic adjustments through new inter-PSE interfaces. Based on the inter-PSE communications described herein, the embodiments described herein may allow mitigation of the disadvantages of keeping RAW domains isolated and uncoordinated.

[0112] Example of multi-domain awareness and inter-domain link establishment

[0113] Described herein is a method for enabling a RAW domain to detect, identify, and register (any of) other adjacent RAW domains. For example, cross-domain RAW communication may be based on one or more links that interconnect RAW domains. In all embodiments described herein, the term "link" is used to specify any type of network connection that can connect two network elements belonging to two different RAW domains, respectively. The (e.g., connected) network element may be a PSE or any other type of network element. For example, a link may be preconfigured (e.g., in an industrial environment). In another example (e.g., any one of a home network, an in-vehicle network), a link may be established based on an on-demand mechanism. A mechanism for establishing a link on demand between RAW domains is described herein.

[0114] For example, the RAW domains may be aware of their (e.g., respective) existence and may predict (e.g., detect) changes in connectivity. For example, the RAW domains may exchange (e.g., transmit and receive) information associated with the RAW domains and describing (e.g., indicating) the RAW domains in order to learn about other RAW domains. The information describing (e.g., indicating) the RAW domains may include (e.g., information items, indicating) any one of the following examples.

[0115] For example, information describing (eg, indicating) the RAW domain may include a first identifier (which may be referred to herein as a RAW-PSE-ID) that is associated with the PSE and allows identification of the PSE network element.

[0116] As another example, the information describing (e.g., indicating) the RAW domain may include a second identifier (which may be referred to herein as a RAW domain ID) associated with the RAW domain and allowing identification of one of the other RAW domains. The RAW domain ID may allow knowledge (e.g., indication) of which neighboring RAW domains are reachable, thereby distinguishing them from other neighboring RAW domains (e.g., unreachable RAW domains).

[0117] For another example, the information describing (eg, indicating) a RAW domain may include a RAW domain prefix indicating one or more IP prefixes of nodes (eg, network elements) reachable in the RAW domain.

[0118] For another example, the information describing (eg, indicating) the RAW domain may include any one of a (eg, IP) address and an interface uniform resource identifier (URI) of a PCE of the RAW domain (which may be referred to herein as a RAW domain PCE).

[0119] Figure 3 3 is a diagram illustrating an example of multi-domain awareness and connectivity establishment. For example, a first RAW domain 31 may be within the scope of a second RAW domain 32. More specifically, the first RAW domain 31 may include one or more first network elements 311, 312, which may be within the scope of one or more second network elements 321 of the second RAW domain 32. For example, the first RAW domain 31 may include a path computation network element 313, which may or may not be within the scope of the second RAW domain 32. For example, there may be different methods for discovering RAW domains, which may be described as follows.

[0120] In a first example, a first RAW domain 31 may discover a second RAW domain 32 based on a directory. For example, a RAW domain operator may publish (e.g., transmit) and may continuously (e.g., transmit) update information indicating RAW domains in the directory that are accessible by other (e.g., authorized) RAW domains. Any technology for populating and hosting a directory (such as, for example, a domain name system (DNS), a public blockchain, and a private blockchain) may be applicable to the embodiments described herein. For example, a first network element 311, 312 of a first RAW domain 31 may transmit first information indicating a first RAW domain as described herein to a second network element 321 of a second RAW domain 32, which may be within a range 331 of the first network element 311, 312. For example, a first network element 311, 312 may receive second information indicating a second RAW domain as described herein from a second network element 321 of a second RAW domain, which may be within a range 331 of the first network element 311, 312.

[0121] In a second example, the first RAW domain 31 may discover the second RAW domain 32 based on out-of-band signaling on a (e.g., established) link 332. For example, the link 332 may have been configured between RAW network elements belonging to different RAW domains. For example, the link 332 may be used to exchange RAW domain information. Any protocol capable of exchanging information indicating a RAW domain may be applicable to the embodiments described herein, such as, but not limited to, any of the Border Gateway Protocol Link State (BGP-LS) and other routing protocols (such as, for example, the Internet Control Message Protocol (ICMP)).

[0122] In a third example, the first RAW domain 31 may discover the second RAW domain 32 based on a RAN-based announcement 331. For example, in the absence of a pre-established link, the (e.g., L2) announcement may be used to piggyback (e.g., transmit / receive) RAW domain information (e.g., using IEEE 802.11 beacon access network query protocol (ANQP)). The information indicating the RAW domain may allow on-demand inter-domain links to be established and their status to be updated in near real-time (e.g., by supporting predictions based on L2 measurements (e.g., any of signal levels and mobility predictions)). For example, some RAN L2 signaling mechanisms (e.g., messages) may include RAW domain information (e.g., indicating a RAW domain) and may be used by a network element (such as, for example, a PSE) at a RAW domain boundary for any of the following purposes: announcing the RAW domain information; and monitoring information broadcasted / shared by PSEs from neighboring RAW domains.

[0123] Example of signaling for inter-domain link establishment

[0124] This document describes a method to enable a RAW domain within the radio coverage of another RAW domain to establish an on-demand inter-domain link to enable coordination across the two RAW domains.

[0125] Figure 4 is a diagram illustrating an example of RAW domain-aware link establishment. Figure 4 Examples of operations and signaling are illustrated, wherein RAW domain awareness, RAW inter-domain link establishment and RAW domain awareness update are described.

[0126] For example, the first RAW domain, which may be referred to herein as "domain 1", may be a mobile RAW domain. The embodiments described herein may (e.g., also) be applicable to fixed RAW domains. For example, the first RAW domain may be within (e.g., enter) the radio coverage of a second RAW domain, which may be referred to herein as "domain 2". For example, a first node of domain 1 (which may be referred to herein as "node 1-4") may be within the radio coverage of one or more second nodes of domain 2 (which may be referred to herein as node 2-1 and node 2-2). For example, one or more layer two (L2) messages 41 may be periodically (e.g., repeatedly) exchanged (e.g., via broadcast). For example, the L2 message 41 may include RAW information indicating any one of a PSE ID, a RAW domain ID, an IP prefix, and a PCE address (e.g., a URI). Any variation of the procedure (e.g., where (only) one parameter may be exchanged via an L2 message, and other means (e.g., messages, protocols) may be used to obtain (e.g., exchange) additional information (e.g., in order to reduce the total overhead)) may be applicable to the embodiments described herein.

[0127] For example, after receiving one or more L2 messages 41, the PSEs (nodes 1-4, nodes 2-1, and nodes 2-2) that may be within the radio coverage may be aware of the existence of other PSEs from different RAW domains. For example, the PSEs of the RAW domain may notify the PCE of the RAW domain in which it is located. For example, one or more PSEs of the corresponding RAW domain (e.g., nodes 1-4, nodes 2-1, and nodes 2-2) may transmit information 42 to the PCE of the RAW domain in which it is located to indicate that there are network elements (PSEs) of other RAW domains within the radio coverage. For example, based on the information 42, the PCE of the first RAW domain (which may be referred to as PCE1 in this article) and the PCE of the second RAW domain (which may be referred to as PCE2 in this article) may be aware of the existence of these PSEs, and one or more links may be established between these PSEs to interconnect the RAW domains in which they are located.

[0128] For example, domain 1 and domain 2 may be aware of each other and may know which border PSEs may establish one or more links to interconnect the RAW domains. For example, PCE1 may receive a path computation request message 43 indicating a request to establish one or more paths (e.g., tracks) between network elements in domain 1 and an IP prefix (e.g., one or more IP addresses) that may be associated with domain 2. Receiving such a path computation request message 43 may indicate to PCE1 that another endpoint may be located in domain 2 and that domain 1 may be locally interconnected with domain 2 (e.g., via a wireless network). For example, PCE1 may execute various procedures to establish a link that interconnects domain 1 with domain 2.

[0129] For example, PCE1 may transmit one or more link establishment messages 44a, 44b to one or more PSEs of domain 1 to request the establishment of a link. For example, the one or more link establishment messages 44a, 44b may include information indicating any of the following: (i) a first link to be established between nodes 1-4 of domain 1 and nodes 2-1 of domain 2; and (ii) a second link to be established between nodes 1-4 of domain 1 and nodes 2-2 of domain 2. For example, PCE1 may transmit similar messages 44c, 44d to PCE2 to request the establishment of the same link by endpoints in domain 2. For example, PCE1 may transmit one or more link establishment messages 44c, 44d to PCE2 of domain 2, the one or more link establishment messages including information indicating any of the following: (i) a first link to be established between nodes 1-4 of domain 1 and nodes 2-1 of domain 2; and (ii) a second link to be established between nodes 1-4 of domain 1 and nodes 2-2 of domain 2. For example, PCE2 may transmit one or more link establishment messages 44e, 44f to one or more PSEs in domain 2, wherein the one or more link establishment messages 44e, 44f may include information indicating any of: (i) a first link to be established between nodes 1-4 of domain 1 and nodes 2-1 of domain 2; and (ii) a second link to be established between nodes 1-4 of domain 1 and nodes 2-2 of domain 2. The exchange of link establishment messages 44a, 44b, 44c, 44d, 44e, 44f may allow links to be established between network elements of different RAW domains.

[0130] For example, domain 1 and domain 2 may be interconnected (eg, via a first link and a second link) (eg, after an exchange of link establishment messages), and a method for establishing an inter-domain connection may be performed as described herein.

[0131] In the case where the first RAW domain (domain 1) moves out of the coverage of the second RAW domain (domain 2), or in the case where an obstacle temporarily blocks connectivity, the border PSE may detect that there is no connectivity between the first RAW domain and the second RAW domain. For example, any border PSE may notify (e.g., transmit information 45a, 45b, 45c indicating that there is no connectivity between the RAW domains) the respective PCE, which may be aware that there may no longer be any available local connectivity between the RAW domains.

[0132] For example, based on any of artificial intelligence and machine learning (AI / ML) algorithms, connectivity disruptions may be predicted before they occur, thereby improving reliability and availability.

[0133] Example of establishing a multi-domain RAW connection

[0134] Mechanisms and signaling extensions for achieving inter-domain RAW connectivity are described herein. For example, an inter-domain link establishment procedure may have been performed as indicated in the embodiments described herein. An interface between PSEs of two RAW domains is described herein that enables calculation of any of the inter-domain paths, tracks, sub-tracks, and supports coordinated OAM across the two RAW domains.

[0135] For example, Figure 5 is a diagram illustrating an example of a multi-domain RAW signaling flow, which is based on Figure 2 The illustrated example (e.g., wherein a first WTRU that may be connected to a first RAW network element 514 (which may be referred to herein as node 1-4) of a first RAW domain may establish communication with a second WTRU that is connected to a second RAW network element 521 (which may be referred to herein as node 2-1) of a second RAW domain.

[0136] For example, an ingress RAW network element 514 (e.g., node 1-4) may receive an initial request message 50 including information indicating a request for connectivity with a (e.g., given) target RAW network element 521 (e.g., node 2-1), and a QoS (e.g., SLA) requested, for example, in terms of reliability and availability. For example, the information may indicate a target address (e.g., a target address of any one of a target WTRU and a target RAW network element to which the target WTRU may be connected). For example, the information may also indicate a QoS (e.g., SLA) that may be requested for a connection with the target WTRU. For example, either of the source and target RAW network elements may be a WTRU. For example, either of the source and target WTRUs may be a RAW network element.

[0137] For example, the ingress RAW network element 514 of domain 1 (e.g., nodes 1-4) may operate as a PSE (which may be referred to herein as the PSE at domain 1) and may transmit a first request message 51 to the PCE 510 of domain 1 (which may be referred to herein as PCE1) to request (e.g., calculate, determine) one or more tracks toward a target RAW network element 521 (to which the target WTRU may be connected) and with the requested QoS (e.g., SLA). For example, the first request message 51 may include information indicating any of the following: (i) a source RAW network element (which may indicate any of an IP address and an identifier of the ingress RAW network element 514); a target RAW network element (which may indicate, for example, any of an IP address and an identifier of the target RAW network element to which the target WTRU may be connected); and the requested QoS (e.g., SLA). For example, the requested QoS (e.g., SLA) may be indicated by one or more values ​​(e.g., levels) of one or more QoS metrics, such as any of: (e.g., bounded) latency, (e.g., guaranteed) bandwidth, (e.g., bounded) jitter, (e.g., bounded) reliability ratio (e.g., any of (e.g., packet) error rate and (e.g., packet) loss rate), (e.g., guaranteed) availability ratio, etc. For example, the target RAW network element may be determined by the ingress RAW network element 514 based on the RAW domain prefix indicated in the RAW domain information (Describing Domain 2) that may have been received from Domain 2. In another example (not shown), the ingress RAW network element 514 may not receive the initial request message 50 from the WTRU, and may receive one or more packets related to the target RAW network element 521 (e.g., Node 2-1), which may trigger the sending of the first request message 51 to request one or more tracks towards the target RAW network element 521 (e.g., Node 2-1).

[0138] For example, PCE1 510 may know (e.g., based on the RAW domain-aware method described above) that the target may be located in another domain (Domain 2) and that the PCE 520 of the target domain may be PCE2. For example, PCE1 510 may know (e.g., based on information collected via the RAW domain-aware method) (e.g., store information indicating) one or more (e.g., ingress) RAW network elements 521, 522 in Domain 2 that may be connected to Domain 1. For example, the one or more (e.g., ingress) RAW network elements 521, 522 (e.g., Node 2-1 and Node 2-2) may operate as a PSE at Domain 2. For example, PCE1 510 may transmit a request message 52 to PCE2 520 to request (e.g., calculate, determine) available tracks from the PSE at Domain 2 to the target (e.g., in Domain 2, which may be referred to herein as Track 2) and characteristics of the links forming these tracks (e.g., link_quality). Any type of information about links that may be provided by PCE2 520 that allows PCE1 510 and any of the PSEs at Domain 1 (eg, Nodes 1-4) to calculate (eg, determine) how to allocate SLAs between RAW domains may be applicable to the embodiments described herein.

[0139] For example, PCE2 520 may determine (e.g., calculate) one or more tracks in domain 2 (which may be referred to herein as track 2), and may respond to PCE1 510 by transmitting a response message 53 to PCE1 510, the response message including information indicating a characteristic of a link (e.g., link_quality). For example, the information indicating a characteristic of a link (e.g., link_quality) may include one or more indications of any of available bandwidth, observed reliability, latency, link variability, link mobility, etc. For example, the response message 53 may also include information indicating one or more tracks in domain 2 (track 2).

[0140] For example, PCE1 510 may provide any tracks that can reach the target and shares of QoS (e.g., SLA) between domain 1 and domain 2 (which may be referred to herein as SLA1 and SLA2) to the PSE at domain 1. For example, PCE1 510 may determine one or more tracks in domain 1, which may be referred to herein as track 1, which may be combined with track 2 in domain 2 to reach the target. For example, the ingress RAW network element 514 of domain 1 may receive a response message 54 from PCE1 510, the response message including information indicating any of the following: (i) one or more tracks (e.g., any of track 1 and track 2); (ii) one or more PSEs 521, 522 of the second RAW domain (e.g., PSEs at domain 2), the one or more PSEs interconnecting the first RAW domain with the second RAW domain; and (iii) a first QoS share and a second QoS share, the first QoS share and the second QoS share to be applied to the first RAW domain and the second RAW domain, respectively.

[0141] For example, any of the SLA and QoS (e.g., numbers, metrics) may include (by way of example and not limitation) any of the following: (i) bounded (e.g., maximum) delay, such as, for example, bounded latency; (ii) guaranteed bandwidth (e.g., data rate, throughput); (iii) bounded (e.g., maximum) jitter, such as, for example, bounded jitter (e.g., packet delay variation); (iv) (e.g., bounded) reliability ratio (e.g., any of (e.g., packet) error rate and (e.g., packet) loss rate); and (v) availability ratio, etc.

[0142] For example, the requested QoS (e.g., SLA) can be split into a first QoS share (e.g., SLA1) and a second QoS share (e.g., SLA2), so that under the condition that the first QoS share is satisfied on the first domain network and under the condition that the second QoS share is satisfied on the second domain network, it can be determined that the requested QoS is satisfied between the source network element and the target network element. Non-limiting examples of SLA / QoS splitting may include any one of the following examples.

[0143] In one example, for a QoS associated with 10ms bounded latency and 99.99 availability, a first QoS share (SLA1) may be associated with 6ms bounded latency and 99.999 availability and a second QoS share (SLA2) may be associated with 3ms bounded latency and 99.999 availability.

[0144] In another example, for a QoS associated with 10ms bounded delay and 1Mbps guaranteed bandwidth, a first QoS share (SLA1) may be associated with 5ms bounded delay and 2Mbps guaranteed bandwidth, and a second QoS share (SLA2) may be associated with a 5ms bounded delay and 5Mbps guaranteed bandwidth SLA.

[0145] More generally, any example of QoS may be applicable to the embodiments described herein as long as it includes (e.g., is associated with) a set of metrics (e.g., criteria to be met) that can be split into a first QoS share and a second QoS share, and where the first QoS share and the second QoS share may include (e.g., is associated with) a set of corresponding sub-metrics (e.g., sub-criteria to be met).

[0146] For example, the PSE 514 at domain 1 may transmit one or more second request messages 55a, 55b to one or more PSEs 521, 522 of the second RAW domain (e.g., PSEs at domain 2), respectively. The one or more second request messages 55a, 55b may (e.g., indicate) a request to establish one or more (e.g., direct) communication channels, for example, to provide (e.g., to carry) network management (e.g., OAM) information to be used by the PSE 514 at domain 1 to determine (e.g., calculate) a sub-track to be used for (e.g., data) traffic. The one or more (e.g., direct) communication channels may be any kind of connection (e.g., session) that may be established between two PSEs, over which the two PSEs may exchange network management (e.g., OAM) information to monitor (e.g., and guarantee) QoS (e.g., SLA). For example, the one or more second request messages 55a, 55b may include information indicating a first QoS share (SLA1) and a second QoS share (SLA2), the first QoS share and the second QoS share to be monitored (e.g., and guaranteed) on the corresponding RAW domain (e.g., domain 1, domain 2) (e.g., by the network element of the corresponding RAW domain), respectively. For example, the one or more second request messages 55a, 55b may also include information indicating one or more tracks (e.g., any of track 1 and track 2) of either domain 1 or domain 2.

[0147] For example, the one or more PSEs 521, 522 at domain 2 may acknowledge the one or more second request messages 55a, 55b, for example, by transmitting an acknowledgement message 56a, 56b (e.g., including information indicating an acknowledgement of the one or more second request messages 55a, 55b). For example, after receiving the acknowledgement message 56a, 56b, a communication channel may be established (e.g., for carrying network management information), and the PSE 514 at domain 1 may operate as a PSE related to the path (sub-track) to be used (e.g., in domain 1) (e.g., may begin making decisions at a forwarding time scale).

[0148] For example, the PSEs at domain 1 and domain 2 may perform network management (e.g., OAM) procedures, such as described in the June 2021 IETF draft "Operations, Administration and Maintenance (OAM) features for RAW" (draft-ietf-raw-oam-support-02). Any kind of network management framework that is capable of monitoring (e.g., determining) whether the monitored QoS (e.g., SLA) reaches (e.g., satisfies) the requested QoS (e.g., SLA, SLA1, SL2) and is capable of applying corrective actions (e.g., performing sub-track selection, adapting any of the sub-tracks and tracks) may be applicable to the embodiments described herein. For example, network management (e.g., OAM) mechanisms may be applied in-band (rate sharing of traffic) or out-of-band. For example, a PSE at domain 1 may exchange network management messages 57b with one or more other PSEs in domain 1 that are associated with (e.g., related to) a track (e.g., track 1) of domain 1 to monitor the QoS of track 1 to determine whether the monitored QoS reaches (e.g., satisfies) a requested first QoS share (e.g., SLA1), and apply any corrective actions (e.g., perform sub-track selection, adapt any of the sub-tracks and tracks) so that the requested first QoS share (e.g., SLA1) is obtainable (e.g., provided). Similarly, a PSE at domain 2 may exchange network management messages 57a to monitor the QoS on a track (e.g., track 2) of domain 2 to determine whether the monitored QoS reaches (e.g., satisfies) a requested second QoS share (e.g., SLA2), and apply any corrective actions (e.g., perform sub-track selection, adapt any of the sub-tracks and tracks) so that the requested second QoS share (e.g., SLA2) is obtainable (e.g., provided). Embodiments described herein may allow per-domain distributed OAM to be performed to react in shorter timescales in any of the involved RAW domains such that the requested QoS / SLA (eg, reliability and availability) may be achieved (eg, obtained, satisfied).

[0149] For example, any aggregated and pre-processed information may be shared between PSEs to facilitate early detection of problems and calculation (e.g., selection) of sub-tracks. In the event that a PSE detects a violation of an SLA, the PSE may notify the domain PCE and any of the other PSEs (e.g., PSEs of other domains) so that countermeasures (e.g., corrective actions) may be performed. Examples of countermeasures (e.g., corrective actions) may include any of the following: selecting a different sub-track; making a different PAREO decision; requesting a PCE (of either domain 1 or domain 2) to recalculate the path and / or adjust the share of cross-domain QoS (e.g., SLA). For example, in the event that a first (respectively, second) QoS share is not achieved on a first (respectively, second) domain network, a message may be transmitted to any of the one or more PSEs of PCE1 (respectively, PCE2) and the second (respectively, first) domain network to request recalculation of the track and / or adjustment of the requested QoS (e.g., SLA) share. For example, a PSE at domain 1 and a PSE at domain 2 may exchange network management messages 58a, 58b via a communication link. For example, the network management message 58a, 58b may include information indicating the QoS to be monitored (eg, a metric), the monitored QoS, and any of a requested corrective action).

[0150] In a first example, the path between WTRU1 and WTRU2 may be bidirectional and the mechanisms described herein may be applied in both directions (WTRU1 to WTRU2 and WTRU2 to WTRU1). In a second example, the path may not be bidirectional and the mechanisms described herein for the WTRU1 to WTRU2 direction may be repeated to cover the WTRU2 to WTRU1 direction.

[0151] Figure 6 6 is a diagram illustrating an example of communication involving two RAW domains 61, 62 interconnected by a wireless network. A first WTRU 611 of the first RAW domain 61 may communicate with a second WTRU 622 of the second RAW domain 62. The first RAW domain 61 and the second RAW domain 61 may be interconnected by any of two interconnection paths and two interconnection links 6110, 6112, which may interconnect two PSEs 612, 613 of the first domain 61 with two PSEs 621, 623 of the second domain 62, respectively. For example, any of the paths and communication links 6110 and 6112 between the first domain 61 and the second domain 62 may be included in any of Track 1 and Track 2 (e.g., for the purpose of network management (e.g., OAM)) for monitoring whether the monitored QoS reaches (e.g., satisfies) any of the requested first QoS share (e.g., SLA1) and the requested second QoS share (e.g., SLA2).

[0152] Figure 7 is a diagram illustrating an example of a multi-domain RAW communication method 700. For example, the method may be implemented in a first path selection network element (PSE1) of a first domain network. For example, in step 710, PSE1 may transmit a first request message to a path calculation network element (PCE1) of the first domain network, the first request message requesting one or more tracks toward a second domain network (e.g., its second path selection network element (PSE2)), the first request message indicating the requested QoS. For example, in step 720, PSE1 may receive a response message from PCE1, the response message indicating any of the following: (i) one or more tracks; (ii) one or more second path selection network elements (PSE2) of the second domain network, the one or more second path selection network elements interconnecting the first domain network with the second domain network; and (iii) a first QoS share of the requested QoS and a second QoS share of the requested QoS, the first QoS share and the second QoS share to be applied to the first domain network and the second domain network, respectively. For example, in step 730, PSE1 may transmit one or more second request messages requesting to establish a communication channel (e.g., to carry network management information) across the first domain network and the second domain network to one or more PSE2 of the second domain network, the one or more second request messages indicating the first QoS share and the second QoS share to be monitored on the first domain network and the second domain network via the network management information (e.g., the communication channel). For example, in step 740, PSE1 may receive a confirmation indicating that the communication channel has been established from one or more PSE2 of the second domain network.

[0153] For example, the requested QoS may be split into a first QoS share and a second QoS share, such that the requested QoS may be met (e.g., between the first path selection network element and the second path selection network element) under the condition that the first QoS share is met on the first domain network and under the condition that the second QoS share is met on the second domain network.

[0154] For example, any of the requested QoS, the first QoS share, and the second QoS share may include at least one QoS metric indicating any of bounded latency, guaranteed bandwidth, bounded jitter, bounded reliability ratio, and availability ratio.

[0155] For example, PSE 1 may receive one or more first network management messages including network management information to monitor a first QoS of a first portion of one or more tracks associated with a first domain network.

[0156] For example, the PSE 1 may adapt any one of a sub-track and a track of a first portion of the one or more tracks based on the received network management information, wherein any one of the sub-track and the track may be adapted so that the monitored first QoS may satisfy the first QoS share.

[0157] For example, PSE1 may receive one or more second network management messages from one or more second path selection network elements of the second domain network, wherein the one or more second network management messages may include network management information to monitor a second QoS of a second portion of one or more tracks associated with the second domain network.

[0158] For example, the one or more second network management messages may be received over a possibly established communication channel.

[0159] For example, the PSE 1 may adapt any one of the sub-tracks and tracks of the second portion of the one or more tracks based on the received network management information, wherein any one of the sub-tracks and tracks may be adapted so that the monitored second QoS can satisfy the second QoS share.

[0160] For example, before transmitting the first request message, PSE1 may receive an initial request message from a first WTRU of a first domain network, wherein the initial request message may include information requesting to establish connectivity with a second WTRU of a second domain network at the requested QoS.

[0161] For example, before transmitting the first request message, PSE1 may receive first information from at least one of the one or more second path selection network elements of the second domain network, wherein the first information may indicate that at least one of the one or more second path selection network elements exists within the radio coverage of the first path selection network element.

[0162] For example, the first information may indicate any of: a first identifier identifying at least one of the one or more second path selection network elements; a second identifier identifying the second domain network; an IP prefix of a network element of the second domain network; and an address of a second domain network path computation network element.

[0163] For example, PSE1 may transmit second information to the path computation network element of the first domain network, wherein the second information may indicate that at least one of the one or more second path selection network elements exists within the radio coverage of the first path selection network element.

[0164] For example, PSE1 may receive third information from a path computation network element of the first domain network, wherein the third information may indicate one or more links to be established between the first path selection network element and one or more second path selection network elements for interconnecting the first domain network with the second domain network.

[0165] For example, when the first path selection network element is not within the coverage of one or more second path selection network elements, PSE1 may transmit fourth information to the path calculation network element of the first domain network, wherein the fourth information indicates that there is no connectivity between the first domain network and the second domain network.

[0166] In one embodiment, a network element is described herein, the network element comprising a processor and a transmitter and a receiver (e.g., a transceiver) operatively coupled to the processor. For example, the processor may be configured to transmit a first request message requesting one or more tracks toward a second domain network to a first network element of a first domain network, the first request message indicating the requested QoS. For example, the processor may be configured to receive a response message from the first network element, the response message indicating: (i) one or more second network elements of the second domain network, the one or more second network elements interconnecting the first domain network with the second domain network; and (ii) QoS partitioning of the requested QoS to be applied to the first domain network and the second domain network. For example, the processor may be configured to transmit one or more second request messages requesting to establish a communication channel across the first domain network and the second domain network to the one or more second network elements of the second domain network, the one or more second request messages indicating the QoS partitioning to be monitored on the first domain network and the second domain network via the communication channel. For example, the processor may be configured to receive a confirmation from the one or more second network elements of the second domain network indicating that the communication channel has been established.

[0167] For example, the requested QoS may be divided into a first QoS budget and a second QoS budget, so that the requested QoS may be met under the condition that the first QoS budget is reached on the first domain network and under the condition that the second QoS budget is reached on the second domain network.

[0168] For example, any of the requested QoS, the first QoS budget, and the second QoS budget may include at least one QoS metric indicating any of bounded latency, guaranteed bandwidth, bounded jitter, bounded reliability ratio, and availability ratio.

[0169] For example, the processor may be further configured to receive one or more network management messages including network management information in order to monitor QoS in the first domain network.

[0170] For example, the processor may be further configured to perform sub-track selection in the one or more tracks based on the network management information such that the first QoS budget can be achieved on the first domain network.

[0171] For example, when the first QoS budget is not reached on the first domain network, the processor may be further configured to transmit a third request message to the first network element of the first domain network to request recalculation of the one or more tracks and / or adjustment of the QoS partitioning.

[0172] For example, the processor may also be configured to receive an initial request message from the first WTRU of the first domain network before transmitting the first request message, wherein the initial request message may include information requesting connectivity to be established with the second WTRU of the second domain network at the requested QoS.

[0173] For example, the processor may also be configured to receive first information from at least one of the one or more second network elements of the second domain network before transmitting the first request message, wherein the first information may indicate that the at least one of the one or more second network elements is within the radio coverage of the network element.

[0174] For example, the first information may indicate any of: a first identifier identifying the at least one second network element among the one or more second network elements; a second identifier identifying the second domain network; and an IP prefix of the network element of the second domain network.

[0175] For example, the processor may be further configured to transmit second information to the first network element of the first domain network, wherein the second information may indicate that the at least one second network element among the one or more second network elements exists within the radio coverage of the network element.

[0176] For example, the processor may also be configured to receive third information from the first network element of the first domain network, wherein the third information may indicate one or more links to be established between the network element and the one or more second network elements for interconnecting the first domain network with the second domain network.

[0177] For example, when the network element is not within the coverage of the one or more second network elements, the processor may be further configured to transmit fourth information to the first network element of the first domain network, wherein the fourth information may indicate that there is no connectivity between the first domain network and the second domain network.

[0178] For example, any of the network element and the one or more second network elements may be a routing network element configured to perform sub-track selection on a per one or more packet basis.

[0179] For example, the first network element may be a path computation network element.

[0180] In one embodiment, a method may be implemented in a network element. For example, the method may include transmitting a first request message to a first network element of a first domain network requesting one or more tracks toward a second domain network, the first request message indicating the requested QoS. For example, the method may also include receiving a response message from the first network element, the response message indicating: (i) one or more second network elements of the second domain network, the one or more second network elements interconnecting the first domain network with the second domain network; and (ii) a QoS partitioning of the requested QoS to be applied to the first domain network and the second domain network. For example, the method may also include transmitting one or more second request messages to the one or more second network elements of the second domain network requesting to establish a communication channel across the first domain network and the second domain network, the one or more second request messages indicating the QoS partitioning to be monitored on the first domain network and the second domain network via the communication channel. For example, the method may also include receiving a confirmation from the one or more second network elements of the second domain network indicating that the communication channel has been established.

[0181] For example, the requested QoS may be divided into a first QoS budget and a second QoS budget, so that the requested QoS may be met under the condition that the first QoS budget is reached on the first domain network and under the condition that the second QoS budget is reached on the second domain network.

[0182] For example, any of the requested QoS, the first QoS budget, and the second QoS budget may include at least one QoS metric indicating any of bounded latency, guaranteed bandwidth, bounded jitter, bounded reliability ratio, and availability ratio.

[0183] For example, the method may further include receiving one or more network management messages including network management information in order to monitor QoS in the first domain network.

[0184] For example, the method may further include performing sub-track selection in the one or more tracks based on the network management information such that the first QoS budget can be achieved on the first domain network.

[0185] For example, the method may further include transmitting a third request message to the first network element of the first domain network to request recalculation of the one or more tracks and / or adjustment of the QoS partitioning if the first QoS budget is not reached on the first domain network.

[0186] For example, the method may also include receiving an initial request message from a first WTRU of the first domain network before transmitting the first request message, wherein the initial request message may include information requesting connectivity to be established with a second WTRU of the second domain network at the requested QoS.

[0187] For example, the method may also include, before transmitting the first request message, receiving first information from at least one second network element of the one or more second network elements of the second domain network, wherein the first information may indicate that the at least one second network element of the one or more second network elements is within the radio coverage of the network element.

[0188] For example, the first information may indicate any of: a first identifier identifying the at least one second network element among the one or more second network elements; a second identifier identifying the second domain network; and an IP prefix of the network element of the second domain network.

[0189] For example, the method may further include transmitting second information to the first network element of the first domain network, wherein the second information may indicate that the at least one second network element of the one or more second network elements exists within the radio coverage of the network element.

[0190] For example, the method may further include receiving third information from the first network element of the first domain network, wherein the third information may indicate one or more links to be established between the network element and the one or more second network elements for interconnecting the first domain network with the second domain network.

[0191] For example, the method may further include transmitting fourth information to the first network element of the first domain network when the network element is not within the coverage of the one or more second network elements, wherein the fourth information may indicate that there is no connectivity between the first domain network and the second domain network.

[0192] For example, any of the network element and the one or more second network elements may be a routing network element configured to perform sub-track selection on a per one or more packet basis.

[0193] For example, the first network element may be a path computation network element.

[0194] Any features, variants, or embodiments described for the method are compatible with: an apparatus including means for processing the disclosed method, an apparatus including circuits configured to process the disclosed method (including any of a transmitter, a receiver, a processor, and a memory), a computer program product including program code instructions, and a non-transitory computer-readable storage medium storing the program instructions.

[0195] in conclusion

[0196] Although features and elements are provided above in specific combinations, it will be understood by those of ordinary skill in the art that each feature or element may be used alone or in any combination with other features and elements. The present disclosure is not limited to the specific embodiments described in the present application, which are intended to be illustrative of various aspects. Many modifications and variations can be made without departing from the essence and scope of the present invention, as they will be apparent to those skilled in the art. Unless explicitly provided as such, any element, action or description used in the present application specification should not be understood as being essential or necessary to the present invention. According to the foregoing description, in addition to those listed herein, functionally equivalent methods and devices within the scope of the present disclosure will be apparent to those skilled in the art. Such modifications and variations are intended to fall within the scope of the appended claims. The present disclosure is limited only to the terms of the appended claims and the full range of equivalent forms of such entitled claims. It should be understood that the present disclosure is not limited to a specific method or system.

[0197] For simplicity, the foregoing embodiments are discussed with respect to terminology and structure of infrared capable devices (i.e., infrared transmitters and receivers). However, the embodiments discussed are not limited to these systems, but may be applied to other systems using other forms of electromagnetic waves or non-electromagnetic waves (such as sound waves).

[0198] It should also be understood that the terms used herein are used only for the purpose of describing specific embodiments and are not intended to be limiting. As used herein, the term "video" or the term "image" may mean any of a snapshot, a single image, and / or a plurality of images displayed on a time basis. For example, when referred to herein, the term "user equipment" and its abbreviation "UE", the term "remote" and / or the term "head-mounted display" or its abbreviation "HMD" may mean or include (i) a wireless transmit and / or receive unit (WTRU); (ii) any of a plurality of embodiments of the WTRU; (iii) a wireless and / or wired (e.g., tetherable) device configured with (in particular) some or all of the structure and functionality of the WTRU; (iii) a wireless and / or wired device configured with less than all of the structure and functionality of the WTRU; or (iv), etc. This document is relative to Figures 1A to 1D Details of an example WTRU are provided that may represent any WTRU described herein. As another example, various disclosed embodiments herein are described above and below as utilizing a head mounted display. Those skilled in the art will recognize that devices other than head mounted displays may be utilized and that some or all of the present disclosure and various disclosed embodiments may be modified accordingly without undue experimentation. Examples of such other devices may include drones or other devices configured to stream information to provide an adapted reality experience.

[0199] In addition, the methods provided herein may be implemented in a computer program, software, or firmware incorporated into a computer-readable medium for execution by a computer or processor. Examples of computer-readable media include electronic signals (sent via a wired or wireless connection) and computer-readable storage media. Examples of computer-readable storage media include, but are not limited to, read-only memory (ROM), random access memory (RAM), registers, cache memory, semiconductor memory devices, magnetic media (such as built-in hard disks and removable disks), magneto-optical media, and optical media (such as CD-ROM disks and digital versatile disks (DVDs)). A processor associated with the software may be used to implement a radio frequency transceiver for a WTRU, UE, terminal, base station, RNC, or any host computer.

[0200] Variations of the methods, devices, and systems provided above are possible without departing from the scope of the present invention. In view of the various embodiments that may be applied, it should be understood that the illustrated embodiments are merely examples and should not be considered to limit the scope of the following claims. For example, the embodiments provided herein include handheld devices that may include or be used with any suitable voltage source (such as a battery, etc.) that provides any suitable voltage.

[0201] In addition, in the embodiments provided above, processing platforms, computing systems, controllers and other devices including processors are indicated. These devices may include at least one central processing unit ("CPU") and memory. According to the practice of those skilled in the art of computer programming, references to the symbolic representations of actions and operations or instructions may be performed by various CPUs and memories. Such actions and operations or instructions may be referred to as being "executed", "computer executed" or "CPU executed".

[0202] Those of ordinary skill in the art will appreciate that the actions and symbolic representations of operations or instructions include manipulation of electrical signals by the CPU. The electrical system represents data bits, which may result in the ultimate transformation of electrical signals or reduction of electrical signals and the retention of data bits at memory locations in the memory system, thereby reconfiguring or otherwise changing the operation of the CPU and performing other processing of signals. The memory location that holds the data bits is a physical location that has specific electrical, magnetic, optical, or organic properties that correspond to or represent the data bits. It should be understood that the embodiments are not limited to the above-mentioned platforms or CPUs, and other platforms and CPUs may also support the provided methods.

[0203] The data bits may also be maintained on computer-readable media, including magnetic disks, optical disks, and any other volatile (e.g., random access memory ("RAM")) or non-volatile (e.g., read-only memory ("ROM")) mass storage system readable by the CPU. The computer-readable media may include cooperating or interconnected computer-readable media that reside solely on the processing system or distributed across multiple interconnected processing systems that may be local or remote relative to the processing system. It should be understood that the embodiments are not limited to the above-mentioned memories, and other platforms and memories may also support the provided methods.

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

[0205] There is little difference between hardware implementation and software implementation of various aspects of the system. The use of hardware or software is usually (but not always, because in some contexts, the choice between hardware and software may become important) a design choice that represents a trade-off between cost and efficiency. There may be various media (e.g., hardware, software, and / or firmware) that can implement the processes and / or systems and / or other technologies described herein, and the preferred media may vary with the context of the deployment process and / or system and / or other technologies. For example, if the implementer determines that speed and accuracy are most important, the implementer may choose a media that is primarily hardware and / or firmware. If flexibility is most important, the implementer may choose a specific implementation that is primarily software. Alternatively, the implementer may choose some combination of hardware, software, and / or firmware.

[0206] The above detailed description has listed various embodiments of the device and / or process by using block diagrams, flow charts and / or examples. In the case where such block diagrams, flow charts and / or examples include one or more functions and / or operations, it should be understood by those skilled in the art that each function and / or operation within such block diagrams, flow charts or examples can be implemented individually and / or collectively by a wide range of hardware, software, firmware or almost any combination thereof. In one embodiment, several parts of the subject matter described herein can be implemented via application specific integrated circuits (ASICs), field programmable gate arrays (FPGAs), digital signal processors (DSPs) and / or other integrated formats. However, those skilled in the art will recognize that some aspects of the embodiments disclosed herein can be equivalently implemented in integrated circuits as a whole or in part as one or more computer programs running on one or more computers (e.g., one or more programs running on one or more computer systems), one or more programs running on one or more processors (e.g., one or more programs running on one or more microprocessors), firmware or almost any combination thereof, and according to the present disclosure, designing circuits and / or writing software and / or firmware codes will be completely within the technical scope of those skilled in the art. Furthermore, those skilled in the art will appreciate that the mechanisms of the subject matter described herein can be distributed as a program product in a variety of forms, and that the illustrative embodiments of the subject matter described herein apply regardless of the specific type of signal-bearing medium used to actually perform the distribution. Examples of signal-bearing media include, but are not limited to, the following: recordable type media (such as floppy disks, hard drives, CDs, DVDs, digital tapes, computer memory, etc.); and transmission type media (such as digital and / or analog communication media (e.g., fiber optic cables, waveguides, wired communication links, wireless communication links, etc.)).

[0207] Those skilled in the art will recognize that it is common in the art to describe devices and / or processes in the manner set forth herein, and thereafter use engineering practices to integrate such described devices and / or processes into a data processing system. That is, at least a portion of the devices and / or processes described herein can be integrated into a data processing system via a reasonable amount of experimentation. Those skilled in the art will recognize that a typical data processing system generally may include one or more of the following: a system unit housing; a video display device; a memory, such as a volatile memory and a non-volatile memory; a processor, such as a microprocessor and a digital signal processor; a computing entity, such as an operating system, a driver, a graphical user interface, and an application; one or more interactive devices, such as a touch pad or a screen; and / or a control system, including a feedback loop and a control motor (e.g., a feedback for sensing position and / or velocity, a control motor for moving and / or adjusting components and / or quantities). A typical data processing system may be implemented using any suitable commercially available components, such as those typically found in data computing / communication and / or network computing / communication systems.

[0208] The subject matter described herein sometimes illustrates different components included in or connected to different other components. It should be understood that such depicted architectures are merely examples, and in fact many other architectures that achieve the same functionality can be realized. In a conceptual sense, any arrangement of components that achieve the same functionality is effectively "associated" so that the desired functionality can be achieved. Therefore, any two components that are combined to achieve a specific functionality in this article can be considered to be "associated" with each other so that the desired functionality is achieved, regardless of the architecture or intermediate components. Similarly, any two components so associated can also be considered to be "operably connected" or "operably coupled" to each other to achieve the desired functionality, and any two components that can be so associated can also be considered to be "operably coupleable" to each other to achieve the desired functionality. Specific examples of operable coupling include, but are not limited to, components that can physically cooperate and / or physically interact and / or components that can wirelessly interact and / or wirelessly interact and / or components that can logically interact and / or components that can logically interact.

[0209] With respect to substantially any plural and / or singular terms used herein, those skilled in the art may translate from the plural to the singular and / or from the singular to the plural as appropriate, as appropriate to the context and / or application. For clarity, various singular / plural arrangements may be explicitly listed herein.

[0210] It will be understood by those skilled in the art that, in general, the terms used herein, and particularly in the appended claims (e.g., the bodies of the appended claims), are generally intended to be "open" terms (e.g., the term "including" should be interpreted as "including but not limited to", the term "having" should be interpreted as "having at least", the term "comprising" should be interpreted as "including but not limited to", etc.). It will also be understood by those skilled in the art that if a specific number of an introduced claim recitation is intended, such intent will be explicitly stated in the claim, and in the absence of such a recitation, there is no such intent. For example, where only one item is intended, the term "single" or similar language may be used. To aid understanding, the following appended claims and / or the description herein may include the use of the introductory phrases "at least one" and "one or more" to introduce claim recitations. However, the use of such phrases should not be construed as implying that any particular claim including such introduced claim recitations is limited to an embodiment including only one such recitation by the indefinite article "a" or "an" to introduce the claim recitation. This is true even when the same claim includes the introductory phrases "one or more" or "at least one" and an indefinite article such as "a" or "a kind" (e.g., "a" and / or "a kind" should be interpreted as meaning "at least one" or "one or more"). The same applies to the use of definite articles used to introduce claim recitations. In addition, even if a specific number of introduced claim recitations is explicitly recited, one skilled in the art will recognize that such recitation should be interpreted as meaning at least the stated number (e.g., a bare recitation of "two recitations" without other modifiers means at least two recitations or two or more recitations). In addition, in those instances where a convention similar to "at least one of A, B, and C, etc." is used, generally speaking, the meaning of such construction is that one skilled in the art will understand the convention (e.g., "a system having at least one of A, B, and C" will include, but is not limited to, a system having A alone, B alone, C alone, A and B simultaneously, A and C simultaneously, B and C simultaneously, and / or A, B, and C simultaneously, etc.). In those instances where a convention similar to "at least one of A, B, or C, etc." is used, generally speaking, the meaning of such construction is that one skilled in the art will understand the convention (e.g., "a system having at least one of A, B, or C" will include, but is not limited to, systems having A alone, B alone, C alone, A and B together, A and C together, B and C together, and / or A, B, and C together, etc.). One skilled in the art will also understand that, in fact, any discrete words and / or phrases presenting two or more alternative terms, whether in the specification, claims, or drawings, should be understood to contemplate the possibility of including one of the terms, any of the terms, or both of the terms.For example, the phrase "A or B" will be understood to include the possibilities of "A" or "B" or "A and B." Additionally, as used herein, the term "any of" followed by a listing of multiple items and / or multiple categories of items is intended to include "any of," "any combination," "any multiples," and / or "any combination of multiples" of the items and / or categories of items, either alone or in combination with other items and / or other categories of items. Additionally, as used herein, the term "set" is intended to include any number of items, including zero. Additionally, as used herein, the term "quantity" is intended to include any quantity, including zero. And, as used herein, the term "plurality" is intended to be synonymous with "multiple."

[0211] In addition, where features or aspects of the disclosure are described in terms of Markush groups, those skilled in the art will recognize that the disclosure is also described in terms of any individual member or subgroup of members of the Markush group.

[0212] As will be understood by those skilled in the art, for any and all purposes (such as for providing a written description), all ranges disclosed herein also encompass any and all possible subranges and combinations of their subranges. Any listed range can be easily identified as fully describing and enabling the same range to be divided into at least equal halves, thirds, quarters, fifths, tenths, etc. As a non-limiting example, each range discussed herein can be easily divided into a lower third, a middle third, and an upper third, etc. As will be understood by those skilled in the art, all languages ​​such as "up to", "at least", "greater than", "less than", etc. include the cited numbers and refer to ranges that can subsequently be divided into subranges as described above. Finally, as will be understood by those skilled in the art, ranges include each individual number. Thus, for example, a group having 1 to 3 units refers to a group having 1, 2, or 3 units. Similarly, a group having 1 to 5 units refers to a group having 1, 2, 3, 4, or 5 units, etc.

[0213] Furthermore, the claims should not be read as limited to the order or elements presented unless otherwise stated. Furthermore, the use of the term "means for..." in any claim is intended to invoke 35 U.S.C. § 112, 6 or means-plus-function claim format, and any claim without the term "means for..." is not intended to be so.

Claims

1. A network element, comprising a processor and a transmitter and a receiver, the transmitter and the receiver being operatively coupled to the processor, the processor being configured to: transmitting, to a first network element of a first domain network, a first request message requesting one or more tracks towards a second domain network, the first request message indicating a requested quality of service QoS; receiving a response message from the first network element, the response message indicating: (i) one or more second network elements of the second domain network, the one or more second network elements interconnecting the first domain network with the second domain network; and (ii) QoS partitioning of the requested QoS to be applied to the first domain network and the second domain network; transmitting, to the one or more second network elements of the second domain network, one or more second request messages requesting establishment of a communication channel across the first domain network and the second domain network, the one or more second request messages indicating the QoS partition to be monitored on the first domain network and the second domain network via the communication channel; as well as An acknowledgement is received from the one or more second network elements of the second domain network indicating that the communication channel has been established.

2. The network element of claim 1 , wherein the requested QoS is divided into a first QoS budget and a second QoS budget, such that the requested QoS is met under the condition that the first QoS budget is reached on the first domain network and under the condition that the second QoS budget is reached on the second domain network.

3. The network element of claim 2, wherein any of the requested QoS, the first QoS budget, and the second QoS budget comprises at least one QoS metric indicating any of bounded latency, guaranteed bandwidth, bounded jitter, bounded reliability ratio, and availability ratio.

4. The network element according to any one of claims 1 to 3, wherein the processor is further configured to: receive one or more network management messages including network management information in order to monitor QoS in the first domain network.

5. The network element according to claims 2 and 4, wherein the processor is further configured to: perform sub-track selection in the one or more tracks based on the network management information so that the first QoS budget is achieved on the first domain network.

6. The network element according to any one of claims 2 to 5, wherein, when the first QoS budget is not reached on the first domain network, the processor is further configured to: transmit a third request message to the first network element of the first domain network to request recalculation of the one or more tracks and / or adjustment of the QoS partitioning.

7. A network element according to any one of claims 1 to 6, wherein the processor is further configured to: before transmitting the first request message, receive an initial request message from a first wireless transmit / receive unit WTRU of the first domain network, wherein the initial request message includes information requesting to establish connectivity with a second WTRU of the second domain network with the requested QoS.

8. The network element according to any one of claims 1 to 7, wherein the processor is further configured to: before transmitting the first request message, receive first information from at least one second network element of the one or more second network elements of the second domain network, wherein the first information indicates that the at least one second network element of the one or more second network elements is within the radio coverage range of the network element.

9. The network element of claim 8, wherein the first information indicates any one of: a first identifier identifying at least one of the one or more second network elements; a second identifier identifying the second domain network; and an Internet Protocol (IP) prefix of a network element of the second domain network.

10. The network element according to any one of claims 8 to 9, wherein the processor is further configured to: transmit second information to the first network element of the first domain network, wherein the second information indicates that the at least one second network element of the one or more second network elements exists within the radio coverage range of the network element.

11. The network element according to any one of claims 1 to 10, wherein the processor is further configured to: receive third information from the first network element of the first domain network, wherein the third information indicates one or more links to be established between the network element and the one or more second network elements for interconnecting the first domain network with the second domain network.

12. The network element according to any one of claims 1 to 11, wherein when the network element is not within the coverage of the one or more second network elements, the processor is further configured to: transmit fourth information to the first network element of the first domain network, wherein the fourth information indicates that there is no connectivity between the first domain network and the second domain network.

13. The network element according to any one of claims 1 to 12, wherein the network element and the one or more second network elements are path selection network elements configured to perform sub-track selection on a per one or more packet basis.

14. The network element according to any one of claims 1 to 13, wherein the first network element is a path computation network element.

15. A method implemented in a network element, the method comprising: transmitting, to a first network element of a first domain network, a first request message requesting one or more tracks towards a second domain network, the first request message indicating a requested quality of service QoS; receiving a response message from the first network element, the response message indicating: (i) one or more second network elements of the second domain network, the one or more second network elements interconnecting the first domain network with the second domain network; and (ii) QoS partitioning of the requested QoS to be applied to the first domain network and the second domain network; transmitting, to the one or more second network elements of the second domain network, one or more second request messages requesting establishment of a communication channel across the first domain network and the second domain network, the one or more second request messages indicating the QoS partition to be monitored on the first domain network and the second domain network via the communication channel; as well as An acknowledgement is received from the one or more second network elements of the second domain network indicating that the communication channel has been established.

16. The method of claim 15, wherein the requested QoS is divided into a first QoS budget and a second QoS budget, so that the requested QoS is met under the condition that the first QoS budget is reached on the first domain network and under the condition that the second QoS budget is reached on the second domain network.

17. The method of claim 16, wherein any of the requested QoS, the first QoS budget, and the second QoS budget comprises at least one QoS metric indicating any of bounded latency, guaranteed bandwidth, bounded jitter, bounded reliability ratio, and availability ratio.

18. The method according to any one of claims 15 to 17, further comprising: One or more network management messages including network management information are received to monitor QoS in the first domain network.

19. The method according to claims 16 and 18, further comprising: Sub-track selection is performed among the one or more tracks based on the network management information such that the first QoS budget is achieved on the first domain network.

20. The method according to any one of claims 16 to 19, further comprising: In case the first QoS budget is not reached on the first domain network, a third request message is transmitted to the first network element of the first domain network to request a recalculation of the one or more tracks and / or an adjustment of the QoS partitioning.