Charging of terminal devices connected to a relay node

Abstract

Example embodiments of this disclosure relate to billing for terminal devices connected to a relay node. One method includes: receiving a first node identifier of a network node to which the terminal device is connected; and, based on determining that the network node to which the terminal device is connected is a relay node, sending a billing data request to a third device configured to provide billing functionality, the billing data request including at least one of the following: the first node identifier or rate group information for at least one terminal device connected to the relay node.

Description

Technical Field

[0001] The various example embodiments disclosed herein relate generally to the telecommunications field, and more specifically to billing of terminal devices connected to relay nodes. Background Technology

[0002] Relay nodes in a communication network can include Radio Access and Backhaul (WAB) nodes (also known as Mobile Radio Access and Backhaul (MWAB)) and Integrated Access and Backhaul (IAB) nodes. A WAB node refers to the radio access portion that connects user equipment to the network and the backhaul portion that connects base stations to the core network. Radio access is responsible for communication between terminal devices (such as mobile phones, Internet of Things (IoT) devices, etc.) and base stations. Radio backhaul is responsible for communication between base stations and core network or upper-level network nodes. IAB is a technical concept or architecture for the design and implementation of integrated radio access and backhaul functions. It emphasizes the deep integration of these two functions in aspects such as network architecture, spectrum utilization, and signal processing. Both WAB and IAB are crucial in current and next-generation mobile communication networks. Summary of the Invention

[0003] In a first aspect of this disclosure, a first apparatus is provided. The first apparatus includes: at least one processor; and at least one memory storing instructions, which, when executed by the at least one processor, cause the first apparatus to at least: receive a first node identifier of a network node to which a terminal device is connected; and, based on determining that the network node to which the terminal device is connected is a relay node, send a billing data request to a third apparatus configured to provide billing functions, the billing data request including at least one of the following: the first node identifier or rate group information for at least one terminal device connected to the relay node.

[0004] In a second aspect of this disclosure, a second apparatus is provided. The second apparatus includes: at least one processor; and at least one memory storing instructions, which, when executed by the at least one processor, cause the second apparatus to at least: receive a second configuration indicating at least one of the following: billing for at least one terminal device connected to a relay node will be performed using at least one second node identifier, or rate group information for billing for at least one terminal device connected to a relay node; receive a policy control request for the terminal device from a first apparatus; and, based on determining that the network node to which the terminal device is connected is a relay node, send a policy control response to the first apparatus based on the second configuration, the policy control response indicating that billing for the terminal device will be performed using a first node identifier or using rate group information.

[0005] In a third aspect of this disclosure, a third apparatus is provided. The third apparatus includes: at least one processor; and at least one memory storing instructions, which, when executed by the at least one processor, cause the third apparatus to at least: receive a billing data request from a first apparatus, the billing data request including a first node identifier of a network node to which a terminal device is connected or rate group information for at least one terminal device connected to a relay node; and perform billing for the terminal device based on a policy associated with the terminal device connected to the relay node, based on determining that the network node to which the terminal device is connected is a relay node.

[0006] In a fourth aspect of this disclosure, a method is provided. The method includes: receiving a first node identifier of a network node to which a terminal device is connected; and, based on a determination that the network node to which the terminal device is connected is a relay node, sending a billing data request to a third device configured to provide billing functions, the billing data request including at least one of the following: the first node identifier or rate group information for at least one terminal device connected to the relay node.

[0007] In a fifth aspect of this disclosure, a method is provided. The method includes: receiving a second configuration indicating at least one of the following: billing for at least one terminal device connected to a relay node will be performed using at least one second node identifier, or rate group information for billing of at least one terminal device connected to a relay node; receiving a policy control request for the terminal device from a first device; and, based on determining that the network node to which the terminal device is connected is a relay node, sending a policy control response to the first device based on the second configuration, the policy control response indicating that billing for the terminal device will be performed using either the first node identifier or the rate group information.

[0008] In a sixth aspect of this disclosure, a method is provided. The method includes: receiving a billing data request from a first device, the billing data request including a first node identifier of a network node to which a terminal device is connected, or rate group information for at least one terminal device connected to a relay node; and performing billing for the terminal device based on a policy associated with the terminal device connected to the relay node, based on determining that the network node to which the terminal device is connected is a relay node.

[0009] In a seventh aspect of this disclosure, a first apparatus is provided. The first apparatus includes: components for receiving a first node identifier of a network node to which a terminal device is connected; and components for sending a billing data request to a third apparatus configured to provide billing functions based on determining that the network node to which the terminal device is connected is a relay node, the billing data request including at least one of the following: the first node identifier or rate group information for at least one terminal device connected to the relay node.

[0010] In an eighth aspect of this disclosure, a second apparatus is provided. The second apparatus includes: components for receiving a second configuration indicating at least one of the following: that billing for at least one terminal device connected to a relay node will be performed using at least one second node identifier, or rate group information for billing for at least one terminal device connected to a relay node; components for receiving a policy control request for the terminal device from a first apparatus; and components for sending a policy control response to the first apparatus based on determining that the network node to which the terminal device is connected is a relay node, the policy control response indicating that billing for the terminal device will be performed using either the first node identifier or the rate group information.

[0011] In a ninth aspect of this disclosure, a third apparatus is provided. The third apparatus includes components for receiving a billing data request from a first apparatus, the billing data request including a first node identifier of a network node to which a terminal device is connected, or rate group information for at least one terminal device connected to a relay node; and components for performing billing for the terminal device based on a policy associated with the terminal device connected to the relay node, based on determining that the network node to which the terminal device is connected is a relay node.

[0012] In a tenth aspect of this disclosure, a computer-readable medium is provided. The computer-readable medium includes instructions stored thereon for causing a device to at least execute the method according to a fourth aspect.

[0013] In the eleventh aspect of this disclosure, a computer-readable medium is provided. The computer-readable medium includes instructions stored thereon for causing a device to at least execute the method according to the fifth aspect.

[0014] In a twelfth aspect of this disclosure, a computer-readable medium is provided. The computer-readable medium includes instructions stored thereon for causing a device to at least execute the method according to the sixth aspect.

[0015] It should be understood that the summary portion is not intended to identify key or essential features of the embodiments of this disclosure, nor is it intended to limit the scope of this disclosure. Other features of this disclosure will become readily apparent from the following description. Attached Figure Description

[0016] Some exemplary embodiments will now be described with reference to the accompanying drawings, in which: Figure 1 An example communication environment in which example embodiments of the present disclosure may be implemented is shown; Figure 2 A schematic diagram of a user plane protocol stack for a WAB architecture according to some exemplary embodiments of the present disclosure is shown; Figure 3The following is illustrated: a signaling flow for billing terminal devices connected to a relay node according to some example embodiments of the present disclosure; Figures 4A to 4B Example signaling flows for billing of terminal devices connected to relay nodes are shown according to some example embodiments associated with Access and Mobility Management Functions (AMF); Figures 5A to 5B Example signaling flows for billing of terminal devices connected to a relay node according to some example embodiments associated with the Session Management Function (SMF); Figure 6 A flowchart is shown illustrating a method implemented at a first device according to some exemplary embodiments of the present disclosure; Figure 7 A flowchart is shown illustrating a method implemented at a second device according to some example embodiments of the present disclosure; Figure 8 A flowchart is shown illustrating a method implemented at a third device according to some example embodiments of the present disclosure; Figure 9 A simplified block diagram of a device suitable for implementing example embodiments of the present disclosure is shown; and Figure 10 A block diagram of an example computer-readable medium according to some example embodiments of the present disclosure is shown.

[0017] Throughout the accompanying drawings, the same or similar reference numerals denote the same or similar elements. Detailed Implementation

[0018] The principles of this disclosure will now be described with reference to some exemplary embodiments. It should be understood that these embodiments are described for illustrative purposes only and to assist those skilled in the art in understanding and implementing this disclosure, and do not imply any limitation on the scope of this disclosure. The embodiments described herein can be implemented in various ways other than those described below.

[0019] In the following description and claims, unless otherwise defined, all technical and scientific terms used herein have the same meaning as commonly understood by one of ordinary skill in the art to which this disclosure pertains.

[0020] References to "an embodiment," "embodiment," "example embodiment," etc., in this disclosure indicate that the described embodiment may include a particular feature, structure, or characteristic, but not every embodiment necessarily includes that particular feature, structure, or characteristic. Furthermore, such phrases do not necessarily refer to the same embodiment. Further, when a particular feature, structure, or characteristic is described in connection with an embodiment, it is proposed that, whether explicitly described or not, its effect in conjunction with other embodiments on such feature, structure, or characteristic is within the knowledge of those skilled in the art.

[0021] It should be understood that although various elements may be described herein using prefixes such as “first,” “second,” etc., these elements should not be limited by these terms. These terms are used only to distinguish one element from another, and they do not restrict the order of the terms. For example, without departing from the scope of the exemplary embodiments, a first element may be referred to as a second element, and similarly, a second element may be referred to as a first element. As used herein, the term “and / or” includes any and all combinations of one or more of the listed terms.

[0022] As used herein, “at least one of the following: a list of two or more elements” and “at least one of the lists of two or more elements” and similar wording, where a list of two or more elements is connected by “and” or “or”, means at least any one of the elements, or at least any two or more of the elements, or at least all of the elements.

[0023] As used herein, unless explicitly stated otherwise, the execution step “in response to A” does not indicate that the step is executed immediately after “A” occurs and may include one or more intermediate steps.

