Billing of terminal components of relay nodes

Abstract

Example embodiments of this disclosure relate to billing of terminal components of a relay node. One method includes: receiving first slice information associated with a terminal device; and sending a billing data request including the first S-NSSAI to a third device configured to provide billing functionality, based on determining that first single network slice selection assistance information included in the first slice information matches at least one second S-NSSAI included in second slice information, wherein the second slice information includes at least one S-NSSAI configured to serve terminal components of a relay node.

Description

Technical Field

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

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

[0003] In a first aspect of this disclosure, a first apparatus is provided. The first apparatus includes: at least one processor; and at least one memory storing instructions, which, when executed by the at least one processor, cause the first apparatus to at least: receive first slice information associated with a terminal device; and, based on determining that a first single network slice selection aid information (S-NSSAI) included in the first slice information matches at least one second S-NSSAI included in second slice information, send a billing data request including the first S-NSSAI to a third apparatus configured to provide billing functionality, wherein the second slice information includes at least one S-NSSAI of a terminal component configured to serve 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 to at least: receive a configuration indicating that billing for a terminal component of a relay node will be performed using Single Network Slice Selection Auxiliary Information (S-NSSAI); receive a policy control request from a first apparatus, the policy control request including first slice information associated with the terminal device; and, based on determining that the first S-NSSAI included in the first slice information matches at least one second S-NSSAI received in the configuration, send a policy control response to the first apparatus, the policy control response indicating that billing for the terminal device will be performed using the first S-NSSAI included in the first slice information associated with the terminal device.

[0005] In a third aspect of this disclosure, a third apparatus is provided. The third apparatus includes at least one processor; and at least one memory storing instructions, which, when executed by the at least one processor, cause the third apparatus to at least: receive a charging data request from a first apparatus, the charging data request including first single network slice selection assistance information (S-NSSAI) associated with a terminal device; and perform charging based on determining that the first S-NSSAI is configured for a terminal component of a relay node, and perform charging of the terminal device according to a policy associated with the terminal component of the relay node.

[0006] In a fourth aspect of this disclosure, a method is provided. The method includes: receiving first slice information associated with a terminal device; and, based on determining that a first Single Network Slice Selection Assist Information (S-NSSAI) included in the first slice information matches at least one second S-NSSAI included in second slice information, sending a charging data request including the first S-NSSAI to a third device configured to provide charging functionality, wherein the second slice information includes at least one S-NSSAI configured to serve a terminal component of a relay node.

[0007] In a fifth aspect of this disclosure, a method is provided. The method includes: receiving a configuration indicating that billing for a terminal component of a relay node will be performed using Single Network Slice Selection Auxiliary Information (S-NSSAI); receiving a policy control request from a first device, the policy control request including first slice information associated with the terminal device; and sending a policy control response to the first device based on determining that a first S-NSSAI included in the first slice information matches at least one second S-NSSAI received in the configuration, the policy control response indicating that billing for the terminal device will be performed using the first S-NSSAI included in the first slice information associated with the terminal device.

[0008] In a sixth aspect of this disclosure, a method is provided. The method includes: receiving a charging data request from a first device, the charging data request including first single network slice selection assistance information (S-NSSAI) associated with a terminal device; and performing charging of the terminal device according to a policy associated with the terminal component of the relay node based on determining that the first S-NSSAI is configured for charging of a terminal component of a relay node.

[0009] In a seventh aspect of this disclosure, a first apparatus is provided. The first apparatus includes: components for receiving first slice information associated with a terminal device; and components for sending a billing data request including the first S-NSSAI to a third device configured to provide billing functionality based on determining that a first single network slice selection assistance information (S-NSSAI) included in the first slice information matches at least one second S-NSSAI included in second slice information, wherein the second slice information includes at least one S-NSSAI configured to serve a terminal component of a relay node.

[0010] In an eighth aspect of this disclosure, a second apparatus is provided. The second apparatus includes: components for receiving a configuration indicating that billing for a terminal component of a relay node will be performed using Single Network Slice Selection Auxiliary Information (S-NSSAI); components for receiving a policy control request from a first apparatus, the policy control request including first slice information associated with the terminal component; and components for sending a policy control response to the first apparatus based on determining that a first S-NSSAI included in the first slice information matches at least one second S-NSSAI received in the configuration, the policy control response indicating that billing for the terminal component will be performed using the first S-NSSAI included in the first slice information associated with the terminal component.

