Group management method for group event monitoring and apparatus therefor

Abstract

The present disclosure can be applied to intelligent services (e.g., smart homes, smart buildings, smart cities, smart cars, connected cars, healthcare, digital education, retail, security and safety-related services) based on 5G communication technology and IoT-related technology. The present disclosure discloses a Group Management method that enables adding / deleting / replacing group members in a Group-based Event Monitoring method.

Description

[Technical Field]

[0001] The present disclosure relates to a communication system and to a group management method that enables adding / deleting / replacing group members in a group-based event monitoring method. [Background technology]

[0002] To meet the increasing demand for wireless data traffic since the commercialization of 4G (4th generation) communication systems, efforts are underway to develop improved 5G (5th generation) or pre-5G communication systems. For this reason, 5G or pre-5G communication systems are referred to as beyond-4G network (Beyond 4G Network) communication systems or post-LTE (Long Term Evolution) systems. To achieve high data transmission rates, 5G communication systems are being considered for implementation in ultra-high frequency (mmWave) bands (e.g., 60 GHz). To mitigate propagation path loss and increase transmission distance in ultra-high frequency bands, beamforming, massive multiple-input multiple-output (MM-IMO), full-dimensional MIMO (FD-MIMO), array antennas, analog beamforming, and large-scale antenna technologies are being discussed for 5G communication systems. Furthermore, to improve the system's network, technological developments are being carried out in the 5G communication system, such as advanced small cells, cloud radio access networks (cloud RAN), ultra-dense networks, device-to-device communication (D2D communication), wireless backhaul, moving networks, cooperative communication, CoMP (Coordinated Multi-Points), and interference cancellation.In addition, 5G systems are being developed with advanced coding modulation (ACM) methods such as FQAM (Hybrid Frequency Shift Keying and Quadrature Amplitude Modulation) and SWSC (Sliding Window Superposition Coding), as well as advanced connection technologies such as FBMC (Filter Bank Multi Carrier), NOMA (Non-Orthogonal Multiple Access), and SCMA (Sparse Code Multiple Access).

[0003] Meanwhile, the Internet is evolving from a human-centered network where humans generate and consume information to an IoT (Internet of Things) network where information is exchanged and processed among distributed components such as objects. The Internet of Everything (IoE) technology, which combines big data processing technology through connections to cloud servers and other devices, is also emerging. To realize the IoT, technological elements such as sensing technology, wired and wireless communication and network infrastructure, service interface technology, and security technology are required. In recent years, research has focused on sensor networks, M2M (Machine to Machine), and MTC (Machine Type Communication) for connecting things. The IoT environment collects and analyzes data generated by connected objects, enabling the provision of intelligent IT (Internet Technology) services that create new value in people's lives. Through the convergence and integration of existing IT (information technology) technologies and various industries, the IoT can be applied to areas such as smart homes, smart buildings, smart cities, smart or connected cars, smart grids, healthcare, smart home appliances, and advanced medical services.

[0004] As a result, various attempts are being made to apply 5G communication systems to IoT networks. For example, 5G communication technologies such as sensor networks, M2M (Machine to Machine), and MTC (Machine Type Communication) can be realized using techniques such as beamforming, MIMO, and array antennas. The application of cloud radio access networks (cloud RAN) as the aforementioned big data processing technology can also be seen as an example of the convergence of 5G and IoT technologies.

[0005] The above information is provided solely for background information to aid in the understanding of the present disclosure. No determination or assertion has been made as to whether any of the above content is applicable as prior art to the present disclosure. Summary of the Invention [Problem to be solved by the invention]

[0006] An object of the present invention is to solve at least the problems and drawbacks described above and to provide at least the advantages described below. Accordingly, one aspect of the present disclosure provides a group member UE (User Equipment) management method for adding, deleting, and replacing group member UEs in a group monitoring event.

[0007] Another object of the present invention is to provide a method and apparatus for efficiently providing services in a wireless communication system.

[0008] Additional aspects will be set forth in part in the description that follows, and in part will be obvious from the description or may be learned by practice of the embodiments presented. [Means for solving the problem]

[0009] According to an embodiment of the present disclosure, a method for adding, deleting, and replacing group members in a group-based event monitoring method is disclosed.

[0010] According to one embodiment of the present invention, a method for managing event monitoring for a group of terminals, performed by a first network function entity in a wireless communication system, is disclosed, the method including: receiving a monitoring request message for modification of a configured monitoring event from a second network function entity; the monitoring request message including a configuration identifier corresponding to the configured monitoring event and a terminal identifier indicating a group management operation for the group of terminals and a terminal associated with the operation; storing the configuration identifier, the operation, and the terminal identifier based on the monitoring request message; updating the configured monitoring event for the indicated terminal based on the operation; and transmitting information for modification of the configured monitoring event, including the configuration identifier and the terminal identifier, to a third network function entity connected to the indicated terminal, wherein the operation includes at least one of adding the terminal to the group or removing the terminal from the group.

[0011] In the method, the step of updating the configured monitoring event may be additionally based on the terminal identifier included in the monitoring request message.

[0012] The monitoring request message is generated based on a message from an application function entity associated with the configured monitoring event, and the message may include a T8 TLTRI (long term transaction reference ID) for identifying the configured monitoring event, the action, and the terminal identifier.

[0013] In the method, the set monitoring event is modified by the third network function entity based on the information, and if the operation is the addition, the monitoring event of the indicated terminal is monitored by the third network function entity, and if the operation is the deletion, the monitoring of the monitoring event of the indicated terminal can be stopped by the third network function entity.

[0014] If the operation is the addition, the update to the configured monitoring event may include: adding the indicated terminal to the group of terminals for the configured monitoring event; and monitoring the indicated terminal for the configured monitoring event.

[0015] If the action is deletion, the update for the configured monitoring event may include: deleting the indicated terminal in the group of terminals for the configured monitoring event; and suspending monitoring of the indicated terminal for the configured monitoring event.

[0016] In the method, the first network function entity may include at least one of an HSS (home subscriber server) or an UDM (unified data management), the second network function entity may include at least one of an SCEF (service capability exposure function) or an NEF (network exposure function), and the third network function entity may include at least one of an MME (mobile management entity), an SGSN (serving GPRS (general packet radio service) support node), an AMF (access and mobility management function), or an SMF (session management function).

