Billing of terminal devices connected to relay nodes

Abstract

Example embodiments of this disclosure relate to billing for terminal devices connected to relay nodes. One method includes: determining that the network node to which the terminal device is connected is a relay node; and sending a billing data request for the terminal device to a third device configured to provide billing functionality, the billing data request including an indication that the network node to which the terminal device is connected is a 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: determine that a network node to which a terminal device is connected is a relay node; and send a billing data request for the terminal device to a third apparatus configured to provide billing functions, the billing data request including an indication that the network node to which the terminal device is connected is a 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 configured to provide policy and control functions to at least: receive a second configuration indicating that billing for a terminal device connected to a relay node will be performed using at least one second node identifier; receive a policy control request from a first apparatus configured to provide access and mobility management functions or session management functions, the policy control request including a first node identifier of a network node to which the terminal device is connected; and, based on determining that the first node identifier matches at least one second node identifier indicated by the second configuration, send a policy control response to the first apparatus, the policy control response including an indication that the network node to which the terminal device is connected is a relay node.

[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 configured to provide charging functions to at least: receive a charging data request for a terminal device from a first apparatus configured to provide access and mobility management functions or session management functions, the charging data request including an indication that a network node to which the terminal device is connected is a relay node; and perform charging for the terminal device based on a policy associated with the terminal device connected to the relay node.

[0006] In a fourth aspect of this disclosure, a method is provided. The method includes: determining that a network node to which a terminal device is connected is a relay node; and sending a billing data request for the terminal device to a third device configured to provide billing functionality, the billing data request including an indication that the network node to which the terminal device is connected is a relay node.

[0007] In a fifth aspect of this disclosure, a method is provided. The method includes: receiving a second configuration indicating that billing for a terminal device connected to a relay node will be performed using at least one second node identifier; receiving a policy control request from a first means configured to provide access and mobility management functions or session management functions, the policy control request including a first node identifier of a network node to which the terminal device is connected; and sending a policy control response to the first means based on determining that the first node identifier matches at least one second node identifier indicated by the second configuration, the policy control response including an indication that the network node to which the terminal device is connected is a relay node.

[0008] In a sixth aspect of this disclosure, a method is provided. The method includes: receiving, from a first means configured to provide access and mobility management functions or session management functions, a charging data request for a terminal device, the charging data request including an indication that a network node to which the terminal device is connected is a relay node; and performing charging for the terminal device based on a policy associated with the terminal device connected to the relay node.

[0009] In a seventh aspect of this disclosure, a first apparatus is provided. The first apparatus includes: components for determining that a network node to which a terminal device is connected is a relay node; and components for sending a billing data request for the terminal device to a third apparatus configured to provide billing functions, the billing data request including an indication that the network node to which the terminal device is connected is a 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 that billing for a terminal device connected to a relay node will be performed using at least one second node identifier; components for receiving a policy control request from a first apparatus configured to provide access and mobility management functions or session management functions, the policy control request including a first node identifier of a network node to which the terminal device is connected; and components for sending a policy control response to the first apparatus based on determining that the first node identifier matches at least one second node identifier indicated by the second configuration, the policy control response including an indication that the network node to which the terminal device is connected is a relay node.

[0011] In a ninth aspect of this disclosure, a third apparatus is provided. The third apparatus includes components for receiving a charging data request for a terminal device from a first apparatus configured to provide access and mobility management functions or session management functions, the charging data request including an indication that a network node to which the terminal device is connected is a relay node; and components for performing charging for the terminal device based on a policy associated with the terminal device connected to the 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 perform at least the method according to the 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 this 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 4E 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 5F Example signaling flows for billing of terminal devices connected to a relay node are shown, based on 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 a list 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, performing the step “in response to A” does not indicate that the step is performed 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), relay, 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 the 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 node 120's WAB gNB via the New Radio User-to-User (NR-UU) interface. Entities in WAB node 120's WAB MT also connect to entities in donor gNB 130 via NR-UU. The GPRS tunneling protocol of the user plane (GTP-U) in WAB node 120's WAB MT establishes a connection with the GTP-U in UE's UPF 150 via the Next Generation User Plane Interface (NG-U). The User Datagram Protocol (UDP) and Internet Protocol (IP) in WAB node 120's WAB MT connect to their corresponding protocols in UE's UPF 150 via the 5G New Radio Interface between the 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 between 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 relays, such as to apply specific billing policies. Furthermore, the communication system needs to be able to use mobile base station relays 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 SMF. These triggers are defined as initiating a billing data request in the Billing 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, (multiple) end devices connected via WAB-gNB should be billed differently from (e.g., in 5GS) typical end devices utilizing typical RAN nodes. Furthermore, the system may expect differentiation between WAB providers; for example, differentiated WAB-gNB billing would be required for different WABs. However, currently, CHF has no way to determine which end devices are connected to the relay node (more specifically, the network components connected to the relay node) to be billed.

[0048] According to example embodiments of this disclosure, some solutions for a charging trigger function (CTF) are proposed to determine whether a network node to which a terminal device is connected is a relay node, and to notify the CHF to charge 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 Signaling flow 300 according to some example embodiments of this 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 1 Discussion process 300. 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 in 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] In the following description, the WAB node will be used primarily as an example. 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 receiving a billing data request. The terminal device may include a typical terminal device, such as a UE, or a terminal component of a relay node, such as a WAB-MT. It is anticipated that the CHF can distinguish between the terminal components of a relay node and typical terminal devices in order to bill them accordingly.

[0056] 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 billing data request received from the CTF. The network nodes to which the terminal device connects can include normal network nodes (e.g., RAN nodes) or network components such as relay nodes for backhaul, such as WAB-gNB or IAB-DU. It is anticipated that the CHF can distinguish between relay nodes and normal network nodes in order to bill terminal devices connected to relay nodes accordingly.

[0057] In an example embodiment of this disclosure, the CTF determines that the network node to which the terminal device is connected is a relay node. Based on the node identifier or rating group information for at least one terminal device connected to the relay node, the CHF is notified that the network node is a relay node.

[0058] like Figure 3 As shown, CTF 301 determines (305) that the network node to which the terminal device 302 is connected is a relay node 304. To access the network, the terminal device 302 (e.g., UE) can connect to a network node, which in some cases may be a typical RAN node, and in others may be a relay node 304. In the case of a relay node, the terminal device 302 can connect to network component 304-1 of the relay node 304, such as WAB-gNB or IAB-DU, and the relay node 304 may also include terminal component 304-2, such as WAB-MT or IAB MT.

[0059] Based on this determination, CTF 301 sends (310) a billing data request for the terminal device to CHF 303. The billing data request includes an indication that the network node to which the terminal device is connected is relay node 304 or more specifically, network component 304-1 of relay node 304.

[0060] CHF 303 receives (315) a charging data request. Based on the indications included in the charging data request, CHF 303 performs (320) charging of terminal device 302 based on the policy associated with the terminal device connected to the relay node. Note that the policy used to charge terminal devices connected to network components connected to the relay node can be configured in any suitable manner, which is not limited in the example embodiments of this disclosure.

