Apparatus, method and computer program relating to event monitoring

Abstract

Embodiments of the present disclosure relate to apparatuses, methods, and computer programs relating to event monitoring. A user device includes at least one processor and at least one memory storing instructions that, when executed by the at least one processor, cause the user device to at least perform: generating a message, the message includes one or more permissions for reporting user equipment related events to one or more monitoring entities; and causing the message to be sent to one or more control network entities.

Description

Technical Field

[0001] The present disclosure relates generally to communication systems and, in particular, but not exclusively, to apparatus, methods and computer programs related to event monitoring in communication systems. Background Art

[0002] A communication system can be considered as a facility that enables communication between two or more communication devices or provides communication devices with access to a data network. A mobile or wireless network is an example of a communication system. Communication devices can be served by application servers.

[0003] Such communication systems operate according to standards such as those provided by 3GPP (3rd Generation Partnership Project) or ETSI (European Telecommunications Standards Institute).An example of a standard is the so-called 5G (fifth generation) standard provided by 3GPP. Summary of the invention

[0004] According to one aspect, a user equipment is provided, comprising: a component for generating a message including one or more permissions for reporting user equipment related events to one or more monitoring entities; and a component for causing the message to be sent to one or more controlling network entities.

[0005] A shared permission may be provided for a collection of two or more different types of user device-related events.

[0006] The user device-related events may include two or more different types of events associated with corresponding permissions.

[0007] One or more different permissions are provided for different monitoring entities among the one or more monitoring entities.

[0008] The one or more permissions may be used by one or more of the one or more controlling network entities to control whether user equipment related events are reported by the one or more network entities to a monitoring entity of the one or more monitoring entities.

[0009] The message may also include a validity period associated with one or more of the one or more rights.

[0010] The message may include a registration request.

[0011] The user equipment may include means for determining that one or more permissions for reporting user equipment related events have changed, means for generating a further message in response, and means for causing the further message to be sent to one or more controlling network entities, the further message including information about the changed one or more permissions for reporting user equipment related events.

[0012] User device related events can include one or more of the following:

[0013] One or more connection loss events;

[0014] one or more reachabilities of user device events;

[0015] one or more locations of user device events;

[0016] Subscribe to one or more changes in permanent identifier permanent device identifier associated events;

[0017] one or more roaming status events;

[0018] one or more communication failure events;

[0019] one or more availability following a downlink data notification failure event;

[0020] One or more protocol data unit session state monitoring authority events;

[0021] one or more numbers of user devices present in the relevant geographic area;

[0022] One or more core network type change events;

[0023] one or more downlink data delivery status events;

[0024] one or more user equipment reachability for a short message service delivery event;

[0025] one or more memories of the user equipment available for short message service events;

[0026] one or more numbers of registered user device events;

[0027] one or more established protocol data unit session events;

[0028] one or more area of ​​interest events;

[0029] One or more group membership list change events; or

[0030] One or more group maximum bitrate events.

[0031] One or more of the one or more monitoring entities include an untrusted monitoring entity.

[0032] One or more of the one or more monitoring entities may be provided outside the core network.One or more controlling network entities may be provided in the core network.

[0033] A controlling network entity of the one or more controlling network entities may include means for providing access and mobility functions.

[0034] A controlling network entity of the one or more controlling network entities may include means for providing user data management functionality.

[0035] According to another aspect, a user equipment is provided, which includes at least one processor and at least one memory, wherein the at least one memory stores instructions, which when executed by the at least one processor causes the user equipment to at least perform: generate a message, wherein the message includes one or more permissions for reporting user equipment related events to one or more monitoring entities; and cause the message to be sent to one or more control network entities.

[0036] According to another aspect, a method is provided, the method comprising: generating a message comprising one or more permissions for reporting user equipment related events to one or more monitoring entities; and causing the message to be sent to one or more controlling network entities.

[0037] A shared permission may be provided for a collection of two or more different types of user device-related events.

[0038] The user device-related events may include two or more different types of user-related events associated with corresponding permissions.

[0039] One or more different permissions are provided for different monitoring entities among the one or more monitoring entities.

[0040] The one or more permissions may be used by one or more of the one or more controlling network entities to control whether user equipment related events are reported by the one or more network entities to a monitoring entity of the one or more monitoring entities.

[0041] The message may also include a validity period associated with one or more of the one or more rights.

[0042] The message may include a registration request.

[0043] The method may include determining that one or more permissions for reporting user equipment related events have changed, generating a further message in response, and causing the further message to be sent to one or more controlling network entities, the further message including information about the changed one or more permissions for reporting user equipment related events.

[0044] User device related events can include one or more of the following:

[0045] One or more connection loss events;

[0046] one or more reachabilities of user device events;

[0047] one or more locations of user device events;

[0048] Subscribe to one or more changes in permanent identifier permanent device identifier associated events;

[0049] one or more roaming status events;

[0050] one or more communication failure events;

[0051] one or more availability following a downlink data notification failure event;

[0052] One or more protocol data unit session state monitoring authority events;

[0053] one or more numbers of user devices present in the relevant geographic area;

[0054] One or more core network type change events;

[0055] one or more downlink data delivery status events;

[0056] one or more user equipment reachability for a short message service delivery event;

[0057] one or more memories of the user equipment available for short message service events;

[0058] one or more numbers of registered user device events;

[0059] one or more established protocol data unit session events;

[0060] one or more area of ​​interest events;

[0061] One or more group membership list change events; or

[0062] One or more group maximum bitrate events.

[0063] One or more of the one or more monitoring entities include an untrusted monitoring entity.

[0064] One or more of the one or more monitoring entities may be provided outside the core network.One or more controlling network entities may be provided in the core network.

[0065] A controlling network entity of the one or more controlling network entities may include means for providing access and mobility functions.

[0066] A controlling network entity of the one or more controlling network entities may include means for providing user data management functionality.

[0067] The method may be performed by a device. The device may be a user equipment.

[0068] According to another aspect, an apparatus is provided that includes: a component for receiving one or more permissions for reporting user device-related events of a first user device to one or more monitoring entities; and a component for storing the one or more permissions in association with data related to the first user device.

[0069] The apparatus may include a component for receiving a request, wherein the request is a request for notification of one or more user device-related events of a first user device by one of the one or more monitoring entities; and a component for determining whether the request for notification of one or more user device-related events of the first user device is authorized based on one or more permissions.

[0070] The request from a monitoring entity may be received via a device providing a network opening function.

[0071] The data relating to the first user equipment may include subscriber data.

[0072] The device can provide user data management functions.

[0073] According to another aspect, a device is provided, comprising at least one processor and at least one memory, the at least one memory storing instructions which, when executed by the at least one processor, cause the device to at least perform: receiving one or more permissions for reporting user equipment-related events of a first subscriber user equipment to one or more monitoring entities; and storing the one or more permissions in association with data related to the first user equipment.

[0074] According to another aspect, a method is provided, the method comprising: receiving one or more permissions for reporting user equipment related events of a first user equipment to one or more monitoring entities; and storing the one or more permissions in association with data related to the first user equipment.

[0075] The method may include receiving a request, wherein the request is a request from one of the one or more monitoring entities for notification of one or more user device-related events for a first user device; and determining whether the request for notification of one or more user device-related events for the first user device is authorized based on one or more permissions.

[0076] The request from a monitoring entity may be received via a device providing a network opening function.

[0077] The data relating to the first user equipment may include subscriber data.

[0078] The method may be performed by a device. The device may provide a user data management function.

[0079] According to another aspect, an apparatus is provided, comprising: means for receiving one or more permissions for reporting user equipment related events of a first subscriber user equipment to one or more monitoring entities; and means for sending the one or more permissions to an apparatus providing user data management functions.

[0080] One or more permissions for reporting user device related events of the first user device may be received from the first user device.

[0081] The device can provide access and mobility functions.

[0082] According to another aspect, an apparatus is provided, comprising at least one processor and at least one memory, the at least one memory storing instructions which, when executed by the at least one processor, cause the apparatus to at least perform: receiving one or more permissions for reporting user equipment-related events of a first subscriber user equipment to one or more monitoring entities; and sending one or more permissions to an apparatus providing user data management functionality.