[0017] According to another embodiment of the present invention, a method for managing event monitoring for a group of terminals, performed by a second network function entity in a wireless communication system, includes the steps of receiving a first monitoring request message for modifying a configured monitoring event from an application function entity associated with the configured monitoring event, the first monitoring request message including a first configuration identifier corresponding to the configured monitoring event and a terminal identifier indicating a group management operation for the group of terminals and a terminal associated with the operation, and transmitting a second monitoring request message based on the first monitoring request message from the first network function entity; a monitoring request message including a second configuration identifier corresponding to the configured monitoring event, the operation, and the terminal identifier, the second configuration identifier, the operation, and the terminal identifier being stored in the first network function entity based on the first monitoring request message, the configured monitoring event being updated for the indicated terminal based on the operation, information regarding the modification of the configured monitoring event being transmitted from the first network function entity to a third network function entity associated with the indicated terminal based on the second monitoring request message, the information including the second configuration identifier and the terminal identifier, and the operation including adding the terminal to the group or removing the terminal from the group.

[0018] According to another embodiment of the present invention, a first network function entity for managing event monitoring for a group of terminals in a wireless communication system may be disclosed, comprising: a transceiver unit; and a controller configured to receive from a second network function entity a monitoring request message for modification of a configured monitoring event, the monitoring request message including a configuration identifier corresponding to the configured monitoring event, a group management operation for the group of terminals and a terminal identifier indicating a terminal associated with the operation, store the configuration identifier, the operation, and the terminal identifier based on the monitoring request message, update the configured monitoring event for the indicated terminal based on the operation, and transmit information for modification of the configured monitoring event, including the configuration identifier and the terminal identifier, to a third network function entity connected to the indicated terminal, wherein the operation includes at least one of adding the terminal to the group or removing the terminal from the group.

[0019] According to another embodiment of the present invention, a second network function entity for managing event monitoring for a group of terminals in a wireless communication system includes a transceiver unit and receives, from an application function entity associated with a configured monitoring event, a first monitoring request message for modifying the configured monitoring event, the first monitoring request message including a first configuration identifier corresponding to the configured monitoring event and a terminal identifier indicating a group management operation for the group of terminals and a terminal associated with the operation, and transmits a second monitoring request message based on the first monitoring request message in the first network function entity. a control unit configured to configure the second monitoring request message, wherein the second monitoring request message includes a second configuration identifier corresponding to the configured monitoring event, the operation, and the terminal identifier, the configured monitoring event is updated for the indicated terminal based on the operation, information regarding the modification of the configured monitoring event is transmitted from the first network function entity to a third network function entity associated with the indicated terminal based on the second monitoring request message, the information includes the second configuration identifier and the terminal identifier, and the operation includes adding the terminal to the group or removing the terminal from the group. [Effects of the Invention]

[0020] In order to add, delete, or replace a UE in an existing Group Monitoring Event, the configured Monitoring Event configuration must be canceled and a new Monitoring Event must be configured. However, through this disclosure, it is possible to efficiently add, delete, and replace Group member UEs without canceling the existing configuration.

[0021] The disclosed embodiments provide an apparatus and method that can efficiently provide services in a wireless communication system.

[0022] Other aspects, advantages, and essential features of the present disclosure will become apparent to those skilled in the art from the following description, which, taken in conjunction with the accompanying drawings, discloses various embodiments of the present disclosure. [Brief explanation of the drawings]

[0023] Other aspects, features, and advantages of particular embodiments of the present disclosure will become more apparent from the description provided in conjunction with the accompanying drawings. [Figure 1] 1 illustrates a wireless communication system according to various implementations of the present disclosure. [Figure 2] 1 is a diagram showing a procedure for setting up a Monitoring Event Configuration via an HSS. [Figure 3] 1 is a diagram showing a procedure for setting up a Monitoring Event Configuration in an MME / SGSN. [Figure 4] 1 is a diagram illustrating the structure of a network entity (including NF and NF instance) according to an embodiment of the present disclosure. [Figure 5] 1 is a diagram illustrating a structure of a terminal according to an embodiment of the present disclosure. [Figure 6] 1 is a diagram illustrating the structure of a base station according to one embodiment of the present disclosure, wherein like reference numerals are used throughout the drawings to denote like elements. DETAILED DESCRIPTION OF THE INVENTION

[0024] The following description, which refers to the accompanying drawings, is provided to facilitate a comprehensive understanding of various embodiments of the present disclosure, as defined by the claims and their equivalents. Although various specific details are included to facilitate such understanding, they are considered to be merely exemplary. Therefore, it will be obvious to those skilled in the art that various changes and modifications to the various embodiments described in the present disclosure can be made without departing from the scope and spirit of the present disclosure. Furthermore, descriptions of well-known functions and configurations may be omitted for the sake of clarity and conciseness.

[0025] The terms and phrases used in the following description and claims are not limited to their literary meanings, but should be used to allow a clear and consistent understanding of the present disclosure. Therefore, it will be apparent to those of ordinary skill in the art that the following description of various embodiments of the present disclosure is provided for illustrative purposes only and is not intended to limit the present disclosure as defined by the appended claims and their equivalents.

[0026] The singular forms "a," "an," and "the" may be understood to include plural referents unless the context clearly dictates otherwise. Thus, for example, a reference to a "component surface" may include a reference to one or more of such surfaces.

[0027] In describing the embodiments, technical details that are well known in the technical field to which the present disclosure pertains and are not directly related to the present disclosure will be omitted in order to clarify and more clearly convey the gist of the present disclosure by omitting unnecessary details.

[0028] For the same reasons, some components in the accompanying drawings are exaggerated, omitted, or illustrated schematically, and the size of each component does not necessarily reflect the actual size. The same or corresponding components in each drawing are designated by the same reference numerals.

[0029] The advantages and features of the present disclosure, and methods for achieving them, will become clearer with reference to the following detailed description of the embodiments along with the accompanying drawings. However, the present disclosure is not limited to the embodiments disclosed below, and may be embodied in various different forms. The embodiments are provided solely to complete the disclosure and fully convey the scope of the disclosure to those skilled in the art. The present disclosure is defined only by the scope of the claims. The same reference numerals refer to the same elements throughout the specification.

[0030] It will be understood that the combination of each block of the process flowchart and the flowchart figures can be implemented by computer program instructions. These computer program instructions can be loaded onto a processor in a general-purpose computer, a special-purpose computer, or other programmable data processing device, such that the instructions, executed by the processor of the computer or other programmable data processing device, create means for performing the functions described in the flowchart blocks. These computer program instructions can also be stored in computer-usable or computer-readable memory that can direct the computer or other programmable data processing device to implement functions in a particular manner, such that the instructions stored in the computer-usable or computer-readable memory can produce an article of manufacture containing instruction means for performing the functions described in the flowchart blocks. Computer program instructions can also be loaded onto a computer or other programmable data processing device, such that a series of operational steps are performed on the computer or other programmable data processing device, creating a computer-implemented process, and the instructions that cause the computer or other programmable data processing device to provide the steps for performing the functions described in the flowchart blocks.