[0061] CTF 301 can use various solutions to determine whether an end component is connected to a relay node. For example, CTF 301 can make the determination based on explicit instructions received from another entity or by means of other entities in the core network, such as Policy and Control Functions (PCF), Unified Data Management Functions (UDM), and Unified Data Repository Functions (UDR). In some example embodiments, CTF 301 can be notified of the node identifier of the network node to which the end device 302 is connecting (e.g., the node identifier of network node 304), which is then used to identify the network node in order to determine whether it is a relay node.

[0062] Furthermore, in some example embodiments, the billing data request sent by CTF 301 may also include type information indicating the type of relay node (e.g., the type of WAB node or IAB node). Based on the received type information, CHF 303 can perform billing for the terminal device according to different types. For example, depending on the different providers or suppliers of the relay nodes, CHF 303 may perform different billing for the terminal components.

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

[0064] exist Figures 4A to 4E and Figures 5A to 5F 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 in... Figures 4A to 4E and Figures 5A to 5F The example implementations discussed herein can be similarly applied to IAB nodes and any other relay nodes.

[0065] Figures 4A to 4E Example signaling flows 400A-400E for billing terminal devices connected to a relay node are shown according to some example embodiments associated with the AMF. Signaling flows 400A-400E can be considered as... Figure 3 An example embodiment of signaling flow 300, wherein CTF 301 is implemented as AMF. For example... Figures 4A to 4E As shown, five options are provided to determine whether the terminal device is connected via a relay node.

[0066] In Option A, during the establishment of a connection between relay node 304 (or more specifically, a network component of relay node 304) and the AMF, the AMF may receive an establishment request that may include an indication that the network node to which the terminal device is connected is a relay node. In some example embodiments, the establishment request may also include type information indicating the type of relay node or the type of network component of the relay node. The AMF uses such information received in the establishment request while sending a billing data request to the CHF.

[0067] Figure 4A Example signaling flow 400 A is shown for billing terminal device 302 connected to relay node 304 according to option A. Signaling flow 400 A involves terminal device 302, relay node 304 (e.g., WAB node or IAB node), AMF 402, and CHF 303. AMF 402 can be... Figure 3Examples of CTF 301 in the example.

[0068] like Figure 4A As shown, terminal device 302 (e.g., UE) connects to the network component of relay node 304. At 410, AMF 402 receives an establishment request from the network node to which terminal device 302 is connected (in this case, from the network component of relay node 304). The establishment request may include an NG establishment request message. The establishment request includes an indication that the network node to which terminal device 302 is connected is relay node 304. That is, relay node 304 can notify AMF 402 that it is the relay node to which terminal device 302 is connecting when establishing a connection with AMF 402. Such an indication for a relay node that is a WAB node can be represented as "wabgNBIndication".

[0069] In some example embodiments, the establishment request may also include type information indicating the type of relay node 304, which is represented as "mwabType" for relay nodes that are WAB nodes.

[0070] Thus, AMF 402 can determine that the network node to which terminal device 302 is connected is relay node 304 based on the indication "wabgNBIndication" included in the establishment request. If type information is included in the establishment request, AMF 402 can also determine the type of relay node 304. At 412, AMF 402 sends an establishment response, such as an NG establishment response, to relay node 304.

[0071] Since the establishment request may include the node identifier of relay node 304 (e.g., MWAB-gNBID), at 414, AMF 402 stores a mapping of the node identifier, indication, and type information of the relay node, such as the mapping of the node identifier “MWAB-gNBID”, the indication “wabgNBIndication”, and the type information “mwabType”.

[0072] To trigger billing for terminal device 302, AMF 402 can use the node identifier of the network node to which terminal device 302 is connected to determine the indication "wabgNBIndication" and type information "mwabType" from the stored mapping. Note that billing for terminal device 302 can be triggered by AMF 402 through any suitable event.

[0073] Then at 416, AMF 402 sends a billing data request to CHF 303. The billing data request may include the indication "wabgNBIndication". If AMF 402 is notified of type information, the billing data request sent to CHF 303 may also include type information.

[0074] At 418, upon receiving the indication “wabgNBIndication” from AMF 402, CHF 303 determines a charging data request for terminal device 302 connected via a network component of a relay node and charges terminal device 302, for example, according to a Service Level Agreement (SLA). For example, the charging for terminal devices connected via a network component of a relay node may be less than that for normally connected terminal devices. Note that differentiated charging for terminal devices connected via a network component of a relay node and charging for terminal devices connected via normally connected RAN network nodes can be configured as needed, and this is not limited to the scope of this disclosure.

[0075] At 420, CHF 303 sends a billing data response to AMF 402.

[0076] In option B, (multiple) terminal devices send a registration request message to the network component of the relay node (e.g., WAB-gNB). The network component of the relay node includes an indication of the terminal device's connection via the network component in a message related to terminal device 302 (e.g., an initial UE message). In some example embodiments, the message may also include type information indicating the type of the relay node or the type of the network component of the relay node. The AMF uses this information while sending a charging data request to the CHF.

[0077] Figure 4B An example signaling flow 400B for billing a terminal device 302 connected to a relay node 304 according to option B is shown. Signaling flow 400B involves the terminal device 302, the relay node 304 (e.g., a WAB node or an IAB node), the AMF 402, and the CHF 303. The AMF 402 may be... Figure 3 Examples of CTF 301 in the example.

[0078] like Figure 4BAs shown, terminal device 302 (e.g., UE) connects to the network component of relay node 304. At 422, terminal device 302 sends a registration request to the network component of relay node 304. At 424, relay node 304 may then send a message related to terminal device 302 to AMF 402. This message may, for example, be an initial UE message. This message may include an indication “wabgNBIndication”, which indicates that the network node to which terminal device 302 is connected is relay node 304, or more specifically, the network component of the relay node, such as WAB-gNB.

[0079] In some example embodiments, the message received by AMF 402 may also include type information indicating the type of relay node 304, which is represented as "mwabType" for relay nodes that are WAB nodes.

[0080] Thus, AMF 402 can determine that the network node to which terminal device 302 is connected is relay node 304 based on the indication "wabgNBIndication" included in the message. If type information is included in the received message, AMF 402 can also determine the type of relay node 304.

[0081] Since the initial UE message may include the node identifier of relay node 304 (e.g., MWAB-gNBID), at 426, AMF 402 stores a mapping of the node identifier, indication, and type information of the relay node, such as a mapping of the node identifier “MWAB-gNBID”, the indication “wabgNBIndication”, and the type information “mwabType”.

[0082] To trigger billing by terminal device 302, at 428, AMF 402 sends a billing data request to CHF 303. The billing data request may include the indication "wabgNBIndication". If AMF 402 is notified of type information, the billing data request sent to CHF 303 may also include type information.

[0083] At 430, upon receiving the indication “wabgNBIndication” from AMF 402, CHF 303 determines a charging data request for terminal device 302 connected via the network component of the relay node, and charges terminal device 302, for example, according to the SLA. At 432, CHF 303 sends a charging data response to AMF 402.