[0083] According to another aspect, a method is provided, the method comprising: receiving one or more permissions for reporting user equipment related events of a first subscriber user equipment to one or more monitoring entities; and sending the one or more permissions to an apparatus providing a user data management function.

[0084] One or more permissions for reporting user device related events of the first user device may be received from the first user device.

[0085] The method may be performed by a device. The device may provide access and mobility functions.

[0086] According to another aspect, a computer program is provided, the computer program comprising instructions which, when executed by an apparatus, cause the apparatus to perform any of the previously listed methods.

[0087] According to another aspect, a computer program is provided, the computer program comprising instructions which, when executed, cause any of the previously listed methods to be performed.

[0088] According to one aspect, there is provided a computer program comprising computer executable code which, when run, causes any of the previously listed methods to be performed.

[0089] According to one aspect, a computer readable medium is provided, on which program instructions are stored, the program instructions being used to execute at least one of the above methods.

[0090] According to one aspect, a non-transitory computer readable medium is provided, the non-transitory computer readable medium comprising program instructions which, when executed by an apparatus, cause the apparatus to perform any of the previously listed methods.

[0091] According to one aspect, a non-transitory computer readable medium is provided, the non-transitory computer readable medium comprising program instructions which, when executed, cause any of the previously listed methods to be performed.

[0092] According to one aspect, a non-volatile tangible storage medium is provided, the non-volatile tangible storage medium having stored thereon program instructions for executing at least one of the above methods.

[0093] In the above, many different aspects have been described. It should be understood that other aspects can be provided by combining any two or more of the above aspects.

[0094] Various other aspects are also described in the following detailed description and appended claims. BRIEF DESCRIPTION OF THE DRAWINGS

[0095] Embodiments will now be described, by way of example only, with reference to the accompanying drawings, in which:

[0096] Figure 1 A schematic overview of some embodiments is shown;

[0097] Figure 2 shows a schematic diagram of a 5G system in which some embodiments may be provided;

[0098] Figure 3 A schematic diagram showing a device that can implement corresponding network functions;

[0099] Figure 4 A schematic diagram of a user equipment is shown;

[0100] Figure 5a and Figure 5b shows the registration process of some embodiments;

[0101] Figure 6 The event opening process of some embodiments is shown;

[0102] Figure 7 A first method of some embodiments is shown;

[0103] Figure 8A second method of some embodiments is shown; and

[0104] Fig. 9 A third method of some embodiments is shown. DETAILED DESCRIPTION

[0105] Some embodiments relate to permissions for providing (e.g., reporting) events to a monitoring entity. These events may be user equipment (UE) related events. Permissions may be used to provide (e.g., report) user equipment related events to a monitoring entity.

[0106] The monitoring entity may be an application server or an untrusted application function that is outside the core network of the communication system and connected to the core network via a network open function of the core network. The core network may be a 3GPP core network (CN) of a 3GPP communication system (hereinafter referred to as a 3GPP system) or any other suitable core network.

[0107] Currently, the 3GPP core network allows monitoring entities (e.g., application servers) to access information stored by the 3GPP core network. For example, the monitoring entity can access information stored by the 3GPP core network using the event open mechanism of the 3GPP core network. The event open mechanism is specified for both the fourth generation 3GPP core network (e.g., Evolved Packet Core (EPC)) and the fifth generation 3GPP core network (e.g., 5GC). The event open mechanism allows an external service capability server (SCS) and / or application server (AS) connected to the EPC, or an untrusted AF (application function) connected to the 5GC to subscribe to notifications about the status of certain UEs communicating with the 3GPP system. The need to receive notifications about the status of certain UEs may stem from the needs of applications running on the SCS or AS or untrusted AF.

[0108] SCS, AS and untrusted AF are some examples of monitoring entities. For example, the monitoring entity may be an AF having a control plane (CP) part connected to the network open function (NEF) of the 5GC and configured to request information about the UE from the 5GC. The monitoring entity may have a user plane part that interacts with the user plane (e.g., UPF) of the 3GPP core network. The user plane part and the control part may be distributed in different entities or provided by a single entity.

[0109] A monitoring entity connected to a 3GPP core network is generally referred to as an external monitoring entity. The external monitoring entity is configured to subscribe to notifications about user equipment (UE) related events to the 3GPP core network (e.g., an event open mechanism of the 3GPP core network). The 3GPP core network (e.g., an event open mechanism of the 3GPP core network) reports monitoring event reports with user equipment (UE) related events to the monitoring entity. However, a privacy issue is that a user, subscriber, or operator of a network (e.g., a core network) associated with a target UE cannot express consent to be monitored by the network (e.g., a core network).

[0110] It is known that the monitoring process may not involve signaling from the UE directly to the monitoring entity. Instead, one or more network entities of the 3GPP core network may report UE-related events to an external monitoring entity.

[0111] Make a reference Figure 1 , which shows an overview of some embodiments. UE 300 communicates with core network (CN) 400. Monitoring entity 404 has a notification of UE-related events subscribed to, or requests information about authorization to monitor and provide (e.g., report) UE-related events from the 3GPP core network using the event open mechanism of the 3GPP core network. UE-related events are monitored and provided (e.g., reported) to the monitoring entity by the core network. In some embodiments, the core network will monitor and provide (e.g., report) UE-related events to the monitoring entity only when the subscriber, user or operator of the UE allows or authorizes the core network to monitor and provide (e.g., report) UE-related events to the monitoring entity. In some embodiments, the authority of the core network to monitor and provide (e.g., report) UE-related events to the monitoring entity may depend on the monitoring entity having subscribed to UE-related events or having requested the 3GPP network to provide UE-related events to the monitoring entity. In some embodiments, the authority of the core network to monitor and provide (e.g., report) UE-related events to the monitoring entity may depend on the type of UE-related events.

[0112] Thus, in some embodiments, the authority to provide (e.g., report) one or more UE-related events to the monitoring entity may be granted or denied. The authority to monitor and provide (e.g., report) one or more UE-related events to the monitoring entity may be considered as reporting authority or monitoring authority for the UE. In some embodiments, the monitoring entity may be external to the core network. In some embodiments, the monitoring entity may be part of the core network.

[0113] Examples of UE-related events may include one or more of a UE location (eg, the location of the UE) and a number of data connections (PDU (Protocol Data Unit) sessions) that the UE has.

[0114] In another example, the monitoring entity may be interested in the registration status or reachability of a telemetry type UE that is using aggressive UE power saving via extended discontinuous reception (eDRX), power saving mode (PSM), or mobile initiated communications only (MICO) mode, which limits the ability to page the UE. The event open mechanism of the 3GPP core network allows the monitoring entity to subscribe to notification event reports, and the 3GPP core network can use the event open mechanism to notify the monitoring entity (e.g., provide to the monitoring entity) when the target UE registers with the 3GPP core network or when the UE becomes reachable. Reporting authority to provide event reports to the monitoring entity can be granted or denied.

[0115] Based on CN detectable protocol events, an event opening mechanism via reporting of monitoring events (e.g., UE related events) may be triggered. The UE and the radio interface may not be directly involved in the event opening procedure, even though UE communications over the radio interface may result in the CN sending monitoring event reports. This may be the case if the monitoring entity has subscribed to notifications of UE related event types related to ongoing radio interface procedures. Reporting rights for the UE for the core network to monitor and provide (e.g., report) these UE related events to the monitoring entity may be granted or denied.

[0116] Hereinafter, in some example embodiments, core network 400 may be a 5G core network of a 5G communication system. However, embodiments may be used for other communication systems, including future communication systems, such as 6G communication systems.

[0117] Figure 4 A schematic diagram of a communication system operating based on a fifth generation radio access technology, commonly referred to as a 5G system (5GS), and in which some embodiments may be implemented is shown. The 5GS may include a (radio) access network (RAN), or more generally, the 5G access network may correspond to, for example, a (radio) access network (RAN), a wired access gateway (W-AGF), an N3IWF (non-3GPP interworking function), etc. The 5GS may include a 5G core network (5GC), one or more application functions (AFs), and one or more data networks (DNs). A user equipment (UE) 300 may access or connect to one or more DNs via the 5GS. It should be understood that one or more AFs may be considered as monitoring entities. One or more AFs may be provided by a third party different from the 5GC network operator. As previously described, the AF may provide the control plane portion of the monitoring entity.

