WO2020155177A1 - Procédés et appareils permettant de surveiller un service d'événement pour un groupe de dispositifs terminaux - Google Patents

Procédés et appareils permettant de surveiller un service d'événement pour un groupe de dispositifs terminaux Download PDF

Info

Publication number
WO2020155177A1
WO2020155177A1 PCT/CN2019/074691 CN2019074691W WO2020155177A1 WO 2020155177 A1 WO2020155177 A1 WO 2020155177A1 CN 2019074691 W CN2019074691 W CN 2019074691W WO 2020155177 A1 WO2020155177 A1 WO 2020155177A1
Authority
WO
WIPO (PCT)
Prior art keywords
group
request
update
terminal device
management node
Prior art date
Application number
PCT/CN2019/074691
Other languages
English (en)
Inventor
Hao Zeng
Jingrui TAO
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)
Priority to PCT/CN2019/074691 priority Critical patent/WO2020155177A1/fr
Publication of WO2020155177A1 publication Critical patent/WO2020155177A1/fr

Links

Images

Classifications

    • 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
    • H04W24/00—Supervisory, monitoring or testing arrangements
    • H04W24/08—Testing, supervising or monitoring using real traffic
    • 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
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W24/00—Supervisory, monitoring or testing arrangements
    • H04W24/04—Arrangements for maintaining operational condition
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
    • H04W4/06—Selective distribution of broadcast services, e.g. multimedia broadcast multicast service [MBMS]; Services to user groups; One-way selective calling services
    • H04W4/08—User group management
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W8/00—Network data management
    • H04W8/02—Processing of mobility data, e.g. registration information at HLR [Home Location Register] or VLR [Visitor Location Register]; Transfer of mobility data, e.g. between HLR, VLR or external networks
    • H04W8/08—Mobility data transfer
    • H04W8/12—Mobility data transfer between location registers or mobility servers