[0024] The terminology used herein is for the purpose of describing particular embodiments only and is not intended to limit the exemplary embodiments. As used herein, the singular forms “a,” “an,” and “the” are also intended to include the plural forms unless the context clearly indicates otherwise. It will be further understood that the terms “comprising,” “including,” “having,” “having,” “containing,” and / or “comprising” as used herein specify the presence of stated features, elements, and / or components, etc., but do not exclude the presence or addition of one or more other features, elements, components, and / or combinations thereof.

[0025] As used in this application, the term "circuit system" may refer to one or more of the following: (a) Hardware circuit implementation only (such as implementation in analog and / or digital circuits only), and (b) A combination of hardware circuitry and software, such as (if applicable): (i) A combination of (multiple) analog and / or digital hardware circuits with software / firmware, and (ii) Any part of the software of (multiple) hardware processors (including (multiple) digital signal processors) and (multiple) memories, which work together to enable a device (such as a mobile phone or server) to perform various functions, and (c) (Multiple) hardware circuits and / or (multiple) processors, such as (multiple) microprocessors or a portion thereof, which require software (e.g., firmware) for operation, but the software may be absent when it is not required for operation.

[0026] This definition of circuit system applies to all uses of the term in this application, including in any claim. As another example, as used herein, the term circuit system also covers implementations of only hardware circuitry or processors (or processors in general) or a portion thereof and their accompanying software and / or firmware. For example, and if applicable to a particular claim element, the term circuit system also covers baseband integrated circuits or processor integrated circuits for mobile devices or similar integrated circuits in servers, cellular network devices, or other computing or network devices.

[0027] As used herein, the term "communication network" refers to a network that conforms to any suitable communication standard, such as New Radio (NR), Long Term Evolution (LTE), LTE-A Advanced (LTE-A), Wideband Code Division Multiple Access (WCDMA), High-Speed ​​Packet Access (HSPA), Narrowband Internet of Things (NB-IoT), etc. Furthermore, communication between terminal devices and network devices in a communication network can be performed according to any suitable generation of communication protocol, including but not limited to first-generation (1G), second-generation (2G), 2.5G, 2.75G, third-generation (3G), fourth-generation (4G), 4.5G, fifth-generation (5G), 5.5G, sixth-generation (6G) communication protocols and / or any other currently known or future-developed protocols. Embodiments of this disclosure can be applied to a variety of communication systems. Given the rapid development in communications, there will naturally be future types of communication technologies and systems that can utilize them to implement this disclosure. This disclosure should not be construed as limiting its scope to only the aforementioned systems.

[0028] As used herein, the term "network device" refers to a node in a communications network through which terminal devices access the network and receive services. Network devices can refer to base stations (BS) or access points (APs), such as Node B (NodeB or NB), evolved Node B (eNodeB or eNB), NR NB (also known as gNB), Remote Radio Unit (RRU), Radio Header End (RH), Remote Radio Header End (RRH), repeater, Integrated Access and Backhaul (IAB) node, low-power node (such as femtoseconds, picoseconds), non-terrestrial network (NTN) or non-terrestrial network equipment (such as satellite network equipment, low Earth orbit (LEO) satellites, and geostationary Earth orbit (GEO) satellites), spacecraft network equipment, etc., depending on the terminology and technology applied. In some example embodiments, the Radio Access Network (RAN) split architecture includes a centralized unit (CU) and a distributed unit (DU) at the IAB donor node. An IAB node includes a mobile terminal (IAB-MT) portion that behaves similarly to a UE with respect to its parent node, and the DU portion of the IAB node behaves similarly to a base station with respect to the next-hop IAB node.

[0029] The term "terminal device" refers to any terminal device capable of wireless communication. As an example and not a limitation, a terminal device may also be referred to as a communication device, user equipment (UE), subscriber station (SS), portable subscriber station, mobile station (MS), or access terminal (AT). Terminal devices can include, but are not limited to, 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, wireless endpoints, mobile stations, laptop embedded devices (LEEs), laptop devices (LMEs), USB dongles, smart devices, wireless customer premises equipment (CPEs), Internet of Things (IoT) devices, watches or other wearable devices, head-mounted displays (HMDs), vehicles, drones, medical devices and applications (e.g., remote surgery), industrial devices and applications (e.g., robots and / or other wireless devices operating in the context of industrial and / or automated processing chains), consumer electronics devices, devices operating on commercial and / or industrial wireless networks, etc. The terminal device may also correspond to the mobile terminal (MT) portion of a WAB node or IAB node (e.g., a relay node). In the following description, the terms "terminal device," "communication device," "terminal," "user equipment," and "UE" are used interchangeably.

[0030] As used herein, the terms “resource,” “transmission resource,” “resource block,” “physical resource block” (PRB), “uplink resource,” or “downlink resource” can refer to any resource used to perform communication (e.g., communication between a terminal device and a network device), such as resources in the time domain, resources in the frequency domain, resources in the spatial domain, resources in the code domain, or any other combination of time, frequency, spatial, and / or code domain resources used to implement communication. In the following, unless explicitly stated otherwise, resources in both the frequency and time domains will be used as examples of transmission resources used to describe some exemplary embodiments of this disclosure. Note that the exemplary embodiments of this disclosure are equally applicable to other resources in other domains.

[0031] As mentioned above, relay nodes such as WAB and IAB nodes are of great importance in current and next-generation communication networks. The primary function of a WAB is to establish backhaul via conventional Protocol Data Unit (PDU) sessions. Assume a WAB node (also known as a Virtual Mobile Relay (VMR) node or Mobile Base Station Relay (MBSR)) consists of a WAB-User Equipment / Mobile Terminal (WAB-UE / MT) and a WAB-gNodeB (WAB-gNB). An IAB node consists of DU and MT components, referred to as IAB DU and IAB MT. The IAB DU can connect to the CU in the donor node.

[0032] A WAB node consists of a UE co-located with a full gNB, a WAB-gNB, and a WAB-UE. The gNB in ​​the trunk establishes N2 and N3 interfaces of the Access and Mobility Management Function (AMF) residing in the 5G Core (5GC) through a PDU session.

[0033] Figure 1 An example communication environment 100 in which example embodiments of the present disclosure may be implemented is shown. For example... Figure 1 As shown, the communication environment 100 includes a UE 110, a WAB node 120, a donor gNB 130 (also known as a backhaul gNB (BH-gNB)), a WAB user plane function (UPF) 140, and a UE UPF 150. The WAB node 120 includes a WAB-gNB 121 (also known as a backhaul gNB) providing radio connectivity for the NR BH and a WAB-mobile terminal (MT) 122 (also known as a WAB-UE). The UE UPF 150 is included in the core network (CN) 160. Figure 1 The diagram illustrates a hypothetical WAB deployment and its relationship to the service network. In some scenarios, CN160 can be the same as the CN residing in UPF140. In other scenarios, UPF140 can be the same as UPF150.

[0034] The main principle of WAB deployment is that the backhaul (BH) connection for WAB-gNB 121 is provided to the serving network by the BH PDU session established for WAB-MT 122. The WAB-gNB 121 NG interface (used for both the control plane and user plane) is transparently forwarded through the serving network. UE 110 connected to WAB-Node 120 treats the WAB cell like a normal cell, and UE 110 can establish a UE PDU session to the UE NGC using existing signaling procedures. Therefore, WAB deployment is transparent to UE 110 and does not require enhancements for legacy UEs. It is foreseeable that the network serving the actual UE and WAB-gNB may differ from the serving network serving the donor gNB 130.

[0035] The AMF 170 connects to the donor gNB 130 and is a key network element in 5GC. It is configured to verify the identity of UE 110 and determine whether UE 110 is allowed to access a specific network slice or cell.

[0036] Communication in communication environment 100 can be implemented according to any suitable communication protocol, including but not limited to cellular communication protocols, wireless local area network communication protocols (such as IEEE 802.11), and / or any other currently known or future-developed protocols. Furthermore, communication can 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 Access (OFDM), Discrete Fourier Transform Extended OFDM (DFT-s-OFDM), and / or any other currently known or future-developed technologies.

[0037] Figure 2 A schematic diagram of the user plane protocol stack for WAB architecture 200 is shown. Figure 2The user plane protocol stacks in UE 110, WAB node 120, donor gNB 130, WAB's UPF 140, and UE's UPF 150 are illustrated. Entities in UE 110 connect to entities in WAB gNB of WAB node 120 via the New Radio User-to-User (NR-UU) interface. Entities in WAB MT of WAB node 120 also connect to entities in donor gNB 130 via NR-UU. The GPRS tunneling protocol of the user plane (GTP-U) in WAB MT of WAB node 120 establishes a connection with GTP-U in UE's UPF 150 via the Next Generation User Plane Interface (NG-U). User Datagram Protocol (UDP) and Internet Protocol (IP) in WAB MT of WAB node 120 connect to their corresponding protocols in UE's UPF 150 via the 5G New Radio Interface between gNB and UPF (N3). Data in Layer 1 (L1) and Layer 2 (L2) is also transmitted via N3 between the WAB MT of WAB node 120 and the UPF 150 of the UE.

[0038] There are some requirements for billing relay nodes in communication systems. It is desirable to differentiate billing for UEs in WAB-enhanced systems.

[0039] For example, the communication system needs to be able to identify and distinguish services relayed via mobile base station repeaters, such as to apply specific billing policies. Furthermore, the communication system needs to be able to use mobile base station repeaters to provide and collect billing information for UEs, including, for example, the identifier of the UE / user involved.

