WO2020147717A1 - Procédé de configuration d'événement de surveillance, dispositif de communication et système de communication - Google Patents

Procédé de configuration d'événement de surveillance, dispositif de communication et système de communication Download PDF

Info

Publication number
WO2020147717A1
WO2020147717A1 PCT/CN2020/071993 CN2020071993W WO2020147717A1 WO 2020147717 A1 WO2020147717 A1 WO 2020147717A1 CN 2020071993 W CN2020071993 W CN 2020071993W WO 2020147717 A1 WO2020147717 A1 WO 2020147717A1
Authority
WO
WIPO (PCT)
Prior art keywords
monitoring
network element
duration
monitoring event
timer
Prior art date
Application number
PCT/CN2020/071993
Other languages
English (en)
Chinese (zh)
Inventor
周晓云
朱奋勤
Original Assignee
华为技术有限公司
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 华为技术有限公司 filed Critical 华为技术有限公司
Publication of WO2020147717A1 publication Critical patent/WO2020147717A1/fr

Links

Images

Classifications

    • 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/0803—Configuration setting
    • 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
    • H04W24/00—Supervisory, monitoring or testing arrangements
    • H04W24/10—Scheduling measurement reports ; Arrangements for measurement reports
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
    • H04W4/60—Subscription-based services using application servers or record carriers, e.g. SIM application toolkits