[0011] In a ninth aspect of this disclosure, a third apparatus is provided. The third apparatus includes: components for receiving a charging data request from a first apparatus, the charging data request including first single network slice selection assistance information (S-NSSAI) associated with a terminal device; and components for performing charging of the terminal device according to a policy associated with the terminal component of the relay node based on determining that the first S-NSSAI is configured for charging of a terminal component of a relay node.

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

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

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

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

[0016] Some exemplary embodiments will now be described with reference to the accompanying drawings, in which: Figure 1 An example communication environment in which example embodiments of the present disclosure may be implemented is shown; Figure 2 A schematic diagram of a user plane protocol stack for a WAB architecture according to some exemplary embodiments of the present disclosure is shown; Figure 3 The following is illustrated: a signaling flow for billing terminal components of a relay node according to some example embodiments of the present disclosure; Figure 4 Example signaling flows for charging of terminal components for relay nodes are shown according to some example embodiments associated with AMF; Figure 5 Example signaling flows for charging of terminal components for a relay node according to some example embodiments associated with SMF are shown; 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, the execution step “in response to A” does not indicate that the step is executed immediately after “A” occurs and may include one or more intermediate steps.

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

[0025] As used in this application, the term "circuit system" may refer to one or more of the following: (a) Hardware circuit implementation only (such as implementation in analog and / or digital circuits only), and (b) A combination of hardware circuitry and software, such as (if applicable): (i) A combination of (multiple) analog and / or digital hardware circuits with software / firmware, and (ii) Any part of the software of (multiple) hardware processors (including (multiple) digital signal processors) and (multiple) memories, which work together to enable a device (such as a mobile phone or server) to perform various functions, and (c) (multiple) hardware circuits and / or (multiple) processors, such as (multiple) microprocessors or a portion thereof, which require software (e.g., firmware) for operation, but the software may not exist 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 in this application, the term circuit also covers the implementation of only hardware circuitry or a processor (or multiple processors) or a portion of hardware circuitry or a processor and its 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 various 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 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, CN 160 can be the same as the CN residing in CN 140. In other scenarios, UPF 140 can be the same as UPF 150.

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

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

[0036] Communication in communication environment 100 can be implemented according to any suitable communication protocol, including but not limited to cellular communication protocols, wireless local area network communication protocols (such as IEEE 802.11), and / or any other currently known or future-developed protocols. Furthermore, communication can utilize any suitable wireless communication technology, including but not limited to: Code Division Multiple Access (CDMA), Frequency Division Multiple Access (FDMA), Time Division Multiple Access (TDMA), Frequency Division Duplex (FDD), Time Division Duplex (TDD), Multiple Input Multiple Output (MIMO), Orthogonal Frequency Division Multiple Access (OFDM), Discrete Fourier Transform Extended OFDM (DFT-s-OFDM), and / or any other currently known or future-developed technologies.

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

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

[0039] For example, the communication system needs to be able to identify and distinguish services relayed via mobile base station 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 is the procedures and triggers for billing definitions in the data connection domain. Table 1 shows the default trigger conditions in the Session Management Function (SMF). These triggers are defined as initiating a billing data request in the Charging Function (CHF). Note that many other triggers are defined, and those in Table 1 are only a subset.

[0043] Table 1

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

[0045] Table 2

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

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

[0048] According to example embodiments of this disclosure, several solutions are proposed to determine whether a terminal device to be billed is a terminal component of a relay node and to apply a differentiated billing strategy accordingly. This determination is achieved by comparing received first slice information associated with the terminal device with second slice information configured for the terminal component of the relay node.

[0049] Using the solution in this disclosure, the terminal components of a relay node can be correctly identified and billed appropriately.

[0050] Now, some example procedures will be described. Figure 3 A flowchart of a signaling flow 300 according to some example embodiments of the present disclosure is shown. For example... Figure 3 As shown, signaling flow 300 may involve Charging Trigger Function (CTF) 301, Policy and Control Function (PCF) 302, CHF 303, and Operation, Administration and Maintenance Function (OAM) 304. For discussion purposes, reference will be made to... Figure 1Discussion process 300. CTF 301, PCF 302, CHF 303, and OAM 304 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 terminal component may include the MT function of the WAB node or IAB node. The relay node may also include RAN devices or components, such as a WAB-gNB or an IAB-DU.