[0040] As a real-world example, a transportation company that installs a relay system enters into an agreement with a mobile network operator (MNO). The MNO pays the transportation company and makes other arrangements, such as discounted / free service for the transportation company's employees using the relay system. In exchange, the MNO is to charge for the following: (1) Special subscription rates can be offered for in-vehicle 5G experience through MNO; (2) Exterior covering of the vehicle; (3) Employees of the transportation company who received the discount.

[0041] Billing assumptions are considered for all scenarios, including: data consumption, QoS, geographic region, time, online / offline billing, etc.

[0042] There are different procedures and triggers for billing definitions in 5G networks. One aspect concerns the procedures and triggers for billing definitions in the data connection domain. Table 1 shows the default trigger conditions in the Session Management Function (SMF). These triggers are defined as initiating a billing data request in the Charging Function (CHF). Note that many other triggers are defined, and those in Table 1 are only a subset.

[0043] Table 1

[0044] Similarly, Table 2 shows the default triggering conditions in the AMF. The following AMF triggers are defined to enable billing requests in the CHF. Note that many other triggers are defined, and the triggers in Table 2 are only a subset.

[0045] Table 2

[0046] As mentioned above, there are explicit requirements for billing in systems with relay nodes. Several methods already exist that can be reused to bill UEs connecting via WAB nodes or the WAB nodes themselves. However, these methods are insufficient to meet all requirements.

[0047] For example, WAB-MT should be billed differently from regular UEs using the communication system. Furthermore, the system may want to differentiate between WAB providers; for example, different WAB-MT billing would be required for different WABs. However, currently, CHF has no way to detect whether a UE is a WAB-MT and bill accordingly.

[0048] Based on example embodiments of this disclosure, some solutions are proposed to determine whether the network node to which the terminal device is connected is a relay node, and to notify the CHF to bill the terminal device according to the corresponding policy.

[0049] Using the solution in this disclosure, terminal devices connected to relay nodes can be correctly identified and billed appropriately.

[0050] Now, some example procedures will be described. Figure 3 A flowchart of a signaling flow 300 according to some example embodiments of the present disclosure is shown. For example... Figure 3 As shown, signaling flow 300 may involve Charging Trigger Function (CTF) 301 and CHF 303. For discussion purposes, reference will be made to... Figure 1The signaling flow 300 is discussed. CTF 301 and CHF 303 can be implemented in the corresponding network devices or entities, such as some core network entities configured to provide the corresponding functions. For ease of description, the functions themselves are described as the following participants.

[0051] In some example embodiments, CTF 301 may be a function typically implemented by a specific network element. It is configured to monitor specific events or conditions in the network and trigger a billing process when predetermined rules are met. In some example embodiments associated with connectivity and mobility domains, CTF 301 may be AMF. Alternatively, in some example embodiments associated with data connectivity domains, CTF 301 may be SMF.

[0052] In the following description, although operations are depicted in a specific order, this should not be construed as requiring that such operations be performed in the specific order shown or sequentially, or requiring that all shown operations be performed to achieve the desired result. In some cases, multitasking and parallel processing may be advantageous. Similarly, while several specific implementation details are included in the above discussion, these should not be construed as limiting the scope of this disclosure, but rather as a description of features that may be specific to particular embodiments. Certain features described in the context of individual embodiments may also be implemented in combination with a single embodiment. Conversely, various features described in the context of a single embodiment may also be implemented individually or in any suitable sub-combination in multiple embodiments.

[0053] The relay node in the exemplary embodiments of this disclosure may include a WAB node or an IAB node. The relay node may include a RAN device or component, such as a WAB-gNB or an IAB-DU. The relay node may also include a terminal device or component, such as an IAB MT or a WAB-MT. The relay node may include any other node having both network components and terminal components.

[0054] The following description will primarily use WAB nodes as relay nodes. It should be understood that these example embodiments can also be applied to IAB nodes or other relay nodes.

[0055] During the process of a terminal device accessing or using a network connection, the CHF can perform billing on the terminal device in response to a received billing data request. The network nodes to which the terminal device connects can include network components such as regular network nodes or relay nodes, for example, WAB-gNB or IAB-DU. It is anticipated that the CHF can distinguish between relay nodes and regular network nodes in order to bill terminal devices connected to relay nodes accordingly.

[0056] In the example embodiments of this disclosure, a network node to which a terminal device is connected is determined to be a relay node based on the node identifier of the network node. The CHF is notified that the network node is a relay node based on the node identifier or rate group information for at least one terminal device connected to the relay node.

[0057] like Figure 3 As shown, CTF 301 receives (305) a first node identifier of the network node connected to the terminal device. Based on the received first node identifier, CTF 301 determines whether the network node is a relay node. CTF 301 may be able to distinguish the node identifier of a relay node from the node identifiers of other typical RAN nodes. In response to an affirmative determination, CTF 301 sends (310) a charging data request for the terminal device to CHF 303, wherein the charging data request may include at least one of the following: a first node identifier or rate group information for at least one terminal device connected to the relay node. CHF 303 receives (315) the charging data request. The rate group information may be associated with a specific rate group configured for connecting to the relay node.

[0058] Based on the first node identifier or rate group information included in the billing data request, CHF 303 performs (320) terminal device billing based on the policy associated with the terminal device connected to the relay node. In this way, CHF 303 can bill terminal devices connected to the relay node in a different manner than terminal devices connected to a typical RAN node.

[0059] In the example embodiments of this disclosure, CTF 301 can use various solutions to determine whether the network node to which the terminal device is connected is a relay node. For example, CTF 301 can make the determination based on at least one second node identifier configured for the relay node, user location information (ULI) reports from the WAB-gNB for the UE, or with the assistance of other entities in the core network, such as policy and control functions (PCFs).

[0060] In some example embodiments, CTF 301 may obtain restriction information indicating one or more additional restrictions to be applied to the billing of terminal devices(s) connected to the relay node. For example, the additional restrictions(s) may indicate that a terminal device connected to a particular relay node may be offered discounted or no-billing service. In some examples, the restriction information indicating the additional restrictions(s) may be configured in the Unified Data Management (UDM) function. CTF 301 may include the restriction information in a billing data request to CHF 303. Specific implementation details will be described in the following text.

[0061] Reference Figure 3 After introducing the overall process, refer to Figures 4A to 4B and Figures 5A to 5B This document describes several solutions for determining whether a network node to which a terminal device is connected is a relay node.

[0062] exist Figures 4A to 4B and Figures 5A to 5B In this example, a WAB node is used as a relay node, with its network component implemented as WAB-gNB and its terminal component implemented as WAB-MT. It should be understood that... Figures 4A to 4B and Figures 5A to 5B The example implementations discussed herein can be similarly applied to IAB nodes and any other relay nodes.

[0063] Figures 4A to 4B Example signaling flows 400A-400B for charging terminal equipment connected to a relay node, according to some example embodiments associated with the AMF, are shown. Signaling flows 400A to 400B can be considered as Figure 3 An example embodiment of signaling stream 300, wherein CTF 301 is implemented as AMF.

[0064] like Figures 4A to 4B As shown, three options are provided to determine whether the network node to which the terminal device is connected is a relay node.

[0065] In Option 1, the PCF may receive a second configuration indicating that billing for at least one terminal device connected to the relay node will be performed using at least one second node identifier. The AMF may send a policy control request to the PCF including a first node identifier of the network node. The PCF may receive the policy control request.

[0066] Based on the determination that the network node to which the terminal device is connected is a relay node, the PCF can send a policy control response to the AMF based on a second configuration. This policy control response instructs the terminal device's charging to be performed using a first node identifier. In some examples, this determination can be achieved by determining that the first node identifier matches at least one second node identifier indicated by the first configuration. This might mean, for example, that the UE's serving node ID (which is the identifier of the WAB-gNB) matches one of the identifiers configured in the PCF.

[0067] In response to receiving a policy control response that includes an indication that billing for the terminal device will be performed using a first node identifier, the AMF may send a billing data request including the first node identifier to the CHF to request the CHF to perform billing for the terminal device accordingly.

[0068] In option 2, the AMF may receive a first configuration indicating that billing for terminal devices connected to a relay node will be performed using at least one second node identifier. Based on determining that the first node identifier matches at least one second node identifier indicated by the first configuration, the AMF may determine that the network node to which the terminal device is connected is a relay node. The AMF may then send a billing data request, including the first node identifier, to the CHF.

[0069] In option 3, the AMF can receive reports associated with the location information of the terminal device, such as a ULI report or an additional ULI report. Based on the received report, the AMF can determine that the network node to which the terminal device is connected is a relay node. The AMF can then send a billing data request, including the first node identifier, to the CHF.

[0070] In some example embodiments, the AMF may also request the PCF for a policy control response in options 2 and 3. Additionally, in some examples, the PCF may receive subscription information related to the terminal device from the UDM. The subscription information may include restriction information indicating at least one restriction to be applied in the billing of the terminal device connected to the relay node. The policy control response sent to the AMF may also include the restriction information. The AMF may then send a billing data request including the restriction information to the CHF. Based on the restriction information, the CHF may utilize additional restrictions (e.g., with a discount or free policy) to perform billing for the terminal device connected to the relay node.

[0071] In some example implementations, the UDM can directly provide restriction information to the AMF.

