Apparatus, method and computer program

Abstract

The present disclosure relates to an apparatus, a method and a computer program. There is provided an apparatus comprising means for: receiving, from a network function, a charging request for a user equipment comprising an access identifier; creating a charging data record for the user equipment based on the charging request, wherein the charging data record is associated with the access identifier; receiving charging information from the network function, the charging information including an access identifier; and updating the charging data record based on the received charging information and the access identifier.

Description

Technical Field

[0001] Various exemplary embodiments of this disclosure generally relate to methods, apparatus and computer programs, and particularly, but not exclusively, to closed / hybrid cell billing mechanisms. Background Technology

[0002] A communication system can be viewed as a facility that enables communication sessions between two or more communication devices, or provides communication devices with access to a network. Mobile or wireless communication networks are an example of communication networks. Communication devices may be served by application servers.

[0003] Mobile or wireless communication networks can operate according to standards provided by, for example, those provided by 3GPP (3rd Generation Partnership Project) or ETSI (European Telecommunications Standards Institute). Examples of mobile or wireless communication networks operating according to 3GPP standards are often referred to as 4G (fourth generation) networks, 5G (fifth generation) networks, 5G Advanced networks, and 6G networks. Summary of the Invention

[0004] Some exemplary embodiments of this disclosure will be described with reference to certain aspects. These aspects are not intended to indicate key or essential features of the various exemplary embodiments of this disclosure, nor are they intended to limit its scope. In view of this disclosure, other features, aspects, and elements will be apparent to those skilled in the art. For example, it should be understood that other aspects may be provided by combination of any two or more aspects described herein.

[0005] In a first aspect, an apparatus is provided, comprising components for: receiving a billing request from a network function including an access identifier of a user equipment; creating a billing data record for the user equipment based on the billing request, wherein the billing data record is associated with the access identifier; receiving billing information from the network function, the billing information including the access identifier; and updating the billing data record based on the received billing information and the access identifier.

[0006] The access identifier may include at least one of the following: access node identifier, femtonode identifier, or closed access group (CAG) identifier.

[0007] Network functions can include session management functions.

[0008] Billing information may include data connection domain billing information.

[0009] The apparatus may include components for: receiving additional billing requests including an access identifier from an additional network function, and receiving additional billing information including the access identifier from the additional network function; and updating billing data records based on the received additional billing information and the received access identifier.

[0010] Other network functions could be access and mobility features.

[0011] Additional billing information may include connectivity and mobility domain information.

[0012] Network functions can include access and mobility functions.

[0013] Billing information may include connectivity and mobility domain information.

[0014] The apparatus may include components for: receiving additional billing information from other network functions; determining that the additional billing information is associated with a user equipment and an access identifier; and updating billing data records based on the received additional billing information.

[0015] Another network function could be session management.

[0016] Additional billing information may include data connection domain billing information.

[0017] In a second aspect, an apparatus is provided, comprising components for: at a network function, receiving, from another network function, a notification that a user equipment has entered or left an area identified by an access identifier, the notification including the area identifier; and in response to the notification, providing a billing request to a billing network function, the billing request including the access identifier, to create or update a billing data record associated with the access identifier.

[0018] The access identifier includes at least one of the following: access node identifier, femtonode identifier, or closed access group (CAG) identifier.

[0019] The device may also include components for: sending a billing data request, including the access identifier, to the billing function after receiving a notification that the user equipment has left the area identified by the access identifier, in order to close the associated billing data record.

[0020] The apparatus may also include components for: sending a subscription request to a network function indicating that a user equipment has entered or left an area identified by an access identifier; and receiving a notification that a user equipment has entered or left an area associated with an access identifier, as a response to the subscription request.

[0021] Notifications that a user equipment has entered or left an area identified by an access identifier may include mobility events.

[0022] A notification that a user equipment has entered an area identified by an access identifier may include a session establishment request.

[0023] Network functions can be session management functions, and other network functions can be access and mobility functions.

[0024] In a third aspect, an apparatus is provided, comprising components for: determining, at a network function, whether a user equipment has entered or left an area identified by an access identifier; and providing the access identifier from the network function to a charging function to create or update a charging data record associated with the access identifier, wherein the access identifier is provided to the charging function in any of the following ways: in a charging request from the user equipment to the charging function; or via another network function in a notification to another network function that the user equipment has entered or left an area identified by the access identifier.

[0025] The apparatus may include components for: receiving a subscription request from another network function, the subscription request being used to notify the user equipment when it enters or leaves an area identified by an access identifier; and, in response to the received notification, providing the other network function with a notification that the user equipment has entered or left an area identified by an access identifier.

[0026] Network functions can be access and mobility functions, and additional network functions can be session management functions.

[0027] The access identifier may include at least one of the following: access node identifier, femtonode identifier, or closed access group (CAG) identifier.

[0028] The components used to determine whether a user equipment enters or leaves an area identified by an access identifier may include components for receiving notifications that a user equipment has entered or left an area identified by an access identifier.

[0029] This notification can be received from the access node.

[0030] The apparatus may also include components for: configuring the access node to report user equipment entering or leaving an area associated with an access identifier; and receiving notifications of user equipment entering or leaving an area associated with an access identifier as a response to the configuration.

[0031] An access node may include at least one cell associated with the area.

[0032] In a fourth aspect, a method is provided, comprising: receiving a billing request from a network function including an access identifier of a user equipment; creating a billing data record for the user equipment based on the billing request, wherein the billing data record is associated with the access identifier; receiving billing information from the network function, the billing information including the access identifier; and updating the billing data record based on the received billing information and the access identifier.

[0033] The access identifier may include at least one of the following: access node identifier, femtonode identifier, or closed access group (CAG) identifier.

[0034] Network functions can include session management functions.

[0035] Billing information may include data connection domain billing information.

[0036] The method may include: receiving a separate billing request including an access identifier from another network function, and receiving separate billing information including the access identifier from another network function; and updating a billing data record based on the received separate billing information and the received access identifier.

[0037] Other network functions could be access and mobility features.

[0038] Additional billing information may include connectivity and mobility domain information.

[0039] Network functions can include access and mobility functions.

[0040] Billing information may include connectivity and mobility domain information.

[0041] The method may include: receiving additional billing information from another network function; determining that the additional billing information is associated with a user equipment and access identifier; and updating the billing data record based on the received additional billing information.

[0042] Another network function could be session management.

[0043] Additional billing information may include data connection domain billing information.

[0044] In a fifth aspect, a method is provided, comprising: at a network function, receiving, from another network function, a notification that a user equipment has entered or left an area identified by an access identifier, the notification including the area identifier; and in response to the notification, providing a billing request to a billing network function, the billing request including the access identifier, to create or update a billing data record associated with the access identifier.

[0045] The access identifier includes at least one of the following: access node identifier, femtonode identifier, or closed access group (CAG) identifier.