[0031] Also, each block may represent a module, segment, or portion of code that includes one or more executable instructions for performing a specified logical function. Also, it should be noted that in some alternative implementations, the functions described in the blocks may occur out of order. For example, two blocks shown adjacently may actually be performed substantially simultaneously, or the blocks may sometimes be performed in reverse order depending on the corresponding function.

[0032] The term "module" used in this embodiment refers to software or hardware components such as FPGAs (Field Programmable Gate Arrays) or ASICs (Application Specific Integrated Circuits), and the "module" may perform any function. However, the term "module" is not limited to software or hardware. The "module" may be configured to reside on an addressable storage medium or to implement one or more processors. Thus, by way of example, the term "module" includes components such as software components, object-oriented software components, class components, and task components, as well as processes, functions, attributes, procedures, subroutines, program code segments, drivers, firmware, microcode, circuits, data, databases, data structures, tables, arrays, and variables. The functions provided within the components and "modules" may be combined into fewer components and "modules" or further separated into additional components and "modules." Furthermore, the components and "modules" may be embodied to implement one or more CPUs within a device or a secure multimedia card.

[0033] Hereinafter, a base station (BS) is an entity that allocates resources to a terminal and may be at least one of a Node B, a Base Station (BS), an eNode B (eNB), a gNode B (gNB), a radio access unit (RAU), a base station controller, or a node on a network. A terminal may include a User Equipment (UE), a Mobile Station (MS), a cellular phone, a smartphone, a computer, or a multimedia system capable of performing communication functions. In addition, embodiments of the present disclosure may be applied to other communication systems having a similar technical background or channel configuration to the embodiments of the present disclosure described below. Furthermore, the embodiments of the present disclosure may be applied to other communication systems with some modifications within the scope of the present disclosure, as determined by a person skilled in the art.

[0034] In the following description, terms for identifying connection nodes, terms for designating network entities or network functions (NFs), terms for designating messages, terms for designating interfaces between network objects, terms for designating various identification information, etc. are exemplified for the convenience of description. Therefore, the present disclosure is not limited to the terms described below, and other terms for designating objects having equivalent technical meanings may be used.

[0035] For convenience of the following description, some terms and names defined in the 3GPP (registered trademark) (3rd generation partnership project) LTE (long term evolution) standard and / or the 3GPP NR (new radio) standard may be used, but the present disclosure is not limited to these terms and names and may be similarly applied to systems conforming to other standards.

[0036] In addition, terms for identifying connection nodes, terms for designating network objects (network entities), terms for designating network functions (NFs), terms for designating messages, terms for designating interfaces between network entities, and terms for designating various identification information used in the following description are exemplified for the convenience of explanation. In this disclosure, the terms network object and network entity may be used interchangeably. Therefore, the terms used in this disclosure are not limited to those used in the present disclosure, and other terms for designating objects having equivalent technical meanings may be used.

[0037] For convenience of explanation, entities exchanging information for connection control and state management will be collectively referred to as NF. NF may refer to, for example, at least one of an Access and Mobility Management Function (AMF) device, a Session Management Function (SMF) device, and a Unified Data Management (UDM) device. However, the embodiments of the present disclosure may also be applied to cases where NFs are actually embodied as instances (e.g., AMF Instance, SMF Instance, UDM Instance, etc.).

[0038] In the present disclosure, the term "instance" refers to a state in which a specific NF exists in the form of software code and is executable by a physical computer system, e.g., a specific computer system on a core network, to perform the functions of the NF by allocating physical and / or logical resources from the computer system. Therefore, an AMF instance, an SMF instance, and an UDM instance may refer to a state in which physical and / or logical resources are allocated and used for AMF, SMF, and UDM operations by a specific computer system on the core network, respectively. Consequently, when a physical AMF, SMF, or UDM device exists, an AMF instance, an SMF instance, or an UDM instance that is allocated and uses physical and / or logical resources for AMF, SMF, and UDM operations from a specific computer system on the network can perform the same operation. Therefore, in embodiments of the present invention, matters described in NFs (AMF, SMF, UPF, UDM, UDR, PCF, etc.) can be replaced with NF instances, or conversely, matters described in NF instances can be replaced with NFs and applied. Similarly, in embodiments of the present invention, matters described in a NW slice can be replaced with a NW slice instance, or conversely, matters described in a NW slice instance can be replaced with a NW slice and applied.

[0039] FIG. 1 illustrates a wireless communication system in accordance with various embodiments of the present disclosure.

[0040] FIG. 1 illustrates network entities based on an NR wireless communication system, but can be similarly understood by corresponding entities for an LTE wireless communication system.

[0041] 1, a base station (radio access node, RAN) 110 and a terminal (user equipment, UE) 120 are illustrated as some of the nodes that use a wireless channel in a wireless communication system. Although FIG. 1 illustrates only one base station 110 and one terminal 120, other base stations that are the same as or similar to the base station 110 may also be included. Also, FIG. 1 illustrates only a case where only one terminal 120 communicates within one base station 110. However, it is obvious that multiple terminals may actually communicate within one base station 110.

[0042] The base station 110 is a network infrastructure that provides wireless connectivity to the terminal 120. The base station 110 has coverage, which is defined as a geographical area determined based on the distance over which a signal can be transmitted (not shown in FIG. 1). The base station 110 may also be referred to as an "access point (AP)," "eNodeB (eNB)," "5G node (5th generation node)," "next generation NodeB (gNB)," "wireless point," "transmission / reception point (TRP)," or other terms having an equivalent technical meaning, in addition to a base station.

[0043] The terminal 120 is a device used by a user and communicates with the base station 110 via a wireless channel. In some cases, the terminal 120 may be operated without the user's involvement. For example, the terminal 120 may be a device that performs machine-type communication (MTC) and is not carried by the user. The terminal 120 illustrated in FIG. 1 may include at least one user-carried device and at least one MTC. The terminal 120 in FIG. 1 may be referred to as a "terminal," a "mobile station," a "subscriber station," a "remote terminal," a "wireless terminal," or a "user device," or other terms having equivalent technical meanings.

[0044] The AMF device 131 can be a network entity that manages wireless network access and mobility management for the terminal 120. The AMF device can correspond to an MME (Mobility Management Entity) in an LTE system. The SMF device 132 can be a network entity that manages packet data network connections for providing packet data to the terminal 120. The SMF device can correspond to an SGSN (Serving General Packet Radio Service (GPRS) Supporting Node) in an LTE system. The connection between the terminal 120 and the SMF 132 can be a PDU (protocol data unit) session.