[0072] Figure 4A Signaling flow 400A is illustrated, in which the AMF instructs the CHF to charge the terminal device based on a policy associated with the terminal device connected to the relay node by sending a specific node identifier. Signaling flow 400A involves UE 110, network component 401 of the relay node (e.g., WAB-gNB), terminal component 402 of the relay node (e.g., WAB-MT), radio access network (RAN) node 403, AMF 404, CHF 303, PCF 405, and UDM 406. It should be understood that UDM 404 may alternatively be a Unified Data Repository (UDR). RAN node 403 may be a backhaul RAN node for terminal component 402.

[0073] like Figure 4AAs shown, for option 1, OAM can configure PCF 405 at 410. That is, PCF 405 can receive a second configuration indicating that billing for at least one terminal device connected to the relay node will be performed using at least one second node identifier (e.g., a specific gNB identifier (ID) for a WAB-gNB).

[0074] For option 2, OAM can configure AMF 404 at 412. Similarly, AMF 404 can receive a second configuration indicating that billing for at least one terminal device connected to the relay node will be performed using at least one second node identifier.

[0075] At 414, restriction information can be configured in UDM 406. The restriction information can indicate at least one restriction to be applied to the billing of terminal devices connected to the relay node. The restriction information can be included in the subscription information of the terminal devices connected to the relay node. In some examples, at least one restriction may include a discount or free service for the terminal devices connected to the relay node.

[0076] Then, at 416, a connection is established for the target terminal component 402. At 418, when newly registered to the network, UE 110 sends a registration request to network component 401. At 420, network component 401 sends UE 110's registration request to AMF 404 via an initial UE message. The initial UE message may include the first node identifier of network component 401 (e.g., serving gNB ID). At 422, AMF 404 sends a policy control request including the first node identifier of network component 401 to PCF 405.

[0077] For option 1, PCF 405 determines whether network component 401 is an end device connected to a relay node based on the received first node identifier and at least one configured second node identifier. For example, if the serving gNB ID is one of the gNB IDs configured for WAB-gNB, then network component 401 is determined to be WAB-gNB. At 426, based on the determination that network component 401 is a relay node, PCF sends a policy control response to AMF 404, which instructs UE 110 that charging will be performed using the first node identifier.

[0078] In some example embodiments, at 424, UDM 406 sends subscription information with the restriction information configured at 414 to PCF 405. PCF 405 then includes the received restriction information in its policy control response to AMF 404.

[0079] For option 2, AMF 404 determines whether network component 401 is an end device connected to a relay node based on the received first node identifier and at least one configured second node identifier. For example, if the serving gNB ID is one of the gNB IDs configured for WAB-gNB, then network component 401 is identified as WAB-gNB.

[0080] For option 3, at 428, AMF 404 determines that network component 401 is a relay node based on reports associated with the location information of UE 110 (e.g., ULI reports or additional ULI reports).

[0081] At 430, AMF 404 determines whether to include the first node identifier in the billing data request to CHF 303 based on any of options 1, 2, and 3. Then, at 432, AMF 404 sends the billing data request, including the first node identifier, to CHF 303. Additionally, in some examples, the billing data request may also include restriction information.

[0082] At 434, CHF 303 uses a policy associated with the terminal device connected to the relay node (e.g., WAB-gNB) to perform charging for UE 110. Furthermore, charging for UE 110 can be performed using restrictions indicated by restriction information, such as discounts or free charging.

[0083] Note that billing is triggered after the registration request, as in the example embodiment above. However, other initiation conditions in AMF 404 can trigger billing.

[0084] Alternatively or additionally, the AMF may send a billing data request that includes other instructions indicating that billing for the terminal device will be performed using rate group information of at least one terminal device connected to the relay node. For example, rate group information may be included.

[0085] In some example embodiments, based on determining that the network node to which the terminal device is connected is a relay node, and based on a second configuration indicating rate group information for billing of at least one terminal device connected to the relay node, the PCF can send a policy control response to the AMF. The policy control response indicates that billing for the terminal device will be performed using the rate group information of at least one terminal device connected to the relay node. Based on the received policy control response, the AMF can send a billing data request including the rate group information to the CHF.

[0086] Since in options 2 and 3 above, the AMF determines whether the network node to which the terminal device is connected is a relay node, the AMF also needs to send an instruction to the PCF to determine this synchronously.

[0087] In some example embodiments, the AMF may send a policy control request to the PCF, the policy control request including an indication that the network node to which the terminal device is connected is a relay node. Based on the indication included in the policy control request, the PCF may send a policy control response to the AMF, the policy control response indicating that the terminal device's billing will be performed using rate group information.

[0088] In some example embodiments, the policy control response may also include restriction information indicating at least one restriction applied to the billing of terminal devices connected to the relay node. The AMF may send the received restriction information to the CHF in a billing data request. Based on the restriction information, the CHF may utilize additional restrictions (e.g., with discount or free policies) to perform billing for terminal devices connected to the relay node.

[0089] Figure 4B Signaling flow 400B is illustrated, in which the AMF instructs the CHF to charge the terminal equipment based on a policy associated with the terminal equipment connected to the relay node by sending rate group information. Signaling flow 400B involves UE 110, network component 401, and terminal component 402 of the relay node, RAN node 403, AMF 404, CHF 303, PCF 405, and UDM 406.

[0090] like Figure 4B As shown, at 436, OAM configures PCF 405 with a specific rate group for UEs connected via WAB-gNB. That is, the second configuration received by PCF 405 can indicate rate group information for billing at least one terminal device connected to the relay node. Optionally, separate rate groups can be configured for UEs with special restrictions (e.g., discounted UEs).

[0091] For option 1, see reference. Figure 4B As described, OAM can configure PCF 405. That is, at 438, PCF405 receives a second configuration indicating that billing for at least one terminal device connected to the relay node will be performed using at least one second node identifier.

[0092] At 440, restriction information can be configured in UDM 406. The restriction information can indicate at least one restriction to be applied to the billing of terminal devices connected to the relay node. The restriction information can be included in the subscription information of the terminal devices connected to the relay node. In some examples, at least one restriction may include a discount or free service for the terminal devices connected to the relay node.

[0093] Then, at 442, a connection is established for terminal component 402. At 444, when newly registered to the network, UE 110 sends a registration request to network component 401. At 446, network component 401 sends UE 110's registration request to AMF 404 via an initial UE message. The initial UE message may include the first node identifier of network component 401 (e.g., serving gNB ID).

[0094] At 448, AMF 404 sends a policy control request to PCF 405, including the first node identifier of network component 401. For options 2 and 3, the policy control request may further include an indication that the network node to which the terminal device is connected is a relay node.

[0095] In some example embodiments, at 450, UDM 406 sends subscription information with the restriction information configured at 440 to PCF 405.

[0096] At 452, based on the determination that the network node to which the terminal device is connected is a relay node, and based on a second configuration indicating rate group information for billing of at least one terminal device connected to the relay node, at 454, PCF 405 sends a policy control response to AMF 404 indicating that billing for the terminal device will be performed using the rate group information for at least one terminal device connected to the relay node. It should be understood that the determination that the network node is a relay node can be based on an indication from AMF 404 or based on the second configuration.

[0097] Based on the received policy control response, at 456, AMF 404 sends a charging data request, including rate group information, to CHF 303. Additionally, in some examples, the charging data request may also include restriction information. In other examples, the rate group information determined by the PCF can be further determined based on additional restrictions. This means that separate rate groups can be configured at the PCF for different UE groups with different additional restrictions.

[0098] At 434, CHF 303 uses a policy associated with the terminal device connected to the relay node (e.g., WAB-gNB) to perform charging for UE 110. Furthermore, charging for UE 110 can be performed using restrictions indicated by restriction information, such as discounts or free charging.

[0099] Note that billing is triggered after the registration request, as in the example embodiment above. However, other initiation conditions in AMF 404 can also trigger billing.

[0100] Figures 5A to 5BExample signaling flows 500A-500B for charging terminal devices connected to a relay node, according to some example embodiments associated with SMF, are shown. Signaling flows 500A to 500B can be considered as Figure 3 An example embodiment of signaling flow 300, wherein CTF 301 is implemented as SMF.

[0101] like Figures 5A to 5B As shown, three options are provided to determine whether the network node to which the terminal device is connected is a relay node.

[0102] In Option 1, the PCF may receive a second configuration indicating that billing for at least one terminal device connected to the relay node will be performed using at least one second node identifier. The SMF may send a policy control request to the PCF including a first node identifier of the network node. In some example embodiments, the SMF may receive the first node identifier of the network node from the AMF.

[0103] The PCF can receive policy control requests. Based on the determination that the network node to which the terminal device is connected is a relay node, the PCF can send a policy control response to the SMF based on a second configuration. The policy control response indicates that the terminal device's billing will be performed using a first node identifier. In some examples, this determination can be achieved by determining that the first node identifier matches at least one second node identifier indicated by the first configuration.

[0104] In response to receiving a policy control response including the first node identifier, the SMF may send a billing data request including the first node identifier to the CHF to request the CHF to perform billing for the terminal device accordingly.

[0105] In option 2, the SMF may receive a first configuration indicating that billing for terminal devices connected to a relay node will be performed using at least one second node identifier. Based on determining that the first node identifier matches at least one second node identifier indicated by the first configuration, the SMF may determine that the network node to which the terminal device is connected is a relay node. The SMF may then send a billing data request, including the first node identifier, to the CHF.