[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] The main concept of this solution is to reuse slice-based billing. That is, CHF 303 can perform different billing based on the slices configured for different terminal devices. Terminal devices may include typical terminal devices, such as UEs, or terminal components of relay nodes, such as WAB-MTs. CHF 303 is expected to differentiate between terminal components of relay nodes and typical terminal devices in order to bill them accordingly.

[0056] like Figure 3As shown, there are two alternative methods to determine whether a terminal device is a terminal component of a relay node. One method is to determine this in PCF 302, and the other is to determine it in CTF 301. A detailed description of these two options is provided below.

[0057] In option 1, the PCF can determine whether the terminal device is a terminal component of the relay node. For example... Figure 3 As shown, OAM304 can send (305) a configuration to PCF 302 indicating that the billing of the relay node's terminal components will be performed using S-NSSAI. PCF 302 can be configured with second slice information, which includes at least one S-NSSAI configured to serve the relay node's terminal components. PCF 302 can receive (310) this configuration.

[0058] In option 2, this determination can be achieved using CTF 301. For example... Figure 3 As shown, OAM 304 can send (315) a configuration to CTF 301 indicating that the billing of the relay node's terminal components will be performed using S-NSSAI. Similarly, CTF 301 can be configured with second slice information, which includes at least one S-NSSAI configured to serve the relay node's terminal components. CTF 301 can receive (320) this configuration.

[0059] Then, CTF 301 determines (325) the first slice information associated with the terminal device to be billed. In an example embodiment where CTF 301 is an AMF, if the terminal device is a terminal component of a relay node, it may receive the first slice information from a radio access network device (such as a donor gNB) to which the terminal device is connected. Alternatively, it may receive the first slice information from a Unified Data Management Function (UDM) or a Unified Data Repository Function (UDR). In some example embodiments, CTF 301 may also determine the first slice information associated with the terminal device to be billed independently based on information received from other network functions. For example, the AMF may determine the allowed NSSAI for the terminal device based on subscription information received from the UDM. In an example embodiment where CTF 301 is an SMF, it may receive the first slice information from the AMF.

[0060] The first slice information associated with the terminal device includes at least one First Single Network Slice Selection Auxiliary Information (S-NSSAI), which is important information for identifying and selecting a specific network slice in the 5G network. In some example embodiments, the first slice information may include at least one allowed S-NSSAI of the terminal device. In some example embodiments, the first slice information may include at least one subscribed S-NSSAI of the terminal device. The at least one subscribed S-NSSAI may be included in the terminal device's subscription information. In some example embodiments, the first slice information may include at least one configured S-NSSAI of the terminal device. In some example embodiments, the first slice information may include at least one S-NSSAI bound to a PDU session established for the terminal device.

[0061] After receiving the first slice information, CTF 301 can send (330) a policy control request including the first slice information to PCF 302. PCF can receive (335) the first slice information.

[0062] For option 1, based on determining that the first S-NSSAI included in the first slice information matches at least the second S-NSSAI received in the configuration, PCF 302 may send a policy control response (340) to CTF 301, the policy control response indicating that the terminal device's charging will be performed using the first S-NSSAI. That is, PCF 302 may compare the first S-NSSAI included in the first slice information with at least the second S-NSSAI included in the configured second slice information. If it is determined that the second slice information contains the first S-NSSAI, then PCF 302 may determine that the terminal device is a terminal component of the relay node. PCF 302 may then send a policy control response (345) to CTF 301.

[0063] For option 2, based on determining that the first S-NSSAI included in the first slice information matches at least the second S-NSSAI received in the configuration, CTF 301 can determine that the terminal device is a terminal component of the relay node.

[0064] In summary, CTF 301 can be triggered to include the first S-NSSAI in the charging data request to CHF 303 based on the configuration from OAM 304 or the policy control response from PCF 302. In another embodiment, CTF 301 can determine that the UE is a WAB-MT based on other available information (e.g., user location information). After determination, CTF 301 can include the first S-NSSAI in the charging data request to CHF 303.