Definitions

  • Embodiments of the disclosure generally relate to wireless communication, and, more particularly, to methods and apparatuses for monitoring event service for a group of terminal devices.
  • a CIoT device such as a user equipment (UE) may adopt a power saving mechanism, e.g. power saving mode (PSM) and extended idle mode discontinuous reception (DRX) .
  • PSM power saving mode
  • DRX extended idle mode discontinuous reception
  • a UE in PSM or DRX is not immediately reachable for mobile terminating services. It is available for mobile terminating services during the time it is in connected mode and for the period of an active time that is after the connected mode. Therefore, it is important for a service capability server (SCS) /application server (AS) to monitor the UE status, e.g. UE reachability, UE location, etc.
  • SCS service capability server
  • AS application server
  • One of the objects of the disclosure is to provide an improved solution for monitoring event service for a group of terminal devices.
  • a method in a subscriber management node comprises receiving, from a network exposure node, a first request for subscribing to a monitoring event for a group of terminal devices.
  • the method further comprises sending, to one or more mobility management nodes, second requests for initiating configuration of the monitoring event for terminal devices of the group.
  • the method further comprises, in response to at least one terminal device being added into or deleted from the group when the initiated configuration is active, sending, to a mobility management node, a third request for initiating or deleting configuration of the monitoring event for the at least one terminal device.
  • the traffic between the subscriber management node and the mobility management node (s) can be decreased for the update of group members when there is an active configuration for the group.
  • the method may further comprise sending, to the network exposure node, information about an update of the group due to the addition or deletion of the at least one terminal device.
  • the information about the update of the group may comprise a number of terminal devices in the updated group and identity (ID) information of the at least one terminal device.
  • the first request may comprise a first indicator indicating whether the subscriber management node is allowed to update the initiated configuration when the initiated configuration is active.
  • the third request may be sent when the first indicator indicates that the update of the initiated configuration is allowed.
  • the third request may be sent when the first indicator indicates that the update of the initiated configuration is not allowed, but an operator policy allows the update of the initiated configuration.
  • the method may further comprise exchanging, with the network exposure node, information about whether the update of the initiated configuration is supported.
  • the first indicator may indicate that the update of the initiated configuration is allowed when both the subscriber management node and the network exposure node support the update of the initiated configuration.
  • the first request may comprise a second indicator instructing a terminal device to reattach a network when the terminal device is added into the group.
  • Each of the second requests may comprise the second indicator.
  • the third request may comprise the second indicator when the at least one terminal device is added into the group.
  • the first request may be a Monitoring Request message.
  • Each of the second requests may be an Insert Subscriber Data Request message.
  • the third request may be an Insert Subscriber Data Request message.
  • the information about whether the update of the initiated configuration is supported by the network exposure node may be received in a Configuration Information Request (CIR) command.
  • CIR Configuration Information Request
  • CIA Configuration Information Answer
  • a method in a network exposure node comprises receiving, from a server, a first request for subscribing to a monitoring event for a group of terminal devices.
  • the method further comprises sending, to a subscriber management node, a second request for subscribing to the monitoring event for the group of terminal devices.
  • the method further comprises receiving, from the subscriber management node, information about an update of the group due to at least one terminal device added into or deleted from the group when the subscribed monitoring event is active.
  • the method further comprises sending the information about the update of the group to the server.
  • the information about the update of the group may comprise a number of terminal devices in the updated group and ID information of the at least one terminal device.
  • each of the first and second requests may comprise a first indicator indicating whether the subscriber management node is allowed to update an initiated configuration of the monitoring event for the group when the initiated configuration is active.
  • the method may further comprise exchanging, with the subscriber management node, information about whether the update of the initiated configuration is supported.
  • the first indicator in the first request may indicate that the update of the initiated configuration is allowed.
  • the first indicator in the second request may indicate that the update of the initiated configuration is allowed when both the subscriber management node and the network exposure node support the update of the initiated configuration.
  • each of the first and second requests may comprise a second indicator instructing a terminal device to reattach a network when the terminal device is added into the group.
  • each of the first and second requests may be a Monitoring Request message.
  • the information about the update of the group may be received and sent in a Monitoring Indication message.
  • the information about whether the update of the initiated configuration is supported by the network exposure node may be sent in a CIR command.
  • the information about whether the update of the initiated configuration is supported by the subscriber management node may be received in a CIA command.
  • a method in a server comprises sending, to a network exposure node, a request for subscribing to a monitoring event for a group of terminal devices.
  • the method further comprises receiving, from the network exposure node, information about an update of the group due to at least one terminal device added into or deleted from the group when the subscribed monitoring event is active.
  • the request may comprise a first indicator indicating whether a subscriber management node is allowed to update an initiated configuration of the monitoring event for the group when the initiated configuration is active.
  • the request may comprise a second indicator instructing a terminal device to reattach a network when the terminal device is added into the group.
  • the request may be a Monitoring Request message.
  • the information about the update of the group may be received in a Monitoring Indication message.
  • a method in a mobility management node comprises receiving, from a subscriber management node, a request for initiating configuration of a monitoring event for a terminal device in a group of terminal devices.
  • the request comprises an indicator instructing the terminal device to reattach a network when the terminal device is added into the group.
  • the method further comprises instructing the terminal device to reattach the network according to the indicator.
  • the request may be an Insert Subscriber Data Request message.
  • a subscriber management node comprises at least one processor and at least one memory.
  • the at least one memory contains instructions executable by the at least one processor, whereby the subscriber management node is operative to receive, from a network exposure node, a first request for subscribing to a monitoring event for a group of terminal devices.
  • the subscriber management node is further operative to send, to one or more mobility management nodes, second requests for initiating configuration of the monitoring event for terminal devices of the group.
  • the subscriber management node is further operative to, in response to at least one terminal device being added into or deleted from the group when the initiated configuration is active, send, to a mobility management node, a third request for initiating or deleting configuration of the monitoring event for the at least one terminal device.
  • the subscriber management node may be operative to perform the method according to the above first aspect.
  • a network exposure node comprises at least one processor and at least one memory.
  • the at least one memory contains instructions executable by the at least one processor, whereby the network exposure node is operative to receive, from a server, a first request for subscribing to a monitoring event for a group of terminal devices.
  • the network exposure node is further operative to send, to a subscriber management node, a second request for subscribing to the monitoring event for the group of terminal devices.
  • the network exposure node is further operative to receive, from the subscriber management node, information about an update of the group due to at least one terminal device added into or deleted from the group when the subscribed monitoring event is active.
  • the network exposure node is further operative to send the information about the update of the group to the server.
  • the network exposure node may be operative to perform the method according to the above second aspect.
  • a server comprising at least one processor and at least one memory.
  • the at least one memory contains instructions executable by the at least one processor, whereby the server is operative to send, to a network exposure node, a request for subscribing to a monitoring event for a group of terminal devices.
  • the server is further operative to receive, from the network exposure node, information about an update of the group due to at least one terminal device added into or deleted from the group when the subscribed monitoring event is active.
  • the server may be operative to perform the method according to the above third aspect.
  • a mobility management node comprises at least one processor and at least one memory.
  • the at least one memory contains instructions executable by the at least one processor, whereby the mobility management node is operative to receive, from a subscriber management node, a request for initiating configuration of a monitoring event for a terminal device in a group of terminal devices.
  • the request comprises an indicator instructing the terminal device to reattach a network when the terminal device is added into the group.
  • the mobility management node is further operative to instruct the terminal device to reattach the network according to the indicator.
  • the mobility management node may be operative to perform the method according to the above fourth aspect.
  • the computer program product comprises instructions which when executed by at least one processor, cause the at least one processor to perform the method according to any of the above first to fourth aspects.
  • a computer readable storage medium comprises instructions which when executed by at least one processor, cause the at least one processor to perform the method according to any of the above first to fourth aspects.
  • a subscriber management node comprises a reception module for receiving, from a network exposure node, a first request for subscribing to a monitoring event for a group of terminal devices.
  • the subscriber management node further comprises a first sending module for sending, to one or more mobility management nodes, second requests for initiating configuration of the monitoring event for terminal devices of the group.
  • the subscriber management node further comprises a second sending module for, in response to at least one terminal device being added into or deleted from the group when the initiated configuration is active, sending, to a mobility management node, a third request for initiating or deleting configuration of the monitoring event for the at least one terminal device.
  • a network exposure node comprises a first reception module for receiving, from a server, a first request for subscribing to a monitoring event for a group of terminal devices.
  • the network exposure node further comprises a first sending module for sending, to a subscriber management node, a second request for subscribing to the monitoring event for the group of terminal devices.
  • the network exposure node further comprises a second reception module for receiving, from the subscriber management node, information about an update of the group due to at least one terminal device added into or deleted from the group when the subscribed monitoring event is active.
  • the network exposure node further comprises a second sending module for sending the information about the update of the group to the server.
  • a server comprising a sending module for sending, to a network exposure node, a request for subscribing to a monitoring event for a group of terminal devices.
  • the server further comprises a reception module for receiving, from the network exposure node, information about an update of the group due to at least one terminal device added into or deleted from the group when the subscribed monitoring event is active.
  • a mobility management node comprises a reception module for receiving, from a subscriber management node, a request for initiating configuration of a monitoring event for a terminal device in a group of terminal devices.
  • the request comprises an indicator instructing the terminal device to reattach a network when the terminal device is added into the group.
  • the mobility management node comprises an instruction module for instructing the terminal device to reattach the network according to the indicator.
  • FIG. 1 shows an example of the existing message flow for update of UE group
  • FIG. 2 is a diagram showing an exemplary communication system into which an embodiment of the disclosure is applicable
  • FIG. 3 is a flowchart illustrating a method implemented at a subscriber management node according to an embodiment of the disclosure
  • FIG. 4 is a flowchart illustrating a method implemented at a network exposure node according to an embodiment of the disclosure
  • FIG. 5 is a flowchart illustrating a method implemented at a server according to an embodiment of the disclosure
  • FIG. 6 is a flowchart illustrating a method implemented at a mobility management node according to an embodiment of the disclosure
  • FIGs. 7A-7B are flowcharts illustrating an exemplary process according to an embodiment of the disclosure.
  • FIG. 8 is a block diagram showing an apparatus suitable for use in practicing some embodiments of the disclosure.
  • FIG. 9 is a block diagram showing a subscriber management node according to an embodiment of the disclosure.
  • FIG. 10 is a block diagram showing a network exposure node according to an embodiment of the disclosure.
  • FIG. 11 is a block diagram showing a server according to an embodiment of the disclosure.
  • FIG. 12 is a block diagram showing a mobility management node according to an embodiment of the disclosure.
  • the network resolves the group to each individual member (each UE within the group) and configures the requested event (e.g. UE reachability) in the corresponding node (e.g. mobility management entity simply referred to as MME) serving each UE.
  • MME mobility management entity
  • the network in particular a home subscriber server simply referred to as an HSS
  • a million messages are required to inform the serving node (s) about the configuration being ended/deleted.
  • the monitoring event has been configured for a large group (e.g. a group having thousands of UEs) , it is difficult to add a new individual member UE to the group or delete a given UE from the group when there is a configuration already initiated or activated in the network.
  • a large group e.g. a group having thousands of UEs
  • each car has a UE identity (ID) e.g. a subscriber identification module (SIM) card.
  • ID e.g. a subscriber identification module (SIM) card.
  • SIM subscriber identification module
  • the cars may be grouped by an External Group ID since they are to be treated in the same manner when it comes to configuration.
  • the fleet management system may want to use group monitoring event function to monitor all cars (e.g., location reporting, roaming status, change of IMSI-IMEI (SV) association) .
  • IMSI refers to international mobile subscriber identification number
  • IMEI refers to international mobile equipment identity
  • SV refers to software version.
  • the cars may be rented from some third companies. Due to certain conditions (such as cars are broken, the lease ends, etc. ) , some cars will be removed from the group and some other cars will be added to the group.
  • the first problem is that the current procedures do not allow “hot” addition/removal of UE (s) for a group.
  • the term “hot” means an active configuration exists for the group.
  • an SCS/AS configures an event for a group, then after the configuration, if there is a new UE added into the group, the new added UE will not be monitored by the SCS/AS. Also, after the configuration, if there is an existing UE removed from the group, the removed UE will still be monitored by the SCS/AS. But in many cases, the SCS/AS wants to always monitor the event for the latest/updated group.
  • the SCS/AS wants to always monitor the event for the latest/updated group, whenever the group is changed, the SCS/AS should delete the previous monitoring event configuration for the group identified by the External Group ID, and then reconfigure a new monitoring event configuration using the same External Group ID.
  • the UE group information is stored in an HSS and there is no interface between the SCS/AS and the HSS to monitor the UE group. Based on the current Monitoring Event procedure, each time when a UE is added into/deleted from the group in the HSS, the SCS/AS does not know the group change. So the SCS/AS does not know when to delete the previous monitoring event configuration and reconfigure a new monitoring event for the group.
  • the second problem is that the traffic between HSS and MME/SGSN will be huge if only a few UEs are added into/deleted from a huge group.
  • the term SGSN refers to serving general packet radio service (GPRS) support node.
  • GPRS general packet radio service
  • the traffic between the HSS and the MME/SGSN is huge since the HSS must send an Insert Subscriber Data Request message to the MME/SGSN for each group member UE to delete/initiate the monitoring configuration.
  • FIG. 1 shows an example message flow for adding UE (s) into or deleting UE (s) from a group which has 10,000 UEs.
  • the present disclosure proposes an improved solution for monitoring event service for a group of terminal devices.
  • the solutions will be described in detail with reference to FIGs. 2-12.
  • the term “communication system” refers to a system following any suitable communication standards, such as the first generation (1G) , 2G, 2.5G, 2.75G, 3G, 4G, 4.5G, 5G communication protocols, and/or any other protocols either currently known or to be developed in the future.
  • the communications between a terminal device and a network node in the communication system may be performed according to any suitable generation communication protocols, including, but not limited to, 1G, 2G, 2.5G, 2.75G, 3G, 4G, 4.5G, 5G communication protocols, and/or any other protocols either currently known or to be developed in the future.
  • different terms may refer to a same or similar network function or network node with the same or similar functionality in different communication systems.
  • the network exposure function may be called SCEF in 4G and NEF in 5G respectively.
  • SCS/AS and AF used herein may refer to a network function or node with the same or similar functionality in 4G and 5G respectively.
  • HSS and UDM used herein may refer to a network function or node with the same or similar functionality in 4G and 5G respectively.
  • MME and AMF used herein may refer to a network function or node with the same or similar functionality in 4G and 5G respectively.
  • the specific terms used herein do not limit the present disclosure only to the communication system related to the specific terms, which however can be more generally applied to other communication systems.
  • FIG. 2 is a diagram showing an exemplary communication system into which an embodiment of the disclosure is applicable.
  • the communication system comprises a user equipment (UE) 202, a radio access network (RAN) 204, a serving GPRS support node (SGSN) 206, a mobility management entity (MME) 208, a serving gateway (SGW) 210, a gateway GPRS support node (GGSN) /packet data network (PDN) gateway (PGW) 212, a service capability exposure function (SCEF) 214, a service capability server (SCS) 216, an application server (AS) 218 and a home subscriber server (HSS) 220.
  • UE user equipment
  • RAN radio access network
  • MME mobility management entity
  • SGW serving gateway
  • GGSN gateway GPRS support node
  • PDN packetet data network gateway
  • SCEF service capability exposure function
  • SCS service capability server
  • AS application server
  • HSS home subscriber server
  • the UE 202 can communicate through a radio access communication link with the RAN 204.
  • the UE may also be referred to as, for example, terminal device, access terminal, mobile station, mobile unit, subscriber station, or the like. It may refer to any end device that can access a wireless communication network and receive services therefrom.
  • the UE may include a portable computer, an image capture terminal device such as a digital camera, a gaming terminal device, a music storage and playback appliance, a mobile phone, a cellular phone, a smart phone, a tablet, a wearable device, a personal digital assistant (PDA) , or the like.
  • PDA personal digital assistant
  • a UE 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 UE and/or a network equipment.
  • the UE may be a machine-to-machine (M2M) device, which may, in a 3rd generation partnership project (3GPP) context, be referred to as a machine-type communication (MTC) device.
  • M2M machine-to-machine
  • 3GPP 3rd generation partnership project
  • MTC machine-type communication
  • machines or devices may include sensors, metering devices such as power meters, industrial machineries, bikes, vehicles, or home or personal appliances, e.g. refrigerators, televisions, personal wearables such as watches, and so on.
  • the RAN 204 may include, for example, a universal mobile telecommunications system (UMTS) terrestrial RAN (UTRAN) , a global system for mobile communication (GSM) enhanced data rate for GSM evolution (EDGE) RAN (GERAN) , and/or an evolved universal terrestrial RAN (E-UTRAN) .
  • UMTS universal mobile telecommunications system
  • UTRAN universal mobile telecommunications system
  • GSM global system for mobile communication
  • EDGE enhanced data rate for GSM evolution
  • GERAN global system for mobile communication
  • E-UTRAN can each include radio network controller (RNC) nodes to control communications through radio base stations providing radio access communication links to UEs that are within their respective communication service cells.
  • the E-UTRAN can include radio base station nodes (eNodeBs or eNBs) that can provide the combined functionality of the RNC nodes and base stations of the UTRAN and the GERAN.
  • eNodeBs or eNBs radio base station nodes
  • the SGSN 206 is a core network node in the UMTS and has a user-plane function and a control-plane function.
  • the user-plane function of the SGSN 206 can transfer user data packets of the UE 202 between the RAN 204 and the GGSN/PGW 212.
  • the control-plane function of the SGSN 206 can carry out mobility management of the UE 202, bearer management and the like.
  • the MME 208 is a core network node in evolved packet system (EPS) and can carry out the mobility management of the UE 202, the bearer management, and the like.
  • the SGW 210 is a packet transfer node in the core network of the EPS.
  • the SGW 210 can transfer user data packets of the UE 202 between the RAN 204 and the GGSN/PGW 212.
  • the GGSN is a core network node in the UMTS.
  • the PGW is a core network node in the EPS.
  • the GGSN/PGW 212 means either the GGSN or the PGW or both.
  • the GGSN/PGW 212 is a user-plane packet transfer node in the core network and can transfer user data packets of the UE 202.
  • the GGSN/PGW 212 can serve as a gateway to an external PDN and provide the UE 202 with the connectivity to the external PDN.
  • the SCEF 214 can securely expose the services and capabilities provided by 3GPP networks by providing access to the services and capabilities through homogenous network application programming interfaces (APIs) defined by open mobile alliance (OMA) , GSM alliance (GSMA) and possibly other standardization bodies.
  • the SCS 216 can make open service access (OSA) standard interfaces accessible by application and provide an abstraction of network protocol for application developers. As a gateway between applications and the network, the SCS 220 can accomplish mapping of OSA interfaces onto network protocols and vice versa.
  • the AS 218 may be a type of server designed to install, operate and host applications and associated services for users.
  • the HSS 220 is a control-plane node in the core network of 3GPP public land mobile network (PLMN) and can manage subscriber information of the UE 202.
  • PLMN public land mobile network
  • the communication system may further comprise a mobile switching center (MSC) 222, a short message service (SMS) -service center (SC) /gateway mobile switching center (GMSC) /interworking MSC (IWMSC) 224, a short message entity (SME) 226, an Internet protocol (IP) -short message (SM) -gateway (GW) 228, a machine-type communication (MTC) -interworking function (IWF) 230, a charge data function (CDF) /charge gateway function (CGF) 232 and an MTC-authentication, authorization and accounting (AAA) 234.
  • MSC mobile switching center
  • SMS short message service
  • SC gateway mobile switching center
  • IWMSC interworking MSC
  • SME short message entity
  • IP Internet protocol
  • SM Internet protocol
  • GW Internet protocol
  • MTC machine-type communication
  • CDF charge data function
  • CGF charge gateway function
  • AAA MTC-authentication, authorization and accounting
  • the MME 208, the SCEF 214, the SCS/AS and the HSS 220 are merely exemplary examples of the components in the communication system and may be replaced by components with similar functionalities.
  • the MME may be replaced by an access and mobility management function (AMF)
  • the SCEF may be replaced by a network exposure function (NEF)
  • the SCS/AS may be replaced by an application function (AF)
  • the HSS may be replaced by a unified data management (UDM) .
  • FIG. 3 is a flowchart illustrating a method implemented at a subscriber management node according to an embodiment of the disclosure.
  • the subscriber management node may be an HSS, a UDM, or any other entity having similar functionality.
  • the subscriber management node receives, from a network exposure node, a first request for subscribing to a monitoring event for a group of terminal devices.
  • the network exposure node may be an SCEF, an NEF, or any other entity having similar functionality.
  • the first request may include ID information of the group and the type of the monitoring event.
  • the first request may be a Monitoring Request message
  • the ID information may be an external group ID of the group
  • the type of the monitoring event may be UE reachability, UE location, or the like.
  • the first request may include a first indicator indicating whether the subscriber management node is allowed to update an initiated configuration of the monitoring event for the group when the initiated configuration is active and particularly when the group of terminal devices is updated.
  • the subscriber management node exchanges, with the network exposure node, information about whether the update of the initiated configuration is supported.
  • the information about whether the network exposure node supports the update of the initiated configuration may be received by the subscriber management node in a Configuration Information Request (CIR) command.
  • CIR Configuration Information Request
  • the information about whether the subscriber management node supports the update of the initiated configuration may be sent by the subscriber management node in a Configuration Information Answer (CIA) command.
  • the network exposure node may set the first indicator to indicate that the update of the initiated configuration is allowed in a case that both the subscriber management node and the network exposure node support the update of the initiated configuration.
  • the first request may include a second indicator instructing a terminal device to reattach a network when the terminal device is added into the group.
  • the second indicator indicates the subscriber management node to request a corresponding mobility management node to instruct reattachment of the terminal device to the network.
  • the subscriber management node sends, to one or more mobility management nodes, second requests for initiating configuration of the monitoring event for terminal devices of the group.
  • the mobility management node may be an MME, an AMF, or any other entity having similar functionality.
  • the subscriber management node may send, for each terminal device in the group, a second request to a corresponding mobility management node serving the terminal device.
  • the second request may include the ID information of the group and the type of the monitoring event, which are indicated in the first request.
  • the second request may be an Insert Subscriber Data Request message.
  • the first request includes the second indicator
  • the second request also includes the second indicator.
  • the subscriber management node in response to at least one terminal device being added into or deleted from the group when the initiated configuration is active, sends, to a mobility management node, a third request for initiating or deleting configuration of the monitoring event for the at least one terminal device.
  • the subscriber management node manages the subscriber information of terminal devices, when a new terminal device associated with the group ID information (e.g. external group ID) accesses the network or when an existing group member terminal device associated with the group ID information exits the network, such situation can be known by the subscriber management node.
  • the subscriber management node may send, for every such (e.g. new or existing group member) terminal device, a third request to a corresponding mobility management node serving the terminal device.
  • the third request may include the ID information of the group and the type of the monitoring event, which are indicated in the first request.
  • the third request may be an Insert Subscriber Data Request message.
  • the first request includes the second indicator and a terminal device is added into the group, the third request also includes the second indicator.
  • the telecom network can be provided with a way to automatically update the monitoring event configuration for added/deleted terminal device (or UE) in the group identified by the group ID information (e.g. External Group ID) .
  • the server e.g. SCS/AS
  • the server does not need to keep monitoring the UE group change on the subscriber management node (e.g. HSS) .
  • the SCS/AS also does not need to delete and reconfigure the monitoring event configuration identified by the External Group ID.
  • the traffic between the HSS and the mobility management node can be reduced much since the HSS only sends a third request (e.g. Insert Subscriber Data Request) to the MME/SGSN for each added/deleted individual group member UEs.
  • a third request e.g. Insert Subscriber Data Request
  • Insert Subscriber Data Request e.g. Insert Subscriber Data Request
  • the third request may be sent when the first indicator indicates that the update of the initiated configuration is allowed.
  • the subscriber management node e.g. HSS
  • SCEF network exposure node
  • the HSS will reject the UE addition/removal until the active configuration for the group is ended.
  • the third request may be sent when the first indicator indicates that the update of the initiated configuration is not allowed, but an operator policy allows the update of the initiated configuration. This is in consideration of the fact that the operator might want to allow the addition/removal of a UE even though the SCEF does not support the dynamic update feature.
  • the subscriber management node sends, to the network exposure node, information about an update of the group due to the addition or deletion of the at least one terminal device. Since such information can be forwarded by the network exposure node to the server (e.g. SCS/AS) , the telecom network can be provided with a way to notify the server about the UE group change on the subscriber management node.
  • the information about the update of the group may comprise the number of terminal devices in the updated group and ID information of the at least one terminal device.
  • FIG. 4 is a flowchart illustrating a method implemented at a network exposure node according to an embodiment of the disclosure.
  • the network exposure node may be an SCEF, an NEF, or any other entity having similar functionality.
  • the network exposure node receives, from a server, a first request for subscribing to a monitoring event for a group of terminal devices.
  • the server may be an SCS, an AS, an application function (AF) , or any other entity having similar functionality.
  • the first request may include ID information of the group and the type of the monitoring event.
  • the first request may be Monitoring Request message
  • the ID information may be an external group ID of the group
  • the type of the monitoring event may be UE reachability, UE location, or the like.
  • the first request may include a first indicator indicating whether the subscriber management node is allowed to update an initiated configuration of the monitoring event for the group when the initiated configuration is active and particularly when the group of terminal devices is updated.
  • the first request may include a second indicator instructing a terminal device to reattach a network when the terminal device is added into the group.
  • the network exposure node sends, to the subscriber management node, a second request for subscribing to the monitoring event for the group of terminal devices.
  • the second request may include the ID information of the group and the type of the monitoring event, which are indicated in the first request.
  • the second request may be a Monitoring Request message.
  • the network exposure node may exchange at block 402, with a subscriber management node, information about whether the update of the initiated configuration is supported.
  • the information about whether the network exposure node supports the update of the initiated configuration may be sent by the network exposure node in a CIR command.
  • the information about whether the subscriber management node supports the update of the initiated configuration may be received by the network exposure node in a CIA command.
  • the network exposure node may set the first indicator in the second request to indicate that the update of the initiated configuration is allowed if both the subscriber management node and the network exposure node support the update of the initiated configuration and if the first indicator in the first request indicates that the update of the initiated configuration is allowed.
  • the second request also includes the second indicator.
  • the network exposure node receives, from the subscriber management node, information about an update of the group due to at least one terminal device added into or deleted from the group when the subscribed monitoring event is active.
  • the information about the update of the group may comprise the number of terminal devices in the updated group and ID information of the at least one terminal device.
  • the number of terminal devices in the updated group may be used by the network exposure node to determine whether reporting for the group is complete. For example, the reporting for the group may be complete when all terminal devices have reached the maximum number of reports requested initially by the server.
  • the network exposure node sends the information about the update of the group to the server.
  • the telecom network can be provided with a way to notify the server about the UE group change on the subscriber management node.
  • the information about the update of the group may be received at block 408 and sent at block 410 in a Monitoring Indication message.
  • FIG. 5 is a flowchart illustrating a method implemented at a server according to an embodiment of the disclosure.
  • the server may be an SCS, an AS, an application function (AF) , or any other entity having similar functionality.
  • the server sends, to a network exposure node, a request for subscribing to a monitoring event for a group of terminal devices.
  • Block 502 corresponds to block 404 and its details are omitted here.
  • the server receives, from the network exposure node, information about an update of the group due to at least one terminal device added into or deleted from the group when the subscribed monitoring event is active.
  • Block 504 corresponds to block 410 and its details are omitted here.
  • FIG. 6 is a flowchart illustrating a method implemented at a mobility management node according to an embodiment of the disclosure.
  • the mobility management node may be an MME, an AMF, or any other entity having similar functionality.
  • the mobility management node receives, from a subscriber management node, a request for initiating configuration of a monitoring event for a terminal device in a group of terminal devices.
  • the request comprises an indicator instructing the terminal device to reattach a network when the terminal device is added into the group.
  • the request may include ID information of the group and the type of the monitoring event.
  • the request may be an Insert Subscriber Data Request message.
  • the mobility management node instructs the terminal device to reattach the network according to the indicator. In this way, when a terminal device is configured at the mobility management node as a group member for the first time, the terminal device can be made reachable so that the server can provide immediate initial instructions to the terminal device.
  • FIGs. 7A-7B are flowcharts illustrating an exemplary process according to an embodiment of the disclosure.
  • the mobility management node is the MME/SGSN or AMF
  • the subscriber management node is the HSS or UDM
  • the network exposure node is the SCEF
  • the server is the SCS/AS or AF.
  • the SCS/AS sends a Monitoring Request to the SCEF.
  • the Monitoring Request message includes the External Group ID and the Allow Update of group members feature indication. If the Allow Update of group members feature indication (set to be True) is included, the HSS allows to add/delete UEs in a group for the existing group monitoring event configuration while the monitoring configuration is active.
  • the SCS/AS may add an indication in the request to instruct the newly added UE (in the case that the UE is configured for the first time or the update of the group is to add UEs) to reattach the network.
  • This indication may serve to make the newly added UEs reachable so that the SCS/AS can provide immediate initial instructions (e.g. to report the battery status, or the location) .
  • a new attribute “Allow Update of group members feature indication” and optionally “Reattach indicator” are added in T8 interface between the SCS/AS and the SCEF. For example, they may be added in “Table 5.3.2.1.2-1: Definition of type MonitoringEventSubscription” in 3GPP technical specification (TS) 29.122 V15.0.0, as shown below.
  • the SCEF and the HSS may exchange their support to the new feature (dynamic update of group members when group-based configuration is active) .
  • the new information Dynamic Group Update may be exchanged as a new supported feature for the Allow Update of group members feature negotiation between the SCEF and the HSS.
  • the Dynamic Group Update may be added in “Table 8.4.23-1: Features of Feature-List-ID used in S6t” in 3GPP TS 29.336 V15.4.0, as shown below.
  • the SCEF accepts the request and processes it.
  • the SCEF sends a Monitoring Request towards the HSS to configure the given Monitoring Event towards the HSS.
  • the SCEF may set the Allow Update of group members feature indication to be true if both the SCEF and the HSS support the dynamic group update according to the information exchange as described above.
  • a new parameter “Allow Update of group members feature indication” and optionally “Reattach indicator” are added in the Monitoring Request of S6t interface between the SCEF and the HSS.
  • the “Allow Update of group members feature indication” may be added in CIR command in 3GPP TS29.336 V15.4.0.
  • the HSS may store this new “Allow Update of group members feature indication” as part of the group-based configuration and check it later (at block 713) when a new UE is added/removed for the group. If the feature was supported when the group-based configuration was initiated, then the addition/removal of UE (s) will be allowed. Otherwise, if the feature was not supported at the time of the configuration, the HSS will base on the operator’s policy to allow or reject the group member update while a configuration for the group is still active/ongoing.
  • the HSS sends a Monitoring Response message to the SCEF to acknowledge acceptance of the Monitoring Request immediately before beginning the processing of individual UEs indicating that Group processing is in progress.
  • the SCEF sends a Monitoring Response message to the SCS/AS.
  • the Cause value indicates progress of Group processing request.
  • the HSS sends an Insert Subscriber Data Request message to the MME/SGSN for each individual group member UE. If the “reattach indicator” was included by the SCS/AS, the HSS also indicates this indicator in the Insert Subscriber Data Request towards the MME.
  • the MME/SGSN may store the received parameters and starts to watch for the indicated Monitoring Event. If the “reattach indicator” was received, the MME instructs the UE to reattach and reports that the newly added UE is reachable (if such monitoring event was already configured for the group) . At block 707, if the monitoring configuration is successful, the MME/SGSN sends an Insert Subscriber Data Answer message to the HSS. At block 708, for group based processing, the HSS sends a Monitoring Response message to the SCEF to acknowledge acceptance of the Monitoring Request. At block 709-712, the process may continue as in the existing procedures.
  • the update of group members may be performed in the HSS.
  • the HSS sends a Monitoring Indication (Updated Number of UEs, Added/Removed Group Member UEs) message to inform about the update of group members to the SCEF.
  • the Updated Number of UEs is the total number of the UE list after the UE addition and/or deletion for the group mentioned in block 713.
  • the updated number of UEs is required since the SCEF and the SCS/AS need to keep track of the group members, e.g. if a maximum number of reports/notifications per UE was initially requested by the SCS/AS, the SCEF and the SCS/AS need to know whether all UEs (e.g. including the newly added UEs) have reached that number, so that the configuration for the group can be locally removed in the SCEF and the SCS/AS.
  • AVPs attribute value pairs
  • RAR Reporting Information Request
  • new information elements or parameters
  • Updated Number of UEs and “Added/Removed Group Member UEs” are added in the existing Monitoring indication message towards the SCEF.
  • the SCEF may find the group monitoring event configuration.
  • the SCEF may update the Number of UEs of the group and add/delete the group member UEs in the group monitoring event configuration.
  • the Number of UEs is used to determine if reporting for the group is complete. If the reporting for the group is complete (i.e. all UEs have reached the maximum number of reports requested initially by the SCS/AS) , the SCEF will delete the group monitoring event configuration.
  • the HSS sends an Insert Subscriber Data Request message to the MME/SGSN for each added/deleted group member UE to initiate/delete the monitoring configuration (which is already active since it was previously done) for the group.
  • the process may continue as per the existing procedures.
  • the SCEF sends a Monitor Indication message to inform the SCS/AS the change of group members for the active monitoring event configuration as the SCEF receives it from the HSS.
  • the “Updated Number of UEs” and “Added/Removed Group Member UEs” are added into Monitoring Event Report in the Monitor Indication.
  • These two new parameters may be added in “Table 5.3.2.3.2-1: Definition of type MonitoringEventReport” in 3GPP TS29.122 V15.0.0. Note that if the SCS subscribes to two different monitoring events for the UE group, then two messages (one for each monitoring event) about the update will be sent to the SCS/AS.
  • the SCEF may determine if the reporting for the group is complete or not. If the reporting for the group is complete (e.g. the removed UE group member was the only remaining UE to report for a given event) , the SCEF will send a request to the HSS to delete the associated Monitoring Event configuration for the whole group. At block 721-724, the process may continue as per the existing procedures. It should be noted that two blocks shown in succession in the figures may, in fact, be executed substantially concurrently, or the blocks may sometimes be executed in the reverse order, depending upon the functionality involved.
  • FIG. 8 is a block diagram showing an apparatus suitable for use in practicing some embodiments of the disclosure.
  • the apparatus 800 may include a processor 810, a memory 820 that stores a program, and optionally a communication interface 830 for communicating data with other external devices through wired and/or wireless communication.
  • the program includes program instructions that, when executed by the processor 810, enable the apparatus 800 to operate in accordance with the embodiments of the present disclosure, as discussed above. That is, the embodiments of the present disclosure may be implemented at least in part by computer software executable by the processor 810, or by hardware, or by a combination of software and hardware.
  • the memory 820 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, flash memories, magnetic memory devices and systems, optical memory devices and systems, fixed memories and removable memories.
  • the processor 810 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 multi-core processor architectures, as non-limiting examples.
  • FIG. 9 is a block diagram showing a subscriber management node according to an embodiment of the disclosure.
  • the subscriber management node 900 comprises a reception module 902, a first sending module 904 and a second sending module 906.
  • the reception module 902 may be configured to receive, from a network exposure node, a first request for subscribing to a monitoring event for a group of terminal devices, as described above with respect to block 304.
  • the first sending module 904 may be configured to send, to one or more mobility management nodes, second requests for initiating configuration of the monitoring event for terminal devices of the group, as described above with respect to block 306.
  • the second sending module 906 may be configured to, in response to at least one terminal device being added into or deleted from the group when the initiated configuration is active, send, to a mobility management node, a third request for initiating or deleting configuration of the monitoring event for the at least one terminal device, as described above with respect to block 308.
  • FIG. 10 is a block diagram showing a network exposure node according to an embodiment of the disclosure.
  • the network exposure node 1000 comprises a first reception module 1002, a first sending module 1004, a second reception module 1006 and a second sending module 1008.
  • the first reception module 1002 may be configured to receive, from a server, a first request for subscribing to a monitoring event for a group of terminal devices, as described above with respect to block 404.
  • the first sending module 1004 may be configured to send, to a subscriber management node, a second request for subscribing to the monitoring event for the group of terminal devices, as described above with respect to block 406.
  • the second reception module 1006 may be configured to receive, from the subscriber management node, information about an update of the group due to at least one terminal device added into or deleted from the group when the subscribed monitoring event is active, as described above with respect to block 408.
  • the second sending module 1008 may be configured to send the information about the update of the group to the server, as described above with respect to block 410.
  • FIG. 11 is a block diagram showing a server according to an embodiment of the disclosure.
  • the server 1100 comprises a sending module 1102 and a reception module 1104.
  • the sending module 1102 may be configured to send, to a network exposure node, a request for subscribing to a monitoring event for a group of terminal devices, as described above with respect to block 502.
  • the reception module 1104 may be configured to receive, from the network exposure node, information about an update of the group due to at least one terminal device added into or deleted from the group when the subscribed monitoring event is active, as described above with respect to block 504.
  • FIG. 12 is a block diagram showing a mobility management node according to an embodiment of the disclosure.
  • the mobility management node 1200 comprises a reception module 1202 and an instruction module 1204.
  • the reception module 1202 may be configured to receive, from a subscriber management node, a request for initiating configuration of a monitoring event for a terminal device in a group of terminal devices, as described above with respect to block 602.
  • the request comprises an indicator instructing the terminal device to reattach a network when the terminal device is added into the group.
  • the instruction module 1204 may be configured to instruct the terminal device to reattach the network according to the indicator, as described above with respect to block 604.
  • the modules described above may be implemented by hardware, or software, or a combination of both.
  • the various exemplary embodiments may be implemented in hardware or special purpose circuits, software, logic or any combination thereof.
  • some aspects may be implemented in hardware, while other aspects may be implemented in firmware or software which may be executed by a controller, microprocessor or other computing device, although the disclosure is not limited thereto.
  • firmware or software which may be executed by a controller, microprocessor or other computing device, although the disclosure is not limited thereto.
  • While various aspects of the exemplary embodiments of this disclosure may be illustrated and described as block diagrams, flow charts, or using some other pictorial representation, it is well understood that these blocks, apparatus, systems, techniques or methods described herein may be implemented in, as non-limiting examples, hardware, software, firmware, special purpose circuits or logic, general purpose hardware or controller or other computing devices, or some combination thereof.
  • the exemplary embodiments of the disclosure may be practiced in various components such as integrated circuit chips and modules. It should thus be appreciated that the exemplary embodiments of this disclosure may be realized in an apparatus that is embodied as an integrated circuit, where the integrated circuit may comprise circuitry (as well as possibly firmware) for embodying at least one or more of a data processor, a digital signal processor, baseband circuitry and radio frequency circuitry that are configurable so as to operate in accordance with the exemplary embodiments of this disclosure.
  • exemplary embodiments of the disclosure may be embodied in computer-executable instructions, such as in one or more program modules, executed by one or more computers or other devices.
  • program modules include routines, programs, objects, components, data structures, etc. that perform particular tasks or implement particular abstract data types when executed by a processor in a computer or other device.
  • the computer executable instructions may be stored on a computer readable medium such as a hard disk, optical disk, removable storage media, solid state memory, RAM, etc.
  • the function of the program modules may be combined or distributed as desired in various embodiments.
  • the function may be embodied in whole or in part in firmware or hardware equivalents such as integrated circuits, field programmable gate arrays (FPGA) , and the like.
  • FPGA field programmable gate arrays

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