[0106] In option 3, the SMF can receive reports associated with the location information of the terminal device, such as a ULI report. Based on the received report, the SMF can determine that the network node to which the terminal device is connected is a relay node. The SMF can then send a billing data request, including the first node identifier, to the CHF.

[0107] In some example embodiments, the SMF may also request the PCF for a policy control response in options 2 and 3. Additionally, in some examples, the PCF may receive subscription information related to the terminal device from the UDM. The subscription information may include restriction information indicating at least one restriction to be applied in the billing of the terminal device connected to the relay node. The policy control response sent to the SMF may also include the restriction information. The SMF may then send a billing data request including the restriction information to the CHF. Based on the restriction information, the CHF may utilize additional restrictions (e.g., with discount or free policies) to perform billing for the terminal device connected to the relay node.

[0108] In some example implementations, the UDM can directly provide restriction information to the SMF.

[0109] Figure 5A Signaling flow 500A is illustrated, in which the SMF instructs the CHF to charge the terminal device based on a policy associated with the terminal device connected to the relay node by sending a specific node identifier. Signaling flow 500A involves UE 110, network component 501 of the relay node (e.g., WAB-gNB or IAB-DU), terminal component 502 of the relay node (e.g., WAB-MT of IAB-MT), RAN node 503, AMF 504, CHF 303, PCF 505, UDM 506, and SMF 507. It should be understood that UDM 504 may alternatively be a Unified Data Repository (UDR). RAN node 503 may be a backhaul RAN node for terminal component 502.

[0110] like Figure 5A As shown, for option 1, OAM can configure PCF 505 at 510. That is, PCF 505 can receive a second configuration indicating that billing for at least one terminal device connected to the relay node will be performed using at least one second node identifier (e.g., a specific gNB ID for a WAB-gNB).

[0111] For option 2, OAM can configure SMF 507 at 512. Similarly, SMF 507 can receive a second configuration indicating that billing for at least one terminal device connected to the relay node will be performed using at least one second node identifier.

[0112] At 514, restriction information can be configured in UDM 506. Restriction information can indicate at least one restriction to be applied to the billing of terminal devices connected to the relay node. Restriction information can be included in the subscription information of the terminal devices connected to the relay node. In some examples, at least one restriction may include a discount or free service for the terminal devices connected to the relay node.

[0113] At 516, authorization and authentication are performed for UE 110 and terminal component 502. At 518, UE 110 connects to network component 501. At 520, terminal component 502 connects to RAN node 503. At 522, UE 110 establishes a PDU session. At 524, terminal component 502 determines that it needs to establish a PDU session to backhaul UE 110's PDU session. At 526, a PDU session establishment request is sent from terminal component 502 to AMF 504. Then, at 528, AMF 504 requests a new PDU session for UE 110 from SMF 507.

[0114] At position 530, SMF 507 sends a policy control request to PCF 505, including the first node identifier of network component 501. The first node identifier can be received from AMF 504.

[0115] For option 1, PCF 505 determines whether network component 501 is an end device connected to a relay node based on the received first node identifier and at least one configured second node identifier. For example, if the serving gNB ID is one of the gNB IDs configured for WAB-gNB, then network component 501 is determined to be WAB-gNB. At 534, based on the determination that network component 501 is a relay node, PCF sends a policy control response to SMF 507, which instructs UE 110 that charging will be performed using the first node identifier.

[0116] In some example embodiments, at 532, UDM 506 sends subscription information with the restriction information configured at 514 to PCF 505. PCF 505 then includes the received restriction information in its policy control response to SMF 507.

[0117] For option 2, SMF 507 determines whether network component 501 is an end device connected to a relay node based on the received first node identifier and at least one configured second node identifier. For example, if the serving gNB ID is one of the gNB IDs configured for WAB-gNB, then network component 501 is identified as WAB-gNB.

[0118] For option 3, at 536, SMF 507 determines that network component 501 is a relay node based on a report (e.g., a ULI report) associated with the location information of UE 110.

[0119] At 538, SMF 507 determines whether to include the first node identifier in the billing data request to CHF 303 based on any of options 1, 2, and 3. Then, at 540, SMF 507 sends the billing data request, including the first node identifier, to CHF 303. Additionally, in some examples, the billing data request may also include restriction information.

[0120] At 542, CHF 303 uses a policy associated with the terminal device connected to the relay node (e.g., WAB-gNB) to perform charging for UE 110. Furthermore, charging for UE 110 can be performed using restrictions indicated by restriction information, such as discounts or free charging.

[0121] Note that the billing in the example embodiment above is triggered after the PDU session is established. However, other initiation conditions in SMF 507 can trigger billing.

[0122] Alternatively or additionally, the SMF may send a billing data request that includes other instructions indicating that billing for the terminal device will be performed using rate group information for at least one terminal device connected to the relay node. For example, rate group information may be included.

[0123] In some example embodiments, based on determining that the network node to which the terminal device is connected is a relay node, and based on a second configuration indicating rate group information for billing of at least one terminal device connected to the relay node, the PCF can send a policy control response to the SMF. The policy control response indicates that billing for the terminal device will be performed using the rate group information of at least one terminal device connected to the relay node. Based on the received policy control response, the SMF can send a billing data request including the rate group information to the CHF.

[0124] Since in options 2 and 3 above, the SMF determines whether the network node to which the terminal device is connected is a relay node, the SMF also needs to send an indication to the PCF to determine this synchronously.

[0125] In some example embodiments, the SMF may send a policy control request to the PCF, the policy control request including an indication that the network node to which the terminal device is connected is a relay node. Based on the indication included in the policy control request, the PCF may send a policy control response to the SMF, the policy control response indicating that the terminal device's billing will be performed using rate group information.

[0126] In some example embodiments, the policy control response may also include restriction information indicating at least one restriction to be applied in the billing of terminal devices connected to the relay node. The SMF may send the received restriction information to the CHF in a billing data request. Based on the restriction information, the CHF may utilize additional restrictions (e.g., with discount or free policies) to perform billing for terminal devices connected to the relay node.

[0127] In some example implementations, the UDM can directly provide restriction information to the SMF.

[0128] Figure 5B Signaling flow 500B is shown, in which the SMF instructs the CHF to charge the terminal equipment based on the policy associated with the terminal equipment connected to the relay node by sending rate group information. Signaling flow 500B involves UE 110, network component 501, terminal component 502, RAN node 503, AMF 504, CHF 303, PCF 505, UDM 506, and SMF 507.

[0129] like Figure 5B As shown, at 544, the OAM configuration PCF 505 has a specific rate group for UEs connected via WAB-gNB. That is, the second configuration received by PCF 505 can indicate rate group information for billing at least one terminal device connected to the relay node. Optionally, separate rate groups can be configured for UEs with special restrictions (e.g., discounted UEs).

[0130] For option 1, see reference. Figure 5A As described, OAM can configure PCF 505. That is, at 546, PCF 505 receives a second configuration indicating that billing for at least one terminal device connected to the relay node will be performed using at least one second node identifier.

[0131] At point 548, restriction information can be configured in UDM 506. Restriction information can indicate at least one restriction to be applied to the billing of terminal devices connected to the relay node. Restriction information can be included in the subscription information of the terminal devices connected to the relay node. In some examples, at least one restriction may include a discount or free service for the terminal devices connected to the relay node.

[0132] At 550, authorization and authentication are performed for UE 110 and terminal component 502. At 552, UE 110 connects to network component 501. At 554, terminal component 502 connects to RAN node 503. At 556, UE 110 establishes a PDU session. At 558, terminal component 502 determines that it needs to establish a PDU session to backhaul UE 110's PDU session. At 560, a PDU session establishment request is sent from terminal component 502 to AMF 504. Then, at 562, AMF 504 requests a new PDU session for UE 110 from SMF 507.

[0133] At 564, SMF 507 sends a policy control request to PCF 505, including the first node identifier of network component 501. In some example embodiments, at 566, UDM 506 sends subscription information with the restriction information configured at 548 to PCF 505.

[0134] For options 2 and 3, the policy control request may further include an indication that the network node to which the terminal device is connected is a relay node. In some other examples, the rate group information determined by the PCF may be further determined based on additional restrictions. This means that separate rate groups can be configured at the PCF for different UE groups with different additional restrictions.

[0135] At point 568, based on the determination that the network node to which the terminal device is connected is a relay node, and based on a second configuration indicating rate group information for billing of at least one terminal device connected to the relay node, at point 570, PCF 505 sends a policy control response to SMF 507, the policy control response indicating that billing for the terminal device will be performed using the rate group information for at least one terminal device connected to the relay node. It should be understood that the determination that the network node is a relay node can be based on an indication from SMF 507 or based on the second configuration.

[0136] Based on the received policy control response, at point 572, SMF 507 sends a billing data request, including rate group information, to CHF 303. Additionally, in some examples, the billing data request may also include restriction information.

[0137] At 574, CHF 303 uses a policy associated with the terminal device connected to the relay node (e.g., WAB-gNB) to perform charging for UE 110. Furthermore, charging for UE 110 can be performed using restrictions indicated by restriction information, such as discounts or free charging.

[0138] Note that the billing in the example embodiment above is triggered after the PDU session is established. However, other initiation conditions in SMF 507 can trigger billing.

[0139] Figure 6 A flowchart of an example method 600 implemented at a first device according to some exemplary embodiments of the present disclosure is shown. For the purposes of discussion, method 600 will be described from the perspective of a first device, which may be or may include... Figure 3 CTF 301 in the middle.

[0140] At box 610, the first device receives a first node identifier of the network node to which the terminal device is connected.