[0046] Upon receiving a notification that the user equipment has left the area identified by the access identifier, the method may include sending a billing data request, including the access identifier, to the billing function to close the associated billing data record.

[0047] The method may include: sending a subscription request to a network function indicating that a user equipment has entered or left an area identified by an access identifier; and receiving a notification that a user equipment has entered or left an area associated with an access identifier, as a response to the configuration.

[0048] Notifications that a user equipment has entered or left an area identified by an access identifier include mobility events.

[0049] A notification that a user equipment has entered an area identified by an access identifier may include a session establishment request.

[0050] Network functions can be session management functions, and other network functions can be access and mobility functions.

[0051] In a sixth aspect, a method is provided, comprising: at a network function, determining that a user equipment has entered or left an area identified by an access identifier; and providing the access identifier to a charging function to create or update a charging data record associated with the access identifier, wherein the access identifier is provided to the charging function in any of the following ways: in a charging request from the user equipment toward the charging function; or via another network function in a notification to another network function that the user equipment has entered or left an area identified by the access identifier.

[0052] The method may include: receiving a subscription request from another network function, the subscription request being used to notify the user equipment when it enters or leaves an area identified by an access identifier; and, in response to the received notification, providing the other network function with a notification that the user equipment has entered or left the area identified by the access identifier.

[0053] Network functions can be access and mobility functions, and additional network functions can be session management functions.

[0054] The access identifier may include at least one of the following: access node identifier, femtonode identifier, or closed access group (CAG) identifier.

[0055] Determining whether a user equipment enters or leaves an area identified by an access identifier may include receiving notifications that the user equipment has entered or left an area identified by an access identifier.

[0056] This notification can be received from the access node.

[0057] The method may include: configuring an access node to report user equipment entering or leaving an area associated with an access identifier; and receiving notifications of user equipment entering or leaving an area associated with an access identifier as a response to the configuration.

[0058] An access node may include at least one cell associated with the area.

[0059] In a seventh aspect, an apparatus is provided, comprising at least one processor and at least one memory storing instructions, which, when executed by the at least one processor, cause the apparatus to perform at least the method according to the third, fourth, or fifth aspect.

[0060] In an eighth aspect, a non-transitory computer-readable medium including instructions is provided, wherein when executed by at least one means, the instructions cause the means to perform the method according to the third, fourth, or fifth aspect.

[0061] In a ninth aspect, a computer-readable medium including instructions is provided, wherein when executed by at least one processor of a device, the instructions cause the device to perform the method according to the third, fourth, or fifth aspect.

[0062] Some example embodiments are defined in the dependent claims.

[0063] Many different aspects have been described above. As previously stated, it should be understood that additional aspects may be provided by combination of any two or more of the aspects described above (or otherwise described in this disclosure).

[0064] Various other aspects are also described in the following detailed description and claims. Attached Figure Description

[0065] Some exemplary embodiments will be described with reference to the accompanying drawings, by way of non-limiting and illustrative examples only, in which:

[0066] Figure 1 An example of a communication network to which the examples disclosed herein can be applied is shown;

[0067] Figure 2 A flowchart based on the example method is shown;

[0068] Figure 3 A flowchart based on the example method is shown;

[0069] Figure 4 A flowchart based on the example method is shown;

[0070] Figure 5 An example signaling diagram is shown;

[0071] Figure 6 An example signaling diagram is shown; and

[0072] Figure 7 An example of the device is shown. Detailed Implementation

[0073] The following exemplary embodiments are provided by way of non-limiting and illustrative example. Although this disclosure may refer to "an," "one," or "some" embodiments or exemplary embodiments in various places, this does not necessarily mean that every reference is to the same embodiment or exemplary embodiment(s), or that a particular feature applies only to a single embodiment or exemplary embodiment. Individual features of different embodiments or different exemplary embodiments may also be combined to provide other embodiments. Furthermore, when a particular feature, structure, or characteristic is described in connection with an embodiment or exemplary embodiment, it is intended that such feature, structure, or characteristic may be applied in combination with other embodiments or other exemplary embodiments (whether explicitly described or not).

[0074] It should be understood that although the terms "first," "second," etc., may be used in this document to describe various elements, these elements should not be limited by these terms. These terms are only used to distinguish one element from another.

[0075] For the purposes of this disclosure, the phrases "at least one of A or B", "at least one of A and B", and "A and / or B" refer to (A), (B), or (A and B). For the purposes of this disclosure, the phrases "A, B, and / or C" refer to (A), (B), (C), (A and B), (A and C), (B and C), or (A, B, and C).

[0076] As used herein, the term “or” means non-exclusive “or” unless otherwise stated (e.g., “otherwise” or “or in the alternative”).

[0077] As used herein, unless explicitly stated otherwise, performing a feature, step, or function "in response to A" does not mean that the feature, step, or function is performed immediately after "A" occurs, because one or more intermediate features, steps, or functions may be performed (at least partially) between the occurrence of the feature, step, or function and "A". Similarly, performing a feature, step, or function "based on A" does not mean that the feature, step, or function is performed solely based on "A", because the feature, step, or function may be based on one or more other features, steps, or functions besides "A".

[0078] The various example embodiments described herein can be implemented in communication networks such as any of the following radio access technologies (RATs): Global Microwave Access Interoperability (WiMAX), Global System for Mobile Communications (GSM, 2G), GSMEDGE Radio Access Network (GERAN), General Packet Radio Service (GRPS), Universal Mobile Telecommunications System based on Basic Wideband Code Division Multiple Access (W-CDMA) (UMTS, 3G), High-Speed ​​Packet Access (HSPA), Long Term Evolution (LTE), Advanced LTE and Enhanced LTE (eLTE), 5G (also known as NR), or any future RAT (such as 6G). Furthermore, communication within the communication network 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 Multiplexing (OFDM), and / or Discrete Fourier Transform Spread Spectrum OFDM (DFT-s-OFDM).

[0079] As used herein, the term "network device" or "network node" refers to a node in a communications network through which user equipment can access the network and / or through which the node is configured to control radio communications and manage radio resources within the cell. A network node or network device may be referred to as a base station (BS), access point (AP), or access node. Depending on the technology applied, a network device may be, for example, a Node B (NodeB or NB), an evolved Node B (eNodeB or eNB), an NR NB (also known as a gNB), a Remote Radio Unit (RRU), a Radio Head (RH), a Remote Radio Head (RRH), a relay, an Integrated Access and Backhaul (IAB) node, a low-power node, a non-terrestrial network (NTN) or non-terrestrial network equipment (such as satellite network equipment, low Earth orbit (LEO) satellites, and geostationary orbit (GEO) satellites), or an aircraft network equipment.