[0118] The 5G(R)AN may include one or more base stations or radio access network (RAN) nodes, such as gNodeB (gNB). A base station or RAN node may include one or more distributed units connected to a central unit.

[0119] 5GC may include various network functions, such as access and mobility management function (AMF), session management function (SMF), authentication server function (AUSF), user data management (UDM), user plane function (UPF), network data repository (NRF), network exposure function (NEF), service communication proxy (SCP), edge application server discovery function (EASDF), policy control function (PCF), network slice access control function (NSACF), network slice specific authentication and authorization function (NSSAAF), and / or network slice selection function (NSSF).

[0120] Figure 3 An example of an apparatus 200 is shown. The apparatus 200 may include or implement Figure 2 One or more of the network functions shown. The device 200 may have at least one processor and at least one memory, the memory storing Figure 2 The apparatus 200 may include at least one random access memory (RAM) 211a and / or at least one read-only memory (ROM) 211b. The apparatus 200 may include at least one processor 212, 213 and / or a network interface 214. At least one processor 212, 213 may be coupled to at least one memory, which in this example is RAM 211a and ROM 211b. At least one processor 212, 213 may be configured to execute appropriate software code 215. For example, the software code 215 may include Figure 2 The software code of one or more of the network functions shown includes software that allows the device to perform one or more operations of one or more aspects of the present invention. For example, the software code 215 may include Figure 2 The UDM function shown or Figure 2 Software code for the AMF function.

[0121] Figure 4An example of a communication device 300 or UE is illustrated. The communication device 300 may be any device capable of or configured to send and receive signals. The communication device may be a wired device or a wireless device. In the case where the communication device is a wireless device, the signal may be a wireless signal such as a radio signal. The communication device 300 may include a mobile station (MS) or a mobile device such as a mobile phone or a so-called "smartphone", a computer equipped with a wireless interface card or other wireless interface facilities (e.g., a USB dongle), a personal data assistant (PDA) or a tablet, a machine type communication (MTC) device, a cellular Internet of Things (CIoT) device, or any combination thereof. The communication device may be an XR (extended reality) device such as a headset, or may be capable of supporting XR applications (e.g., capable of executing or running XR applications). The headset may be a VR headset. The communication device may be a vehicle, UAV or AVV or a part thereof. The communication device 300 may be configured to send or receive wireless signals, such as radio signals carrying communications. The communication may be one or more of voice, email (email), text message, multimedia, data, machine data, etc.

[0122] In the case where the communication device 300 is a wireless device, the communication device may be configured to send and / or receive wireless signals, such as radio signals, via a transceiver device 306 over the air or radio interface 307. The transceiver device 306 may include, for example, a radio part and an associated antenna arrangement. The radio part may convert baseband signals to radio frequency and / or vice versa. The antenna arrangement may be arranged internally or externally to the mobile device and may include a single antenna or multiple antennas. The antenna arrangement may be an antenna array including multiple antenna elements.

[0123] The communication device 300 may include at least one processor 301 and / or at least one memory. The at least one memory may be at least one ROM 302a and / or at least one RAM 302b. Other possible components 303 may be provided for software and hardware-assisted execution of the tasks it is designed to perform, including control of access to and communication with access networks (such as 5G RAN and other communication devices). At least one processor 301 is coupled to RAM 302b and ROM 302a. At least one processor 301 may be configured to execute instructions of software code 308. The execution of the instructions of software code 308 may, for example, allow the communication device 300 to perform one or more operations. The software code 308 may be stored in ROM 302a. It should be understood that in other embodiments, any other suitable memory may be used alternatively or additionally.

[0124] The at least one processor 301 , the at least one ROM 302 a and / or the at least one RAM 302 b may be arranged on a suitable circuit board, in an integrated circuit and / or in a chipset. This feature is indicated by reference 304 .

[0125] The communication device 300 may optionally have a user interface, such as a keypad 305, a touch-sensitive screen or touchpad, a combination thereof, etc. Optionally, the communication device may have one or more of a display, a speaker, and a microphone.

[0126] In the following examples, the term UE or User Equipment is used. This term includes any of the previously discussed examples of the communication device 300 and / or any other communication device.

[0127] In some embodiments, a user of a UE (hereinafter referred to as UE user) may grant or deny reporting rights of the UE for allowing a network (eg, CN 400 ) to send notifications of UE-related events to a monitoring entity 404 outside CN 400 .

[0128] In some embodiments, the UE may be programmed or configured to have one or more reporting permissions for the UE. In some embodiments, the UE may be programmed or configured by the UE or the owner of the UE to have one or more reporting permissions. Optionally, the programming or configuration of the UE may be done over the air. For example, when an employee uses the UE, the employee's employer may control the reporting permissions for UE-related events. In another example, the UE may be a monitoring UE, and the owner or operator of the monitoring UE may control the reporting permissions for UE-related events.

[0129] When the UE registers with the core network 400, the UE may provide the core network 400 with the reporting authority of the UE. The reporting authority of the UE may be signaled to the core network 400 (e.g., AMF in the case where the core network is 5GC, or MME (mobility management entity) in the case where the core network is EPC). The AMF or MME may be regarded as a controlling network entity. By including the change of the reporting authority of the UE in the registration process initiated by the UE 300 when the UE setting is changed, the change of the reporting authority of the UE may be signaled to the core network (AMF or MME).

[0130] Reporting permissions may be changed by the user at the UE, or over the air, or via the network.

[0131] If regulatory requirements allow or require public authorities to monitor UEs, the ability of a UE user to deny monitoring of one or more specific UE-related events or to monitor all relevant events may be overridden in the 3GPP core network (e.g., CN 400). In some embodiments, the UE's reporting rights may only be overridden by a properly authorized monitoring entity.

[0132] The reporting authority of the UE for a given type of UE-related event may apply to any monitoring entity. Alternatively, the reporting authority of the UE for a given type of UE-related event may apply only to an external monitoring entity. Alternatively, the secondary reporting authority of the UE for a given type of UE-related event may be set for one or more designated monitoring entities.

[0133] The reporting rights of a UE that allow sending notification event reports (eg, notification reports on UE-related events) may be active or passive.

[0134] For example, the UE may proactively provide the event disclosure mechanism of the CN 400 with a reporting authority for exposing the network information of the UE to an external third party.

[0135] The reporting authority of the UE may be included in non-access stratum (NAS) signaling, such as a registration request included in NAS signaling sent by the UE to the AMF of the 3GPP core network. If the AMF receives NAS signaling including an indication of the reporting authority of the UE (e.g., yes or no), the AMF may include the indication in a UE CM (connection management) registration message sent by the AMF to the UDM. The UE CM registration message may be sent by the AMF to the UDM via the N8 interface of the CN 400.

[0136] If the UE does not have such reporting rights provisioned for the UE, the core network falls back to using the pre-configured default reporting rights for the UE stored as part of the subscriber data. The default reporting rights for the UE may be set to allow reporting of UE related events for the subscriber, or to deny reporting of UE related events for the subscriber. The default rights for the UE may be set for all UE related events, or for one type of UE related events, or for multiple different types of UE related events. The default reporting rights may be set for all monitoring entities, for each monitoring entity, or for each monitoring entity class.

[0137] When deciding whether to authorize a notification event subscription from a monitoring entity and which subscription is for a certain UE, the UDM checks the reporting rights of the UE. In addition, the UDM may also check any other specified authorization criteria. These other specified authorization criteria may be as defined in TS 23.502 clause 4.15.3.2.3 step 2.

[0138] If reporting rights have been provided to the UDM of the target UE, the UDM uses the reporting rights to determine whether to authorize the notification event subscription. If no reporting rights have been provided to the UDM of the target UE, the UDM may use the preconfigured default settings in the subscriber data to determine whether to authorize the notification event subscription.

[0139] The following table provides some examples of event types. The table indicates the event types specified for 5GS in TS23.502 Section 4.15.3.1. Some embodiments may be used with one or more event types in the table and / or one or more different event types not shown in the table.

[0140]

[0141]

[0142]