Definitions

  • This application relates to the field of communication, and more specifically, to a method, communication device, and communication system for configuring monitoring events.
  • the present application provides a method, communication device and communication system for configuring monitoring events, which can provide the possibility to support multiple monitoring events.
  • a method for configuring monitoring events including: a mobility management function network element obtains multiple configuration information for multiple monitoring events of the same terminal (or UE), where one monitoring event corresponds to one Configuration information, where the configuration information includes a monitoring type and a time parameter; the mobility management function network element determines the duration of the periodic update timer of the terminal according to the multiple configuration information.
  • the mobility management function network element determines the duration of the periodic update timer of the terminal according to the multiple configuration information, including: the mobility management function network element determines the duration of the periodic update timer of the terminal according to the The minimum value of the multiple time parameters included in the multiple configuration information determines the duration of the periodic update timer as the first duration.
  • the method further includes: the mobility management function network element determining the duration of the mobility reachable timer according to the minimum value or according to the first duration.
  • the first timer is started when the mobile reachable timer is started, and the duration of the first timer is a time parameter of the target monitoring event; or,
  • the first timer is started when the mobile reachable timer expires, and the duration of the first timer is the difference between the time parameter of the target monitoring event and the minimum value.
  • the method further includes: if the mobility reachable timer expires, the mobility management function The network element reports the monitoring event corresponding to the minimum value.
  • the method further includes: in the case where the multiple monitoring events include a monitoring event whose monitoring type is terminal reachable, if the multiple monitoring events include a maximum response time, then The mobility management network element sends the maximum value of the multiple maximum response times to the terminal.
  • the user data management network element When the user data management network element receives the multiple monitoring events, sending the multiple configuration information to the mobility management function network element;
  • the mobility management function network element receives the multiple configuration information
  • the mobility management function network element may also execute the unit of the method in the first aspect or any possible implementation of the first aspect.
  • a computer program product containing instructions which when run on a computer, causes the computer to execute the above-mentioned first aspect and the method in any possible implementation of the above-mentioned first aspect.
  • Fig. 1 is a schematic block diagram of a communication system provided by the present application.
  • Figure 2 is a diagram of the open architecture of service capabilities in the 4G network of this application.
  • Fig. 5 is a schematic flowchart of a method for configuring a monitoring event provided by the present application.
  • Fig. 10 is a schematic flowchart of another method for configuring a monitoring event provided by the present application.
  • the size of the sequence number of each process does not mean the order of execution, and the execution order of each process should be determined by its function and internal logic, rather than corresponding to the embodiments of the present application.
  • the implementation process constitutes any limitation.
  • UE and terminal represent the same concept, and the two can be interchanged.
  • the maximum delay time indicates the maximum acceptable delay time for downlink data transmission.
  • the configuration information may also include the reference identifier of the monitoring event and the identifier (ID) of the capability opening network element corresponding to the monitoring event, or include the notification target address of the monitoring event, or include the notification target address of the monitoring event and the notification association logo.
  • the mobility management function network element 120 may start a mobility reachable timer.
  • the mobility management function network element 120 determines whether to report monitoring event #1 and monitoring event #2 by detecting whether the mobility reachability timer expires.
  • the mobility management function network element 120 reports monitoring event #1 and monitoring event #2.
  • the mobility management function network element 120 determines the duration of the periodic update timer of the UE according to T2 (or T1). For example, the duration of the periodic update timer of the UE can be equal to T2 or shorter than T2 by a preset duration , The preset duration is, for example, 4 minutes.
  • the mobility management function network element 120 may send the duration of the periodic update timer of the UE to the UE in the subsequent RAU/TAU/Registration Update process.
  • the mobility management function network element 120 may determine the duration of the mobility reachable timer according to T2 or the duration of the periodic update timer of the UE. For example, the duration of the mobility reachable timer is equal to T2.
  • SMF buffers data according to the recommended number of downlink data packets (data is buffered in SMF) or sends the recommended number of downlink data packets to UPF, and UPF buffers data according to the recommended number of downlink data packets (data is buffered in UPF).
  • the mobility management function network element 120 may start a mobility reachable timer.
  • the mobility management function network element 120 determines whether to report monitoring event #2 by detecting whether the mobility reachable timer has expired. When the mobility reachable timer expires, the mobility management function network element 120 reports monitoring event #2.
  • the mobility management function network element 120 reports monitoring event #1.
  • the mobility management function network element 120 determines the duration of the periodic update timer of the UE according to T2. For example, the duration of the periodic update timer of the UE may be equal to T2 or shorter than T2 by a preset duration. The duration is, for example, 4 minutes.
  • the mobility management function network element 120 may send the duration of the periodic update timer of the UE to the UE in the subsequent RAU/TAU/Registration Update process. Further, the mobility management function network element 120 may determine the duration of the mobility reachable timer according to T2 or the duration of the periodic update timer of the UE. For example, the duration of the mobility reachable timer is equal to T2.
  • SMF buffers data according to the recommended number of downlink data packets (data is buffered in SMF) or sends the recommended number of downlink data packets to UPF, and UPF buffers data according to the recommended number of downlink data packets (data is buffered in UPF).
  • the mobility management function network element 120 determines whether to report monitoring event #1 and monitoring event #2 by detecting whether the UE is in a connected state or whether the UE can be paged. When the UE enters the connected state or the UE can be paged, the mobility management function network element 120 reports monitoring event #1 and monitoring event #2. Optionally, when the UE enters the idle state, the mobility management function network element 120 may start the mobility reachable timer.
  • both configuration information #1 and configuration information #2 include the maximum response time
  • a larger maximum response time is provided to the UE, and the UE maintains a pageable state time according to the maximum response time.
  • both configuration information #1 and configuration information #2 include the recommended number of downlink data packets
  • the larger recommended number of downlink data packets is provided to the S-GW, and the S-GW buffers the data according to the recommended number of downlink data packets.
  • the mobility management function network element 120 provides the suggested number of downlink data packets to the SMF.
  • SMF buffers data according to the recommended number of downlink data packets (data is buffered in SMF) or sends the recommended number of downlink data packets to UPF, and UPF buffers data according to the recommended number of downlink data packets (data is buffered in UPF).
  • the mobility management function network element 120 receives the configuration information #2, it can perform the second processing according to the configuration information #1 and the configuration information #2.
  • the second treatment includes:
  • the mobility management function network element 120 may not change the second duration and the third duration, that is, the periodic update timer and the mobility reachable timer of the UE keep the previous configuration unchanged.
  • Event type #1 is connection loss
  • event type #2 is UE reachable
  • the mobility management function network element 120 provides the maximum response time to the UE, and the UE maintains a pageable state time according to the maximum response time. If configuration information #2 also includes the recommended number of downlink data packets, the mobility management function network element 120 provides the recommended number of downlink data packets to the S-GW, and the S-GW buffers the data according to the recommended number of downlink data packets. Or the mobility management function network element 120 provides the suggested number of downlink data packets to the SMF.
  • SMF buffers data according to the recommended number of downlink data packets (data is buffered in SMF) or sends the recommended number of downlink data packets to UPF, and UPF buffers data according to the recommended number of downlink data packets (data is buffered in UPF).
  • the mobility management function network element 120 determines the duration of the periodic update timer of the UE according to T2, and sends the determined duration to the UE in the subsequent RAU/TAU/Registration Update process.
  • the UE changes the duration of its periodic update timer from the second duration to the determined duration (for example, the first duration). Further, the mobility management function network element 120 may determine the duration of the mobility reachable timer according to T2, and change the duration of the mobility reachable timer from the third duration to the time determined this time. If the configuration information #1 also includes the maximum response time, the mobility management function network element 120 provides the maximum response time to the UE, and the UE maintains a pageable state time according to the maximum response time.
  • the mobility management function network element 120 provides the suggested number of downlink data packets to the SMF.
  • SMF buffers data according to the recommended number of downlink data packets (data is buffered in SMF) or sends the recommended number of downlink data packets to UPF
  • UPF buffers data according to the recommended number of downlink data packets (data is buffered in UPF).
  • the mobility management function network element 120 determines the duration of the periodic update timer of the UE according to T2, and sends the determined duration to the UE in the subsequent RAU/TAU process.
  • the UE changes the duration of its periodic update timer from the second duration to the determined duration (for example, the first duration).
  • the mobility management function network element 120 may determine the duration of the mobility reachable timer according to T2 or the duration of the periodic update timer of the UE, and change the duration of the mobility reachable timer from the third duration Change the duration determined for this time.
  • both configuration information #1 and configuration information #2 include the maximum response time, a larger maximum response time is provided to the UE, and the UE maintains a pageable state time according to the maximum response time.
  • the mobility management function network element 120 determines whether to report monitoring event #1 and monitoring event #2 by detecting whether the UE is in a connected state or whether the UE can be paged. When the UE enters the connected state or the UE can be paged, the mobility management function network element 120 reports monitoring event #1 and monitoring event #2. Optionally, when the UE enters the idle state, the mobility management function network element 120 may start the mobility reachable timer.
  • SMF buffers data according to the recommended number of downlink data packets (data is buffered in SMF) or sends the recommended number of downlink data packets to UPF, and UPF buffers data according to the recommended number of downlink data packets (data is buffered in UPF).
  • GSM global system of mobile communication
  • CDMA code division multiple access
  • WCDMA broadband code division multiple access
  • GPRS general packet radio service
  • LTE long term evolution
  • FDD frequency division duplex
  • TDD LTE Time division duplex
  • UMTS universal mobile telecommunication system
  • WiMAX worldwide interoperability for microwave access
  • the terminal can also be a cellular phone, a cordless phone, a session initiation protocol (SIP) phone, a wireless local loop (WLL) station, a personal digital assistant (PDA), and a wireless communication function Handheld devices, computing devices or other processing devices connected to wireless modems, in-vehicle devices, wearable devices, terminal devices in the future 5G system or terminals in the future evolution of the public land mobile network (PLMN) Devices, etc., are not limited in the embodiment of the present application.
  • the terminal may be an Internet of Things terminal with application characteristics of low cost, simple function, low power consumption, and infrequent user data transmission.
  • the SCEF network element 220 is the core network element in the architecture, so that the 3GPP network can safely provide service capabilities to the third-party service provider SCS/AS.
  • HSS230 is the home (or home) user subscription server, which saves the user's subscription information.
  • MME240 and SGSN250 are network elements responsible for mobility management of the UE.
  • the SCS/AS210 calls the service capabilities provided by the SCEF through T8 application programming interface (Application Programming Interface, API) interfaces (for example, API1, API2, and API3 shown in the figure).
  • API Application Programming Interface
  • Fig. 3 shows an architecture diagram of service capability opening in a 5G network that can be applied to this application.
  • the architecture diagram shown in Figure 3 includes SCS/AS310, Network Exposure Function (NEF) 320, Unified Data Management (UDM) 330, Core Access and Mobility Management Functions (Core Access and Mobility) Management Function (AMF) 340, and Session Management Function (SMF) 350.
  • the architecture diagram may also include UEs not shown in the figure.
  • NEF similar to SCEF functions
  • UDM similar to the part of the mobility management function in HSS
  • AMF functions similar to MME
  • SMF similar to a part of the session management function in the MME
  • NEF provides supported services and capabilities to the NEF through the Nsmf service.
  • the user data management network element, the mobility management function network element, and the capability opening function network element (for example, the first capability opening function network element and the second capability opening function network element) in the system shown in FIG. UDM, AMF, NEF in the architecture diagram shown.
  • UDM, AMF, and NEF are respectively used to implement the functions of the user data management network element, the mobility management function network element, and the capability opening function network element described above.
  • the architecture diagram shown in FIG. 2 may also include another NEF.
  • the architecture diagram shown in FIG. 3 may also include other network elements, which are not shown here.
  • the memory 402 can be read-only memory (ROM) or other types of static storage devices that can store static information and instructions, random access memory (RAM), or other types that can store information and instructions
  • the dynamic storage device can also be electrically erasable programmable read-only memory (EEPROM), compact disc read-only memory (CD-ROM) or other optical disc storage, optical disc storage (Including compact discs, laser discs, optical discs, digital universal discs, Blu-ray discs, etc.), magnetic disk storage media or other magnetic storage devices, or can be used to carry or store desired program codes in the form of instructions or data structures and can be used by a computer Any other media accessed, but not limited to this.
  • the memory can exist independently and is connected to the processor through a connection line (for example, a system bus). The memory can also be integrated with the processor.
  • the communication apparatus 400 may further include an output device 404 and an input device 404.
  • the output device 404 communicates with the processor 401 and can display information in various ways.
  • the output device 404 may be a liquid crystal display (LCD), a light emitting diode (LED) display device, a cathode ray tube (CRT) display device, or a projector (projector) Wait.
  • the input device 404 communicates with the processor 401 and can accept user input in various ways.
  • the input device may be a mouse, keyboard, touch screen device, or sensor device.
  • the aforementioned communication device 400 may be a general-purpose computer device or a special-purpose computer device.
  • the computer device 400 may be a desktop computer, a portable computer, a network server, a PDA (Personal Digital Assistant, PDA), a mobile phone, a tablet computer, a wireless terminal device, a communication device, an embedded device, or a device shown in Figure 4. Similar structure equipment.
  • PDA Personal Digital Assistant
  • the embodiment of the present invention does not limit the type of the communication device 400.
  • S501 SCS/AS1 sends a monitoring request message #1A to SCEF1.
  • SCEF1 receives the monitoring request message #1A sent by SCS/AS1.
  • the monitoring request message #1A is used to request the configuration of the first monitoring event.
  • the monitoring request message #1A may carry SCS/AS identification #1, T8 destination address #1, monitoring type #1, and T8 long-term interaction reference identification (T8 long term interaction reference identification, TLTRI) #1.
  • SCS/AS identification #1 is used to identify SCS/AS1
  • T8 destination address #1 is the address of SCS/AS1
  • monitoring type #1 is used to indicate the monitoring type of the first monitoring event
  • TLTRI#1 is used to indicate the first monitoring event.
  • the monitoring event configuration is used to indicate the first monitoring event.
  • the monitoring request message #1A When the monitoring request message #1A configures monitoring events for a single UE, the monitoring request message #1A also carries an external identifier (External Id) or a mobile subscriber integrated service digital network/public switched telephone network number (Mobile Subscriber International ISDN/PSTN number) ,MSISDN); when the monitoring request message #1A performs monitoring event configuration for a group of UEs, the monitoring request message #1A also carries an external group ID (External Group Id). Among them, monitoring type #1 is connection loss or UE reachability.
  • SCEF1 saves SCS/AS identification #1, T8 destination address #1, monitoring type #1 and TLTRI#1, and MDT#1 or ML#1, and authorizes the monitoring event configuration according to the local policy. After the authorization is successful, SCEF1 allocates SCEF Reference ID #1 and saves the correspondence between SCEF Reference ID #1 and TLTRI#1.
  • the SCEF reference identifier #1 is used to identify the first monitoring event configuration in the core network.
  • SCEF1 sends a monitoring request message (also called a monitoring event configuration request message) #1B to the HSS. Accordingly, the HSS receives the monitoring request message #1B sent by SCEF1.
  • a monitoring request message also called a monitoring event configuration request message
  • the monitoring request message #1B carries the external identifier or MSISDN or external group identifier, SCEF1 identifier, SCEF reference identifier #1 and monitoring type #1, and MDT#1 or ML#1. In addition, the monitoring request message #1B may also carry optional parameters in S501.
  • the monitoring request message #1B may also carry priority #1.
  • the HSS determines the duration of the periodic update timer of the UE according to MDT#1. If the monitoring type #1 is that the UE is reachable, and the monitoring request message #1B carries ML#1, the HSS determines the duration of the periodic update timer of the UE for the UE according to ML#1. For details on how to determine the duration of the periodic update timer of the UE, reference may be made to the foregoing description, which is not repeated here.
  • monitoring type #1 is UE reachable, and monitoring request message #1B also provides MRT#1 and/or SNPD#1, insert user subscription data request message #1 can also carry MRT#1 and/or SNPD #1.
  • S505 can refer to the prior art, which will not be repeated here.
  • the MME/SGSN allocates the received duration of the periodic update timer of the UE or the duration of the periodic update timer of the UE determined by itself to the UE. If monitoring type #1 is connection loss, MME/SGSN starts to monitor the mobility reachable timer expiration.
  • the mobility reachable timer is set according to the periodic update timer of the UE. Generally, if the duration of the periodic update timer of the UE is set according to MDT#1, the duration of the mobility reachable timer and the periodic update timing of the UE The device is the same or slightly longer than it, but the embodiment of the present application does not limit this.
  • the monitoring request response message #1B carries the SCEF reference identifier #1 and acceptance indication information #1B, and the acceptance indication information #1B is used to indicate that the HSS accepts the first monitoring event configuration.
  • the monitoring request message #2A is used to request the second monitoring event configuration.
  • the monitoring request message #2A can carry the SCS/AS identifier #2, the T8 destination address #2, the monitoring type #2, and TLTRI#2.
  • SCS/AS identification #2 is used to identify SCS/AS2
  • T8 destination address #2 is the address of SCS/AS2
  • monitoring type #2 is used to indicate the monitoring type of the second monitoring event
  • TLTRI#2 is used to indicate the second Monitoring event configuration.
  • the monitoring request message #2A can also carry the maximum detection time, which is recorded as MDT#2 here.
  • SCEF2 saves SCS/AS identification #2, T8 destination address #2, monitoring type #2 and TLTRI#2, and MDT#2 or ML#2, and authorizes the monitoring event configuration according to the local policy. After the authorization is successful, SCEF2 allocates SCEF reference identifier #2, and saves the corresponding relationship between reference identifier #2 and TLTRI#2.
  • the monitoring request message #2B carries the external identifier or MSISDN or external group identifier, SCEF2 identifier, SCEF reference identifier #2 and monitoring type #2, and MDT#2 or ML#2. In addition, the monitoring request message #2B may also carry optional parameters in S510.
  • the HSS performs related processing according to the monitoring request message #2B and the monitoring request message #1B.
  • Table 1 shows a form of the monitoring event configuration table. It should be understood that this application does not limit the form or manner in which the HSS saves the relevant parameters of the monitoring event configuration, nor does it limit the specific form of the monitoring event configuration table. Table 1 is only an exemplary description and should not constitute any limitation to the application.
  • each row in Table 1 except for the first and last rows has an entry, and each entry corresponds to a monitoring event.
  • Each entry can include the monitoring type of the monitoring event, SCEF ID, SCEF Reference ID, maximum detection time or maximum delay, maximum response time (if any), and recommended number of downlink data packets (if any).
  • the above table can be issued in full or incremental form.
  • S515 The MME/SGSN saves the received monitoring event configuration table or the parameters in the table.
  • the MME/SGSN performs corresponding processing according to the monitoring event configuration table or the parameters in the table. For this treatment, see the second treatment described above. I won't repeat it here. It should be understood that MDT#1 or ML#1 may correspond to T1 in the second process, and MDT#2 or ML#2 may correspond to T2 in the second process.
  • S517 The HSS sends a monitoring request response message #2B to SCEF2.
  • SCEF2 receives the monitoring request response message #2B sent by the HSS.
  • the HSS can accept multiple monitoring events (or multiple monitoring event configurations), and by sending configuration information for the multiple monitoring events to the MME/SGSN, the MME/SGSN can follow
  • the multiple configuration information manages the periodic update timer, the mobility reachable timer, and the first timer that may be involved in the UE, such as determining the duration, sending the determined duration, and starting the timer, so as to achieve Support for the multiple monitoring events.
  • SCS/AS1 and SCS/AS2 shown in FIG. 5 may be the same SCS/AS, and SCEF1 and SCEF2 may also be the same SCEF, which is not limited in the embodiment of the present application.
  • FIG. 6 shows an exemplary flowchart of a method for configuring a monitoring event according to another embodiment of the present application.
  • Figure 6 shows the process of reporting (or reporting) events.
  • both monitoring type #1 and monitoring type #2 are UE reachable.
  • step S601 After step S515 in FIG. 5, the MME/SGSN detects that the UE becomes connected or the UE becomes paging reachable.
  • S602 The MME/SGSN sends a first monitoring event report #1A to SCEF1.
  • SCEF1 receives the first monitoring event report #1A sent by the MME/SGSN.
  • the first monitoring event report #1A carries monitoring type #1 and SCEF reference identifier #1.
  • SCEF1 sends the first monitoring event report #1B to SCS/AS1.
  • SCS/AS1 receives the first monitoring event report #1B sent by SCEF1.
  • the first monitoring event report #1B carries monitoring type #1 and TLTRI#1.
  • S604 The MME/SGSN sends a second monitoring event report #1A to SCEF2.
  • SCEF2 receives the second monitoring event report #1A sent by MME/SGSN.
  • S605 SCEF2 sends a second monitoring event report #1B to SCS/AS2.
  • SCS/AS2 receives the second monitoring event report #1B sent by SCEF2.
  • Fig. 7 shows an exemplary flowchart of a method for monitoring event configuration in an embodiment of the present application.
  • Figure 7 shows the process of reporting (or reporting) events.
  • both monitoring type #1 and monitoring type #2 are connection loss.
  • the MME/SGSN reports the detected event to the associated SCEF.
  • the MME/SGSN reports the detected event to the associated SCEF.
  • the MME/SGSN detects that the mobility reachable timer expires after step S515 in FIG. 5.
  • the method includes steps S702a to S703a. If the mobile reachable timer is used for the second monitoring event (or the second monitoring event configuration), the method includes steps S702b to S703b.
  • S702a The MME/SGSN sends the first monitoring event report #1A to SCEF1.
  • SCEF1 receives the first monitoring event report #1A sent by the MME/SGSN.
  • S703a SCEF1 sends the first monitoring event report #1B to SCS/AS1.
  • SCS/AS1 receives the first monitoring event report #1B sent by SCEF1.
  • S702b The MME/SGSN sends a second monitoring event report #1A to SCEF2.
  • SCEF2 receives the second monitoring event report #1A sent by MME/SGSN.
  • SCEF2 sends a second monitoring event report #1B to SCS/AS2.
  • SCS/AS2 receives the second monitoring event report #1B sent by SCEF2.
  • the second monitoring event report #1B carries monitoring type #2 and TLTRI#2.
  • S704 The MME/SGSN detects that the first timer expires.
  • the method includes steps S705a to S706a. If the first timer is used for the first monitoring event, the method includes steps S705b to S706b.
  • the second monitoring event report #1A carries monitoring type #2 and SCEF reference identifier #2.
  • SCEF2 sends a second monitoring event report #1B to SCS/AS2.
  • SCS/AS2 receives the second monitoring event report #1B sent by SCEF2.
  • the first monitoring event report #1A carries monitoring type #1 and SCEF reference identifier #1.
  • the first monitoring event report #1B carries monitoring type #1 and TLTRI#1.
  • the MME/SGSN sending the first monitoring event report can also be described as the MME/SGSN reporting the first monitoring event.
  • the MME/SGSN sending the second monitoring event report can also be described as the MME/SGSN reporting the second monitoring event event.
  • the MME/SGSN When the first timer is not set (that is, the duration of the first timer is not determined), no matter whether the mobile reachable timer is set according to the maximum detection time of the first monitoring event or the maximum detection time of the second monitoring event Setting, when the MME/SGSN detects that the mobile reachable timer expires, the MME/SGSN sends the first monitoring event report and the second monitoring event report respectively.
  • FIG. 8 shows an exemplary flowchart of a method for configuring a monitoring event according to another embodiment of the present application.
  • the embodiment shown in FIG. 8 can be applied to the system or architecture diagram shown in FIG. 3. It should be understood that FIG. 8 shows detailed steps or operations of the method 800, but these steps or operations are only examples, and the embodiment of the present application may also perform other operations or only perform some operations in FIG. 8.
  • S801 SCS/AS1 sends a Nnef event exposure subscription request (Nnef_EventExposure_Subscribe request) message #1 to NEF1.
  • NEF1 receives the Nnef event exposure subscription request message #1 sent by SCS/AS1.
  • the Nnef event exposure subscription request message #1 is used to request the first monitoring event configuration.
  • the Nnef event exposure subscription request message #1 carries the SCS/AS identifier #1 and the monitoring type #1.
  • SCS/AS identification #1 and monitoring type #1 reference may be made to the description of step S501 when the method 500 is described above.
  • the Nnef event exposure subscription request message #1 When configuring a monitoring event for a single UE, the Nnef event exposure subscription request message #1 also carries an external ID or MSISDN; when configuring a monitoring event for a group of UEs, the Nnef event exposure subscription request message #1 also carries an external group ID.
  • the Nnef event exposure subscription request message #1 can also carry the maximum detection time, which is recorded as MDT#1 here.
  • Nnef event exposure subscription request message #1 can also carry the maximum delay time, which is recorded as ML#1 here.
  • Nnef event exposure subscription request message #1 can also carry one or more of the following parameters:
  • the maximum response time here is marked as: MRT#1;
  • NEF1 saves SCS/AS identification #1 and monitoring type #1, and MDT#1 or ML#1, and allocates notification target address #1 and notification association identification #1 (optional).
  • the notification target address #1 or the notification target address #1 and the notification association identifier #1 are used to identify the first monitoring event configuration.
  • NEF1 authorizes configuration requests according to local policies.
  • S802 can refer to the prior art, which will not be repeated here.
  • NEF1 may determine the priority of the first monitoring event according to the service level agreement with SCS/AS1, which is expressed as priority #1 here.
  • NEF1 sends a Nudm event exposure subscription request (Nudm_EventExposure_Subscriberequest) message #1 to UDM.
  • UDM receives the Nudm event exposure subscription request message #1 sent by NEF1.
  • the Nudm event exposure subscription request message #1 may also carry priority #1.
  • the UDM determines whether to accept the first monitoring event configuration, and if accepted, saves the received parameters.
  • the UDM stores the corresponding relationship between the external identifier and the UE user identifier, and the corresponding relationship between the external group identifier and the UE user identifier of the group members.
  • the HSS determines the duration of the periodic update timer of the UE according to MDT#1. If the monitoring type #1 is that the UE is reachable, and the Nudm event exposure subscription request message #1 carries ML#1, the HSS determines the duration of the periodic update timer of the UE according to ML#1. For details on how to determine the duration of the periodic update timer of the UE, reference may be made to the foregoing description, which is not repeated here.
  • UDM sends a Nudm_SDM notification request (Nudm_SDM_Notification Request) message #1 to the AMF for the UE or each group member UE.
  • the AMF receives the Nudm_SDM notification request message #1 sent by the UDM.
  • the Nudm_SDM notification request message #1 may also carry the duration of the periodic update timer of the UE. If the duration of the periodic update timer of the UE is not determined in S804, the Nudm_SDM notification request message #1 carries MDT#1 or ML#1.
  • Nudm_SDM notification request message #1 can also be MRT#1 (if provided) and SNPD#1 (if provided).
  • the AMF determines the periodic update timing of the UE for the UE according to MDT#1 If the monitoring type #1 is UE reachable, the AMF determines the duration of the periodic update timer of the UE for the UE according to ML#1.
  • the AMF allocates the received duration of the periodic update timer of the UE or the duration of the periodic update timer of the UE determined by itself to the UE. If monitoring type #1 is connection loss, AMF starts to monitor the mobility reachability timer expiration.
  • the mobility reachable timer is set according to the periodic update timer of the UE. Generally, if the duration of the periodic update timer of the UE is set according to MDT#1, the duration of the mobility reachable timer and the periodic update timing of the UE The device is the same or slightly longer than it, but the embodiment of the present application does not limit this. If monitoring type #1 indicates that the UE is reachable, the AMF starts to monitor the UE to enter the connected state.
  • S808 The AMF sends a Nudm_SDM notification response (Nudm_SDM_Notification Response) message #1 to the UDM.
  • UDM receives the Nudm_SDM notification response message #1 sent by AMF.
  • Nudm_SDM notification response message #1 carries acceptance indication information #1A, and the acceptance indication information #1A is used to indicate that the AMF accepts data insertion, that is, accepts the first monitoring event configuration.
  • Namf_event exposure subscription response message #1 carries AMF subscription identifier #1 and acceptance indication information #1B, and acceptance indication information 1B is used to indicate that AMF has accepted the first monitoring event configuration.
  • UDM allocates a UDM subscription (Subscription) identifier #1, and saves the corresponding relationship between the AMF subscription identifier #1 and the UDM subscription identifier #1.
  • UDM sends a Nudm event exposure subscription response (Nudm_EventExposure_SubscribeReponse) message #1 to NEF1.
  • NEF1 receives the Nudm event exposure subscription response message #1 sent by UDM.
  • Nudm event exposure subscription response message #1 carries UDM subscription identifier #1 and acceptance indication information #1C, and acceptance indication information #1C is used to instruct UDM to accept the first monitoring event configuration.
  • NEF1 allocates NEF1 subscription identifier, and maintains the corresponding relationship between UDM subscription identifier #1 and NEF1 subscription identifier.
  • NEF1 sends a Nnef event exposure subscription response (Nnef_EventExposure_SubscribeResponse) message #1 to SCS/AS1.
  • SCS/AS1 receives the Nnef event exposure subscription response message #1 sent by NEF1.
  • the Nnef event exposure subscription response message #1 carries the NEF1 subscription identifier and acceptance indication information #1D, and the acceptance indication information #1D is used to instruct NEF1 to accept the first monitoring event configuration.
  • the Nnef event exposure subscription request message #2 is used to request the second monitoring event configuration.
  • the Nnef event exposure subscription request message #2 carries the SCS/AS identifier #2 and the monitoring type #2.
  • the Nnef event exposure subscription request message #2 also carries an external identifier or MSISDN;
  • the Nnef event exposure subscription request message #2 also carries an external group identifier.
  • the UE represented by the external identifier or MSISDN here is the same UE as the UE in S901.
  • the user group represented by the external group identifier represents the same user group as the user group in S901.
  • the Nnef event exposure subscription request message #2 can also carry the maximum detection time, which is recorded as MDT#2 here.
  • Nnef event exposure subscription request message #2 can also carry the maximum delay time, which is recorded as ML#2 here.
  • Nnef event exposure subscription request message #2 can also carry one or more of the following parameters:
  • the maximum response time here is recorded as: MRT#2;
  • the recommended number of downlink data packets is recorded here as: SNDP#2.
  • NEF2 saves SCS/AS identification #2, and MDT#2 or ML#2, and allocates notification target address #2 and notification association identification #2 (optional).
  • the notification target address #2 or the notification target address #2 and the notification association identifier #2 are used to identify the second monitoring event configuration NEF2 to authorize the configuration request according to the local policy.
  • S813 can refer to the prior art, which will not be repeated here.
  • NEF2 may determine the priority of the second monitoring event configuration according to the service level agreement with SCS/AS2, which is expressed as priority #2 here.
  • NEF2 sends a Nudm event exposure subscription request message #2 to UDM.
  • UDM receives the Nudm event exposure subscription request message #2 sent by NEF2.
  • Nudm event exposure subscription request message #2 carries an external identifier or MSISDN or external group identifier, monitoring type #2, notification target address #2, and notification association identifier #2 (optional), and MDT#2 or ML#2.
  • the Nudm event exposure subscription request message #2 can also carry optional parameters in S812.
  • the Nudm event exposure subscription request message #2 may also carry priority #2.
  • UDM can create a monitoring event configuration table.
  • Each monitoring event configuration corresponds to an entry in the table, and the love entry includes related parameters of the monitoring event configuration.
  • the monitoring event configuration table can be created when UDM receives monitoring event configuration for the first time, for example, in S804, or the monitoring event configuration table can be created when UDM receives monitoring event configuration for the second time. This is not limited.
  • Table 2 shows a form of the monitoring event configuration table. It should be understood that this application does not limit the form or manner in which the UDM saves the relevant parameters of the monitoring event configuration, nor does it limit the specific form of the monitoring event configuration table. Table 2 is only an exemplary description, and should not constitute any limitation to this application.
  • each row in Table 2 except the first row and the last row has an entry, and each entry corresponds to a monitoring event.
  • Each entry can include the monitoring type of the monitoring event, notification target address, notification association identification, maximum detection time or maximum delay, maximum response time (if any), and recommended number of downlink data packets (if any).
  • the above table can be issued in full or incremental form.
  • UDM sends Nudm_SDM notification to AMF for each UE (UDM stores the corresponding relationship between the external identifier and user identifier) or each group member UE (UDM stores the corresponding relationship between the external group identifier and the user identifier of each group member) Request message #2.
  • the AMF receives the Nudm_SDM notification request message #2 sent by the UDM.
  • the Nudm_SDM notification request message #2 carries the external identifier or MSISDN, and the UDM sends the Nudm_SDM notification request message #2 to all AMFs serving this group.
  • the UDM sends a Namf event exposure subscription request (Namf_EventExposure_Subscribe Request) message #2 for the UE or each group member UE to the AMF.
  • the AMF receives the Namf event exposure subscription request message #2 sent by the UDM.
  • Namf event exposure subscription request message #2 carries monitoring type #2, notification target address #2, and notification association identifier #2 (optional). Among them, the Namf event exposure subscription request message #2 also carries the monitoring event configuration table or other parameters in the table.
  • AMF performs corresponding processing according to the monitoring event configuration table or the parameters in the table. For this treatment, see the second treatment described above. I won't repeat it here. It should be understood that MDT#1 or ML#1 may correspond to T1 in the second process, and MDT#2 or ML#2 may correspond to T2 in the second process.
  • S819 The AMF sends a Nudm_SDM notification response message #1 to the UDM.
  • UDM receives the Nudm_SDM notification response message #1 sent by AMF.
  • Nudm_SDM notification response message #1 carries acceptance indication information #2A, which is used to indicate that the AMF accepts data insertion.
  • the AMF allocates the AMF subscription identifier #2, and returns the Namf event exposure subscription response message #2 to the UDM.
  • UDM receives Namf event exposure subscription response message #2 sent by AMF.
  • UDM allocates UDM subscription identifier #2, and maintains the corresponding relationship between AMF subscription identifier #2 and UDM subscription identifier #2.
  • UDM also sends Nudm event exposure subscription response message #2 to NEF2.
  • NEF2 receives the Nudm event exposure subscription response message #2 sent by UDM.
  • the Nudm event exposure subscription response message #2 carries the UDM subscription identifier #2 and acceptance indication information #2C, and the acceptance indication information #2C is used to indicate that the UDM accepts the second monitoring event configuration.
  • the Nnef event exposure subscription response message #2 carries the NEF2 subscription identifier and acceptance indication information #2D, and the acceptance indication information #2D is used to indicate that NEF has accepted the second monitoring event configuration.
  • UDM can accept multiple monitoring events (or multiple monitoring event configurations), and by sending configuration information for the multiple monitoring events to AMF, AMF can configure according to the multiple monitoring events.
  • the information manages the UE’s periodic update timer, mobility reachable timer, and possibly related first timers, such as determining the duration, sending the determined duration, and starting the timer, so as to realize the multiple Support for monitoring events.
  • SCS/AS1 and SCS/AS2 shown in FIG. 8 may be the same SCS/AS, and NEF1 and NEF2 may also be the same NEF, which is not limited in the embodiment of the present application.
  • UDM only includes monitoring events with the same event type in Table 1. That is, if event type #2 and event type #1 are not the same, after UDM accepts monitoring event #2, UDM sends Table 1 including monitoring event #2 configuration information to AMF, and requests AMF to delete the saved configuration information.
  • the monitoring type of the configuration information of multiple monitoring events saved on the AMF is always the same.
  • FIG. 9 shows an exemplary flowchart of a method for configuring a monitoring event according to another embodiment of the present application.
  • Figure 9 shows the process of reporting (or reporting) events.
  • both monitoring type #2 and monitoring type #2 are UE reachable events.
  • the AMF detects that the UE becomes connected or the UE becomes paging reachable according to step S818 in FIG. 8.
  • S902 The AMF sends the first monitoring event report #1A to NEF1.
  • NEF1 receives the first monitoring event report #1A sent by AMF.
  • NEF1 sends the first monitoring event report #1B to SCS/AS1.
  • SCS/AS1 receives the first monitoring event report #1B sent by NEF1.
  • the first monitoring event report #1B carries monitoring type #1 and NEF1 subscription identifier.
  • S904 The AMF sends the second monitoring event report #1A to NEF2.
  • NEF2 receives the second monitoring event report #2A sent by AMF.
  • the second monitoring event report #1A carries monitoring type #2 and notification target address #2. Further, the second monitoring event report #1A may carry the notification association identifier #2 (if received).
  • NEF2 sends a second monitoring event report #1B to SCS/AS2.
  • SCS/AS2 receives the second monitoring event report #1B sent by NEF2.
  • the second monitoring event report #1B carries monitoring type #2 and NEF2 subscription identifier.
  • FIG. 10 shows an exemplary flowchart of a method for monitoring event configuration in an embodiment of the present application.
  • Figure 10 shows the process of reporting (or reporting) events.
  • both monitoring type #1 and monitoring type #2 are connection loss events.
  • AMF reports the detected event to the associated SCEF.
  • the first timer is set, when the first timer expires, AMF reports the detected event to the associated NEF .
  • the communication device further includes: a second sending unit, configured to report the target monitoring event when the first timer expires.
  • the communication device further includes: a seventh sending unit, configured to, when the multiple monitoring events include a monitoring event whose monitoring type is terminal reachable, if the multiple monitoring events The event includes the recommended number of downlink data packets, and the maximum number of the multiple recommended numbers of downlink data packets is sent to the serving network element or the session management network element.
  • a seventh sending unit configured to, when the multiple monitoring events include a monitoring event whose monitoring type is terminal reachable, if the multiple monitoring events The event includes the recommended number of downlink data packets, and the maximum number of the multiple recommended numbers of downlink data packets is sent to the serving network element or the session management network element.
  • each unit in the device 1100 is used to execute each action or process performed by the mobility management function network element in the method embodiment or in the system 100.
  • each unit in the device 1100 can be used to execute the method 500.
  • the MME/SGSN and the various actions or processes performed by the AMF in the method 800 can also achieve the beneficial effects in the foregoing method embodiments.
  • detailed descriptions are omitted.
  • the disclosed system, device, and method may be implemented in other ways.
  • the device embodiments described above are only schematic.
  • the division of the unit is only a logical function division, and there may be other divisions in actual implementation, for example, multiple units or components may be combined or Can be integrated into another system, or some features can be ignored, or not implemented.
  • the displayed or discussed mutual coupling or direct coupling or communication connection may be indirect coupling or communication connection through some interfaces, devices or units, and may be in electrical, mechanical, or other forms.
  • the units described as separate components may or may not be physically separated, and the components displayed as units may or may not be physical units, that is, they may be located in one place, or they may be distributed on multiple network units. Some or all of the units may be selected according to actual needs to achieve the purpose of the solution of this embodiment.