[0084] This can be referenced above. Figure 4A The similar methods for initiating billing data triggers and differentiated billing discussed will not be described in detail here.

[0085] In option C, OAM can provide a mapping of the node identifier "mwabg NBID", the indication "mwabgNBIndication", and the type information "mwabType" within the Unified Data Management or Repository Function (UDM / UDR). The terminal device can send a registration request message to the network component of the relay node, which also sends messages associated with the terminal device 302, including the Cell Group Identifier (CGI) parameter. AMF derives the node identifier from the CGI and uses it as a data key to retrieve information related to the network component of the relay node from the UDM / UDR. AMF also uses the same information as when sending a charging data request to CHF.

[0086] Figure 4C An example signaling flow 400C for charging a terminal device 302 connected to a relay node 304 according to option C is shown. Signaling flow 400C involves the terminal device 302, the relay node 304 (e.g., a WAB node or an IAB node), AMF 402, CHF 303, and UDM / UDR 404. AMF 402 can be... Figure 3 Examples of CTF 301 in the example.

[0087] In signaling flow 400C, at 434, UDM / UDR 404 is provided with a mapping of node identifier “mwabg NBID”, indicator “mwabgNBIndication” and type information “mwabType”.

[0088] AMF 402 can obtain the node identifier of the network node to which terminal device 302 is connected. Specifically, at 436, terminal device 302 sends a registration request to the network component of relay node 304. At 438, relay node 304 can then send a message related to terminal device 302 to AMF 402. For example, this message could be an initial UE message. The message related to terminal device 302 may include the CGI of the network node. At 440, AMF 402 can derive the node identifier "mwabgNBID" of relay node 304 from the CGI included in the message.

[0089] At position 442, the AMF sends an information retrieval request to UDM / UDR 404, including the node identifier "mwabg NBID" of the network node. The information retrieval request may include a request to retrieve gNB information.

[0090] In response to the information retrieval request, at 444, UDM / UDR 404 may send back an information retrieval response including the node identifier "mwabgNBID" and an indication "wabgNBIndication" indicating that the network node to which terminal device 302 is connected is relay node 304. The information retrieval response may, for example, be a gNB information retrieval response.

[0091] In some example embodiments, the information retrieval response may also include type information indicating the type of relay node 304, which is represented as "mwabType" for relay nodes that are WAB nodes.

[0092] At 446, AMF 402 stores a mapping of node identifiers, indications, and type information for relay nodes, such as a mapping of the node identifier “MWAB-gNBID”, indication “wabgNBIndication”, and type information “mwabType” received from UDM / UDR 404.

[0093] To trigger billing by terminal device 302, at 448, AMF 402 sends a billing data request to CHF 303. The billing data request may include the indication "wabgNBIndication". If AMF 402 is notified of type information, the billing data request sent to CHF 303 may also include type information.

[0094] At 450, upon receiving the indication “wabgNBIndication” from AMF 402, CHF 303 determines a charging data request for terminal device 302 connected via the network component of the relay node, and charges terminal device 302, for example, according to the SLA. At 452, CHF 303 sends a charging data response to AMF 402.

[0095] This can be referenced above. Figure 4A The similar methods for initiating billing data triggers and differentiated billing discussed will not be described in detail here.

[0096] In option D, OAM configures the mapping of the node identifier "mwabg NBID", the indicator "mwabgNBIndication", and the type information "mwabType" in the AMF. Therefore, the AMF uses the same information when sending billing data requests to the CHF.

[0097] Figure 4DAn example signaling flow 400D for billing a terminal device 302 connected to a relay node 304, according to option D, is shown. Signaling flow 400D involves the terminal device 302, the relay node 304 (e.g., a WAB node or an IAB node), AMF 402, CHF 303, and OAM 408. AMF 402 can be... Figure 3 Examples of CTF 301 in the example.

[0098] In signaling flow 400D, at 454, AMF 402 receives from OAM 408 a configuration indicating that billing for terminal device 302 connected to relay node 304 will be performed using at least one node identifier “mwabgNBID”. In some example embodiments, this configuration may also indicate type information corresponding to at least one node identifier, which may specifically be the type of relay node 304. For example, OAM 408 may configure a mapping of at least one node identifier “mwabgNBID”, an indication “mwabgNBIndication”, and type information “mwabType” in the AMF.

[0099] At 456, AMF 402 stores a mapping of at least one node identifier “mwabgNBID”, indicator “mwabgNBIndication”, and type information “mwabType” received from OAM.

[0100] At 458, terminal device 302 sends a registration request to the network component of relay node 304. At 460, relay node 304 may then send a message related to terminal device 302 to AMF 402. This message may, for example, be an initial UE message. This message may include the node identifier of the network component of the relay node.

[0101] Based on the determination that the received node identifier matches the node identifier in the stored mapping, AMF 402 can determine that the network node connected to terminal device 302 is relay node 304. Then, at 462, AMF 402 sends a charging data request to CHF 303. The charging data request may include the indication "wabgNBIndication". If AMF 402 is notified of type information, the charging data request sent to CHF 303 may also include type information.

[0102] At 464, upon receiving the indication “wabgNBIndication” from AMF 402, CHF 303 determines a charging data request for terminal device 302 connected via the network component of the relay node, and charges terminal device 302, for example, according to the SLA. At 466, CHF 303 sends a charging data response to AMF 402.

[0103] This can be referenced above. Figure 4A The similar methods for initiating billing data triggers and differentiated billing discussed will not be described in detail here.

[0104] In option E, the PCF is configured or provided with a policy associated with at least one node identifier of at least one of the network components of (multiple) relay nodes, such as (multiple) MWAB-gNBID. The PCF may send policy information to the AMF including an indication of “mwabgNBIndication”, which indicates that the network node to which the terminal device 302 is connected is a relay node 304. In some example embodiments, the policy information received by the AMF 402 may also include type information indicating the type of relay node 304, which is represented as “mwabType” for relay nodes that are WAB nodes.

[0105] Figure 4E An example signaling flow 400E for charging a terminal device 302 connected to a relay node 304, according to option E, is shown. Signaling flow 400E involves the terminal device 302, the relay node 304 (e.g., a WAB node or an IAB node), AMF 402, CHF 303, and PCF 409. AMF 402 can be... Figure 3 Examples of CTF 301 in the example.

[0106] At 468, terminal device 302 sends a registration request to the network component of relay node 304. At 470, relay node 304 may then send a message related to terminal device 302 to AMF 402. This message may, for example, be an initial UE message. The message related to terminal device 302 may include the node identifier "mwabgNBID" of relay node 304.

[0107] At position 472, AMF 402 sends a policy control request to PCF 409, including the node identifier "mwabg NBID" of relay node 304. The policy control request can be, for example, an Npcf_AMPolicy_Control_Create request message.

[0108] When PCF 409 receives a policy control request from AMF 402, PCF 409 determines the policy information to return based on the configured policy. This policy information indicates that the network node to which terminal device 302 is connected is relay node 304. If PCF 409 is also configured or provided with type information for relay node 304, PCF 409 can also return type information.