[0080] Furthermore, in the context of split radio access networks (RANs), network devices can refer to centralized units (CUs) and / or distributed units (DUs) of a base station. The interface between the CU and the DU can be referred to as the F1 interface in NR. In a split RAN architecture, node operations can be performed at least partially in a central / centralized unit (CU, e.g., a server, host, or node) that is operationally coupled to a DU (e.g., a radio head / node). A CU can control one or more DUs to at least act as a transmit / receive (Tx / Rx) node. In some example embodiments, a DU may include, for example, a Radio Link Control (RLC), Media Access Control (MAC) layer, and a Physical (PHY) layer, while a CU may include layers above the RLC layer, such as a Packet Data Convergence Protocol (PDCP) layer, Radio Resource Control (RRC), and Internet Protocol (IP) layer. Other functional splitting is also possible. In practice, any processing task can be performed in a CU or a DU, and the boundary of responsibility transfer between the CU and the DU can depend on the applied implementation.

[0081] The term "terminal device" refers to any terminal device that can be configured to perform wireless communication. For example, a terminal device may be referred to as a communication device, user equipment (UE), subscriber station (SS), or mobile station (MS). Terminal devices can include mobile phones, cellular phones, smartphones, Voice over IP (VoIP) phones, wireless local loop phones, tablets, wearable terminal devices, personal digital assistants (PDAs), portable computers, desktop computers, image capture terminal devices (such as digital cameras), gaming terminal devices, music storage and playback devices, in-vehicle wireless terminal devices, USB dongles, Internet of Things (IoT) devices, watches or other wearable devices, head-mounted displays (HMDs), automobiles, 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, and so on.

[0082] As used herein, the term "resource" can refer to radio resources in the time domain, frequency domain, spatial domain, and / or code domain. Some examples of resources may include, for example, physical resource blocks (PRBs), radio frames, subframes, time slots, subbands, frequency regions, subcarriers, beams, etc. The terms "transmit" and / or "receive" can refer to wireless transmission and / or reception over radio resources via a wireless propagation channel.

[0083] Figure 1The illustration shows an example of a communication network to which the examples disclosed herein can be applied. The communication network, or cellular communication network, may include a network node 110 configured to provide one or more cells, such as cell 100, and a network node 112 configured to provide one or more other cells, such as cell 102. For example, each cell may be a macrocell, microcell, femtocell, or picocell. A cell may define the coverage area or service area of ​​a corresponding access node.

[0084] Network nodes (110, 112) can be configured to provide radio access to a communication network to user equipment (UE) 120 (one or more UEs). Radio access may include downlink (DL) communication from network nodes (110, 112) to UE 120 and uplink (UL) communication from UE 120 to network nodes (110, 112). Examples of uplink channels may include a Physical Uplink Control Channel (PUCCH) for transmitting control information and a Physical Uplink Shared Channel (PUSCH) for transmitting data toward the network. Examples of downlink channels may include a Physical Downlink Control Channel (PDCCH) for transmitting control information and a Physical Downlink Shared Channel (PDSCH) for transmitting data toward the user equipment.

[0085] Multiple UEs (120, 122) can exist in this system. Each of the multiple UEs can be served by the same or different network nodes (110, 112). UEs can be configured with dual connectivity (DC), where a UE (e.g., UE 120) can be connected to multiple network nodes (110, 112). UEs (120, 122) can communicate with each other when a device-to-device (D2D) communication interface is established between them via a so-called sidechain (SL). For example, this D2D communication can be referred to as machine-to-machine, peer-to-peer (P2P) communication, or vehicle-to-vehicle (V2V) communication.

[0086] In a communication network with multiple network nodes, these nodes can connect to each other via interfaces. For example, the LTE specification refers to this interface as the X2 interface. The interface between an LTE node and a 5G node, or between two 5G nodes, can be called the Xn interface.

[0087] Network nodes 110 and 112 can also connect to the core network 116 of the communication network via another interface. The LTE specification designates the core network as an Evolved Packet Core (EPC), and the core network can include multiple entities (e.g., Mobility Management Entity (MME) and gateway nodes). The MME can handle the mobility of terminal devices in a tracking area comprising multiple cells and handle signaling connections between the terminal devices and the core network. Gateway nodes can handle data routing within the core network and data routing to / from terminal devices. The 5G specification designates the core network as a 5G Core (5GC). For example, the 5GC can include Access and Mobility Management Functions (AMF) and User Plane Functions / Gateways (UPF), among other functions. The AMF can handle the termination of Non-Access Stratum (NAS) signaling, NAS encryption and integrity protection, registration management, connection management, mobility management, access authentication and authorization, and security context management. For example, UPF nodes can support packet routing and forwarding, packet inspection, and Quality of Service (QoS) processing.

[0088] Femtosecond support in 5G has been agreed upon. Aspects to be agreed upon include: how to enable interoperability between Closed Access Group (CAG) cells in 5G and Closed Subscriber Group (CSG) cells in 4G; whether and how to support the provisioning of subscribers allowed to access CAG cells; and how to manage access control by CAG owners or authorized administrators. Billing is also under discussion.

[0089] The 3GPP standard defines 5G data connection domain charging and charging management. The SMF with embedded CTF (Charging Trigger Function) generates charging events toward CHF (Charging Function) for data connection convergence charging.

[0090] The billing functions specified for 5G data connection billing include PDU sessions in SMF, SDF (Service Data Stream) within PDU sessions, and QoS streams within PDU sessions.

[0091] For example, SMF can collect one or more of the following billing information for converged billing: • Use of access and core network resources: For example, billing information can describe the amount of data delivered to and forwarded from the UE; • Duration of use: The duration of a PDU session can be counted as the time interval from the establishment of the PDU session to the release of the PDU session; • User: Billing information can provide the actual UE address used by the user for the PDU session; • Data network: Billing information can be described in terms of the accuracy determined by the DNN for data network addresses; • Use of external data networks: Billing information can describe the amount of data sent to and received from external data networks. External networks can be identified by a DNN; • Start Time: This identifies when the PDU session begins; • User location: For example, it could be an HPLMN, VPLMN, an internal / external reporting area, and optional higher-precision location information.

[0092] Triggered by PCC rules received from the PCF, or by pre-configured information available at the SMF, or by online billing methods received from the CHF via the quota management mechanism, the SMF provides URR (Usage Reporting Rules) to the UPF to control how usage reports are executed.

[0093] UPF supports reporting usage information to the SMF. UPF can support reporting based on different triggers, including periodic reports with periods defined by the SMF, usage thresholds provided by the SMF, and / or on-demand reports received from the SMF.

[0094] When 5G connectivity and mobility converged charging is activated, it can be performed by the AMF (Agency Management Function) interacting with the CHF (Convergence of Charges). The AMF can perform converged charging by interacting with the CHF for charging data related to registration, connectivity, and location management. Charging data requests and responses are exchanged between the AMF and CHF based on IEC (Instant Event Charging), PEC (Post-Event Charging), or ECR (Event Charging with Cell Retention) scenarios specified in 3GPP standards. When certain conditions (chargable events) are met, the AMF sends a charging data request to the CHF. To enable connectivity and mobility domain charging, AMF supports converged charging using service-based interfaces, collecting charging information per UE registration to 5GS (initial, MRU, periodic RU, emergency registration), collecting charging information per UE N2 connection between 5G-AN and AMF (for 3GPP and untrusted non-3GPP access), collecting charging information per user location report, and collecting charging information including (multiple) CAG identifiers per UE registration to 5GS.

