WO2022012674A1 - Procédé et appareil de surveillance d'événements - Google Patents

Procédé et appareil de surveillance d'événements Download PDF

Info

Publication number
WO2022012674A1
WO2022012674A1 PCT/CN2021/106811 CN2021106811W WO2022012674A1 WO 2022012674 A1 WO2022012674 A1 WO 2022012674A1 CN 2021106811 W CN2021106811 W CN 2021106811W WO 2022012674 A1 WO2022012674 A1 WO 2022012674A1
Authority
WO
WIPO (PCT)
Prior art keywords
monitoring
scef
group identifier
data management
hss
Prior art date
Application number
PCT/CN2021/106811
Other languages
English (en)
Inventor
Jingrui TAO
David Castellanos Zamora
Beatriz Maroto Gil
Emiliano Merino Vazquez
Original Assignee
Telefonaktiebolaget Lm Ericsson (Publ)
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Telefonaktiebolaget Lm Ericsson (Publ) filed Critical Telefonaktiebolaget Lm Ericsson (Publ)
Publication of WO2022012674A1 publication Critical patent/WO2022012674A1/fr

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W24/00—Supervisory, monitoring or testing arrangements
    • H04W24/10—Scheduling measurement reports ; Arrangements for measurement reports
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/08—Configuration management of networks or network elements
    • H04L41/085—Retrieval of network configuration; Tracking network configuration history
    • H04L41/0853—Retrieval of network configuration; Tracking network configuration history by actively collecting configuration information or by backing up configuration information
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W24/00—Supervisory, monitoring or testing arrangements
    • H04W24/02—Arrangements for optimising operational condition
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W8/00—Network data management
    • H04W8/18—Processing of user or subscriber data, e.g. subscribed services, user preferences or user profiles; Transfer of user or subscriber data
    • H04W8/186—Processing of subscriber group data