[0143] The reporting rights of the UE (whether explicitly indicated in the NAS process or stored as part of the subscriber data) may be used for certain types of UE-related events. For example, the reporting rights of the UE may allow the core network (e.g., CN 400) to provide information required for UE reachability to an external monitoring entity. The reporting rights of the UE allow the external monitoring entity to communicate with the UE. However, the reporting rights of the UE may not allow the core network to provide (e.g., report) UE-related events to the monitoring entity, such as revealing subscriber-related information. For example, the reporting rights of the UE may not allow the core network (e.g., CN 400) to provide (e.g., report) UE-related events such as UE location or roaming status to the monitoring entity.

[0144] Therefore, the reporting authority of the UE can be granted or denied according to each event type (e.g., the reporting authority of the UE can be granted or denied for each type of UE-related event). For example, the monitoring entity can provide (e.g., report) UE-related events, such as the reachability status of the UE, by allowing one or more monitoring events (such as connection loss, UE reachability, PDU session status, and / or UE reachability for SMS (Short Message Service) delivery). If it is not desired to allow the monitoring entity to know the geographical location of the UE at the same time, the reporting authority of the UE will be denied for UE-related events related to location reporting.

[0145] One or more reporting permissions of the UE may be associated with a validity period. At the end of the validity period, the reporting permissions may be restored to the default reporting permissions or restored to the opposite reporting permissions.

[0146] The reporting rights of the UE indicated by the UE or the pre-configured reporting rights of the UE may allow the core network (e.g., CN 400) to provide (e.g., report) UE-related events to a specific monitoring entity. For example, the reporting rights of the UE may allow a monitoring entity associated with an employer to access any UE-related events, such as roaming or location-related events of an employee's UE, while preventing other monitoring entities from accessing roaming or location-related events of the same UE.

[0147] Make a reference now Figure 5a and Figure 5b , they show an example process where permissions for event notification reporting (referred to herein as event notification permissions) are signaled to a core network (e.g., a 3GPP core network) as part of a registration process. In this example, permissions for event notification reporting are signaled to the core network in a NAS process (e.g., a registration process). Figure 5a and Figure 5b The process shown is based on the registration process specified in clause 4.2.2.2 of TS23.502. It should be understood that this is just an example, and in other examples, the rights for event notification reporting may be provided to the core network in any other suitable manner.

[0148] Therefore, in Figure 5a and Figure 5b In the example of , the UE signals (multiple) event notification rights in the NAS procedure, such as in a Registration Request message sent by the UE in the registration procedure. The (multiple) event notification rights may be as described above. The (multiple) event notification rights are received by the AMF. The AMF notifies the UDM of the (multiple) event notification rights. The AMF may notify the UDM of the (multiple) event notification rights by sending a Nudm_UECM_Registration message or other suitable message including the (multiple) event notification rights to the UDM.

[0149] It should be understood that in some embodiments, even without movement to another TA (tracking area) or expiration of the periodic update timer, the UE may make additional registration updates when the UE monitors changes in the authority settings.

[0150] In some embodiments, if the monitoring authority of the UE changes, the UE will obtain another new trigger for initiating an additional registration. This additional registration can be initiated by the UE sending a registration request in 5GS, such as Figure 5a shown.

[0151] At 1, the UE provides one or more monitoring permissions for allowing or denying notification event reporting. The monitoring permissions for reporting UE-related events are provided in (e.g., included in) a registration request sent by the UE to the RAN. The monitoring permissions associated with reporting of UE-related events may be as described above. The (multiple) monitoring permissions may be set by a user of the UE or may be set in other ways as described above.

[0152] At 2, RAN selects AMF (new AMF).

[0153] At 3, the RAN sends a registration request including monitoring rights to the selected AMF (new AMF).

[0154] At 4, optionally, the selected AMF sends a UE context transfer request to the old AMF. The request may be a Namf_Communication_UEContextTransfer request.

[0155] At 5, the old AMF provides a UE context transfer response to the new AMF.

[0156] At 6, if the UE does not provide SUCI (Subscriber Hidden Identity) and no SUCI is retrieved from the old AMF, the Identity Request procedure is initiated by the AMF by sending an Identity Request message to the UE requesting SUCI.

[0157] At 7, the UE responds with an Identity Response message including the SUCI.

[0158] At 8, AMF selects AUSF.

[0159] At 9, the UE is authenticated. This involves the AUSF, new AMF and UDM.

[0160] At 10, the new AMF notifies the old AMF that the UE's registration in the new AMF is complete, for example, by calling the Namf_Communication_RegistrationStatusUpdate service operation.

[0161] At 11, the AMF may send an identity request to the UE, and the UE provides a PEI (Permanent Equipment Identifier) ​​in response.

[0162] The new AMF may initiate a ME (Mobile Equipment) identity check with the EIR (Equipment Identity Register) at 12. The EIR performs the identity check and provides a response.

[0163] At 13, the new AMF selects a UDM if necessary.

[0164] At 14a, the new AMF registers with the UDM to access the registration. This can be done using Nudm_UECM_Registration. If a monitoring rights reference was provided in the registration request as part of the process received at 1, the AMF notifies the UDM of the monitoring rights included in the registration request. The UDM stores this indication as part of the subscriber data.

[0165] At 14b, if the new AMF does not have the UE's subscription data, the AMF retrieves the UE's subscription data, SMF select subscription data, UE context in SMF data, and LCS mobility initiation. This can be done using Nudm_SDM_Get.

[0166] At 14c, the AMF subscribes to be notified by the UDM when the requested data is modified. This can be done using Nudm_SDM_Subscribe.

[0167] At 14d, UDM initiates the deregistration procedure with the old AMF. This can be done using Nudm_UECM_DeregistrationNotification.

[0168] At 14e, the old AMF unsubscribes via UDM for the subscription data. This can be done using Nudm_SDM_unsubscribe.

[0169] At 15, the new AMF may select a new PCF.

[0170] At 16, the new AMF and the new PCF may perform AM (Access and Mobility) policy association establishment.

[0171] At 17, the AMF may send a session context update (e.g., Nsmf_PDUSession_UpdateSMContext) or a session context release (e.g., Nsmf_PDUSession_ReleaseSMContext) to the SMF.

[0172] At 18, if the new AMF and the old AMF are in the same PLMN, the new AMF sends a UE context modification request to the N3IWF (Non-3GPP Interworking Function), TNGF (Trusted Non-3GPP Gateway Function) or W-AGF (Wired Access Gateway Function).

[0173] At 19, if necessary, the N3IWF, TNGF or W-AGF sends a UE Context Modification Response to the new AMF.

[0174] At 19a, after the new AMF receives the UE Context Modification Response from the N3IWF, W-AGF or TNGF at 19, the new AMF may need to register its profile with the UDM. The AMF may register its profile with the UDM using Nudm_UECM_Registration, where the access type is set to "Non-3GPP Access". If monitoring rights are included in the registration request at 1, the AMF notifies the UDM of the monitoring rights included in the registration request. The UDM stores the monitoring rights as part of the subscriber data.

[0175] At 19b, UDM initiates the deregistration procedure to the old AMF. This can be done using Nudm_UECM_DeregistrationNotification.

[0176] At 19c, the old AMF unsubscribes from the subscription data via UDM. This can be done using Nudm_SDM_unsubscribe.

[0177] At 21, the new AMF may send a Registration Accept message to the UE.

[0178] As shown in 21b, the new AMF and PCF perform UE policy association establishment.

[0179] As shown in 22, the UE sends a registration completion message to the new AMF.

[0180] As shown in 23, if the access and mobility subscription data provided by the UDM to the new AMF in 14b includes guidance of roaming information and instructs the UDM to request confirmation of receipt of this information from the UE, the AMF provides the UDM with UE confirmation. This can be done using Nudm_SDM_Info. If the monitoring authority has been updated, the AMF can also provide the UDM with the updated monitoring authority.

[0181] As shown in reference 23a, for 3GPP access registration, if the AMF does not release the signaling connection, the AMF sends RRC inactive assistance information to the RAN.

[0182] At 24, after step 14a, in parallel with any previous steps, the AMF shall send a "Homogeneous support for IMS voice over PS sessions" indication to the UDM using Nudm_UECM_Update. If the monitoring rights have been updated, the AMF may also provide the UDM with the updated monitoring rights. The "Homogeneous support for IMS (IP Multimedia Subsystem) voice over PS (Packet Switched) sessions" indication is sent if:

[0183] - if the AMF has evaluated support for IMS Voice over PS sessions; and

[0184] - If the AMF determines that it needs to update the homogeneous support for IMS Voice over PS sessions.

[0185] At 25, if the UE indicates that it supports network slice specific authentication and authorization, the relevant procedures are performed at this step.

[0186] As described above, providing one or more monitoring permissions of the UE may be optional. Therefore, the monitoring permissions of the UE may not be provided or may not be obtained from the UE. In the absence of such monitoring permissions of the UE, one or more default monitoring permissions of the UE may be used. The default monitoring permission of the UE may be to allow monitoring of UE-related events, or the default monitoring permission may be to not allow or deny monitoring of UE-related events.

[0187] In some embodiments, the default monitoring permission of the UE may be to allow monitoring of UE-related events.

[0188] The default monitoring permissions can be changed by sending a request (such as the registration request described above) and user preferences for monitoring permissions. User preferences for monitoring permissions are stored in subscription data stored in the UDM and / or UDR.

[0189] Make a reference now Figure 6 , which illustrates an example event opening procedure, where permissions for event notification reporting are used to determine whether subscriptions to one or more events associated with a UE may be reported to a monitoring entity. Figure 6 The process shown is based on the event opening process specified in TS23.502 clauses 4.15.3.2.2 and 4.15.3.2.3.

[0190] AF can be used Figure 6 Use the procedures shown to subscribe to event notifications, modify a group-based event notification subscription, or explicitly cancel a previous subscription.

[0191] The following is an excerpt from TS23.502 4.15.3.2.3 - NEF Service Operation Information Flow, which discusses Figure 6 process.

[0192] However, in some embodiments, a portion of the process of reference 2 is modified. If the UDM has received one or more permissions for the UE's event notification report and / or one or more event types specified by the event notification subscription, the UDM uses these one or more permissions to determine whether to authorize the notification event subscription.

[0193] If the UDM does not receive any permissions from the UE and / or one or more event types specified by the event notification subscription, the UDM uses one or more default notification event permissions to determine whether to authorize the notification event subscription.

[0194] 1. AF subscribes to one or several events (identified by event IDs) and provides the relevant notification endpoint of AF by sending Nnef_EventExposure_Subscribe request.

[0195] The event reporting information defines the type of report requested (e.g., one-time report, periodic report, or event-based report for monitoring events). If the reporting event subscription is authorized by the NEF, the NEF records the association of the event trigger and the requester identity. The subscription may also include the maximum number of reports and / or the maximum duration of the reporting IE, and optional MTC provider information.

[0196] If the subscription to group-based event notification is deleted or added for some UEs in a group of UEs that have event notification subscription, the AF provides the affected UE information (e.g., SUPI, MSISDN (Mobile Station International Subscriber Directory Number) or external identity) and operation indication (which is cancellation or addition) to the NEF via Nnef_EventExposure_Subscribe, without canceling the entire group-based event notification subscription.

[0197] 2. [Conditional - subject to authorization in step 1] The NEF subscribes to receive events (identified by event IDs) and provides the relevant notification endpoints of the NEF to the UDM by sending a Nudm_EventExposure_Subscribe request. The NEF may receive the DNN (Data Network Name), S-NSSAI (Single Network Slice Selection Assistance Information) from the AF in step 1, or map the AF identifier to a combination of DNN and S-NSSAI based on local configuration and include the DNN and S-NSSAI in the request.

[0198] If the report event subscription is authorized by the UDM, the UDM records the association of the event trigger and the requester identity. Otherwise, the UDM proceeds to step 4 to indicate a failure.

[0199] If Nnef_EventExposure_Subscribe and its update are received in step 1, indicating the deletion of the event notification subscription of some UEs in a group of UEs for which event notification subscription exists, the NEF provides the affected UE information (e.g., SUPI, MSISDN or external identity) and the operation indication (cancellation) to the UDM via Nudm_EventExposure_Subscribe, without canceling the entire group-based event notification subscription. If the maximum number of reports applies to the event subscription, the NEF sets the number of reports of the stored (multiple) indicated UEs to the maximum number of reports.

[0200] If Nnef_EventExposure_Subscribe with update is received in step 1, indicating adding event notification subscription for some UEs in a group of UEs for which event notification subscription exists, NEF provides affected UE information (e.g., SUPI, MSISDN or external identity) and operation indication (addition) to UDM via Nudm_EventExposure_Subscribe.

[0201] 3a.[Conditional] If the requested event (e.g. monitoring for connection loss) requires AMF assistance, the UDM sends a Namf_EventExposure_Subscribe to the AMF serving the requested UE. The UDM sends a Namf_EventExposure_Subscribe request to all serving AMFs (if the subscription applies to a UE or a group of UEs), or to all AMFs in the same PLMN as the UDM (if the subscription applies to any UE).

[0202] NOTE 1: If a UE that is a member of a group registers with the AMF without having a subscription to group event(s) for the group, the UDM creates a subscription to these event(s) with the AMF during the registration procedure in clause 4.2.2.2.2.

[0203] Since the UDM itself is not an event receiving NF, in addition to the notification endpoint of the NEF, the UDM should also provide its own notification endpoint. Each notification endpoint is associated with a related (group) (multiple) event IDs. This is to ensure that the UDM can receive notifications of subscription change related events.

[0204] If the subscription applies to a group of (multiple) UEs, the UDM shall include its own same Notification Endpoint, i.e. Notification Target Address (+ Notification Correlation Id), in the subscriptions of the (multiple) serving AMFs of all UEs.

[0205] NOTE 2: The same notification endpoint of UDM is used to help the AMF identify whether the subscription to the requested group events is the same when a new group member UE registers.

[0206] If a Nudm_EventExposure_Subscribe with an update is received in step 2, indicating the deletion of the event notification subscription of some UEs in a group of UEs for which event notification subscription exists, the UDM provides the affected UE information (e.g. SUPI, MSISDN) and an action indication (cancellation) to the AMF via Namf_EventExposure_Subscribe, without cancelling the entire group-based event notification subscription for the events monitored by the AMF.

[0207] If a Nudm_EventExposure_Subscribe with an update is received in step 2, indicating the addition of an event notification subscription for some UEs in a group of UEs for which an event notification subscription exists, the UDM provides the affected UE information (e.g., SUPI, MSISDN) and an operation indication (addition) to the AMF via the Namf_EventExposure_Subscribe of the event monitored by the AMF.

[0208] 3b.[Conditional] AMF confirms the execution of Namf_EventExposure_Subscribe.

[0209] 3c. [Conditional] If the requested event (e.g., PDU session status) requires SMF assistance, the UDM sends a Nsmf_EventExposure_Subscribe request message to each SMF where at least one UE identified in step 2 has established a PDU session. The NEF notification endpoint received in step 2 is included in the message.

[0210] Note 3: In case of local routing, UDM sends subscription to V(Visitor)-SMF via H(Home)-SMF.

[0211] 3d-e. [Conditional] If the requested event (e.g., UserDataUsageMeasures) requires UPF assistance, SMF Figure 4 .Step 4 in 15.4.5.2-1 sends a request to the UPF, including the NEF notification endpoint received in step 3c.

[0212] 3f.[Conditional] SMF confirms the execution of Nsmf_EventExposure_Subscribe.

[0213] 4. [Conditional] UDM confirms the execution of Nudm_EventExposure_Subscribe.

[0214] If the subscription applies to a group (or multiple) of UEs and the maximum number of reports was included in the event report information in step 1, the number of UEs (including all group member UEs regardless of their registration status) is included in the confirmation. If the AMF or SMF provided the first event report in step 3b or step 3d, the UDM includes the event report in the confirmation.

[0215] 5. The NEF confirms the execution of Nnef_EventExposure_Subscribe to the requester that initiated the request. If the NEF has received the first event report in step 4, the NEF includes the event report in the confirmation.