Landscapes

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

Abstract

L'invention concerne un procédé de configuration d'un événement de surveillance, un dispositif de communication et un système de communication, lesquels peuvent fournir la possibilité de prendre en charge une pluralité d'événements de surveillance. Le procédé comprend les étapes suivantes : un élément de réseau de fonction de gestion de mobilité obtient une pluralité d'éléments d'informations de configuration d'une pluralité d'événements de surveillance pour le même terminal, un événement de surveillance correspond à un élément d'informations de configuration, et les informations de configuration comprennent un type de surveillance et un paramètre de temps ; et l'élément de réseau de fonction de gestion de mobilité détermine, en fonction de la pluralité d'éléments d'informations de configuration, la durée d'un temporisateur de mise à jour périodique du terminal.
PCT/CN2020/071993 2019-01-15 2020-01-14 Procédé de configuration d'événement de surveillance, dispositif de communication et système de communication WO2020147717A1 (fr)

Applications Claiming Priority (4)

Application Number Priority Date Filing Date Title
CN201910037269 2019-01-15
CN201910037269.X 2019-01-15
CN201910404868.0 2019-05-16
CN201910404868.0A CN111435921B (zh) 2019-01-15 2019-05-16 配置监控事件的方法、通信装置和通信系统

Publications (1)