[0065] CTF 301 sends a (350) charging data request to CHF 303, the charging data request including a first S-NSSAI. CHF 303 receives the (355) charging data request. In some example embodiments, the charging data request may indicate charging for a PDU session established for the terminal device. Based on determining that the first S-NSSAI is configured for charging the terminal component of the relay node, CHF 303 performs (360) charging for the terminal device according to the policy associated with the terminal component of the relay node.

[0066] As mentioned above, CTF 301 can be either AMF or SMF. In the following text, combined with... Figure 4 and Figure 5 Example implementations of triggering slice-based billing in AMF and SMF will be described respectively.

[0067] Figure 4 Example signaling flow 400 for charging a terminal component for a relay node according to some example embodiments associated with AMF is shown. Signaling flow 400 can be considered as Figure 3 An example embodiment of signaling flow 300. For illustrative purposes, the following will be discussed... Figure 1 Describe signaling flow 400. Signaling flow 400 involves terminal component 401 of the relay node (e.g., WAB MT or IAB MT), radio access network node 402, AMF 403, PCF 302, and CHF 303. Figure 4 In the example embodiment, AMF 403 is Figure 3 Example of CTF 301. Radio access network node 402 can be a donor network node for the terminal component 401 of the relay node.

[0068] Figure 4 Two alternative methods for determining whether terminal device 410 is a terminal component of a terminal node are shown. There are some minor differences in the steps of the two alternative methods. For option 1, at least one second S-NSSAI configuration is received in the slice information via PCF 302 at 405. For option 2, the configuration is received via AMF 403 at 410.

[0069] like Figure 4 As shown, at 405, OAM 304 configures PCF 302 to indicate that billing for WB-MT is performed via at least one second S-NSSAI (including multiple S-NSSAIs for the return trip). At 410, OAM 304 configures AMF 403 to indicate that billing for WB-MT is performed via at least one second S-NSSAI (including multiple S-NSSAIs for the return trip).

[0070] At 415, when terminal component 401 newly registers with radio access network node 402, it sends a registration request to radio access network node 402. Then, at 420, radio access network node 402 provides the registration request of terminal component 401 to AMF 403 via an initial UE message.

[0071] At 425, AMF 403 requests policy information from PCF 302. That is, AMF 403 sends a policy control request to PCF 302 including first slice information associated with terminal component 401. The first slice information may include the allowed(multiple) S-NSSAIs, subscribed(multiple) S-NSSAIs, requested(multiple) S-NSSAIs, or default(multiple) S-NSSAIs of terminal component 401. The first slice information can be received from radio access network node 402 or OAM 304.

[0072] At 430, PCF 302 sends a policy control response to AMF 403. For option 1, the policy control response may instruct that billing for terminal node 402 will be performed using a first S-NSSAI included in the first slice information. That is, PCF 302 compares the received first slice information with at least one second slice information. If the first S-NSSAI matches at least one second S-NSSAI configured for billing of the terminal component used as a relay node, then PCF 302 includes an information element for “slice-based billing” applied to terminal component 401. In some example embodiments, slice-based billing may be applied per slice, and therefore the policy control response may also include the requested, subscribed, or default S-NSSAI associated with terminal component 401.

[0073] For option 2, AMF 403 compares the first slice information with at least one second slice information to determine whether to apply slice-based billing to terminal component 401 using S-NSSAI.

[0074] At 435, based on option 1 or option 2, AMF 403 determines to apply slice-based billing to terminal component 401. At 440, based on this determination, AMF 403 includes a first S-NSSAI for differentiated billing in its billing data request to CHF 303. Note that slice information may have already been sent in the request, rather than being a new trigger. At 445, CHF 303 receives a billing data request including the first S-NSSAI. Based on the determination that the first S-NSSAI is configured for billing of terminal components of relay nodes, CHF 303 bills terminal component 401 accordingly based on the first S-NSSAI.

[0075] Note that in this example, billing is triggered after the registration request. However, other initiation conditions in AMF 403 can trigger billing.