[0109] At 476, AMF 402 receives a policy control response from PCF 409. This policy control response includes a node identifier “mwabgNBID” and an indication “mwabgNBIndication” indicating that the network node to which terminal device 302 is connected is relay node 304, as well as possible type information of relay node 304. The policy control response may be, for example, an Npcf_AMPolicy Control_Create response message.

[0110] AMF 402 can determine, based on the indications included in the policy control response, that the network node to which the terminal device 302 is connected is a relay node 304, and possibly the type information of the relay node 304.

[0111] At 478, AMF 402 stores a mapping of node identifiers, indications, and type information for relay nodes, such as the mapping of node identifier “MWAB-gNBID”, indication “wabgNBIndication”, and type information “mwabType” received from PCF 409.

[0112] To trigger billing on terminal device 302, at 480, AMF 402 sends a billing data request to CHF 303. The billing data request may include the indication "wabgNBIndication". If AMF 402 is notified of type information, the billing data request sent to CHF 303 may also include type information.

[0113] At 482, upon receiving the indication “wabgNBIndication” from AMF 402, CHF 303 determines a charging data request for terminal device 302 connected via the network component of the relay node, and charges terminal device 302, for example, according to the SLA. At 484, CHF 303 sends a charging data response to AMF 402.

[0114] This can be referenced above. Figure 4A The similar methods for initiating billing data triggers and differentiated billing discussed will not be described in detail here.

[0115] Figures 5A-5F Example signaling flows 500A-500F for charging terminal devices connected to a relay node, according to some example embodiments associated with SMF, are shown. Signaling flows 500A-500F can be considered as... Figure 3 An example embodiment of signaling flow 300, wherein CTF 301 is implemented as SMF. For example... Figures 5A-5F As shown, six options are provided to determine whether the terminal device is connected via a relay node.

[0116] In option A, the setup process is used to notify the AMF terminal device to connect via the network components of the relay node (e.g., WAB-gNB), and then the AMF can provide this information to the SMF.

[0117] Figure 5A Example signaling flow 500A for billing of terminal device 302 connected to relay node 304 according to option A is shown. Signaling flow 500A involves terminal device 302, relay node 304 (e.g., WAB node or IAB node), AMF 402, SMF 502, and CHF 303. SMF 502 may be Figure 3 Examples of CTF 301 in the example.

[0118] like Figure 5A As shown, the AMF 402 first determines that the network node connected to the terminal device 302 is a relay node 304, and obtains the type information of the relay node 304, such as... Figure 4A Option A is shown.

[0119] Specifically, at 510, AMF 402 receives an establishment request from the network node to which terminal device 302 is connected (in this case, from the network component of relay node 304). The establishment request may include an NG establishment request message. The establishment request includes an indication that the network node to which terminal device 302 is connected is relay node 304. That is, relay node 304 can notify AMF 402 that it is the relay node to which terminal device 302 is connecting when establishing a connection with AMF 402. Such an indication for a relay node that is a WAB node can be represented as "wabgNBIndication".

[0120] In some example embodiments, the establishment request may also include type information indicating the type of relay node 304, which is represented as "mwabType" for relay nodes that are WAB nodes.

[0121] Thus, AMF 402 can determine that the network node to which terminal device 302 is connected is relay node 304 based on the indication "wabgNBIndication" included in the establishment request. If type information is included in the establishment request, AMF 402 can also determine the type of relay node 304. At 511, AMF 402 sends an establishment response, such as an NG establishment response, to relay node 304.

[0122] In response to the PDU session establishment request from terminal device 302 at 512, at 513, AMF 402 sends a session context creation request to SMF 502. AMF 402 may include an indication "wabgNBIndication" in the session context creation request, which indicates that the network node to which the terminal device is connected is a relay node. In some examples, the session context creation request may also include the type information "mwabType" of the relay node 304. In some examples, the session context creation request may be, for example, an Nsmf_PDUSession_Create SMContext request message.

[0123] SMF 502 can determine that the network node to which the terminal device is connected is a relay node based on the indication included in the session context creation request. At 514, SMF 502 sends a session context creation response, such as an Nsmf_PDUSession_Create SMContext response message, to AMF 402.

[0124] At 515, SMF 502 stores a mapping of node identifiers, indications, and type information for relay nodes, such as a mapping of node identifier “MWAB-gNBID”, indication “wabgNBIndication”, and type information “mwabType”.

[0125] To trigger billing for terminal device 302, SMF 502 can use the node identifier of the network node to which terminal device 302 is connected to determine the indication "wabgNBIndication" and type information "mwabType" from the stored mapping. Note that billing for terminal device 302 can be triggered by SMF 502 through any suitable event.

[0126] Then at 516, SMF 502 sends a billing data request to CHF 303. The billing data request may include the indication "wabgNBIndication". If type information is notified to SMF 502, the billing data request sent to CHF 303 may also include type information.

[0127] At point 517, upon receiving the indication "wabgNBIndication" from SMF 502, CHF 303 determines a charging data request for terminal device 302 connected via a network component of a relay node, and charges terminal device 302, for example, according to the SLA. For example, the charging for terminal devices connected via a network component of a relay node may be less than that for normally connected terminal devices. Note that differentiated charging for terminal devices connected via a network component of a relay node and charging for terminal devices connected via normally connected RAN network nodes can be configured as needed, and this is not limited to the scope of this disclosure.

[0128] At position 518, CHF 303 sends a billing data response to SMF 502.

[0129] Then at 519, differentiated billing can be applied to terminal devices connected via network components of relay nodes (e.g., WAB-gNB).

[0130] In option B, the UL Non-Access Layer (NAS) transmission message is used to notify the AMF end device that it is connected through the network component of the relay node (e.g., WAB-gNB), and then the AMF can provide such information to the SMF.

[0131] Figure 5B An example signaling flow 500B for billing a terminal device 302 connected to relay node 304 according to option B is shown. Signaling flow 500B involves terminal device 302, relay node 304 (e.g., a WAB node or IAB node), AMF 402, SMF 502, and CHF 303. SMF 502 can be... Figure 3 Examples of CTF 301 in the example.

[0132] like Figure 5B As shown, the first step is for AMF 402 to determine that the network node connected to the terminal device 302 is the relay node 304.

[0133] At point 521, terminal device 302 sends a PDU session establishment or service request to the network component (e.g., WAB-gNB) of relay node 304.

[0134] At 522, the network component of relay node 304 sends a UL NAS transport message to AMF 402 by including an indication “mwabgNBIndication” indicating that the network node to which terminal device 302 is connected is relay node 304. In some example embodiments, the UL NAS transport message may also include type information indicating the type of relay node 304, which is represented as “mwabType” for relay nodes that are WAB nodes.

[0135] Then, similar to the operations at 513, 514, and 515 in signaling flow 500A, at 523, 524, and 525, AMF402 notifies the SMF of the indication “mwabgNBIndication” and possibly the type information “mwabType”. SMF 502 stores a mapping of the relay node's node identifier, indication, and type information; for example, a mapping of the node identifier “MWAB-gNBID”, the indication “wabgNBIndication”, and the type information “mwabType”.