[0095] For location reporting billing, the level of location change (i.e., TAI change and / or cell change) or the presence of the UE in (multiple) Presence Reporting Areas (PRAs) can be reported. The PRA list may include: (i) (multiple) core network pre-configured presence reporting areas identified by (multiple) PRA identifiers; and (ii) (multiple) UE-specific presence reporting areas defined by (multiple) PRA identifiers, each of which is provided with its elements.

[0096] The location reporting level can be TAI + cell identifier. The report type indicates whether the message is intended to trigger a single, independent report about the current cell identifier serving the UE, initiate NG-RAN reporting when the UE changes cells, or request NG-RAN reporting when the UE moves out of or into an area of ​​interest. However, note that requesting a report whenever the UE changes cells can increase signaling load on multiple interfaces. Requesting reports of all changes to the PSCell ID can also increase signaling load. Therefore, it is recommended that any such reporting be limited to a limited number of subscribers.

[0097] For CSG / Hybrid cells, different rates and billing models can be applied when a user consumes network services via a CSG cell or a hybrid cell based on their CSG information. User CSG information includes CSG ID, access mode, and CSG membership indication. The billing system can select the applicable rate based on the user's CSG information. The billing process at the CSG enables differentiated billing at CSG cells, differentiated billing at member hybrid cells, and differentiated billing at non-member hybrid cells. The CSG billing model can be enabled by reporting user CSG information to the appropriate network elements. Changes to user CSG information can be a trigger for CDR billing information collection in the following scenarios: • Add S-CDR (collected by SGSN) billing information; • Add SGW-CDR billing information; • Add PGW-CDR billing information; or • Adding TDF-CDR billing information

[0098] In LTE, conditions for changes to user CSG information are defined. When user CSG information (e.g., CSG ID, access mode, or CSG membership indication) changes (triggering a request to the CHF), the CDR can be updated using the open "Service Data Volume List," which is then closed. If CSG information reporting is required, a report of user CSG information changes is provided. When billing conditions change, a data volume count is added to the CDR, and a new count begins. Considering "authorized units" may be beneficial (or perhaps necessary) when considering unit-retained billing scenarios.

[0099] When an Accounting Event (ACR) is triggered by a "Change of User CSG Information" condition, the following can be applied to the added data volume container. When a user enters a CSG cell or hybrid cell, the CSG ID, access mode, and CSG membership indication (in the case of hybrid cells) can be provided along with the "Change of User CSG Information" condition. When a user leaves a CSG cell or hybrid cell, the "Change of User CSG Information" condition should be provided without providing any CSG ID, access mode, or CSG membership indication, unless the user is entering a new CSG cell or hybrid cell.

[0100] For 5G data connection domain billing, although "CAG" is listed in the abbreviation list in the standard, the specification does not mention CAG or UE entering / leaving a CAG cell. NPN-related billing focuses on SNPN. Although the specification acknowledges SNPN and PNI-NPN as two options for NPN deployment, billing only focuses on SNPN.

[0101] PNI-NPN billing is captured in 5G connectivity and mobility domain billing. End-user billing for PNI-NPN network access is based on registration management billing in the AMF. The AMF may collect billing information, including (if available) CAG identifiers registered with each UE to the 5GS, and send them to the CHF. The UE's CAG information is included in the subscription as part of mobility restrictions.

[0102] The following aims to enable differentiated 5G femtocell access billing so that end users accessing femtocells can be billed differently (e.g., at a lower price than accessing via a normal cell) due to macrocell offloading. To achieve this, CHF should be triggered when a UE enters / leaves a femtocell CAG cell for mobility (e.g., via AMF) and / or data connectivity (e.g., via SMF).

[0103] Figure 2 A flowchart illustrating a method according to an example embodiment is shown. This method can be performed by a device. The device may include, implement, or implement a network function. The network function may be a billing function.

[0104] At point 201, the method includes: receiving a billing request from a network function, including an access identifier, from a user equipment.

[0105] At 202, the method includes: creating a billing data record for a user equipment based on a billing request, wherein the billing data record is associated with an access identifier.

[0106] At 203, the method includes: receiving billing information from a network function, the billing information including an access identifier.

[0107] At 204, the method includes updating the billing data record based on the received billing information and access identifier.

[0108] The network function can be a session management function or an access and mobility function. When the network function is a session management function, the billing information may include data connection domain billing information. When the network function is an access and mobility function, the billing information may include connection and mobility domain information.

[0109] Figure 3 A flowchart of a method according to an example embodiment is shown. This method can be performed by a device. The device may include, implement, or be a network function. The network function may be a session management function. The session management function may implement a charging trigger function (CTF).

[0110] At 301, the method includes: at a network function, receiving from another network function a notification that the user equipment has entered or left an area identified by an access identifier, the notification including the area identifier.

[0111] At 302, the method includes: in response to the notification, providing a charging request to a charging network function, the charging request including an access identifier, to create or update a charging data record associated with the access identifier.

[0112] Other network functions could include access and mobility management.

[0113] Figure 4 A flowchart of a method according to an example embodiment is shown. This method can be performed by a device. The device may include, implement, or contain network functions. The network functions may be access and mobility functions. The access and mobility functions may implement a billing triggering function.

[0114] At 401, the method includes: at the network function, determining that the user equipment has entered an area identified by an access identifier.

[0115] At 402, the method includes: providing an access identifier to a billing function to create or update a billing data record associated with the access identifier, wherein the access identifier is provided to the billing function in any of the following ways: in a billing request from the user equipment to the billing function, or in a notification from another network function that the user equipment has entered or left an area identified by the access identifier.

[0116] Another network function could be session management.

[0117] When the UE is served by a CAG cell, the above method can enable the use of reporting and billing.

[0118] In some example embodiments, the AMF identifies the CAG ID and sends the CAG ID to the SMF and / or CHF.

[0119] In some example implementations, the SMF receives the CAG ID from the AMF and provides the CAG ID as part of the CDR to the CHF. When the UE is served by a CAG cell, the SMF can request / merge the use reporting rules to the UPF.

[0120] In some example implementations, the CHF opens a Charging Data Record (CDR) for the CAG ID (which may be provided by the AMF for connectivity and mobility domain charging, and / or by the SMF for data connectivity domain charging) and sends a charging data response including the CAG ID to the AMF and / or SMF. When the UE is serviced by the CAG cell based on updates provided by the AMF, the CHF may filter and merge usage reports provided by the SMF. Updating the CDR may indicate that the CDR is turned off when the UE leaves the area. Specific QoS information can be sent to the charging system via the CGF function for statistical reporting purposes.