[0045] The User Plane Function (UPF) device 133 can be a gateway or a network entity that acts as a gateway for transmitting packets transmitted and received by the terminal 120. The UPF 133 is connected to a data network (DN) 140 connected to the Internet and can provide a path for data transmission and reception between the terminal 120 and the DN 140. Therefore, the UPF 133 can route data that must be transmitted over the Internet among packets transmitted by the terminal 120 to the Internet data network.

[0046] The network slice selection function (NSSF) device 134 can be a network entity that performs the network selection operations described in this disclosure, such as selecting a network slice.

[0047] An AUSF (Authentication Server Function) device 151 can be a device (network entity) that provides services for subscriber authentication processing.

[0048] The Network Exposure Function (NEF) device 152 can access information that manages the terminal 120 in a 5G network, and can be a network entity that can subscribe to mobility management events for the terminal, subscribe to session management events for the terminal, request session-related information, set charging information for the terminal, request a PDU session policy change for the terminal, and transmit small data to the terminal. The NEF device can correspond to the Service Capability Exposure Function (SCEF) of the LTE system.

[0049] The Network Repository Function (NRF) device 153 can be an NF (network entity) that stores state information of NFs and has the function of processing requests from other NFs to search for connectable NFs.

[0050] A Policy and Charging Function (PCF) device 154 can be a network entity that applies a mobile communication operator's service policy, charging policy, and policy for a PDU session to the terminal 120.

[0051] A Unified Data Management (UDM) device 155 can be a network entity that stores information about subscribers and / or terminals 120. The UDM can correspond to a Home Subscriber Server (HSS) in an LTE system.

[0052] The Application Function (AF) device 156 can be a network entity (NF) that has the function of providing services to users in conjunction with a mobile communication network. The AF can correspond to the Service Capability Server / Application Server (SCS / AS) of the LTE system.

[0053] The Service Communication Proxy (SCP) device 157 is an NF (network entity) that provides functions such as NF discovery for communication between NFs and message transmission between NFs. The SCP 157 can operate in an integrated form with the NRF 153 at the operator's discretion. In this case, the SCP 157 can include the functions of the NRF 153, or conversely, the NRF 153 can include the functions of the SCP 157.

[0054] The AMF device 131, SMF device 132, UPF device 133, NSSF device 134, AUSF device 151, NEF device 152, NRF device 153, PCF device 154, UDM device 155, AF device 156, and SCP device 157 described above may be implemented in the form of software or firmware operated by at least one or more devices and / or systems. Furthermore, the devices 131, 132, 133, 134, 151, 152, 153, 154, 155, 156, and 157 may also be implemented in the form of hardware if necessary. In the following description, the term "device" will be omitted for convenience of explanation. For example, the AMF device 131 will be described as AMF 131, and the SMF device 132 will be described as SMF 132.

[0055] Meanwhile, in Figure 1, the symbols between the connecting lines between each network entity, UE 120, and RAN 110 may represent the interfaces of each entity. For example, this may mean that an N1 interface is used between UE 120 and AMF 131, an N2 interface is used between RAN 110 and AMF 131, and an N3 interface is used between RAN 110 and UPF 133. Similarly, an N4 interface may be used between SMF 132 and UPF 133, an N9 interface may be used between or within UPF 133, and an N6 interface may be used between UPF 133 and DN 140.

[0056] Hereinafter, a group management method that enables adding, deleting, and / or replacing group members within a group for group-based event monitoring will be disclosed. Although each embodiment in this disclosure is described based on an LTE system, each embodiment can also be applied to an NR system.

[0057] In the following description, the SCS / AS (Service Capability Server / Application Server) of the LTE system can correspond to the AF of the NR system. Similarly, the SCEF (Service Capabilities Exposure Function) of the LTE system can correspond to the NEF of the NR system, the HSS of the LTE system can correspond to the UDM of the NR system, and the MME / SGSN of the LTE system can correspond to the AMF and SMF of the NR system.

[0058] Figure 2 shows the procedure for setting up Monitoring Event Configuration via HSS. The flowchart is based on the LTE system, but as mentioned above, it can also be applied to the 5G system. The SCS / AS (Service Capability Server / Application Server) can be represented by the AF, the SCEF by the NEF, the HSS by the UDM, and the MME / SGSN by the AMF and SMF.

[0059] Referring to Figure 2, in step 1, the SCS / AS (or AF) can send a Monitoring Request message to the SCEF (or NEF) to request monitoring for a specific event. The message can include the following parameters: External Identifier or MSISDN (Mobile Station International Subscriber Directory Number) or External Group ID, SCS / AS Identifier, Monitoring Type, Maximum Number of Reports, Monitoring Duration, T8 Destination Address, TLTRI (T8 Long Term Transaction Reference ID) for Deletion or Group Management, Group Reporting Guard Time, MTC Provider Information, Operation of Group Management (Insertion (Addition), Deletion, or Replacement), and List of Impacted UEs (External Identifiers or MSISDNs).

[0060] The following is a description of each of the above parameters:

[0061] The External Identifier or MSISDN is a terminal ID that identifies the terminal outside the network.

[0062] The External Group ID is a terminal group ID that identifies a group of terminals outside the network.

[0063] SCS / AS Identifier is the ID of the SCS / AS server.

[0064] The Monitoring Type can indicate the type of specific Monitoring Event being requested.

[0065] Maximum Number of Reports allows you to indicate the maximum number of event reports that can be generated.

[0066] Monitoring Duration can indicate how long the requested monitoring event will last.

[0067] T8 Destination Address is the address information directed to the SCS / AS.

[0068] TLTRI (T8 Long Term Transaction Reference ID) is an ID assigned by SCEF to identify a Monitoring Request. If an SCS / AS wants to delete an existing Monitoring Event or change the configuration of an existing Monitoring Event, it must include the TLTRI assigned to the existing Monitoring Event in the Request message.

[0069] Group Reporting Guard Time is the time to wait until UE reports are collected in order to transmit the Monitoring Event report value of each UE at once when performing Group-Based Monitoring.

[0070] The MTC Provider Information is included by the SCEF as an ID to identify the MTC Service Provider and MTC Application.

[0071] In the case of Group Event Monitoring, an operation of group management (addition, deletion, or replacement) is requested by the SCS / AS when it is necessary to add, delete, or replace a terminal group member UE.

[0072] The List of Impacted UEs (External Identifiers or MSISDNs) can indicate the list of UEs that are added, deleted, or replaced by the Group Management Operation.

[0073] The SCEF that receives a Monitoring Request can assign a TLTRI to the Request.

[0074] When the SCS / AS attempts to set a Monitoring Event for a UE group, the request message may include an External Group Identifier and a Group Reporting Guard Time.

[0075] At stage 2, the SCEF may store the following information: SCS / AS Identifier, T8 Destination Address, Monitoring Duration, Maximum Number of Reports and Group Reporting Guard Time.