[0216] 6a-6b.[Conditional - Event Dependent] The UDM (Event Dependent) detects the event occurrence and sends an event report along with a timestamp to the relevant notification endpoint of the NEF via the Nudm_EventExposure_Notify message. The NEF can store this information along with a timestamp in the UDR using the Nudr_DM_Create or Nudr_DM_Update service operations as needed.

[0217] If Nudm_EventExposure_Subscribe with an update is received in step 2, indicating the deletion of event notification subscriptions of some UEs in a group of UEs for which event notification subscriptions exist, the UDM shall stop event reporting for the affected UEs. If the maximum number of reports is applied, the UDM shall set the number of reports of the indicated UE(s) to the maximum number of reports for the events monitored by the UDM.

[0218] If Nudm_EventExposure_Subscribe with an update is received in step 2, indicating adding an event notification subscription for some UEs in a group of UEs for which event notification subscription exists, then UDM shall create a subscription to event notification for the affected UEs in order to detect the monitored events and send event reports for such affected UEs.

[0219] 6c to 6d. [Conditional - depends on the event] The AMF detects the event and sends an event report along with a timestamp to the relevant notification endpoint of the NEF via a Namf_EventExposure_Notify message. The NEF can store this information along with a timestamp in a UDR using the Nudr_DM_Create or Nudr_DM_Update service operations as needed.

[0220] If the AMF has stored the maximum number of reports for a UE or individual member UE, the AMF shall reduce its value of reporting events by 1.

[0221] If a Namf_EventExposure_Subscribe with an update is received in step 3a, indicating that some UEs in a group of UEs that have event notification subscriptions cancel event notification subscriptions, the AMF shall stop event notifications for the affected UEs. If the maximum number of reports is applied, the AMF shall set the number of reports for the specified UE(s) to the maximum number of reports.

[0222] If a Namf_EventExposure_Subscribe with an update is received in step 3a, indicating the addition of an event notification subscription for some UEs in a group of UEs for which an event notification subscription exists, the AMF shall create a subscription to the event notification for the affected UEs in order to detect the monitored events and send event reports for such affected UEs.

[0223] For both step 6a and step 6c, when the maximum number of reports is reached, if subscription is applied to the UE, the NEF unsubscribes from the monitoring event(s) to the UDM, and the UDM unsubscribes from the monitoring event(s) to the AMF serving the UE.

[0224] For both step 6a and step 6c, when the individual group member UE reaches the maximum reporting number, the NEF uses the number of UEs received in step 4 and the maximum reporting number to determine whether the reporting of the group is completed. If the NEF determines that the reporting of the group is completed, the NEF unsubscribes from the (multiple) monitoring events to the UDM, and the UDM unsubscribes from the (multiple) monitoring events to all (multiple) AMFs that provide services for UEs belonging to the group.

[0225] NOTE 4: If the expiry time specified in clause 6.2.6.2.6 of TS 29.518

[18] is not included in the event subscription, the lifecycle of the event subscription needs to be controlled by other means, since there is no time-based cancellation at all, even if any group member UE fails to register.

[0226] When the maximum reporting duration in NEF, UDM and AMF expires, each of these nodes shall locally unsubscribe from monitoring events.

[0227] 6e-6f. [Conditional - event dependent] When the SMF detects a subscribed event, the SMF sends an event report to the relevant notification endpoint of the NEF provided in step 3c via the Nsmf_EventExposure_Notify message. The NEF can store this information in the UDR along with a timestamp using the Nudr_DM_Create or Nudr_DM_Update service operations as needed.

[0228] 6g-6h.[Conditional - event dependent] When the UPF detects a subscription event, as part of step 3c, the UPF sends an event report to the relevant notification endpoint of the NEF provided by the SMF to the UPF via a Nupf_EventExposure_Notify message. The NEF may store this information along with a timestamp in a UDR using the Nudr_DM_Create or Nudr_DM_Update service operations as required.

[0229] 7. [Conditional - depends on the events in steps 6a-6f] The NEF forwards the reporting events received via Nudm_EventExposure_Notify and / or Namf_EventExposure_Notify to the AF. In case of a PDU Session Status Event, the NEF maps it to a PDN Connection Status Notification when reporting to the AF.

[0230] 8. [Conditional - event dependent] The AMF detects that a subscription change related event occurs, e.g. a subscription correlation ID changes due to AMF reallocation or a new subscription correlation ID is added due to a new group of UEs being registered, and the AMF sends an event report to the relevant notification endpoint of the UDM, e.g. by means of a Namf_EventExposure_Notify message.

[0231] a. If the user's notification event permissions are received from the UE in an earlier registration process, the permissions will be stored in the UDM. The UDM uses the permission settings requested by the UE to determine whether to authorize the notification event subscriptions received from the monitoring entity. The UDM may receive the request from the AF via the NEF.

[0232] b. If the monitoring request subscription is associated with a regulatory reason that overrides the subscriber's privacy, the UDM ignores the user permissions on the monitoring event and allows monitoring to continue regardless of any user permission settings.

[0233] c. If the notification event permissions for the event type requested in the subscription are not received from the UE, the UDM uses the default notification event permissions setting in the subscriber data to determine whether to authorize the notification event subscription.

[0234] d. The privacy request of the UE user can be encoded in the registration request by denying or allowing the core network to generate monitoring events. Monitoring permissions can be added as an extension of the existing IE (Information Element) or provided as part of an additional IE in a registration or similar request.

[0235] If a single allow / deny permission for all monitoring event types is supported, a single bit may be used. A single bit may indicate monitoring is allowed with one state and no monitoring permission with another state. This may be provided in an indication provided by the UE to, for example, the AMF.

[0236] In another example, the monitoring rights indication of the UE user can be encoded as a new IE in the registration request message. Examples of information elements (e.g., information) included in the registration message include the information elements shown in TS24.501 in Table 8.2.6.1.1, and a new information element called user monitoring rights, which is an information element for monitoring rights. In this example, the length of the user rights for monitoring IE is 5 octets, but this is just an example. In other embodiments, the IE can be longer or shorter than 5 octets. All 5 octets can be used, or only some of the 5 octets can be used.

[0237]

[0238]

[0239]

[0240] An illustrative example of a monitoring authority information element is given below.

[0241]

[0242] Hereinafter, examples of possible monitoring rights for different bits of the third octet, the fourth octet, and the fifth octet assigned to the IE are given. In this example, 7 bits of the last octet are unused or spare. It should be understood that this is only an example. In other embodiments, there may be more than 7 or less than 7 spare bits, or even no spare bits.

[0243] 17 monitoring authority examples are given below, as referenced to P1 to P17, and the locations are shown in the table above. It should be understood that in other embodiments, there may be more or less than 17 monitoring authorities. It should be understood that one or more different monitoring authorities may be provided alternatively or additionally. It should also be understood that the specific monitoring authority assigned to a specific bit of a specific octet is provided only as an example. In different embodiments, a given monitoring authority may be provided in different octets and / or different bits in an octet.

[0244] In the following, a given reporting permission of an allowed UE is associated with one value of a bit, and a corresponding reporting permission of a disallowed UE is associated with another value of the bit. In other embodiments, the opposite value may be used to indicate whether a particular reporting permission of a UE is allowed.

[0245] P1: Connection loss monitoring permission

[0246] 0 Do not allow connection loss detection

[0247] 1 Enable connection loss detection.

[0248] P2: UE reachability monitoring authority

[0249] 0 Do not allow UE reachability monitoring

[0250] 1 Allow UE reachability monitoring

[0251] P3: Location reporting monitoring permission

[0252] 0 Do not allow location monitoring

[0253] 1 Allow location monitoring

[0254] P4: SUPI-PEI association change authority

[0255] 0 Do not allow SUPI-PEI association changes

[0256] 1 Allow SUPI-PEI association changes

[0257] P5: Roaming status monitoring permission

[0258] 0 Do not allow roaming status monitoring

[0259] 1 Allow roaming status monitoring

[0260] P6: Communication fault monitoring authority

[0261] 0 Communication fault monitoring is not allowed

[0262] 1 Enable communication fault monitoring

[0263] P7: Availability monitoring authority after DL data notification failure

[0264] 0 Do not allow DL data to notify availability monitoring after a failure

[0265] 1 Allows DL data to notify availability monitoring after a failure

[0266] P8: PDU session status monitoring permission