[0141] At box 620, based on the determination that the network node to which the terminal device is connected is a relay node, the first device sends a billing data request to a third device configured to provide billing functions. The billing data request includes at least one of the following: a first node identifier or rate group information for at least one terminal device connected to the relay node.

[0142] In some example embodiments, method 600 may further include: sending a policy control request to a second device configured to provide policy and control functions, the policy control request including a first node identifier of a network node; receiving a policy control response from the second device, the policy control response indicating that billing for a terminal device will be performed using the first node identifier; and, based on the policy control response, sending a billing data request including the first node identifier to a third device.

[0143] In some example embodiments, method 600 may further include: sending a policy control request to a second device configured to provide policy and control functions, the policy control request including a first node identifier of a network node; receiving a policy control response from the second device, the policy control response indicating that billing for a terminal device will be performed using rate group information for at least one terminal device connected to a relay node; and, based on the policy control response, sending a billing data request including rate group information to a third device.

[0144] In some example embodiments, method 600 may further include: sending a policy control request to a second device configured to provide policy and control functions, the policy control request including an indication that the network node to which the terminal device is connected is a relay node; receiving a policy control response from the second device, the policy control response indicating that billing for the terminal device will be performed using rate group information of at least one terminal device connected to the relay node; and, based on the policy control response, sending a billing data request including rate group information to a third device.

[0145] In some example embodiments, the policy control response may further include restriction information for terminal devices connected to the relay node, the restriction information indicating at least one restriction to be applied in the billing of terminal devices connected to the relay node; and wherein the billing data request may further include the restriction information included in the policy control response.

[0146] In some example embodiments, method 600 may further include: receiving a first configuration indicating that billing for a terminal device connected to a relay node will be performed using at least one second node identifier; determining that the network node to which the terminal device is connected is a relay node based on determining that the first node identifier matches at least one second node identifier indicated by the first configuration; and sending a billing data request including the first node identifier to a third device.

[0147] In some example embodiments, method 600 may further include: receiving a report associated with location information of a terminal device; and based on the received report, determining that the network node to which the terminal device is connected is a relay node, and sending a billing data request including a first node identifier to a third device.

[0148] In some example embodiments, method 600 may further include: sending a policy control request to a second device configured to provide policy and control functions, the policy control request including a first node identifier of a network node and an indication that the network node to which the terminal device is connected is a relay node; and receiving a policy control response from the second device, the policy control response including rate group information for at least one terminal device connected to the relay node, and wherein the billing data request includes at least the rate group information included in the policy control response.

[0149] In some example embodiments, the first device may be configured to provide access and mobility management functions, and the first device may be made to receive a first node identifier of a network node by receiving the first node identifier of a network node from a network node to which the terminal device is connected.

[0150] In some example embodiments, the first device may be configured to provide session management functionality, and the first device may be configured to receive a first node identifier of a network node by receiving the first node identifier of a network node from a device configured to provide access and mobility management functionality, wherein the first node identifier of the network node is included in a session context creation request for a Packet Data Unit (PDU) session established for a terminal device.

[0151] In some example embodiments, a relay node may include a wireless access and backhaul (WAB), a node, or an integrated access and backhaul (IAB) node.

[0152] Figure 7A flowchart of an example method 700 implemented at a second device according to some exemplary embodiments of the present disclosure is shown. For the purposes of discussion, method 700 will be described from the perspective of a second device, which may be or may include... Figures 4A to 4B PCF 405 or Figures 5A-5B PCF 505 in the example.

[0153] At box 710, the second device receives a second configuration indicating at least one of the following: billing for at least one terminal device connected to the relay node will be performed using at least one second node identifier, or rate group information for billing for at least one terminal device connected to the relay node.

[0154] In box 720, the second device receives a policy control request for the terminal device from the first device.

[0155] At box 730, based on the determination that the network node to which the terminal device is connected is a relay node, the second device sends a policy control response to the first device based on the second configuration. The policy control response instructs the terminal device that billing will be performed using the first node identifier or using rate group information.

[0156] In some example embodiments, method 700 may further include: determining that the network node to which the terminal device is connected is a relay node based on determining that a first node identifier matches at least one second node identifier indicated by a first configuration.

[0157] In some example embodiments, method 700 may further include: determining, based on an indication included in the policy control request, that the network node to which the terminal device is connected is a relay node.

[0158] In some example embodiments, the second device may be configured to: send a policy control response to the first device based on determining that the network node to which the terminal device is connected is a relay node, and based on determining that a second configuration indicates that billing for at least one terminal device connected to the relay node will be performed using at least one second node identifier, the policy control response indicating that billing for the terminal device will be performed using the first node identifier.

[0159] In some example embodiments, method 700 may further include: sending a policy control response to a first device based on determining that the network node to which the terminal device is connected is a relay node, and based on a second configuration indicating rate group information for billing of at least one terminal device connected to the relay node, the policy control response indicating that billing of the terminal device will be performed using the rate group information for at least one terminal device connected to the relay node.

[0160] In some example embodiments, method 700 may further include: receiving subscription information related to a terminal device from a means configured to provide unified data management functions, wherein the subscription information includes restriction information. In some example embodiments, the policy control response may further include restriction information for terminal devices connected to a relay node, the restriction information indicating at least one restriction to be applied in the billing of terminal devices connected to the relay node.

[0161] In some example embodiments, method 700 may further include: determining rate group information for terminal devices connected to the relay node based on at least one restriction to be applied in the billing of terminal devices connected to the relay node; and sending a policy control response to a first device, the policy control response instructing that the billing of the terminal devices will be performed using the rate group information for at least one terminal device connected to the relay node.

[0162] In some example embodiments, the first device may be configured to provide access and mobility management functions, or to provide session management functions.

[0163] In some example embodiments, a relay node may include a wireless access and backhaul (WAB), a node, or an integrated access and backhaul (IAB) node.

[0164] Figure 8 A flowchart of an example method 800 implemented at a third device according to some example embodiments of the present disclosure is shown. For the purposes of discussion, method 800 will be described from the perspective of a third device, which may be or may include... Figure 3 CHF 303 in the middle.

[0165] At box 810, the third device receives a billing data request from the first device. The billing data request includes a first node identifier of the network node to which the terminal device is connected, or rate group information for at least one terminal device connected to a relay node.

[0166] At box 820, based on the determination that the network node to which the terminal device is connected is a relay node, the third device performs billing for the terminal device based on the policy associated with the terminal device connected to the relay node.

[0167] In some example embodiments, a relay node may include a wireless access and backhaul (WA), a node, or an integrated access and backhaul (IAB) node.