L'invention concerne des procédés et des appareils permettant de surveiller un service d'événement pour un groupe de dispositifs terminaux. Selon un mode de réalisation, un noeud de gestion d'abonné reçoit, en provenance d'un noeud d'exposition de réseau, une première demande pour s'abonner à un événement de surveillance pour un groupe de dispositifs terminaux. Le noeud de gestion d'abonné envoie, à un ou plusieurs nœuds de gestion de mobilité, des secondes demandes pour initier la configuration de l'événement de surveillance pour des dispositifs terminaux du groupe. En réponse à l'ajout ou à la suppression d'au moins un dispositif terminal du groupe lorsque la configuration déclenchée est active, le noeud de gestion d'abonné envoie, à un noeud de gestion de mobilité, une troisième demande pour initier ou supprimer la configuration de l'événement de surveillance pour l'au moins un dispositif terminal.
PCT/CN2019/074691 2019-02-03 2019-02-03 Procédés et appareils permettant de surveiller un service d'événement pour un groupe de dispositifs terminaux WO2020155177A1 (fr)

Priority Applications (1)

Application Number Priority Date Filing Date Title
PCT/CN2019/074691 WO2020155177A1 (fr) 2019-02-03 2019-02-03 Procédés et appareils permettant de surveiller un service d'événement pour un groupe de dispositifs terminaux

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/CN2019/074691 WO2020155177A1 (fr) 2019-02-03 2019-02-03 Procédés et appareils permettant de surveiller un service d'événement pour un groupe de dispositifs terminaux