[0267] 0 Do not allow PDU session status monitoring

[0268] 1 Allow PDU session status monitoring

[0269] P9: Permission to monitor the number of UEs present in a geographical area

[0270] 0 Do not allow monitoring of the number of UEs present in a geographical area

[0271] 1 Allows monitoring of the number of UEs present in a geographical area

[0272] Note: This monitoring is relevant to all UEs present in the area, so in some embodiments, it may not be appropriate to let any single UE set permissions for it. In some embodiments, there may be no privacy issues because this monitoring event only returns the UE count to the monitoring event subscriber P10: CN Type Change Monitoring Permissions

[0273] 0 Do not allow CN type change monitoring

[0274] 1 Allow CN type change monitoring

[0275] P11: DL data delivery status monitoring authority

[0276] 0 Do not allow DL data delivery status monitoring

[0277] 1 Allows DL data delivery status monitoring

[0278] P12: UE reachability monitoring permission for SMS delivery

[0279] 0 Do not allow UE reachability monitoring for SMS delivery

[0280] 1 Allow UE reachability monitoring for SMS delivery

[0281] P13: UE storage monitoring permission that can be used for SMS

[0282] 0 Do not allow UE memory monitoring available for SMS

[0283] 1 Allow monitoring of UE memory available for SMS

[0284] P14: Permission to monitor the number of registered UEs or established PDU sessions

[0285] 0 Do not allow monitoring of the number of UEs or established PDU sessions

[0286] 1 Allows monitoring of the number of UEs or established PDU sessions

[0287] Note: This monitoring is relevant to all UEs present in the area, so in some embodiments, it may not be appropriate to let any single UE set permissions for it. In some embodiments, there may be no privacy issues because the monitoring event only returns the UE count to the monitoring event subscriber P15: Interest area monitoring permissions

[0288] 0 Do not allow ROI monitoring

[0289] 1 Allows monitoring of regions of interest

[0290] P16: Group member list changes monitoring permissions

[0291] 0 Do not allow group member list change monitoring

[0292] 1 Allow group member list change monitoring

[0293] P17: Group MBR monitoring permissions

[0294] 0 Do not allow group MBR monitoring

[0295] 1 Enable group MBR monitoring

[0296] The remaining code points may be encoded as "alternate".

[0297] In some embodiments, any of the IE examples discussed above may be used in a message sent to the UDM for the AMF indicating the monitoring permissions associated with the UE. The IE may be included in any suitable message from the AMF to the UDM. For example, the IE may be included in a registration message such as a Nudm_UECM_Registration operation and / or an update message such as a Nudm_UECM_Update service operation.

[0298] Make a reference Figure 7 , which illustrates the methods of some embodiments.

[0299] The method may be performed by a device. The device may be a user equipment.

[0300] The apparatus may include suitable components such as circuitry for providing the method.

[0301] Alternatively or additionally, the apparatus may include at least one processor and at least one memory, the at least one memory storing instructions which, when executed by the at least one processor, cause the apparatus to at least provide the following method.

[0302] Alternatively or additionally, the device may be Figure 4 shown.

[0303] The method may be provided by computer program code or computer executable instructions.

[0304] As with reference A1 , the method may include generating a message including one or more permissions for reporting user equipment related events to one or more monitoring entities.

[0305] As with reference A2, the method may include causing the message to be sent to one or more controlling network entities.

[0306] It should be understood that Figure 7 The methods outlined in may be modified to include any of the features previously described.

[0307] Make a reference Figure 8 , which illustrates the methods of some embodiments.

[0308] The method may be performed by a device. The device may provide a user data management function.

[0309] The apparatus may include suitable components such as circuitry for providing the method.

[0310] Alternatively or additionally, the apparatus may include at least one processor and at least one memory, the at least one memory storing instructions which, when executed by the at least one processor, cause the apparatus to at least provide the following method.

[0311] Alternatively or additionally, the device may be Figure 3 shown.

[0312] The method may be provided by computer program code or computer executable instructions.

[0313] As referred to B1 , the method may include receiving one or more permissions for reporting user equipment related events of the first user equipment to one or more monitoring entities.

[0314] As with reference B2, the method may include storing one or more permissions in association with data related to the first user device.

[0315] It should be understood that Figure 8 The methods outlined in may be modified to include any of the features previously described.

[0316] Make a reference Fig. 9 , which illustrates the methods of some embodiments.

[0317] The method may be performed by a device. The device may provide access and mobility functions.

[0318] The apparatus may include suitable components such as circuitry for providing the method.

[0319] Alternatively or additionally, the apparatus may include at least one processor and at least one memory, the at least one memory storing instructions which, when executed by the at least one processor, cause the apparatus to at least provide the following method.

[0320] Alternatively or additionally, the device may be Figure 3 shown.

[0321] The method may be provided by computer program code or computer executable instructions.

[0322] As referenced to C1 , the method may include receiving one or more permissions for reporting user equipment related events of the first subscriber user equipment to one or more monitoring entities.

[0323] As shown in reference C2, the method may include sending one or more permissions to a device providing user data management functionality.

[0324] It should be understood that Fig. 9 The methods outlined in may be modified to include any of the features previously described.

[0325] The computer program code may be downloaded and stored in one or more memories of the relevant apparatus or device.

[0326] Therefore, although certain embodiments are described above by way of example with reference to certain example architectures of wireless networks, technologies and standards, the embodiments may be applied to any other suitable form of communication system than shown and described herein. In this example, some embodiments have been described for a 5G network.

[0327] It should also be noted herein that, although the exemplary embodiments are described above, without departing from the scope of the present invention, various changes and modifications may be made to the disclosed solution. As used herein, "at least one of the following: <list of two or more elements>" and "<at least one of the list of two or more elements>" and similar wording (wherein the list of two or more elements is connected by "and" or "or") refer to at least any one of these elements, or at least any two or more of these elements, or at least all of these elements. In general, various embodiments may be implemented in hardware or dedicated circuit systems, software, logic, or any combination thereof. Some aspects of the present disclosure may be implemented in hardware, while other aspects may be implemented in firmware or software, which may be performed by a controller, a microprocessor, or other computing devices, but the present disclosure is not limited thereto. Although various aspects of the present disclosure may be shown and described as block diagrams, flow charts, or using some other graphical representations, it is well understood that, as non-limiting examples, these blocks, devices, systems, techniques, or methods described herein may be implemented in hardware, software, firmware, dedicated circuits or logic, general hardware or controllers, or other computing devices, or some combination thereof.

[0328] As used in this application, the term "circuitry" may refer to one, more, or all of the following:

[0329] (a) purely hardware circuits (such as analog and / or digital circuits only), and

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

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

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

[0333] (c) hardware circuit(s) and / or processor(s), such as microprocessor(s) or portion(s) of microprocessor(s), that require software (e.g., firmware) for operation, but where not required for operation, the software may be absent.”

[0334] This definition of circuitry applies to all uses of the word "component" in this application, including in any claims. As another example, as used in this application, the term circuitry also covers an implementation of only a hardware circuit or processor (or multiple processors) or a portion of a hardware circuit or processor and its accompanying software and / or firmware. For example, if applicable to a particular claim element, the term circuitry also covers an integrated circuit such as 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 network device.

[0335] Embodiments of the present disclosure may be implemented by computer software executable by a data processor of a mobile device, such as in a processor entity, or by hardware, or by a combination of software and hardware. Computer software or programs (also referred to as program products, including software routines, applets and / or macros) may be stored in any device-readable data storage medium, and they include program instructions for performing specific tasks. A computer program product may include one or more computer executable components that are configured to perform an embodiment when the program is running. One or more computer executable components may be at least one software code or a portion thereof.

[0336] Furthermore, in this regard, it should be noted that any block of the logic flow shown in the figure can represent program steps, or interconnected logic circuits, blocks and functions, or a combination of program steps and logic circuits, blocks and functions. The software can be stored on physical media, such as memory chips or memory blocks implemented in a processor, magnetic media such as hard disks or floppy disks, and optical media such as DVDs and their data variants CDs. Physical media are non-transient media.

[0337] The term "non-transitory" as used herein is a restriction on the medium itself (ie, tangible, not a signal), not on the persistence of data storage (eg, RAM vs. ROM).