Publication Number Publication Date
WO2020147717A1 true WO2020147717A1 (fr) 2020-07-23

Family

ID=71580137

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2020/071993 WO2020147717A1 (fr) 2019-01-15 2020-01-14 Procédé de configuration d'événement de surveillance, dispositif de communication et système de communication

Country Status (2)

Country Link
CN (1) CN111435921B (fr)
WO (1) WO2020147717A1 (fr)

Families Citing this family (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN116032721A (zh) * 2021-10-25 2023-04-28 苏州盛科通信股份有限公司 一种事件监控方法、装置、芯片和计算机存储介质

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2015172079A1 (fr) * 2014-05-08 2015-11-12 Interdigital Patent Holdings, Inc. Services de surveillance de communications de type machine
CN105592534A (zh) * 2014-11-07 2016-05-18 思科技术公司 用于在网络环境中提供省电模式增强的系统和方法
CN108476394A (zh) * 2016-01-18 2018-08-31 三星电子株式会社 移动通信系统中终端通信的方法和装置
CN110351698A (zh) * 2018-04-04 2019-10-18 华为技术有限公司 事件订阅的方法、装置和系统

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2015172079A1 (fr) * 2014-05-08 2015-11-12 Interdigital Patent Holdings, Inc. Services de surveillance de communications de type machine
CN105592534A (zh) * 2014-11-07 2016-05-18 思科技术公司 用于在网络环境中提供省电模式增强的系统和方法
CN108476394A (zh) * 2016-01-18 2018-08-31 三星电子株式会社 移动通信系统中终端通信的方法和装置
CN110351698A (zh) * 2018-04-04 2019-10-18 华为技术有限公司 事件订阅的方法、装置和系统

Also Published As

Publication number Publication date
CN111435921A (zh) 2020-07-21
CN111435921B (zh) 2022-04-22

Similar Documents

Publication Publication Date Title
US11438860B2 (en) Event subscription method, apparatus, and system
US10039072B2 (en) System and method for providing power saving mode enhancements in a network environment
TWI700948B (zh) 無線傳輸/接收單元及由其實施的方法
US10555218B2 (en) Method and apparatus to address user equipment power consumption
US10660067B2 (en) Systems and methods for efficient signaling of IoT devices in a wireless telecommunications network
US9693289B2 (en) Moderating communications within a wireless telecommunications network based on UE power saving modes
EP3911010A1 (fr) Procédé et dispositif de surveillance d'événement
US20220287136A1 (en) Method and Apparatus for Session Management
US9699725B1 (en) System and method for providing power saving mode enhancements in a network environment
US12028774B2 (en) Method for location service control and communications unit
US20190191353A1 (en) Method for processing information or message, and network device
JP2019521592A (ja) モノのインターネットにおけるｓｍｓ処理方法、モビリティ管理ネットワークエレメント及び端末デバイス
WO2017004773A1 (fr) Procédé de communication et appareil de communication
US11368837B2 (en) Node and method for managing a packet data network connection
US20230016327A1 (en) Methods and Apparatuses for Event Reporting
WO2019095379A1 (fr) Procédé, dispositif, et support de stockage informatique pour l'activation et la désactivation d'un service
WO2018068188A1 (fr) Procédé d'émission de données de liaison descendante, dispositif de réseau et dispositif de plan d'utilisateur
WO2020147717A1 (fr) Procédé de configuration d'événement de surveillance, dispositif de communication et système de communication
US20210168585A1 (en) Indication information sending method, apparatus and system, and storage medium
US20220038540A1 (en) Methods and Apparatuses for IP and Non-IP Data Communication
US11395215B2 (en) Systems and methods for detecting and remediating excessive messaging by wireless telecommunications devices
WO2023051772A1 (fr) Procédé et appareil de rapport d'événement
WO2020258986A1 (fr) Procédé et dispositif d'obtention d'informations de capacité radio, support de stockage et dispositif électronique
JP2024528950A (ja) セッション復元のための方法及び装置

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

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

Country of ref document: EP

Kind code of ref document: A1