[0076] The SCEF can store the TLTRI and assign a SCEF Reference ID for the TLTRI.

[0077] The SCEF Reference ID is assigned to a Monitoring Event by the SCEF and can be used to identify the Monitoring Event when reporting or deleting the Monitoring Event. The SCEF Reference ID can also be used to search for Monitoring Event-related information within the SCEF. The SCEF Reference ID is stored in the Home Subscriber Server (HSS), Mobility Management Entity (MME), Serving GPRS Support Node (SGSN), and InterWorking Service Capabilities Exposure Function (IWK-SCEF). If a related TLTRI is received from the SCS / AS for deletion of an existing Monitoring Event or Group Management, the SCEF context is searched to find the related SCEF Reference ID. The SCEF Reference ID is an ID used by the SCEF to identify the Monitoring Event and its configuration, so it can be referred to differently in the NR system.

[0078] In step 3, the SCEF can send a Monitoring Request message to the HSS (or UDM) containing the following information: External Identifier or MSISDN or External Group Identifier, SCEF ID, SCEF Reference ID, Monitoring Type, Maximum Number of Reports, Monitoring Duration, SCEF Reference ID for Deletion or Group Management, Chargeable Party Identifier, Group Reporting Guard Time, MTC Provider Information, Operation of Group Management (Addition, Deletion, or Replacement), List of Impacted UEs (External Identifiers or MSISDNs).

[0079] In step 4, the HSS can check the Monitoring Request message for errors. The HSS can store the following information: SCEF Reference ID, the SCEF ID, Maximum Number of Reports, Monitoring Duration and the SCEF Reference ID for Deletion or Group Management as provided by the SCEF, Operation of Group Management (Addition, Deletion, or Replacement), List of Impacted UEs (External Identifiers or MSISDNs).

[0080] In step 4a, if the request is group-based, i.e., if an External Group Identifier is received, the HSS may send a Monitoring Response message to the SCEF with the following information: SCEF Reference ID, Number of UEs, Cause. If a monitoring event deletion request is received, the HSS may delete the monitoring event configuration corresponding to the SCEF Reference ID.

[0081] If a Group Management request is received, the HSS can update the monitoring event configuration and external group identifier corresponding to the SCEF Reference ID based on the Operation of Group Management (Addition, Deletion, or Replacement) and List of Impacted UEs (External Identifiers or MSISDNs) parameters. In the case of an Addition operation, the Impacted UE is added to the Monitoring Event, in the case of a Deletion operation, the Impacted UE is deleted from the Monitoring Event, and in the case of a Replacement operation, the existing UE can be replaced with the Impacted UE. If you want to delete some existing UEs and delete new UEs, you can also perform two Operations of Group Management in one Monitoring Request message.

[0082] In step 4b, the SCEF may send a Monitoring Response message to the SCS / AS including the TLTRI and Cause value. The Cause value may indicate information about the progress of the Group processing request.

[0083] In step 5, if a specific Monitoring Type or Monitoring Event must be performed by the MME / SGSN (or AMF / SMF), the HSS can send an Insert Subscriber Data Request message to the MME / SGSN for each UE. In particular, in the case of Group Event Monitoring, a separate message can be sent for each group member UE to all MME / SGSN(s) serving each group member UE. The sent message can include the following information: Monitoring Type, SCEF ID, SCEF Reference ID, Maximum Number of Reports, Monitoring Duration, SCEF Reference ID for Deletion, and Chargeable Party Identifier.

[0084] If a SCEF Reference ID for a Group Management request is received, an Insert Subscriber Data Request message can be sent based on the Operation of Group Management (Addition, Deletion, or Replacement) and the List of Impacted UEs (External Identifiers or MSISDNs). In the case of an addition operation, an Insert Subscriber Data Request message (without the SCEF Reference ID for Deletion) is sent to the MME / SGSN serving the Impacted UE, and in the case of a deletion operation, an Insert Subscriber Data Request message can be sent with the SCEF Reference ID for Deletion included to the MME / SGSN serving the Impacted UE. In the case of a replacement operation, an Insert Subscriber Data Request message can be sent with the SCEF Reference ID for Deletion included to the MME / SGSN serving the existing UE, and an Insert Subscriber Data Request message (without the SCEF Reference ID for Deletion) can be sent to the MME / SGSN serving the Impacted UE.

[0085] In step 6, the MME / SGSN can store the received parameters and perform the requested monitoring event. If a SCEF Reference ID for deletion is received, the MME / SGSN can delete the monitoring configuration.

[0086] In step 7, if the monitoring configuration is successful, the MME / SGSN can send an Insert Subscriber Data Answer (Cause) message to the HSS. If a Monitoring Event Report is enabled, this report can be included in the Subscriber Data Answer message and sent.

[0087] In step 8, the HSS can send a Monitoring Response / Indication message to the SCEF. This message can include the following parameters: SCEF Reference ID, Cause, and Monitoring Event Report. The HSS can delete the monitoring event configuration identified by the SCEF Reference ID.

[0088] In step 9a, the SCEF may send a Monitoring Response message to the SCS / AS, which may include a Cause value and a Monitoring Event Report.

[0089] In step 9b, for the Group UE, the SCEF may send a Monitor Indication message to the SCS / AS. This message may include a TLTRI, a Cause, and a Monitoring Event Report.

[0090] In step 9c, the SCS / AS may send a Monitoring Indication Response (Cause) message to the SCEF.

[0091] Figure 3 shows a procedure for setting up Monitoring Event Configuration in MME / SGSN. This procedure is based on the LTE system, but as mentioned above, it can also be applied to the 5G system. The SCS / AS can be handled by the AF, the SCEF by the NEF, the HSS by the UDM, and the MME / SGSN by the AMF and SMF.

[0092] Referring to Figure 3, in step 1, the SCS / AS (Service Capability Server / Application Server) can send a Monitoring Request message to the SCEF (Service Capabilities Exposure Function) to request monitoring for a specific event. The message can include the following parameters: External Identifier or MSISDN or External Group ID, SCS / AS Identifier, Monitoring Type, Maximum Number of Reports, T8 Destination Address, TLTRI for Deletion or Group Management, Group Reporting Guard Time, Operation of Group Management (Addition, Deletion, or Replacement), and List of Impacted UEs (External Identifiers or MSISDNs).