[0076] Figure 5 Example signaling flow 500 for charging a terminal component for a relay node according to some example embodiments associated with SMF is shown. Signaling flow 500 can be considered as Figure 3 Another example embodiment of the signaling flow 300. For illustrative purposes, the following will be discussed... Figure 1 Describe signaling flow 500. Signaling flow 500 involves UE 110, network component 501 of the relay node (e.g., WAB-gNB), terminal component 502 of the relay node (e.g., WAB-MT), radio access network node 503, AMF 505, SMF 504, PCF 302, and CHF 303. Terminal component 502 of the relay node is an example of a terminal device. Radio access network node 503 is an example of donor gNB 130. Figure 5 In an example embodiment, SMF 504 is Figure 3 Examples of CTF 301 in the example.

[0077] like Figure 5 As shown, for option 1, at least one second S-NSSAI configuration is received at 515 via PCF 302. For option 2, the configuration is received at 510 via SMF 504.

[0078] At 520, authorization and authentication are performed for UE 110 and the terminal component 502 of the relay node. At 525, UE 110 connects to the network component 501 of the relay node. At 530, the terminal component 502 of the relay node connects to the radio access network node 503.

[0079] Then, at 535, UE 110 establishes a PDU session. At 540, the network component 501 of the relay node determines that it needs to establish a PDU session for backhaul UE PDU sessions. At 545, a PDU session establishment request is sent from the terminal component 502 of the relay node to AMF 505. At 550, AMF 505 requests a new PDU session for UE 110 from SMF 504.

[0080] At 555, SMF 504 requests policy information from PCF 302. That is, SMF 504 sends a policy control request to PCF 302. The policy control request includes first slice information associated with the terminal component 502 of the relay node. The first slice information may include one or more allowed S-NSSAI(s), subscribed S-NSSAI(s), requested S-NSSAI(s), or default S-NSSAI(s) of the terminal component 502 of the relay node. The first slice information can be received from AMF 505.

[0081] At 560, PCF 302 sends a policy control response to SMF 504. For option 1, the policy control response may instruct that billing for the relay node's terminal component 502 will be performed using the first S-NSSAI included in the first slice information. That is, PCF 302 compares the received first slice information with at least one second slice information. If the first S-NSSAI matches at least one second S-NSSAI, then PCF 302 includes information elements for applying slice-based billing to the relay node's terminal component 502. For option 2, SMF 504 compares the first slice information with at least one second slice information.

[0082] At 565, based on option 1 or option 2, SMF 504 determines that slice-based charging is applied to the relay node's terminal component 502. At 570, based on this determination, SMF 504 includes a first S-NSSAI for differentiated charging in its charging data request to CHF 303. Note that slice information may have already been sent in the request, rather than being a new trigger. At 580, CHF 303 receives a charging data request including the first S-NSSAI. Based on the determination that the first S-NSSAI is configured for charging the relay node's terminal component, CHF 303 charges the relay node's terminal component 502 accordingly based on the first S-NSSAI.

[0083] Note that in this example, billing is triggered after the PDU session is established. However, other initiation conditions in SMF 504 can trigger billing.

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

[0085] At frame 610, the first device receives first slice information associated with the terminal device.

[0086] At box 620, based on determining that the first single network slice selection auxiliary information included in the first slice information matches at least one second S-NSSAI included in the second slice information, the first device sends a billing data request including the first S-NSSAI to a third device configured to provide billing functionality, wherein the second slice information includes at least one S-NSSAI of a terminal component configured to serve a relay node.

[0087] In some example embodiments, method 600 may further include: receiving a configuration indicating that the billing of the terminal component of the relay node will be performed using S-NSSAI; and determining, based on the configuration, that the first S-NSSAI matches at least one second S-NSSAI.

[0088] In some example embodiments, the configuration may include second slice information.

[0089] In some example embodiments, method 600 may further include: sending a policy control request, including received first slice information, to a second device configured to provide policy and control functions; and receiving a policy control response from the second device, the policy control response indicating that billing of the terminal components of the relay node will be performed using at least one S-NSSAI included in the received first slice information.

[0090] In some example embodiments, the first device may be configured to provide access and mobility management functions, and the first device may be configured to receive first slice information associated with a terminal device by at least one of the following: receiving the first slice information associated with the terminal device from a radio access network device connected to the terminal device; or receiving the slice information associated with the terminal device from a device configured to provide unified data management functions, wherein the slice information is included in the terminal device's subscription information.

[0091] In some example embodiments, the first device may be configured to provide session management functionality, and the first device may be configured to receive first slice information associated with a terminal device by receiving first slice information associated with a terminal device from a device configured to provide access and mobility management functionality.