[0338] The memory may be of any type suitable for the local technical environment and may be implemented using any suitable data storage technology, such as semiconductor-based memory devices, magnetic memory devices and systems, optical memory devices and systems, fixed memory, and removable memory. The data processor may be of any type suitable for the local technical environment and may include, as non-limiting examples, one or more of a general-purpose computer, a special-purpose computer, a microprocessor, a digital signal processor (DSP), an application-specific integrated circuit (ASIC), an FPGA, a gate-level circuit, and a processor based on a multi-core processor architecture.

[0339] Embodiments of the present disclosure may be implemented in various components such as integrated circuit modules. The design of integrated circuits is generally a highly automated process. Complex and powerful software tools are available to convert logic level designs into semiconductor circuit designs for etching and formation on semiconductor substrates.

[0340] The above description provides a complete and informative description of exemplary embodiments of the present disclosure by way of non-limiting examples. However, when read in conjunction with the accompanying drawings and the appended claims, various modifications and adaptations may be apparent to those skilled in the relevant art in view of the above description. In fact, there are other embodiments that may include a combination of one or more embodiments with any other embodiments previously discussed. The claims define the scope of protection sought by some embodiments of the present disclosure. The embodiments and features (if any) described in this specification that do not fall within the scope of the claims will be interpreted as examples that are helpful in understanding the various embodiments of the present disclosure. It should be noted that in related applications (such as divisional applications or continuation applications), different claims with different claim scopes may be pursued.

Claims

1. A user equipment, comprising: At least one processor and at least one memory, wherein the at least one memory stores instructions, and when the instructions are executed by the at least one processor, the user equipment at least performs: generating one or more permissions for reporting events related to the user equipment to one or more monitoring entities; as well as A message including the one or more permissions for reporting user equipment related events is sent to one or more controlling network entities.

2. The user device according to claim 1, wherein the one or more permissions include: A shared permission for reporting two or more different types of events related to a user's device.

3. The user equipment according to claim 1, wherein the user equipment related event comprises: Two or more different types of user device-related events associated with corresponding permissions.

4. The user equipment of claim 1 , wherein the one or more permissions include at least two different permissions, and wherein sending includes: The at least two permissions are sent to different monitoring entities of the one or more monitoring entities.

5. A user device according to claim 1, wherein the one or more permissions are used by one or more of the one or more control network entities to control whether the one or more of the one or more control network entities are allowed to provide the user device-related events to the one or more control network entities.

6. The user equipment according to claim 1, wherein the message further comprises: A time period associated with one or more of the one or more permissions during which the one or more permissions are valid.

7. The user equipment of claim 1, wherein the message comprises a registration request.

8. The user equipment according to claim 1, further comprising: determining that one or more permissions for reporting events related to a user device have changed; as well as A further message to be generated is sent to the one or more controlling network entities, the further message having information about the changed one or more permissions for reporting user equipment related events.

9. The user equipment according to claim 1, wherein the one or more user equipment related events include one or more of the following: One or more connection loss events; one or more reachabilities of the user equipment event; one or more locations of the user equipment event; Subscribe to one or more changes in permanent identifier-permanent device identifier association events; one or more roaming status events; one or more communication failure events; one or more availability following a downlink data notification failure event; One or more protocol data unit session state monitoring authority events; one or more numbers of user devices present in the relevant geographic area; One or more core network type change events; one or more downlink data delivery status events; one or more user equipment reachability for a short message service delivery event; one or more memories of the user equipment available for short message service events; one or more numbers of registered user device events; one or more established protocol data unit session events; one or more area of ​​interest events; One or more group membership list change events; or One or more group maximum bitrate events.

10. An apparatus for a communication network, the apparatus comprising: at least one processor; as well as at least one memory storing instructions that, when executed by the at least one processor, cause the apparatus to at least perform: receiving one or more permissions for reporting user equipment related events of the first user equipment to one or more monitoring entities; and The one or more permissions are stored in association with data related to the first user device.

11. The apparatus of claim 10, wherein the instructions, when executed by the at least one processor, cause the apparatus to at least perform: receiving a request, the request being a request for notification of one or more user device-related events for the first user device sent by one of the one or more monitoring entities, and determining whether the request for notification of one or more user device-related events for the first user device is authorized based on the one or more permissions.

12. The apparatus of claim 11, wherein the request is received from the one monitoring entity via a device providing a network opening function.

13. An apparatus for a communication network, the apparatus comprising: at least one processor and at least one memory, the at least one memory storing instructions, which when executed by the at least one processor cause the apparatus to at least perform: receiving one or more permissions for reporting user equipment-related events of a first user equipment to one or more monitoring entities; as well as The one or more permissions are sent to a user data management function of the communication network. 14 . The apparatus of claim 13 , wherein the one or more permissions for reporting user equipment related events of the first user equipment are received from the first user equipment.

15. A method of a user equipment, the method comprising: generating a message comprising: one or more permissions for reporting user equipment related events to one or more monitoring entities; and The message is caused to be sent to one or more controlling network entities.

16. The method of claim 15, wherein the one or more permissions include: A shared permission for reporting two or more different types of events related to a user's device.

17. The method according to claim 15, wherein the user equipment related event comprises: Two or more different types of user device-related events associated with corresponding permissions.

18. The method of claim 15, wherein the one or more permissions include at least two different permissions, and wherein sending includes: The at least two permissions are sent to different monitoring entities of the one or more monitoring entities.

19. The method of claim 15, wherein the one or more permissions are used by one or more of the one or more control network entities to control whether the one or more of the one or more control network entities are allowed to provide the user equipment-related events to the one or more control network entities.

20. The method of claim 15, wherein the message further comprises: A time period associated with one or more of the one or more permissions during which the one or more permissions are valid.

21. The method of claim 15, wherein the message comprises a registration request.

22. The method of claim 15, further comprising: determining that one or more permissions for reporting events related to a user device have changed; as well as A further message to be generated is sent to the one or more controlling network entities, the further message having information about the changed one or more permissions for reporting user equipment related events.

23. The method of claim 15, wherein the one or more user equipment related events include one or more of the following: One or more connection loss events; one or more reachabilities of the user equipment event; one or more locations of the user equipment event; Subscribe to one or more changes in permanent identifier-permanent device identifier association events; one or more roaming status events; one or more communication failure events; one or more availability following a downlink data notification failure event; One or more protocol data unit session state monitoring authority events; one or more numbers of user devices present in the relevant geographic area; One or more core network type change events; one or more downlink data delivery status events; one or more user equipment reachability for a short message service delivery event; one or more memories of the user equipment available for short message service events; one or more numbers of registered user device events; one or more established protocol data unit session events; one or more area of ​​interest events; One or more group membership list change events; or One or more group maximum bitrate events.

24. A method of a communication network, the method comprising: receiving one or more permissions for reporting user equipment-related events of a first user equipment to one or more monitoring entities; as well as The one or more permissions are stored in association with data related to the first user device.

25. The method according to claim 24, further comprising: receiving a request, the request being a request for notification of one or more user device-related events for the first user device sent by one of the one or more monitoring entities, and determining whether the request for notification of one or more user device-related events for the first user device is authorized based on the one or more permissions.

26. The method of claim 25, wherein the request is received from the one monitoring entity via a device providing a network opening function.

27. A method of a communication network, comprising: receiving one or more permissions for reporting user equipment related events of a first subscriber user equipment to one or more monitoring entities; as well as The one or more permissions are sent to a subscriber data management function of the communication network.

28. The method of claim 27, wherein the one or more permissions for reporting user equipment related events of the first user equipment are received from the first user equipment.

29. A computer-readable medium comprising instructions which, when executed by at least one processor of a user device, cause the user device to perform any one of claims 15 to 23.

30. A computer-readable medium comprising instructions which, when executed by at least one processor of a device, cause the device to perform any one of claims 24 to 28.

31. A computer program, the computer readable medium comprising instructions, wherein when the computer program is executed by at least one processor of a user device, the user device is caused to perform any one of claims 15 to 23.

32. A computer program, the computer readable medium comprising instructions, wherein when the computer program is executed by at least one processor of a device, the device is caused to perform any one of claims 24 to 28.

Images