NF producer selection with extended subscription data

Abstract

Various example embodiments of the subject disclosure relate to an apparatus, method, and computer process for charging. One such example embodiment relates to a method comprising: receiving, by a service producer, a request from a service consumer to provide a service to a subscriber, where the request comprises an identifier of the subscriber; querying from the data repository an indication of a group of service producers associated with the subscriber, wherein the query includes an identifier of the subscriber; receiving, by the service producer, an indication of a service producer group associated with the subscriber in response to requesting the indication of the service producer group associated with the subscriber from the data repository; checking whether the service producer belongs to a service producer group associated with the subscriber; in response to checking that the service producer does not belong to the group of service producers associated with the subscriber: prohibiting the service producer from providing the service to the subscriber; and notifying the service consumer of the group of service producers associated with the subscriber.

Description

Technical Field

[0001] Various example embodiments of the subject disclosure are directed to apparatus, methods, and computer processes for charging.

[0002] abbreviation

[0003] 3GPP Third Generation Partnership Project

[0004] 5G / 6G / 7G fifth generation / sixth generation / seventh generation

[0005] 5GC 5G Core Network

[0006] ABMF account balance management function

[0007] AMF Access Management Function

[0008] API Application Programming Interface

[0009] AR Augmented Reality

[0010] CCS Converged Billing System

[0011] CDR Billing Data Record

[0012] CEF Accounting Enablement Feature

[0013] CGF Billing Gateway Function

[0014] CHF billing function

[0015] cNF Consumer Network Function

[0016] CTF Billing Trigger Function

[0017] EES Edge Enabler Server

[0018] HPLMN Home Public Land Mobile Network

[0019] ID Identifier

[0020] IMS IP Multimedia System

[0021] MMS Multimedia Messaging Service

[0022] MnS Management Services

[0023] NF Network Function

[0024] PCF Policy Charging Function

[0025] PDU Protocol Data Unit

[0026] PGW Packet Data Gateway

[0027] PGW-C Packet Data Gateway - Control

[0028] PLMN Public Land Mobile Network

[0029] RF Rating Function

[0030] SBA Service-Based Architecture

[0031] SMF session management functions

[0032] SMSF Short Message Service Function

[0033] SUPI Subscription Persistent Identifier

[0034] NEF Network Exposure Function

[0035] NRF Network Repository Features

[0036] TS Technical Specifications

[0037] UDM Unified Data Management

[0038] UDR User Data Repository

[0039] UE User Equipment

[0040] UPF User Plane Function

[0041] URLLC Ultra-Reliable and Low-Latency Communications

[0042] VPLMN Access Public Land Mobile Network

[0043] WLAN Wireless Local Area Network

[0044] XR Background Art

[0045] A communication system can be viewed as a facility that enables communication sessions between two or more entities (eg, communication devices, base stations, and / or other nodes) by providing carrier waves between the entities involved in the communication path.

[0046] The communication system may be a wireless communication system. Examples of wireless systems include PLMNs operating based on radio standards (e.g., standards provided by 3GPP), satellite-based communication systems, and different wireless local networks. The wireless local network may, for example, be implemented as a WLAN. Wireless systems may typically be divided into cells and are therefore typically referred to as cellular systems.

[0047] Communication systems and associated equipment typically operate in accordance with a given standard or specification, which specifies what the various entities associated with the system are allowed to do and how it should be achieved. Communication protocols and / or parameters applied to the connection are also typically defined. An example of a set of standards is the so-called 5G standard. Summary of the invention

[0048] The various example embodiments disclosed in the subject matter are intended to address at least a portion of the difficulties and / or problems and / or shortcomings explicitly described herein or apparent to those skilled in the relevant art, so as to provide methods, devices, and computer processes by which mechanisms and / or processes for billing in a network can be improved.

[0049] Several aspects of various example embodiments will be described with respect to certain aspects. These aspects are not intended to indicate the key or essential features of various example embodiments, nor are they intended to be used to limit the scope of this subject disclosure. In view of this subject disclosure, those skilled in the art will readily appreciate other features, aspects, and units of various example embodiments.

[0050] According to a first aspect, there is provided an apparatus comprising:

[0051] at least one processor, and at least one memory storing instructions that, when executed by the at least one processor, cause the apparatus to perform:

[0052] Receiving, by a service producer, a request from a service consumer to provide a service to a subscriber, wherein the request includes an identifier of the subscriber;

[0053] querying a data repository for an indication of a group of service producers associated with the subscriber, wherein the query includes the identifier of the subscriber;

[0054] receiving, by the service producer, the indication of the group of service producers associated with the subscriber in response to requesting the indication of the group of service producers associated with the subscriber from the data repository;

[0055] checking whether the service producer belongs to the service producer group associated with the subscriber;

[0056] In response to checking that the service producer does not belong to the service producer group associated with the subscriber:

[0057] prohibiting the service producer from providing the service to the subscriber; and

[0058] The service consumer is notified of the group of service producers with which the subscriber is associated.

[0059] The identifier of the subscriber may be a subscriber permanent identifier.

[0060] The data repository may be a user data repository and the identifier of the service producer group may be received as part of subscription data of the subscriber.

[0061] The instructions, when executed by the at least one processor, may further cause the apparatus to perform

[0062] monitoring whether the request from the service consumer includes an indication that the service producer is intended to provide the service to the subscriber;

[0063] In response to monitoring the request from the service consumer, the service producer provides the subscriber with

[0064] Instructions for the services described:

[0065] · inhibiting querying the data repository for the indication of the group of service producers and checking whether the service producer belongs to the group of service producers to which the subscriber is associated; and

[0066] Instructing the service producer to provide the service to the subscriber.

[0067] According to a second aspect, there is provided an apparatus comprising:

[0068] at least one processor, and at least one memory storing instructions that, when executed by the at least one processor, cause the apparatus to perform:

[0069] receiving an identifier of a group of service producers in response to requesting a service for a first subscriber from a first service producer;

[0070] selecting a second service producer such that, in the received discovery response, an identifier of the second service producer is associated with an identifier of the group of service producers, wherein the discovery response comprises identifiers of a plurality of service producers, the identifiers of the plurality of service producers comprising an identifier of the first service producer and an identifier of the second service producer, and each of the identifiers of the plurality of service producers is associated with an identifier of a corresponding group of service producers;

[0071] The service for the first subscriber is requested from the second service producer.

[0072] The instructions, when executed by the at least one processor, may also cause the apparatus to perform

[0073] requesting from a repository function identifiers of one or more service producers capable of providing said service to said first subscriber;

[0074] The repository function receives the discovery response in response to the request.

[0075] The instructions, when executed by the at least one processor, may further cause the apparatus to perform

[0076] until the timer expires, selecting the second service producer for each session of the first subscriber without requesting from a repository function an identifier of one or more service producers capable of providing the service to the first subscriber;

[0077] When the timer has expired, selection of the second service producer for the session of the first subscriber is inhibited without requesting from a repository function the identifiers of one or more service producers capable of providing the service to the first subscriber.

[0078] The request for the service for the first subscriber may include

[0079] a subscriber group identifier indicating that the first subscriber belongs to a subscriber group,

[0080] The request for the service for a second subscriber different from the first subscriber may include the subscriber group identifier; and the instructions, when executed by the at least one processor, may further cause the apparatus to perform

[0081] The second service producer is selected for the session of the second subscriber without requesting from a repository function identifiers of one or more service producers that provide the service to the second subscriber.

[0082] The instructions, when executed by the at least one processor, may further cause the apparatus to perform

[0083] selecting the first service producer based on the discovery response;

[0084] The service for the first subscriber is requested from the first service producer.

[0085] The instructions, when executed by the at least one processor, may further cause the apparatus to perform

[0086] The first service producer is selected without regard to the identifier of the group of service producers associated with the identifier of the first service producer.

[0087] Each of the requests for the service may include a subscriber permanent identifier of the first subscriber.

[0088] The instructions, when executed by the at least one processor, may further cause the apparatus to perform

[0089] Along with requesting the service for the first subscriber from the second service producer, indicating to the second service producer that the second service producer is intended to provide the service for the first subscriber.

[0090] According to a third aspect, there is provided an apparatus comprising:

[0091] at least one processor, and at least one memory storing instructions that, when executed by the at least one processor, cause the apparatus to perform:

[0092] receiving a request to provide subscription data to a subscriber, wherein the request includes an identifier of the subscriber;

[0093] retrieving from a data repository an identifier of a group of service producers associated with said identifier of said subscriber;

[0094] In response to said request to provide said subscription data, said identifier of said group of service producers is provided.

[0095] The request may request provision of service subscription data for the subscriber.

[0096] The identifier of the subscriber may be a subscriber permanent identifier.

[0097] According to a fourth aspect, there is provided a method comprising:

[0098] Receiving, by a service producer, a request from a service consumer to provide a service to a subscriber, wherein the request includes an identifier of the subscriber;

[0099] querying a data repository for an indication of a group of service producers associated with the subscriber, wherein the query includes the identifier of the subscriber;

[0100] In response to requesting the data repository for an indication of the group of service producers associated with the subscriber, receiving, by the service producer, the indication of the group of service producers associated with the subscriber;

[0101] checking whether the service producer belongs to the service producer group associated with the subscriber;

[0102] In response to checking that the service producer does not belong to the service producer group associated with the subscriber:

[0103] prohibiting the service producer from providing the service to the subscriber; and

[0104] The service consumer is notified of the group of service producers with which the subscriber is associated.

[0105] The identifier of the subscriber may be a subscriber permanent identifier.

[0106] The data repository may be a user data repository and the identifier of the service producer group may be received as part of subscription data of the subscriber.

[0107] The method may further comprise:

[0108] monitoring whether the request from the service consumer includes an indication that the service producer is intended to provide the service to the subscriber;

[0109] In response to monitoring the request from the service consumer, the service producer provides the subscriber with

[0110] Instructions for the services described:

[0111] · inhibiting querying the data repository for the indication of the group of service producers and checking whether the service producer belongs to the group of service producers to which the subscriber is associated; and

[0112] Instructing the service producer to provide the service to the subscriber.

[0113] According to a fifth aspect, there is provided a method comprising:

[0114] receiving an identifier of a group of service producers in response to requesting a service for a first subscriber from a first service producer;

[0115] selecting a second service producer such that, in the received discovery response, an identifier of the second service producer is associated with an identifier of the group of service producers, wherein the discovery response comprises identifiers of a plurality of service producers, the identifiers of the plurality of service producers comprising an identifier of the first service producer and an identifier of the second service producer, and each of the identifiers of the plurality of service producers is associated with an identifier of a corresponding group of service producers;

[0116] The service for the first subscriber is requested from the second service producer.

[0117] The method may further comprise:

[0118] requesting from a repository function identifiers of one or more service producers capable of providing said service to said first subscriber;