[0093] The following is an explanation of each of the above parameters. External Identifier or MSISDN is a terminal ID that identifies a terminal outside the network. External Group ID is a terminal group ID that identifies a group of terminals outside the network. SCS / AS Identifier is the ID of the SCS / AS server. Monitoring Type may indicate the type of specific monitoring event being requested. Maximum Number of Reports may indicate the maximum number of event reports to be generated. Monitoring Duration may indicate the duration of the requested monitoring event. T8 Destination Address is address information directed to the SCS / AS. TLTRI (T8 Long Term Transaction Reference ID) is an ID assigned by the SCEF to identify the Monitoring Request. If the SCS / AS wants to delete an existing configured monitoring event or change the settings of an existing monitoring event, it must include the TLTRI assigned to the existing monitoring event in the request message. Group Reporting Guard Time is the time to wait until reports from each UE are collected in order to send the Monitoring Event report value of each UE at once when performing Group-Based Monitoring. Operation of Group Management (Addition, Deletion, or Replacement) is requested by the SCS / AS when addition, deletion, or replacement of a terminal group member UE is required in the case of Group Event Monitoring. List of Impacted UEs (External Identifiers or MSISDNs) can indicate the list of UEs to be added, deleted, or replaced by the Group Management Operation.

[0094] The SCEF that receives the Monitoring Request can assign a TLTRI to the request. When the SCS / AS wants to set a Monitoring Event for a UE group, the request message can include an External Group Identifier and a Group Reporting Guard Time.

[0095] In step 2, the SCEF can store the following information: SCS / AS Identifier, T8 Destination Address, Monitoring Duration, Maximum Number of Reports, and Group Reporting Guard Time. The SCEF can store the TLTRI and assign a SCEF Reference ID for the TLTRI. The SCEF Reference ID is assigned to a Monitoring Event by the SCEF and can be used to identify the Monitoring Event when reporting or deleting a Monitoring Event. The SCEF Reference ID can also be used to search for Monitoring Event-related information in the SCEF. The SCEF Reference ID is stored in the Home Subscriber Server (HSS), Mobility Management Entity (MME), Serving GPRS Support Node (SGSN), and IWK-SCEF. If the SCEF receives a related TLTRI from the SCS / AS for deletion or Group Management of an existing Monitoring Event, it searches the corresponding SCEF context to find the related SCEF Reference ID. If External Group Identifier(s) are included in step 1, it performs steps 2a / 2b.

[0096] In step 2a, the SCEF can send an External Group ID Resolution Request (External Group Identifier(s)) message to the HSS. If a Group Management request is received, the SCEF also sends the following information: TLTRI for Deletion or Group Management, Operation of Group Management (Addition, Deletion, or Replacement), List of Impacted UEs (External Identifiers or MSISDNs).

[0097] In step 2b, the HSS can convert the External Group Identifier(s) into IMSI-Group Identifier(s) and send the converted values ​​to the SCEF in an External Group ID Resolution Response message.

[0098] If a Group Management request is received, the HSS can update the External Group Identifier based on the Operation of Group Management (Addition, Deletion, or Replacement) and List of Impacted UEs (External Identifiers or MSISDNs) parameters. In the case of an Addition operation, the Impacted UE can be added to the External Group Identifier, in the case of a Deletion operation, the Impacted UE can be deleted from the External Group Identifier, and in the case of a Replacement operation, the Impacted UE can replace the existing UE. The HSS can send the existing IMSI-Group Identifier(s) and the updated IMSI-Group Identifier(s) in an External Group ID Resolution Response message to the SCEF.

[0099] In step 3, the SCEF can send a Monitoring Request message to the MME / SGSN for each UE. In particular, in the case of Group Event Monitoring, a separate message can be sent for each group member UE to all MME / SGSN(s) serving each group member UE. The message sent can include the following information: Monitoring Type, SCEF ID, SCEF Reference ID, Maximum Number of Reports, Monitoring Duration, and SCEF Reference ID for Deletion.

[0100] If a SCEF Reference ID for a Group Management request is received, a Monitoring Request message can be sent based on the Operation of Group Management (Addition, Deletion, or Replacement) and the List of Impacted UEs (External Identifiers or MSISDNs). In the case of an Addition operation, a Monitoring Request message (without the SCEF Reference ID for Deletion) is sent to the MME / SGSN serving the Impacted UE, and in the case of a Deletion operation, a Monitoring Request message including the SCEF Reference ID for Deletion can be sent to the MME / SGSN serving the Impacted UE. In the case of a Replacement operation, a Monitoring Request message including the SCEF Reference ID for Deletion can be sent to the MME / SGSN serving the existing UE, and a Monitoring Request message (without the SCEF Reference ID for Deletion) can be sent to the MME / SGSN serving the Impacted UE.

[0101] In step 4, the MME / SGSN can store the received parameters and perform the requested monitoring event. If a SCEF Reference ID for deletion is received, the MME / SGSN can delete the monitoring configuration.

[0102] In step 5, the MME / SGSN may send a Monitoring Response (SCEF Reference ID, Cause, Monitoring Event Report) message to the SCEF.

[0103] In step 6, the SCEF can send a Monitoring Response (TLTRI, Cause, Monitoring Event Report) message to the SCS / AS.

[0104] FIG. 4 is a diagram illustrating the structure of a network entity (including an NF and an NF instance) according to one embodiment of the present disclosure.

[0105] The network entity shown in Figure 4 may represent at least one of the MME, SGSN, HSS, SCEF, SCS / AS, AMF, SMF, UDM, NEF, and AF, and is not limited to a specific network entity. In addition, the network entity may be provided in the form of an instance. When provided as an instance, the network entity exists in the form of software code and may represent a state in which physical and / or logical resources are allocated from a computer system to perform the function of an NF in a physical computer system, for example, a specific computer system existing on a core network, and is executable. Therefore, the structure of Figure 4 may represent a physical division or a logical division.

[0106] Referring to FIG. 4, the network entity (NF) may be composed of a transceiver 410, a memory 420, and a controller 430. The transceiver 410, the controller 430, and the memory 420 may operate according to the communication method of the network entity. However, the components of the network entity are not limited to the above examples. For example, the network entity may include more or fewer components than those described above. Furthermore, the transceiver 410, the controller 430, and the memory 420 may be implemented in the form of a single chip. Furthermore, the controller 430 may include one or more processors.

[0107] The transceiver 410, commonly referred to as the receiver of a network entity and the transmitter of a network entity, can transmit and receive signals to and from a base station, a terminal, or another network entity. The signals transmitted and received to and from a base station, a terminal, or another network entity may include control information and data. To this end, the transceiver 410 may include an RF transmitter that up-converts and amplifies the frequency of a transmitted signal, an RF receiver that low-noise amplifies a received signal, and down-converts the frequency. However, this is only one embodiment of the transceiver 410, and the components of the transceiver 410 are not limited to an RF transmitter and an RF receiver. In addition, the receiver serves as an interface for transmitting and receiving data, and can transmit and receive data not only via wireless signals but also via wired connections via a backhaul network.

