Apparatus, methods and computer programs
Patent Information
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Filing Date
- 2026-02-14
- Publication Date
- 2026-08-14
Smart Images
Figure CN122579248A_ABST
Abstract
Description
Technical Field
[0001] The various embodiments of this disclosure relate to methods, apparatuses, and computer programs, and more particularly (but not limited to) to apparatuses, methods, and computer programs related to Wireless Access and Backhaul (WAB). Background Technology
[0002] A communication network can be viewed as a facility that enables communication between two or more communication devices, or provides data network access capabilities to communication devices. Mobile or wireless communication networks are one example of a communication network, where application servers can provide services to communication devices.
[0003] Such communication networks operate according to standards such as those provided by the 3rd Generation Partnership Project (3GPP) or the European Telecommunications Standards Institute (ETSI). Examples of standards include the so-called fifth-generation (5G) and sixth-generation (6G) standards released by 3GPP. Summary of the Invention
[0004] Some embodiments of this disclosure will be described in conjunction with certain aspects. These aspects are not intended to identify key or essential features of the embodiments of this disclosure, nor are they intended to limit its scope of protection. Other features, aspects, and elements will be readily apparent to those skilled in the art in conjunction with the content of this disclosure.
[0005] According to a first aspect, a method is provided, comprising: receiving information about the quality of service (QoS) of a wireless access and backhaul mobile terminal (WAB-MT) for a WAB node, the information including information about the QoS of the backhaul link of the WAB-MT; using the QoS information regarding one or more packet data unit (PDU) sessions between the device and a network via the backhaul link; and sending the information about the one or more PDU sessions and the QoS information to a network entity.
[0006] The method may include: determining, based on information about quality of service, that the quality of service for one or more current PDU sessions of the device cannot be satisfied, and the information sent to the network regarding the one or more PDU sessions includes: a request to release the quality of service for the one or more current PDU sessions for which it cannot be satisfied.
[0007] The method may include: determining, based on information about quality of service, that the quality of service for one or more current PDU sessions of the aforementioned device cannot be satisfied, and determining, based on information about quality of service, that one or more current PDU sessions will be modified, and the information about the one or more PDU sessions sent to the aforementioned network includes: a request for modifying the one or more current PDU sessions to be modified.
[0008] The method may include: determining, based on information about quality of service, that one or more PDU sessions will be established, and sending information about one or more packet data unit sessions to the network, including: a request for establishing one or more current PDU sessions to be established.
[0009] The method may include: avoiding requests for PDU sessions that are associated with a higher quality of service than indicated by information about quality of service.
[0010] Information about Quality of Service (QoS) includes one or more of the following: maximum QoS; best available QoS; one or more QoS stream identifiers; guaranteed bit rate; minimum latency and maximum bit rate.
[0011] This method can be performed by a device, which can be a user equipment or can be provided in a user equipment.
[0012] The apparatus may include one or more components for performing the methods described above.
[0013] The device may include at least one processor and at least one memory storing instructions that, when executed by the at least one processor, cause the device to perform at least any of the methods in the first aspect.
[0014] According to the second aspect, a method is provided, comprising: determining that a user equipment (UE) is a radio access and backhaul mobile terminal (WAB-MT) of a WAB node; requesting information about the quality of service (QoS) for the backhaul link from a session management function (SMF) for the WAB-MT; receiving the requested QoS information about the backhaul link from the SMF; and providing the QoS information about the backhaul link to the WAB-MT.
[0015] The information regarding the quality of service (QoS) used for the backhaul link includes one or more of the following: maximum QoS; best available QoS; one or more QoS flow identifiers; guaranteed bit rate; minimum latency and maximum bit rate.
[0016] The method may include determining, based on one or more attributes of a base station serving a WAB-MT associated with the backhaul link, information regarding the quality of service for the backhaul link will be utilized.
[0017] One or more attributes of the base station include one or more of the following: a first interface between the base station and a WAB-MT having a non-terrestrial network NTN link; or a second interface between the base station and a device having an NTN link.
[0018] The method may include: receiving information indicating that the WAB-MT will be switched from the first backhaul base station to the second backhaul base station, and wherein the component is configured to: request information regarding the quality of service for the backhaul link associated with the second backhaul base station.
[0019] The first backhaul base station may include either a terrestrial base station or a non-terrestrial base station, and the aforementioned second backhaul base station may include either a terrestrial base station or a non-terrestrial base station.
[0020] This method can be performed by a device, which may be an access and mobility management function entity or provide access and mobility management functions.
[0021] The apparatus may include one or more components for performing the methods described above.
[0022] The device may include at least one processor and at least one memory storing instructions for access and mobility management functions, which, when executed by the at least one processor, cause the device to perform at least any of the methods of the second aspect.
[0023] According to a third aspect, a method is provided, comprising: receiving information about the quality of service (QoS) of a wireless access and backhaul mobile terminal (WAB-MT) for a WAB node, the information including information about the QoS of the backhaul link of the WAB-MT; and sending the QoS information to a network entity.
[0024] A network entity includes one of the following: a network entity that provides policy control functions for a user equipment (UE); or a network entity that provides session management functions for a UE that has a connection to the network via a backhaul link.
[0025] This method can be performed by a device.
[0026] The device may be an access and mobility management function entity, or provide access and mobility management functions.
[0027] The device can be a session management function entity, or provide session management functions.
[0028] The apparatus may include one or more components for performing the methods described above.
[0029] The device may include at least one processor and at least one memory storing instructions for access and mobility management functions, which, when executed by the at least one processor, cause the device to perform at least any of the methods of the third aspect.
[0030] The device may include at least one processor and at least one memory storing instructions for session management functions, which, when executed by the at least one processor, cause the device to perform at least any of the methods in the third aspect.
[0031] According to the fourth aspect, a method is provided, comprising: receiving information about the quality of service (QoS) of a wireless access and backhaul mobile terminal (WAB-MT) for a WAB node, the information including information about the QoS of the backhaul link of the WAB-MT; determining, based on the QoS information, that a connection between a user equipment (UE) and a network via the backhaul link is associated with a QoS limitation; and, based on the determination that a QoS limitation exists, causing modification or removal of one or more PDU sessions supported by the connection.
[0032] This method can be performed by a device.
[0033] The device can be a session management function entity, or provide session management functions.
[0034] The apparatus may include one or more components for performing the methods described above.
[0035] The device may include at least one processor and at least one memory storing instructions for session management functions, which, when executed by the at least one processor, cause the device to perform at least any of the methods in the fourth aspect.
[0036] According to the fifth aspect, a method is provided, comprising: receiving information about the quality of service (QoS) of a wireless access and backhaul mobile terminal (WAB-MT) for a WAB node, the information including information about the QoS of the backhaul link of the WAB-MT; and providing one or more policies to a user equipment having a connection to a network via the backhaul link based on the QoS information.
[0037] This method can be performed by a device.
[0038] The device can be a policy control function entity, or provide policy control functions.
[0039] The apparatus may include one or more components for performing the methods described above.
[0040] The device may include at least one processor and at least one memory storing instructions for policy control functions, which, when executed by the at least one processor, cause the device to perform at least any of the methods in the fifth aspect.
[0041] According to another aspect, a computer-readable medium is provided that stores program instructions thereon for performing at least one of the methods described above.
[0042] According to one aspect, a non-transitory computer-readable medium is provided, on which program instructions are stored for performing at least one of the methods described above.
[0043] According to one aspect, a non-volatile tangible storage medium is provided, on which program instructions are stored, the program instructions being used to perform at least one of the methods described above.
[0044] The above text has described several different aspects. It should be understood that combining any two or more of these aspects can yield more implementation details.
[0045] Other aspects will also be described in the detailed embodiments and claims below. Attached Figure Description
[0046] Some embodiments will now be described by way of non-limiting and illustrative example only, with reference to the accompanying drawings, in which:
[0047] Figure 1 An example of a communication network to which the examples disclosed herein can be applied is shown;
[0048] Figure 2 This is a schematic representation of a communication system, such as a 5G communication system (5GS).
[0049] Figure 3 The illustration schematically shows user equipment connected to the core network via satellite;
[0050] Figure 4a The WAB architecture is illustrated schematically.
[0051] Figure 4b The user plane protocol stack used in the WAB architecture is illustrated schematically.
[0052] Figure 5a The first flow of some embodiments is shown;
[0053] Figure 5b The second process of some embodiments is shown;
[0054] Figures 6a-6c The third process of some embodiments is shown;
[0055] Figure 7 A first method of some embodiments is shown;
[0056] Figure 8 A second method is shown in some embodiments;
[0057] Figure 9 A third method is shown in some embodiments;
[0058] Figure 10 A fourth method is shown in some embodiments;
[0059] Figure 11 A fifth method is shown in some embodiments; and
[0060] Figure 12 An example of a device is shown. Detailed Implementation
[0061] The following embodiments are provided by way of non-limiting and illustrative examples. Although the term "a," "one," or "some" embodiments may be referenced in several places herein, this does not necessarily mean that the same embodiment is referred to every time, or that a particular feature applies only to a single embodiment. Individual features (or corresponding portions thereof) of different embodiments may also be combined to provide other embodiments. Furthermore, when a particular feature, structure, or characteristic is described in connection with embodiments, it is intended that such feature, structure, or characteristic may be applied in combination with other embodiments (whether explicitly described or not).
[0062] It should be understood that although the terms "first," "second," etc., may be used in this document to describe various elements, these elements should not be limited by these terms. These terms are only used to distinguish one element from another.
[0063] As used herein, the phrases “at least one of A or B,” “at least one of A and B,” and “A and / or B” mean (A), (B), or (A and B). Similarly, the phrase “A, B, and / or C” means (A), (B), (C), (A and B), (A and C), (B and C), or (A, B, and C).
[0064] As used herein, the term “or” means non-exclusive “or” unless otherwise specified (e.g., using “or other “or” or in alternatives”).
[0065] As used herein and unless explicitly stated otherwise, “responding to A” to perform a corresponding feature, step, or function does not mean that the corresponding feature, step, or function is performed immediately after “A” appears, because one or more intervening features, steps, or functions may be performed (at least partially) between the appearance of the corresponding feature, step, or function and “A”. Similarly, “based on A” to perform a corresponding feature, step, or function does not mean that the corresponding feature, step, or function is performed solely based on “A”, because the corresponding feature, step, or function may be based on one or more other features, steps, or functions in addition to “A”. The embodiments described herein can be implemented in communication networks, such as any of the following radio access technologies (RATs): worldwide interoperability for microwave access (WiMAX), global system for mobile communications (GSM, 2G), GSM EDGE radio access network (GERAN), general packet radio service (GPRS), universal mobile telecommunication system (UMTS, 3G) based on wideband-code division multiple access (W-CDMA), high-speed packet access (HSPA), long term evolution (LTE), advanced LTE and enhanced LTE (eLTE), 5G (also known as NR), 6G or above.Furthermore, communications within the communication network may utilize any suitable wireless communication technology, including but not limited to: code division multiple access (CDMA), frequency division multiple access (FDMA), time division multiple access (TDMA), frequency division duplex (FDD), time division duplex (TDD), multiple-input multiple-output (MIMO), orthogonal frequency division multiple (OFDM), and / or discrete fourier transform spread OFDM (DFT-s-OFDM). As used herein, references to user equipment (UE) should be understood as references to any suitable terminal equipment.
[0066] The term "terminal device" refers to any terminal device capable of wireless communication. As a non-limiting and illustrative example, a terminal device may be referred to as a communication device, UE, subscriber station (SS), or mobile station (MS). Terminal devices can include mobile phones, cellular phones, smartphones, Voice over IP (VoIP) phones, wireless local loop phones, tablets, wearable terminal devices, personal digital assistants (PDAs), portable computers, desktop computers, image capture terminal devices such as digital cameras, gaming terminal devices, music storage and playback devices, in-vehicle wireless terminal devices, USB dongles, Internet of Things (IoT) devices, watches, or other wearable smart glasses. Other examples include goggles, smart headsets, smart earphones, smart necklaces, smart earrings, head-mounted displays (HMDs), vehicles, targets, medical devices and applications (e.g., remote surgery), industrial devices and applications (e.g., robots and / or other wireless devices operating in industrial and / or automated processing chain environments), consumer electronics devices, devices operating on commercial and / or industrial wireless networks, etc.
[0067] Figure 1An example of a communication network that can be applied to the publicly disclosed examples is shown. The communication network or cellular communication network may include a network node 110 configured to provide one or more cells (e.g., cell 100), and a network node 112 configured to provide one or more other cells (e.g., cell 102). For example, each cell may be, for example, a macrocell, microcell, femtocell, or picocell. A cell may define the coverage area or service area of the corresponding node.
[0068] Network node 110 can provide radio access to a communication network to user equipment (UE) 120 (one or more UEs). Radio access may include downlink (DL) communication from the network node to UE 120 and uplink (UL) communication from UE 120 to the network node. Examples of uplink channels include a Physical Uplink Control Channel (PUCCH) for transmitting control information and a Physical Uplink Shared Channel (PUSCH) for transmitting data to the network. Examples of downlink channels include a Physical Downlink Control Channel (PDCCH) for transmitting control information and a Physical Downlink Shared Channel (PDSCH) for transmitting data to the user equipment.
[0069] The system can have multiple UEs 120 and 122. Each UE among the multiple UEs 120 and 122 can be served by the same or different network nodes 110 and 112. UEs can be configured with dual connectivity (DC), where a UE (e.g., UE 120) can connect to multiple network nodes 110 and 112. UEs 120 and 122 can communicate with each other by establishing a device-to-device (D2D) communication interface between UEs 120 and 122 via a so-called "side link" (SL). Such D2D communication can be referred to as, for example, machine-to-machine, peer-to-peer (P2P) communication, or vehicle-to-vehicle (V2V) communication.
[0070] In a communication network with multiple network nodes, these nodes can connect to each other via interfaces. The LTE specification refers to this interface as the X2 interface. The interface between an LTE node and a 5G node, or between two 5G nodes, can be called the Xn interface.
[0071] Network nodes 110 and 112 can also be connected to the core network 202 of the communication network via another interface.
[0072] For example, the LTE specification designates the core network as the Evolved Packet Core (EPC), and the core network may include, for example, a Mobility Management Entity (MME) and gateway nodes. The MME can handle the mobility of terminal devices in a tracking area comprising multiple cells and handle signaling connections between the terminal devices and the core network. Gateway nodes can handle data routing within the core network as well as data routing to / from terminal devices.
[0073] For example, the 5G specification designates the core network as the 5G Core (5GC). The 5G Core can include, for example, Access and Mobility Management Functions (AMF) and User Plane Functions / Gateways (UPF), as well as other functions. AMF can handle the termination of Non-Access Stratum (NAS) signaling, NAS encryption and integrity protection, registration management, connection management, mobility management, access authentication and authorization, and security context management. For example, UPF nodes can support packet routing and forwarding, packet inspection, and Quality of Service (QoS) processing.
[0074] Figure 2 A schematic diagram of a communication system, such as a 5G communication system (5GS), is shown. The 5GS may include a User Equipment (UE) 120, a 5G core network (5GC) 202, and one or more application functions. The UE may connect to the 5GC via a network node 110 (e.g., a radio access node) of the radio access network. Application functions (AFs) may be deployed as trusted application functions in the 5GS, or as hosts on one or more application servers of a data network (DN) 204. Such AFs may be untrusted application functions. The 5GS may be configured to connect the UE to the data network, the access network, and the 5GC 202 (e.g., a UPF of the 5GC).
[0075] 5GC may include the following network functions: network slice selection function (NSSF); network exposure function (NEF); network repository function (NRF); policy control function (PCF); unified data management (UDM); application function (AF); authentication server function (AUSF); access and mobility management function (AMF); session management function (SMF); network data analytics function (NWDAF); and / or user plane function (UPF).
[0076] Figure 2It also illustrates various interfaces (e.g., N1, N2, etc.) that can be implemented between system components. Not all of the aforementioned network functional entities are included. Figure 2 As shown in the figure, some examples of 5GC may include other network function entities and interfaces besides those mentioned above.
[0077] AMF can be configured to handle non-access stratum (NAS) signaling termination, NAS encryption and integrity protection, registration management, connection management, mobility management, access authentication and authorization, and / or security context management. UPF can support, for example, packet routing and forwarding and / or packet detection, as well as Quality of Service (QoS) processing.
[0078] refer to Figure 3 This illustrates an example where UE 120 connects to core network 202 via satellite 110'. UE 120 connects to relay station 302, which in turn connects to satellite 110', which acts as a base station. In another deployment configuration, the NG interface between the base station and the core network can be implemented via a satellite link.
[0079] Some embodiments relate to architectures with Wireless Access and Backhaul (WAB). (See references) Figure 4a This illustrates an example of a WAB architecture. When UE 120 connects to the network, it can establish a UE PDU session 400 with the core network. This PDU session is established between UE 120 and the core network's UPF 402. In the WAB architecture, this UPF connected to the user equipment is referred to as UE UPF 402 or UPF (UE) 402. The UPF can be combined as follows... Figure 2 As described.
[0080] WAB node 406 is configured. WAB nodes can be considered as relay nodes. WAB nodes include WAB-gNB 408 and WAB-MT 410 (WAB mobile terminal, sometimes also called WAB-UE).
[0081] The backhaul (BH) connection 412 for the WAB-gNB is provided by the PDU session established for the WAB-MT to the core network serving the UE. The WAB-gNB 408 provides radio connectivity to the UE 120 for the NR backhaul (BH) 412. The NG interface of the WAB-gNB (both control plane and user plane) is transparently forwarded through the serving network of the WAB-MT.
[0082] The BH connection used for the WAB-gNB will be implemented via the backhaul gNB 414 and the UPF416 of the core network that provides services for the BH connection. The backhaul gNB is sometimes also referred to as the donor gNB.
[0083] For a UE connected to WAB-gNB 408 on WAB node 406, the WAB cell is the same as a non-WAB cell. The UE can use the same signaling procedure as when connecting to a non-WAB-gNB to establish a PDU session to the UE core network. Therefore, WAB deployment is transparent to the UE.
[0084] The WAB-MT 410 has a wireless connection 420 to the gNB 414 for backhaul.
[0085] The backhaul gNB 414 can have a connection 422 with the core network AMF 418.
[0086] An example of a WAB node is a vehicular repeater (VMR).
[0087] The network providing services to UEs and WAB nodes may be the same as or different from the network providing services to backhaul gNBs.
[0088] refer to Figure 4b It shows the user plane protocol stack used in the WAB architecture.
[0089] UE 120 has a PDU session 400, which is transmitted through the SDAP layer, PDCP layer, RLC layer, MAC layer, and PHY layer. The PDU session is mapped to the corresponding PDU session of UPF 402 that provides services to the UE.
[0090] The WAB-gNB 408 has SDAP, PDCP, RLC, MAC, and PHY layers. The SDAP, PDCP, RLC, MAC, and PHY layers of the UE are mapped to the SDAP, PDCP, RLC, MAC, and PHY layers of the WAB-gNB, respectively.
[0091] WAB-MT has a GTP-U layer, a UDP layer, an IP layer, an SDAP layer, a PDCP layer, an RLC layer, a MAC layer, and a PHY layer. The GTP-U layer, UDP layer, and IP layer can be mapped to the corresponding layers in UPF 402 that provide services to the UE.
[0092] The backhaul gNB 414 has corresponding layer mappings to the SDAP, PDCP, RLC, MAC, and PHY layers of the WAB-MT 410. The backhaul gNB also has corresponding GTP-U, UDP, IP, and L1 / L2 layers mapped to the UPF that provides services to the WAB.
[0093] The UPF 416 that provides services to WAB 406 also has an L1 / L2 layer that maps to the corresponding L1 / L2 layer of the UPF that provides services to the UE.
[0094] In non-WAB systems, gNB backhaul is typically not a bottleneck, and compared to the resources between the UE and gNB, backhaul usually has no resource limitations. Generally, the connection between the UE and gNB is considered a limiting factor for the number of supported PDU sessions or QoS flows. Therefore, no resource limitations related to backhaul need to be considered.
[0095] Some implementations address the potential resource constraints in backhaul within a WAB architecture. In some embodiments, the network may take into account the available Quality of Service (QoS) associated with backhaul. For example, the network may consider this QoS when initiating the establishment of a PDU / QoS flow for a UE.
[0096] In a WAB architecture, backhaul resources may be limited due to limited resources between the WAB-MT and BH-gNB, or for example, latency between the BH-gNB and the AMF / UPF. Resources between the WAB-MT and BH-gNB can be used by all UEs connected to the WAB-gNB and / or non-UE-related processes of the WAB-gNB. These resources may be radio resources. In some embodiments, the core network initiates a PDU session / QoS flow for the UE when it is aware of the available QoS related to backhaul. This avoids unnecessary setup procedures.
[0097] Taking the WAB node as an example of VMR, when the UE moves between different wireless coverage areas with the vehicle, the WAB-MT will switch the access network node (backhaul access node). Different access network nodes may have different access capabilities. For example, different access nodes may be associated with different bandwidths, different radio access technologies (RAT), etc. For example, the access node can be a terrestrial network TN node or a non-terrestrial network NTN node. NTN access nodes can be provided by satellite. TN nodes are located on the ground and are typically used in non-satellite-based networks. TN nodes are usually closer to the UE than NTN nodes.
[0098] Currently, the UEs and their serving networks are unaware of the type of backhaul link (e.g., satellite backhaul link) or changes in backhaul link type. Some implementations address the issue that backhaul changes may affect user experience due to different QoS supported by different backhaul links.
[0099] In some embodiments, backhaul-related Quality of Service (QoS) information is provided to the WAB node. This information is hereinafter referred to as QoS information. For example, the QoS information can provide information indicating which QoS level can be supported by the backhaul link. The AMF supporting WAB-MT provides QoS information to WAB-MT. This information can be provided via NAS signaling.
[0100] Quality of Service (QoS) information related to BH links can be applied to the link between WAB-MT and BH-gNB (e.g., the Uu link). QoS information related to BH links can also be applied to the link between BH-gNB and AMF. Furthermore, QoS information related to BH links can be applied to the link from WAB-MT to AMF or the entire connection.
[0101] Quality of Service (QoS) information may include the highest QoS for WAB-MT. QoS-related information may include the best available QoS for WAB-MT. QoS-related information may include the guaranteed bit rate (GBR) available for WAB-MT. QoS-related information may include the maximum bit rate (MBR) available for WAB-MT. QoS-related information may include one or more available QFIs for WAB-MT. QoS-related information may include minimum latency (e.g., the minimum latency that WAB-MT packets may face due to an NTN link). QoS-related information may include maximum latency (e.g., the maximum latency that WAB-MT packets may face due to an NTN link).
[0102] WAB-MT shares this service quality information with WAB-gNB.
[0103] The AMF can be triggered to provide quality of service information by determining the WAB-MT connection.
[0104] This trigger may depend on determining that the backhaul is achieved via satellite, such as via NG via satellite for BH-gNB or via Uu via satellite.
[0105] AMF can request SMF to provide QoS information.
[0106] WAB nodes can receive QoS information for WAB-MT, which can be coordinated with the network associated with WAB-gNB.
[0107] WAB-gNB can send QoS information to the AMF associated with the UE.
[0108] The AMF associated with the UE can send QoS information to the PCF.
[0109] Alternatively, the AMF associated with the UE can send QoS information to the SMF. The SMF then sends this QoS information to the PCF.
[0110] PCF can create one or more policies and / or modify one or more policies for the UE based on the QoS information received from WAB-MT.
[0111] As an alternative, the AMF associated with the UE can send QoS information to the SMF. Based on this QoS information, the SMF can modify or release PDU sessions or QoS flows for which QoS is not supported.
[0112] In other embodiments, the WAB-gNB provides QoS information to one or more UEs. The UE may consider reference QoS information related to the PDU session. The QoS information can provide information indicating what QoS(s)(s) can or cannot be provided through the connection between the WAB-MT and the BH-gNB.
[0113] For example, if the QoS required for a PDU session cannot be supported, the session can be released.
[0114] If the QoS used for a PDU session is not supported, the session can be modified based on this QoS information. The PDU session will be modified based on this QoS information to make the PDU session supported.
[0115] One or more PDU sessions can be established based on this QoS information. The established PDU sessions based on this QoS information can be supported.
[0116] Figure 5a The first example procedure is illustrated. In this example, the UE is switched to a gNB with NTN backhaul, meaning the NG interface has an NTN connection toward the core network entity. In other words, there is a satellite link between the BH base station and the core network.
[0117] As shown in Figure 1, the WAB-MT connects to the BH-gNB. In this example, the WAB-MT connects to the BH-gNB via a terrestrial backhaul. In some embodiments, this may be via an NG or 5G access network. In this way, a connection is established between the WAB-MT and the BH-gNB.
[0118] As shown in Figure 2, the UE connects to the WAB-gNB. In this way, a connection is established between the UE and the WAB-gNB.
[0119] In the process sections of references 3 to 5, a connection is established between the WAB-gNB and the return gNB. This connection can be an Xn connection.
[0120] As shown in Figure 3, the WAB-gNB sends a request to the backhaul gNB for a connection to be established. This request can be for an Xn connection. The connection request can be an Xn establishment request. The request for the connection to be established can include information related to the WAB-MT.
[0121] As shown in Figure 4, the return gNB sends a response to the WAB-gNB regarding the request to establish a connection. This response can be an Xn establishment response.
[0122] As shown in Figure 5, a connection is established between the WAB-gNB and the backhaul gNB. This can be an Xn connection. This connection can allow, enable, or otherwise facilitate the arrival of information indicating the common location of the WAB-MT and WAB-gNB by the backhaul gNB. Instead of the Xn information exchange described herein, other methods may exist that allow the BH-gNB to determine that it is serving the WAB-UE.
[0123] It should be noted that in some embodiments, the connection may have been previously established.
[0124] As shown in Figure 6, the WAB-MT sends a measurement report to the backhaul gNB. The measurement report may include measurements of one or more cells of the target backhaul gNB. In this example, the target backhaul gNB may be the NTN target backhaul gNB.
[0125] As shown in Figure 7, the BH-gNB determines that the WAB-MT will be switched to the target return gNB. This determination can be based on measurements received in the measurement report.
[0126] In the process section from 8 to 10, the switch from the return gNB to the target return gNB is completed.
[0127] As shown in Figure 8, the backhaul gNB sends a WAB-MT handover request to the target backhaul gNB.
[0128] As shown in Figure 9, the target backhaul gNB sends a handover command to the backhaul gNB. The handover command is then sent from the backhaul gNB to the WAB-MT.
[0129] As shown in Figure 10, the switch from the return gNB to the target return gNB is completed.
[0130] As shown in Figure 11, the target return gNB sends a path switching request to the AMF.
[0131] As shown in Figure 12, the AMF sends a path handover confirmation to the target backhaul gNB. This will perform a path handover to transfer the PDU session from the core network (e.g., UPF) to the target BH-gNB.
[0132] As shown in Figure 13, when the UE is a WAB-MT, the AMF determines that it will request QoS-related information from the SMF. For example, the determination of the QoS-related information to be requested is based on the AMF's determination that the UE is a WAB-MT. Alternatively, the AMF may determine the QoS-related information to be requested based on other information. For example, the AMF may determine the QoS-related information to be requested based on the backhaul of the target BH-gNB as the NTN link.
[0133] Information related to Quality of Service (QoS) may include the maximum QoS of WAB-MT. Information related to QoS may include the best available QoS for WAB-MT. Information related to QoS may include the guaranteed bit rate available for WAB-MT. Information related to QoS may include the maximum bit rate available for WAB-MT. Information related to QoS may include one or more available QFIs for WAB-MT. Information related to QoS may include minimum latency, such as the minimum latency that WAB-MT data packets may experience due to the NTN link. Information related to QoS may include maximum latency, such as the maximum latency that WAB-MT data packets may experience due to the NTN link.
[0134] As shown in Figure 14, the AMF sends a request for QoS information to the SMF. The AMF can specify which metrics to report. Alternatively, the SMF can determine which metrics to report. This request can be sent in `Nsmf_PDUSession_UpdateSMContextRequest`.
[0135] As shown in Figure 15, the SMF provides the AMF with a response containing the requested QoS information. The SMF can determine the requested QoS information. The SMF can provide information about one or more of the following: GBR, MBR, latency, one or more possible QFIs, etc. The response can be Nsmf_PDUSession_UpdateSMContextResponse.
[0136] As shown in Figure 16, NAS signaling is used to provide QoS information to WAB-MT via AMF.
[0137] As shown in Figure 17, WAB-MT provides QoS information to WAB-gNB.
[0138] It should be understood that in some embodiments, QoS information can be per-UE. In some embodiments, QoS information can be modified by the WAB-gNB, for example, based on the WAB-gNB's load or one or more other attributes. In other embodiments, QoS information is not modified by the WAB-gNB.
[0139] In one variant of this process, AMF can provide QoS information.
[0140] In one variation of this process, the AMF can provide QoS information to the target BH-gNB. For example, the AMF can provide QoS information to the target return gNB during path switching acknowledgments (see the section on the process referenced at 12). In this example, the sections on the process mentioned at 13-15 occur before the section on the process mentioned at 12. The QoS information can be modified by the target BH-gNB and / or forwarded to the WAB-MT.
[0141] Alternatively or concurrently, the WAB-gNB can be configured via OAM using a mapping of slices available for the WAB-MT. One or more slices can correspond to QoS information. For example, where the QoS information pertains to a maximum QoS, one or more slices will be associated with a QoS no greater than the maximum QoS.
[0142] It should be noted that, for example, when the WAB-MT is initially connected to the BHgNB, a similar procedure as shown can usually be followed. See Figure 5B.
[0143] As shown in Figure 1, the WAB-MT is connected to the BH-gNB. In this example, the WAB-MT is connected to the BH-gNB via a backhaul. In some embodiments, the backhaul may be provided by an NTN link.
[0144] As shown in Figure 2, WAB-MT sends a PDU establishment request to AMF via BH-gNB.
[0145] As shown in Figure 3, the UE is connected to the WAB-gNB.
[0146] As shown in Figure 4, when the UE is a WAB-MT, the AMF determines that it will request QoS information from the SMF. For example, the determination that QoS information will be requested is based on the AMF's determination that the UE is a WAB-MT. Additionally or alternatively, the AMF may determine that QoS information will be requested based on other information. For example, the AMF may determine that it needs to request information related to quality of service based on the backhaul of the BH-gNB as an NTN link.
[0147] As shown in Figure 5, the AMF sends a request for QoS information to the SMF. The AMF can specify which metrics to report. Alternatively, the SMF can determine which metrics to report. This request can be sent in `Nsmf_PDUSession_CreateSMContextRequest`.
[0148] As shown in Figure 6, the SMF provides the AMF with a response containing the requested QoS information. The SMF can determine the requested QoS information. This response can be Nsmf_PDUSession_createSMContextResponse.
[0149] As shown in Figure 7, the AMF sends a registration acceptance message to the WAB-MT. This message may include QoS information. This message can be a registration acceptance message. As shown in Figure 8, the WAB-MT provides QoS information to the WAB-gNB.
[0150] refer to Figures 6a to 6c It shows an example process that starts with receiving QoS information from a WAB-gNB.
[0151] As shown in Figure 1, the WAB-gNB receives QoS information. It can be combined with... Figure 5a or Figure 5b As described.
[0152] The following describes the first and second options for providing QoS information to the AMF that provides services to the UE.
[0153] In the first option, WAB-gNB provides QoS information to the core network.
[0154] As shown in Figure 2, the WAB-gNB sends a message to the core network (e.g., AMF). This message can be an NG or 5G message. It can be a configuration update. It can provide QoS information.
[0155] The second option will be described below.
[0156] As shown in Figure 3, the WAB-gNB provides QoS information to one or more UEs connected to the WAB-gNB. This can be achieved through dedicated signaling or broadcast signals. The WAB-gNB can identify a group of one or more UEs that may be affected by this QoS information. This identification can be based on one or more PDU sessions associated with the UE and the corresponding QoS associated with these one or more PDU sessions. For example, based on this QoS information, the required QoS for one or more PDU sessions can be compared with the supported QoS.
[0157] In other embodiments, different criteria may be used to selectively determine potentially affected UEs (based on the QoS associated with the UE's PDU session), or any other criteria may be used to select a group of affected UEs.
[0158] As shown in Figure 4, the UE can initiate the removal of PDU sessions / QoS flows whose QoS cannot be satisfied based on the received QoS information.
[0159] As shown in Figure 5, the UE can initiate one or more PDU sessions / QoS flows where the QoS can be satisfied based on the received QoS information.
[0160] In some processes, the executable process is one or both of sections 4 and 5.
[0161] Alternatively or concurrently, the UE may modify one or more existing PDU sessions based on the received QoS information to associate them with the new QoS.
[0162] The UE can consider the received QoS information in one or more future PDU session requests. For example, the UE can avoid requesting PDU sessions with higher QoS values based on the received QoS information.
[0163] As shown in Figure 6, the UE sends one or more requests to establish a PDU session, modify a PDU session, or release a PDU session as needed. The UE sends the request to the AMF supporting the UE. This request may include QoS information received from the WAB-gNB.
[0164] As shown in Figure 7, one or more PDU sessions are created, modified, and / or released. This is based on a request received from the UE.
[0165] After the AMF providing services to the UE has QoS information, three further options are available.
[0166] In the first further option, the AMF provides QoS information to the PCF.
[0167] As shown in Figure 8, the AMF can send QoS information to the PCF. This can be done in policy modification and / or policy establishment requests.
[0168] In the second further option, the SMF reports QoS information to the PCF.
[0169] As shown in Figure 9, the AMF can send QoS information to the SMF. This can occur during requests for PDU session establishment, modification, or release. It can also be a scenario where the second option of providing QoS information to the AMF serving the UE is used.
[0170] As shown in Figure 10, the SMF provides QoS information to the PCF. This can be done in policy modification and / or policy establishment requests.
[0171] As shown in 14, for any of the first and second further options described above, the PCF determines one or more new policies and / or modifies one or more policies based on QoS information. For example, the QoS of one or more UE data sessions can be changed.
[0172] As shown in 15, change the UE policy.
[0173] In the third further option, SMF performs operations based on the received QoS information.
[0174] As shown in Figure 11, the AMF sends QoS information to the SMF. This can occur during PDU session establishment, PDU session modification, or PDU session release requests. It can also be a scenario where the second option of providing QoS information to the AMF serving the UE is used.
[0175] As shown in Figure 12, the SMF determines that the UE establishes a connection through the WAB-gNB based on QoS information, and its backhaul to the gNB is subject to QoS restrictions.
[0176] As shown in 13, based on the determinations made in part 12 of the process, the SMF determines that one or more existing PDU sessions will be modified or removed.
[0177] In some embodiments, the QoS information provided by the WAB to the core network may take into account one or more other factors, such as the current capacity of the WAB-gNB based on, for example, load. This means that the WAB-gNB can modify the QoS information received from the WAB-MT.
[0178] In some embodiments, WAB-gNB may release a session or request a session modification based on QoS information.
[0179] In some embodiments, the UE may initiate PDU session modification or deletion based on, for example, an estimated understanding of the maximum QoS change based on the UE's quality of experience.
[0180] In a switching scenario, QoS information can indicate whether a better quality of service can be supported compared to the current session, or a worse quality of service can be supported compared to the current session.
[0181] Some implementations may allow, enable, or otherwise facilitate the modification, release, or establishment of UE sessions in response to changes in the BH link conditions of the WAB-MT. Therefore, UEs connected to the WAB-gNB can be handled correctly.
[0182] refer to Figures 7 to 11 It illustrates several methods of some embodiments.
[0183] Each method can be performed by the device.
[0184] The device may include suitable components, such as a circuit system for providing the corresponding method.
[0185] Additionally or alternatively, the device may include at least one processor and at least one memory, the memory storing instructions that, when executed by the at least one processor, cause the device to at least provide a corresponding method.
[0186] Additionally or alternatively, the device may be, for example, combined with Figure 12 As discussed.
[0187] The corresponding method can be provided through computer program code or computer executable instructions.
[0188] refer to Figure 7 The device may be a user equipment or may be provided in a user equipment.
[0189] The method includes, with reference to A1, receiving information about the quality of service (QoS) of the wireless access and backhaul mobile terminal WAB-MT for the WAB node, including information about the QoS of the backhaul link of the WAB-MT.
[0190] The method includes, with reference to A2, using information about quality of service regarding one or more packet data unit (PDU) sessions between the device and the network via a backhaul link.
[0191] The method includes, with reference to A3, sending information about one or more PDU sessions and information about quality of service to the network entity.
[0192] refer to Figure 8 The device may be an access and mobility management function, or provide access and mobility management functions, or other network functions related to access and mobility management.
[0193] The device may include at least one processor and at least one memory storing instructions for access and mobility management functions, which, when executed by the at least one processor, cause the device to at least perform the method.
[0194] The method includes, with reference to B1, determining that the user equipment (UE) is a radio access and backhaul mobile terminal (WAB-MT) of the WAB node.
[0195] The method includes, with reference to B2, requesting information about the quality of service for the backhaul link from the session management function SMF for the WAB-MT.
[0196] The method includes, with reference to B3, receiving from the SMF requested information about the quality of service used for the backhaul link.
[0197] The method includes, with reference to B4, providing WAB-MT with information about the quality of service used for the backhaul link.
[0198] refer to Figure 9 The device may be an access and mobility management function, or provide access and mobility management functions, or other network functions related to access and mobility management. The device may be a session management function, or provide session management functions, or other network functions related to session management.
[0199] The device may include at least one processor and at least one memory storing instructions for access and mobility management functions, which, when executed by the at least one processor, cause the device to at least perform the method.
[0200] The device may include at least one processor and at least one memory storing instructions for session management functions, which, when executed by the at least one processor, cause the device to at least perform the method.
[0201] The method includes, with reference to C1, receiving information about the quality of service (QoS) of the wireless access and backhaul mobile terminal WAB-MT for the WAB node, the information including information about the QoS of the backhaul link of the WAB-MT.
[0202] The method includes, with reference to C2, sending information about quality of service to the network entity.
[0203] refer to Figure 10 The device may be a session management function, or provide session management functions or other network functions related to session management.
[0204] The device may include at least one processor and at least one memory storing instructions for session management functions, which, when executed by the at least one processor, cause the device to at least perform the method.
[0205] The method includes, with reference to D1, receiving information about the quality of service (QoS) of the wireless access and backhaul mobile terminal WAB-MT for the WAB node, including information about the QoS of the backhaul link of the WAB-MT.
[0206] The method includes, with reference to D2, determining, based on information about quality of service, the connection between the user equipment (UE) and the network via the backhaul link and the limitations of quality of service.
[0207] The method includes, with reference to D3, causing modification or removal of one or more PDU sessions supported by the connection based on the determination that a quality of service limitation exists.
[0208] refer to Figure 11 The device may be a policy control function, or provide policy control functions or other network functions related to policy control.
[0209] The apparatus may include at least one processor and at least one memory, the memory storing policy control instructions that, when executed by the at least one processor, cause the apparatus to at least perform the method.
[0210] The method includes, with reference to E1, receiving information about the quality of service (QoS) of the wireless access and backhaul mobile terminal WAB-MT for the WAB node, the information including information about the QoS of the backhaul link of the WAB-MT.
[0211] The method includes, with reference to E2, providing one or more policies to a user equipment having a connection to the network via a backhaul link, based on information about quality of service.
[0212] It should be understood that Figures 7 to 11 Any method described herein may be modified to include one or more features (or their respective portions) discussed in the foregoing examples.
[0213] It should be understood that the various network functions mentioned above may include means for performing at least some of the functions associated with these network functions. Furthermore, the means containing network functions may include virtual network function instances of those network functions. This means may be a virtual machine provided by the infrastructure of a cloud computing system (e.g., a hypervisor, processor, and / or memory). This means may be part of a distributed computing system that may include multiple computing devices (e.g., servers) communicating with each other via a data network. The same or different devices in a distributed computing system may perform different network function operations.
[0214] Although these devices are described as a single entity, different modules and memory can be implemented in one or more physical or logical entities.
[0215] It should be noted that while some embodiments have been described for 5G networks and future networks, similar principles apply to other networks and communication systems. Some embodiments can be used in 6G networks. Therefore, although some embodiments have been described above, as non-limiting exemplary examples and with reference to certain wireless network architectures, technologies, and standards, these embodiments can also be applied to any other suitable communication system besides the communication systems shown and described herein.
[0216] It should also be noted that although embodiments have been described above, several variations and modifications can be made to the present invention without departing from the scope of this disclosure.
[0217] Figure 12A block diagram of apparatus 10 is shown as a non-limiting example. Apparatus 10 includes, for example, at least one processor 12 and at least one memory 14 storing instructions 15 that, when executed by the at least one processor, will cause apparatus 10 to perform the methods (or portions thereof) disclosed herein, as well as any embodiments (or corresponding portions thereof). In one example, the at least one memory and instructions are configured together with the at least one processor to cause apparatus 10 to perform the methods (or portions thereof) disclosed herein, as well as any embodiments (or corresponding portions thereof).
[0218] The processor 12 may include, or be composed of, one or more circuits configured to perform various stages of the methods described in the embodiments herein.
[0219] As used herein, the term "circuit" may refer to one or more or all of the following: (a) a purely hardware circuit implementation, such as an implementation of analog, digital, and / or quantum circuits; (b) a combination of hardware circuitry and software, such as (if applicable): (i) a combination of analog, digital, and / or quantum hardware circuitry with software / firmware; (ii) any or all portions of a hardware processor (including digital and / or quantum processors) combined with software and memory, which work together to enable a device (e.g., a mobile device, user device, computing device, or server) to perform various functions; (c) any or all portions of a hardware circuit, such as a microprocessor, processor, and / or quantum processor, which require software (e.g., firmware) to function, but may be absent if not required to function. This definition applies to all uses of the term herein, including in any claim. For example, as used herein, the term "circuit" also covers an implementation comprising only hardware circuitry or a processor (or processors) or a portion thereof, and its accompanying software and / or firmware. For example, the term "circuit" also covers (if applicable to a particular claim element) baseband integrated circuits or processor integrated circuits in mobile devices, or similar integrated circuits in servers, cellular network devices or other computing or network devices.
[0220] The memory 14 can be implemented using any suitable data storage technology. The memory may include a database for storing data. For example, the memory 14 may be at least partially located outside the device 10, but accessible to the device 10.
[0221] Instruction 15 may be contained in a computer-readable medium or a non-transient computer-readable medium. As used herein, the term “non-transient” refers to a limitation on the medium itself (i.e., tangible, not signaling) rather than a limitation on the persistence of non-data storage (e.g., random access memory).
[0222] For example, device 10 may be implemented as a UE, contain a UE, or be placed within a UE. The device may include a chipset. Device 10 may be configured to perform at least... Figure 7 The methods shown and / or one or more embodiments described herein.
[0223] For example, device 10 can be configured to provide network functions. This device can be an access and mobility management function, or provide access and mobility management functions or other network functions related to access and mobility management. Device 10 can be configured to perform at least... Figure 8 or Figure 9 The methods shown and / or one or more embodiments described herein.
[0224] For example, device 10 can be configured to provide network functions. This device can be a session management function, or provide session management functions or other network functions related to session management. Device 10 can be configured to perform at least... Figure 8 or Figure 9 The methods shown and / or one or more embodiments described herein.
[0225] For example, device 10 may be configured to provide network functions. This device may be a policy control function, or provide policy control functions or other network functions related to access and policy control. Device 10 may be configured to perform at least... Figure 11 The methods shown and / or any one or more embodiments described herein.
[0226] The device may include one or more protocol layer entities, such as a MAC entity, an RRC entity, an RLC entity, a PDCP entity, or a PHY entity.
[0227] Device 10 optionally includes a radio interface 16. Radio interface 16 provides communication capabilities to device 10. Radio interface 16 may include a receiver configured to receive information according to at least one cellular or non-cellular standard. Radio interface 16 may include a transmitter configured to transmit information according to at least one cellular or non-cellular standard. Receivers may include multiple receivers. Transmitters may include multiple transmitters. Radio interface 16 may include a transceiver configured to receive and transmit information according to at least one cellular or non-cellular standard. Transceivers may include multiple transceivers.
[0228] Device 10 may optionally include interface 18 (e.g., user interface), which includes at least one of, for example, a keyboard, microphone, touch screen, display screen, speaker, etc. A user can use interface 18 (e.g., user interface) to control the device. Interface 18 (e.g., user interface) may be located externally to device 10. For example, device 10 may be connected to another device (e.g., a computer) via a wireless or wired connection, and device 10 may be controlled by the computer.
[0229] In one embodiment, at least a portion of the processes described herein may be performed by a device comprising means for performing at least a portion of the processes. The means for performing the method steps disclosed herein may include software and / or hardware components of the device 10. For example, at least one processor 12, memory 14, and computer program code constitute means for performing the methods (or portions thereof) disclosed herein, and any embodiments (or corresponding portions thereof). The term “means” as used herein should be interpreted as either the singular (i.e., a single element) or the plural (i.e., a combination of multiple single elements). Therefore, the term “means for [performing A, B, C]” should be interpreted to encompass a device comprising only one means for performing A, B, and C, or a separate means for performing A, B, and C, or means comprising partially or completely overlapping means for performing A, B, and C. Furthermore, the terms “means for performing A, means for performing B, means for performing C” should be interpreted to encompass a device comprising only one means for performing A, B, and C, or a separate means for performing A, B, and C, or means comprising partially or completely overlapping means for performing A, B, and C.
[0230] Although various embodiments of this disclosure have been described above with reference to the accompanying drawings as non-limiting examples, it is apparent that the scope of this disclosure is not limited thereto, and that it can be modified in many different ways. As technology advances, those skilled in the art will be able to clearly understand how certain embodiments of this disclosure can be further implemented and / or modified in various ways. Furthermore, those skilled in the art should understand that any embodiment (or any part thereof) described herein may (but is not required to) be combined in various ways with any other embodiment (or any part thereof) described herein.
Claims
1. A device for communication, comprising: A component for receiving information about the quality of service (QoS) of wireless access and backhaul mobile terminal WAB-MT for WAB nodes, the information including information about the QoS of the backhaul link of the WAB-MT; A component for using the information about the quality of service regarding one or more Packet Data Unit (PDU) sessions between the device and the network via the backhaul link; as well as Components for sending information about the one or more PDU sessions and the information about the quality of service to network entities.
2. The apparatus of claim 1, wherein the component for using the information regarding the quality of service is configured to: determine, based on the information regarding the quality of service, that the quality of service for one or more current PDU sessions of the apparatus cannot be satisfied, and the information regarding the one or more PDU sessions sent to the network includes: Requests used to release the quality of service for one or more current PDU sessions that cannot be satisfied.
3. The apparatus of claim 1 or 2, wherein the component for using the information about the quality of service is configured to: determine, based on the information about the quality of service, that the quality of service for one or more current PDU sessions of the apparatus cannot be satisfied, and determine, based on the information about the quality of service, that the one or more current PDU sessions will be modified, and the information about the one or more PDU sessions sent to the network includes: A request to modify one or more current PDU sessions that will be modified.
4. The apparatus of any preceding claim, wherein the component for using the information regarding the quality of service is configured to: determine, based on the information regarding the quality of service, that one or more PDU sessions will be established and sent to the network, and that the information regarding the one or more Packet Data Unit sessions includes: A request to establish one or more current PDU sessions to be established.
5. The apparatus of any preceding claim, wherein the component for using the information about the quality of service is configured to: avoid requesting a PDU session associated with a higher quality of service than indicated by the information about the quality of service.
6. The apparatus of any preceding claim, wherein the information regarding the quality of service includes one or more of the following: Maximum Quality of Service; Best Available Quality of Service; One or more Quality of Service Stream Identifiers; Guaranteed Bit Rate; Minimum Latency and Maximum Bit Rate.
7. A device for communication, comprising: Components used to determine whether a user equipment (UE) served by the device is a wireless access and backhaul mobile terminal (WAB-MT) of a WAB node; A component used to request information about the quality of service for the backhaul link from the Session Management Function (SMF) for the WAB-MT; A component for receiving, from the SMF, the requested information regarding the quality of service for the backhaul link; as well as Components for providing the WAB-MT with information about the quality of service for the backhaul link.
8. The apparatus of claim 7, wherein the information regarding the quality of service for the backhaul link includes one or more of the following: Maximum quality of service; best available quality of service; one or more quality of service stream identifiers; guaranteed bit rate; minimum latency; and maximum bit rate.
9. The apparatus of claim 7 or 8, further comprising a component for: determining, based on determining one or more attributes of a base station serving the WAB-MT associated with the backhaul link, that the information regarding the quality of service for the backhaul link will be utilized.
10. The apparatus of claim 9, wherein the one or more attributes of the base station include one or more of the following: The base station has a first interface with the WAB-MT that has a non-terrestrial network NTN link; or The base station has a second interface with the device having an NTN link.
11. The apparatus of any one of claims 7 to 10, further comprising a component for receiving information indicating that the WAB-MT will be switched from a first backhaul base station to a second backhaul base station, and wherein the component for requesting the information regarding the quality of service is configured to: request information regarding the quality of service for the backhaul link associated with the second backhaul base station.
12. The apparatus of claim 11, wherein the first backhaul base station comprises either a terrestrial base station or a non-terrestrial base station, and the second backhaul base station comprises either a terrestrial base station or a non-terrestrial base station.
13. A communication apparatus, comprising: A component for receiving information about the quality of service (QoS) of wireless access and backhaul mobile terminal WAB-MT for WAB nodes, the information including information about the QoS of the backhaul link of the WAB-MT; as well as A component used to send information about the quality of service to network entities.
14. The apparatus of claim 13, wherein the network entity comprises one of the following: A network entity that provides policy control functions for a user equipment (UE); or a network entity that provides session management functions for a UE that has a connection to the network via the backhaul link.
15. An apparatus for communication, comprising: A component for receiving information about the quality of service (QoS) of wireless access and backhaul mobile terminal WAB-MT for WAB nodes, the information including information about the QoS of the backhaul link of the WAB-MT; A component for determining, based on the information regarding the quality of service, the connection between the user equipment (UE) and the network via the backhaul link and the associated quality of service limitations; as well as A component for inducing the modification or removal of one or more PDU sessions supported by the connection based on the determination that a limitation of the quality of service exists.
16. An apparatus for communication, comprising: A component for receiving information about the quality of service (QoS) of wireless access and backhaul mobile terminal WAB-MT for WAB nodes, the information including information about the QoS of the backhaul link of the WAB-MT; as well as Components for providing one or more policies to a user equipment having a connection to a network via the backhaul link, based on the information regarding the quality of service.
17. A method for communication, comprising: Receive information about the quality of service (QoS) of the wireless access and backhaul mobile terminal WAB-MT for the WAB node, the information including information about the QoS of the backhaul link of the WAB-MT; The information regarding the quality of service is used for one or more Packet Data Unit (PDU) sessions between the device and the network via the backhaul link; as well as Send information about the one or more PDU sessions and the information about the quality of service to the network entity.
18. A method for communication, comprising: Determine that the User Equipment (UE) is the Radio Access and Backhaul Mobile Terminal (WAB-MT) of the WAB node; The WAB-MT requests information about the Quality of Service (QoS) for the backhaul link from the Session Management Function (SMF). Receive the requested information from the SMF regarding the quality of service for the backhaul link; as well as Provide the WAB-MT with the information regarding the quality of service for the backhaul link.
19. A method for communication, comprising: Receive information about the quality of service (QoS) of the wireless access and backhaul mobile terminal WAB-MT for the WAB node, the information including information about the QoS of the backhaul link of the WAB-MT; as well as Information regarding the quality of service is sent to the network entity.
20. A method for communication, comprising: Receive information about the quality of service (QoS) of the wireless access and backhaul mobile terminal WAB-MT for the WAB node, the information including information about the QoS of the backhaul link of the WAB-MT; Based on the information regarding the quality of service, it is determined that the connection between the user equipment (UE) and the network via the backhaul link is associated with a limitation on the quality of service. as well as Based on the determination of the existence of the aforementioned quality of service limitations, one or more PDU sessions supported by the connection may be modified or removed.
21. A method for communication, comprising: Receive information about the quality of service (QoS) of the wireless access and backhaul mobile terminal WAB-MT for the WAB node, the information including information about the QoS of the backhaul link of the WAB-MT; as well as One or more policies are provided to a user equipment having a connection to the network via the backhaul link, based on the information regarding the quality of service.
22. A computer program product comprising computer-executable instructions that, when executed, cause the method of any one of claims 17 to 21 to be performed.