[0121] refer to Figures 2 to 4 The access identifier in any of the described methods may include an access identifier that includes at least one of the following: an access node identifier, a femtonode identifier, or a closed access group (CAG) identifier. The gNB ID, HgNB ID, and CAG ID may be used to indicate a cell to which the UE is connected and / or which is serviced by the cell.

[0122] While the above describes 5G network functions (e.g., AMF, SMF, CHF, CDR, CAG), it can be applied to any version of the 3GPP core (e.g., future 6G core).

[0123] Reference Figure 2 and Figure 3 In an example embodiment of the described method, the network function includes an SMF. That is, the SMF embeds a CTF. The AMF should know that the UE has entered a CAG cell. When the UE enters a CAG cell and initiates a PDU session via the CAG cell, or enters a CAG cell during the lifecycle of an active PDU session, the AMF provides the SMF with a CAG ID to indicate that the UE is served by the CAG cell. This is an example of receiving a notification at the network function that the user equipment has entered an area identified by an access identifier, which includes the area identifier. The notification that the user equipment has entered an area identified by the access identifier may include signaling messages (e.g., mobility events) associated with a session establishment request or a path handover request during an HO procedure. The signaling messages may be, for example... Nsmf_PDUSession_CreateSMContext request or Nsmf_ PDUSession_UpdateSMContext request Alternatively, if the SMF subscribes to UE mobility events from the AMF using the CAG ID, the notification can be a UE mobility event notification from the AMF.

[0124] refer to Figure 3 The method may include: sending a subscription request to a network function indicating that a user equipment has entered or left an area identified by an access identifier, and receiving a notification that a user equipment has entered or left an area associated with an access identifier as a response to the subscription request.

[0125] For example, during PDU session establishment, when the UE is within the coverage area of ​​a CAG cell or enters / leaves a CAG cell during the lifecycle of an active PDU session, the SMF provides the CHF with a CDR including the CAG ID, which can be triggered by receiving a notification from the AMF.

[0126] Based on information received from the SMF, the CHF opens a CAG-specific billing data record and updates it based on usage reported by the SMF using existing mechanisms. This is an example of creating a billing data record for a user equipment based on a billing request, where the billing data record is associated with an access identifier and billing information, including the access identifier, is received from network functions.

[0127] CHF maintains billing information associated with CAG IDs and users. This is an example of updating billing data records based on received billing information and access identifiers.

[0128] Figure 5 The signaling flow for an example embodiment of SMF embedding CTF is shown. In this example, an enhancement to the PDU session establishment process is proposed. When the UE connects to the CAG cell, the SMF receives the CAG ID from the AMF and initiates PDU session establishment. Then, the SMF (via CTF) triggers a charging data request including the CAG ID to the CHF.

[0129] In step 1, the UE sends a PDU session establishment request to the RAN node (Femtobit AP, HgNB), and the RAN node provides the AMF with the gNB ID or HgNB ID and / or CAG ID.

[0130] In step 2, the AMF performs SMF selection based on the existing process.

[0131] At step 3, the AMF sends an Nsmf_PDUSession_CreateSMContext request to the SMF, including the gNB ID or HgNB ID and / or CAG ID, and the SMF responds. The SMF also triggers the following steps 3ch-a.

[0132] At step 3ch-a, the SMF creates a billing identifier for the gNB ID or HgNB ID and / or CAG ID, and sends a billing data request with the gNB ID or HgNB ID and / or CAG ID to the CHF [Initial].

[0133] At step 3ch-b, CHF opens a CDR for the gNB ID or HgNB ID and / or CAG ID.

[0134] At step 3ch-c, CHF confirms by sending a billing data response [Initial] to SMF, including gNB ID or HgNB ID and / or CAG ID.

[0135] At step 4, the SMF can optionally subscribe to the AMF for UE mobility events with gNB ID or HgNB ID and / or CAG ID. The SMF can use event notifications to know when the UE leaves the (CAG) cell.

[0136] At step 5, the SMF configures (multiple) UPFs (N4 rules / URRs) to collect usage reports when the UE is served by a (CAG) cell. As part of the usage report from the (multiple) UPFs, the SMF may trigger steps 5ch-a, 5ch-b, and 5ch-c to update the CDR. These CDR update messages also include the gNB ID or HgNB ID and / or CAG ID.

[0137] At step 6, the SMF receives a UE mobility event notification from the AMF, which indicates that the UE leaves a (CAG) cell (step 6a). Alternatively, the SMF receives an Nsmf_PDUSession_UpdateSMContext message from the AMF, including the gNB ID or HgNB ID and / or CAG ID, for example, during a HO process where the UE moves from a CAG cell identified by the CAG ID to a non-CAG cell, or a CAG cell identified by another CAG ID.

[0138] When a UE leaves a (CAG) cell and the SMF is triggered by the AMF as described above, the SMF performs steps 6ch-a, 6ch-b, and 6ch-c to terminate the CDR. These CDR termination messages also include the gNB ID or HgNB ID and / or CAG ID. Here is an example of receiving a notification that a UE has left an area identified by an access identifier, where the notification is received from another network function, and a charging data request including the access identifier is sent to the charging function to close the associated charging data record.

[0139] The proposed enhancements can be applied to message streams captured for PDU session billing in TS 32.255 5.2.2, where the gNB ID or HgNB ID and / or CAG ID are included in the aforementioned request / open / update / response messages.

[0140] To achieve this, in one example, the Nchf_ConvergedCharging service is enhanced to include the gNB ID or HgNB ID and / or CAG ID as part of the input parameters for the Nchf_ConvergedCharging_Create / Update / Release / Notify service.

[0141] Considering the business model in use, the following billing scenarios can be updated: PEC (post-event billing), IEC (instant event billing), ECR (event billing with cell retention), and SCUR (session billing with cell retention).

[0142] When the CHF receives a charging data request [update] with a gNB ID or HgNB ID and / or CAG ID, the triggering conditions in Table 5.2.3.2.2.1 of TS32.255 (as shown in Table 1 below) should be updated with "UE enters / leaves CAG cell" or "Serving NG-RAN node changes". It is worth noting that the existing condition regarding "Serving node change" indicates that the SMF change is part of the I-SMF / V-SMF topology.

[0143] Similarly, the structure of the charging data request message from the SMF captured in Table 6.1.1.2.1 of TS 32.255 and the structure of the PDU session charging information in Table 6.2.1.2.1 of TS 32.255 should be updated to include the gNB ID or HgNB ID and / or CAG ID. The new IE can be referred to as the "Serving NG-RAN Node". Table 1