[0168] In some example embodiments, a first means capable of performing any method in method 600 (e.g., Figure 3The CTF 301 in the document may include components for performing the corresponding operations of method 600. The components may be implemented in any suitable form. For example, the components may be implemented in a circuit or software module. The first device may be implemented as or included in... Figure 3 CTF301 in In some example embodiments, the first device includes: a component for receiving a first node identifier of a network node to which the terminal device is connected; and a component for sending a billing data request to a third device configured to provide billing functions based on determining that the network node to which the terminal device is connected is a relay node, the billing data request including at least one of the following: the first node identifier or rate group information for at least one terminal device connected to the relay node.

[0169] In some example embodiments, the first device may further include: a component for sending a policy control request to a second device configured to provide policy and control functions, the policy control request including a first node identifier of a network node; a component for receiving a policy control response from the second device, the policy control response indicating that billing of a terminal device will be performed using the first node identifier; and a component for sending a billing data request including the first node identifier to a third device based on the policy control response.

[0170] In some example embodiments, the first device may further include: a component for sending a policy control request to a second device configured to provide policy and control functions, the policy control request including a first node identifier of a network node; a component for receiving a policy control response from the second device, the policy control response indicating that billing for a terminal device will be performed using rate group information for at least one terminal device connected to a relay node; and a component for sending a billing data request including rate group information to a third device based on the policy control response.

[0171] In some example embodiments, the first device may further include: a component for sending a policy control request to a second device configured to provide policy and control functions, the policy control request including an indication that the network node to which the terminal device is connected is a relay node; a component for receiving a policy control response from the second device, the policy control response indicating that the billing of the terminal device will be performed using rate group information of at least one terminal device connected to the relay node; and a component for sending a billing data request including rate group information to a third device based on the policy control response.

[0172] In some example embodiments, the policy control response may further include restriction information for terminal devices connected to the relay node, the restriction information indicating at least one restriction to be applied in the billing of terminal devices connected to the relay node; and wherein the billing data request may further include the restriction information included in the policy control response.

[0173] In some example embodiments, the first device may further include: a component for receiving a first configuration indicating that billing for a terminal device connected to a relay node will be performed using at least one second node identifier; a component for determining that the network node to which the terminal device is connected is a relay node based on determining that the first node identifier matches at least one second node identifier indicated by the first configuration; and a component for sending a billing data request including the first node identifier to a third device.

[0174] In some example embodiments, the first device may further include: components for receiving a report associated with location information of the terminal device; components for determining, based on the received report, that the network node to which the terminal device is connected is a relay node; and components for sending a billing data request including a first node identifier to a third device.

[0175] In some example embodiments, the first device may further include: a component for sending a policy control request to a second device configured to provide policy and control functions, the policy control request including a first node identifier of a network node and an indication that the network node to which the terminal device is connected is a relay node; and a component for receiving a policy control response from the second device, the policy control response including rate group information for at least one terminal device connected to the relay node, and wherein the billing data request includes at least the rate group information included in the policy control response.

[0176] In some example embodiments, the first device may be configured to provide access and mobility management functions, and the first device may be made to receive a first node identifier of a network node by receiving the first node identifier of a network node from a network node to which the terminal device is connected.

[0177] In some example embodiments, the first device may be configured to provide session management functionality, and the first device may be configured to receive a first node identifier of a network node by receiving the first node identifier of a network node from a device configured to provide access and mobility management functionality, wherein the first node identifier of the network node is included in a session context creation request for a packet data unit (PDU) session established for a terminal device.

[0178] In some example embodiments, the relay node may include a wireless access and backhaul (WAB) node or an integrated access and backhaul (IAB) node.

[0179] In some example embodiments, a second means capable of performing any method in method 700 (e.g., Figures 4A to 4BPCF 405 in Figures 700 or PCF 505 in Figures 5A-5B may include components for performing the corresponding operations of method 700. The components may be implemented in any suitable form. For example, the components may be implemented in a circuit or software module. The second device may be implemented as or included in... Figures 4A to 4B PCF 405 or Figures 5A to 5B In PCF 505.

[0180] In some example embodiments, the second apparatus includes: components for receiving a second configuration indicating at least one of the following: billing for at least one terminal device connected to a relay node will be performed using at least one second node identifier; rate group information for billing of at least one terminal device connected to a relay node; components for receiving a policy control request for the terminal device from the first apparatus; and components for sending a policy control response to the first apparatus based on the second configuration, based on determining that the network node to which the terminal device is connected is a relay node, the policy control response indicating that billing for the terminal device will be performed using either the first node identifier or the rate group information.

[0181] In some example embodiments, the second apparatus may further include a component for determining that the network node to which the terminal device is connected is a relay node based on determining that a first node identifier matches at least one second node identifier indicated by a first configuration.

[0182] In some example embodiments, the second apparatus may further include a component for determining, based on an indication included in the policy control request, that the network node to which the terminal device is connected is a relay node.

[0183] In some example embodiments, the second device may be configured to: send a policy control response to the first device based on determining that the network node to which the terminal device is connected is a relay node, and based on determining that a second configuration indicates that billing for at least one terminal device connected to the relay node will be performed using at least one second node identifier, the policy control response indicating that billing for the terminal device will be performed using the first node identifier.

[0184] In some example embodiments, the second apparatus may further include: a component for indicating rate group information for billing at least one terminal device connected to the relay node based on determining that the network node to which the terminal device is connected is a relay node, and a component for sending a policy control response to the first apparatus, the policy control response indicating that billing for the terminal device will be performed using the rate group information for at least one terminal device connected to the relay node.

[0185] In some example embodiments, the second apparatus may further include a component for receiving subscription information related to a terminal device from an apparatus configured to provide unified data management functions, wherein the subscription information includes restriction information. In some example embodiments, the policy control response may also include restriction information for terminal devices connected to the relay node, the restriction information indicating at least one restriction to be applied in the billing of terminal devices connected to the relay node.

[0186] In some example embodiments, the second apparatus may further include: components for determining rate group information for a terminal device connected to the relay node based on at least one restriction to be applied in the billing of a terminal device connected to the relay node; and components for sending a policy control response to the first apparatus, the policy control response indicating that the billing of the terminal device will be performed using the rate group information for at least one terminal device connected to the relay node.

[0187] In some example embodiments, the first device may be configured to provide access and mobility management functions, or to provide session management functions.

[0188] In some example embodiments, a relay node may include a wireless access and backhaul (WA), a node, or an integrated access and backhaul (IAB) node.

[0189] In some example embodiments, a third device capable of performing any of the methods in 800 (e.g., Figure 3 CHF303 in the document may include components for performing the corresponding operations of method 800. The components may be implemented in any suitable form. For example, the components may be implemented in a circuit or software module. The third device may be implemented as or included in... Figure 3 In CHF 303.

[0190] In some example embodiments, the third device includes components for receiving a billing data request from the first device, the billing data request including a first node identifier of a network node to which the terminal device is connected or rate group information for at least one terminal device connected to a relay node; and components for performing billing for the terminal device based on a policy associated with the terminal device connected to the relay node, based on determining that the network node to which the terminal device is connected is a relay node.

[0191] In some example embodiments, the relay node may include a wireless access and backhaul (WAB) node or an integrated access and backhaul (IAB) node.

[0192] Figure 9 This is a simplified block diagram of a device 900 suitable for implementing exemplary embodiments of the present disclosure. The device 900 can be provided to implement a communication device, for example, Figure 3The CTF 301 or CHF 303 in FIGS, PCF 405 in FIGS, PCF 505 in FIGS, and PCF 505 in FIGS. As shown, the device 900 includes one or more processors 910, one or more memories 920 coupled to the processors 910, and one or more communication modules 940 coupled to the processors 910.

[0193] Communication module 940 is used for bidirectional communication. Communication module 940 has one or more communication interfaces to facilitate communication with one or more other modules or devices. The communication interface can represent any interface necessary for communication with other network elements. In some example embodiments, communication module 940 may include at least one antenna.

[0194] As a non-limiting example, processor 910 can be any type suitable for a local technology network and can include one or more of the following: general-purpose computer, special-purpose computer, microprocessor, digital signal processor (DSP), and processor based on a multi-core processor architecture. Device 900 can have multiple processors, such as application-specific integrated circuit chips that are time-dependent on a clock that synchronizes with the main processor.

[0195] Memory 920 may include one or more non-volatile memories and one or more volatile memories. Examples of non-volatile memories include, but are not limited to, read-only memory (ROM) 924, electrically programmable read-only memory (EPROM), flash memory, hard disk, compact disc (CD), digital video disc (DVD), optical disc, laser disc, and other magnetic and / or optical storage. Examples of volatile memories include, but are not limited to, random access memory (RAM) 922 and other volatile memories that will not persist for the duration of a power outage.

[0196] Computer program 930 includes computer-executable instructions that are executed by an associated processor 910. The instructions of program 930 may include instructions for performing operations / actions of some example embodiments of this disclosure. Program 930 may be stored in memory (e.g., ROM 924). Processor 910 can perform any suitable actions and processes by loading program 930 into RAM 922.

[0197] The exemplary embodiments of this disclosure can be implemented by program 930, enabling device 900 to perform as described in the reference. Figures 2 to 8 Any process discussed in this disclosure. Exemplary embodiments of this disclosure may also be implemented by hardware or a combination of software and hardware.

[0198] In some example embodiments, program 930 may be tangibly contained in a computer-readable medium, which may be included in device 900 (such as in memory 920) or other storage device accessible by device 900. Device 900 may load program 930 from the computer-readable medium into RAM 922 for execution. In some example embodiments, the computer-readable medium may include any type of non-transitory storage medium, such as ROM, EPROM, flash memory, hard disk, CD, DVD, etc. As used herein, the term "non-transitory" refers to a limitation of the medium itself (i.e., tangible, not tactile), rather than a limitation of the persistence of data storage (e.g., RAM versus ROM).

[0199] Figure 10 An example of a computer-readable medium 1000 is shown, which may be in the form of a CD, DVD, or other optical storage disc. The computer-readable medium 1000 has a program 930 stored thereon.

[0200] Generally, the various embodiments of this disclosure can be implemented in hardware or dedicated circuitry, software, logic, or any combination thereof. Some aspects can be implemented in hardware, and others can be implemented in firmware or software that can be executed by a controller, microprocessor, or other computing device. Although various aspects of the embodiments of this disclosure are shown and described as block diagrams, flowcharts, or using some other graphical representation, it should be understood that the blocks, apparatuses, systems, techniques, or methods described herein can be implemented in hardware, software, firmware, dedicated circuitry or logic, general-purpose hardware, or controllers or other computing devices, or some combination thereof, as non-limiting examples.

[0201] Some exemplary embodiments of this disclosure also provide at least one computer program product tangibly stored on a computer-readable medium, such as a non-transitory computer-readable medium. The computer program product includes computer-executable instructions that execute in a device on a target physical or virtual processor, such as those included in a program module, to perform any of the methods described above. Typically, a program module includes routines, programs, libraries, objects, classes, components, data structures, etc., that perform a particular task or implement a particular abstract data type. In various embodiments, the functionality of a program module can be combined or split among program modules as needed. The machine-executable instructions for a program module can execute within a local or distributed device. In a distributed device, the program module can reside on both local and remote storage media.

[0202] Program code used to perform the methods of this disclosure may be written in any combination of one or more programming languages. The program code may be provided to a processor or controller of a general-purpose computer, special-purpose computer, or other programmable data processing apparatus, such that, when executed by the processor or controller, the program code causes the functions / operations specified in the flowcharts and / or block diagrams to be implemented. The program code may be executed entirely on a machine, partially on a machine, as a stand-alone software package, partially on a machine and partially on a remote machine, or entirely on a remote machine or server.

[0203] In the context of this disclosure, computer program code or related data may be carried by any suitable carrier wave to enable a device, apparatus, or processor to perform the various processes and operations described above. Examples of carrier waves include signals, computer-readable media, etc.

[0204] Computer-readable media can be computer-readable signal media or computer-readable storage media. Computer-readable media can include, but is not limited to, electronic, magnetic, optical, electromagnetic, infrared, or semiconductor systems, apparatuses, or devices, or any suitable combination thereof. More specific examples of computer-readable storage media will include electrical connections having one or more wires, portable computer disks, hard disks, random access memory (RAM), read-only memory (ROM), erasable programmable read-only memory (EPROM or flash memory), optical fibers, portable optical disc read-only memory (CD-ROM), optical storage devices, magnetic storage devices, or any suitable combination thereof.

[0205] Furthermore, although operations are described in a specific order, this should not be construed as requiring that such operations be performed in the specific order shown or sequentially, or requiring that all shown operations be performed to achieve the desired result. In some cases, multitasking and parallel processing may be advantageous. Similarly, although several specific implementation details are included in the above discussion, these should not be construed as limiting the scope of this disclosure, but rather as a description of features that may be specific to particular embodiments. Unless explicitly stated otherwise, certain features described in the context of a single embodiment may also be implemented in combination in a single embodiment. Conversely, unless explicitly stated otherwise, various features described in the context of a single embodiment may also be implemented individually or in any suitable sub-combination in multiple embodiments.

[0206] Although this disclosure has been described in language specific to structural features and / or methodological actions, it should be understood that the disclosure as defined in the appended claims is not necessarily limited to the specific features or actions described above. Rather, the specific features and actions described above are disclosed as exemplary forms for implementing the claims.

Claims

1. A first device for communication, comprising: At least one processor; as well as At least one memory storing instructions that, when executed by the at least one processor, cause the first device to at least: The first node identifier of the network node to which the receiving terminal device is connected; as well as Based on the determination that the network node to which the terminal device is connected is a relay node, a billing data request is sent to a third device configured to provide billing functions. The billing data request includes at least one of the following: the first node identifier or rate group information for at least one terminal device connected to the relay node.

2. The first device according to claim 1, wherein the first device is further configured to: Send a policy control request to a second device configured to provide policy and control functions, the policy control request including the first node identifier of the network node; The terminal device receives a policy control response from the second device, the policy control response indicating that billing for the terminal device will be performed using the first node identifier; as well as Based on the policy control response, the billing data request, including the first node identifier, is sent to the third device.

3. The first device according to claim 1, wherein the first device is further configured to: Send a policy control request to a second device configured to provide policy and control functions, the policy control request including the first node identifier of the network node; The second device receives a policy control response, which instructs the terminal device that billing will be performed using the rate group information for at least one terminal device connected to the relay node; as well as Based on the policy control response, a billing data request including the rate group information is sent to the third device.

4. The first device according to claim 1, wherein the first device is further configured to: A policy control request is sent to a second device configured to provide policy and control functions, the policy control request including an indication that the network node to which the terminal device is connected is a relay node; The second device receives a policy control response, which instructs the terminal device that billing will be performed using the rate group information for at least one terminal device connected to the relay node; as well as Based on the policy control response, a billing data request including the rate group information is sent to the third device.

5. The first apparatus according to any one of claims 2 to 4, wherein the policy control response further includes restriction information for the terminal device connected to the relay node, the restriction information indicating at least one restriction to be applied when billing the terminal device connected to the relay node; and The charging data request also includes the restriction information included in the policy control response.

6. The first device according to claim 1, wherein the first device is configured to: Receive a first configuration, the first configuration indicating that billing for terminal devices connected to the relay node will be performed using at least one second node identifier; and Based on the determination that the first node identifier matches the at least one second node identifier indicated by the first configuration, it is determined that the network node to which the terminal device is connected is the relay node. Send the billing data request, including the first node identifier, to the third device.

7. The first device according to claim 1, wherein the first device is configured such that: Receive reports associated with the location information of the terminal device; and Based on the received report, it is determined that the network node to which the terminal device is connected is the relay node, and Send the billing data request, including the first node identifier, to the third device.

8. The first device according to any one of claims 6 or 7, wherein the first device is configured to: A policy control request is sent to a second device configured to provide policy and control functions, the policy control request including a first node identifier of the network node and an indication that the network node to which the terminal device is connected is the relay node; and The second device receives a policy control response, the policy control response including rate group information for at least one terminal device connected to the relay node, and The billing data request includes at least the rate group information included in the policy control response.

9. The first apparatus according to any one of claims 1 to 4, wherein the first apparatus is configured to provide access and mobility management functions, and the first apparatus is caused to receive the first node identifier of the network node by: The terminal device receives the first node identifier of the network node from the network node to which it is connected.

10. The first apparatus according to any one of claims 1 to 4, wherein the first apparatus is configured to provide session management functionality, and the first apparatus is caused to receive the first node identifier of the network node by: The network node receives the first node identifier from a device configured to provide access and mobility management functions, the first node identifier of the network node being included in a session context creation request for a Packet Data Unit (PDU) session established for the terminal device.

11. The first apparatus according to any one of claims 1 to 4, wherein the relay node comprises a wireless access and backhaul (WAB) node or an integrated access and backhaul (IAB) node.

12. A second means for communication, comprising: At least one processor; as well as At least one memory storing instructions that, when executed by the at least one processor, cause the second device to at least: Receive a second configuration indicating at least one of the following: Billing for at least one terminal device connected to the relay node will be performed using at least one second node identifier, or Rate group information for billing at least one terminal device connected to the relay node; Receive a policy control request for the terminal device from the first device; as well as Based on the determination that the network node to which the terminal device is connected is a relay node, a policy control response is sent to the first device based on the second configuration. The policy control response indicates that the billing of the terminal device will be performed using the first node identifier or using the rate group information.

13. The second means of claim 12, wherein the policy control request includes a first node identifier of the network node to which the terminal device is connected, and wherein the second means is configured to: Based on the determination that the first node identifier matches the at least one second node identifier indicated by the first configuration, it is determined that the network node to which the terminal device is connected is a relay node.

14. The second apparatus of claim 12, wherein the policy control request includes an indication that the network node to which the terminal device is connected is a relay node, and wherein the second apparatus is configured to: Based on the indication included in the policy control request, it is determined that the network node to which the terminal device is connected is a relay node.

15. The second device according to any one of claims 12 to 14, wherein the second device is configured to: Based on the determination that the network node to which the terminal device is connected is a relay node, and based on the determination that the second configuration indicates that billing for at least one terminal device connected to the relay node will be performed using at least one second node identifier, The policy control response is sent to the first device, the policy control response instructing the terminal device to use the first node identifier for billing.

16. The second device according to any one of claims 12 to 14, wherein the second device is configured to: Based on the determination that the network node to which the terminal device is connected is a relay node, and based on the second configuration indicating the rate group information for billing at least one terminal device connected to the relay node, The policy control response is sent to the first device, the policy control response instructing the terminal device to perform billing using the rate group information for at least one terminal device connected to the relay node.

17. The second device according to any one of claims 12 to 14, wherein the second device is further configured to: The device receives subscription information related to the terminal device from a device configured to provide unified data management functions, wherein the subscription information includes the restriction information, and The policy control response further includes restriction information for the terminal device connected to the relay node, the restriction information indicating at least one restriction to be applied in the billing of the terminal device connected to the relay node.

18. The second device according to any one of claims 12 to 14, wherein the second device is further configured to: Rate group information for the terminal devices connected to the relay node is determined based on at least one restriction to be applied in the billing of the terminal devices connected to the relay node; and The policy control response is sent to the first device, the policy control response instructing the terminal device to perform billing using the rate group information for at least one terminal device connected to the relay node.

19. The second apparatus according to any one of claims 12 to 14, wherein the first apparatus is configured to provide access and mobility management functions, or is configured to provide session management functions.

20. The second apparatus according to any one of claims 12 to 14, wherein the relay node comprises a wireless access and backhaul (WAB) node or an integrated access and backhaul (IAB) node.

21. A third means for communication, comprising: At least one processor; as well as At least one memory storing instructions that, when executed by the at least one processor, cause the third device to at least: The first device receives a billing data request, the billing data request including a first node identifier of a network node to which the terminal device is connected or rate group information for at least one terminal device connected to a relay node. as well as Based on the determination that the network node to which the terminal device is connected is a relay node, the billing of the terminal device is performed based on the policy associated with the terminal device connected to the relay node.

22. The third apparatus of claim 21, wherein the relay node comprises a wireless access and backhaul (WAB) node or an integrated access and backhaul (IAB) node.

23. A method for communication, comprising: The first node identifier of the network node to which the receiving terminal device is connected; as well as Based on the determination that the network node to which the terminal device is connected is a relay node, a billing data request is sent to a third device configured to provide billing functions. The billing data request includes at least one of the following: the first node identifier or rate group information for at least one terminal device connected to the relay node.

24. A method for communication, comprising: Receive a second configuration indicating at least one of the following: Billing for at least one terminal device connected to the relay node will be performed using at least one second node identifier, or Rate group information for billing at least one terminal device connected to the relay node; Receive a policy control request for the terminal device from the first device; as well as Based on the determination that the network node to which the terminal device is connected is a relay node, a policy control response is sent to the first device based on the second configuration. The policy control response indicates that the billing of the terminal device will be performed using the first node identifier or the rate group information.

25. A method for communication, comprising: The first device receives a billing data request, the billing data request including a first node identifier of a network node to which the terminal device is connected or rate group information for at least one terminal device connected to a relay node. as well as Based on the determination that the network node to which the terminal device is connected is a relay node, the billing of the terminal device is performed based on the policy associated with the terminal device connected to the relay node.

26. A computer-readable medium comprising instructions stored thereon, the instructions being configured to cause a device to perform at least the method of claim 23, the method of claim 24, or the method of claim 25.

Images