New publicly available events and their usage against AF, NEF and UDM
By introducing 'SUPI-GPSI association change' monitoring events into the cellular network, the problem of SIM replacement event detection and notification is solved, enabling timely detection of SIM replacement and enhanced user authentication, thus ensuring the trustworthiness of user identities.
Patent Information
- Application Number
- CN202610607812.5
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Priority Date
- 2025-05-09
- Filing Date
- 2026-05-06
- Publication Date
- 2026-11-10
AI Technical Summary
The lack of standard methods in existing cellular network systems for detecting and notifying changes in the association between user equipment identifiers, particularly SIM replacement events, leads to challenges in fraud detection and user authentication.
A new monitoring event type, 'SUPI-GPSI association change', is introduced, providing event reporting to monitor and notify SIM replacements through enhanced services of NEF and UDM, including managing identifier associations of user equipment in the cellular network and receiving and reporting related events.
It enables timely detection and notification of SIM replacement events, supports fraud detection and enhanced user authentication, and ensures the trustworthiness of user identities.
Smart Images

Figure CN123075480A_ABST
Abstract
Description
Technical Field
[0001] Examples of embodiments in this document generally relate to cellular networks, and more specifically, to the same events and notifications for devices connected to such cellular networks. Background Technology
[0002] The core network (CN) of a cellular system contains multiple network functions (NFs). One important function is the Network Exposure Function (NEF). The NEF provides a platform that exposes selected network functions as new services by integrating APIs (Application Programming Interfaces), enabling developers to securely and uniformly access these exposed network functions. This includes, for example, the secure exposure of network services to Application Functions (AFs), such as those used by third-party applications. Specifically, the NEF can act as a "gatekeeper" for the CN, handling authentication and authorization outside the CN for AFs to communicate with NFs within the CN.
[0003] Another feature is the Unified Data Management (UDM) function. UDM plays a role in managing user-related data, such as subscriber profiles, authentication credentials, and authorization policies.
[0004] An Application Function (AF) is a function that can reside either inside or outside a Network Component (CN). An AF interacts with the CN to provide services. In other words, an AF allows applications to communicate with Network Components (NFs) within the CN, such as accessing user-related data. When an AF is located outside the CN, it must interact with NFs (such as UDMs) through a gateway in the Network Element (NEF).
[0005] There are situations where applications may want to monitor events via AF, and this can be improved. Summary of the Invention
[0006] This section is intended to provide examples and is not intended to be limiting.
[0007] In the example, a method is disclosed that includes: managing an association between a first identifier and a second identifier for a user device in the core network of a cellular network, wherein a change in the association between the first identifier and the second identifier for the user device indicates a change in an end-user subscription; receiving a request for an event report related to a change in the association between the first identifier and the second identifier for the user device; detecting the change in the association; and reporting the detected change to a network function in the core network.
[0008] Additional examples include a computer program that includes instructions for performing the methods described in the preceding paragraph when the computer program is run on the device. The computer program according to this paragraph is a computer program product comprising a computer-readable medium carrying instructions embodied therein for use with the device. Another example is a computer program according to this paragraph that can be directly loaded into the internal memory of the device.
[0009] An example of an apparatus includes one or more processors and one or more memories storing instructions that, when executed by the one or more processors, cause the apparatus to at least perform: managing an association between a first identifier and a second identifier for a user equipment in the core network of a cellular network, wherein a change in the association between the first identifier and the second identifier for the user equipment indicates a change in an end-user subscription; receiving a request for an event report related to a change in the association between the first identifier and the second identifier for the user equipment; detecting the change in the association; and reporting the detected change to network functions in the core network.
[0010] An example of a computer program product includes a computer-readable storage medium carrying instructions that, when executed by a device, cause the device to perform at least the following: in the core network of a cellular network, managing an association between a first identifier and a second identifier for a user equipment, wherein a change in the association between the first identifier and the second identifier for the user equipment indicates a change in an end-user subscription; receiving a request for an event report related to a change in the association between the first identifier and the second identifier for the user equipment; detecting the change in the association; and reporting the detected change to network functions in the core network.
[0011] In another example, an apparatus includes components for: managing an association between a first identifier and a second identifier for a user equipment in the core network of a cellular network, wherein a change in the association between the first identifier and the second identifier for the user equipment indicates a change in an end-user subscription; receiving a request for an event report related to a change in the association between the first identifier and the second identifier for the user equipment; detecting the change in the association; and reporting the detected change to network functions in the core network.
[0012] In one example, a method is disclosed that includes: in the core network of a cellular network, determining that an association between a first identifier and a second identifier for a user equipment should be monitored, and determining that an event for the association should be reported, wherein a change in the association between the first identifier and the second identifier for the user equipment indicates a change in an end-user subscription; and sending a request for event reporting to a network function in the core network to request that the association between the first identifier and the second identifier for the user equipment be monitored and the event for the association be reported.
[0013] Additional examples include a computer program that includes instructions for performing the methods described in the preceding paragraph when the computer program is run on the device. The computer program according to this paragraph is a computer program product comprising a computer-readable medium carrying instructions embodied therein for use with the device. Another example is a computer program according to this paragraph that can be directly loaded into the internal memory of the device.
[0014] An example of an apparatus includes one or more processors and one or more memories storing instructions that, when executed by the one or more processors, cause the apparatus to perform at least: in the core network of a cellular network, determining that an association between a first identifier and a second identifier for a user equipment should be monitored, and determining that an event for the association should be reported, wherein a change in the association between the first identifier and the second identifier for the user equipment indicates a change in an end-user subscription; and sending a request for event reporting to a network function in the core network to request that the association between the first identifier and the second identifier for the user equipment be monitored and the event for the association to be reported.
[0015] An example of a computer program product includes a computer-readable storage medium carrying instructions that, when executed by a device, cause the device to perform at least the following: in the core network of a cellular network, determining that an association between a first identifier and a second identifier for a user equipment should be monitored, and determining that an event for the association should be reported, wherein a change in the association between the first identifier and the second identifier for the user equipment indicates a change in an end-user subscription; and sending a request for event reporting to a network function in the core network to request that the association between the first identifier and the second identifier for the user equipment be monitored and the event for the association to be reported.
[0016] In another example, an apparatus includes components for: determining, in the core network of a cellular network, that an association between a first identifier and a second identifier for a user equipment should be monitored, and determining that an event for the association should be reported, wherein a change in the association between the first identifier and the second identifier for the user equipment indicates a change in an end-user subscription; and sending a request for event reporting to network functions in the core network to request that the association between the first identifier and the second identifier for the user equipment be monitored and the event for the association to be reported.
[0017] In one example, a method is disclosed, comprising: in the core network of a cellular network, receiving a request for an event report from a first network function to request that an association between a first identifier and a second identifier for a user equipment be monitored and events for the association to be reported, wherein a change in the association between the first identifier and the second identifier for the user equipment indicates a change in an end-user subscription; sending a message to a second network function that manages the association between the first identifier and the second identifier for the user equipment, the message requesting the second network function to monitor the association between the first identifier and the second identifier for the user equipment and events for the association to be reported; receiving a report from the second network function having information indicating a change detected in the association; and sending the information indicating the change detected in the association to the first network function.
[0018] Additional examples include a computer program that includes instructions for performing the methods described in the preceding paragraph when the computer program is run on the device. The computer program according to this paragraph is a computer program product comprising a computer-readable medium carrying instructions embodied therein for use with the device. Another example is a computer program according to this paragraph that can be directly loaded into the internal memory of the device.
[0019] An example of an apparatus includes one or more processors and one or more memories storing instructions that, when executed by the one or more processors, cause the apparatus to perform at least the following: in the core network of a cellular network, receiving a request for event reporting from a first network function to request that an association between a first identifier and a second identifier for a user equipment be monitored and events for the association to be reported, wherein a change in the association between the first identifier and the second identifier for the user equipment indicates a change in an end-user subscription; sending a message to a second network function that manages the association between the first identifier and the second identifier for the user equipment, the message requesting the second network function to monitor the association between the first identifier and the second identifier for the user equipment and events for the association to be reported; receiving from the second network function a report having information indicating a change detected in the association; and sending the information indicating the change detected in the association to the first network function.
[0020] An example of a computer program product includes a computer-readable storage medium carrying instructions that, when executed by a device, cause the device to perform at least the following: in the core network of a cellular network, receiving a request for event reporting from a first network function to request that an association between a first identifier and a second identifier for a user equipment be monitored and events for the association to be reported, wherein a change in the association between the first identifier and the second identifier for the user equipment indicates a change in an end-user subscription; sending a message to a second network function that manages the association between the first identifier and the second identifier for the user equipment, the message requesting the second network function to monitor the association between the first identifier and the second identifier for the user equipment and events for the association to be reported; receiving from the second network function a report having information indicating a change detected in the association; and sending the information indicating the change detected in the association to the first network function.
[0021] In another example, an apparatus includes components for: receiving, in the core network of a cellular network, a request from a first network function for an event reporting request that an association between a first identifier and a second identifier for a user equipment be monitored and events for the association to be reported, wherein a change in the association between the first identifier and the second identifier for the user equipment indicates a change in an end-user subscription; sending a message to a second network function that manages the association between the first identifier and the second identifier for the user equipment, the message requesting the second network function to monitor the association between the first identifier and the second identifier for the user equipment and events for the association to be reported; receiving from the second network function a report having information indicating a change detected in the association; and sending the information indicating the change detected in the association to the first network function. Attached Figure Description
[0022] The accompanying drawings use reference numerals, where the same reference numerals throughout the text may refer to the same parts, but parts with the same reference numerals may differ in operation and assembly. In the drawings:
[0023] Figure 1 This demonstrates the GSMA operator platform that exposes the CAMARA API to applications;
[0024] Figure 2 This illustrates possible changes in the association / mapping of user-related identifiers;
[0025] Figure 3 It is a signaling diagram that captures SIM replacement event subscriptions, detections, and notifications;
[0026] Figure 3A It is similar to Figure 3 The signaling diagram in the image is used for SIM replacement events to unsubscribe;
[0027] Figure 4 , 5 And 6 is a flowchart corresponding to the methods for providing new publicly available events for AF, NEF, and UDM;
[0028] Figure 7 This is a block diagram of the communication network 700 that the UE can use to access the data network;
[0029] Figure 8 This is a block diagram of three possible deployments for the core network, where the core network can use one or more of the deployments. Detailed Implementation
[0030] Abbreviations that may be found in the specification and / or drawings are defined as follows, at the end of the detailed description section.
[0031] The word "exemplary" is used herein to mean "serving as an example, instance, or illustration." Any embodiment described herein as "exemplary" should not necessarily be construed as preferred or superior to other embodiments. All embodiments described in this detailed description are exemplary embodiments provided to enable those skilled in the art to make or use these examples.
[0032] When more than one reference numeral, word, or abbreviation is used with “ / ” in this specification, and as is generally used in this specification, “ / ” can be interpreted as “or,” “and,” or “both.” As used herein, “at least one of the following: ” and “at least one of ” and similar expressions, wherein the list of two or more elements is connected by “and” or “or”, refers to at least one element, or at least two or more elements, or at least all elements.
[0033] As used herein, the singular forms “a,” “an,” and “the” are also intended to include the plural forms, unless the context clearly specifies otherwise. It should be further understood that the terms “comprises,” “comprising,” “has,” “having,” “includes,” and / or “including,” when used herein, specify the presence of the stated feature, element, and / or component, but do not preclude the presence or addition of one or more other features, elements, components, and / or combinations thereof.
[0034] It should be noted that words or phrases with uppercase and lowercase letters are considered the same in this article. For example, the words “Slice,” “slice,” and “SLICE” are the same, as are the phrases “Network Repository Function,” “networkrepository function,” and “NETWORK REPOSITORY FUNCTION.”
[0035] Any flowchart or signaling diagram in this document is considered a logical flowchart and illustrates the operation of exemplary methods, the results of execution of computer program instructions in a computer-readable storage medium, and / or the functionality of logical execution implemented in a circuit system. For methods, flowcharts, and signaling diagrams, the order of method steps, process blocks, or signaling is not critical and is merely illustrative.
[0036] Technical context for understanding the example is now provided. This is provided as a brief overview of potentially relevant technical fields.
[0037] The so-called GSMA (GSM Association, where GSM = Global System for Mobile Communications) operator platform directly or through an aggregation platform exposes the CAMARA API (Application Programming Interface) to applications on the NBI (Northbound Interface), such as... Figure 1 As shown in the diagram, this figure illustrates how the GSMA Operator Platform 130 exposes the CAMARA API to applications. CAMARA is an open-source project under the Linux Foundation that defines, develops, and tests APIs that provide telecommunications functionality for retrieving information from and configuring networks. CAMARA works closely with the GSMA Operator Platform group to harmonize API requirements and publish API definitions and APIs. API uniformity is achieved through the rapid and agile creation of working code using documentation that is easy for developers to access.
[0038] NBI 115 provides direct connectivity between the operator platform 130 (also known as Nokia's NEP, Network Open Platform) and application 1110-1, as well as connectivity via aggregation platform 120 to application 1110-2, which uses the CAMARA API. The CAMARA API is designed for ease of use by developers, abstracting away any complexities of the underlying / supporting 3GPP networks. NBI 115 is an API or protocol that allows lower-level network components to communicate with higher-level or more central components.
[0039] On SBI 180, the GSMA Operator Platform (OP) 130 integrates with the 3GPP (3rd Generation Partnership Project) network via NEF (Network Open Functions) 99-2 and / or CAPIF (Public API Framework), although NEF 99-2 in Figure 1 The conversion and mapping of NBICAMARA API calls to SBI NEF API calls is shown in the example. This is performed in the GSMA Operator Platform (OP) 130. The SBI 180 in this example, also referred to as SBI-NR, is the (GSMA OP) SBI for network resources.
[0040] Industry players (e.g., cellular operators operating GSMA Operator Platform 130) have recognized that authentication and fraud prevention are important concerns. Authentication and fraud prevention can involve Application 110 and NEF 99-2. One such concern involves SIM replacement.
[0041] SIM replacement refers to the process of replacing the SIM card associated with a mobile number, i.e., a change in the association / mapping between GPSI (General Public Subscriber Identifier) (e.g., MSISDN: Mobile Station ISDN (International Subscriber Directory Number)) and SUPI (Subscription Permanent Identifier) (e.g., IMSI: International Mobile Subscriber Identifier). Figure 2As shown on the left. Figure 2 Three identifiers are shown: MSISDN (e.g., GPSI) 210; IMEI (PEI: Permanent Device Identifier) 220; and IMSI (SUPI) 230.
[0042] One of these identifiers is SUPI, which is described in Clause 5.9.2 of 3GPP TS 23.501 as follows (between the quotation marks):
[0043] A “Globally Unique 5G Subscription Permanent Identifier (SUPI)” should be assigned to each subscriber in the 5G system and configured in the UDM / UDR. The SUPI is used only within the 3GPP system, and its privacy is specified in TS 33.501.
[0044] SUPI can include:
[0045] - As defined in TS 23.003, or
[0046] - Network-specific identifiers used for private networks, as defined in TS22.261.
[0047] - As further described in TS23.316, the GLI and operator identifier used by the 5GC operator to support FN-BRG.
[0048] - GCI and operator identifier for 5GC operators supporting FN-CRG and 5G-CRG, as further described in TS23.316.
[0049] Internal references have been removed. 5GC = Fifth Generation Core; GLI = Global Line Identifier; FN-BRG = Fixed Network Broadband Residential Gateway; FN-CRG = Fixed Network Wired Residential Gateway; 5G-CRG = 5G Residential Gateway as defined in DOCSIS MULPI (Wired Data Service Interface Specification, MAC and Upper-Layer Protocol Interface).
[0050] GPSI is described in clause 5.9.8 as follows:
[0051] "The General Public Subscription Identifier (GPSI) is required to address 3GPP subscriptions in different data networks outside the 3GPP system. The 3GPP system stores the association between the GPSI and the corresponding SUPI in the subscription data."
[0052] GPSI is a public identifier used both inside and outside the 3GPP system.
[0053] GPSI is the MSISDN or external identifier, see TS 23.003. If the MSISDN is included in the subscription data, it should be possible for the same MSISDN value to be supported in both 5GS and EPS.
[0054] Note: There is no implicit one-to-one relationship between GPSI and SUPI.
[0055] Internal references are omitted. EPS = Evolved Packet System. It should be noted that SUPI is used only within the 3GPP system, while GPSI is a public identifier used both internally and externally within the 3GPP system.
[0056] For device replacement 215 (where the phone number remains the same but the device changes), changes may occur between MSISDN 210 and IMEI 220. For the 3GPP event CHANGE_OF_IMSA_IMEI_ASSOCIATION (where the SIM / mobile subscription remains the same but the device changes), changes may also occur between IMEI 220 and IMSI 230 (see attached reference numeral 225). The final set of possible changes is based on changes between IMSI 230 and MSISDN 210 for SIM replacement 240, where the phone number remains the same but the SIM card / mobile subscription changes. A change in mobile subscription can also be referred to as a change in end-user subscription, therefore SIM replacement 240 can be considered a change in end-user subscription.
[0057] SIM replacement 240 can occur for legitimate reasons:
[0058] 1) Customers may have lost their phones and are requesting a SIM replacement to continue using their phone numbers; or
[0059] 2) The customer may be getting a new phone that requires a different SIM card size (e.g., switching from a micro SIM card to a nano SIM card).
[0060] However, it can also be exploited by fraudsters: attackers can trick MNOs (mobile network operators) into issuing new SIM cards and using these cards to receive SMS-based authentication codes or bypass multi-factor authentication systems. Attackers can then reset passwords and social media accounts.
[0061] Standard methods for detecting SIM swapping events are available for business use cases, such as the following: A bank has developed a mobile application that allows customers to manage their daily finances anytime, anywhere. Since the login process relies on an SMS-based authentication code, the bank wants to check if a user's SIM card has been changed. The bank can use this information to determine whether the user's identity is trustworthy or should be re-authenticated.
[0062] However, there is currently no standard method available in 3GPP TS 23.502 for capturing changes in the association / mapping between SUPI and GPSI, and therefore no vendor-independent implementation guide for the SIM replacement API is available in GSMA OPG.09. There is also currently no vendor-independent solution to detect and notify of changes in the association / mapping between GPSI and SUPI, thus hindering the implementation of fraud detection scenarios required by the industry.
[0063] The examples in this article address these issues, as well as others. The examples include one or more of the following:
[0064] 1) Enhancements to the NEF Nnef_EventExposure service, introducing a new monitoring event type "SUPI-GPSI association change". This event type uses GPSI as input and outputs the timestamp of the last occurrence of the event in the core network and the current identification information of the UE.
[0065] 2) Enhancements to the UDM Nudm_EventExposure service: Add a new monitoring event type, "Change of SUPI-GPSI Association." This event type uses UE identification information as input and outputs the timestamp of the event's last occurrence in the CN (core network) and the UE's current identification information. This event should be triggered when any change occurs in the list of SUPIs associated with GPSIs in the UE's identification information. Additionally, this event should support immediate reporting.
[0066] The monitoring event type “SUPI-GPSI Associated Change” is used herein as the name for a monitoring event type used to issue alerts to: monitor SIM replacement for a UE used by a user (e.g., a change to the end-user subscription) or information regarding SIM replacement. Names other than “SUPI-GPSI Associated Change” may be used as long as the event notified to AF 99-1 (e.g., and the corresponding application) involves SIM replacement, i.e., a change to the end-user subscription. It should be noted that “replacement” includes changes.
[0067] SUPI can be a first identifier for the user equipment, and GPSI can be a second identifier for the user equipment. There is a correlation between the first and second identifiers for the user equipment, where a change in this correlation indicates a change in the subscriber identification module within the user equipment, thus resulting in a change in the end-user subscription. Figure 2As shown, SIM replacement 240 can be determined based on changes in identifiers 210 and 230, which are typically GPSI and SUPI respectively. Identifiers 210 and 230 may also be MSISDN and IMSI respectively. Other combinations are also possible (e.g., GPSI and IMSI), and there may also be associations between other identifiers used for the UE that would illustrate replacement in the subscriber identification module of the user equipment.
[0068] Taking the example of a bank developing a mobile application to allow its customers to manage their daily finances anytime, anywhere, the application might want to check whether a user's SIM card has been changed during initial registration and at any other time. The bank's application can use this information to determine whether the user's identity can be trusted or whether that identity should be re-authenticated. The application can contact the AF (Agent Funding Authority) to request this information from the entity managing the associated entity (e.g., UDM), which can provide instructions for SIM card replacement. 240 This will be discussed below. Figure 3 It begins to be described in detail.
[0069] Figure 3 A signaling graph is depicted, capturing a proposed method for detecting and notifying SIM replacement events. Specifically, the graph captures SIM replacement event subscription, detection, and notification. Figure 3 The diagram illustrates AF 99-1 communicating partially with a core network (CN) 90, which includes NEF 99-2 and UDM 99-3. Network functions (NFs) inside and outside CN 90 are designated by reference numeral 99, and each individual NF is assigned a number. These NFs 99 communicate using service-based interfaces, as will be described in more detail below. In these examples, AF 99-1 is assumed to be located outside CN 90, but this is not required. When AF 99-1 is outside CN 90, NEF 99-2 acts as a "gatekeeper," ensuring security within CN 90, providing authentication for the AF, and granting authorization for the AF to contact NFs 99 within CN 90, etc.
[0070] Step 1. UDM Management (e.g., Keeping Track) of the association between SUPI-GPSIs. It should be noted that the UDR (Unified Data Repository) can also participate in the management of the association between SUPI-GPSIs. The management of SUPI-GPSI associations includes the following: OAM (Operations, Administration, and Maintenance) interactions with the UDM / UDR can exist, allowing the operator to manage SUPI-GPSI relationships. This is related to subscriber management, for example, when a new SIM (and therefore a new SUPI) will be associated with a GPSI, for instance, because an end user has had their phone stolen and is being used by someone else.
[0071] The signaling consists of two parts. Block 310 indicates the subscription part of the presence signaling, which is shown via steps 2-5. Block 320 indicates the event notification part of the presence signaling, which is shown via steps 6-8.
[0072] Step 2. AF 99-1 (e.g., GSMA OP) subscribes to monitor the "SUPI-GPSI association change" event type in NEF. This occurs via an Nnef_EventExposure_Subscribe request message with an event ID (identifier) of "SUPI-GPSI association change". It should be noted that since this is an association between two elements, SUPI-GPSI and GPSI-SUPI are assumed to be equivalent. Additionally, some or all of the messages sent herein can be API calls carried in HTTP (Hypertext Transfer Protocol) messages. As part of the subscription request, the subscriber's GPSI is provided, which is the target of the event reporting. The subscription request may include a request for immediate reporting (e.g., via an immediate reporting flag) to receive the current state of the association in the subscription response.
[0073] Regarding the option of immediate reporting, consider event subscriptions / notifications as subscriptions to a magazine. They (e.g., the magazine publisher, UDM 99-3) would send them when a new issue is published. However, with immediate reporting, the magazine publisher (e.g., UDM) also sends the latest issue immediately, so the AF has the latest information from the outset. Therefore, with immediate reporting, step 4 (described below) already contains information about previous changes to the SUPI-GPSI association.
[0074] While receiving notifications when a SIM is replaced is very useful, a primary use case for SIM replacement is detecting whether a SIM replacement has occurred in the past. Immediate reporting helps with this. When a subscription with attached immediate reporting is requested, UDM 99-3 not only creates a subscription to monitor future SUPI-GPSI association changes, but the UDM also sends back the latest information it has regarding SUPI-GPSI association changes to the NEF, so that the NEF can immediately see whether a SIM replacement has occurred in the past and inform the AF. If the association changes in the future, the AF will still be able to receive notifications, see block 320.
[0075] This means that immediate reporting is only applicable to... Figure 3 Steps 4 and 5 are valid. If an immediate report is requested, the subscription response will contain up-to-date information about the SIM replacement (in addition to all other information required to confirm the subscription request). If an immediate report is not requested, it will only be used to confirm the subscription.
[0076] Also note that the AF (or the corresponding application requesting a SIM replacement) may want to limit the time period to a certain length of time from the request for immediate reporting, such as a week, a month, or a year, rather than all time or many years. The AF has the option to send the time period for use by UDM 99-3 when executing notifications for immediate reporting.
[0077] Step 2 and NEF's response provide the enhancements to the NEF Nnef_EventExposure service described earlier, introducing a new monitoring event type, "Change in SUPI-GPSI Association," which takes GPSI as input and outputs the timestamp of the last occurrence of the event in the core network and the UE's current identification information.
[0078] Step 3. NEF 99-2 requests to subscribe to the same event as UDM 99-3 via Nudm_EventExposure_Subscribe. In the subscription, NEF 99-2 provides the UE (User Equipment) identifier (e.g., from GPSI) and (if received from AF) a request for immediate reporting (via the immediate reporting flag).
[0079] Step 3 and the UDM's response provide enhancements to the previously described UDMmudm_EventExposure service, adding a new event type, "SUPI-GPSI Associated Change," which takes the UE identification information as input and outputs the timestamp of the event's last occurrence in the CN (core network) and the UE's current identification information. This event should be triggered when any change occurs in the list of SUPIs associated with the GPSI in the UE's identification information. In the example, immediate reporting is also supported.
[0080] Step 4. UDM 99-3 accepts the subscription request and sends information indicating acceptance. In the subscription response sent, if the request includes an immediate reporting flag, UDM 99-3 additionally provides information indicating the current status of the association by indicating the time when the GPSI-SUPI association was created. This is performed via the Nudm_EventExposure_Subscribe response message, which has an indication of the operation's outcome (e.g., indicating that the subscription or request has been approved) and a subscription association ID. This subscription association ID will be used by AF 99-1 to unsubscribe (see...). Figure 3A ).
[0081] Step 5. NEF 99-2 confirms the subscription request (or unsubscribe request) to AF 99-1 (providing the subscription association ID to be used by the AF, for example, for unsubscribing). If Immediate Reporting is selected, the response may include the time when the GPSI-SUPI association was created. Note that if used, this time period may also be modified, as if the GPSI-SUPI association was created before the time period indicated by the AF (and its corresponding application), and the time when the GPSI-SUPI association was created may not be included (although other changes to the GPSI-SUPI association can be included if available within the time limit).
[0082] The next step is the event notification part of the signaling (see block 320), which is shown in steps 6-8.
[0083] Step 6. UDM 99-3 detects when the subscriber's GPSI-SUPI association changes.
[0084] Step 7. UDM 99-3 sends a notification with the event type and timestamp to NEF 99-2. This is performed via the Nudm_EventExposure_Notify message. The event ID is "SUPI-GPSI associated change" and includes the timestamp.
[0085] Step 8. NEF 99-2 forwards a notification with the event type and timestamp to AF 99-1. AF may decide to restart the full user authentication process to cross-verify that the GPSI-SUPI association change does not indicate that GPSI has been associated with another user.
[0086] It should be noted that when a user subscription ends (e.g., GPSI no longer corresponds to a valid user subscription), the 3GPP core network (e.g., via NEF's UDM) notifies the AF, and subscriptions for the event "Change of GPSI-SIM association" can be automatically stopped.
[0087] refer to Figure 3A The image is similar to Figure 3The signaling diagram in the figure is used for SIM replacement event unsubscription. Block 330 indicates that there is an unsubscription portion in the signaling, which is shown through steps 2-5. In step 2, there is an unsubscription request containing the subscription association ID. In step 3, NEF 99-2 sends a corresponding unsubscription request with the subscription association ID to UDM 99-3. In step 4, UDM 99-3 responds with an unsubscription response, also with the subscription association ID. NEF 99-2 sends a corresponding unsubscription response to AF 99-1. AF 99-1 (e.g., and its corresponding application) has now unsubscribed from notifications of changes in the SUPI-GPSI association for these specific identifiers.
[0088] Figure 4 , Figure 5 as well as Figure 6 Correspondingly, flowcharts are provided for methods to provide new publicly available events for AF, NEF, and UDM. These flowcharts provide methods for signaling and responses to events. Figure 3 Additional details of the actions taken based on the signaling. Even if a block has signals from... Figure 3 Steps, Figure 4 , Figure 5 as well as Figure 6 Other details may also be provided.
[0089] Go to Figure 4 This is a flowchart illustrating the method for providing new publicly available events for AF 99-1. Figure 3 Before step 2, AF 99-1 determines the request to report a “SUPI-GPSI association change” for the UE and the corresponding GPSI, which can indicate a change to the end-user subscription. See block 410. This can occur in several ways, one of which is in block 415, for example, when an application needs to know when a SIM replacement has occurred, and the AF receives a subscription request from that application, which triggers an action by AF 99-1 in subscription block 310. This also causes the AF to report the subscription result and the changes(s) associated with the SIM replacement to the application (e.g., via a notification message, such as NOTIFY). The event ID of the “SUPI-GPSI association change” is the primary method for determining that a SIM replacement has occurred. Block 420 shows an example where a user creates an application account and associates that account with a GPSI (e.g., MSISDN). Similarly, an update to an application account that may modify the GPSI (e.g., MSISDN) can trigger the application to want to know when a SIM replacement has occurred.
[0090] As part of step 2 (see also) Figure 3AF 99-1 creates and sends a message for the UE with the corresponding GPSI in the message, with the event ID: "Change of SUPI-GPSI association". In block 425, if AF 99-1 wants to report a previous change to the SUPI-GPSI association, the AF instructs that it be reported immediately, for example, there may be corresponding time periods during which changes should be reported.
[0091] Blocks 430 and 435 are applicable based on the request for an immediate report received by the AF and step 5. In block 430, the AF receives (within a time period) Figure 3 Step 5) has a response with a “SUPI-GPSI associated change” with a corresponding timestamp for any of the changes. In response, and in block 435, the AF (in response to step 5) reports the changes to the application of one or both of the subscription results and the changes to the associated changes, for example, using NOTIFY messages.
[0092] In step 8 (see also) Figure 3 In block 440, the AF receives a message for the UE with the corresponding GPSI in the message, bearing the event ID: "Change of SUPI-GPSI association". In response, the AF reports the change(s) to the application in block 440, for example, using a NOTIFY message. Alternatively or concurrently, in block 445, the AF can restart the full user authentication process to cross-check that the GPSI-SUPI association change does not indicate that the GPSI has been associated with another user.
[0093] Go to Figure 5 This diagram is a flowchart of a method for providing new publicly available events to NEF. Step 2 of NEF 99-2 (see...) Figure 3 The UE receives a message with the corresponding GPSI in the message, bearing the event ID: "Change of SUPI-GPSI Association," which can indicate a change to the end-user subscription. In block 510, NEF 99-2 authorizes the AF to request and determine the UDM instance to be contacted. That is, there can be, and typically multiple, UDM instances, and the NEF determines the UDM instance for this UE and the GPSI.
[0094] In block 515, NEF determines whether the AF wants to report immediately, and that the message has corresponding time periods during which changes should be reported. In block 515, in response to the AF wanting to report immediately, NEF populates the message with an immediate reporting flag. In block 520, NEF populates the message with a time period based on the fact that the message requesting that time period is used. In block 525, NEF sends a populated message with the event ID of the corresponding GPSI in the message: "SUPI-GPSI associated change". See also Figure 3 Step 3.
[0095] In step 4 (see also...) Figure 3 NEF receives a response. In block 530, if an immediate report is requested, NEF receives any applicable event ID with a corresponding timestamp for any (or more) changes within a time period (if enabled): “SUPI-GPSI associated change”. In block 535, NEF forms a message for step 5 based on any received event ID: “SUPI-GPSI associated change” and its corresponding timestamp, or, in the absence of such an event ID (if not applicable due to no immediate report being requested). Figure 3 ).
[0096] See Figure 3 Steps 5, 7, and 8 are described below. In step 5, the NEF sends a response message to the AF. In step 7, the NEF receives a notification (e.g., Notify) message with the event ID "SUPI-GPSI Association Change" and the corresponding timestamp. In step 8, the NEF sends a notification (e.g., Notify) message containing the applicable event ID "SUPI-GPSI Association Change" and the corresponding timestamp.
[0097] Figure 6 This is a flowchart of a method for providing new publicly available events for UDM. In step 1 (see also...) Figure 3 UDM 99-3 receives the SUPI-GPSI association applicable to the UE, for example via OAM. In step 3 (see also...) Figure 3 In the request, upon receiving the event ID "Change of SUPI-GPSI Association," the UDM may perform some or all of steps 605-625. "Change of SUPI-GPSI Association" may indicate a change to the end-user subscription. The UDM 99-3 enable request in block 605 enables event monitoring and notification for the AF and UE. This may involve storing other corresponding information, such as the UDM instance, GPSI, time period, etc.
[0098] In block 610, the UDM, in response to the immediate reporting flag in the request, performs one or more of steps 615-625. In block 615, the UDM determines the last one or more changes to the SUPI-GPSI association and their corresponding timestamps. In block 620, the UDM determines any time period indicated in the request for the SUPI-GPSI association. In block 625, the UDM adds the SUPI-GPSI association and corresponding timestamps for any changes within the time period used for the message, and sends the message to the NEF in step 4 (see [link to NEF]). Figure 3 ).
[0099] In step 6 (see also) Figure 3 In response to detecting a change in the monitored SUPI-GPSI used for AF and the corresponding UE, UDM executes block 635, in which UDM creates and sends a message with the event ID "SUPI-GPSI associated change" and the corresponding timestamp.
[0100] Figure 7 A block diagram of a communication network 700 is shown, through which a user equipment (UE) 702 can access the communication network 700 via a data network 707 to communicate with an application server (not shown) hosting third-party application functions (not shown). The communication network 700 includes a radio access network (RAN) 706 (e.g., NG-RAN) and a core network 90 (e.g., a 5G fifth-generation core network (5GC)), which operate based on fifth-generation radio access technology, described in standards such as the 3rd Generation Partnership Project (3GPP) for New Radio. The core network 90 is connected to the operation and maintenance entity 710 of the communication network 700, as will be described in more detail below.
[0101] Radio Access Network 706 includes one or more Radio Access Network (RAN) nodes (otherwise referred to as base stations), such as gNodeBs (gNBs). A RAN node may include a central unit (e.g., a gNB-CU not shown) and one or more distributed units (e.g., one or more gNB-DUs not shown), which are linked to the central unit (e.g., the gNB-CU) via an F1 interface. UE 702 establishes a radio connection with RAN 706 via radio link 711. The UE-RAN connection is 3GPP Access 791.
[0102] Non-3GPP access 790 is also supported. This example uses access point (AP) 795, and UE 702 can connect to AP 795 via radio access using radio link 712 or via wired access using wired link 713. AP 795 connects to AMF via the N2 interface through Non-3GPP Interoperability Function (N3IWF). This is just one example of non-3GPP access.
[0103] Core network 90 has a service-based architecture (SBA) and includes multiple network functions (NFs) 99, including (in alphabetical order of their initials): Access and Mobility Function (AMF), Authentication Server Function (AUSF), Network Exposure Function (NEF) 99-2, Network Repository Function (NRF), Network Slice Selection Function (NSSF), Network Data Analysis Function (NWDAF), Policy Control Function (PCF), Session Management Function (SMF), User Plane Function (UPF), and Unified Data Repository (UDM) 99-3. For ease of illustration, other network functions of core network 90, such as Binding Support Function (BSF) and Charging Function (CHF), are not shown. In these examples, Application Function (AF) 99-1 is outside CN 90 and communicates with NEF 99-2. The functionality of the core network functions is well-known to those skilled in the art and therefore requires no detailed description. Many descriptions and further details for these NFs can be found, for example, in 3GPP TS 23.501.
[0104] Application Function (AF) 99-1 interacts with the 3GPP core network to provide services. Network Exposure Function (NEF) 99-2 provides a platform for creating new services by integrating APIs (Application Programming Interfaces) and providing developers with unified access to the API framework. This can include: secure exposure of network services (voice, data connectivity, billing, subscriber data, etc.) to third-party applications; a developer environment for operators and the community; service portfolios for creating end-to-end provisioning by combining any network assets into applications; and an integration layer for connecting applications to the operator's network. UDM 99-3 plays a role in managing user-related data, such as subscriber profiles, authentication credentials, and authorization policies. It ensures that authorized users can access 5G networks and services while maintaining the integrity, security, and privacy of user information.
[0105] However, a brief overview of how CN 90 works is now provided. This overview concerns the software-based interface description and the description of NF consumers / NF producers.
[0106] Each NF99 in the core network 90 can provide one or more services to other network functions of the core network 90 via an application programming interface (API). Each NF99 can also register itself and the services it supports (e.g., services provided by the NF99 to other network functions) with the NRF of the core network 90. The NRF can be used by any network function to discover other network functions (or instances of NF99) and other services supported by other NFs (e.g., services provided by other NF99s). Any NF99 can consume (e.g., use) services provided and exposed by another NF99. An NF99 that consumes the services of another NF99 is generally referred to as a network function service consumer. One or more NF99s that provide and expose their services are referred to as network function service producers.
[0107] Another part of the overview relates to the description of the NWDAF. The Network Analysis Data Function (NWAF) is configured to collect or retrieve data about one or more NFs 99 in the core network 90, generate analysis results, and provide the generated analysis (including energy consumption analysis) to itself or other NFs that have requested analysis generated by the NWDAF. The NWDAF may include an Analysis Logic Function (AnLF) configured to generate analysis (e.g., generate statistics and / or generate predictions) based on data about one or more NFs 99 collected and / or retrieved by the NWDAF. The NWDAF also includes an analysis service exposed by the NWDAF for providing the analysis generated by the AnLF. The NWDAF also includes a Model Training Logic Function (NWDAF (MTLF)) configured to train an artificial intelligence / machine learning (AI / ML) model that can be used by the AnLF to generate analysis, including energy consumption analysis based on data about one or more network functions collected or retrieved from one or more network functions and / or OAM entity 710.
[0108] In data network 707, instruction 794 is stored in computer-readable storage medium 704-1, which can be a circuit system, such as long-term memory (e.g., a hard disk or solid-state drive), short-term memory (e.g., dynamic random access memory), or a combination of both (e.g., reading from long-term memory for temporary storage in short-term memory and subsequently downloading). Computer-readable medium 704-1 contains instruction 794, which, when downloaded and installed into CN 706, creates a corresponding NF 720, causing NF 720 (e.g., once instantiated) to perform the corresponding actions described herein. Computer-readable storage medium 704 can be implemented in other forms, such as via optical disc (as computer-readable storage medium 704-2) or on a memory disk containing instruction 794.
[0109] Generally, various embodiments of user equipment 702 can include, but are not limited to: devices implementing cellular technology (such as smartphones, mobile phones, cellular phones, Voice over Internet Protocol (IP) phones and / or wireless local loop phones), tablet computers, portable computers, vehicles or in-vehicle devices (e.g. for wireless V2X (vehicle-to-everything) communication), image acquisition devices (such as digital cameras), gaming devices, music storage and playback devices, internet devices (including Internet of Things (IoT) devices), IoT devices with sensors and / or actuators (e.g. for automation applications), and portable units or terminals that include a combination of the above functions, laptop embedded devices (LEE), laptop mounted devices (LME), Universal Serial Bus (USB) dongles, smart devices, wireless client devices (CPE), Internet of Things (IoT) devices, watches or other wearable devices, head-mounted displays (HMDs), vehicles, drones, medical devices and applications (e.g., remote surgery), industrial equipment 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. In other words, UE 10 can be any terminal device capable of wireless communication. By way of example and not limitation, UE may also be referred to as a communication device, terminal device (MT), subscriber station (SS), portable subscriber station, mobile station (MS), or access terminal (AT).
[0110] Go to Figure 8 This diagram shows a block diagram of a possible, non-limiting example of a core network (CN) 890 and illustrates some or all possible deployments for the CN 890. Three possible deployments are shown: a traditional (e.g., standalone) deployment 801; a virtualized deployment 802; and a container deployment 803. It should be noted that only a single network function (NF) is shown for each deployment, but each deployment can have more NFs implemented. For simplicity, the same reference numerals are used for the elements in the diagram, but the elements may differ for each deployment. That is, the hardware (with “w / ” circuitry) 810 in a traditional deployment 801 may differ from the hardware 810 in a container deployment 803.
[0111] Traditional deployment 801 implements hardware 810 and executes operating system (OS) 815. NF 820 is NF 99. NF 820 runs on OS 815. NF 820 is implemented by executing on hardware 810 (via OS 815). For virtualization deployment 802, this includes hardware 810 executing OS 815. Hypervisor 825 runs on OS 815, and two virtual machines (VMs) 830-1 and 830-2 are implemented using hypervisor 825. VM 830-1 has OS 835-1, bin (binary) / library 840-1, and NF 820-1. Similarly, VM 830-2 has OS 835-2, bin (binary) / library 840-2, and NF 820-2. NF 820 is executed by hardware 810. For container deployment 803, container 845, container runtime 843, and OS 815 are executed by hardware 810. Container 845 is run on container runtime 843, while NF 820 uses bin / library 850.
[0112] Regardless of which deployment 801, 802, or 803 is selected, there is a relationship between NF 820 and hardware 810. That is, all NF 820 implementations use hardware 810.
[0113] Specifically, hardware 810 may include one or more processors 813 and one or more memories 817, both of which may contain or be accessible with instructions 811. Instructions 811 (e.g., from OS 815, OS 835, Bin / Library 840, Bin / Library 850, and / or NF 820) are used to cause the OS, Bin / Library, and / or NF of the device, and the corresponding device deployed 801, 802, or 803, to perform the operations described herein. It is assumed that processor 813 and memory 817 may or may not differ for deployment 801, 802, or 803.
[0114] Without limiting the scope, interpretation, or application of the claims appearing below in any way, one or more technical effects and / or advantages of the exemplary embodiments disclosed herein include providing a supplier-independent method for detecting and notifying SIM replacement events.
[0115] The following are additional examples.
[0116] Example 1. A method comprising: in a core network of a cellular network, managing an association between a first identifier and a second identifier for a user equipment, wherein a change in the association between the first identifier and the second identifier for the user equipment indicates a change in an end-user subscription; receiving a request for an event report relating to the change in the association between the first identifier and the second identifier for the user equipment; detecting the change in the association; and reporting the detected change to a network function in the core network.
[0117] Example 2. The method according to Example 1, wherein: the request for event reporting includes information instructing immediate reporting; and the method further includes, before receiving the request, sending information to the network function in the core network indicating one or more changes detected in the association between the first identifier and the second identifier.
[0118] Example 3. According to the method of Example 2, wherein the information indicating one or more changes includes information indicating the current state of the association, the current state of the association being indicated by indicating the time when the association was created.
[0119] Example 4. The method according to Example 1, wherein: the request for an event report includes information instructing immediate reporting and a corresponding time period; and the method further includes, before receiving the request and during the time period, determining whether one or more changes are detected in the association between the first identifier and the second identifier, and sending information to the network function in the core network indicating any identified one or more changes along with a corresponding timestamp.
[0120] Example 5. The method according to any one of Examples 1 to 4, wherein the request for an event report related to the change in the association between the first identifier and the second identifier for the user equipment includes an event type corresponding to a service for monitoring the event type, the service using the user equipment's identification information as input and outputting a timestamp corresponding to the last time the event of the change subscribed by the end user occurred in the core network and the user equipment's current identification information.
[0121] Example 6. The method according to Example 5, wherein the event is triggered in response to any change in the first identifier list associated with the second identifier in the identification information for the user equipment.
[0122] Example 7. A method comprising: in a core network of a cellular network, determining that an association between a first identifier and a second identifier for a user equipment should be monitored, and determining that an event for the association should be reported, wherein a change in the association between the first identifier and the second identifier for the user equipment indicates a change in an end-user subscription; and sending a request for event reporting to a network function in the core network to request that the association between the first identifier and the second identifier for the user equipment be monitored and the event for the association be reported.
[0123] Example 8. The method according to Example 7 further includes, in response to the sending, receiving an indication that a subscription has been initiated to monitor and report events related to the association between a first identifier and a second identifier for a user device.
[0124] Example 9. The method according to Example 8, wherein: the request for an event report includes information instructing immediate reporting; and receiving the instruction further includes, in response to the request, receiving information instructing one or more changes in the association between the first identifier and the second identifier that were detected prior to the request for an event report.
[0125] Example 10. The method according to Example 9, wherein the information indicating one or more changes includes information indicating the current state of the association, the current state of the association being indicated by indicating the time when the association was created.
[0126] Example 11. The method according to Example 8, wherein: the request for an event report includes information instructing immediate reporting and a corresponding time period; and receiving the instruction further includes receiving information indicating that any one or more changes to the network function in the core network have been determined to have occurred during the time period. Note that Examples 11 and 9 may be directly dependent on Example 7.
[0127] Example 12. The method according to any one of Examples 7 to 11, wherein the following are determined in response to a request from the application for the monitoring and reporting: the association between the first identifier and the second identifier for the user device should be monitored, and events related to the association should be reported; and for any information indicating one or more changes in the association that has been determined to have been performed, information indicating the one or more changes is reported to the application.
[0128] Example 13. The method according to any one of Examples 7 to 12 further includes restarting the complete user authentication process to cross-check that the association changes that have occurred for the first identifier and the second identifier are not a sign that the second identifier has been associated with another user.
[0129] Example 14. The method according to any one of Examples 7 to 13 further includes: receiving a notification from the network function that the association between the first identifier and the second identifier for the user equipment has changed, the notification having a corresponding timestamp, and including a monitoring event type indicating that the association between the first identifier and the second identifier for the user equipment has changed.
[0130] Example 15. A method comprising: in the core network of a cellular network, receiving from a first network function a request for event reporting to request that an association between a first identifier and a second identifier for a user equipment be monitored and that an event for the association be reported, wherein a change in the association between the first identifier and the second identifier for the user equipment indicates a change in an end-user subscription; sending a message to a second network function, the second network function managing the association between the first identifier and the second identifier for the user equipment, the message requesting the second network function to monitor the association between the first identifier and the second identifier for the user equipment and the event for the association between the first identifier and the second identifier for the user equipment to be reported; receiving from the second network function a report having information indicating a change detected in the association; and sending the information indicating the change detected in the association to the first network function.
[0131] Example 16. The method according to Example 15, wherein: the request received from the first network function includes information indicating immediate reporting; the method further includes: receiving information indicating one or more changes in the association between the first identifier and the second identifier that were detected before the request was received from the first network function; and sending information indicating the one or more changes in the association to the first network function.
[0132] Example 17. The method according to Example 15, wherein: the request received from the first network function includes information indicating immediate reporting and having a corresponding time period; the method further includes: receiving information indicating one or more changes in the association between the first identifier and the second identifier detected before the request is received from the first network function and during the time period; and sending information indicating the one or more changes in the association to the first network function.
[0133] Example 18. The method according to any one of Examples 15 to 17, wherein the request from the first network function includes an event type corresponding to a service for monitoring the event type, the service using the second identifier as an input identifier, and outputting a timestamp of the last time the event corresponding to the change in the end-user subscription occurred in the core network and the current identification information of the user equipment.
[0134] Example 19. The method according to any one of Examples 1 to 18, wherein the first identifier includes a subscription permanent identifier for the user device, and the second identifier includes a general public subscription identifier for the user device.
[0135] Example 20. The method according to any one of Examples 1 to 18, wherein the request for an event report includes information indicating a monitoring event type, the monitoring event type indicating a change in the association between the first identifier and the second identifier for the user equipment to be monitored, and indicating an event of the change to be reported.
[0136] Example 21. An apparatus comprising: in a core network of a cellular network, managing an association between a first identifier and a second identifier for a user equipment, wherein a change in the association between the first identifier and the second identifier for the user equipment indicates a change in an end-user subscription; receiving a request for an event report relating to the change in the association between the first identifier and the second identifier for the user equipment; detecting the change in the association; and reporting the detected change to a network function in the core network.
[0137] Example 22. The apparatus according to Example 21, wherein: the request for an event report includes information instructing immediate reporting; and the component is further configured to send information to the network function in the core network, prior to receiving the request, instructing one or more changes detected in the association between the first identifier and the second identifier.
[0138] Example 23. The apparatus according to Example 22, wherein the information indicating one or more changes includes information indicating the current state of the association, the current state of the association being indicated by indicating the time when the association was created.
[0139] Example 24. The apparatus according to Example 21, wherein: the request for an event report includes information instructing immediate reporting and a corresponding time period; and the component is further configured to, before receiving the request and during the time period, determine whether one or more changes are detected in the association between the first identifier and the second identifier, and send information to the network function in the core network indicating any identified one or more changes along with a corresponding timestamp.
[0140] Example 25. An apparatus according to any one of Examples 21 to 24, wherein the request for an event report related to a change in the association between the first identifier and the second identifier for the user equipment includes an event type corresponding to a service for monitoring the event type, the service using the user equipment's identification information as input and outputting a timestamp corresponding to the last time the event of the change subscribed by the end user occurred in the core network and the user equipment's current identification information.
[0141] Example 26. The apparatus according to Example 25, wherein the event is triggered in response to any change in the first identifier list associated with the second identifier in the identification information for the user equipment.
[0142] Example 27. An apparatus comprising: in a core network of a cellular network, determining that an association between a first identifier and a second identifier for a user equipment should be monitored, and determining that an event for the association should be reported, wherein a change in the association between the first identifier and the second identifier for the user equipment indicates a change in an end-user subscription; and sending a request for event reporting to a network function in the core network to request that the association between the first identifier and the second identifier for the user equipment be monitored and the event for the association to be reported.
[0143] Example 28. The apparatus according to Example 27, wherein the component is further configured to receive an indication in response to the sending, indicating that a subscription has been initiated to monitor and report events relating to the association between a first identifier and a second identifier for a user device.
[0144] Example 29. The apparatus according to Example 28, wherein: the request for an event report includes information instructing immediate reporting; and receiving the instruction further includes, in response to the request, receiving information instructing one or more changes in the association between the first identifier and the second identifier that were detected prior to the request for an event report.
[0145] Example 30. The apparatus according to Example 29, wherein the information indicating one or more changes includes information indicating the current state of the association, the current state of the association being indicated by indicating the time when the association was created.
[0146] Example 31. The apparatus according to Example 28, wherein: the request for an event report includes information instructing immediate reporting and a corresponding time period; and receiving the instruction further includes receiving information indicating that any one or more changes to the network function in the core network have been determined to have occurred during the time period. It should be noted that Examples 31 and 29 are directly subordinate to Example 27.
[0147] Example 32. An apparatus according to any one of Examples 27 to 31, wherein determining the following is made in response to a request from an application for the monitoring and reporting: the association between the first identifier and the second identifier for the user equipment should be monitored, and events related to the association should be reported; and for any information indicating one or more changes in the association that has been determined to have been performed, information indicating the one or more changes is reported to the application.
[0148] Example 33. The apparatus according to any one of Examples 27 to 32, wherein the component is further configured to: restart the full user authentication process to cross-check that the association changes that have occurred for the first identifier and the second identifier are not a sign that the second identifier has been associated with another user.
[0149] Example 34. An apparatus according to any one of Examples 27 to 33, wherein the component is further configured to: receive a notification from the network function that the association between the first identifier and the second identifier for the user equipment has changed, the notification having a corresponding timestamp, and including a monitoring event type indicating that the association between the first identifier and the second identifier for the user equipment has changed.
[0150] Example 35. An apparatus comprising: in the core network of a cellular network, receiving, from a first network function, a request for event reporting to request that an association between a first identifier and a second identifier for a user equipment be monitored and that an event for the association be reported, wherein a change in the association between the first identifier and the second identifier for the user equipment indicates a change in an end-user subscription; sending a message to a second network function, the second network function managing the association between the first identifier and the second identifier for the user equipment, the message requesting the second network function to monitor the association between the first identifier and the second identifier for the user equipment and the event for the association between the first identifier and the second identifier for the user equipment to be reported; receiving from the second network function a report having information indicating a change detected in the association; and sending the information indicating the change detected in the association to the first network function.
[0151] Example 36. The apparatus according to Example 35, wherein: the request received from the first network function includes information indicating immediate reporting; the component is further configured to: receive information indicating one or more changes in the association between the first identifier and the second identifier detected before the request is received from the first network function; and send information indicating the one or more changes in the association to the first network function.
[0152] Example 37. The apparatus according to Example 35, wherein: the request received from the first network function includes information indicating immediate reporting and having a corresponding time period; the component is further configured to: receive information indicating one or more changes in the association between the first identifier and the second identifier detected before the request is received from the first network function and during the time period; and send information indicating the one or more changes in the association to the first network function.
[0153] Example 38. An apparatus according to any one of Examples 35 to 37, wherein the request from the first network function includes an event type corresponding to a service for monitoring the event type, the service using the second identifier as an input identifier, and outputting a timestamp of the last time the event corresponding to the change in the end-user subscription occurred in the core network and the current identification information of the user equipment.
[0154] Example 39. An apparatus according to any one of Examples 21 to 38, wherein the first identifier includes a subscription permanent identifier for the user device, and the second identifier includes a general public subscription identifier for the user device.
[0155] Example 40. An apparatus according to any one of Examples 21 to 38, wherein the request for an event report includes information indicating a monitoring event type, the monitoring event type indicating a change in the association between the first identifier and the second identifier for the user equipment to be monitored, and indicating an event of the change to be reported.
[0156] Example 41. An apparatus comprising: one or more processors; and one or more memories storing instructions that, when executed by the one or more processors, cause the apparatus to at least: manage, in the core network of a cellular network, an association between a first identifier and a second identifier for a user equipment, wherein a change in the association between the first identifier and the second identifier for the user equipment indicates a change in an end-user subscription; receive a request for an event report relating to the change in the association between the first identifier and the second identifier for the user equipment; detect the change in the association; and report the detected change to a network function in the core network.
[0157] Example 42. The apparatus according to Example 41, wherein: the request for an event report includes information instructing immediate reporting; and the one or more memories also store instructions that, when executed by the one or more processors, cause the apparatus to at least: before receiving the request, send information to the network function in the core network indicating one or more changes detected in the association between the first identifier and the second identifier.
[0158] Example 43. The apparatus according to Example 42, wherein the information indicating one or more changes includes information indicating the current state of the association, the current state of the association being indicated by indicating the time when the association was created.
[0159] Example 44. The apparatus according to Example 41, wherein: the request for an event report includes information instructing immediate reporting and a corresponding time period; and the one or more memories also store instructions that, when executed by the one or more processors, cause the apparatus to at least: before receiving the request and during the time period, determine whether one or more changes are detected in the association between the first identifier and the second identifier, and send information to the network function in the core network indicating any identified one or more changes along with a corresponding timestamp.
[0160] Example 45. An apparatus according to any one of Examples 41 to 44, wherein the request for an event report related to a change in the association between the first identifier and the second identifier for the user equipment includes an event type corresponding to a service for monitoring the event type, the service using the user equipment's identification information as input and outputting a timestamp corresponding to the last time the event of the change subscribed by the end user occurred in the core network and the user equipment's current identification information.
[0161] Example 46. The apparatus according to Example 45, wherein the event is triggered in response to any change in the first identifier list associated with the second identifier in the identification information for the user equipment.
[0162] Example 47. An apparatus comprising: one or more processors; and one or more memories storing instructions that, when executed by the one or more processors, cause the apparatus to perform at least: in a core network of a cellular network, determining that an association between a first identifier and a second identifier for a user equipment should be monitored, and determining that an event for the association should be reported, wherein a change in the association between the first identifier and the second identifier for the user equipment indicates a change in an end-user subscription; and sending a request for event reporting to a network function in the core network to request that the association between the first identifier and the second identifier for the user equipment be monitored and the event for the association to be reported.
[0163] Example 48. The apparatus according to Example 47, wherein the one or more memories further store instructions that, when executed by the one or more processors, cause the apparatus to at least: in response to the transmission, receive an indication that a subscription has been initiated to monitor and report events related to the association between a first identifier and a second identifier for a user device.
[0164] Example 49. The apparatus according to Example 48, wherein: the request for an event report includes information instructing immediate reporting; and receiving the instruction further includes, in response to the request, receiving information instructing one or more changes in the association between the first identifier and the second identifier that were detected prior to the request for an event report.
[0165] Example 50. The apparatus according to Example 49, wherein the information indicating one or more changes includes information indicating the current state of the association, the current state of the association being indicated by indicating the time when the association was created.
[0166] Example 51. The apparatus according to Example 48, wherein: the request for an event report includes information instructing immediate reporting and a corresponding time period; and receiving the instruction further includes receiving information indicating that any one or more changes to the network function in the core network have been determined to have occurred during the time period. Note that Examples 51 and 49 may be directly dependent on Example 47.
[0167] Example 52. An apparatus according to any one of Examples 47 to 51, wherein determining the following is made in response to a request from an application for the monitoring and reporting: the association between the first identifier and the second identifier for the user equipment should be monitored, and events related to the association should be reported; and for any information indicating one or more changes in the association that has been determined to have been performed, information indicating the one or more changes is reported to the application.
[0168] Example 53. An apparatus according to any one of Examples 47 to 52, wherein the one or more memories further store instructions that, when executed by the one or more processors, cause the apparatus to perform at least: restarting the full user authentication process to cross-check that the association changes that have occurred for the first identifier and the second identifier are not a sign that the second identifier has been associated with another user.
[0169] Example 54. An apparatus according to any one of Examples 47 to 53, wherein the one or more memories further store instructions that, when executed by the one or more processors, cause the apparatus to at least: receive a notification from the network function that the association between the first identifier and the second identifier for the user equipment has changed, the notification having a corresponding timestamp, and including a monitoring event type indicating that the association between the first identifier and the second identifier for the user equipment has changed.
[0170] Example 55. An apparatus comprising: one or more processors; and one or more memories storing instructions that, when executed by the one or more processors, cause the apparatus to perform at least: in the core network of a cellular network, receiving a request for event reporting from a first network function to request that an association between a first identifier and a second identifier for a user equipment be monitored and that an event for the association be reported, wherein a change in the association between the first identifier and the second identifier for the user equipment indicates a change in an end-user subscription; sending a message to a second network function that manages the association between the first identifier and the second identifier for the user equipment, the message requesting the second network function to monitor the association between the first identifier and the second identifier for the user equipment and the event for the association between the first identifier and the second identifier for the user equipment to be reported; receiving from the second network function a report having information indicating a change detected in the association; and sending the information indicating the change detected in the association to the first network function.
[0171] Example 56. An apparatus according to Example 55, wherein: the request received from the first network function includes information instructing immediate reporting; wherein the one or more memories further store instructions that, when executed by the one or more processors, cause the apparatus to at least: receive information indicating one or more changes in the association between the first identifier and the second identifier detected before the request was received from the first network function; and send information to the first network function indicating the one or more changes in the association.
[0172] Example 57. An apparatus according to Example 55, wherein: the request received from the first network function includes information indicating immediate reporting and having a corresponding time period; wherein the one or more memories further store instructions that, when executed by the one or more processors, cause the apparatus to at least: receive information indicating one or more changes in the association between the first identifier and the second identifier detected before the request was received from the first network function and during the time period; and send information indicating the one or more changes in the association to the first network function.
[0173] Example 58. An apparatus according to any one of Examples 55 to 57, wherein the request from the first network function includes an event type corresponding to a service for monitoring the event type, the service using the second identifier as an input identifier, and outputting a timestamp of the last time the event corresponding to the change in the end-user subscription occurred in the core network and the current identification information of the user equipment.
[0174] Example 59. An apparatus according to any one of Examples 41 to 58, wherein the first identifier includes a subscription permanent identifier for the user device, and the second identifier includes a general public subscription identifier for the user device.
[0175] Example 60. An apparatus according to any one of Examples 41 to 58, wherein the request for an event report includes information indicating a monitoring event type, the monitoring event type indicating a change in the association between the first identifier and the second identifier for the user equipment to be monitored, and indicating an event of the change to be reported.
[0176] Example 61. A computer program including instructions that, when executed by a device, cause the device to perform any of the methods described in Examples 1 to 20.
[0177] Example 62. A computer program according to Example 61, wherein the computer program is a computer program product comprising a computer-readable medium carrying instructions embodied therein for use with the device.
[0178] Example 63. A computer program according to Example 61, wherein the computer program can be directly loaded into the internal memory of the device.
[0179] As used in this application, the term "circuit system" may refer to one or more of the following:
[0180] (a) Hardware circuit implementation only (such as implementation only in analog, digital and / or quantum circuit systems) and
[0181] (b) A combination of (multiple) hardware circuits and software, such as (if applicable): (i) a combination of (multiple) analog, digital, and / or quantum hardware circuits with software / firmware and (ii) any portion of (multiple) hardware processors having software (including (multiple) digital and / or quantum processors) and (multiple) memories, which work together to enable a device (such as a mobile device, computing device, or server) to perform various functions and
[0182] (c) Any or all parts of (multiple) hardware circuits (such as (multiple) microprocessors, (multiple) processors and / or quantum processors) that require software (e.g., firmware) to operate, but may not have software when operation does not require software.
[0183] This definition of "circuit system" applies to all uses of the term in this application, including in any claim. As another example, as used in this application, the term "circuit system" also covers only the implementation of hardware circuitry or a processor (or multiple processors) or portions thereof and their accompanying software and / or firmware. The term "circuit system" also covers, for example, if applicable to a particular claim element, a baseband integrated circuit or processor integrated circuit for a mobile device or a similar integrated circuit in a server, cellular network device, or other computing or networking device.
[0184] In one example embodiment, software as used herein (e.g., application logic, instruction set) is stored on any of a variety of conventional computer-readable media. In the context of this document, "computer-readable medium" can be any medium or component capable of containing, storing, communicating, propagating, or transmitting instructions for use by or associated with an instruction execution system, apparatus, or device, such as a computer, an example of which is described and depicted, for example in Figure 8 In this context, a computer-readable medium can include a computer-readable storage medium (such as memory 817 or other devices), which can be any medium or component capable of containing, storing, and / or transmitting instructions for use by or in connection with an instruction execution system, apparatus, or device, such as a computer. A computer-readable storage medium does not contain propagating signals and can therefore be considered non-transitory. As used herein, the term "non-transitory" refers to a limitation of the medium itself (i.e., it is tangible, not signal-based), not a limitation of the persistence of data storage (e.g., RAM random access memory, versus ROM read-only memory).
[0185] If necessary, the different functions discussed in this document may be executed in different orders and / or concurrently with each other. Furthermore, if necessary, one or more of the above functions may be optional or may be combined.
[0186] Although various aspects of the invention are set forth in the independent claims, other aspects of the invention include other combinations of features from the described embodiments and / or dependent claims with features of the independent claims, not just those expressly listed in the claims.
[0187] It should also be noted in this document that although exemplary embodiments of the invention have been described above, these descriptions should not be considered limiting. Rather, several variations and modifications are possible without departing from the scope of the invention as defined in the appended claims.
[0188] The following abbreviations that may appear in this specification and / or drawings are defined as follows:
[0189] 3GPP Third Generation Partnership Project
[0190] 5G (Fifth Generation)
[0191] 5GC 5G Core Network
[0192] AF Application Functions
[0193] AI / ML Artificial Intelligence / Machine Learning
[0194] AMF Access and Mobility Management Functions
[0195] AnLF Analysis Logic Function
[0196] AP access point
[0197] API (Application Programming Interface)
[0198] AUSF Authentication Server Functionality
[0199] bin (binary)
[0200] BSF Binding Support Functionality
[0201] CAPIF Public API Framework
[0202] CHF Billing Function
[0203] CN Core Network
[0204] EPS Evolution Grouping System
[0205] FN-BRG Fixed Network Broadband Residential Gateway
[0206] gNB and gNodeB are used as base stations for 5G.
[0207] GLI Global Line Identifier
[0208] GPSI General Public Subscription Identifier
[0209] GSMA GSM Association, where GSM = Global System for Mobile Communications.
[0210] HTTP (Hypertext Transfer Protocol)
[0211] ID or Id identifier
[0212] I / F interface
[0213] IMEI International Mobile Equipment Identity
[0214] IMSI International Mobile Subscriber Identity
[0215] MNO mobile network operator
[0216] MTLF model training logic function
[0217] MSISDN Mobile ISDN (International Subscriber Directory Number)
[0218] N3IWF Non-3GPP Interoperability Function
[0219] NBI (GSMA OP) Northbound Interface
[0220] NEF Network Public Function
[0221] NF Network Functions
[0222] ng or NG next generation
[0223] NG-RAN (Next Generation Radio Access Network)
[0224] NR New Wireless
[0225] NRF Network Repository Functionality
[0226] NSSF Network Slice Selection Function
[0227] NWDAF Network Data Analysis Function
[0228] OAM Operation, Management and Maintenance
[0229] OP (GSMA) operator platform
[0230] OPG (GSMA) Operator Platform Group
[0231] OS operating system
[0232] PEI Permanent Device Identifier
[0233] PRD Permanent Reference Document
[0234] RAN (Radio Access Network)
[0235] SBA Service-Based Architecture
[0236] SBI Southbound Interface
[0237] SBI-NR (GSMAOP) is an SBI framework for network resources.
[0238] SIM subscriber identification module
[0239] SMF Session Management Function
[0240] SUPI subscription permanent identifier
[0241] UDM Unified Data Management
[0242] UDR Unified Data Repository
[0243] UPF User Face Functions
[0244] UE (User Equipment) (Wireless, typically mobile devices)
[0245] VM virtual machine
Claims
1. A communication apparatus comprising components for: In the core network of a cellular network, an association between a first identifier and a second identifier for a user equipment is managed, wherein a change in the association between the first identifier and the second identifier for the user equipment indicates a change in the end-user subscription; Receive a request for an event report related to a change in the association between the first identifier and the second identifier used for the user equipment; Detect changes in the association; as well as The detected changes are reported to network functions in the core network.
2. The apparatus according to claim 1, wherein: The request for an incident report includes information instructing immediate reporting; and The component is also configured to send information to the network function in the core network, prior to receiving the request, indicating one or more changes detected in the association between the first identifier and the second identifier; or The request for an incident report includes information instructing immediate reporting and the corresponding time period; and The component is also configured to, before receiving the request and during the time period, determine whether one or more changes have been detected in the association between the first identifier and the second identifier, and send information to the network function in the core network indicating any identified one or more changes along with their corresponding timestamps.
3. The apparatus of any one of claims 1 to 2, wherein the request for an event report related to a change in the association between the first identifier and the second identifier for the user equipment includes an event type corresponding to a service for monitoring the event type, the service taking the identification information of the user equipment as input and outputting a timestamp of the last time the event corresponding to the change subscribed by the end user occurred in the core network and the current identification information of the user equipment, and wherein the event is triggered in response to any change in the first identifier list associated with the second identifier in the identification information of the user equipment.
4. A communication apparatus comprising components for: In the core network of a cellular network, the association between a first identifier and a second identifier for a user equipment should be monitored, and events related to said association should be reported, wherein a change in the association between the first identifier and the second identifier for the user equipment indicates a change in the end-user's subscription; and Send a request for event reporting to the network functions in the core network to request that the association between the first identifier and the second identifier used for the user equipment be monitored and that the event used for the association be reported.
5. The apparatus according to claim 4, wherein: The request for an incident report includes information instructing immediate reporting; The component is also configured to, in response to the request, receive information indicating one or more changes in the association between the first identifier and the second identifier that were detected prior to the request for an event report; and The information indicating one or more changes includes information indicating the current state of the association, which is indicated by the time when the association was created.
6. The apparatus according to claim 4, wherein: The request for an incident report includes information instructing immediate reporting and the corresponding time period; and The component is also configured to receive information indicating any one or more changes to the network functions in the core network that have been determined to have occurred during the time period.
7. The apparatus according to any one of claims 4 to 6, wherein: The following items are determined in response to a request from the application for the monitoring and reporting: the association between the first identifier and the second identifier for the user device should be monitored, and events related to the association should be reported; and For any information indicating that one or more changes in the association have been determined to have been performed, the information indicating the one or more changes will be reported to the application.
8. The apparatus according to any one of claims 4 to 6, wherein the component is further configured to: Restart the full user authentication process to cross-check that any association changes that have occurred for the first and second identifiers do not indicate that the second identifier has been associated with another user; or A notification is received from the network function, the notification indicating that the association between the first identifier and the second identifier for the user equipment has changed, the notification having a corresponding timestamp, and including a monitoring event type indicating that the association between the first identifier and the second identifier for the user equipment has changed.
9. A communication apparatus comprising components for: In the core network of a cellular network, a request for event reporting is received from a first network function to request that an association between a first identifier and a second identifier for a user equipment be monitored and an event for the association be reported, wherein a change in the association between the first identifier and the second identifier for the user equipment indicates a change in the end-user subscription. A message is sent to a second network function that manages the association between the first identifier and the second identifier for the user equipment. The message requests the second network function to monitor the association between the first identifier and the second identifier for the user equipment and the events that will be reported for the association between the first identifier and the second identifier for the user equipment. Receive a report from the second network function containing information indicating detected changes in the association; as well as Send information to the first network function indicating the detected change in the association.
10. The apparatus of claim 9, wherein the request from the first network function includes an event type corresponding to a service for monitoring the event type, the service using the second identifier as an input identifier, and outputting a timestamp corresponding to the last time the event of the change in the end-user subscription occurred in the core network and the current identification information of the user equipment.