[0144] Reference Figure 2 and Figure 4In an example embodiment of the described method, the network function includes an AMF (Access Provider Function). That is, the AMF embeds a CTF (Cost-to-Factory Function). When the AMF embeds the CTF, it should know that the UE has entered a CAG (Category Auxiliary) cell (i.e., the AMF determines that the user equipment has entered an area identified by an access identifier). When the UE enters a CAG cell, the AMF provides the CHF (Category Certification Function) with a CDR (Category Draw) including the CAG ID. This is an example of providing the access identifier from the network function to the charging function to create or update charging data records associated with the access identifier, wherein the access identifier is provided to the charging function in a charging request for the user equipment to the charging function. Reference Figure 4 The method may include configuring an access node to report user equipment entering or leaving an area associated with an access identifier, and receiving notifications of user equipment entering or leaving an area associated with an access identifier as a response to the configuration.

[0145] Determining whether a user equipment (UE) has entered or left an area identified by an access identifier may include receiving a notification that the UE has entered or left the area identified by the access identifier. The notification that the UE has entered the area identified by the access identifier may be received from an access node (e.g., a gNB or NR femto). The access node may include at least one cell associated with the area.

[0146] Based on the information received from AMF, CHF opens the CAG-specific billing data record.

[0147] When the UE is served by a CAG cell, this example embodiment may rely on the CHF to filter and merge CDRs from the AMF (UE entering / leaving the CAG cell) and CDRs from the SMF (data volume used for transmission). For example, as referenced Figure 2 The method may include receiving additional billing information from another network function, determining that the additional billing information is associated with a user equipment and access identifier, and updating billing data records based on the received additional billing information. In this example, the network function is an AMF, and the other network function may be an SMF. The additional billing information may include data connection domain billing information.

[0148] CHF maintains billing information related to CAG ID and user usage reports.

[0149] Figure 6 An example signaling flow for embedding CTF within an AMF is shown. This example proposes enhancements to the process for establishing PDU sessions and / or making handover requests. When the AMF receives a CAG ID from the RAN node as part of a PDU session establishment or HO request, the AMF (via CTF) triggers a charging data request, including the CAG ID, to the CHF.

[0150] In step 1, the UE sends a PDU session establishment request to the RAN node (Femtobit AP, HgNB), and the RAN node provides the AMF with the gNB ID or HgNB ID and / or CAG ID.

[0151] In step 2, the AMF performs SMF selection based on the existing process.

[0152] In step 3, the AMF sends an Nsmf_PDUSession_CreateSMContext request to the SMF, and the SMF responds.

[0153] At step 3ch-a, the AMF creates a billing identifier for the gNB ID or HgNB ID and / or CAG ID, and sends a billing data request with the gNB ID or HgNB ID and / or CAG ID to the CHF [Initial].

[0154] At step 3ch-b, CHF opens a CDR for the gNB ID or HgNB ID and / or CAG ID.

[0155] At step 3ch-c: CHF confirms by sending a billing data response [Initial] to AMF, including gNB ID or HgNB ID and / or CAG ID.

[0156] At step 4: Based on other triggering conditions, such as conditions that have already been supported, the AMF can trigger steps 4ch-a, 4ch-b, and 4ch-c to update the CDR. These CDR update messages also include the gNB ID or HgNB ID and / or CAG ID.

[0157] In step 5, in one option, the UE sends a measurement report, and the RAN node decides to trigger a HO (House of Interest) to the AMF (Advanced Context Provider). The AMF responds to the HO request. Note that this step can be triggered by the RAN node based on its internal mechanisms. In another option, the UE sends an AN (Anti-Connection) release, and the RAN node sends an N2 (Context Release).

[0158] At step 6, the AMF identifies the UE leaving (CAG) cell based on the method described above. When the UE leaves (CAG) cell, the AMF performs steps 6ch-a, 6ch-b, and 6ch-c to terminate the CDR. These CDR termination messages also include the gNB ID or HgNB ID and / or CAG ID. This is an example of updating the billing data record by closing the billing data record associated with the access identifier.

[0159] As part of this example implementation, (when the UE enters / leaves the CAG cell) the CHF tracks the CDRs provided by the AMF to filter and merge the CDRs from the SMF (for data connection billing) when the UE is served by the CAG cell.

[0160] The proposed enhancements can be applied to message streams captured for 5G connectivity and mobility billing in TS 32.256 5.2.2, where the gNB ID or HgNB ID and / or CAGID are included in the aforementioned request / open / update / response messages.

[0161] To achieve this, the Nchf_ConvergedCharging service can be enhanced to include the gNB ID or HgNB ID and / or CAG ID as part of the input parameters for the Nchf_ConvergedCharging_Create / Update / Release / Notify service.

[0162] The billing scenario can be updated depending on the business model in use.

[0163] When CHF receives a billing data request [update] with gNB ID or HgNB ID and / or CAG ID, the triggering conditions in Table 5.2.1.2.1.1 of TS32.256 (as shown in Table 2 below) can be updated using "UE enters / leaves CAG cell" or "serving NG-RAN node changes".

[0164] It is worth noting that the existing condition regarding "changes in the presence of UEs in (multiple) presence reporting areas" is part of location reporting-related billing. As mentioned above, requesting reports of all changes in the PSCell ID can further increase signal load. In the above method, signaling is only available to a limited number of subscribers. Specifying cell changes only for CAG cells can reduce signal load.

[0165] The structure of the billing data request from the AMF captured in Table 6.1.1.2.1 of TS 32.256 and the structure of the PDU session billing information in Table 6.2.1.2.1 of TS 32.256 can be updated to include the gNB ID or HgNB ID and / or CAGID. The new IE can be referred to as "Serving NG-RAN Node". Table 2

[0166] refer to Figure 2The method may include: receiving an additional billing request including an access identifier from another network function, and receiving additional billing information, including the access identifier, from the other network function; and updating a billing data record based on the received additional billing information and the received access identifier. In this example embodiment, the network function is SMF, and the other network function is AMF. In this example embodiment, AMF and SMF embed CTF.

[0167] In the example implementation where the AMF and SMF embed the CTF, the AMF should know that the UE has entered a CAG cell. When the UE enters a CAG cell, the AMF provides the CHF with a CDR including the CAG ID.

[0168] Based on the information received from the AMF, the CHF opens the CAG-specific billing data record for connectivity and mobility domain billing.

[0169] When a UE initiates a PDU session, the AMF provides the CAG ID to the SMF.

[0170] During the PDU session establishment, the SMF provides the CHF with a CDR including the CAG ID.

[0171] Based on the CAG ID provided by SMF, CHF opens the CAG-specific billing data record for data connection domain billing.

[0172] When the UE is served by a CAG cell, this example embodiment relies on the CHF to provide the SMF (the amount of data to be transmitted) with the same CDR that was initially provided to the AMF (when the UE enters the CAG cell).

[0173] CHF maintains billing information related to CAG ID and user usage reports.

[0174] In the example where CTF is embedded in AMF and SMF, CHF is triggered by AMF when the UE enters a (CAG) cell, and by SMF when the UE establishes a PDU session. (See reference...) Figure 6 Compared to the example described above that embeds CTF and CHF filters and merges CDRs based on CHF implementation, this example mitigates the filtering / merging process. This is achieved by assigning the same CDR ID to the AMF and SMF by CHF when the UE is served by a (CAG) cell.