Definitions

  • the non-limiting and exemplary embodiments of the present disclosure generally relate to the technical field of communications, and specifically to methods and apparatuses for event monitoring.
  • CCT Cellular Internet of Things
  • MTC Machine-Type Communication
  • An example of such applications is the use of smart-metering readers, in which an MTC device can be placed in different locations and start sending and/or receiving data on a regular basis (e.g. electricity consumption reports, water-levels) .
  • a hiring car company is another example, since they can place an MTC device on each car to track the consumers/customers and send them any kind of local advertising whenever they pass through a certain location.
  • an exposure function entity such as service capability exposure function (SCEF) or network exposure function (NEF) or an SCEF+NEF provides a means to securely expose the services and capabilities provided by a 3GPP network.
  • the exposure function entity is a functional entity (network function) which receives the configuration of different monitoring events (e.g. when MTC device becomes reachable) initiated by an Application Function (AF) .
  • AF Application Function
  • This monitoring request is then sent by the exposure function entity via the HSS (Home Subscriber Server) towards the Mobility Management Entity (MME) in fourth generation (4G) core network via a diameter protocol (s6t interface, as described in 3GPP TS 29.336 V16.2.0, the disclosure of which is incorporated by reference herein in its entirety, or via UDM (User Data Management) towards the Access Management Function (AMF) in fifth generation (5G) core network, as described in 3GPP TS 29.503, the disclosure of which is incorporated by reference herein in its entirety.
  • This monitoring can be requested for an individual user/device identified by an External Identifier, e.g. device1@ericsson. com, or for a group of users/devices identified by an External Group Identifier, e.g. devices-group-1@ericsson. com.
  • SCEF and NEF can be a combined node or separate nodes. The same happens for HSS and UDM, since they can be co-located or deployed in separate functional entities.
  • the detail of SCEF has been defined in 3GPP TS 23.682 V16.7.0, the disclosure of which is incorporated by reference herein in its entirety.
  • the detail of NEF has been defined in 3GPP TS 23.501 V16.5.0, the disclosure of which is incorporated by reference herein in its entirety. NEF may inherit the functions from SCEF.
  • the architecture for SCEF and/or NEF may enable the 3GPP network to securely expose its services and capabilities provided by the 3GPP network interfaces to an external 3rd party service provider such as services capability server/an application server (SCS/AS) or application function (AF) entity hosting an application (s) .
  • an external 3rd party service provider such as services capability server/an application server (SCS/AS) or application function (AF) entity hosting an application (s) .
  • the HSS shall be able to resolve the External Group Identifier to an IMSI-Group Identifier and one of the External Identifier (s) for each of the IMSIs in the IMSI-Group. If an AF or AS requires the reporting of an event for all the UEs in an operator’s network (e.g. international mobile equipment identity (IMEI) change) , it cannot be performed, since the interface between AF and exposure function entity only allows an External Identifiers (a single UE) or an External Group Identifier (a group of UEs) .
  • IMEI international mobile equipment identity
  • One of these two identifiers is a mandatory field in T8 interface. If all UEs managed by the HSS are requested to be monitored, a possible choice is to create a group and provision each and every UE in the network inside the group. This results in huge signaling since when the group is resolved to its individual members, each UE within the group requires a monitoring request. In addition, each time the operator adds or removes one or several UEs (e.g. new users) in the network, it needs to perform an update to include those new UEs. In short, keeping the group updated is a hard task for the operator. In addition, it is very inefficient from the storage perspective, since this group containing all devices should be defined and maintained in the database.
  • the embodiments of the present disclosure propose an improved event monitoring solution.
  • a method performed by an exposure function entity comprises receiving a first monitoring request from an application function entity.
  • the first monitoring request comprises an external group identifier identifying all user equipments (UEs) managed by a data management entity.
  • the method further comprises sending a second monitoring request to the data management entity.
  • the second monitoring request comprises the external group identifier identifying all UEs managed by the data management entity.
  • the first monitoring request further comprises an indication of global group identifier.
  • the second monitoring request further comprises the indication of global group identifier.
  • the method may further comprise identifying the external group identifier as a global group identifier.
  • the second monitoring request further comprises an indication of global group identifier.
  • identifying the external group identifier as a global group identifier comprises identifying the external group identifier as the global group identifier based on a local policy.
  • the local policy is based on machine-type communication (MTC) provider information and the external group identifier.
  • MTC machine-type communication
  • the external group identifier is a global group identifier.
  • a group reporting guard timer and maximum number of reports are absent in both the first monitoring request and the second monitoring request.
  • the method may further comprise receiving a first monitoring indication message from a network entity.
  • the method may further comprise sending a second monitoring indication message to the application function entity.
  • the first monitoring request and the second monitoring request are used for configuration and/or deletion of monitoring events for all UEs managed by the data management entity.
  • the monitoring events for all UEs managed by the data management entity comprises at least one of association of a UE and Universal Integrated Circuit Card (UICC) and/or new international mobile subscriber identity, international mobile equipment identity software version (IMSI-IMEI-SV) association; or roaming status of a UE, and change in roaming status of the UE.
  • UICC Universal Integrated Circuit Card
  • IMSI-IMEI-SV new international mobile subscriber identity
  • IMSI-IMEI-SV international mobile equipment identity software version
  • the method may further comprise receiving a second monitoring response from the data management entity, wherein a number of UEs belonging to a global group is absent in the second monitoring response.
  • the application function entity is an Application Function (AF) or Services Capability Server/Application Server (SCS/AS) .
  • AF Application Function
  • SCS/AS Services Capability Server/Application Server
  • the exposure function entity is a service capability exposure function (SCEF) or a network exposure function (NEF) or an SCEF+NEF.
  • SCEF service capability exposure function
  • NEF network exposure function
  • SCEF+NEF SCEF+NEF
  • the data management entity is a home subscriber server (HSS) or a unified data management (UDM) or a HSS+UDM.
  • HSS home subscriber server
  • UDM unified data management
  • HSS+UDM unified data management
  • a method performed by a data management entity comprises receiving a second monitoring request from an exposure function entity.
  • the second monitoring request comprises an external group identifier identifying all user equipments (UEs) managed by the data management entity.
  • the method further comprises handling the second monitoring request.
  • UEs user equipments
  • the second monitoring request further comprises an indication of global group identifier.
  • the method may further comprise identifying the external group identifier as a global group identifier.
  • identifying the external group identifier as a global group identifier comprises identifying the external group identifier as the global group identifier based on a local policy.
  • the local policy is based on machine-type communication (MTC) provider information and the external group identifier.
  • MTC machine-type communication
  • a group reporting guard timer and maximum number of reports are absent in the second monitoring request.
  • the method may further comprise sending a first monitoring indication message to the exposure function entity.
  • the second monitoring request is used for configuration and/or deletion of monitoring events for all UEs managed by the data management entity.
  • the method may further comprise sending a second monitoring response to the exposure function entity.
  • the number of UEs belonging to a global group is absent in the second monitoring response.
  • handling the second monitoring request comprises at least one of skipping a check for authorization of a machine-type communication (MTC) provider identifier; skipping a resolution of the external group identifier to an international mobile subscriber (IMSI) group identifier; skipping sending of configuration progress reports to the exposure function entity; or skipping a check of existence of the external group identifier.
  • MTC machine-type communication
  • IMSI international mobile subscriber
  • a method performed by an application function entity comprises sending a first monitoring request to an exposure function entity.
  • the first monitoring request comprises an external group identifier identifying all user equipments (UEs) managed by the data management entity.
  • UEs user equipments
  • the first monitoring request further comprises an indication of global group identifier.
  • a group reporting guard timer and maximum number of reports are absent in the first monitoring request.
  • the method may further comprise receiving a second monitoring indication message from the exposure function entity.
  • the first monitoring request is used for configuration and/or deletion of monitoring events for all UEs managed by the data management entity.
  • an exposure function entity comprises a processor and a memory coupled to the processor. Said memory contains instructions executable by said processor. Said exposure function entity is operative to receive a first monitoring request from an application function entity. The first monitoring request comprises an external group identifier identifying all user equipments (UEs) managed by a data management entity. Said exposure function entity is further operative to send a second monitoring request to the data management entity. The second monitoring request comprises the external group identifier identifying all UEs managed by the data management entity.
  • UEs user equipments
  • a data management entity comprising a processor and a memory coupled to the processor. Said memory contains instructions executable by said processor. Said data management entity is operative to receive a second monitoring request from an exposure function entity. The second monitoring request comprises an external group identifier identifying all UEs managed by the data management entity. Said data management entity is further operative to handle the second monitoring request.
  • an application function entity comprises a processor and a memory coupled to the processor. Said memory contains instructions executable by said processor. Said application function entity is operative to send a first monitoring request to an exposure function entity.
  • the first monitoring request comprises an external group identifier identifying all user equipments (UEs) managed by the data management entity.
  • an exposure function entity comprises a receiving module and a sending module.
  • the receiving module may be configured to receive a first monitoring request from an application function entity.
  • the first monitoring request comprises an external group identifier identifying all user equipments (UEs) managed by a data management entity.
  • the sending module may be configured to send a second monitoring request to the data management entity, wherein the second monitoring request comprises the external group identifier identifying all UEs managed by the data management entity.
  • the data management entity comprises a receiving module and a handling module.
  • the receiving module may be configured to receive a second monitoring request from an exposure function entity.
  • the second monitoring request comprises the external group identifier identifying all UEs managed by the data management entity.
  • the handling module may be configured to handle the second monitoring request.
  • an application function entity comprises a sending module.
  • the sending module may be configured to send a first monitoring request to an exposure function entity.
  • the first monitoring request comprises an external group identifier identifying all user equipments (UEs) managed by the data management entity.
  • UEs user equipments
  • a computer program product comprising instructions which, when executed on at least one processor, cause the at least one processor to carry out any of the methods according to the first, second and third aspects of the disclosure.
  • a computer-readable storage medium storing instructions which when executed by at least one processor, cause the at least one processor to carry out any of the methods according to the first, second and third aspects of the disclosure.
  • the proposed solution introduces the concept of Global Group Identifier so that it can be used by operators to avoid provisioning of individual UEs within the group.
  • the proposed solution can reduce network signaling since there is not individual signaling for UE group member.
  • the proposed solution can reduce the unnecessary signaling for intermediate reporting on groups involving all UEs for a network.
  • the proposed solution proposes an efficient way to manage the storage for all UEs as a group while maintains backward compatibility within current interfaces towards external applications.
  • the embodiments herein are not limited to the features and advantages mentioned above. A person skilled in the art will recognize additional features and advantages upon reading the following detailed description.
  • FIG. 1a is a diagram illustrating a monitoring event configuration procedure according to an embodiment of the present disclosure
  • FIG. 1b is a diagram illustrating a monitoring event reporting procedure according to an embodiment of the present disclosure
  • FIG. 1c schematically shows a high level architecture in a 4G network
  • FIG. 1d schematically shows a high level architecture in a 5G network
  • FIG. 1e schematically shows a high level architecture for service exposure for EPC -5GC interworking
  • FIG. 2 shows a flowchart of a method according to an embodiment of the present disclosure
  • FIG. 3 shows a flowchart of a method according to another embodiment of the present disclosure
  • FIG. 4 shows a flowchart of a method according to another embodiment of the present disclosure
  • FIG. 5 shows a flowchart of a method according to another embodiment of the present disclosure
  • FIG. 6 shows a flowchart of a method according to another embodiment of the present disclosure.
  • FIG. 7 shows a flowchart of a method according to another embodiment of the present disclosure.
  • FIG. 8 is a diagram illustrating a monitoring event configuration procedure according to an embodiment of the present disclosure.
  • FIG. 9 is a diagram illustrating a monitoring event reporting procedure according to an embodiment of the present disclosure.
  • FIG. 10 illustrates the procedure of configuring monitoring at the HSS or the MME/SGSN according to an embodiment of the present disclosure
  • FIG. 11a illustrates the procedure of configuring monitoring at the MME/SGSN according to an embodiment of the present disclosure
  • FIG. 11b illustrates the common procedure flow of reporting Monitoring Events that are detected by the MME/SGSN or HSS according to an embodiment of the present disclosure
  • FIG. 12 is a block diagram showing an apparatus suitable for practicing some embodiments of the disclosure.
  • FIG. 13 is a block diagram showing an exposure function entity according to an embodiment of the disclosure.
  • FIG. 14 is a block diagram showing a data management entity according to an embodiment of the disclosure.
  • FIG. 15 is a block diagram showing an application function entity according to an embodiment of the disclosure.
  • the term “network” refers to a network following any suitable (wireless or wired) communication standards.
  • the wireless communication standards may comprise new radio (NR) , long term evolution (LTE) , LTE-Advanced, wideband code division multiple access (WCDMA) , high-speed packet access (HSPA) , Code Division Multiple Access (CDMA) , Time Division Multiple Address (TDMA) , Frequency Division Multiple Access (FDMA) , Orthogonal Frequency-Division Multiple Access (OFDMA) , Single carrier frequency division multiple access (SC-FDMA) and other wireless networks.
  • NR new radio
  • LTE long term evolution
  • WCDMA wideband code division multiple access
  • HSPA high-speed packet access
  • CDMA Code Division Multiple Access
  • TDMA Time Division Multiple Address
  • FDMA Frequency Division Multiple Access
  • OFDMA Orthogonal Frequency-Division Multiple Access
  • SC-FDMA Single carrier frequency division multiple access
  • a CDMA network may implement a radio technology such as Universal Terre
  • UTRA includes WCDMA and other variants of CDMA.
  • a TDMA network may implement a radio technology such as Global System for Mobile Communications (GSM) .
  • An OFDMA network may implement a radio technology such as Evolved UTRA (E-UTRA) , Ultra Mobile Broadband (UMB) , IEEE 802.11 (Wi-Fi) , IEEE 802.16 (WiMAX) , IEEE 802.20, Flash-OFDMA, Ad-hoc network, wireless sensor network, etc.
  • E-UTRA Evolved UTRA
  • UMB Ultra Mobile Broadband
  • IEEE 802.11 Wi-Fi
  • IEEE 802.16 WiMAX
  • IEEE 802.20 Flash-OFDMA
  • Ad-hoc network wireless sensor network
  • the communications between two devices in the network may be performed according to any suitable communication protocols, including, but not limited to, the wireless communication protocols as defined by a standard organization such as 3rd generation partnership project (3GPP) or the wired communication protocols.
  • the wireless communication protocols may comprise the first generation (1G) , 2G, 3G, 4G, 4.5G, 5G communication protocols, and/or any other protocols either currently known or to be developed in the future.
  • entity refers to a network device or network node or network function in a communication network.
  • a core network device may offer numerous services to customers who are interconnected by an access network device. Each access network device is connectable to the core network device over a wired or wireless connection.
  • network function refers to any suitable function which can be implemented in a network entity (physical or virtual) of a communication network.
  • a network function can be implemented either as a network element on a dedicated hardware, as a software instance running on a dedicated hardware, or as a virtualized function instantiated on an appropriate platform, e.g. on a cloud infrastructure.
  • the 5G system may comprise a plurality of NFs such as AMF (Access and mobility Function) , SMF (Session Management Function) , AUSF (Authentication Service Function) , UDM (Unified Data Management) , PCF (Policy Control Function) , AF (Application Function) , NEF (Network Exposure Function) , UPF (User plane Function) and NRF (Network Repository Function) , RAN (radio access network) , SCP (service communication proxy) , NWDAF (network data analytics function) , etc.
  • the 4G system (such as LTE) may include MME (Mobile Management Entity) , HSS (home subscriber server) , SCEF, etc.
  • the network function may comprise different types of NFs for example depending on the specific network.
  • terminal device refers to any end device that can access a communication network and receive services therefrom.
  • the terminal device refers to a mobile terminal, user equipment (UE) , or other suitable devices.
  • the UE may be, for example, a Subscriber Station (SS) , a Portable Subscriber Station, a Mobile Station (MS) , or an Access Terminal (AT) .
  • SS Subscriber Station
  • MS Mobile Station
  • AT Access Terminal
  • the terminal device may include, but not limited to, a portable computer, an image capture terminal device such as a digital camera, a gaming terminal device, a music storage and a playback appliance, a mobile phone, a cellular phone, a smart phone, a voice over IP (VoIP) phone, a wireless local loop phone, a tablet, a wearable device, a personal digital assistant (PDA) , a portable computer, a desktop computer, a wearable terminal device, a vehicle-mounted wireless terminal device, a wireless endpoint, a mobile station, a laptop-embedded equipment (LEE) , a laptop-mounted equipment (LME) , a USB dongle, a smart device, a wireless customer-premises equipment (CPE) and the like.
  • a portable computer an image capture terminal device such as a digital camera, a gaming terminal device, a music storage and a playback appliance
  • a mobile phone a cellular phone, a smart phone, a voice over IP (VoIP) phone
  • a terminal device may represent a UE configured for communication in accordance with one or more communication standards promulgated by the 3GPP, such as 3GPP’ LTE standard or NR standard.
  • 3GPP 3GPP’ LTE standard or NR standard.
  • a “user equipment” or “UE” may not necessarily have a “user” in the sense of a human user who owns and/or operates the relevant device.
  • a terminal device may be configured to transmit and/or receive information without direct human interaction.
  • a terminal device may be designed to transmit information to a network on a predetermined schedule, when triggered by an internal or external event, or in response to requests from the communication network.
  • a UE may represent a device that is intended for sale to, or operation by, a human user but that may not initially be associated with a specific human user.
  • a terminal device may represent a machine or other device that performs monitoring and/or measurements, and transmits the results of such monitoring and/or measurements to another terminal device and/or network equipment.
  • the terminal device may in this case be a machine-to-machine (M2M) device, which may in a 3GPP context be referred to as a machine-type communication (MTC) device.
  • M2M machine-to-machine
  • MTC machine-type communication
  • the terminal device may be a UE implementing the 3GPP narrow band internet of things (NB-IoT) standard.
  • NB-IoT narrow band internet of things
  • a terminal device may represent a vehicle or other equipment that is capable of monitoring and/or reporting on its operational status or other functions associated with its operation.
  • references in the specification to “one embodiment, ” “an embodiment, ” “an example embodiment, ” and the like indicate that the embodiment described may include a particular feature, structure, or characteristic, but it is not necessary that every embodiment includes the particular feature, structure, or characteristic. Moreover, such phrases are not necessarily referring to the same embodiment. Further, when a particular feature, structure, or characteristic is described in connection with an embodiment, it is submitted that it is within the knowledge of one skilled in the art to affect such feature, structure, or characteristic in connection with other embodiments whether or not explicitly described.
  • first and second etc. may be used herein to describe various elements, these elements should not be limited by these terms. These terms are only used to distinguish one element from another. For example, a first element could be termed a second element, and similarly, a second element could be termed a first element, without departing from the scope of example embodiments.
  • the term “and/or” includes any and all combinations of one or more of the associated listed terms.
  • the phrase “at least one of A and B” should be understood to mean “only A, only B, or both A and B. ”
  • the phrase “A and/or B” should be understood to mean “only A, only B, or both A and B. ”
  • FIG. 1a is a diagram illustrating a monitoring event configuration procedure according to an embodiment of the present disclosure.
  • Some exemplary network elements such as a UE, a MME, a UDR (Unified Data Repository) , a HSS, a SCEF+NEF, and a SCS/AS/AF are depicted in FIG. 1a.
  • the operator has indicated the AFs that, if they want to subscribe to an event for all UEs, the external group ID (identifier) to be used is e.g., all-UEs@google. com.
  • This group includes all UEs in the network and it is constantly updated by the operator every time a UE is added (the operator provisions the UE in the group) or removed (the operator removes the UE in the group) .
  • an application subscribes to an event for the external group ID which contains all UEs.
  • SCS/AS/AF sends a monitoring event subscription request to SCEF+NEF.
  • SCEF+NEF sends the subscription to HSS over s6t, indicating the group-guard-timer for HSS to send progress reports (i.e., time interval for reports) for the configuration result for each UE in the group (success/failure) .
  • SCEF+NEF sends s6t-configuration-information-request to HSS.
  • HSS retrieves the group data, that is, the group members (UE external identifiers) . In this way, the group is resolved to its individual members.
  • HSS sends s6t-configuration-information-Answer including configuration-in-progress to SCEF+NEF.
  • the HSS stores the event (IMEI-change) and the SCEF-ID which is to be notified when the IMEISV changes.
  • FIG. 1b is a diagram illustrating a monitoring event reporting procedure according to an embodiment of the present disclosure.
  • Some exemplary network elements such as a UE, a MME, a UDR (Unified Data Repository) , a HSS, a SCEF+NEF, and a SCS/AS/AF are depicted in FIG. 1b.
  • HSS sends a s6t-reporting-information-request including a list of UEs configured so far to SCEF+NEF.
  • SCEF+NEF sends a s6t-reporting-information-Answer to HSS.
  • HSS keeps on storing the event for the remaining UEs.
  • HSS sends a s6t-reporting-information-request including a list of UEs configured since a last report to SCEF+NEF.
  • SCEF+NEF sends a s6t-reporting-information-Answer to HSS.
  • HSS keeps on storing the event for the remaining UEs and sends reports after each interval expires for all UEs in the group until last UE is configured.
  • the configuration for a large group of UEs or all UEs involves a lot of time and signaling. Moreover, every time a new UE joins the group or leave the group, the group needs to be updated or provisioned by the operator.
  • FIGs. 1c-1e show some system architectures in which the embodiments of the present disclosure can be implemented.
  • the system architectures of FIGs. 1c-1e only depict some exemplary elements.
  • a communication system may further include any additional elements suitable to support communication between terminal devices or between a wireless device and another communication device, such as a landline telephone, a service provider, or any other network node or terminal device.
  • the communication system may provide communication and various types of services to one or more terminal devices to facilitate the terminal devices’ access to and/or use of the services provided by, or via, the communication system.
  • FIG. 1c schematically shows a high level architecture in a 4G network, which is same as Figure 4.2-1a of 3GPP TS 23.682 V16.7.0, the disclosure of which is incorporated by reference herein in its entirety.
  • the system architecture of FIG. 1c may comprise some exemplary elements such as SCS, AS, SCEF, HSS (home subscriber server) , UE, RAN (Radio Access Network) , SGSN (Serving GPRS (General Packet Radio Service) Support Node) , MME (Mobile Management Entity) , MSC (Mobile Switching Centre) , S-GW (Serving Gateway) , GGSN/P-GW (Gateway GPRS Support Node/PDN (Packet Data Network) Gateway) , MTC-IWF (Machine Type Communications-InterWorking Function) CDF/CGF (Charging Data Function/Charging Gateway Function) , MTC-AAA (Machine Type Communications-authentication, authorization and accounting) , SMS-SC/GMSC/IWM
  • FIG. 1d schematically shows a high level architecture in a 5G network, which is same as Figure 4.2.3-1 of 3GPP TS 23.501 V16.5.0, the disclosure of which is incorporated by reference herein in its entirety.
  • the system architecture of FIG. 1d may comprise some exemplary elements such as AMF, SMF, AUSF, UDM, PCF, AF, NEF, UPF and NRF, (R) AN, SCP, etc.
  • the network elements, reference points and interfaces as shown in FIG. 1d may be same as the corresponding network elements, reference points and interfaces as described in 3GPP TS 23.501 V16.5.0.
  • FIG. 1e schematically shows a high level architecture for service exposure for EPC (evolved packet core) -5GC (5G core) interworking, which is same as Figure 4.3.5.1 1 of 3GPP TS 23.501 V16.5.0.
  • EPC evolved packet core
  • 5G core 5G core
  • the network is expected to associate the UE with an SCEF+NEF node for service capability exposure.
  • the system architecture of FIG. 1e may comprise some exemplary elements such as AF/AS, SCEF+NEF, EPC node, NF, etc.
  • the network elements and interfaces as shown in FIG. 1e may be same as the corresponding network elements and interfaces as described in 3GPP TS 23.501 V16.5.0.
  • the exposure function entity such as SCEF and NEF may provide a means to securely expose the services and capabilities provided by the network (such as 3GPP network) interfaces.
  • the exposure function entity may provide a means for the discovery of the exposed services and capabilities.
  • the exposure function entity may provide access to network capabilities through network application programming interfaces (e.g. Network APIs (Application Programming Interfaces) ) .
  • the exposure function entity may abstract the services from the underlying network interfaces and protocols.
  • monitoring capability may be used for monitoring of specific event for a terminal device in a network such as 4G/5G system and making such monitoring events information available for external exposure via the exposure function entity such as SCEF/NEF.
  • the provisioning capability may be used for allowing external party to provision of information which can be used for the terminal device such as UE in the network such as 4G/5G system.
  • the policy/charging capability may be used for handling QoS (quality of service) and charging policy for the terminal device such as UE based on the request from an external party.
  • the analytics reporting capability may be used for allowing an external party to fetch or subscribe/unsubscribe to analytics information generated by the network such as 4G/5G system.
  • Data capability may be used for allowing an external party to communicate with a terminal device such as UE via an application programming interface.
  • the exposure function entity may support network exposure function and network exposure services as described in 3GPP TS 23.501 V16.5.0 (such as clause 6.2.5, clause 7.2.8 of 3GPP TS 23.501 V16.5.0) .
  • the exposure function entity may support the network exposure function as described in clause 4.4.8 of 3GPP TS 23.682 V16.7.0 (such as clause 4.4.8) .
  • FIG. 2 shows a flowchart of a method 200 according to an embodiment of the present disclosure, which may be performed by an apparatus implemented in or at or as an exposure function entity (such as SCEF, NEF or SCEF+NEF) or communicatively coupled to the exposure function entity.
  • the apparatus may provide means or modules for accomplishing various parts of the method 200 as well as means or modules for accomplishing other processes in conjunction with other components.
  • the method 200 illustrates the procedure of configuring monitoring at network entity such as the HSS or the MME/SGSN.
  • the method 200 may be used for various monitoring event types. For example, the following events may be configured for monitoring for all UEs managed by a data management entity such as HSS:
  • UICC Universal Integrated Circuit Card
  • IMSI-IMEI-SV new international mobile subscriber identity, international mobile equipment identity software version
  • the method 200 is also used for deleting a previously configured monitoring event either as a standalone procedure or together with configuring a new monitoring event between the same SCEF and the same SCS/AS, or replacing a previously configured monitoring event with a new monitoring event of the same type between the same SCEF and the same SCS/AS, or for one-time reporting in case the configured monitoring event is available at the configured node
  • the exposure function entity receives a first monitoring request from an application function entity.
  • the first monitoring request comprises an external group identifier identifying all UEs managed by the data management entity.
  • the first monitoring request may further comprise any other suitable parameters.
  • the first monitoring request may further include common parameters as described in clause 5.6.0 of 3GPP TS 23.682 V16.7.0.
  • the application function entity may be an SCS/AS or AF.
  • the data management entity may be a home subscriber server (HSS) or a unified data management (UDM) or a HSS+UDM.
  • HSS home subscriber server
  • UDM unified data management
  • HSS+UDM unified data management
  • the first monitoring request may be similar to the monitoring request sent from the SCS/AS to the SCEF as described in clause 5.6.1.1 of 3GPP TS 23.682 V16.7.0 except that the first monitoring request may include the external group identifier identifying all UEs managed by the data management entity.
  • the SCS/AS sends a Monitoring Request (external group identifier identifying all UEs managed by a data management entity, SCS/AS Identifier, Monitoring Type, Monitoring Duration, T8 Destination Address, TLTRI (T8 Long Term Transaction Reference ID) for Deletion, Group Reporting Guard Time, MTC Provider Information) message to the SCEF.
  • the SCEF assigns a TLTRI that identifies the Monitoring Request.
  • the SCS/AS may perform deletion of a previously configured monitoring event together with configuring a new monitoring event. If the SCS/AS wants to perform deletion of a previously configured monitoring event, then it shall include TLTRI for Deletion.
  • the SCS/AS wants to configure monitoring event for the external group identifier identifying all UEs managed by a data management entity, the SCS/AS can send Monitoring Request message including the external group identifier identifying all UEs managed by the data management entity. If the SCS/AS includes the external group identifier identifying all UEs managed by the data management entity in the Monitoring Request message, External Identifier or MSISDN shall be ignored.
  • the exposure function entity handles the first monitoring request.
  • the SCEF stores SCS/AS Identifier, T8 Destination Address, Monitoring Duration.
  • the SCEF stores the TLTRI, and also assigns it to an SCEF Reference ID.
  • the SCEF Based on operator policies, if either the SCS/AS is not authorized to perform this request (e.g. if the SLA (Service Level Agreement) does not allow for it) or the Monitoring Request is malformed or the SCS/AS has exceeded its quota or rate of submitting monitoring requests, the SCEF sends monitoring response and provides a Cause value appropriately indicating the error. If the SCEF received a TLTRI for Deletion, the SCEF looks up the SCEF context pointed to by the TLTRI to derive the related SCEF Reference ID for Deletion.
  • SLA Service Level Agreement
  • the exposure function entity sends a second monitoring request to the data management entity.
  • the second monitoring request comprises the external group identifier identifying all UEs managed by the data management entity.
  • the second monitoring request may be any suitable monitoring requests for various monitoring event types.
  • the second monitoring request may further include any other suitable parameters.
  • the second monitoring request may further include common parameters as described in clause 5.6.0 of 3GPP TS 23.682 V16.7.0.
  • the second monitoring request may be the monitoring request sent from the SCEF to the HSS as described in clause 5.6.1.1 of 3GPP TS 23.682 V16.7.0.
  • the SCEF sends a Monitoring Request (External Group Identifier identifying all UEs managed by a data management entity, SCEF ID, SCEF Reference ID, Monitoring Type, Monitoring Duration, SCEF Reference ID for Deletion, Chargeable Party Identifier, MTC Provider Information) message to the HSS to configure the given monitoring event on the HSS and on the MME/SGSN, if required.
  • the MTC Provider Information is an optional parameter.
  • the SCEF should validate the provided MTC Provider Information and may override it to an SCEF selected MTC Provider Information based on configuration.
  • the first monitoring request further comprises an indication of global group identifier.
  • the second monitoring request further comprises the indication of global group identifier.
  • the indication of global group identifier may take any suitable form.
  • the indication of global group identifier may be an explicit or implicit indication.
  • the first monitoring request and the second monitoring request are used for configuration and/or deletion of monitoring events for all UEs managed by the data management entity.
  • the exposure function entity receives a second monitoring response from the data management entity.
  • a number of UEs belonging to a global group is absent in the second monitoring response.
  • the second monitoring response may include any parameters.
  • the second monitoring response may be similar to the monitoring response sent from the HSS to the SCEF as described in clause 5.6.1.1 of 3GPP TS 23.682 V16.7.0 except that the number of UEs belonging to the global group is absent in the second monitoring response.
  • FIG. 3 shows a flowchart of a method 300 according to another embodiment of the present disclosure, which may be performed by an apparatus implemented in or at or as an exposure function entity (such as SCEF, NEF or SCEF+NEF) or communicatively coupled to the exposure function entity.
  • the apparatus may provide means or modules for accomplishing various parts of the method 300 as well as means or modules for accomplishing other processes in conjunction with other components. For some parts which have been described in the above embodiments, detailed description thereof is omitted here for brevity.
  • the exposure function entity receives a first monitoring request from an application function entity, wherein the first monitoring request comprises an external group identifier identifying all UEs managed by a data management entity.
  • Block 302 is same as block 202 of FIG. 2.
  • the exposure function entity identifies the external group identifier as a global group identifier.
  • the second monitoring request further comprises an indication of global group identifier.
  • the exposure function entity may identify the external group identifier as the global group identifier in various ways.
  • an external group identifier may be defined as the global group identifier which is known by the exposure function entity and the application function entity.
  • the exposure function entity may identify the external group identifier as the global group identifier based on a local policy.
  • the local policy is based on machine-type communication (MTC) provider information and the external group identifier.
  • MTC provider information may identify the MTC Service Provider and/or MTC Application.
  • the exposure function entity sends a second monitoring request to the data management entity, wherein the second monitoring request comprises the external group identifier identifying all UEs managed by the data management entity.
  • Block 308 is same as block 206 of FIG. 2.
  • Block 308 the exposure function entity receives a second monitoring response from the data management entity.
  • Block 308 is same as block 206 of FIG. 2.
  • the external group identifier may be a global group identifier.
  • the external group identifier may be GLOBAL-GROUP-IDENTIFIER-TYPE (2) .
  • the value 2 indicates the External-Identifier AVP (attribute-value pair) carries an identity which has been identified as a Global Group (all UEs) .
  • the Global Group Identifier may only be used if the monitoring event is either IMEI (SV) change or Roaming Status.
  • a group reporting guard timer and maximum number of reports are absent in both the first monitoring request and the second monitoring request.
  • the group reporting guard timer indicates that the collected status indications and/or reports for UEs belonging to a group shall be reported no later than at the interval indicated by the group reporting guard timer.
  • the group reporting guard timer shall be present if the User-Identifier contains an External Group Identifier and the External Group Identifier is not identified as a Global Group Identifier; otherwise, the group reporting guard timer shall be absent.
  • Maximum number of reports is a parameter that indicates the maximum number of event reports to be generated by a network entity such as the HSS, MME, or SGSN until the associated monitoring event is considered to expire.
  • FIG. 4 shows a flowchart of a method 400 according to another embodiment of the present disclosure, which may be performed by an apparatus implemented in or at or as an exposure function entity (such as SCEF, NEF or SCEF+NEF) or communicatively coupled to the exposure function entity.
  • the apparatus may provide means or modules for accomplishing various parts of the method 400 as well as means or modules for accomplishing other processes in conjunction with other components. For some parts which have been described in the above embodiments, detailed description thereof is omitted here for brevity.
  • the exposure function entity receives a first monitoring indication message from a network entity.
  • the network entity may be the HSS or UDM or HSS+UDM.
  • the network entity may be the MME/SGSN.
  • the network entity may be the AMF.
  • a monitoring event may be detected by a network entity such as the HSS, or the network entity such as the HSS needs to inform the exposure function entity such as SCEF about the change of status (suspend/resume/cancel) of an ongoing monitoring if an event related with the change of monitoring support at the serving node, (e.g. lack of monitoring support in a network entity such as MME/SGSN or revocation of monitoring authorization) is detected in the network entity such as the HSS.
  • the network entity such as HSS also stores the time when the event is detected or the status is changed.
  • the network entity such as HSS sends a Monitoring Indication (SCEF Reference ID (s) , External ID or MSISDN (Mobile Subscriber ISDN (Integrated Services Digital Network) Number) , Monitoring Event Report) message to the exposure function entity such as SCEF.
  • SCEF Reference ID s
  • External ID or MSISDN Mobile Subscriber ISDN (Integrated Services Digital Network) Number
  • Monitoring Event Report a Monitoring Indication
  • External ID or MSISDN are only included if the indication is associated with an individual Group Member UE.
  • SCEF Based on SCEF Reference ID, the SCEF can determine what groups the report pertains to. Multiple SCEF Reference IDs can be included if the UE is part of multiple groups that require the same monitoring indication.
  • the exposure function entity sends a second monitoring indication message to the application function entity. For example, using the SCEF Reference ID, the SCEF retrieves the associated TLTRI along with the T8 Destination Address. If the TLTRI refers to a group-based Monitoring Event configuration, and if no Group Reporting Guard Time was set, then the SCEF sends a Monitoring Indication (TLTRI (s) , Cause, Monitoring Event Report) message to the identified destination. So that the SCEF can determine what groups the report pertains to, multiple TLTRIs can be included if the UE is part of multiple groups that require the same monitoring indication. For each group member UE all the received Monitoring Event Report, and the corresponding time received at SCEF or the time value sent by HSS, are sent to the SCS/AS.
  • TLTRI Monitoring Indication
  • FIG. 5 shows a flowchart of a method 500 according to another embodiment of the present disclosure, which may be performed by an apparatus implemented in or at or as a data management entity (such as HSS, UDM or HSS+UDM) or communicatively coupled to the data management entity.
  • the apparatus may provide means or modules for accomplishing various parts of the method 500 as well as means or modules for accomplishing other processes in conjunction with other components. For some parts which have been described in the above embodiments, detailed description thereof is omitted here for brevity.
  • the data management entity receives a second monitoring request from an exposure function entity.
  • the second monitoring request comprises an external group identifier identifying all UEs managed by the data management entity.
  • the exposure function entity such as SCEF may send the second monitoring request to the data management entity at block 204 of FIG. 2, and the data management entity may receive the second monitoring request from the exposure function entity.
  • the external group identifier is a global group identifier.
  • a group reporting guard timer and maximum number of reports are absent in the second monitoring request.
  • the second monitoring request further comprises an indication of global group identifier.
  • the data management entity handles the second monitoring request.
  • the data management entity such as HSS examines the monitoring Request message, e.g. with regard to the existence of External Group Identifier, whether any included parameters are in the range acceptable for the operator, whether the monitoring event (s) is supported by the serving MME/SGSN, whether the group-basis monitoring event feature is supported by the serving MME/SGSN, or whether the monitoring event that shall be deleted is valid.
  • the HSS optionally authorizes the chargeable party identified by Chargeable Party Identifier. If this check fails, the HSS sends a Monitoring Response and provides a Cause value indicating the reason for the failure condition to the SCEF.
  • the HSS if the HSS receives the Monitoring Request with an External Group Identifier identifying all UEs managed by the data management entity, the HSS sends a Monitoring Response (SCEF Reference ID, Cause) message to the SCEF to acknowledge acceptance of the Monitoring Request immediately.
  • the HSS deletes the monitoring event configuration identified by the SCEF Reference ID, if it was requested.
  • the HSS stores the SCEF Reference ID, the SCEF ID, Monitoring Duration and the SCEF Reference ID for Deletion as provided by the SCEF.
  • SCEF SCEF Reference ID
  • Monitoring Duration SCEF Reference ID for Deletion as provided by the SCEF.
  • SCEF SCEF Reference ID
  • Monitoring Duration SCEF Reference ID for Deletion as provided by the SCEF.
  • HSS stores the subscription with an external Identity as “virtual user” (associated to the “global” group) . No progress reports shall be sent to SCEF.
  • the second monitoring request further comprises the indication of global group identifier.
  • the data management entity may skip a check for authorization of a machine-type communication (MTC) provider identifier.
  • MTC machine-type communication
  • the data management entity may skip a resolution of the external group identifier to an international mobile subscriber (IMSI) group identifier.
  • IMSI international mobile subscriber
  • the data management entity may skip a check of existence of the external group identifier.
  • the data management entity may skip sending of configuration progress reports to the exposure function entity.
  • the data management entity sends a second monitoring response to the exposure function entity.
  • the number of UEs belonging to a global group is absent in the second monitoring response.
  • the data management entity sends a first monitoring indication message to the exposure function entity.
  • FIG. 6 shows a flowchart of a method 600 according to another embodiment of the present disclosure, which may be performed by an apparatus implemented in or at or as a data management entity (such as HSS, UDM or HSS+UDM) or communicatively coupled to the data management entity.
  • the apparatus may provide means or modules for accomplishing various parts of the method 600 as well as means or modules for accomplishing other processes in conjunction with other components. For some parts which have been described in the above embodiments, detailed description thereof is omitted here for brevity.
  • the data management entity receives a second monitoring request from an exposure function entity.
  • the second monitoring request comprises the external group identifier identifying all UEs managed by the data management entity.
  • Block 602 is same as block 502 of FIG. 5.
  • the data management entity identifies the external group identifier as a global group identifier.
  • the data management entity may identify the external group identifier as the global group identifier based on a local policy.
  • the local policy is based on machine-type communication (MTC) provider information and the external group identifier.
  • MTC machine-type communication
  • Block 606 the data management entity handles the second monitoring request.
  • Block 606 is same as block 504 of FIG. 5.
  • the data management entity sends a second monitoring response to the exposure function entity.
  • the number of UEs belonging to a global group is absent in the second monitoring response.
  • Block 608 is same as block 506 of FIG. 5.
  • Block 610 the data management entity sends a first monitoring indication message to the exposure function entity.
  • Block 610 is same as block 508 of FIG. 5.
  • FIG. 7 shows a flowchart of a method 700 according to another embodiment of the present disclosure, which may be performed by an apparatus implemented in or at or as an application function entity (such as SCS/AS or AF) or communicatively coupled to the application function entity.
  • the apparatus may provide means or modules for accomplishing various parts of the method 700 as well as means or modules for accomplishing other processes in conjunction with other components. For some parts which have been described in the above embodiments, detailed description thereof is omitted here for brevity.
  • the application function entity may send a first monitoring request to an exposure function entity.
  • the first monitoring request comprises an external group identifier identifying all UEs managed by the data management entity.
  • the application function entity may receive a first monitoring response from the exposure function entity.
  • the application function entity may receive a Monitoring Response (TLTRI, Cause) message from the exposure function entity.
  • TTRI, Cause Monitoring Response
  • the Cause value indicates progress of group processing request.
  • the application function entity may receive a second monitoring indication message from the exposure function entity.
  • the SCEF retrieves the associated TLTRI along with the T8 Destination Address. If the TLTRI refers to a group-based Monitoring Event configuration, and if no Group Reporting Guard Time was set, then the SCEF sends a Monitoring Indication (TLTRI (s) , Cause, Monitoring Event Report) message to the identified destination. So that the SCEF can determine what groups the report pertains to, multiple TLTRIs can be included if the UE is part of multiple groups that require the same monitoring indication.
  • TLTRI Monitoring Indication
  • the Global External Group Identifier may be used to identify all UEs in an operator’s network (i.e. all UEs managed by a network entity such as HSS) .
  • the application function entity such as AF may use this global/special group that may be understood as all UEs in a network such as HPLMN (Home Public Land Mobile Network) .
  • the exposure function entity such as SCEF may (e.g., based on local configuration) identify an external group identifier as a Global Group, that is, involving all UEs managed by a data management entity such as HSS.
  • the exposure function entity such as SCEF may indicate a data management entity such as HSS that the External Group is of type Global.
  • This new type of Group may serve as an indication that no progress reports are required, neither the number of UEs within the group.
  • the data management entity such as HSS detects the indication of a global group and acts accordingly, that is, it does not need to check the group existence, since it is understood as global subscription.
  • the data management entity such as HSS also understands that there is no need (as it does not make any sense) of any progress reports or number of UEs within the group.
  • FIG. 8 is a diagram illustrating a monitoring event configuration procedure according to an embodiment of the present disclosure.
  • Some exemplary network elements such as a UE, a MME, a UDR (Unified Data Repository) , a HSS, a SCEF+NEF, and a SCS/AS/AF are depicted in FIG. 8.
  • the operator has indicated the AFs that, if they want to apply a subscription for all UEs, the external group ID (identifier) to be used is e.g., all-UEs@google. com.
  • the external group ID identifier
  • the operator has indicated the AFs that, if they want to apply a subscription for all UEs, the external group ID (identifier) to be used is e.g., all-UEs@google. com.
  • the external group ID identifier
  • an application subscribes to an event for the external group ID which identifies all UEs. For example, The application subscribes to an event to be monitored and reported for an External Group Identifier which identifies “all UEs in the network” , e.g. all-UEs@ericsson. com.
  • SCS/AS/AF sends a monitoring event subscription request to SCEF+NEF.
  • SCEF+NEF detects, based on a local policy, that the External Group ID corresponds to all UEs. Hence, a new type of identifier (global group ID) is to be sent to HSS. Since this a bulk subscription for SCEF, progress report items and number of UEs in the group are not expected.
  • SCEF+NEF sends s6t-configuration-information-request to HSS.
  • SCEF+NEF detects, based on a local policy, that the group identifier is a Global group (i.e. it corresponds to all UEs, hence it is not provisioned as a group) .
  • SCEF+NEF includes a new group-type information element to indicate that the group has been identified as global.
  • HSS detects, based on the new type of external group ID, that the external group ID identifies all UEs managed by the HSS. The presence of this type indicates that no configuration progress report are to be sent to SCEF, neither the number of UEs.
  • HSS stores the subscription with an external Identity as “virtual user” (associated to the “global” group) . No progress reports shall be sent to SCEF.
  • FIG. 9 is a diagram illustrating a monitoring event reporting procedure according to an embodiment of the present disclosure.
  • Some exemplary network elements such as a UE, a MME, a UDR (Unified Data Repository) , a HSS, a SCEF+NEF, and a SCS/AS/AF are depicted in FIG. 9.
  • step 901 after changing smart phone (IMEI changes to a 5G capable device) , a user attaches to the network over 4G network.
  • IMEI changes to a 5G capable device
  • MME sends an update-location-request including IMEISV to HSS. For example, when a UE in the network changes its IMEISV and attaches to the 4G network. HSS receives the new IMEISV in the location update procedure.
  • HSS reads user data from UDR and checks stored IMEISV. Since the IMEI has changed, HSS stores the new IMEI.
  • the retrieved subscription data includes the SCEF IDs.
  • HSS sends a s6t-reporting-information-request to notifies SCEF+NEF about the event (IMEI change) .
  • HSS reads the User’s data from the database and detects that the IMEI has changed. It then retrieves the subscription to events being monitored for this virtual user associated to the “global” group by querying the event subscription (IMEISV change) .
  • the subscriptions data retrieved include the identities (i.e. SCEF-ID) subscribed to those changes and HSS notifies the event to that identity.
  • SCEF+NEF sends a monitoring event notification to SCS/AS.
  • HSS notifies SCEF so that SCEF is able to notify SCS/AS/AF.
  • FIGs. 8-9 There are some advantages of the solutions of FIGs. 8-9. For example, there is no extra signaling regarding of the amount of UEs present in the group. In addition, there is no provisioning required at all for new/removed UEs, since this “virtual user” is equivalent to “all UEs” .
  • the Global Group Identifier can be detected (via local policy) in the data management entity such as HSS
  • 5GS 5G Core Network
  • SCEF is replaced by NEF
  • MME is replaced by AMF
  • HSS is replaced by UDM.
  • FIGs. 2-9 may be viewed as method steps, and/or as operations that result from operation of computer program code, and/or as a plurality of coupled logic circuit elements constructed to carry out the associated function (s) .
  • the schematic flow chart diagrams described above are generally set forth as logical flow chart diagrams. As such, the depicted order and labeled steps are indicative of specific embodiments of the presented methods. Other steps and methods may be conceived that are equivalent in function, logic, or effect to one or more steps, or portions thereof, of the illustrated methods. Additionally, the order in which a particular method occurs may or may not strictly adhere to the order of the corresponding steps shown.
  • the following events may be configured for monitoring for an individual UE or a group of UEs:
  • Roaming status i.e. Roaming or No Roaming, VPLMN-ID
  • VPLMN-ID Roaming or No Roaming
  • the following events may be configured for monitoring for all UEs managed by the HSS:
  • Roaming status i.e. Roaming or No Roaming, VPLMN-ID
  • VPLMN-ID Roaming or No Roaming
  • the HSS shall, in the following order:
  • the HSS can skip the check for authorization of the MTC Provider ID
  • the HSS shall return the IMSI Group Id (s) in the order of sequence that corresponds to the order of sequence of the received External Group Identifier (s) received in the User-Identifier AVP and AdditionalIdentifiers AVP.
  • the Result Code shall be set to DIAMETER_SUCCESS. Stop processing.
  • Result-Code in Monitoring-Event-Config-Status for the affected service shall be set to DIAMETER_RESOURCES_EXCEEDED (5006) .
  • the Result-Code shall be set to DIAMETER_SUCCESS in the Configuration Information Answer.
  • the HSS applies the Monitoring-Event-Configuration AVP to each UE of the Group and includes the CIA-Flags AVP with the Group-Configuration-In-Progress bit set in the Configuration Information Answer.
  • the Result-Code shall be set to DIAMETER_SUCCESS in the Configuration Information Answer.
  • the HSS shall forward the monitoring event configuration to the serving node and wait for the answer before sending the Configuration Information Answer to the SCEF.
  • the monitoring event configuration status from the serving node for each event shall be conveyed by the HSS to the SCEF.
  • the Result-Code shall be set to DIAMETER_SUCCESS in the Configuration Information Answer.
  • the HSS shall store the configuration data related to the service; also, it shall indicate to the SCEF that the user is absent, in the Configuration Information Answer, by setting the relevant bit in the S6t-HSS-Cause IE.
  • the Result-Code shall be set to DIAMETER_SUCCESS in the Configuration Information Answer.
  • the HSS (e.g. as being received from the MME/SGSN in the Insert Subscriber Data answer) shall include this data in the Configuration Information Answer.
  • the HSS shall additionally report the capabilities of the different nodes to the SCEF by including Supported-Services AVP (s) with the subset of services supported by the serving node (s) among those supported by the HSS, as indicated by the Node-Type AVP (e.g. HSS, MME) . If the capabilities are the same reported from the MME, the SGSN and the HSS, the HSS shall report the service capabilities without Node-Type to the SCEF.
  • Supported-Services AVP s
  • the HSS shall report the service capabilities without Node-Type to the SCEF.
  • the HSS shall report the Supported-Services to the SCEF excluding the Supported-Services from the purged node.
  • the HSS shall check the Result-Codes in Monitoring-Event-Config-Status AVPs reported by the MME and the SGSN:
  • the HSS shall include both Service-Report AVPs with the respective Node-Type (indicating the type of serving node) in the Monitoring-Event-Config-Status AVP to the SCEF in the CIA command;
  • the HSS shall include one Service-Report AVP without Node-Type in the Monitoring-Event-Config-Status AVP to the SCEF in the CIA command.
  • the HSS shall set the Experimental-Result-Code in Monitoring-Event-Config-Status for the affected service (s) to DIAMETER_ERROR_REQUESTED_RANGE_IS_NOT ALLOWED (5512) .
  • the HSS shall set the Experimental-Result-Code in Monitoring-Event-Config-Status for the affected service (s) to DIAMETER_ERROR_CONFIGURATION_EVENT_NON_EXISTANT (5514) .
  • the HSS shall set the Experimental-Result-Code in Monitoring-Event-Config-Status for the affected service (s) to DIAMETER_ERROR_CONFIGURATION_EVENT_STORAGE_NOT_SUCCESSFUL (5513) .
  • the HSS shall stop processing the request and set Result-Code in Configuration Information Answer to DIAMETER_UNABLE_TO_COMPLY.
  • the HSS shall include in the CIA command the Monitoring Event Report AVP including the SCEF Reference ID of the overwritten configuration data in the SCEF-Reference-ID and SCEF-Reference-ID-for-Deletion AVPs.
  • the HSS needs to report loss of connectivity it shall include the Monitoring-Type AVP set to "LOSS_OF_CONNECTIVITY" in the Monitoring Event Report.
  • the HSS may also include the Loss-Of-Connectivity-Reason AVP in the Monitoring Event Report.
  • the HSS shall include the Supported-Services AVP with the Supported-Monitoring-Events AVP indicating the authorized monitoring events for the requesting SCEF in the CIA command.
  • CIR message includes multiple SCEF Reference ID and one, several or all SCEF Reference ID Monitoring events cannot be handled, or fail to be configured at the registered serving node (s)
  • the HSS shall report all SCEF-Reference-ID requested to the SCEF with an appropriate Experimental-Result-Code or Result-Code in the Monitoring-Event-Config-Status AVP (s) .
  • the HSS can still store the configuration data, return a successful response to SCEF and report the SCEF with monitoring event (s) suspended.
  • the configuration data can then be forwarded whenever traffic is received from MME/SGSN and event (s) can be reported to SCEF as resumed, as described in chapter 7.2.2.
  • the HSS shall reply within the AESE-Communication-Pattern-Config-Status all SCEF Reference ID requested to the SCEF with an appropriate Experimental-Result-Code or Result-Code.
  • the HSS shall delete the stored CP sets associated with the SCEF reference Id and store the new CP set (s) .
  • the CIR message contains combinations of monitoring events and CP parameter set it shall handle each set belonging to an SCEF Reference ID separately and shall send a combined answer to the SCEF with all SCEF Reference IDs requested.
  • the receiving node shall delete the corresponding configuration, if stored.
  • the receiving node shall store the configuration event.
  • the HSS shall delete all Monitoring events configured by the SCEF for the subscriber. This includes forwarding the deletion to involved serving nodes.
  • the HSS shall delete all Communication Pattern configured by the SCEF for the subscriber. This includes forwarding the deletion to involved serving nodes.
  • the HSS shall delete all Suggested Network Configurations configured by the SCEF for the subscriber. This includes the updating of involved serving nodes.
  • the HSS shall return the current settings of Enhanced Coverage together with the current Serving PLMN-ID (if any) in the CIA command.
  • the HSS shall update the subscription data for Enhanced Coverage; the update shall be a complete replacement of any stored information with the received information. This may result in the need to update the MME/SGSN via S6a/d/MAP-Gr with the new value for access restriction; there is however no need for the HSS to delay sending of CIA until updates of serving nodes are confirmed.
  • the HSS shall check whether the suggested parameters are acceptable, and if so, update the stored UE's subscription parameters accordingly and overwrites the old SCEF-Reference-ID and SCEF-ID with the new values. This may result in Insert Subscriber Data Signalling towards the UE's serving node. If the HSS modifies parameters received in Suggested-Network-Configuration AVP, the HSS shall inform the SCEF about the active parameters.
  • the HSS shall delete the related Monitoring event for the UE or the individual group member UE locally after sending the Monitoring-Event-Report.
  • the HSS shall accept the request as follows:
  • the HSS shall set the subscribed periodic RAU/TAU timer using the newly received value.
  • the HSS shall set the subscribed Active Time using the newly received value.
  • the HSS shall set the subscribed Suggested number of downlink packets by adding the newly received value to the currently used value of Suggested number of downlink packets if the aggregated value is within the operator defined range. If the aggregated value is not within the operator defined range, the HSS shall set the subscribed Suggested number of downlink packets according to operator defined range.
  • the HSS shall send the RIR command before the Group Guard Timer expires and shall include several reports and/or status indications in one or more Group Report AVPs.
  • the HSS may divide the accumulated Monitoring Configuration Indications/immediate reports into multiple messages.
  • the HSS shall send immediate reports and/or status indications (for Monitoring Event Configurations) and/or Network Parameter Configurations (for Suggested Network Configurations) for group-based configuration processing using the Group-Report.
  • the HSS shall include the RIR-Flags AVP with the Group-Configuration-In-Progress bit set and restart the Group Guard Timer to the value it originally received in the CIR.
  • the HSS shall indicate that the UE is absent by setting the relevant bit in the S6t-HSS-Cause IE of the Group Report-Item AVP.
  • the HSS shall initiate an RIR command and include a Monitoring-Event-Report AVP including the SCEF Reference ID of the overwritten configuration data and provide the SCEF Reference ID in the SCEF-Reference-ID-for-Deletion AVP.
  • the HSS may initiate a RIR command providing the SCEF Reference ID of the previous Network Parameter Configurations and include the Updated-Network-Configuration AVP including only those parameter configuration (s) which have been updated and are being applied in the network.
  • a RIR command providing the SCEF Reference ID of the previous Network Parameter Configurations and include the Updated-Network-Configuration AVP including only those parameter configuration (s) which have been updated and are being applied in the network.
  • the HSS shall initiate an RIR command and include a Monitoring-Event-Report AVP including the SCEF Reference ID of the overwritten configuration data and provide the SCEF Reference ID in the SCEF-Reference-ID-for-Deletion AVP.
  • the HSS shall delete the related Monitoring event for the UE or the individual group member UE locally after sending the Monitoring-Event-Report. If UE Reachability is reported, a Maximum-UE-Availability-Time AVP may also be present in the report.
  • the HSS detects that the serving node does not support or does not activate (as indicated in IDA or NOR commands) a Monitoring event, or if the UE is part of a group and requires the External-Identifier to be supported by the serving node when it does not, it shall send to the SCEF, an RIR command with the Event-Handling AVP with the value SUSPEND.
  • an HSS detects that in the new serving node an event to be activated is supported which was not supported in the old serving node or if the HSS detects that the new serving node supports the External-Identifier for a UE that is part of a group and requires the External-Identifier which was not supported in the old serving node, it shall send an RIR command with the Event-handling AVP with the value RESUME to the SCEF.
  • the HSS shall send an RIR command to the SCEF, for the monitoring event configurations not accepted by the IWK-SCEF, with the Event-Handling AVP set to the value CANCEL.
  • the HSS shall locally delete the monitoring event configuration (s) and shall skip the sending of a RIR command to the SCEF.
  • the HSS If the HSS receives the DIAMETER_ERROR_SCEF_REFERENCE_ID_UNKNOWN within an RIA command, it shall delete the event stored for the indicated SCEF-Reference-ID (see 3GPP TS 23.007 [19] ) .
  • the HSS shall report all the Supported-Services AVP (s) to the SCEF with the corresponding Node-Type AVP (e.g. HSS, MME) If the services supported and authorized by the HSS are the same than those supported by the serving node (s) , the Node-Type AVP shall be absent.
  • Node-Type AVP e.g. HSS, MME
  • the HSS shall send an RIR command to the SCEF with the Event-Handling AVP set to the value SUSPEND/RESUME.
  • the HSS shall send RIR command with RIR-flags indicating that authorization has changed for one or more events.
  • the Supported-Monitoring-Events AVP shall indicate the authorized or revoked authorization for each event.
  • the HSS When a subscriber is deleted from the HSS while monitoring is active or the authorization for monitoring is revoked, if Report-Eff-MONTE feature is not supported by SCEF or HSS, the HSS shall send an RIR command to the SCEF with the Event-Handling AVP set to the value CANCEL. If the HSS and SCEF support the Report-Eff-MONTE feature, the HSS shall make use of RIR-flags AVP for a given User-Identity and no Monitoring-Event-Report AVP(s) shall be included.
  • the HSS shall make use of the RIR-flag "All-Communication-Pattern-Cancelled" to indicate removal of Communication Pattern for a given User-Identity.
  • the User-Identifier AVP is of type Grouped and it contains the different identifiers used by the UE. This AVP is defined in clause 6.4.2.
  • the AVP format for the S6t interface shall be as given below.
  • This AVP shall contain one of the identifiers (IMSI, MSISDN or External-Identifier) .
  • IMSI the identifiers
  • MSISDN the identifiers
  • External-Identifier the identifiers
  • the IMSI of the UE shall be included (when applicable) in the User-Name AVP.
  • the External-Identifier AVP may either contain the identity of an individual UE or the identity of a Group of UEs or the identity identified as Global Group.
  • the Type-Of-External-Identifier is used to indicate which type of identity is carried in the External-Identifier. When the Type-Of-External-Identifier is not present, it means the External-Identifier AVP contains the identity of an individual UE.
  • the Maximum-Number-of-Reports AVP is of type Unsigned32. It shall contain the number of reports to be generated and sent to the SCEF.
  • This AVP shall not be present when Monitoring-Type is AVAILABILITY_AFTER_DDN_FAILURE (6) or when the External Group is identified as a Global Group.
  • This AVP shall not be greater than one if:
  • - Monitoring-Type is UE_REACHABILITY (1) and Reachability-Type is "Reachability for SMS" or
  • Monitoring-Type is LOCATION_REPORTING (2) and MONTE-Location-Type is LAST_KNOWN_LOCATION (1) .
  • the Type-Of-External-Identifier AVP is of type Unsigned32 and it shall indicate which type of identity is carried in the External-Identifier AVP. The following values are defined:
  • the value 0 indicates the External-Identifier AVP carries the identity of an individual UE.
  • the value 1 indicates the External-Identifier AVP carries the identity of a Group of UEs.
  • the value 2 indicates the External-Identifier AVP carries an identity which has been identified as a Global Group (all UEs) .
  • a Global Group Identifier may only be used if the monitoring event is either IMEI (SV) change or Roaming Status.
  • the Global Group Identifier is an External Group Identifier which applies to any UE managed by the HSS. It is used on the interface between the SCS/AS and the SCEF and on the interface between the SCEF and the HSS. This identifier is used in monitoring event configuration and deletion for all UEs managed by the HSS.
  • the SCEF shall be able to identify the External Group Identifier as a Global Group Identifier and indicate HSS that the External Group Identifier is a Global Group Identifier.
  • HSS When a Global Group Identifier is used, HSS does not inform that Group processing is in progress for each individual UE and the number of UEs is not provided to SCEF. Similarly, Maximum Number of Reports is not applicable for Global Group Identifiers (i.e. only Monitoring Duration is used) .
  • An External Group Identifier identified as Global Group Identifier does not map to an IMSI-Group Identifier.
  • SCEF Reference ID is a parameter created by the SCEF to associate a Monitoring Event report or a deletion of a Monitoring Event to a specific Monitoring Request and the associated context information within the SCEF.
  • SCEF Reference ID is stored by HSS, MME, SGSN, and IWK-SCEF.
  • an SCEF may aggregate Monitoring Event configuration requests for the same External identifier/MSISDN from different SCS/AS instances.
  • an SCEF may aggregate Monitoring Event configuration requests for the same External Group Identifier from different SCS/AS instances.
  • SCEF ID indicates the SCEF to which the Monitoring Indication message has to be sent to by the HSS, MME, SGSN, or IWK-SCEF.
  • SCEF ID is stored by the HSS, MME, SGSN, and IWK-SCEF.
  • SCEF Reference ID for Deletion identifies the monitoring event configuration that shall be deleted before applying the requested monitoring event configuration.
  • Monitoring Type identifies the specific Monitoring Event being requested.
  • the HSS includes User Identity in the monitoring event configuration.
  • Maximum Number of Reports is an optional parameter that indicates the maximum number of event reports to be generated by the HSS, MME, or SGSN until the associated monitoring event is considered to expire.
  • This parameter can be used when configuring a monitoring event for an individual UE or a group not identified as Global. When the parameter is configured for a group, the configured value is applied to each individual UE's monitoring event configuration. A value of one implies a single event report is to be generated which makes it equivalent to a One-time Monitoring Request.
  • Monitoring Duration is an optional parameter that indicates the absolute time at which the related monitoring event request is considered to expire. For Monitoring Requests for a group not identified as Global, this parameter applies to every group member UE. For Monitoring Requests for a group identified as Global, this parameter applies to all UEs managed by the HSS.
  • Monitoring Request a Continuous Monitoring Request.
  • a single Monitoring Request may generate more than one Monitoring Indication message. Support of continuous monitoring is optional.
  • Monitoring Request Absence of both Maximum Number of Reports and Monitoring Duration makes the Monitoring Request a One-time Monitoring Request.
  • One-time Monitoring Requests a single Monitoring Request generates only one Monitoring Report for an individual UE and for an individual group member UE.
  • the monitoring request is considered to expire as soon as one of the conditions is met.
  • Chargeable Party Identifier is an optional parameter included by the SCEF. It identifies the entity towards which accounting/charging functionality is performed by the involved 3GPP network elements.
  • MTC Provider Information is an optional parameter included by the SCEF. It identifies the MTC Service Provider and/or MTC Application. Optionally the MTC Provider Information may also be provided by the SCS/AS.
  • Group Reporting Guard Time is an optional parameter for group-based monitoring configuration. The parameter is not applicable if the group is identified as Global Group. It is used to indicate the time for which the Monitoring Event Reporting (s) detected by the UEs in a group can be aggregated before sending them to the SCEF/SCS/AS.
  • the value of the Group Reporting Guard time should be set less than the Monitoring Duration. For the continuous monitoring reporting, unless the Monitoring Duration has been reached, the Group Reporting Guard timer is restarted when it expires. If the time left until Monitoring Duration is less than the Group Reporting Guard Time, then the Group Reporting Guard timer shall be set to expire when the Monitoring Duration expires. If the Monitoring Duration is expired, the Group Reporting Guard Time, if running, shall be considered to expire and aggregated Monitoring Event Reporting (s) is sent to destination immediately.
  • Number of UEs is a parameter that is provided to the SCEF during group-based monitoring configuration if the group is not identified as Global. It is used to indicate the number of UEs within the group identified by the External Group Identifier. The SCEF uses this value to determine whether the monitoring event has been reported for all group member UEs.
  • FIG. 10 illustrates the procedure of configuring monitoring at the HSS or the MME/SGSN.
  • the procedure is common for various Monitoring Event types. Common parameters for this procedure are detailed in clause 5.6.0. The steps and parameters specific to different Monitoring Event types are detailed in clauses 5.6.1.3 to 5.6.1.9.
  • the procedure is also used for deleting a previously configured Monitoring Event either as a standalone procedure or together with configuring a new Monitoring Event between the same SCEF and the same SCS/AS, or replacing a previously configured Monitoring Event with a new Monitoring Event of the same type between the same SCEF and the same SCS/AS, or for one-time reporting in case the Configured Monitoring Event is available at the configured node.
  • the SCS/AS sends a Monitoring Request (External Identifier or MSISDN or External Group ID, SCS/AS Identifier, Monitoring Type, Maximum Number of Reports, Monitoring Duration, T8 Destination Address, TLTRI for Deletion, Group Reporting Guard Time, MTC Provider Information) message to the SCEF.
  • the SCEF assigns a TLTRI that identifies the Monitoring Request. If the SCS/AS may perform deletion of a previously configured Monitoring Event together with configuring a new Monitoring Event. If the SCS/AS wants to perform deletion of a previously configured Monitoring Event, then it shall include TLTRI for Deletion.
  • the SCS/AS can send Monitoring Request message including External Group Identifier and optionally Group Reporting Guard Time. If the SCS/AS includes External Group Identifier in the Monitoring Request message, External Identifier or MSISDN shall be ignored.
  • a Group Reporting Guard Time is an optional parameter to indicate that aggregated Monitoring Event Reporting (s) which have been detected for the UEs in a group needs to be sent to the SCS/AS once the Group Reporting Guard Time is expired.
  • the SCEF stores SCS/AS Identifier, T8 Destination Address, Monitoring Duration, Maximum Number of Reports and Group Reporting Guard Time, if provided.
  • the SCEF stores the TLTRI, and also assigns it to an SCEF Reference ID. Based on operator policies, if either the SCS/AS is not authorized to perform this request (e.g. if the SLA does not allow for it) or the Monitoring Request is malformed or the SCS/AS has exceeded its quota or rate of submitting monitoring requests, the SCEF performs step 9 and provides a Cause value appropriately indicating the error. If the SCEF received a TLTRI for Deletion, the SCEF looks up the SCEF context pointed to by the TLTRI to derive the related SCEF Reference ID for Deletion.
  • the SCEF uses the Group Reporting Guard Time for a Monitoring Event Reporting for the group of UEs when the Monitoring Indication message is sent from the MME/SGSN to the SCEF.
  • the SCEF sets the Group Reporting Guard Time for HSS less than the value for the SCEF received from SCS/AS in order to ensure to receive accumulated Monitoring Indication from HSS before the Group Reporting Guard Timer for SCEF is expired.
  • the SCEF sends a Monitoring Request (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, Chargeable Party Identifier, Group Reporting Guard Time, MTC Provider Information) message to the HSS to configure the given Monitoring Event on the HSS and on the MME/SGSN, if required. If the External Group Identifier is included, External Identifier or MSISDN shall be ignored. For Monitoring Request of Roaming Status and/or change of IMSI-IMEI (SV) , the SCEF does not indicate the Group Reporting Guard Time.
  • SV IMSI-IMEI
  • the SCEF may identify the External Group Identifier as a Global Group Identifier. If the External Group is a Global Group, the SCEF shall include an indication of Global Group Identifier towards the HSS.
  • the MTC Provider Information in step 1 is an optional parameter.
  • the SCEF should validate the provided MTC Provider Information and may override it to an SCEF selected MTC Provider Information based on configuration. How the SCEF determines the MTC Provider Information if not present in step 1 is left to implementation (e.g. based on the requesting SCS/AS) .
  • the HSS examines the Monitoring Request message, e.g. with regard to the existence of External Identifier or MSISDN or External Group Identifier, whether any included parameters are in the range acceptable for the operator, whether the monitoring event (s) is supported by the serving MME/SGSN, whether the group-basis monitoring event feature is supported by the serving MME/SGSN, or whether the monitoring event that shall be deleted is valid.
  • the HSS optionally authorizes the chargeable party identified by Chargeable Party Identifier. If this check fails the HSS follows step 8 and provides a Cause value indicating the reason for the failure condition to the SCEF.
  • the HSS stores the SCEF Reference ID, the SCEF ID, Maximum Number of Reports, Monitoring Duration and the SCEF Reference ID for Deletion as provided by the SCEF. For a Monitoring Request for a group not identified as global, such parameters are stored for every group member UE.
  • the HSS uses the Group Reporting Guard Time for a Monitoring Event Reporting for the group of UEs not identified as Global when the Monitoring Indication message is sent from the HSS to the SCEF.
  • the HSS For group based processing, if the HSS receives the Monitoring Request with an External Group Identifier, the HSS sends a Monitoring Response (SCEF Reference ID, Number of UEs, Cause) message to the SCEF to acknowledge acceptance of the Monitoring Request immediately. If the group is not identified as Global, the HSS shall begin the processing of individual UEs indicating that Group processing is in progress. The HSS deletes the monitoring event configuration identified by the SCEF Reference ID, if it was requested.
  • SCEF Reference ID Number of UEs, Cause
  • the SCEF sends a Monitoring Response (TLTRI, Cause) message to the SCS/AS.
  • the Cause value indicates progress of Group processing request.
  • the HSS sends an Insert Subscriber Data Request (Monitoring Type, SCEF ID, SCEF Reference ID, Maximum Number of Reports, Monitoring Duration, SCEF Reference ID for Deletion, Chargeable Party Identifier) message to the MME/SGSN for each individual UE and for each individual group member UE.
  • the Monitoring Request message is for a group of UEs, for each UE group member, the HSS includes the selected External ID or the MSISDN in the monitoring event configuration and sends an Insert Subscriber Data Request message per UE to all the MME/SGSN (s) serving the members of the group.
  • the HSS allocates a Provider-Group-ID based on the MTC Provider Information (different from the IMSI-Group-Id) and sends it to the MME/SGSN to assist the serving node (s) when selecting and differentiating configurations for a given MTC Service Provider (e.g. to delete the configurations for a specific MTC Service Provider at the MME/SGSN) .
  • the MME/SGSN If the MME/SGSN is configured to use an IWK-SCEF for the PLMN of the SCEF then clause 5.6.6 applies. Otherwise, the MME/SGSN verifies the request, e.g. if the Monitoring Type is covered by a roaming agreement when the request is from another PLMN or whether it serves the SCEF Reference ID for Deletion and can delete it. If this check fails, the MME/SGSN follows step 7 and provides a Cause value indicating the reason for the failure condition to the HSS. Based on operator policies, the MME/SGSN may also reject the request due to other reasons (e.g. overload or HSS has exceeded its quota or rate of submitting monitoring requests defined by an SLA) .
  • reasons e.g. overload or HSS has exceeded its quota or rate of submitting monitoring requests defined by an SLA
  • the MME/SGSN stores the received parameters and starts to watch for the indicated Monitoring Event unless it is a One-time request and the Monitoring Event is available to the MME/SGSN at the time of sending Insert Subscriber Data Answer.
  • the MME/SGSN deletes the monitoring configuration identified by the SCEF Reference ID for Deletion, if provided.
  • the MME/SGSN will transfer the parameters stored for every monitoring task as part of its context information during an MME/SGSN change.
  • the MME/SGSN sends an Insert Subscriber Data Answer (Cause) message to the HSS. If the requested Monitoring Event is available to the MME/SGSN at the time of sending Insert Subscriber Data Answer, then the MME/SGSN includes the Monitoring Event Report in the Insert Subscriber Data Answer message.
  • the HSS sends a Monitoring Response (SCEF Reference ID, Cause, Monitoring Event Report) message to the SCEF to acknowledge acceptance of the Monitoring Request and the deletion of the identified monitoring event configuration, if it was requested.
  • the HSS deletes the monitoring event configuration identified by the SCEF Reference ID, if it was requested. If the requested Monitoring Event is available to the HSS at the time of sending Monitoring Response message or was received from the MME/SGSN in step 7, then the HSS includes a Monitoring Event Report in the Monitoring Response message.
  • the HSS deletes the associated Monitoring Event configuration for the individual UE or for the individual group member UE.
  • the HSS For group-based processing, if the HSS sent the Monitoring Response in step 4a, i.e. due to having received a Monitoring Request with an External Group Identifier not identified as Global and if the Group Reporting Guard Time was provided in the Monitoring Request, the HSS accumulates multiple responses for the UEs of the group within the Group Reporting Guard Time. After the Group Reporting Guard Time expiration, the HSS sends a Monitoring Indication with the accumulated responses.
  • the HSS includes UE identity (ies) and a Cause value indicating the reason for the failure in the message if the monitoring configuration of the group member failed.
  • the HSS may divide the accumulated Monitoring Indications into multiple messages due to e.g. limitation of the message size.
  • the HSS determines whether the new MME/SGSN supports requested Monitoring Event (s) .
  • the SCEF sends a Monitoring Response (Cause, Monitoring Event Report) message to the SCS/AS to acknowledge acceptance of the Monitoring Request and the deletion of the identified monitoring event configuration, if it was requested. If the SCEF received a Monitoring Event Report then it includes the Monitoring Event Report in the Monitoring Response message. If it is a One-time request for an individual UE and the Monitoring Response includes a Monitoring Event Report for the UE, the SCEF deletes the associated Monitoring Event configuration.
  • a Monitoring Response Common, Monitoring Event Report
  • the SCEF sends the Monitor Indication (TLTRI, Cause, Monitoring Event Report) message to the SCS/AS as it receives them from the HSS. Otherwise, it accumulates Monitoring Event for the UEs of the group until the expiration of Group Reporting Guard Time. Upon expiration, the SCEF sends a Monitoring Indication (TLTRI, Cause, list of (External Identifier or MSISDN, Monitoring Event Report) ) message to the SCS/AS. A list of accumulated Monitoring Event Report for each UE identified by either External Identifier or MSISDN is also included.
  • the SCEF uses the list of UE Identities that were received in step 8 and the Number of UEs parameter that was received in step 4a to check if the reports for all the individual group member UEs have been received. If the SCEF determines that a report for all individual group member UEs have been received, the SCEF sends a request to the HSS to delete the associated Monitoring Event configuration for the group.
  • Step 9c For each Monitoring Indication message received in step 9b, the SCS/AS sends a Monitoring Indication Response (Cause) message to the SCEF.
  • Cause Monitoring Indication Response
  • Cause value reflects successful or unsuccessful acknowledgement of Monitoring Indication message.
  • the HSS detects that the current serving MME/SGSN cannot support a requested Monitoring Event or the group-basis monitoring event feature (e.g. after a UE mobility event) , the HSS performs the procedures given below.
  • the HSS shall configure the new MME/SGSN with the Monitoring Event and notify the SCEF of resumption of the suspended Monitoring Event;
  • the HSS and the SCEF shall independently delete the Monitoring Event.
  • FIG. 11a illustrates the procedure of configuring monitoring at the MME/SGSN.
  • the procedure is common for various monitoring event types. Common parameters for this procedure are detailed in clause 5.6.2.2. The steps specific to different Monitoring Event types are detailed in clause 5.6.2.3. This procedure is not applicable for group configuration.
  • the SCS/AS sends a Monitoring Request (SCS/AS Identifier, Monitoring Type, Monitoring Duration, Maximum Number of Reports, T8 Destination Address, TLTRI for Deletion) message to the SCEF.
  • the SCEF assigns a TLTRI that identifies the Monitoring Request.
  • the SCEF stores the TLTRI, and also assigns it to an SCEF Reference ID. Based on operator policies, if either the SCS/AS is not authorized to perform this request (e.g. if the SLA does not allow for it) or the Monitoring Request is malformed or the SCS/AS has exceeded its quota or rate of submitting monitoring requests, the SCEF performs step 6 and provides a Cause value appropriately indicating the error.
  • the SCEF stores the Monitoring Duration, the Maximum Number of Reports, the T8 Destination Address, the SCS/AS Identifier. If the SCEF received a TLTRI for Deletion, the SCEF looks up the SCEF context pointed to by the TLTRI to derive the related SCEF Reference ID for Deletion. If an External Group Identifier (s) was included in the request of step 1, then then flow proceeds to step 2a, otherwise steps 2a and 2b are skipped.
  • the SCEF sends an External Group ID Resolution Request (External Group Identifier (s) ) message to the HSS.
  • the HSS resolves the External Group Identifier (s) , if not identified as Global, to IMSI-Group Identifier (s) and sends an External Group ID Resolution Response (IMSI-Group Identifier (s) ) message to the SCEF.
  • the SCEF sends a Monitoring Request (SCEF ID, SCEF Reference ID, Monitoring Type, Monitoring Duration, Maximum Number of Reports, SCEF Reference ID for Deletion) message to the MME (s) /SGSN (s) .
  • SCEF ID SCEF Reference ID
  • Monitoring Type Monitoring Duration
  • Maximum Number of Reports SCEF Reference ID for Deletion
  • the MME/SGSN examines whether it can accept the request from that SCEF based on operator configuration or whether it serves the SCEF Reference ID for Deletion and can delete it. If acceptable, the MME/SGSN stores SCEF ID, SCEF Reference ID, Monitoring Duration, Maximum Number of Reports and other relevant parameters unless it is a One-time request and the Monitoring Event is available to the MME/SGSN at this time. The MME/SGSN deletes the monitoring configuration identified by the SCEF Reference ID for Deletion, if provided.
  • the MME/SGSN sends a Monitoring Response (SCEF Reference ID, Cause, Monitoring Event Report) message to the SCEF to acknowledge acceptance of the Monitoring Request and to provide the requested monitoring information or to acknowledge the deletion of the identified monitoring event configuration, if it was requested.
  • SCEF Reference ID, Cause, Monitoring Event Report SCEF Reference ID, Cause, Monitoring Event Report
  • the SCEF sends a Monitoring Response (TLTRI, Cause, Monitoring Event Report) message to the SCS/AS to acknowledge acceptance of the Monitoring Request and to provide the requested monitoring information in Monitoring Event Report parameter or to acknowledge the deletion of the identified monitoring event configuration, if it was requested.
  • TLTRI Monitoring Response
  • FIG. 11b illustrates the common procedure flow of reporting Monitoring Events that are detected by the MME/SGSN or HSS. The steps specific to different Monitoring Event types are detailed in clauses 5.6.3.2 to 5.6.3.8.
  • a Monitoring Event is detected by the MME/SGSN at which the Monitoring Event is configured.
  • the HSS also stores the time when the Event is detected or the status is changed.
  • the MME/SGSN sends a Monitoring Indication (SCEF Reference ID (s) , Monitoring Event Report, User Identity) message to the SCEF.
  • SCEF Monitoring Indication
  • the SCEF store the time when it receives the Monitoring Indication.
  • the Monitoring Event configuration is deleted by the MME/SGSN upon completion of this step. If the MME/SGSN has a Maximum Number of Reports stored for this monitoring task, the MME/SGSN shall decrease its value by one. If the value of remaining number of reports is zero, the MME/SGSN shall locally remove the Monitoring Event Configuration. If the Monitoring Event configuration includes User Identity, the MME/SGSN sends the Monitoring Indication message including the User Identity. So that the SCEF can determine what groups the report pertains to, multiple SCEF Reference IDs can be included if the UE is part of multiple groups that require the same monitoring indication.
  • the HSS When reporting for an individual UE or individual Group Member UE, the HSS sends a Monitoring Indication (SCEF Reference ID (s) , External ID or MSISDN, Monitoring Event Report) message to the SCEF. External ID or MSISDN are only included if the indication is associated with an individual Group Member UE. If the Monitoring Event configuration was triggered by a One-time Monitoring Request, then the Monitoring Event configuration for the individual UE and for the individual group member UE is deleted by the HSS upon completion of this step. If the HSS has a Maximum Number of Reports stored for this monitoring task, the HSS shall decrease its value by one. Based on SCEF Reference ID, the SCEF can determine what groups the report pertains to. Multiple SCEF Reference IDs can be included if the UE is part of multiple groups that require the same monitoring indication.
  • SCEF Reference ID SCEF Reference ID
  • Multiple SCEF Reference IDs can be included if the UE is part of multiple groups that require the same monitoring indication.
  • the HSS If Group Reporting Guard Time was provided during the Monitoring Event configuration procedure, the HSS accumulates a Monitoring Event for the UEs of the group within the Group Reporting Guard Time. After the Group Reporting Guard Time expiration, the HSS send a Monitoring Indication (SCEF Reference ID, (Monitoring Event Report (s) , External ID or MSISDN) Set, External Group ID) message to the SCEF. For each group member UE all the Monitoring Event Report and the corresponding stored time (s) are sent to the SCEF.
  • SCEF Reference ID Monitoring Indication
  • the External Group ID may be included in the message to indicate that the event has been detected for all group members.
  • External ID (s) and MSISDN (s) are optional.
  • the HSS may divide the accumulated Monitoring Event Reports into multiple Monitoring indication messages due to the limitation of the message size.
  • the SCEF retrieves the associated TLTRI along with the T8 Destination Address.
  • the SCEF sends a Monitoring Indication (TLTRI, Cause, Monitoring Event Report) message to the identified destination. If the TLTRI refers to a group-based Monitoring Event configuration, and if no Group Reporting Guard Time was set, then the SCEF sends a Monitoring Indication (TLTRI (s) , Cause, Monitoring Event Report) message to the identified destination. So that the SCEF can determine what groups the report pertains to, multiple TLTRIs can be included if the UE is part of multiple groups that require the same monitoring indication.
  • TLTRI refers to a group-based Monitoring Event Configuration
  • Group Reporting Guard Time was provided during the Monitoring Event configuration procedure
  • the SCEF accumulates Monitoring Event for the UEs of the group until the Group Reporting Guard Time expiry.
  • the SCEF sends a Monitoring Indication (TLTRI, Cause, list of (External Identifier or MSISDN, Monitoring Event Report (s) ) ) message to the identified destination.
  • TLTRI Monitoring Indication
  • a list of accumulated Monitoring Event Report for each group member UE identified by either External Identifier or MSISDN is also included.
  • For each group member UE all the received Monitoring Event Report, and the corresponding time received at SCEF or the time value sent by HSS, are sent to the SCS/AS.
  • the SCEF requests the HSS (for monitoring events configured via HSS) to delete the related monitoring event configuration for the individual UE and deletes also its associated Monitoring Event configuration according to the procedure of clause 5.6.1.1 step 3-8.
  • the SCEF shall either:
  • the SCEF uses the identity of individual group member UE (s) (i.e. External Identifier or MSISDN) received in the step 2a or step 2b and the Number of UEs received in step 4a in clause 5.6.1.1 to determine if reporting for the group is complete. If it is complete, the SCEF deletes the associated Monitoring Event configuration for the group.
  • s individual group member UE
  • MSISDN External Identifier
  • the SCS/AS For each Monitoring Indication message received in step 3a, the SCS/AS sends a Monitoring Indication Response (Cause) message to the SCEF.
  • Cause Monitoring Indication Response
  • Cause value reflects successful or unsuccessful acknowledgement of Monitoring Indication message.
  • each of these nodes shall locally delete the related Monitoring Event configuration associated with the individual UE or group member UE or the Global Group.
  • This monitoring event is detected as of step 1b of clause 5.6.3.1, which is when the HSS receives from a serving node an IMEISV that is different from the IMEISV stored by the HSS for the IMSI.
  • Step 2b of clause 5.6.3.1 is executed.
  • Step 3 of clause 5.6.3.1 is executed.
  • the Monitoring Indication message includes the new IMEISV. Operator policies may allow this event to be applied to any UE managed by the HSS (i.e. SCEF may identify an External Group Identifier as Global Group Identifier)
  • This monitoring event is detected as of step 1b of clause 5.6.3.1, which is when the HSS receives from a serving node a serving PLMN ID that is different from the one stored by the HSS.
  • Step 2b of clause 5.6.3.1 is executed.
  • Step 3 of clause 5.6.3.1 is executed.
  • the monitoring information indicates the ID of the serving PLMN and whether it is the home or a roaming PLMN.
  • Operator policies may allow this event to be applied to any UE managed by the HSS (i.e. SCEF may identify an External Group Identifier as Global Group Identifier) . Additional operator policies in the SCEF may restrict the report, e.g. to indicate only whether the UE is in the HSS (i.e. SCEF may identify an External Group Identifier as Global Group Identifier) . Additional operator policies in the SCEF may restrict the report, e.g. to indicate only whether the UE is in the
  • the proposed solution introduces the concept of Global Group Identifier so that it can be used by operators to avoid provisioning of individual UEs within the group.
  • the proposed solution can reduce network signaling since there is not individual signaling for UE group member.
  • the proposed solution can reduce the unnecessary signaling for intermediate reporting on groups involving all UEs for a network.
  • the proposed solution proposes an efficient way to manage the storage for all UEs as a group while maintains backward compatibility within current interfaces towards external applications.
  • the embodiments herein are not limited to the features and advantages mentioned above. A person skilled in the art will recognize additional features and advantages upon reading the following detailed description.
  • FIG. 12 is a block diagram showing an apparatus suitable for practicing some embodiments of the disclosure.
  • any one of the exposure function entity, the application function entity and the data management entity described above may be implemented as or through the apparatus 1200.
  • the apparatus 1200 comprises at least one processor 1221, such as a digital processor (DP) , and at least one memory (MEM) 1222 coupled to the processor 1221.
  • the apparatus 1220 may further comprise a transmitter TX and receiver RX 1223 coupled to the processor 1221.
  • the MEM 1222 stores a program (PROG) 1224.
  • the PROG 1224 may include instructions that, when executed on the associated processor 1221, enable the apparatus 1220 to operate in accordance with the embodiments of the present disclosure.
  • a combination of the at least one processor 1221 and the at least one MEM 1222 may form processing means 1225 adapted to implement various embodiments of the present disclosure.
  • Various embodiments of the present disclosure may be implemented by computer program executable by one or more of the processor 1221, software, firmware, hardware or in a combination thereof.
  • the MEM 1222 may be of any type suitable to 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 memories and removable memories, as non-limiting examples.
  • the processor 1221 may be of any type suitable to the local technical environment, and may include one or more of general purpose computers, special purpose computers, microprocessors, digital signal processors (DSPs) and processors based on multicore processor architecture, as non-limiting examples.
  • general purpose computers special purpose computers
  • microprocessors microprocessors
  • DSPs digital signal processors
  • processors based on multicore processor architecture, as non-limiting examples.
  • the memory 1222 contains instructions executable by the processor 1221, whereby the exposure function entity operates according to any step of any of the methods related to the exposure function entity as described above.
  • the memory 1222 contains instructions executable by the processor 1221, whereby the data management entity operates according to any step of the methods related to the data management entity as described above.
  • the memory 1222 contains instructions executable by the processor 1221, whereby the application function entity operates according to any step of the methods related to the application function entity as described above.
  • FIG. 13 is a block diagram showing an exposure function entity according to an embodiment of the disclosure.
  • the exposure function entity 1300 comprises a receiving module 1302 and a sending module 1304.
  • the receiving module 1302 may be configured to receive a first monitoring request from an application function entity.
  • the first monitoring request comprises an external group identifier identifying all user equipments (UEs) managed by a data management entity.
  • the sending module 1304 may be configured to send a second monitoring request to the data management entity, wherein the second monitoring request comprises the external group identifier identifying all UEs managed by the data management entity.
  • UEs user equipments
  • FIG. 14 is a block diagram showing a data management entity according to an embodiment of the disclosure.
  • the data management entity 1400 comprises a receiving module 1402 and a handling module 1404.
  • the receiving module 1402 may be configured to receive a second monitoring request from an exposure function entity.
  • the second monitoring request comprises the external group identifier identifying all UEs managed by the data management entity.
  • the handling module 1404 may be configured to handle the second monitoring request.
  • FIG. 15 is a block diagram showing an application function entity according to an embodiment of the disclosure.
  • the application function entity 1500 comprises a sending module 1502.
  • the sending module 1502 may be configured to send a first monitoring request to an exposure function entity.
  • the first monitoring request comprises an external group identifier identifying all user equipments (UEs) managed by the data management entity.
  • UEs user equipments
  • unit or module may have conventional meaning in the field of electronics, electrical devices and/or electronic devices and may include, for example, electrical and/or electronic circuitry, devices, modules, processors, memories, logic solid state and/or discrete devices, computer programs or instructions for carrying out respective tasks, procedures, computations, outputs, and/or displaying functions, and so on, as such as those that are described herein.
  • the exposure function entity, the application function entity or the data management entity may not need a fixed processor or memory, any computing resource and storage resource may be arranged from the exposure function entity, the application function entity or the data management entity in the communication system.
  • the introduction of virtualization technology and network computing technology may improve the usage efficiency of the network resources and the flexibility of the network.
  • a computer program product being tangibly stored on a computer readable storage medium and including instructions which, when executed on at least one processor, cause the at least one processor to carry out any of the methods as described above.
  • a computer-readable storage medium storing instructions which when executed by at least one processor, cause the at least one processor to carry out any of the methods as described above.
  • the present disclosure may also provide a carrier containing the computer program as mentioned above, wherein the carrier is one of an electronic signal, optical signal, radio signal, or computer readable storage medium.
  • the computer readable storage medium can be, for example, an optical compact disk or an electronic memory device like a RAM (random access memory) , a ROM (read only memory) , Flash memory, magnetic tape, CD-ROM, DVD, Blue-ray disc and the like.
  • an apparatus implementing one or more functions of a corresponding apparatus described with an embodiment comprises not only prior art means, but also means for implementing the one or more functions of the corresponding apparatus described with the embodiment and it may comprise separate means for each separate function or means that may be configured to perform one or more functions.
  • these techniques may be implemented in hardware (one or more apparatuses) , firmware (one or more apparatuses) , software (one or more modules) , or combinations thereof.
  • firmware or software implementation may be made through modules (e.g., procedures, functions, and so on) that perform the functions described herein.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Databases & Information Systems (AREA)
  • Mobile Radio Communication Systems (AREA)
  • Telephonic Communication Services (AREA)

Abstract

Des modes de réalisation de la présente divulgation concernent des procédés et des appareils de surveillance d'événements. Un procédé comprend la réception d'une première demande de surveillance en provenance d'une entité de fonctionnement d'application. La première demande de surveillance comprend un identifiant de groupe externe identifiant tous les équipements d'utilisateur (UE) gérés par une entité de gestion de données. Le procédé comprend en outre l'envoi d'une seconde demande de surveillance à l'entité de gestion de données. La seconde demande de surveillance comprend l'identifiant de groupe externe identifiant tous les UE gérés par l'entité de gestion de données.
PCT/CN2021/106811 2020-07-17 2021-07-16 Procédé et appareil de surveillance d'événements WO2022012674A1 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CNPCT/CN2020/102739 2020-07-17
CN2020102739 2020-07-17

Publications (1)

Publication Number Publication Date
WO2022012674A1 true WO2022012674A1 (fr) 2022-01-20

Family

ID=79554490

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2021/106811 WO2022012674A1 (fr) 2020-07-17 2021-07-16 Procédé et appareil de surveillance d'événements

Country Status (1)

Country Link
WO (1) WO2022012674A1 (fr)

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN109150560A (zh) * 2017-06-15 2019-01-04 中兴通讯股份有限公司 物联网组监控的设置方法、系统及计算机可读存储介质
US20190028866A1 (en) * 2016-01-18 2019-01-24 Samsung Electronics Co., Ltd. Method and apparatus for communication of terminal in mobile communication system
CN110366199A (zh) * 2018-04-09 2019-10-22 华为技术有限公司 一种事件监控方法及装置

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20190028866A1 (en) * 2016-01-18 2019-01-24 Samsung Electronics Co., Ltd. Method and apparatus for communication of terminal in mobile communication system
CN109150560A (zh) * 2017-06-15 2019-01-04 中兴通讯股份有限公司 物联网组监控的设置方法、系统及计算机可读存储介质
CN110366199A (zh) * 2018-04-09 2019-10-22 华为技术有限公司 一种事件监控方法及装置

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
HUAWEI: "Procedures for monitoring", 3GPP DRAFT; C3-182508 WAS 2489 WAS 2294 WAS 2025 NAPS-CT_AI_15.4.1_PROCEDURES FOR MONITORING, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE, vol. CT WG3, no. Kunming, China; 20180416 - 20180420, 23 April 2018 (2018-04-23), Mobile Competence Centre ; 650, route des Lucioles ; F-06921 Sophia-Antipolis Cedex ; France , XP051435252 *

Similar Documents

Publication Publication Date Title
US10039072B2 (en) System and method for providing power saving mode enhancements in a network environment
CN112205015B (zh) 用于策略分发的方法、装置和计算机可读介质
KR102585690B1 (ko) 사용량 모니터링 데이터 제어
CN113056928B (zh) 用于事件监视的方法和装置
US9699725B1 (en) System and method for providing power saving mode enhancements in a network environment
JP7499939B2 (ja) ロケーションサービスのための方法及び装置
US20210352464A1 (en) Methods and apparatuses for event monitoring
WO2021180170A1 (fr) Procédé et appareil de transfert intercellulaire
WO2021136651A1 (fr) Procédé et appareil de gestion de disponibilité d'un dispositif terminal
WO2022012674A1 (fr) Procédé et appareil de surveillance d'événements
CN116803112A (zh) 用于动态发现核心网络中的服务网络节点的方法、网络节点和计算机可读介质
WO2023143385A1 (fr) Procédé et appareil de formation de groupe fondé sur la localisation
WO2022083736A1 (fr) Procédé et appareil de surveillance de configuration d'événement
WO2023051772A1 (fr) Procédé et appareil de rapport d'événement
WO2022152209A1 (fr) Procédé et appareil d'extraction d'informations de routage
WO2023274366A1 (fr) Procédé et appareil d'établissement de session avec une qualité de service requise
US20220353668A1 (en) Methods, network function nodes and computer readable media for contents communication management
CN113748703A (zh) 用于配置终端设备的监视的方法和装置
CN117859353A (zh) 用于会话恢复的方法和装置
JP2024056680A (ja) 無線通信ネットワークにおけるｉｐアドレス割り当て
CN117242745A (zh) 接入和移动性策略控制

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 21841420

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 21841420

Country of ref document: EP

Kind code of ref document: A1