Publications (1)

Publication Number Publication Date
WO2020155177A1 true WO2020155177A1 (fr) 2020-08-06

Family

ID=71840670

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2019/074691 WO2020155177A1 (fr) 2019-02-03 2019-02-03 Procédés et appareils permettant de surveiller un service d'événement pour un groupe de dispositifs terminaux

Country Status (1)

Country Link
WO (1) WO2020155177A1 (fr)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2022071726A1 (fr) 2020-09-29 2022-04-07 Samsung Electronics Co., Ltd. Procédé et appareil de gestion de groupe pour la surveillance d'événements de groupe

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2014071171A2 (fr) * 2012-11-02 2014-05-08 Interdigital Patent Holdings, Inc. Procédé et appareil de surveillance de dispositif de communication du type machine
CN104349373A (zh) * 2013-08-07 2015-02-11 华为终端有限公司 终端监控事件配置方法、应用服务器以及归属位置设备
US20160277243A1 (en) * 2015-03-22 2016-09-22 Lg Electronics Inc. Method for transmitting and receiving signal related to monitoring by scef in wireless communication system and apparatus for the same

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2014071171A2 (fr) * 2012-11-02 2014-05-08 Interdigital Patent Holdings, Inc. Procédé et appareil de surveillance de dispositif de communication du type machine
CN104349373A (zh) * 2013-08-07 2015-02-11 华为终端有限公司 终端监控事件配置方法、应用服务器以及归属位置设备
US20160277243A1 (en) * 2015-03-22 2016-09-22 Lg Electronics Inc. Method for transmitting and receiving signal related to monitoring by scef in wireless communication system and apparatus for the same