[0175] In other words, when a UE enters a (CAG) cell, it follows... Figure 6 Steps 1 through 3ch-c are used to assign CDR IDs. Then, follow... Figure 5Steps 3 through 3ch-c are performed to assign the same CDR ID when the SMF sends the initial CDR request to the CHF. After this is completed, the same CDR ID will be used at any time during updates and terminations provided by the AMF and / or SMF.

[0176] Figure 7 A block diagram of apparatus 10 is shown by way of example. For example, apparatus 10 includes at least one processor 12 and at least one memory 14 storing instructions 15, which, when executed by the at least one processor, cause apparatus 10 to perform at least one or more methods (or portions thereof) disclosed herein, and any example embodiments (or corresponding portions thereof). In the example, at least one memory and instructions (e.g., computer program code, software) are configured, together with at least one processor, to cause apparatus 10 to perform one or more methods (or portions thereof) disclosed herein, and any example embodiments (or corresponding portions thereof).

[0177] The processor 12 may include, or be configured as, one or more circuit systems configured to perform various stages of the method according to the example embodiments described herein.

[0178] As used herein, the term "circuit system" can refer to one or more or all of the following: (a) a hardware circuit implementation only, such as an implementation only in analog and / or digital circuit systems; and (b) a combination of hardware circuits and software, such as, as applicable: (i) a combination of (multiple) analog and / or digital hardware circuits having software / firmware; and (ii) any portion of (multiple) hardware processors having software (including (multiple) digital signal processors), software, and (multiple) memories, which work together to enable a device (such as a user equipment) to perform various functions; and (c) (multiple) hardware circuits and / or (multiple) processors, such as (multiple) microprocessors or portions of (multiple) microprocessors, which require software (e.g., firmware) to operate, but may be absent when operation is not required. This definition of circuit system applies to all uses of the term herein (including in any claim). As another example, as used herein, the term circuit system also covers an implementation of hardware circuits or processors (or multiple processors) or a portion of hardware circuits or processors and their accompanying software and / or firmware. For example, and if applicable to certain claim elements, the term circuit also systematically 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.

[0179] The memory 14 can be implemented using any suitable data storage technology. The memory may include a database for storing data. For example, the memory 14 may be at least partially located outside the device 10, but accessible by the device 10.