[0136] To trigger billing in terminal device 302, at 526, SMF 502 sends a billing data request to CHF 303. The billing data request may include the indication "wabgNBIndication". If SMF 502 is notified of type information, the billing data request sent to CHF 303 may also include type information.

[0137] At 527, upon receiving the indication “wabgNBIndication” from SMF 502, CHF 303 determines a charging data request for terminal device 302 connected via the network component of the relay node, and charges terminal device 302, for example, according to the SLA. At 528, CHF 303 sends a charging data response to SMF 502.

[0138] Then at 529, differentiated billing can be applied to terminal devices connected via network components of relay nodes (e.g., WAB-gNB).

[0139] This can be referenced above. Figure 5A The similar methods for initiating billing data triggers and differentiated billing discussed will not be described in detail here.

[0140] In option C, the OAM configuration maps the node identifier "mwabgNBID", the indicator "mwabgNBIndication", and the type information "mwabType" in the AMF. The AMF can send such information to the SMF, for example, as part of the session context creation process.

[0141] Figure 5C Example signaling flow 500 C is shown for billing of terminal device 302 connected to relay node 304 according to option C. Signaling flow 500 C involves terminal device 302, relay node 304 (e.g., WAB node or IAB node), AMF 402, SMF 502, CHF 303, and OAM 508. SMF 502 can be... Figure 3 Examples of CTF 301 in the example.

[0142] like Figure 5C As shown, the first step is for AMF 402 to determine that the network node connected to the terminal device 302 is the relay node 304.

[0143] In signaling flow 500C, at point 531, AMF 402 receives configuration from OAM 508, which indicates that billing for terminal device 302 connected to relay node 304 will be performed using at least one node identifier “mwabgNBID”. In some example embodiments, this configuration may also indicate type information corresponding to at least one node identifier, which may specifically be the type of relay node 304. For example, OAM 508 may configure a mapping in the AMF for at least one node identifier “mwabgNBID” for the backhaul, an indication “mwabgNBIndication”, and type information “mwabType”.

[0144] At 532, AMF 402 stores a mapping of at least one node identifier “mwabgNBID”, indicator “mwabgNBIndication”, and type information “mwabType” received from OAM.

[0145] Then, similar to the operations at 521 to 525 in signaling flow 500B, at 533 to 537, the SMF obtains and stores a mapping of node identifiers, indications, and type information of relay nodes from the AMF 402, such as the mapping of node identifier “MWAB-gNBID”, indication “wabgNBIndication”, and type information “mwabType”.

[0146] To trigger billing by terminal device 302, at 538, SMF 502 sends a billing data request to CHF 303. The billing data request may include the indication "wabgNBIndication". If SMF 502 is notified of type information, the billing data request sent to CHF 303 may also include type information.

[0147] At 539, upon receiving the indication “wabgNBIndication” from SMF 502, CHF 303 determines a charging data request for terminal device 302 connected via the network component of the relay node, and charges terminal device 302, for example, according to the SLA. At 540, CHF 303 sends a charging data response to SMF 502.

[0148] Then at 541, differentiated billing can be applied to terminal devices connected via network components of relay nodes (e.g., WAB-gNB).

[0149] This can be referenced above. Figure 5A The similar methods for initiating billing data triggers and differentiated billing discussed will not be described in detail here.

[0150] In option D, compared to option C, the SMF is provided with a mapping of MWAB-gNBID and mwabgNBIndication, which in turn sends this information to the CHF as part of the billing data request.

[0151] Figure 5D An example signaling flow 500D for billing a terminal device 302 connected to a relay node 304, according to option D, is shown. Signaling flow 500D involves the terminal device 302, the relay node 304 (e.g., a WAB node or an IAB node), AMF 402, SMF 502, CHF 303, and OAM 508. SMF 502 can be... Figure 3 Examples of CTF 301 in the example.

[0152] In signaling flow 500D, at 542, SMF 502 receives configuration from OAM 508, which indicates that billing for terminal device 302 connected to relay node 304 will be performed using at least one node identifier “mwabg NBID”. In some example embodiments, this configuration may also indicate type information corresponding to at least one node identifier, which may specifically be the type of relay node 304. For example, OAM 508 may configure a mapping in the AMF for at least one node identifier “mwabgNBID” for backhaul, an indication “mwabgNBIndication”, and type information “mwabType”.

[0153] At 543, SMF 502 stores a mapping of at least one node identifier “mwabgNBID”, indicator “mwabgNBIndication”, and type information “mwabType” received from OAM.

[0154] At point 544, terminal device 302 sends a PDU session establishment or service request to the network component (e.g., WAB-gNB) of relay node 304.

[0155] At 545, the network component of relay node 304 sends a UL NAS transmission message to AMF 402, which may include the node identifier of the relay node to which the terminal device 302 is connected.

[0156] At point 546, AMF 402 sends a session context creation request to SMF 502, which can be, for example, an Nsmf_PDUS ession_Create SMContext request message. At point 547, SMF 502 sends a session context creation response to AMF 402, such as an Nsmf_PDUS ession_Create SMContext response message.

[0157] Since SMF 502 stores a mapping of at least one node identifier “mwabgNBID”, indication “mwabgNBIndication”, and type information “mwabType” received from OAM to trigger billing by terminal device 302, at 548, SMF 502 sends a billing data request to CHF 303. The billing data request may include the indication “wabgNBIndication”. If SMF 502 is notified of type information, the billing data request sent to CHF 303 may also include type information.

[0158] At 549, upon receiving the indication “wabgNBIndication” from SMF 502, CHF 303 determines a charging data request for terminal device 302 connected via the network component of the relay node, and charges terminal device 302, for example, according to the SLA. At 550, CHF 303 sends a charging data response to SMF 502.

[0159] Then at 551, differentiated billing can be applied to terminal devices connected via network components of relay nodes (e.g., WAB-gNB).

[0160] This can be referenced above. Figure 5A The similar methods for initiating billing data triggers and differentiated billing discussed will not be described in detail here.

[0161] In option E, the UDM / UDR can be provided with a mapping of at least one node identifier "mwabgNBID", an indication "mwabgNBIndication", and type information "mwabType". The AMF can use the node identifier to query this type of information for a specific relay node. The AMF can send this type of information to the SMF.

[0162] Figure 5EAn example signaling flow 500E for billing a terminal device 302 connected to a relay node 304, according to option E, is shown. Signaling flow 500E involves the terminal device 302, the relay node 304 (e.g., a WAB node or an IAB node), AMF 402, SMF 502, CHF 303, and UDM / UDR 404. SMF 502 can be... Figure 3 Examples of CTF 301 in the example.

[0163] In signaling flow 500E, at position 552, UDM / UDR 404 is provided with a mapping of node identifier “mwabgNBID”, indicator “mwabgNBIndication”, and type information “mwabType”.

[0164] AMF 402 can obtain the node identifier of the network node to which terminal device 302 is connected. Specifically, at 553, terminal device 302 sends a PDU session establishment request or service request to the network component of relay node 304. At 554, relay node 304 can then send a message related to terminal device 302 to AMF 402. This message may, for example, be a UL NAS transport message. The message related to terminal device 302 may include the node identifier "mwabgNBID" of relay node 304.