Non-Patent Citations (2)

* Cited by examiner, † Cited by third party
Title
ERICSSON ET AL.: "TLTRI and TTRI Usage, S2-184860,", 3GPP TSG-SA WG2 MEETING #127BIS,, 1 June 2018 (2018-06-01), XP051535409 *
HUAWEI ET AL.: "Enhancement of Monitoring Event configuration, S2-1900456,", 3GPP TSG-SA2 MEETING #130,, 25 January 2019 (2019-01-25), XP051590132 *

Cited By (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2022071726A1 (fr) 2020-09-29 2022-04-07 Samsung Electronics Co., Ltd. Procédé et appareil de gestion de groupe pour la surveillance d'événements de groupe
CN115211148A (zh) * 2020-09-29 2022-10-18 三星电子株式会社 用于针对群组事件监控的群组管理的方法和装置
EP4066518A4 (fr) * 2020-09-29 2023-01-25 Samsung Electronics Co., Ltd. Procédé et appareil de gestion de groupe pour la surveillance d'événements de groupe
US11924660B2 (en) 2020-09-29 2024-03-05 Samsung Electronics Co., Ltd. Method and apparatus for group management for group event monitoring
CN115211148B (zh) * 2020-09-29 2024-06-14 三星电子株式会社 用于针对群组事件监控的群组管理的方法和装置

Similar Documents

Publication Publication Date Title
US20240121591A1 (en) Methods and apparatuses for event monitoring
CN113056928B (zh) 用于事件监视的方法和装置
EP3984319A1 (fr) Procédé et dispositif pour l'attribution d'un identifiant de session pdu pour un dispositif terminal
WO2020155177A1 (fr) Procédés et appareils permettant de surveiller un service d'événement pour un groupe de dispositifs terminaux
US11323841B2 (en) Methods and apparatuses for exposure of presence reporting area functionality
US11522962B2 (en) Methods and apparatuses for IP and non-IP data communication using a unified interface
US11930424B2 (en) Method and apparatus for location based group message delivery
US11647379B2 (en) Methods and apparatuses for exposure of monitoring event
WO2021000915A1 (fr) Procédés et appareils de distribution de données non ip
WO2019232780A1 (fr) Procédé et appareil de transmission de données
WO2020221297A1 (fr) Procédés et appareils de configuration de surveillance pour équipement terminal
US11451996B2 (en) Methods and apparatuses for PLMN rate control
WO2020073199A1 (fr) Procédés et appareils de déclenchement de dispositif
OA20515A (en) Methods and apparatuses for configuration of monitoring for terminal device.
EP4218289A1 (fr) Quotas de tranche de réseau en présence d'interfonctionnement

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: 19912575

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: 19912575

Country of ref document: EP

Kind code of ref document: A1