[0092] In some example embodiments, a billing data request may indicate billing for a Protocol Data Unit (PDU) session established for a terminal device.

[0093] In some example embodiments, the first slice information may include at least one allowed S-NSSAI of the terminal device, or at least one subscribed S-NSSAI of the terminal device, or at least one configured S-NSSAI of the terminal device, or at least one S-NSSAI bound to a PDU session established for the terminal device.

[0094] In some example embodiments, the relay node may include a Wireless Access and Backhaul (WAB) node or an Integrated Access and Backhaul (IAB) node, and the terminal component may include the mobile terminal (MT) functionality of the WAB node or IAB node.

[0095] 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 3 PCF 302 in the middle.

[0096] At box 710, the second device receives a configuration indicating that the billing of the terminal components of the relay node will be performed using Single Network Slice Selection Auxiliary Information (S-NSSAI).

[0097] At frame 720, the second device receives a policy control request from the first device, the policy control request including first slice information associated with the terminal device.

[0098] At box 730, based on determining that the first S-NSSAI included in the first slice information matches at least one second S-NSSAI received in the configuration, the second device sends a policy control response to the first device, the policy control response instructing the terminal device to perform billing using the first S-NSSAI included in the first slice information associated with the terminal device.

[0099] In some example embodiments, method 700 may further include receiving configuration from a device configured to provide operation, management and maintenance functions.

[0100] In some example embodiments, the first slice information may include at least one allowed S-NSSAI of the terminal device, or at least one subscribed S-NSSAI of the terminal device, or at least one configured S-NSSAI of the terminal device, or at least one S-NSSAI bound to a PDU session established for the terminal device.

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

[0102] In some example embodiments, the relay node includes a wireless access and backhaul (WAB) node or an integrated access and backhaul (IAB) node, and the terminal component includes the mobile terminal (MT) function of the WAB node or IAB node.

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

[0104] At box 810, the third device receives a billing data request from the first device. The billing data request includes first single network slice selection assistance information (S-NSSAI) associated with the terminal device.

[0105] At box 820, based on determining that the first S-NSSAI is configured for billing of the terminal component of the relay node, the third device performs billing of the terminal device according to the policy associated with the terminal component of the relay node.

[0106] In some example embodiments, the relay node may include a Wireless Access and Backhaul (WAB) node or an Integrated Access and Backhaul (IAB) node, and the terminal component may include the mobile terminal (MT) functionality of the WAB node or IAB node.

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

[0108] In some example embodiments, the first device includes: components for receiving first slice information associated with a terminal device; and components for sending a billing data request including the first S-NSSAI to a third device configured to provide billing functionality based on determining that a first single network slice selection assistance information (S-NSSAI) included in the first slice information matches at least one second S-NSSAI included in the second slice information, wherein the second slice information includes at least one S-NSSAI of a terminal component configured to serve a relay node.

[0109] In some example embodiments, the first apparatus may further include: a component for receiving a configuration indicating that the billing of a terminal component of a relay node will be performed using S-NSSAI; and a component for determining, based on the configuration, that the first S-NSSAI matches at least one second S-NSSAI.

[0110] In some example embodiments, the configuration may include second slice information.

[0111] In some example embodiments, the first device may further include: a component for sending a policy control request, including received first slice information, to a second device configured to provide policy and control functions; and a component for receiving a policy control response from the second device, the policy control response indicating that billing of the terminal components of the relay node will be performed using at least one S-NSSAI included in the received first slice information.

[0112] In some example embodiments, the first device may be configured to provide access and mobility management functions, and the first device may be configured to receive first slice information associated with a terminal device by at least one of the following: receiving the first slice information associated with the terminal device from a radio access network device connected to the terminal device; or receiving the slice information associated with the terminal device from a device configured to provide unified data management functions, wherein the slice information is included in the terminal device's subscription information.

[0113] In some example embodiments, the first device may be configured to provide session management functionality, and the first device may be configured to receive first slice information associated with a terminal device by receiving first slice information associated with a terminal device from a device configured to provide access and mobility management functionality.

[0114] In some example embodiments, a billing data request may indicate billing for a Protocol Data Unit (PDU) session established for a terminal device.