[0165] At position 555, the AMF sends an information retrieval request to UDM / UDR 404, including the node identifier "mwabgNBID" of the network node. The information retrieval request may include a request to retrieve gNB information.

[0166] In response to the information retrieval request, at 556, UDM / UDR 404 may send back an information retrieval response including the node identifier "mwabgNBID" and an indication "wabgNBIndication" indicating that the network node to which terminal device 302 is connected is relay node 304. The information retrieval response may, for example, be a gNB information retrieval response.

[0167] In some example embodiments, the information retrieval response may also include type information indicating the type of relay node 304, which is represented as "mwabType" for relay nodes that are WAB nodes.

[0168] Then, at 557, AMF 402 sends a session context creation request to SMF 502. AMF 402 may include the indication "wabgNBIndication" in the session context creation request, which indicates that the network node the terminal device is connected to is a relay node. In some examples, the session context creation request may also include the type information "mwabType" of the relay node 304. In some examples, the session context creation request may be, for example, an Nsmf_PDUS session_CreateSMContext request message.

[0169] SMF 502 can determine whether the network node to which the terminal device is connected is a relay node based on the indications included in the session context creation request. At 558, SMF 502 sends a session context creation response, such as an Nsmf_PDUSession_Create SMContext response message, to AMF 402.

[0170] At 559, SMF 502 stores a mapping of node identifiers, indications, and type information for relay nodes, such as a mapping of node identifier “MWABgNBID”, indication “wabgNBIndication”, and type information “mwabType”.

[0171] To trigger billing on terminal device 302, at 560, SMF 502 sends a billing data request to CHF 303. The billing data request may include the indication "wabgNBIndication". If SMF 502 is notified of type information, the billing data request sent to CHF 303 may also include type information.

[0172] At point 561, upon receiving the indication “wabgNBIndication” from SMF 502, CHF 303 determines a charging data request for terminal device 302 connected via the network component of the relay node, and charges terminal device 302, for example, according to the SLA. At point 562, CHF 303 sends a charging data response to SMF 502.

[0173] Then at 563, differentiated billing can be applied to terminal devices connected via network components of relay nodes (e.g., WAB-gNB).

[0174] This can be referenced above. Figure 5A The similar methods for initiating billing data triggers and differentiated billing discussed will not be described in detail here.

[0175] In option F, the UDM / UDR can be provided with a mapping of at least one node identifier "mwabgNBID", an indication "mwabgNBIndication", and type information "mwabType". The SMF can use the node identifier to query this type of information for a specific relay node and send it to the CHF in a billing data request.

[0176] Figure 5F An example signaling flow 500F for charging a terminal device 302 connected to a relay node 304 according to option F is shown. Signaling flow 500F involves the terminal device 302, the relay node 304 (e.g., a WAB node or an IAB node), AMF 402, SMF 502, CHF 303, and UDM / UDR 404. SMF 502 can be... Figure 3 Examples of CTF 301 in the example.

[0177] In signaling flow 500F, at position 564, UDM / UDR 404 is provided with a mapping of node identifier “mwabgNBID”, indicator “mwabgNBIndication”, and type information “mwabType”.

[0178] SMF 502 can obtain the node identifier of the network node to which terminal device 302 is connected. Specifically, at 565, terminal device 302 sends a PDU session establishment request or service request to the network component of relay node 304. At 566, relay node 304 can then send a message related to terminal device 302 to AMF 402. This message may be, for example, a UL NAS transport message. The message related to terminal device 302 may include the node identifier "mwabgNBID" of relay node 304.

[0179] At point 567, AMF 402 sends a session context creation request to SMF 502. AMF 402 may include the relay node's node identifier "mwabgNBID" in the session context creation request. In some examples, the session context creation request may be, for example, an Nsmf_PDUS ession_Create SMContext request message. At point 568, SMF 502 sends a session context creation response to AMF 402, such as an Nsmf_PDUS ession_Create SMContext response message.

[0180] At position 569, SMF 502 sends an information retrieval request to UDM / UDR 404, including the node identifier "mwabgNBID" of the network node. The information retrieval request may include a request to retrieve gNB information.

[0181] In response to the information retrieval request, at 570, UDM / UDR 404 may send back an information retrieval response including the node identifier "mwabgNBID" and an indication "wabgNBIndication" indicating that the network node to which terminal device 302 is connected is relay node 304. The information retrieval response may, for example, be a gNB information retrieval response.

[0182] In some example embodiments, the information retrieval response may also include type information indicating the type of relay node 304, which is represented as "mwabType" for relay nodes that are WAB nodes.

[0183] At 571, SMF 502 stores a mapping of node identifiers, indications, and type information for relay nodes, such as a mapping of node identifier “MWABgNBID”, indication “wabgNBIndication”, and type information “mwabType”.

[0184] To trigger billing in terminal device 302, at 572, SMF 502 sends a billing data request to CHF 303. The billing data request may include the indication "wabgNBIndication". If SMF 502 is notified of type information, the billing data request sent to CHF 303 may also include type information.

[0185] At 573, upon receiving the indication “wabgNBIndication” from SMF 502, CHF 303 determines a charging data request for terminal device 302 connected via the network component of the relay node, and charges terminal device 302, for example, according to the SLA. At 574, CHF 303 sends a charging data response to SMF 502.

[0186] Then at 575, differentiated billing can be applied to terminal devices connected via network components of relay nodes (e.g., WAB-gNB).

[0187] This can be referenced above. Figure 5A The similar methods for initiating billing data triggers and differentiated billing discussed will not be described in detail here.

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

[0189] Figure 6A 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 context of CTF.

[0190] At box 610, the first device determines that the network node to which the terminal device is connected is a relay node.

[0191] At box 620, the first device sends a billing data request for a terminal device to a third device configured to provide billing functionality. The billing data request includes an indication that the network node to which the terminal device is connected is a relay node.

[0192] In some example embodiments, method 600 further includes: receiving an establishment request from a network node to which the terminal device is connected, the establishment request including an indication that the network node to which the terminal device is connected is a relay node; and determining, based on the indication included in the establishment request, that the network node to which the terminal device is connected is a relay node.

[0193] In some exemplary embodiments, the establishment request further includes type information indicating the type of relay node; and the billing data request further includes the type information included in the establishment request.

[0194] In some example embodiments, method 600 further includes: receiving a message related to the terminal device from a network node to which the terminal device is connected, the message including an indication that the network node to which the terminal device is connected is a relay node; and determining, based on the indication included in the message, that the network node to which the terminal device is connected is a relay node.

[0195] In some example embodiments, the message associated with the terminal device also includes type information indicating the type of the relay node; and the billing data request also includes the type information included in the message associated with the terminal device.

[0196] In some example embodiments, method 600 further includes: obtaining a first node identifier of a network node to which the terminal device is connected; sending an information retrieval request to a fourth device configured to provide unified data management or repository functions, the information retrieval request including the first node identifier of the network node; receiving an information retrieval response from the fourth device, the information retrieval response including an indication that the network node to which the terminal device is connected is a relay node; and determining, based on the indication included in the information retrieval response, that the network node to which the terminal device is connected is a relay node.