[0119] The repository function receives the discovery response in response to the request.

[0120] The method may further comprise:

[0121] until the timer expires, selecting the second service producer for each session of the first subscriber without requesting from a repository function an identifier of one or more service producers capable of providing the service to the first subscriber;

[0122] When the timer has expired, selection of the second service producer for the session of the first subscriber is inhibited without requesting from a repository function the identifiers of one or more service producers capable of providing the service to the first subscriber.

[0123] The request for the service for the first subscriber may include

[0124] a subscriber group identifier indicating that the first subscriber belongs to a subscriber group,

[0125] The request for the service for a second subscriber different from the first subscriber may include the subscriber group identifier; and the method may further include

[0126] The second service producer is selected for the session of the second subscriber without requesting from a repository function an identifier of one or more service producers capable of providing the service to the second subscriber.

[0127] The method may further comprise:

[0128] selecting the first service producer based on the discovery response;

[0129] The service for the first subscriber is requested from the first service producer.

[0130] Selecting the first service producer may be performed without regard to the identifier of the group of service producers associated with the identifier of the first service producer.

[0131] Each of the requests for the service may include a subscriber permanent identifier of the first subscriber.

[0132] The method may further comprise:

[0133] Along with requesting the service for the first subscriber from the second service producer, indicating to the second service producer that the second service producer is intended to provide the service for the first subscriber.

[0134] According to a sixth aspect, there is provided a method comprising:

[0135] receiving a request to provide subscription data to a subscriber, wherein the request includes an identifier of the subscriber;

[0136] retrieving from a data repository an identifier of a group of service producers associated with said identifier of said subscriber;

[0137] In response to said request to provide said subscription data, said identifier of said group of service producers is provided.

[0138] The request may request provision of service subscription data for the subscriber.

[0139] The identifier of the subscriber may be a subscriber permanent identifier.

[0140] According to each of the first to sixth aspects, the service may include a billing service; the service producer may include a billing function; and the service producer group may include a billing function group.

[0141] Each of the methods in the fourth to sixth aspects may be a method selected by a NF producer, particularly a method selected by a CHF producer.

[0142] According to a seventh aspect, there is provided a computer process product comprising an instruction set, which when executed on a device is configured to cause the device to perform a method according to any one of aspects 4 to 6. The computer process product may be embodied as a computer readable medium or may be directly loaded into a computer.

[0143] According to some example embodiments, at least one of the following advantages may be achieved:

[0144] · ensuring that the expected CHF is available for the subscriber;

[0145] It can reduce latency.

[0146] Consumers of NF services (particularly: NChf services (billing services)) provided by CHF do not need to find out the correct (expected) CHF;

[0147] The same applies to other services, where service producers can be grouped and groups can be associated with subscribers. BRIEF DESCRIPTION OF THE DRAWINGS

[0148] In the following, some exemplary embodiments will be described in more detail by way of non-limiting and illustrative examples with reference to the accompanying drawings, in which:

[0149] Figure 1 shows the charging architecture according to 3GPP TS 32.240;

[0150] Figure 2 shows a message flow according to some example embodiments;

[0151] Figure 3 An apparatus according to an example embodiment is shown;

[0152] Figure 4 A method according to an example embodiment is shown;

[0153] Figure 5 An apparatus according to an example embodiment is shown;

[0154] Figure 6 A method according to an example embodiment is shown;

[0155] Figure 7 An apparatus according to an example embodiment is shown;

[0156] Figure 8 A method according to an example embodiment is shown;

[0157] Fig. 9 An apparatus according to an example embodiment is shown. DETAILED DESCRIPTION

[0158] Certain example embodiments will be described in detail below with reference to the accompanying drawings, wherein the features of the example embodiments may be freely combined with each other unless otherwise specified. However, it should be clearly understood that the description of certain example embodiments is provided only by way of non-limiting and illustrative examples and is by no means intended to be understood as limiting.

[0159] The terms used herein are generally used only to describe certain example embodiments and are not intended to be limiting. Hereinafter, unless otherwise defined, all technical and scientific terms used herein may have the same meaning as commonly understood by one of ordinary skill in the art to which this subject disclosure belongs.

[0160] References in the subject disclosure to "example embodiments," "some example embodiments," "certain example embodiments," "various example embodiments," etc. indicate that the referenced embodiments may include a particular feature, structure, or characteristic, but not every example embodiment described herein may include the particular feature, structure, or characteristic. Furthermore, these phrases do not necessarily refer to the same example embodiment. Furthermore, when particular features, structures, or characteristics are described in conjunction with example embodiments, it should be understood that it is within the knowledge of those skilled in the art to combine such features, structures, or characteristics with any other example embodiments described herein, whether or not such a combination is explicitly described.

[0161] As used herein, the singular forms "a", "an" and "the" are intended to include the plural forms as well, unless the context clearly indicates otherwise. It will be further understood that when used herein, the terms "include", "comprise", "have" and / or "contain" specify the presence of stated features, elements and / or components, etc., but do not preclude the presence or addition of one or more other features, elements, components and / or combinations thereof.

[0162] Furthermore, it should be understood that the apparatus is configured to perform the corresponding method, although in some cases only the apparatus or the method is described.

[0163] Before describing various example embodiments in detail, certain aspects of the 5G wireless communication system are briefly explained.

[0164] In non-roaming scenarios, the SMF may select a CHF instance at PDU session establishment based on the following priorities (see 3GPP TS 32.255, clause 5.1.8):