[0108] The transceiver 410 can receive a signal through a wireless channel, output the signal to the controller 430, and transmit the signal output from the controller 430 through the wireless channel.

[0109] The memory 420 can store programs and data necessary for the operation of the NF. The memory 420 can also store control information or data included in signals acquired by the NF. The memory 420 can be configured as a storage medium such as a ROM, RAM, hard disk, CD-ROM, DVD, etc., or a combination of storage media. The memory 420 can also be configured as being included in the control unit 430, rather than being a separate unit.

[0110] The controller 430 may control a series of processes to operate the network entity according to the above-described embodiments of the present disclosure. For example, the controller 430 may receive control signals and data signals via the transceiver 410 and process the received control signals and data signals. The controller 430 may also transmit the processed control signals and data signals via the transceiver 410. There may be a plurality of controllers 430, and the controllers 430 may control the components of the NF by executing programs stored in the memory 420.

[0111] FIG. 5 is a diagram illustrating the structure of a terminal according to an embodiment of the present disclosure.

[0112] Referring to FIG. 5, the terminal may be composed of a transceiver 510, a memory 520, and a control unit 530. The transceiver 510, the control unit 530, and the memory 520 of the terminal may operate according to the above-described terminal communication method. However, the components of the terminal are not limited to the above-described examples. For example, the terminal may include more or fewer components than those described above. Furthermore, the transceiver 510, the control unit 530, and the memory 520 may be embodied in the form of a single chip. Furthermore, the processor 530 may include one or more processors.

[0113] The transceiver 510, which is commonly referred to as the receiver and transmitter of a terminal, can transmit and receive signals to and from a base station, a NF, or another terminal. Signals transmitted and received from a base station, a NF, or another terminal may include control information and data. To this end, the transceiver 510 may be configured with an RF transmitter that up-converts and amplifies the frequency of a signal to be transmitted, and an RF receiver that low-noise amplifies and down-converts the frequency of a received signal. However, this is only one embodiment of the transceiver 510, and the components of the transceiver 510 are not limited to an RF transmitter and an RF receiver.

[0114] In addition, the transceiver 510 can receive a signal through a wireless channel, output the signal to the controller 530, and transmit the signal output from the controller 530 through the wireless channel.

[0115] The memory 520 can store programs and data necessary for the operation of the terminal. The memory 520 can also store control information or data included in signals acquired by the terminal. The memory 520 can be configured as a storage medium such as a ROM, a RAM, a hard disk, a CD-ROM, a DVD, etc., or a combination of storage media. The memory 520 can also be configured as being included in the control unit 530, rather than being a separate device.

[0116] The control unit 530 can control a series of processes to operate the terminal according to the above-described embodiments of the present disclosure. For example, the control unit 530 can receive control signals and data signals via the transceiver unit 510 and process the received control signals and data signals. The control unit 530 can also transmit the processed control signals and data signals via the transceiver unit 510. There may be a plurality of control units 530, and the control units 530 can control the components of the terminal by executing programs stored in the memory 520.

[0117] FIG. 6 is a diagram illustrating the structure of a base station according to an embodiment of the present disclosure.

[0118] Referring to FIG. 6, the base station may be comprised of a transceiver unit 610, a memory 620, and a control unit 630. The transceiver unit 610, the control unit 630, and the memory 620 of the base station may operate according to the above-described base station communication method. However, the components of the base station are not limited to the above-described examples. For example, a terminal may include more or fewer components than the above-described components. Furthermore, the transceiver unit 610, the control unit 630, and the memory 620 may be embodied in the form of a single chip. Furthermore, the control unit 630 may include one or more processors.

[0119] The transceiver 610, commonly referred to as the receiver of a base station and the transmitter of a base station, can transmit and receive signals to and from a mobile station, a network facility (NF), or another base station. Signals transmitted and received from and received by a mobile station, a network facility (NF), or another base station may include control information and data. To this end, the transceiver 610 may include an RF transmitter that up-converts and amplifies the frequency of a signal to be transmitted, and an RF receiver that low-noise amplifies and down-converts the frequency of a received signal. However, this is only one embodiment of the transceiver 610, and the components of the transceiver 610 are not limited to an RF transmitter and an RF receiver.

[0120] The transceiver 610 can receive a signal via a wireless channel and output it to the controller 630, and can transmit the signal output from the controller 630 via a wireless channel.

[0121] The memory 620 can store programs and data necessary for the operation of the base station. The memory 620 can also store control information or data included in signals acquired by the base station. The memory 620 can be configured as a storage medium such as a ROM, RAM, hard disk, CD-ROM, DVD, etc., or a combination of storage media. The memory 620 can also be configured as being included in the control unit 530, rather than being a separate unit.

[0122] The control unit 630 can control a series of processes to operate the base station according to the above-described embodiments of the present disclosure. For example, the control unit 630 can receive control signals and data signals via the transceiver 610 and process the received control signals and data signals. The control unit 630 can also transmit the processed control signals and data signals via the transceiver 610. There can be multiple control units 630, and the control units 630 can control the components of the base station by executing programs stored in the memory 620.

[0123] The methods according to the embodiments described in the claims or specification of the present disclosure may be implemented in the form of hardware, software, or a combination of hardware and software.

[0124] In the case of a software implementation, a computer-readable storage medium may be provided that stores one or more programs (software modules). The one or more programs stored on the computer-readable storage medium are configured for execution by one or more processors in an electronic device. The one or more programs include instructions that cause the electronic device to perform a method according to the embodiments described in the claims or specification of the present disclosure.

[0125] Such programs (software modules, software) can be stored in random access memory, non-volatile memory including flash memory, read-only memory (ROM), electrically erasable programmable read-only memory (EEPROM), magnetic disc storage device, compact disc-ROM (CD-ROM), digital versatile discs (DVDs), or other forms of optical storage, magnetic cassette, or in memory configured from a combination of some or all of these. Also, each of the constituent memories may be included in plural.

[0126] The program may also be stored in an attachable storage device accessible via a communication network such as the Internet, an intranet, a local area network (LAN), a wide area network (WAN), or a storage area network (SAN), or a combination thereof. Such a storage device may be connected to a device that performs an embodiment of the present disclosure via an external port. Alternatively, a separate storage device on the communication network may be connected to a device that performs an embodiment of the present disclosure.

[0127] Meanwhile, the embodiments of the present disclosure disclosed in this specification and drawings are presented as specific examples to facilitate the description of the present disclosure and to facilitate understanding of the present disclosure, and are not intended to limit the scope of the present disclosure. In other words, it would be obvious to one skilled in the art to which the present disclosure pertains that other modifications based on the technical concepts of the present disclosure are possible. Furthermore, the above-mentioned embodiments can be combined with each other as necessary. For example, a base station and a terminal can be operated by combining one embodiment of the present disclosure with a part of another embodiment. Furthermore, the embodiments of the present disclosure can be applied to other communication systems, and other modifications based on the technical concepts of the embodiments may also be possible. [Explanation of symbols]