[0197] In some example embodiments, method 600 further includes: receiving a message related to the terminal device from a network node to which the terminal device is connected, the message including a cell group identifier (CGI) for the network node; and obtaining a first node identifier of the network node from the CGI included in the message.

[0198] In some exemplary embodiments, the information retrieval response further includes type information indicating the type of the relay node; and the billing data request further includes the type information included in the information retrieval response.

[0199] In some example embodiments, method 600 further includes: 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; receiving a first node identifier of a network node to which the terminal device is connected; and 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.

[0200] In some example embodiments, method 600 further includes: determining a billing data request to include network node type information based on determining that a first node identifier matches at least one second node identifier indicated by a first configuration.

[0201] In some example embodiments, method 600 further includes: receiving a message related to the terminal device from a network node to which the terminal device is connected, the message including a first node identifier of the network node; sending 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; receiving a policy control response from the second device, the policy control response including an indication that the network node to which the terminal device is connected is a relay node; and determining, based on the indication included in the policy control response, that the network node to which the terminal device is connected is a relay node.

[0202] In some example embodiments, the policy control response also includes type information indicating the type of the relay node; and the billing data request also includes the type information included in the policy control response.

[0203] In some example embodiments, the first device is configured to provide access and mobility management functions.

[0204] In some example embodiments, the first device is configured to provide session management functionality.

[0205] In some example embodiments, method 600 further includes: receiving a session context creation request from a device configured to provide access and mobility management functions, the session context creation request including an indication that the network node to which the terminal device is connected is a relay node; and determining, based on the indication included in the session context creation request, that the network node to which the terminal device is connected is a relay node.

[0206] In some example embodiments, the session context creation request also includes type information indicating the type of the relay node; and the billing data request also includes the type information included in the session context creation request.

[0207] In some example embodiments, relay nodes include wireless access and backhaul (WAB) nodes or integrated access and backhaul (IAB) nodes.

[0208] Figure 7 A 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... Figure 4E PCF 409 in the middle.

[0209] At box 710, the second device receives a second configuration indicating that billing for terminal devices connected to the relay node will be performed using at least one second node identifier.

[0210] At box 720, the second device receives a policy control request from the first device configured to provide access and mobility management functions or session management functions. The policy control request includes a first node identifier of the network node to which the terminal device is connected.

[0211] At box 730, based on determining that a first node identifier matches at least one second node identifier indicated by a second configuration, the second device sends a policy control response to the first device, the policy control response including an indication that the network node to which the terminal device is connected is a relay node.

[0212] In some example embodiments, the policy control response also includes type information indicating the type of relay node.

[0213] In some example embodiments, method 700 further includes: determining a policy control response to include type information for the network node based on determining that a first node identifier matches at least one second node identifier indicated by a second configuration.

[0214] In some example embodiments, relay nodes include wireless access and backhaul (WAB) nodes or integrated access and backhaul (IAB) nodes.

[0215] Figure 8A 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.

[0216] At box 810, the third device receives a billing data request for a terminal device from a first device configured to provide access and mobility management functions or session management functions. The billing data request includes an indication that the network node to which the terminal device is connected is a relay node.

[0217] At box 820, the third device performs billing for the terminal devices based on a policy associated with the terminal devices connected to the relay node.

[0218] In some example embodiments, method 800 further includes: performing billing for the terminal device based on a Service Level Agreement (SLA) corresponding to the type of the relay node.

[0219] In some example embodiments, relay nodes include wireless access and backhaul (WAB) nodes or integrated access and backhaul (IAB) nodes.