[0180] Instruction 15 may be included in a computer-readable medium or a non-transitory computer-readable medium. As used herein, the term “non-transitory” refers to a limitation on the medium itself (i.e., tangible, not signaling), rather than a limitation on the persistence of data storage (e.g., random access memory (RAM) and read-only memory (ROM).

[0181] For example, device 10 may be a terminal device, such as a UE. As another example, the device is included in such a terminal device, for example, as a chipset configured to control the terminal device.

[0182] As another example, device 10 is a network entity. In another example embodiment, the device is included in such a network entity, for example, as a chipset configured to control the network entity. Device 10 can be caused or configured to at least perform Figure 2 , Figure 3 or Figure 4 The methods and / or any one or more example embodiments described herein.

[0183] The device may include one or more entities of any protocol layer, such as a MAC entity, RRC entity, RLC entity, PDCP entity, or PHY entity. In some example embodiments, the entity is configured to at least perform Figure 2 , Figure 3 or Figure 4 The method and / or any one or more of the example embodiments described.

[0184] Device 10 includes a radio interface 16. The radio interface 16 can provide communication capabilities to device 10. The radio interface 16 may include a receiver configured to receive information according to at least one cellular or non-cellular standard. The radio interface 16 may include a transmitter configured to transmit information according to at least one cellular or non-cellular standard. The receiver may include more than one receiver. The transmitter may include more than one transmitter. The radio interface 16 may include a transceiver configured to receive and transmit information according to at least one cellular or non-cellular standard. The transceiver may include more than one transceiver.

[0185] Device 10 may include a user interface 18, which includes, for example, at least one of a keyboard, microphone, touch display, monitor, speaker, etc. User interface 18 can be used to control the device by a user. User interface 18 may be external to device 10. For example, device 10 may be connected to another device, such as a computer, via a wireless or wired connection, and device 10 may be controlled by a user via the computer.

[0186] In exemplary embodiments, at least some of the processes described herein may be performed by means including components for performing at least some of the processes. Components for performing the method steps disclosed herein may include software and / or hardware components of means 10. For example, at least one processor 12, memory 14, and computer program code form components for performing one or more methods (or portions thereof) disclosed herein, and any exemplary embodiments (or corresponding portions thereof). As used herein, the term “component” shall be interpreted in the singular, meaning a single element, or in the plural, meaning a combination of single elements. Therefore, the term “component for [performing A, B, C]” shall be interpreted to encompass means having only one component for performing A, B, and C, means having separate components for performing A, B, and C, or means having partially or completely overlapping components for performing A, B, and C. In addition, the terms “component for performing A, component for performing B, component for performing C” should be interpreted as covering an apparatus in which there is only one component for performing A, B and C, or an apparatus in which there are separate components for performing A, B and C, or an apparatus in which there are partially or completely overlapping components for performing A, B and C.

[0187] Although this disclosure has been described above with reference to the accompanying drawings and non-limiting and illustrative examples, it will be apparent to those skilled in the art that the scope of this disclosure is not limited thereto and that it can be modified in many different ways. As technology advances, it will become apparent to those skilled in the art how to further implement and / or modify this disclosure in various ways. Furthermore, it will be clear to those skilled in the art that the exemplary embodiments described herein can, but need not, be combined in various ways with other exemplary embodiments described herein. 3GPP TSG-SA5 Meeting #157 S5-24xxxx Hyderabad, India, October 14-18, 2024 Source: Nokia Title: Rel-19 DP femtobilization support Purpose of the document: Discussion Agenda Item: 7.5.2 1. The requested decision / action This discussion paper provides an overview of femtoseconds. 2 References [1] 3GPP TR 23.700-45: “Study on System aspects of 5G NR Femto”. [2] 3GPP TS 23.501: "System architecture for the 5G System (5GS)". [3] 3GPP TS 23.502: "Procedures for the 5G System (5GS)". [4] 3GPP TS 23.203: "Policy and charging control architecture". 3. Basic Principles 3GPP TR 23.700-45[1] is now available and clearly indicates the need for 5GS to support 5G NR femtocells. SID proposal SP-231797 emphasizes in Chapter 8 that the billing aspect should be evaluated. Therefore, this study should focus on evaluating KI#2 (enabling provisioning of subscribers allowed access to CAG cells and managing access control by CAG owners or authorized administrators) in non-roaming scenarios: • CAG owners or authorized administrators provide CAG information via NEF. • The NEF API (i.e., the parameter supply specified in Clause 4.15.6 of TS 23.502[3]) has been enhanced to support 5G femto-cAG supply. • The CAG owner or authorized administrator provides the CAG information stored in the UDM / UDR. UDM updates CAG information to AMF according to the existing Rel-18 specification. • AMF updates the CAG information to the UE according to the existing Rel-18 specification. The agreed-upon WID (SP-240629) is already in 3GPP TS 23.501[2] and 3GPP TS 23.502[3], which proposes changes to the architecture and its processes. The normative work on the architecture will follow the conclusions of the RAN WG3 study and the conclusions obtained in TR 38.799. Ultimately, the changes will focus on matching the required enhancements with functional and procedural changes to support 5G NR femto deployment; and to enable CAG owners or authorized administrators to supply CAG information via NEF for non-roaming purposes. However, this work is not yet available. The following solutions need to be evaluated in order to identify the billing impact: 1. Functional and process changes to support 5G NR femtosecond deployment. 2. Supplying CAG information to 5G femtosecond service networks 3. Use CAG subscription updates from AF to supply subscribers who are allowed access to CAG cells. 4. Proposal The research project aims to assess the necessary changes in billing to support 5G NR femtoseconds.

Claims

1. A communication apparatus comprising components for: Receive a billing request from the user equipment, including the access identifier, from the network function; A billing data record is created for the user equipment based on the billing request, wherein the billing data record is associated with the access identifier; Receive billing information from the network function, the billing information including the access identifier; and The billing data record is updated based on the received billing information and the access identifier.

2. The apparatus of claim 1, wherein the access identifier comprises at least one of the following: Access node identifier, Femtonode identifier; or Closed access group identifier.

3. The apparatus according to claim 1 or 2, wherein the network function is a session management function.

4. The apparatus of claim 3, wherein the billing information includes data connection domain billing information.

5. The apparatus according to claim 2 or claim 3, comprising components for: Receive a separate billing request, including the access identifier, from another network function, and receive separate billing information, including the access identifier, from the other network function; and The billing data record is updated based on the received additional billing information and the received access identifier.

6. The apparatus of claim 5, wherein the additional network function is an access and mobility function.

7. The apparatus of claim 5 or claim 6, wherein the additional billing information includes connectivity and mobility domain information.

8. The apparatus of claim 1, wherein the network function is an access and mobility function.

9. The apparatus of claim 8, wherein the billing information includes connectivity and mobility domain information.

10. The apparatus according to claim 8 or claim 9, comprising components for: Receive additional billing information from other network functions; Determine that the additional billing information is associated with the user equipment and the access identifier; and The billing data record is updated based on the received additional billing information.

11. The apparatus of claim 10, wherein the additional network function is a session management function.

12. The apparatus of claim 10 or claim 11, wherein the additional billing information includes data connection domain billing information.

13. A communication apparatus comprising components for: At the network function level, a notification is received from another network function that the user equipment has entered or left an area identified by an access identifier, the notification including the area identifier; and In response to the notification, a billing request is provided to the billing network function, the billing request including the access identifier, to create or update a billing data record associated with the access identifier.

14. The apparatus of claim 13, wherein the access identifier comprises at least one of the following: Access node identifier, Femtonode identifier; or Closed access group identifier.

15. The apparatus according to any one of claims 13 or 14, further comprising components for: After receiving a notification that the user equipment has left the area identified by the access identifier Send a billing data request, including the access identifier, to the billing function to close the associated billing data record.

16. The apparatus according to any one of claims 13 to 15, further comprising components for: Send a subscription request to the network function that the user equipment has entered or left the area identified by the access identifier; and The notification received by the user equipment when it enters or leaves the area associated with the access identifier is used as a response to the subscription request.

17. The apparatus of any one of claims 13 to 16, wherein the notification that the user equipment has entered or left the area identified by the access identifier comprises: Mobility events.

18. The apparatus of any one of claims 13 to 15, wherein the notification that the user equipment has entered the area identified by the access identifier comprises: Session establishment request.

19. The apparatus according to any one of claims 13 to 18, wherein the network function is a session management function, and the additional network function is an access and mobility function.

20. A communication apparatus comprising components for: At the network function level, it determines whether the user equipment enters or leaves the area identified by the access identifier; and The access identifier is provided to the billing function to create or update billing data records associated with the access identifier. The access identifier is provided to the billing function in either of the following ways: in a billing request from the user equipment to the billing function; or via another network function in a notification to the other network function that the user equipment has entered or left the area identified by the access identifier.

21. The apparatus of claim 20, further comprising components for: Receive subscription requests from the additional network functions, the subscription requests being used to notify the user equipment when it has entered or left the area identified by the access identifier; and In response to the received notification, the additional network function is provided with the notification that the user equipment has entered or left the area identified by the access identifier.

22. The apparatus of claim 20 or 21, wherein the network function is an access and mobility function, and the additional network function is a session management function.

23. The apparatus according to any one of claims 20 to 22, wherein the access identifier comprises at least one of the following: Access node identifier, Femtonode identifier; or Closed access group identifier.

24. The apparatus according to any one of claims 20 to 23, wherein the component for determining whether the user equipment enters or leaves the area identified by the access identifier includes components for: Receive notifications that the user equipment has entered or left the area identified by the access identifier.

25. The apparatus of claim 24, wherein the notification is received from the access node.

26. The apparatus of claim 25, further comprising components for: The access node is configured to report when the user equipment enters or leaves the area associated with the access identifier; and Receive notifications from the user equipment that it enters or leaves the area associated with the access identifier, as a response to the configuration.

27. The apparatus of any one of claims 25 and 26, wherein the access node comprises at least one cell associated with the region.

28. The apparatus according to any one of claims 1 to 27, wherein the component comprises: At least one processor; And at least one memory storing instructions that, when executed by the at least one processor, cause the device to be executed.

29. A method for communication, comprising: Receive a billing request from the user equipment, including the access identifier, from the network function; A billing data record is created for the user equipment based on the billing request, wherein the billing data record is associated with the access identifier; Receive billing information from the network function, the billing information including the access identifier; and The billing data record is updated based on the received billing information and the access identifier.

30. A method for communication, comprising: At the network function level, a notification is received from another network function that the user equipment has entered or left an area identified by an access identifier, the notification including the area identifier; as well as In response to the notification, a billing request is provided to the billing network function, the billing request including the access identifier, to create or update a billing data record associated with the access identifier.

31. A method for communication, comprising: At the network function level, determine whether the user equipment enters or leaves the area identified by the access identifier; as well as The access identifier is provided to the billing function to create or update a billing data record associated with the access identifier, wherein the access identifier is provided to the billing function in any of the following ways: in a billing request from the user equipment to the billing function; or via the other network function in a notification to the other network function that the user equipment has entered or left the area identified by the access identifier.

32. A computer-readable medium comprising instructions, wherein the instructions, when executed by at least one processor of the apparatus, cause the apparatus to perform the method according to any one of claims 1 to 12, 13 to 19, or 20 to 27.

Images