[0128] 110 base station 120 terminals 131 Equipment 132 Equipment 133 Equipment 133 User Plane Functional Device 134 Network Slice Selection Function Unit 140 Data Network 151 AUSF (Authentication Server Function) device 152 Network Exposure Functional Device 153 Network Storage Function Device 154 Policy and Billing Functional Device 154 Policy and Billing Functional Device 155 Integrated Data Management Device 156 Application Function Device 157 Service communication proxy device 410 Transmitter / Receiver 420 Memory 430 Control Unit 510 Transmitter / Receiver 520 Memory 530 Control Unit 610 Transmitter / Receiver 620 Memory 630 Control Unit

Claims

1. 1. A method for managing event monitoring for a group of terminals performed by a unified data management (UDM) in a wireless communication system, comprising: receiving a monitoring request message for modification of a configured monitoring event from a network exposure function (NEF), the monitoring request message including a group management operation for the group of terminals and a terminal identifier indicating a terminal affected by the operation; updating the configured monitoring event for the affected terminal identified by the terminal identifier based on the action; Identifying whether the configured monitoring event needs to be performed by an access and mobility management function (AMF); and If the configured monitoring event needs to be performed by the AMF, transmitting information for modifying the configured monitoring event, including a configuration identifier corresponding to the configured monitoring event and the terminal identifier, to the AMF associated with the affected terminal; The method, wherein the actions include at least one of adding the terminal to the group or removing the terminal from the group.

2. The method described in claim 1, wherein the monitoring request message is generated based on a message from an application function entity associated with the configured monitoring event, and the monitoring request message includes group report guard time information for collecting terminal reports, the operation, and the terminal identifier.

3. If the action is the add, the update to the configured monitoring event includes: Adding the affected terminal to the group of terminals for the configured monitoring event; and monitoring the affected terminal for the configured monitoring event; If the action is the delete, the update to the configured monitoring event includes: Deleting the affected terminals from the group of terminals for the configured monitoring event; and Suspending monitoring of the affected terminal for the configured monitoring event; The configured monitoring event is modified in the AMF based on the information; If the operation is the addition, the affected terminal is monitored for the monitoring event by the AMF; The method of claim 1, wherein if the action is the deletion, the affected terminal stops monitoring the monitoring event in the AMF.

4. 1. A method for managing event monitoring for a group of terminals performed by a network exposure function (NEF) in a wireless communication system, comprising: receiving a first monitoring request message for modifying the configured monitoring event from an application function entity associated with the configured monitoring event, the first monitoring request message including a first configuration identifier corresponding to the configured monitoring event and a terminal identifier indicating a group management operation for the group of terminals and terminals affected by the operation; transmitting a second monitoring request message based on the first monitoring request message in a unified data management (UDM), the second monitoring request message including a second configuration identifier corresponding to the configured monitoring event, the operation, and the terminal identifier; The method, wherein the action includes adding the terminal to the group or removing the terminal from the group.

5. The method described in claim 4, wherein the first monitoring request message and the second monitoring request message include group report guard time information for collecting terminal reports.

6. If the action is the addition, the affected terminal is added to the group of terminals for the configured monitoring event and monitored for the configured monitoring event; If the action is "delete," the affected terminal is deleted from the group of terminals for the configured monitoring event, and monitoring for the configured monitoring event is discontinued; The configured monitoring event is modified in the AMF based on information regarding modification of the configured monitoring event; If the operation is the addition, the affected terminal is monitored for the monitoring event by the AMF; The method of claim 4, wherein if the action is the deletion, the affected terminal stops monitoring the monitoring event in the AMF.

7. A unified data management (UDM) that manages event monitoring for a group of terminals in a wireless communication system, a transceiver unit; and Receive a monitoring request message for modification of a configured monitoring event from a network exposure function (NEF), the monitoring request message including a group management operation for the group of terminals and a terminal identifier indicating a terminal affected by the operation; updating the configured monitoring events for the affected terminal based on the action; Identifying whether the configured monitoring event needs to be performed by an access and mobility management function (AMF); A controller configured to send, when the configured monitoring event needs to be performed by the AMF, information for modifying the configured monitoring event, including a configuration identifier corresponding to the configured monitoring event and the terminal identifier, to the AMF associated with the affected terminal; The UDM, wherein the actions include at least one of adding the terminal to the group or removing the terminal from the group.

8. The UDM described in Claim 7, wherein the monitoring request message is generated based on a message from an application function entity associated with the configured monitoring event, and the monitoring request message includes group report guard time information for collecting terminal reports, the operation, and the terminal identifier.

9. When the operation is the addition, the control unit adding the affected terminal to the group of terminals for the configured monitoring event; and configured to monitor the affected terminal for the configured monitoring event; When the operation is the deletion, the control unit Deleting the affected terminals from the group of terminals for the configured monitoring event; and configured to suspend monitoring of the affected terminal for the configured monitoring event; The configured monitoring event is modified in the AMF based on the information; If the operation is the addition, the affected terminal is monitored for the monitoring event by the AMF; The UDM of claim 7, wherein if the action is the deletion, the affected terminal stops monitoring the monitoring event in the AMF.

10. A network exposure function (NEF) that manages event monitoring for a group of terminals in a wireless communication system, a transceiver unit; and receiving a first monitoring request message for modifying the configured monitoring event from an application function entity associated with the configured monitoring event, the first monitoring request message including a first configuration identifier corresponding to the configured monitoring event and a terminal identifier indicating a group management operation for the group of terminals and terminals affected by the operation; a control unit configured to send a second monitoring request message based on the first monitoring request message in a unified data management (UDM), the second monitoring request message includes a second configuration identifier corresponding to the configured monitoring event, the operation, and the terminal identifier; The operation includes adding or removing the terminal from the group.

11. The NEF of claim 10, wherein the first monitoring request message and the second monitoring request message include group report guard time information for collecting terminal reports.

12. If the action is the addition, the affected terminal is added to the group of terminals for the configured monitoring event and monitored for the configured monitoring event; If the action is "delete," the affected terminal is deleted from the group of terminals for the configured monitoring event, and monitoring for the configured monitoring event is discontinued; The configured monitoring event is modified in the AMF based on information regarding modification of the configured monitoring event; If the operation is the addition, the affected terminal is monitored for the monitoring event by the AMF; The NEF of claim 10, wherein if the action is the deletion, the affected terminal stops monitoring the monitoring event in the AMF.

Images