[0220] In some example embodiments, a first means capable of performing any method in method 600 (e.g., Figure 3 The 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 In CTF301.

[0221] In some example embodiments, the first device includes: components for determining that the network node to which the terminal device is connected is a relay node; and components for sending a billing data request for the terminal device to a third device configured to provide billing functions, the billing data request including an indication that the network node to which the terminal device is connected is a relay node.

[0222] In some example embodiments, the first apparatus further includes: a component for receiving an establishment request from a network node to which the terminal device is connected, the establishment request including an indication that the network node to which the terminal device is connected is a relay node; and a component for determining, based on the indication included in the establishment request, that the network node to which the terminal device is connected is a relay node.

[0223] In some exemplary embodiments, the establishment request further includes type information indicating the type of relay node; and the billing data request further includes the type information included in the establishment request.

[0224] In some example embodiments, the first apparatus further includes: a component for receiving a message related to the terminal device from a network node to which the terminal device is connected, the message including an indication that the network node to which the terminal device is connected is a relay node; and a component for determining, based on the indication included in the message, that the network node to which the terminal device is connected is a relay node.

[0225] In some example embodiments, the message associated with the terminal device also includes type information indicating the type of the relay node; and the billing data request also includes the type information included in the message associated with the terminal device.

[0226] In some example embodiments, the first apparatus further includes: a component for obtaining a first node identifier of a network node to which the terminal device is connected; a component for sending an information retrieval request to a fourth apparatus configured to provide unified data management or repository functions, the information retrieval request including the first node identifier of the network node; a component for receiving an information retrieval response from the fourth apparatus, the information retrieval response including an indication that the network node to which the terminal device is connected is a relay node; and a component for determining, based on the indication included in the information retrieval response, that the network node to which the terminal device is connected is a relay node.

[0227] In some example embodiments, the first apparatus further includes: a component for receiving a message related to the terminal device from a network node to which the terminal device is connected, the message including a cell group identifier (CGI) of the network node; and a component for obtaining a first node identifier of the network node from the CGI included in the message.

[0228] In some exemplary embodiments, the information retrieval response further includes type information indicating the type of relay node; and the billing data request further includes the type information included in the information retrieval response.

[0229] In some example embodiments, the first apparatus further includes: components for receiving a first configuration indicating that billing for a terminal device connected to the relay node will be performed using at least one second node identifier; components for receiving a first node identifier of a network node from which the terminal device is connected; and components 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.

[0230] In some example embodiments, the first apparatus further includes: determining a billing data request that also includes network node type information based on determining that a first node identifier matches at least one second node identifier indicated by a first configuration.

[0231] In some example embodiments, the first apparatus further includes: components for receiving a message related to the terminal device from a network node to which the terminal device is connected, the message including a first node identifier of the network node; components for sending a policy control request to a second apparatus configured to provide policy and control functions, the policy control request including the first node identifier of the network node; components for receiving a policy control response from the second apparatus, the policy control response including an indication that the network node to which the terminal device is connected is a relay node; and components for determining, based on the indication included in the policy control response, that the network node to which the terminal device is connected is a relay node.

[0232] In some example embodiments, the policy control response also includes type information indicating the type of the relay node; and the billing data request also includes the type information included in the policy control response.

[0233] In some example embodiments, the first device is configured to provide access and mobility management functions.

[0234] In some example embodiments, the first device is configured to provide session management functionality.

[0235] In some example embodiments, the first apparatus further includes: a component for receiving a session context creation request from an apparatus configured to provide access and mobility management functions, the session context creation request including an indication that the network node to which the terminal device is connected is a relay node; and a component for determining, based on the indication included in the session context creation request, that the network node to which the terminal device is connected is a relay node.

[0236] In some example embodiments, the session context creation request also includes type information indicating the type of the relay node; and the billing data request also includes the type information included in the session context creation request.

[0237] In some example embodiments, relay nodes include wireless access and backhaul (WAB) nodes or integrated access and backhaul (IAB) nodes.

[0238] In some example embodiments, a second means capable of performing any method in method 700 (e.g., Figure 4E PCF 409 in the diagram 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... Figure 4E In PCF 409.

[0239] In some example embodiments, the second apparatus includes: a component for receiving a second 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 receiving a policy control request from a first apparatus configured to provide access and mobility management functions or session management functions, the policy control request including a first node identifier of a network node to which the terminal device is connected; and a component for sending a policy control response to the first apparatus based on determining that the first node identifier matches at least one second node identifier indicated by the second configuration, the policy control response including an indication that the network node to which the terminal device is connected is a relay node.

[0240] In some example embodiments, the policy control response also includes type information indicating the type of relay node.

[0241] In some example embodiments, the second apparatus further includes a component for determining a policy control response to include type information for the network node based on determining that a first node identifier matches at least one second node identifier indicated by a second configuration.

[0242] In some example embodiments, relay nodes include wireless access and backhaul (WAB) nodes or integrated access and backhaul (IAB) nodes.

[0243] In some example embodiments, a third means (e.g., capable of performing any method in method 800) Figure 3 CHF 303 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.

[0244] In some example embodiments, the third means includes components for receiving a billing data request for a terminal device from a first means configured to provide access and mobility management functions or session management functions, the billing data request including an indication that the network node to which the terminal device is connected is 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.

[0245] In some example embodiments, the third apparatus further includes a component for performing billing of the terminal device based on a Service Level Agreement (SLA) corresponding to the type of relay node.

[0246] In some example embodiments, relay nodes include wireless access and backhaul (WAB) nodes or integrated access and backhaul (IAB) nodes.

[0247] Figure 9This is a simplified block diagram of a device 900 suitable for implementing an example embodiment of the present disclosure. The device 900 can be provided to implement a communication device, for example, such as... Figure 3 , Figures 4A-4E and Figures 5A-5F The CTF 301, CHF 303, PCF, OAM, etc. are shown. As shown in the figure, 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.

[0248] 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.

[0249] 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.

[0250] 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.

[0251] 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.

[0252] The exemplary embodiments of this disclosure can be implemented by program 930, enabling device 900 to perform as described in the reference. Figures 3 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.

[0253] 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).

[0254] 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.

[0255] 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.

[0256] 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.

[0257] 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.

[0258] 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.

[0259] 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.

[0260] 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.

[0261] 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: Determine that the network node the terminal device is connected to is a relay node; as well as A billing data request for the terminal device is sent to a third device configured to provide billing functionality. The billing data request includes an indication that the network node to which the terminal device is connected is the relay node.

2. The first device according to claim 1, wherein the first device is configured to: Receive an establishment request from the network node to which the terminal device is connected, the establishment request including an indication that the network node to which the terminal device is connected is the relay node; and Based on the indication included in the establishment request, it is determined that the network node to which the terminal device is connected is the relay node.

3. The first apparatus according to claim 2, wherein the establishment request further includes type information indicating the type of the relay node; and The billing data request also includes the type information included in the setup request.

4. The first device according to claim 1, wherein the first device is configured to: Receive a message related to the terminal device from the network node to which the terminal device is connected, the message including an indication that the network node to which the terminal device is connected is the relay node; and Based on the indication included in the message, it is determined that the network node to which the terminal device is connected is the relay node.

5. The first apparatus of claim 4, wherein the message associated with the terminal device further includes type information indicating the type of the relay node; and The billing data request also includes the type information included in the message associated with the terminal device.

6. The first device according to claim 1, wherein the first device is configured to: Obtain the first node identifier of the network node to which the terminal device is connected; Send an information retrieval request to a fourth device configured to provide unified data management or repository functions, the information retrieval request including the first node identifier of the network node; Receive an information retrieval response from the fourth device, the information retrieval response including an indication that the network node to which the terminal device is connected is the relay node; and Based on the indication included in the information retrieval response, it is determined that the network node to which the terminal device is connected is the relay node.

7. The first device according to claim 6, wherein the first device is configured such that: Receive a message related to the terminal device from the network node to which the terminal device is connected, the message including a cell group identifier (CGI) for the network node; The first node identifier of the network node is obtained from the CGI included in the message.

8. The first apparatus according to claim 6 or 7, wherein the information retrieval response further includes type information indicating the type of the relay node; and The billing data request also includes the type information included in the information retrieval response.

9. 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; Receive the first node identifier of the network node from the network node to which the terminal device is connected; as well as 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.

10. The first apparatus of claim 9, wherein the first configuration further indicates type information corresponding to the at least one second node identifier, the type information indicating the type of the relay node, and The first device is further configured to: Based on determining that the first node identifier matches the at least one second node identifier indicated by the first configuration, the billing data request is determined to also include the type information of the network node.

11. The first device according to claim 1, wherein the first device is configured to: Receive a message related to the terminal device from the network node to which the terminal device is connected; the message includes a first node identifier of the network node. 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; Receive a policy control response from the second device, the policy control response including an indication that the network node to which the terminal device is connected is the relay node; and Based on the indication included in the policy control response, it is determined that the network node to which the terminal device is connected is the relay node.

12. The first apparatus of claim 11, wherein the policy control response further includes type information indicating the type of the relay node; and The charging data request also includes the type information included in the policy control response.

13. The first device according to any one of claims 1 to 7 or any one of claims 9 to 12, wherein the first device is configured to provide access and mobility management functions.

14. The first apparatus according to claim 6, 7, 9 or 10, wherein the first apparatus is configured to provide session management functionality.

15. The first apparatus of claim 1, wherein the first apparatus is configured to provide session management functionality, and the first apparatus is such that: A session context creation request is received from a device configured to provide access and mobility management functions, the session context creation request including an indication that the network node to which the terminal device is connected is the relay node; and Based on the indication included in the session context creation request, it is determined that the network node to which the terminal device is connected is the relay node.

16. The first apparatus of claim 15, wherein the session context creation request further includes type information indicating the type of the relay node; and The billing data request also includes the type information included in the session context creation request.

17. The first apparatus according to any one of claims 1 to 7, any one of claims 9 to 12, or any one of claims 15 to 16, wherein the relay node comprises a wireless access and backhaul (WAB) node or an integrated access and backhaul (IAB) node.

18. A method for communication, comprising: Determine that the network node the terminal device is connected to is a relay node; as well as A billing data request for the terminal device is sent to a third device configured to provide billing functionality. The billing data request includes an indication that the network node to which the terminal device is connected is the relay node.

19. A computer-readable medium having instructions stored thereon for causing a device to perform at least the method according to claim 18.

Images