[0115] In some example embodiments, the first slice information may include at least one allowed S-NSSAI of the terminal device, or at least one subscribed S-NSSAI of the terminal device, or at least one configured S-NSSAI of the terminal device, or at least one S-NSSAI bound to a PDU session established for the terminal device.

[0116] In some example embodiments, the relay node may include a Wireless Access and Backhaul (WAB) node or an Integrated Access and Backhaul (IAB) node, and the terminal component may include the mobile terminal (MT) function of the WAB node or IAB node.

[0117] In some example embodiments, a second means capable of performing any method in method 700 (e.g., Figure 3 PCF 302 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 3 In PCF302.

[0118] In some example embodiments, the second apparatus includes: components for receiving a configuration indicating that the billing of a terminal component of a relay node will be performed using Single Network Slice Selection Auxiliary Information (S-NSSAI); components for receiving a policy control request from the first apparatus, the policy control request including first slice information associated with the terminal component; and components for sending a policy control response to the first apparatus based on determining that the first S-NSSAI included in the first slice information matches at least one second S-NSSAI received in the configuration, the policy control response indicating that the billing of the terminal component will be performed using the first S-NSSAI included in the first slice information associated with the terminal component.

[0119] In some example embodiments, the second device may further include a component for receiving configuration from a device configured to provide operation, management and maintenance functions.

[0120] In some example embodiments, the first slice information may include at least one allowed S-NSSAI of the terminal device, or at least one subscribed S-NSSAI of the terminal device, or at least one configured S-NSSAI of the terminal device, or at least one S-NSSAI bound to a PDU session established for the terminal device.

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

[0122] In some example embodiments, the relay node may include a Wireless Access and Backhaul (WAB) node or an Integrated Access and Backhaul (IAB) node, and the terminal component may include the mobile terminal (MT) function of the WAB node or IAB node.

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

[0124] In some example embodiments, the third device includes: a component for receiving a billing data request from the first device, the billing data request including first single network slice selection assistance information (S-NSSAI) associated with the terminal device; and a component for performing billing of the terminal device according to a policy associated with the terminal component of the relay node based on determining that the first S-NSSAI is configured for billing of the terminal component of the relay node.

[0125] In some example embodiments, the relay node may include a Wireless Access and Backhaul (WAB) node or an Integrated Access and Backhaul (IAB) node, and the terminal component may include the mobile terminal (MT) function of the WAB node or IAB node.

[0126] Figure 9 This 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 The CTF 301, PCF 302, or CHF 303 are shown. As shown, device 900 includes one or more processors 910, one or more memories 920 coupled to processor 910, and one or more communication modules 940 coupled to processor 910.

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

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

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

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

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

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

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

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

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

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

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

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

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

[0140] 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: Receive first slice information associated with the terminal device; and Based on determining that a first single network slice selection auxiliary information (S-NSSAI) included in the first slice information matches at least one second S-NSSAI included in the second slice information, a billing data request including the first S-NSSAI is sent to a third device configured to provide billing functionality, wherein the second slice information includes at least one S-NSSAI of a terminal component configured to serve a relay node.

2. The first device according to claim 1, wherein the first device is further configured to: The configuration indicating that the terminal component of the relay node will use S-NSSAI for billing will be performed; and Based on the configuration, it is determined that the first S-NSSAI matches the at least one second S-NSSAI.

3. The first apparatus according to claim 2, wherein the configuration includes the second slice information.

4. The first device according to any one of claims 1 to 3, wherein the first device is further configured to: Send a policy control request, including the received first slice information, to a second device configured to provide policy and control functions; and The second device receives a policy control response indicating that the billing of the terminal component of the relay node will be performed using at least one S-NSSAI included in the received first slice information.

5. The first device according to any one of claims 1 to 3, wherein the first device is configured to provide access and mobility management functions, and the first device is enabled to receive the first slice information associated with the terminal device by at least one of the following: Receive the first slice information associated with the terminal device from a radio access network device connected to the terminal device; or The slice information associated with the terminal device is received from a device configured to provide unified data management functions, and the slice information is included in the subscription information of the terminal device.

6. The first apparatus according to any one of claims 1 to 3, wherein the first apparatus is configured to provide session management functionality, and the first apparatus is configured to receive the first slice information associated with the terminal device by: The first slice information associated with the terminal device is received from a device configured to provide access and mobility management functions.

7. The first apparatus according to any one of claims 1 to 3, wherein the billing data request indicates billing for a Protocol Data Unit (PDU) session established for the terminal apparatus.

8. The first device according to any one of claims 1 to 3, wherein the first slice information includes at least one allowed S-NSSAI of the terminal device, or includes at least one subscribed S-NSSAI of the terminal device, or includes at least one configured S-NSSAI of the terminal device, or includes at least one S-NSSAI bound to a PDU session established for the terminal device.

9. The first apparatus according to any one of claims 1 to 3, wherein the relay node comprises a wireless access and backhaul (WAB) node or an integrated access and backhaul (IAB) node, and the terminal component comprises the mobile terminal (MT) function of the WAB node or the IAB node.

10. A second means for communication, comprising: At least one processor; as well as At least one memory storing instructions that, when executed by the at least one processor, cause the second device to at least: The billing of the terminal component receiving the instruction relay node will be configured to be performed using Single Network Slice Selection Auxiliary Information (S-NSSAI). Receive a policy control request from a first device, the policy control request including first slice information associated with a terminal device; and Based on the determination that a first S-NSSAI included in the first slice information matches at least one second S-NSSAI received in the configuration, a policy control response is sent to the first device, the policy control response instructing the terminal device that billing will be performed using the first S-NSSAI included in the first slice information associated with the terminal device.

11. The second device according to claim 10, wherein the second device is configured to: The configuration is received from a device configured to provide operation, management, and maintenance functions.

12. The second apparatus according to claim 10 or 11, wherein the first slice information includes at least one allowed S-NSSAI of the terminal device, or includes at least one subscribed S-NSSAI of the terminal device, or includes at least one configured S-NSSAI of the terminal device, or includes at least one S-NSSAI bound to a PDU session established for the terminal device.

13. The second apparatus according to claim 10 or 11, wherein the first apparatus is configured to provide access and mobility management functions, or is configured to provide session management functions.

14. The second apparatus according to claim 10 or 11, wherein the relay node includes a Wireless Access and Backhaul (WAB) node or an Integrated Access and Backhaul (IAB) node, and the terminal component includes the mobile terminal (MT) function of the WAB node or the IAB node.

15. A third means for communication, comprising: At least one processor; as well as At least one memory storing instructions that, when executed by the at least one processor, cause the third device to at least: Receive a billing data request from a first device, the billing data request including first single network slice selection assistance information S-NSSAI associated with a terminal device; as well as Based on the determination that the first S-NSSAI is configured for the terminal component of the relay node, billing of the terminal device is performed according to the policy associated with the terminal component of the relay node.

16. The third apparatus of claim 15, wherein the relay node comprises a Wireless Access and Backhaul (WAB) node or an Integrated Access and Backhaul (IAB) node, and the terminal component comprises the mobile terminal (MT) function of the WAB node or the IAB node.

17. A method for communication, comprising: Receive the first slice information associated with the terminal device; as well as Based on determining that a first single network slice selection auxiliary information (S-NSSAI) included in the first slice information matches at least one second S-NSSAI included in the second slice information, a billing data request including the first S-NSSAI is sent to a third device configured to provide billing functionality, wherein the second slice information includes at least one S-NSSAI of a terminal component configured to serve a relay node.

18. A method for communication, comprising: The billing of the terminal component receiving the instruction relay node will be configured to be performed using Single Network Slice Selection Auxiliary Information (S-NSSAI). Receive a policy control request from a first device, the policy control request including first slice information associated with a terminal device; and Based on the determination that a first S-NSSAI included in the first slice information matches at least one second S-NSSAI received in the configuration, a policy control response is sent to the first device, the policy control response instructing the terminal device to perform billing using the first S-NSSAI included in the first slice information associated with the terminal device.

19. A method for communication, comprising: Receive a billing data request from a first device, the billing data request including first single network slice selection assistance information S-NSSAI associated with a terminal device; as well as Based on the determination that the first S-NSSAI is configured for the terminal component of the relay node, billing of the terminal device is performed according to the policy associated with the terminal component of the relay node.

20. A computer-readable medium having instructions stored thereon for causing a device to perform at least the method of claim 17, the method of claim 18, or the method of claim 19.

Images