[0165] • The CHF address with possible associated CHF instance ID and / or CHF set ID provided by the PCF for the PDU session.

[0166] · UDM provides billing features.

[0167] Based on the findings of NRF.

[0168] Billing features provided locally by SMF.

[0169] In roaming situations, the same principle applies to the V-SMF when selecting a CHF in the VPLMN in the home routing scenario. For CHF selection in the HPLMN, the V-SMF may not consider the CHF address provided by the PCF, the charging features provided by the UDM, and the charging features provided locally by the SMF, but only consider the discovery based on the NRF.

[0170] SMF is an example of a CHF consumer. Other consumers of CHF may be SMF, SMSF, AMF, SMF+PGW-C, NEF, IMS node, MMS node, CEF, MnS producer or EES. Figure 1 The logical ubiquitous charging architecture according to 3GPP TS 32.240 is shown. The CHF consumer communicates with the CHF (which is part of the CCS) through the Nchf interface. The other components of the CCS are the ABMF, CGF and RF. The CHF is connected to the charging domain (via the CGF ( Figure 1 The CHF may include an online charging function (OCF) that provides a quota management function under the credit control term, and / or a charging data function (CDF) that provides a CDR generation function for charging events received from the CTF or CEF through the Nchf interface.

[0171] CHF provides the services shown in Table 1. Table 1 also includes a list of example consumers for each service.

[0172]

[0173]

[0174] Table 1: NF services provided by CHF

[0175] CHFs can be grouped into CHF groups. For example, a CHF group can be associated with an enterprise customer or a customer of a specific branch of an operator to provide billing for these subscribers. In UDM / UDR, a CHF group can be associated with each subscriber or subscriber group.

[0176] Currently, SUPI is used for NRF-based discovery of CHF. The CHF discovery mechanism does not support NF consumers (such as SMF, AMF, SMSF and PCF) to discover CHF based on information about the network segment to which the CHF belongs. For example:

[0177] In network deployment, CHF groups may be deployed to support billing for enterprise customers.

[0178] • It is also possible to deploy CHF groups to support billing of customers belonging to a specific branch of an operator.

[0179] There are obvious benefits in selecting a CHF that is closer to the UE, and if there is an edge infrastructure, the CHF should be the one in the edge infrastructure.

[0180] If the network includes multiple CHFs, the cNF shall use the CHF associated with the subscriber through the CHF group. In 3GPP Rel-17, the CHF can register with the NRF using the CHF-Group-ID (and other parameters such as CHF-Hostname, IPAddress, etc.). The NF consumer can use the CHF-Group-ID during the CHF discovery process through the NRF.

[0181] Nevertheless, the current mechanism is not sufficient to ensure that a subscriber is served by a CHF of the CHF group associated with the subscriber for the following reasons:

[0182] Some NF consumers of CHF (consumers listed in Table 1) do not have a CHF associated with the UE -

[0183] Group-ID information.

[0184] Not all NF consumers (e.g. SMSF, CEF, MnS Producer, EES, etc.) may have access to the Group ID mapping stored in the UDR.

[0185] • This requires the UDR to store / maintain a mapping of subscribers in the network to the corresponding CHF-Group-ID so that the correct CHF belonging to the correct Group ID can serve its subscribers.

[0186] In view of these limitations, it may be considered to implement a specific mechanism for each type of NF consumer to identify the correct CHF for the UE based on the CHF group. However, for some use cases, it is not recommended that each CHF consumer implements business logic to identify the correct CHF. Instead, for some use cases, it is recommended that the CHF is self-contained and identifies the correct CHF by itself. Some example embodiments provide such business logic, which may be applicable to any type of CHF consumer, or may be limited to certain types of CHF consumers.

[0187] Some example embodiments are described in more detail below:

[0188] According to some example embodiments, ChfSubscriptionData is maintained at the UDM / UDR. Thus, service consumers of the UDM and UDR can obtain ChfSubscriptionData including at least the CHF Group ID. ChfSubscriptionData can be stored in the UDM / UDR for a group of UEs or for each individual UE, for example, in the same way as other SubscriptionData is maintained in the UDM / UDR.

[0189] This additional field in UDM / UDR may be defined in 3GPP TS29.503 (Unified Data Management Services; Stage 3) and 3GPP TS29.505 (Use of Unified Data Repository Services for Subscription Data; Stage 3). Table 2 shows an example definition of ChfSubscriptionData.

[0190]

[0191] Table 2: Example definition of ChfSubscriptionData

[0192] According to some example embodiments, the Nudr interface (defined by 3GPP TS29.505) allows the CHF to retrieve data from the UDM / UDR. The CHF may obtain the ChfSubscriptoinData for each UE.

[0193] Figure 2 A message sequence chart according to some example embodiments is shown. Figure 2 The actions in are as follows:

[0194] 1. NF Service Consumer (any type) wants to access Nchf service for CHF of subscriber (UE). Therefore, NF Service Consumer sends a discovery request to NRF to discover appropriate CHF. The discovery request includes the subscriber's SUPI as one of the query parameters.

[0195] 2. As part of the discovery response, the NRF provides a list of IDs of one or more CHFs that meet the discovery criteria. The discovery response includes the corresponding CHF group ID for each CHF. In the following, it is assumed that the discovery response includes the IDs of multiple CHFs belonging to at least two different CHF groups.

[0196] 3.NF service consumer selects a CHF ID ( Figure 2 The service request includes the subscriber's SUPI.

[0197] 3a. After receiving the service request from the NF service consumer (action 3), the NF service producer (CHF1) queries the UDM / UDR and requests the ChfSubsrciptionData corresponding to the SUPI.

[0198] 3b. In response to the query from CHF1 (action 3a), UDM / UDR provides the CHF Group ID to CHF1 as part of the ChfSubscriptionData.

[0199] 3c. CHF1 checks whether the CHF group ID received from UDM / UDR is identical to one of its own CHF group IDs.

[0200] 3d. If CHF1 checks that the CHF Group ID received from UDM / UDR is identical to one of its own CHF Group IDs, then CHF1 knows that it is the appropriate CHF to provide NChf services to the subscriber identified by the SUPI. Therefore, it processes the service request and responds to the NF Service Consumer.

[0201] 3e. If CHF1 checks that the CHF Group ID received from UDM / UDR is not the same as any of its own CHF Group IDs, then CHF1 knows that it is not the right CHF to provide NChf services to the subscriber identified by the SUPI. Therefore, CHF1 provides the CHF Group ID (SUPI's CHF Group ID) received from UDM / UDR in action 3b in response to the service request from the NF service consumer (action 3). Typically, the response may include an error code (e.g., 307). The SUPI's CHF Group ID and the error code (if any) may be part of the header of the response message.

[0202] Actions 4 and 5 follow action 3e but not action 3d, ie if CHF1 checks that the CHF group ID received from UDM / UDR is not identical to any of its own CHF group IDs.

[0203] 4. The NF service consumer reselects another CHF based on the discovery result received from the NRF in action 2 and the CHF group ID of the SUPI received from CHF1 in operation 3e. Figure 2 In more detail, the NF Service Consumer selects one of the CHFs (e.g. CHF2) in the CHF list received in the discovery response (action 2) from the NRF, such that the CHF Group ID associated with this CHF ID in the discovery response is the same as the CHF Group ID received in the response from CHF1 in action 3e.

[0204] 5. The NF service consumer invokes the Nchf service API towards CHF2 to request the provision of Nchf service for the subscriber identified by the SUPI. Action 5 for CHF2 corresponds to Action 3 for CHF1.

[0205] The NF service consumer may then use CHF2 for subsequent Nchf service requests for the subscriber identified by the SUPI.

[0206] For the replacement of CHF (CHF2, Figure 2 In the selection of action 4), the NF service consumer may consider other parameters besides the CHF group ID, such as the NF set.

[0207] In some example embodiments, the expiration timer may be associated with the CHF Group ID of the subscriber received from CHF1. For example, the timer may be provided by the UDM / UDR and forwarded to the NF Service Consumer via CHF1, or the timer may be started at the NF Service Consumer when the NF Service Consumer receives the CHF Group ID from CHF1 (action 3e). The duration until the timer expires may be predefined or provided to the NF Service Consumer (via CHF1) by the UDM / UDR. The NF Service Consumer may select CHF2 for different sessions of the subscriber until the timer expires. The NF Service Consumer may then run again as in Figure 2 Same process as shown.

[0208] The request for providing the billing service may include a group ID indicating that the subscriber belongs to a subscriber group. If the same group ID is indicated in the request for providing the billing service for another subscriber, the CHF ( Figure 2 CHF2 in the example) can also be used for another subscriber.

[0209] In some example embodiments, when the NF service consumer requests the Nchf service for the second time ( Figure 2When CHF2 receives the Nchf service request of action 5, which includes an indication that CHF2 is the expected CHF of the subscriber (e.g., a set flag), CHF2 does not need to check again whether CHF2 is the expected CHF of the subscriber with the help of UDM / UDR.

[0210] Table 3 shows CDR request message attributes according to some example embodiments. For example, these CDR message attributes may be defined by 3GPP TS 32.255 Table 6.1.1.2.1.

[0211]

[0212]

[0213] Table 3: CDR request message attributes according to some example embodiments

[0214] Table 4 shows CDR response message attributes according to some example embodiments. For example, these CDR message attributes may be defined by 3GPP TS 32.255 Table 6.1.1.2.2.

[0215]

[0216] Table 4: CDR Response Message Attributes According to Some Example Embodiments

[0217] In the above, some example embodiments are explained for billing as a service, where CHF is a service producer, each CHF belongs to at least one CHF group, and subscribers are associated with the CHF group. However, some example embodiments may be applied to services other than billing, where each service producer of the service belongs to at least one service producer group, and subscribers are associated with at least one service producer group.

[0218] Figure 3 An apparatus according to an example embodiment is shown. In some example embodiments, the apparatus may include a CHF function or be implemented as a unit of a CHF. In some example embodiments, the apparatus may be configured to operate as a CHF. For example, the apparatus may be configured to perform one or more functions of a CHF. Figure 4 A method according to an example embodiment is shown. Figure 3 The device can perform Figure 4 method, but not limited to this method. Figure 4 The method can be Figure 3 The present invention is performed by a device, but is not limited to being performed by the device.

[0219] The apparatus includes a first means for receiving 110, a means for querying 120, a second means for receiving 130, a means for checking 140, a means for prohibiting 150, and a means for notifying 160. The first means for receiving 110, the means for querying 120, the second means for receiving 130, the means for checking 140, the means for prohibiting 150, and the means for notifying 160 may be a first receiving means, a query means, a second receiving means, a checking means, a prohibiting means, and a notifying means, respectively. The first means for receiving 110, the means for querying 120, the second means for receiving 130, the means for checking 140, the means for prohibiting 150, and the means for notifying 160 may be a first receiver, a queryer, a second receiver, a checker, a prohibitor, and a notifier, respectively. The first receiving component 110, the querying component 120, the second receiving component 130, the checking component 140, the prohibiting component 150 and the notifying component 160 may be a first receiving processor, a querying processor, a second receiving processor, a checking processor, a prohibiting processor and a notifying processor, respectively.

[0220] The first receiving component 110 receives a request from a service consumer to provide a service (eg, a billing service) to a subscriber through a service producer (eg, a billing function) (S110). The request includes an identifier of the subscriber, such as a SUPI.

[0221] The means 120 for querying queries a data repository (eg, UDM / UDR) for an indication of a service producer group (eg, CHF group) to which the subscriber is associated (S120). The query includes an identifier of the subscriber.

[0222] The second receiving component 130 receives an indication of a service producer group associated with the subscriber through the service producer (S130). In response to a request for an indication of a service producer group associated with the subscriber, i.e., in response to the query of S120, the second receiving component 130 receives an indication of a service producer group from a data repository.

[0223] The checking means 140 checks whether the service producer belongs to the service producer group associated with the subscriber (S140). That is, the checking means identifies the service producer group to which the service producer belongs and compares it with the service producer group indicated in S130.

[0224] In response to checking that the service producer does not belong to the service producer group associated with the subscriber (S140=No), the actions of the component 150 for prohibiting and the component 160 for notifying are as follows:

[0225] The prohibition component 150 prohibits the service producer from providing services to the subscriber (S150). The notification component 160 notifies the service consumer of the service producer group associated with the subscriber (S160), ie, the service producer group received in S130.

[0226] S150 and S160 can be executed in any order. They can be executed completely or partially in parallel.

[0227] Figure 5 An apparatus according to an example embodiment is shown. In some example embodiments, the apparatus may include NF consumer (e.g., NF consumer of CHF) functionality or be implemented as an element of such NF consumer. In some example embodiments, the apparatus may be configured to operate as a NF consumer (e.g., NF consumer of CHF). For example, the apparatus may be configured to perform one or more functions of a NF consumer (e.g., NF consumer of CHF). Figure 6 A method according to an example embodiment is shown. Figure 5 The device can execute Figure 6 method, but not limited to this method. Figure 6 The method can be Figure 5 The present invention is performed by a device, but is not limited to being performed by the device.

[0228] The apparatus includes a receiving component 210, a selecting component 220, and a requesting component 230. The receiving component 210, the selecting component 220, and the requesting component 230 may be a receiving component, a selecting component, and a requesting component, respectively. The receiving component 210, the selecting component 220, and the requesting component 230 may be a receiver, a selector, and a requester, respectively. The receiving component 210, the selecting component 220, and the requesting component 230 may be a receiving processor, a selecting processor, and a requesting processor, respectively.

[0229] The receiving means 210 receives an identifier of a service producer group (eg, CHF group) (S210). In response to requesting a service (eg, billing service) for a subscriber from a first service producer (eg, billing function), the receiving means 210 receives an identifier of a service producer group.

[0230] The component 220 for selecting selects a second service producer (e.g., a second billing function) (S220). The component 220 for selecting selects the second service producer so that in the received discovery response, the identifier of the second service producer is associated with the identifier of the service producer group. The discovery response can be received in response to the discovery request and includes identifiers of multiple service producers. The identifiers of the multiple service producers include an identifier of the first service producer and an identifier of the second service producer. Each of the identifiers of the multiple service producers is associated with an identifier of the corresponding service producer group.

[0231] The means 230 for requesting requests the second service producer selected in S220 for the service for the subscriber (S230).

[0232] Figure 7 An apparatus according to an example embodiment is shown. In some example embodiments, the apparatus may include data repository (e.g., UDM / UDR) functionality or be implemented as an element of such a data repository. In some example embodiments, the apparatus may be configured to operate as a data repository (e.g., UDM / UDR). For example, the apparatus may be configured to perform one or more functions of a data repository (e.g., UDM / UDR). Figure 8 A method according to an example embodiment is shown. Figure 7 The device can perform Figure 8 method, but not limited to this method. Figure 8 The method can be Figure 7 The present invention is performed by a device, but is not limited to being performed by the device.

[0233] The device includes a component 310 for receiving, a component 320 for retrieving, and a component 330 for providing. The component 310 for receiving, the component 320 for retrieving, and the component 330 for providing can be a receiving component, a retrieving component, and a providing component, respectively. The device 310 for receiving, the component 320 for retrieving, and the component 330 for providing can be a receiver, a retriever, and a provider, respectively. The component 310 for receiving, the component 320 for retrieving, and the component 330 for providing can be a receiving processor, a retrieving processor, and a providing processor, respectively.

[0234] The receiving means 310 receives a request for providing subscription data to a subscriber (S310). The request includes an identifier of the subscriber.

[0235] The means for retrieving 320 retrieves the identifier of the service producer group (eg, CHF group) associated with the identifier of the subscriber from the data repository (eg, UDM / UDR) (S320).

[0236] In response to the request to provide the subscription data of S310, the component 330 for providing provides an identifier of the service producer group (S330).

[0237] Fig. 9 An apparatus according to an example embodiment is shown. The apparatus comprises at least one processor 810, at least one memory 820, the memory 820 storing instructions, which when executed by at least one processor 810 causes the apparatus to perform a method according to at least one of the following figures and related descriptions: Figure 4 ,or Figure 6 ,or Figure 8 .

[0238] In some example embodiments, at least one processor 810 may be of any type suitable for the local technology network, and may include one or more of the following: a general purpose computer, a special purpose computer, a microprocessor, a digital signal processor (DSP), and a processor based on a multi-core processor architecture, as non-limiting and illustrative examples. The device may have multiple processors, such as application specific integrated circuit chips, which are time-slaved to a clock synchronized with a main processor.

[0239] In some example embodiments, at least one memory 820 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), electrically programmable read-only memory (EPROM), flash memory, hard disk, compact disk (CD), digital video disk (DVD), optical disk, laser disk, and other magnetic and / or optical memories. Examples of volatile memories include, but are not limited to, random access memory (RAM) and other volatile memories that do not persist during power outages.

[0240] In some example embodiments, a program (e.g., a computer program) may be provided that includes executable instructions executed by at least one processor 810. The instructions of the program may include instructions for performing the operations / actions of some example embodiments of the present disclosure. The program may be stored in at least one memory 820, such as a ROM. At least one processor 810 may perform any suitable actions and processes by loading the program into RAM.

[0241] The exemplary embodiments of the present disclosure may be implemented by a program such that Fig. 9 The device may be configured to perform any of the processes of the present disclosure, such as reference Figure 4 , Figure 6 or Figure 8 Various exemplary embodiments of the present disclosure may also be implemented by hardware or a combination of software and hardware.

[0242] In some example embodiments, the program may be tangibly embodied in a computer-readable medium, which may be included in Fig. 9 in an apparatus (e.g., in at least one memory 820) or in other storage devices accessible to the apparatus. Fig. 9 The device may be configured to load the program from the computer-readable medium to the RAM 822 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.

[0243] The term "non-transitory" as used herein refers to a limitation of the medium itself (eg, tangible, as opposed to a signal), rather than a limitation of data storage persistence (eg, RAM versus ROM).

[0244] Some example embodiments are explained for 5G (NR). However, other example embodiments may be used for other 3GPP generations, such as 4G, 6G, 7G, etc., or for other wireless or wired communication devices.

[0245] Some example embodiments are described with SUPI as the ID of the subscriber (UE). However, according to some example embodiments, another ID of the subscriber (eg, MSISDN) may be used.

[0246] UE is an example of a terminal. Other examples are MTC devices. Each terminal can be implemented as a smart phone, a mobile phone, a laptop, a sensor device, etc. A typical terminal is a cellular communication device for communicating in a cellular network (such as a 3GPP network), but this is not mandatory.

[0247] Unless otherwise specified or clear from the context, the term “CHF” or “service producer” may be understood as a “CHF instance” and a “service producer instance”, respectively.

[0248] A piece of information can be sent from one entity to another in one or more messages. Each of these messages can include further (different) information.

[0249] The names of network elements, network functions, protocols and methods are based on current standards. In other versions or other technologies, the names of these network elements and / or network functions and / or protocols and / or methods may be different, as long as they provide corresponding functions. The same applies to terminals.

[0250] Unless otherwise specified or the context clearly dictates otherwise, the statement that two entities are different means that they perform different functions. This does not necessarily mean that they are based on different hardware. That is, each entity described in this subject disclosure may be based on different hardware, or some or all of the entities may be based on the same hardware. This does not necessarily mean that they are based on different software. That is, each entity described in this subject disclosure may be based on different software, or some or all of the entities may be based on the same software. Each entity described in this subject disclosure may be deployed in the cloud.

[0251] From the above description, it is apparent that example embodiments provide, for example, a service producer (e.g., a billing function) or elements thereof, devices embodying the same, methods of controlling and / or operating the same, computer programs for controlling and / or operating the same, and media that carry such computer programs and form computer program products.

[0252] From the above description, it is apparent that the example embodiments, for example, provide a consumer of a service provided by a service producer (for example, a consumer of a billing service provided by a billing function (for example, SMF, SMSF, AMF, SMF+PGW-C, NEF, IMS-node, MMS-node, CEF, MnS producer, or EES)) or an element thereof, an apparatus embodying the same, a method of controlling and / or operating the same, a computer program for controlling and / or operating the same, and a medium that carries such a computer program and forms a computer program product).

[0253] Based on the above description, it should be apparent that the example embodiments provide, for example, a data repository (e.g., a UDM, a UDR, or a UDM / UDR) or elements thereof, an apparatus embodying the same, a method of controlling and / or operating the same, a computer program for controlling and / or operating the same, and a medium that carries such a computer program and forms a computer program product.

[0254] As non-limiting and illustrative examples, implementations of any of the above blocks, devices, systems, techniques, or methods include implementations of hardware, software, firmware, dedicated circuits or logic, circuits, general-purpose hardware or controllers, or other computing devices, or some combination thereof. Each entity described in this subject disclosure may be embodied in the cloud. As used herein, the term "circuitry" may refer to one or more or all of the following example embodiments:

[0255] (a) pure hardware circuit implementation (e.g. implementation in analog and / or digital circuits only) and

[0256] (b) a combination of hardware circuitry and software, such as (where applicable):

[0257] (i) a combination of analog and / or digital hardware circuitry and software / firmware, and

[0258] (ii) any portion of a hardware processor (including a digital signal processor), software and memory with software that works together to enable a device such as a mobile phone or server to perform various functions, and

[0259] (c) Hardware circuits and / or processors (such as a microprocessor or portion of a microprocessor) that require software (such as firmware) for operation, but the software may not be present when it is not needed for operation.

[0260] This definition of circuitry applies to all uses of this term herein, including in any claims. As a further example embodiment, as used herein, the term circuitry also covers implementations of only a hardware circuit or processor (or multiple processors) or a portion of a hardware circuit or processor and its accompanying software and / or firmware. The term circuitry also covers, for example, a baseband integrated circuit or processor integrated circuit for a mobile device or a similar integrated circuit in a server, cellular network node, or other computing or network node, if applicable to the particular claim element.

[0261] As used herein, unless explicitly stated, performing a step “in response to A” does not indicate that the step is performed immediately after “A” occurs, and one or more intermediate steps may be included between “A” and the step.

[0262] As used herein, the terms "first X" and "second X" include options where the "first X" is the same as the "second X" and where the "first X" is different from the "second X", unless otherwise specified. It should be understood that although the terms "first", "second", etc. may be used herein to describe various elements, these elements should not be limited by these terms. These terms are only used to distinguish one element from another. For example, a first element may be referred to as a second element, and similarly, a second element may be referred to as a first element without departing from the scope of the example embodiments.

[0263] As used herein, "at least one of: " and "at least one of " and similar expressions, where a list of two or more elements is connected by "and" or "or", mean at least any one of the elements, or at least any two or more of the elements, or at least all of the elements. As used herein, the term "and / or" includes any and all combinations of one or more of the associated listed terms.

[0264] Although various exemplary embodiments of the subject disclosure have been described in language specific to structural features and / or method actions, it should be understood that the various exemplary embodiments of the subject disclosure are not necessarily limited to the above-mentioned specific features or actions. Rather, the specific features and actions described herein are disclosed as example forms for implementing the various exemplary embodiments of the subject disclosure.

Claims

1. A device comprising: at least one processor, and at least one memory storing instructions that, when executed by the at least one processor, cause the apparatus to perform: Receiving, by a service producer, a request from a service consumer to provide a service to a subscriber, wherein the request includes an identifier of the subscriber; querying a data repository for an indication of a group of service producers associated with the subscriber, wherein the query includes the identifier of the subscriber; receiving, by the service producer, the indication of the group of service producers associated with the subscriber in response to requesting the indication of the group of service producers associated with the subscriber from the data repository; checking whether the service producer belongs to the service producer group associated with the subscriber; In response to checking that the service producer does not belong to the service producer group associated with the subscriber: prohibiting the service producer from providing the service to the subscriber; and The service consumer is notified of the group of service producers with which the subscriber is associated.

2. The device according to claim 1, wherein: The identifier of the subscriber is a subscriber permanent identifier.

3. A device comprising: at least one processor, and at least one memory storing instructions that, when executed by the at least one processor, cause the apparatus to perform: receiving an identifier of a group of service producers in response to requesting a service for a first subscriber from a first service producer; selecting a second service producer such that, in the received discovery response, an identifier of the second service producer is associated with an identifier of the group of service producers, wherein the discovery response comprises identifiers of a plurality of service producers, the plurality of identifiers of the plurality of service producers comprising an identifier of the first service producer and an identifier of the second service producer, and each of the plurality of identifiers of the plurality of service producers is associated with an identifier of a corresponding group of service producers; The service for the first subscriber is requested from the second service producer.

4. The device according to claim 3, wherein: The instructions, when executed by the at least one processor, further cause the apparatus to perform: requesting from a repository function identifiers of one or more service producers capable of providing said service to said first subscriber; In response to requesting the repository function, receiving the discovery response.

5. A device comprising: at least one processor, and at least one memory storing instructions that, when executed by the at least one processor, cause the apparatus to perform: receiving a request to provide subscription data to a subscriber, wherein the request includes an identifier of the subscriber; retrieving from a data repository an identifier of a group of service producers associated with said identifier of said subscriber; In response to said request to provide said subscription data, said identifier of said group of service producers is provided.

6. The device according to claim 5, wherein: The request requests provision of service subscription data to the subscriber.

7. A method comprising: Receiving, by a service producer, a request from a service consumer to provide a service to a subscriber, wherein the request includes an identifier of the subscriber; querying a data repository for an indication of a group of service producers associated with the subscriber, wherein the query includes the identifier of the subscriber; receiving, by the service producer, the indication of the group of service producers associated with the subscriber in response to requesting the indication of the group of service producers associated with the subscriber from the data repository; checking whether the service producer belongs to the service producer group associated with the subscriber; In response to checking that the service producer does not belong to the service producer group associated with the subscriber: prohibiting the service producer from providing the service to the subscriber; and The service consumer is notified of the group of service producers with which the subscriber is associated.

8. A method comprising: receiving an identifier of a group of service producers in response to requesting a service for a first subscriber from a first service producer; selecting a second service producer such that, in the received discovery response, an identifier of the second service producer is associated with an identifier of the group of service producers, wherein the discovery response comprises identifiers of a plurality of service producers, the plurality of identifiers of the plurality of service producers comprising an identifier of the first service producer and an identifier of the second service producer, and each of the plurality of identifiers of the plurality of service producers is associated with an identifier of a corresponding group of service producers; The service for the first subscriber is requested from the second service producer.

9. A method comprising: receiving a request to provide subscription data to a subscriber, wherein the request includes an identifier of the subscriber; retrieving from a data repository an identifier of a group of service producers associated with said identifier of said subscriber; In response to the request to provide the subscription data, the identifier of the group of service producers is provided.

10. A computer process product comprising a set of instructions which, when executed on a device, are configured to cause the device to perform the method according to any one of claims 7 to 9.

Images