Event reporting methods, devices, and equipment

Abstract

This application discloses an event reporting method, apparatus, device, and storage medium, which belong to the field of communications technology, and the event reporting method of an embodiment of this application includes a terminal transmitting first information, the first information being used to indicate relevant information for which the terminal reports an event outside a first area, the first area being an area in which the terminal is permitted to report an event, the terminal receiving event reporting configuration information matching the first information, and the terminal reporting an event based on the event reporting configuration information.

Description

Technical Field

[0001] (Cross-reference to Related Applications) This application claims the priority of a Chinese patent application filed with the Chinese Patent Office on April 6, 2023, with an application number of 202310366782.X and a title of "Event Reporting Method, Apparatus, Device, and Storage Medium", and all of its content is incorporated into this application by reference.

[0002] This application belongs to the field of communication technology, and specifically relates to an event reporting method, apparatus, device, and storage medium.

Background Art

[0003] In locations prior to R18, a third-party application (LCS client) requests to obtain an event report of a UE when the network side meets a certain event request (including periodic, area-based, and motion-based).

[0004] Currently, for event reporting, in R18, an event report allowed area has been introduced, that is, the UE can report an area (this area is called a power saving area) that represents that the UE reports its location only within this area. The GMLC determines the event report allowed area based on the power saving area, generally converting a fine-grained area to a coarse-grained area. For example, a certain rectangular area (that is, an area composed of coordinate points) is converted into a tracking area (TA) or a cell list. Therefore, the current usage method of the event report allowed area is that the UE executes an event report only when the UE is in the event report allowed area.

[0005] However, there are currently no feasible solutions regarding whether the UE can perform event reporting outside the event reporting allowed area. [Overview of the project] [Problems that the invention aims to solve]

[0006] Embodiments of this application provide an event reporting method, apparatus, device, and storage medium for giving a terminal a way to perform event reporting outside the event reporting allowed area. [Means for solving the problem]

[0007] According to the first aspect, an event reporting method is provided, and the method is The terminal transmits first information, the first information is used to indicate relevant information for which the terminal reports an event outside of a first area, and the first area is an area in which the terminal is permitted to report an event. The terminal receives event reporting configuration information that matches the first information, This includes the terminal performing an event report based on the event reporting configuration information.

[0008] According to a second aspect, an event reporting method is provided, the method is The first network-side device acquires first information of the terminal, the first information is used to indicate relevant information for which the terminal reports events outside of the first area, and the first area is an area in which the terminal is permitted to report events. The first network-side device acquires event reporting configuration information that matches the first information, This includes the first network-side device transmitting the reporting configuration information to the terminal.

[0009] According to a third aspect, an event reporting device is provided, which is A first transmission module for transmitting first information, wherein the first information is used to indicate relevant information for which a terminal reports an event outside a first area, and the first area is an area in which the terminal is permitted to report an event. A first receiving module for receiving event reporting configuration information that matches the first information, It includes a first processing module for performing event reporting based on the aforementioned event reporting configuration information.

[0010] According to a fourth aspect, an event reporting device is provided, which is A first acquisition module for acquiring first information of a terminal, wherein the first information is used to indicate relevant information for which the terminal reports events outside a first area, and the first area is an area in which the terminal is permitted to report events; A second acquisition module for obtaining event reporting configuration information that matches the first piece of information, It includes a second transmission module for transmitting the aforementioned report configuration information to the terminal.

[0011] According to the fifth aspect, a terminal is provided, which includes a processor and a memory, the memory storing a program or instruction that can be run on the processor, and when the program or instruction is executed by the processor, a step of the method according to the first aspect is realized.

[0012] According to the sixth aspect, a network-side device is provided, which includes a processor and memory, the memory storing a program or instruction that can be run on the processor, and when the program or instruction is executed by the processor, the steps of the method according to the second aspect are realized.

[0013] According to the seventh aspect, a terminal is provided, the terminal including a processor and a communication interface, wherein the communication interface is used to transmit first information, wherein the first information is used to indicate relevant information for which the terminal reports events outside a first area, the first area being an area in which the terminal is permitted to report events. The communication interface is further used to receive event reporting configuration information that matches the first information. The processor is used to perform event reporting based on the event reporting configuration information.

[0014] According to the eighth aspect, a network-side device is provided, which includes a processor and a communication interface, wherein the communication interface is used to acquire first information of a terminal, wherein the first information is used to indicate relevant information for which the terminal reports events outside a first area, and the first area is an area in which the terminal is permitted to report events. The processor is used to obtain event reporting configuration information that matches the first information. The communication interface is further used to transmit the reporting configuration information to the terminal.

[0015] According to the ninth aspect, a readable storage medium is provided, the readable storage medium storing a program or instruction, and when the program or instruction is executed by a processor, a step of the method according to the first aspect is realized, or a step of the method according to the second aspect is realized.

[0016] According to the tenth aspect, a wireless communication system is provided, which includes a terminal and network-side equipment, wherein the terminal may be used to perform a step of the method according to the first aspect, and the network-side equipment may be used to perform a step of the method according to the second aspect.

[0017] According to the eleventh aspect, a chip is provided, the chip comprising a processor and a communication interface, the communication interface being coupled with the processor, the processor running a program or instructions, and being used to implement the method according to the first aspect or the method according to the second aspect.

[0018] According to the twelfth aspect, a computer program / program product is provided, the computer program / program product is stored in a storage medium, and the program / program product is executed by at least one processor to realize the steps of the event reporting method described in the first or second aspect.

[0019] According to the thirteenth aspect, an embodiment of the present application provides an event reporting device used to perform a step of an event reporting method described in the first or second aspect. [Effects of the Invention]

[0020] In an embodiment of the present application, the terminal can send the first information to the first network-side device, and the first network-side device can obtain the event report configuration information matching the first information and then send this event report configuration information to the terminal. In this way, the terminal can perform an event report based on the event report configuration information. Here, the first information is used to indicate the related information for the terminal to perform an event report outside the first area. The first area (i.e., event report allowed area) is the area where the terminal is allowed to perform an event report. As can be seen therefrom, in an embodiment of the present application, the terminal can report to the first network-side device the related information (i.e., the first information) for it to perform an event report outside the event report allowed area. Thereby, the first network-side device can configure appropriate event report configuration information for the terminal based on this related information, and further the terminal can realize a more appropriate event report outside the event report allowed area. Therefore, in an embodiment of the present application, a method for the terminal to perform an event report outside the event report allowed area is provided.

Brief Description of the Drawings

[0021] [Figure 1] It is a block diagram of a wireless communication system to which an embodiment of the present application is applicable. [Figure 2] It is a schematic diagram of an architecture for realizing a location service. [Figure 3] It is a flowchart of a Mobile Terminated Location Request (MT-LR). [Figure 4] It is a flowchart of an event report method in an embodiment of the present application. [Figure 5] It is a schematic diagram for determining an event report allowed area based on power saving in an embodiment of the present application. [Figure 6]This is a schematic diagram of "forward use" and "reverse use" in the embodiment of this application. [Figure 7] This is a flowchart of another event reporting method in the embodiment of this application. [Figure 8] This is a flowchart of a specific embodiment 1 of the event reporting method of the embodiment of this application. [Figure 9] This is a flowchart of a specific embodiment 2 of the event reporting method of the embodiment of this application. [Figure 10] This is a flowchart of a specific embodiment 3 of the event reporting method of the embodiment of this application. [Figure 11] This is a flowchart of a specific embodiment 4 of the event reporting method of the embodiment of this application. [Figure 12] This is a structural block diagram of the event reporting device in an embodiment of this application. [Figure 13] This is a structural block diagram of another event reporting device in an embodiment of this application. [Figure 14] This is a structural block diagram of the communication equipment in an embodiment of this application. [Figure 15] This is a structural block diagram of the terminal in the embodiment of this application. [Figure 16] This is a structural block diagram of the network-side equipment in an embodiment of this application. [Modes for carrying out the invention]

[0022] The following clearly describes the technical concepts in the embodiments of this application, linking them to the drawings of the embodiments. Clearly, the embodiments described are only some, not all, embodiments of this application. All other embodiments obtained by those skilled in the art based on the embodiments of this application are all within the scope of protection of this application.

[0023] The terms "first," "second," etc., used in this application are intended to distinguish similar objects and not to describe a specific order or sequence. It should be understood that these terms are interchangeable where appropriate, so that the embodiments of this application can be carried out in an order other than those illustrated or described herein, and the objects distinguished by "first" and "second" are generally of the same kind and do not limit the number of objects; for example, the first object may be one or more. In this application, "or" indicates at least one of the connected objects; for example, "A or B" covers three solutions: solution 1: including A but not B, solution 2: including B but not A, and solution 3: including both A and B. The character " / " generally indicates that the preceding and succeeding related objects are in an "or" relationship.

[0024] The term "instruction" as used in this application may be direct (or explicit) or indirect (or implicit). Here, a direct instruction may be understood as the sender clearly notifying the recipient of specific information, the operations to be performed, or the desired outcome in the instruction sent by the sender, while an indirect instruction may be understood as the recipient determining or judging the corresponding information based on the instruction sent by the sender, and determining the operations to be performed or the desired outcome based on the judgment.

[0025] It should be noted that the technologies described in the embodiments of this application are not limited to Long Term Evolution (LTE) / LTE-Advanced (LTE-A) systems, but are also applicable to other wireless communication systems, such as Code Division Multiple Access (CDMA), Time Division Multiple Access (TDMA), Frequency Division Multiple Access (FDMA), Orthogonal Frequency Division Multiple Access (OFDMA), Single-carrier Frequency-Division Multiple Access (SC-FDMA), or other systems. The terms "system" and "network" in the embodiments of this application are always used interchangeably, and the technologies described may be applied to the systems and radio technologies mentioned above, or to other systems and radio technologies. The following description uses the New Radio (NR) system for illustrative purposes, and uses NR terminology in most of the following descriptions, but these technologies are also applicable to systems other than NR systems, such as sixth-generation (6 th It can also be applied to Generation 6G communication systems.

[0026] Figure 1 shows a block diagram of a wireless communication system to which an embodiment of this application can be applied. The wireless communication system includes a terminal 11 and network-side equipment 12. Here, terminal 11 is a terminal-side device such as a mobile phone, tablet personal computer, laptop computer, notebook computer, personal digital assistant (PDA), palmtop computer, netbook, ultra-mobile personal computer (UMPC), mobile internet device (MID), augmented reality (AR), virtual reality (VR) equipment, robot, wearable device, aircraft (flight vehicle), vehicle user equipment (VUE), ship equipment, pedestrian user equipment (PUE), smart home (home equipment with wireless communication capabilities, such as refrigerators, televisions, washing machines, or furniture), game console, personal computer (PC), deposit machine, or self-service machine. Wearable devices include smartwatches, smart wristbands, smart earphones, smart glasses, smart accessories (such as smart bracelets, smart hand chains, smart rings, smart necklaces, smart ankle bracelets, smart anklets, etc.), smart bands, smart clothing, etc. Here, in-vehicle equipment may also be referred to as in-vehicle terminals, in-vehicle controllers, in-vehicle modules, in-vehicle components, in-vehicle chips, or in-vehicle units. It should be noted that the terminal 11 in the embodiments of this application is not limited to a specific type.The network-side equipment 12 may include access network equipment or core network equipment, where access network equipment may also be called radio access network (RAN) equipment, radio access network functions, or radio access network units. Access network equipment may include base stations, wireless local area network (WLAN) access points (AS), or wireless fidelity (WiFi) nodes. Here, a base station may also be called a Node B (NB), an Evolved Node B (eNB), the next generation Node B (gNB), a New Radio Node B (NR Node B), an access point, a Relay Base Station (RBS), a Serving Base Station (SBS), a Base Transceiver Station (BTS), a radio base station, a radio transceiver, a Basic Service Set (BSS), an Extended Service Set (ESS), a home Node B (HNB), a home evolved Node B, a Transmission Reception Point (TRP), or any other appropriate term in the art, and as long as the same technical effect is achieved, the base station is not limited to any particular technical term. For the purposes of this explanation, the embodiments of this application only use base stations in NR systems as examples and do not limit the specific types of base stations.

[0027] The core network equipment includes core network nodes, core network functions, Mobility Management Entity (MME), Access and Mobility Management Function (AMF), Session Management Function (SMF), User Plane Function (UPF), Policy Control Function (PCF), Policy and Charging Rules Function (PCRF), Edge Application Server Discovery Function (EASDF), Unified Data Management (UDM), Unified Data Repository (UDR), Home Subscriber Server (HSS), Centralized network configuration (CNC), Network Repository Function (NRF), Network Exposure Function (NEF), Local NEF (or L-NEF), Binding Support Function (BSF), and Application Functions (Application It may include, but is not limited to, at least one of the following: Function, AF, etc. It should be noted that the embodiments of this application only illustrate core network equipment in an NR system and do not limit the specific types of core network equipment.Core network nodes, core network functions, Mobility Management Entity (MME), Access and Mobility Management Function (AMF), Session Management Function (SMF), User Plane Function (UPF), Policy Control Function (PCF), Policy and Charging Rules Function (PCRF), Edge Application Server Discovery Function (EASDF), Unified Data Management (UDM), Unified Data Repository (UDR), Home Subscriber Server (HSS), Centralized network configuration (CNC), Network Repository Function (NRF), Network Exposure Function (NEF), Local NEF (or L-NEF), Binding Support Function (BSF), Application Functions It may include, but is not limited to, at least one of the following: Function, AF, etc. It should be noted that the embodiments of this application only illustrate core network equipment in an NR system and do not limit the specific types of core network equipment.

[0028] To facilitate understanding of the event reporting method of the embodiment of this application, the following related technologies are now introduced.

[0029] 1. About Location Services (LCS) As shown in Figure 2, location services are executed and provided by network elements such as the AMF and Location Management Function (LMF) within the core network. LCS messages interact between the UE and the LCS entity (client) or AF, and one relatively typical flow is the MT-LR flow.

[0030] Here, the MT-LR flow is initiated by an external third-party application (LCS client) or AF via the NEF network element, and ultimately obtains the UE's location information via network elements such as the Gateway Mobile Location Centre (GMLC), AMF, and LMF.

[0031] Here, N1, N2, N51, N33, N52, N8, NL1, NL2, NL5, NL6, NL7, and Le in Figure 2 each represent different interfaces.

[0032] 2. MT-LR flow As shown in Figure 3, the following steps 31 to 331 are specifically included.

[0033] Step 31a: LCS clientc sends an LCS Service Request message to the Home Gateway Mobile Location Center (H-GMLC). Step 31b-1: AF sends an Nnef_EventExposure_Subscribe Request message to the NEF, Step 31b-2: The NEF sends a GMLC network element location request message (Ngmlc_Location_ProvideLocation Request) to the H-GMLC. Specifically, the LCS client or AF accesses the H-GMLC via the NEF and initiates a service request to the LCS system, requesting periodic or triggered location reports. In the request, the LCS client carries the type of periodic or triggered location report and related parameters. This type includes UE availability, area, periodic location, and motion.

[0034] Here, for area-based event reporting, the LCS service request message carries detailed information about the geographic region, whether to report when the UE enters, stays in, or leaves this region, the duration of the report, the interval between two successful reports, the maximum sampling interval, whether location estimation is carried in the report message, and whether one or more reports are required. If the target region is represented as a single local location coordinate or a single geographic name, H-GMLC converts the target region into a geographic region represented by shape.

[0035] Step 32: H-GMLC and UDM interact with the UDM network element's subscription data management request message (Nudm_SDM_Get), meaning H-GMLC confirms the UE's privacy check and obtains updates to the UE's privacy information from the UDM, thereby obtaining changes to the UE's privacy information in a timely manner.

[0036] Step 33: The H-GMLC and UDM interact with the UDM network element's UE context management request message (Nudm_UECM_Get), i.e., the H-GMLC obtains the AMF address from the UDM.

[0037] Step 34: The H-GMLC sends a location request (Ngmlc_Location_ProvideLocation Request) to the Visited Gateway Mobile Location Centre (V-GMLC). If the UE is under the control of the H-GMLC, this step can be skipped.

[0038] Step 35. The H-GMLC or V-GMLC initiates a location request to the serving AMF (for example, the V-GMLC sends a Namf_Location_ProvidePositioningInfo Request message to the AMF). For area-based event reporting, the target geographic region is mapped to a list of cell or TA identifiers.

[0039] Step 36: The AMF sends an AMF network element location provision response message (Namf_Location_ProvidePositioningInfo Response) to the V-GMLC. Step 37: V-GMLC sends a GMLC network element location provision response message (Ngmlc_Location_ProvideLocation Response) to H-GMLC. Step 38a: H-GMLC sends an LCS Service Response to the LCS Client. Step 38b-1: H-GMLC sends a GMLC network element location provision response message (Ngmlc_Location_ProvideLocation Response) to the NEF. Step 38b-2: The NEF sends an Event Exposure Subscription Response message (Nnef_EventExposure_Subscribe Response) for the NEF network element to the AF. As can be seen from steps 36-38 above, if AMF supports the periodic or triggered delayed location reporting described above, AMF will return an acknowledgment to LCSclient or AF.

[0040] Step 39: The AMF waits until the UE becomes accessible, i.e., if the UE is currently inaccessible, for example, when using Extended-Discontinuous Reception (eDRX), the AMF waits until the UE becomes accessible.

[0041] Step 310: The AMF triggers Network Triggered Service Requests until the UE becomes accessible. If the UE is in an idle state (connection management-IDLE, CM-IDLE), the AMF initiates a Network Triggered Location Request flow to establish a signaling connection between the UE and the network.

[0042] Step 311: The AMF sends a NAS Location Notification Invoke Request to the UE. Step 312: The UE sends the NAS Location Notification Return Result to the AMF. In other words, steps 311-312 inform the UE of information such as location requests and associated privacy inspection requests, and the type of periodic or triggered location reports.

[0043] Step 313: The AMF performs the LMF selection process, i.e., selects an LMF to perform the delayed position request task.

[0044] Step 314: The AMF sends an LMF Network Element Location Determining Location Request (Nlmf_Location_DetermineLocation Request) message to the selected LMF, i.e., the AMF sends a request message to the LMF to locate the delayed location. For all types of events, this message carries the LCS-related identifier, AMF identifier, serving cell identifier, client type, and may also carry directive information to indicate the UE's support for Long Term Evolution Positioning Protocol (LPP) messages, the desired Location Quality of Service (QoS), and geodomain description type.

[0045] Step 315: UE Location, i.e., LMF, executes one or more location flows to request and obtain the location of the UE.

[0046] Step 316: The LMF sends a Location Periodic-Triggered Invoke Request (LCS) message to the UE for a delayed location report, i.e., a delayed location report. The LMF sends a supplemental LCS Periodic-Triggered Invoke Request to the UE via the AMF of the service, the request carrying the location request message that the LMF received from the AMF in Step 314, instructing the UE to subsequently perform the corresponding delayed Periodic-Triggered Location Report.

[0047] Step 317: The UE sends a Location Periodic-Triggered Invoke Return (LCS) message to the LMF, i.e., if the UE supports the request in step 316, the UE returns an acknowledgment message to the LMF.

[0048] Step 318: The LMF sends an LMF network element location-determine-location response message (Nlmf_Location_DetermineLocation Response) to the AMF. Step 319: The AMF sends an AMF network element location event notification message (Namf_Location_EventNotify) to the V-GMLC. Step 320: V-GMLC sends a GMLC network element location event notification message (Ngmlc_Location_EventNotify) to H-GMLC. Step 321a: H-GMLC sends a Location Service Response (LCS Service Response) to the LCS Client. Step 321b-1: H-GMLC sends a GMLC network element location event notification message (Ngmlc_Location_EventNotify) to the NEF. Step 321b-2: The NEF sends an event exposure notification message (Nnef_EventExposure_Notify) for the NEF network element to the AF. In other words, if the UE supports the request according to steps 318-3121, the LMF notifies the LCS client of this information via the AMF and GMLC, where this information may include information such as the UE's location capabilities.

[0049] Step 322: If an event is detected, i.e., if the periodic or triggered location requests in steps 316 and 317 occur successfully, the UE monitors for the occurrence of the event requested in step 316. For area events or motion events, the UE monitors at time intervals no more than or equal to the maximum event sampling interval.

[0050] Here, the UE triggers an event report if any of the following situations occur:

[0051] (1) If the requested area event or motion event has already been detected, and the minimum reporting time interval has already elapsed since the last report (if this is not the first event report), (2) When the required periodic event occurs, (3) If the maximum reporting time for an area event or motion event has already elapsed.

[0052] If an event trigger has been detected and the UE is in the area in step 316 or connected to an access type permitted by the LMF, the UE continues to execute step 323. If the UE does not have access to an access type permitted, the UE may skip reporting the trigger event or, based on a request received from the LMF in step 316, report the trigger event when an access type permitted becomes available.

[0053] Step 323: Location measurement, i.e., the UE obtains location measurement information or location estimation information requested or permitted in step 316.

[0054] Step 324: The UE initiates a UE-Triggered Service Request (UE Triggered Service Request) flow, i.e., if the UE is in a CMM idle state, the UE executes the service request flow and establishes an N1 signaling connection with the AMF.

[0055] Step 325: The UE sends an event report to the LMF, i.e., the UE sends a supplemental event report message to the AMF corresponding to the LMF, and finally sends it to the LMF, where the AMF transparently transmits this message. This message may carry an embedded LPP message carrying the event type and location estimation information.

[0056] Step 326: The LMF sends an event report confirmation to the UE, meaning the LMF receives and processes the event report, updates the status of the event report (e.g., the number of reports to date, the duration of the report, etc.), and returns a confirmation message to the UE.

[0057] Step 327: If location estimation information is required for the UE location flow, i.e., event reporting, the LMF may perform one or more location flows. The LMF determines the location of the UE using at least one of the measurement information and the location estimation, where timestamp information is also determined.

[0058] Step 328: LMF sends Nlmf_Location_EventNotify to V-GMLC, Step 329: V-GMLC sends Ngmlc_Location_EventNotify to H-GMLC, Step 330a: H-GMLC sends an LCS Service Response to the LCS Client. Step 330b-1: H-GMLC sends Ngmlc_Location_EventNotify to NEF, Step 330b-2: NEF sends Nnef_EventExposure_Notify to AF, Specifically, in steps 328-330, the LMF performs event reporting to the LCS client via GMLC and reports the UE location to the LCS client.

[0059] 31. UE continuously monitors subsequent events.

[0060] In the following sections, the event reporting method according to the embodiments of this application will be described in detail with reference to several embodiments and their application scenarios, accompanied by drawings.

[0061] According to a first embodiment, with reference to Figure 1, an embodiment of the present application provides an event reporting method, which may include the following steps 401-403.

[0062] Step 401: The terminal transmits the first piece of information.

[0063] Here, the first information is used to indicate relevant information for which the terminal reports events outside the first area, and the first area is an area in which the terminal is permitted to report events; that is, the first area is the event report allowed area described in the preamble. Selectively, the terminal reporting events outside the first area may specifically mean that the terminal reports conditional events outside the first area. Here, the constraints that enable the conditional event reporting may be constraints indicated by a reporting policy configured on the network side.

[0064] Furthermore, in the embodiments of this application, the terminal can report a power saving area (used to instruct the terminal to report events within this area) to the network, and the network can determine the event report allowed area based on the power saving area, generally converting fine-grained areas to coarse-grained areas, for example, converting a rectangular area into a single TA list or cell list, as shown in Figure 5.

[0065] Furthermore, the first piece of information described above is used to indicate the relevant information for which the terminal reports events outside the first domain; that is, the first piece of information is used to indicate at least one of the relevant parameter information, capabilities, or actions of whether or not to report events outside the first domain.

[0066] Selectively, the first piece of information includes at least one of the following items A-1 to A-3.

[0067] A-1: A second area for the terminal to indicate the area where it wishes to report events. Section A-2: Reporting instructions (i.e., Power saving class) to indicate whether the terminal supports reporting events outside the first area, or whether the terminal reports events outside the first area, or to indicate at least one level regarding the terminal reporting events outside the first area. Section A-3: Area usage indication for indicating whether the first area is to be used in the forward direction or in the reverse direction.

[0068] In section A-1, the second area mentioned above is the power saving area, which serves as the basis for the network to determine the event report allowed area.

[0069] Regarding item A-2, there may be three possible interpretations of the reporting instruction.

[0070] Understanding Method 1: This describes the terminal's ability to characterize whether the terminal supports reporting events outside of the primary domain.

[0071] Understanding Method 2: This method instructs whether the terminal will perform an event report outside the first area, i.e., it instructs the terminal to perform an event report outside the first area. In this understanding method, a form for carrying out the invention may be that the reporting instruction has two values, where 0 indicates that no event report will be performed, and 1 indicates that a conditional event report will be performed.

[0072] Understanding method 3: Indicates the level at which the terminal reports events outside the first area, i.e., that the terminal is in a power-saving level. In this understanding method, the embodiments for carrying out the invention may be as follows.

[0073] In one embodiment, the reporting instruction may specify two levels, high and low, that characterize whether the terminal performs event reporting outside a first area, where high indicates no event reporting and low indicates conditional event reporting.

[0074] In another embodiment, the report instruction may be applied to area-based event reporting, for example, specifying a first level (i.e., high level), a second level (i.e., medium level), and a third level (i.e., low level). If the level is the first level, the terminal reports events only within the first area (i.e., does not report events outside the first area). If the level is the second level, the terminal must report events within the first area and conditionally report events outside the first area and within the second area. If the level is the third level, the terminal must report events within the first area and conditionally report events outside the first area.

[0075] Regarding item A-3, as shown in Figure 6, when used in the forward direction, area A is the inside area and area B is the outside area. However, when used in the reverse direction, area A is the outside area and area B is the inside area. Therefore, using the first area in the forward direction means that the area inside the first area is the inside area and the area outside the first area is the outside area. Using the first area in the reverse direction means that the area outside the first area is the inside area and the area inside the first area is the outside area. Here, the forward or reverse use of the first area may be represented by different values ​​for the area usage instruction, as shown in Table 1, for example. By default, it is used in the forward direction, meaning that the area outside the first area used in the following sentence may be understood as the outside area in the forward direction.

[0076] [Table 1]

[0077] In typical cases, terminals often report events within a certain area. However, for users who operate in a fixed area for extended periods, periodic event reporting is unnecessary to conserve power; it is only valuable when they report an event when they leave that area. For example, elderly residents in nursing homes, who spend many years there, need to report their location after leaving the nursing home to prevent them from getting lost (elderly mobile phones), and kindergarten children need to report their location to their parents' mobile phones if they leave the school grounds during class time to prevent them from getting lost (children's watches). Therefore, for some specialized terminals (e.g., elderly mobile phones, children's watches), the network can be configured to use the first area in reverse, thereby meeting the location and power-saving needs in the relevant scenarios.

[0078] One embodiment of the area usage instruction is that the terminal does not provide this parameter, and the first network-side device determines it based on information such as the type of the fourth network-side device, the location service type, and subscription information related to the terminal's location.

[0079] Selectively, step 401 "The terminal transmits the first information" is performed. The terminal transmits a target message in which the first information is carried, Here, the target message includes at least one of the following items B-1 to B-3.

[0080] Section B-1: Registration request message, Section B-2: Location privacy settings request message, Section B-3: Uplink non-access layer transmission messages.

[0081] Here, the terminal transmits the first information to the third network-side device, which then transmits it to the second network-side device, which in turn provides the first information to the first network-side device, which then obtains event reporting configuration information matching the first information and transmits it to the terminal. Here, the first network-side device may be a GMLC, the second network-side device may be a UDM, and the third network-side device may be an AMF.

[0082] Regarding item B-1, for example, the terminal may send this registration request to the AMF by carrying the first information into 5G Mobility Management (5GMM) capability information and packaging this 5GMM capability information into a registration request message, or the terminal may send this registration request to the AMF by packaging the first information as a new IE into a registration request message. Section B-2 above indicates that the terminal may send the first information to the AMF via a UE Location Privacy Setting Request message. Section B-3 above indicates that the terminal may transmit the first information to the AMF via an uplink non-access layer transmission (UL NAS TRASPORT) message.

[0083] Step 402: The terminal receives event reporting configuration information that matches the first information.

[0084] Here, the first piece of information is used to indicate the relevant information (i.e., at least one of the relevant parameter information, capabilities, or reporting behavior) for the terminal to report an event outside the first domain. Therefore, the event reporting configuration information matches the first piece of information, i.e., the event reporting configuration information matches at least one of the relevant parameter information, capabilities, or reporting behavior for the terminal to report an event outside the first domain.

[0085] Selectively, the event reporting configuration information includes at least one of the following items C-1 to C-2.

[0086] Section C-1: Target instruction information for indicating whether the terminal needs to report an event outside the first area, Section C-2: A reporting policy that specifies at least one constraint condition under which a terminal should report events.

[0087] With respect to item C-1, the decision may be made based on the reporting instruction in the first information, where the reporting instruction is understood based on "Understanding Method 1" above, i.e., if the reporting instruction is characterized by capability, then if the reporting instruction indicates that the terminal supports reporting events outside the first area, the target instruction information indicates that the terminal reports events outside the first area; if the reporting instruction indicates that the terminal does not support reporting events outside the first area, then the target instruction information indicates that the terminal does not report events outside the first area. If the reporting instruction is based on "Understanding Method 2 or 3" above, there is no need to determine the target instruction information based on this reporting instruction, i.e., in such cases, the event reporting configuration information does not include target instruction information.

[0088] Section C-2 is used to specify the constraints under which the terminal implements conditional event reporting. Here, the reporting instruction in the first information indicates that the terminal must implement conditional event reporting if it supports the terminal reporting events outside the first area, or if it indicates the terminal reporting events outside the first area, or if it indicates the second or third level described above. In such cases, the event reporting configuration information must include this reporting policy to specify how the terminal implements conditional event reporting.

[0089] Selectively, the first information further includes a policy set, wherein the policy set includes at least one candidate reporting policy, and the reporting policy included in the event reporting configuration information is determined based on one candidate reporting policy in the policy set.

[0090] As can be seen, the terminal can send a policy set to the first network-side device (for example, the terminal sends the policy set to the third network-side device, which then sends it to the second network-side device, which then provides the policy set to the first network-side device), and in this way, the first network-side device can select one candidate reporting policy from this policy set and, based on this selected candidate reporting policy, determine which reporting policy needs to be sent to the terminal.

[0091] Furthermore, the first network side is, The fourth type of network-side equipment (i.e., the type of equipment requesting location services (e.g., LCS client / AF)), Location-based work type (i.e., deferred 5GC-MT-LR type (area, periodic, or motion)), Subscription information related to the device's location, The first area and, The second area and, Reporting instructions, Based on at least one piece of information, such as area usage instructions, a reporting policy that needs to be sent to the terminal may be determined.

[0092] Alternatively, a fourth network-side device (i.e., the device requesting location services) may carry a reporting policy with the location service request sent to the first network-side device, so that the first network-side device can determine which reporting policy needs to be sent to the terminal based on the reporting policy carried with the location service request.

[0093] Step 403: The terminal reports an event based on the event reporting configuration information.

[0094] Here, the event report includes the terminal's location information. Therefore, the terminal can perform an event report and report its location information to the network side.

[0095] As can be seen from steps 401 to 403 above, in the embodiments of this application, a terminal can transmit first information to a first network-side device, and the first network-side device can transmit event reporting configuration information to the terminal by obtaining event reporting configuration information that matches the first information, thereby enabling the terminal to perform event reporting based on the event reporting configuration information, where the first information is used to indicate relevant information for which the terminal will perform event reporting outside a first area, and the first area (i.e., event report allowed area) is an area in which the terminal is permitted to perform event reporting. As can be seen thereafter, in the embodiments of this application, a terminal can report to the first network-side device relevant information (i.e., first information) for which it will perform event reporting outside the event report allowed area, thereby enabling the first network-side device to configure appropriate event reporting configuration information for the terminal based on this relevant information, and further enabling the terminal to perform more appropriate event reporting outside the event report allowed area. Therefore, embodiments of this application provide a method for a terminal to perform event reporting outside the event report allowed area.

[0096] Furthermore, while the related technologies support terminals reporting events only when they are within the event report allowed area, they do not provide specific guidelines on whether terminals should be allowed to report events when they are outside the event report allowed area, or, if so, how they should report events.

[0097] Furthermore, regarding not reporting events outside the event report allowed area, the problem is that if a terminal does not report events for an extended period, the LCS client / AF may cancel the location flow by assuming that the terminal has already disconnected the location service session (LCS session).

[0098] Below, we will explain the consequences of not submitting event reports for different types of event reports.

[0099] (1) Area-based event reporting: In this type, the LCS client / AF provides a target area, and if the target area is larger than the event report allowed area, location information cannot be collected within the target area but outside the event report allowed area, reducing the amount of location data collected and the LCS client / AF experience. (2) Periodic-based event reporting: Outside the event reporting allowed area, the terminal does not directly report its location, and the LCS client / AF considers the terminal inaccessible and disconnects the connection, which may affect the location provision of some commercial services. (3) Motion-based event reporting: If the event report allowed area is relatively small, the pre-set linear movement distance may exceed the event report allowed area, failing to trigger a report and leading to a reduction in reported information.

[0100] When conditional event reporting is possible outside the event reporting allowed area, the LCS client / AF can, in this way, have some knowledge of the terminal's location outside the event reporting allowed area, while still maintaining the LCS session (location service period) and taking power conservation into consideration. For example, depending on the power conservation status of the UE terminal itself, it can report occasionally or reduce the reporting frequency so that the network side knows that the terminal's event reporting is still active.

[0101] Below, we will explain the advantages of performing conditional event reporting outside the event report allowed area for different types of event reports.

[0102] (1) Area-based event reporting: In this type, the terminal is allowed to report its location within the target area but outside the event report allowed area, satisfying the LCS client / AF's location information collection needs while also taking into account the terminal's actual power consumption. (2) Periodic-based event reporting: Outside the area, the terminal will make conditional reports considering its own power consumption, and will still be able to maintain connectivity to some commercial services. (3) Motion-based event reporting: If the event report allowed area is relatively small, the predetermined linear movement distance may exceed the area, and in such cases, event reporting will still be maintained.

[0103] As this demonstrates, performing conditional event reporting outside the event reporting allowed area can satisfy both the demand for location services and the need for terminal power saving.

[0104] Selectively, step 403 "the terminal reports an event based on the event reporting configuration information" includes at least one of the following E-1 to E-10.

[0105] Section E-1: If the event reporting configuration information includes the target instruction information, and the target instruction information indicates that the terminal does not need to report an event outside the first area, the terminal will not report an event outside the first area, i.e., if it understands the reporting instruction based on the "Understanding Method 1", then if the target instruction information received by the terminal indicates that it does not need to report an event outside the first area, the terminal will not report an event when it is outside the first area.

[0106] Section E-2: If the event reporting configuration information includes the target instruction information and the reporting policy, and the target instruction information indicates that the terminal needs to report an event outside the first area, the terminal will report an event outside the first area based on the reporting policy, i.e., understand the reporting instruction based on the "Understanding Method 1", then if the terminal has received the target instruction information and the reporting policy, and the target instruction information indicates that the terminal needs to report an event outside the first area, the terminal will perform a conditional event report based on the reporting policy when it is outside the first area.

[0107] Section E-3: If the event reporting configuration information includes the target instruction information, and the reporting configuration information does not include the reporting policy, and the target instruction information indicates that the terminal needs to report an event outside the first area, the terminal may not report an event outside the first area, or the terminal may report an event outside the first area based on its realization, i.e., understand the reporting instruction based on the "Understanding Method 1" above, and the terminal has received the target instruction information but has not received the reporting policy, and the target instruction information indicates that the terminal needs to report an event outside the first area, then the terminal may not report an event when it is outside the first area, or it may report an event depending on the actual situation of the terminal.

[0108] Section E-4: If the first information includes the reporting instruction, and the reporting instruction instructs not to report an event outside the first area, and the terminal does not report an event outside the first area, i.e., understands the reporting instruction based on the "Understanding Method 2", then if the reporting instruction instructs not to report an event outside the first area, the network does not need to send a reporting policy to the terminal, and in this way, the terminal does not report an event when it is outside the first area.

[0109] Section E-5: If the first information includes the reporting instruction, and the reporting instruction instructs to report an event outside the first area, and the event reporting configuration information includes the reporting policy, the terminal reports an event outside the first area based on the reporting policy, i.e., understands the reporting instruction based on the "Understanding Method 2", and if the reporting instruction instructs to report an event outside the first area, the network may send the reporting policy to the terminal, and in this way, the terminal may perform conditional event reporting based on the reporting policy when it is outside the first area.

[0110] Section E-6: If the first information includes the reporting instruction, and the reporting instruction instructs to report an event outside the first area, and the event reporting configuration information does not include the reporting policy, the terminal may not report an event outside the first area, or the terminal may report an event outside the first area based on its realization, i.e., if it understands the reporting instruction based on the "Understanding Method 2", and this reporting instruction instructs to report an event outside the first area, the network does not need to send a reporting policy to the terminal. Thus, when the terminal is outside the first area, it does not need to report an event, and may report an event depending on the actual situation of the terminal.

[0111] Section E-7: If the first information includes the reporting instruction, and the reporting instruction indicates a first level, and the event reporting configuration information does not include the reporting policy, then the terminal does not report events outside the first area, i.e., if the reporting instruction is understood in accordance with "Understanding Method 3", then the first level is characterized by the terminal not reporting events outside the first area (i.e., the first level is an implicit instruction that "the terminal does not report events outside the first area"), then when the reporting instruction indicates a first level, the network does not need to send a reporting policy to the terminal, and thus the terminal does not need to report events when it is outside the first area.

[0112] Section E-8: If the first information includes the reporting instruction, and the reporting instruction indicates a second level, and the event reporting configuration information includes the reporting policy, and the terminal reports an event outside the first area and within the second area based on the reporting policy, i.e., if the terminal understands the reporting instruction based on the "Understanding Method 3", then when the reporting instruction indicates the second level, the network side may send the reporting policy to the terminal, and in this way the terminal may report a conditional event when it is outside the first area and within the second area.

[0113] Section E-9: If the first information includes the reporting instruction, and the reporting instruction indicates a third level, and the event reporting configuration information includes the reporting policy, and the terminal reports an event outside the first area based on the reporting policy, i.e., when the terminal understands the reporting instruction based on "Understanding Method 3", the network may send the reporting policy to the terminal when the reporting instruction indicates a third level, if the third level is characterized by the terminal reporting a conditional event outside the first area (i.e., the third level is an implicit indication that "the terminal reports a conditional event outside the first area").

[0114] Section E-10: If the first information includes the reporting instruction, and the reporting instruction indicates the second or third level, and the event reporting configuration information does not include the reporting policy, the terminal will not report an event outside the first area, or the terminal will report an event outside the first area based on its realization. That is, if the reporting instruction is understood based on the "Understanding Method 3", and the reporting instruction indicates the second or third level, the network does not need to send a reporting policy to the terminal, and in this way, the terminal does not need to report an event when it is outside the first area, and may report an event depending on the actual situation of the terminal.

[0115] Selectively, the reporting policy includes at least one of the following items D-1 to D-3:

[0116] Section D-1: Maximum number of event reports, Item D-2: Minimum time interval between two adjacent event reports, Item D-3: Trigger conditions for event reporting to specify threshold information other than the minimum time interval and the maximum number of reports.

[0117] Here, clause D-1 is used to indicate that when a terminal performs conditional event reporting, the number of reports must not exceed the maximum number of reports. For example, when a terminal performs conditional event reporting outside the first area, it will not continue to perform event reporting outside the first area after the number of event reports outside the first area has reached the maximum number of reports.

[0118] Clause D-2 is used to indicate that when a terminal performs conditional event reporting, the time interval between two adjacent event reports must not exceed the minimum time interval.

[0119] Section D-3 represents other constraints that enable conditional event reporting, for example, event reporting only occurs when the straight-line distance traveled reaches 100m.

[0120] Selectively, the terminal may perform event reporting based on the reporting policy. The terminal performs conditional event reporting based on at least one of the maximum number of reports, the minimum time interval, and the trigger condition.

[0121] For example, if the reporting policy includes the maximum number of reports (x), the minimum time interval (t), and the trigger condition (F condition), the terminal will perform conditional event reporting outside the first domain based on this reporting policy. That is, when the terminal detects condition F outside the first domain, it will perform an event report according to t, and when the number of reports reaches x, it will stop reporting. The constraints for reporting outside the first domain are stricter than those for reporting within the first domain, such as a lower maximum number of reports, a longer minimum reporting interval, and a longer linear travel distance.

[0122] Selectively, the above method, The terminal further includes transmitting a third piece of information containing the changed information from the first piece of information when at least one piece of information contained in the first piece of information changes.

[0123] As can be seen from this, if at least one of the following pieces of information changes: "second area, reporting instructions, area usage instructions, policy set," the terminal may send the changed information to the first network-side device.

[0124] Here, the method by which the terminal transmits the third information is the same as the method by which the terminal transmits the first information described in the preceding paragraph; that is, the terminal transmits the third information to the third network-side device, the third network-side device transmits it to the second network-side device, and the second network-side device then provides the third information to the first network-side device.

[0125] Selectively, the above method, The terminal receives a fourth piece of information, wherein the fourth piece of information includes at least one of the first area and the event reporting configuration information, and the fourth piece of information is determined based on the third piece of information. The terminal further includes reporting an event based on the fourth piece of information.

[0126] As can be seen, if at least one piece of information among the terminal's "second area, reporting instructions, area usage instructions, and policy set" changes, the first network-side device may further update the first area and event reporting configuration information (including at least one of the target instruction information and the reporting policy) based on the changed information, thereby sending the updated information (i.e., the fourth piece of information) to the terminal so that the terminal can perform event reporting based on this fourth piece of information. In this way, the event reporting status can be adapted to the actual situation of the terminal.

[0127] Here, the first network-side device transmits the fourth information to the third network-side device, which then transmits it to the fifth network-side device (e.g., LMF), and the fifth network-side device then transmits it to the terminal.

[0128] According to a second embodiment, as shown in Figure 7, the embodiment of the present application further provides an event reporting method which may include the following steps 701 to 703.

[0129] Step 701: The first network-side device obtains the first information of the terminal.

[0130] Here, the first information is used to indicate relevant information for which the terminal reports events outside the first area, and the first area is an area in which the terminal is permitted to report events; that is, the first area is the event report allowed area described in the preamble. Selectively, the terminal reporting events outside the first area may specifically mean that the terminal reports conditional events outside the first area. Here, the constraints that enable the conditional event reporting may be constraints indicated by a reporting policy configured on the network side.

[0131] Furthermore, in the embodiments of this application, the terminal can report a power saving area (used to instruct the terminal to report events within this area) to the network, and the network can determine the event report allowed area based on the power saving area, generally converting fine-grained areas to coarse-grained areas, for example, converting a rectangular area into a single TA list or cell list, as shown in Figure 5.

[0132] Furthermore, the first piece of information described above is used to indicate the relevant information for which the terminal reports events outside the first domain; that is, the first piece of information is used to indicate at least one of the relevant parameter information, capabilities, or actions of whether or not to report events outside the first domain.

[0133] Selectively, the first piece of information includes at least one of the following items A-1 to A-3.

[0134] A-1: A second area for the terminal to indicate the area where it wishes to report events. Section A-2: Reporting instructions (i.e., Power saving class) to indicate whether the terminal supports reporting events outside the first area, or whether the terminal reports events outside the first area, or to indicate at least one level regarding the terminal reporting events outside the first area. Section A-3: Area usage indication for indicating whether the first area is to be used in the forward direction or in the reverse direction.

[0135] For a detailed interpretation of items A-1 to A-3 above, please refer to the previous explanation; no further explanation will be provided here.

[0136] Selectively, step 701 "The first network-side device obtains the first information of the terminal" is performed. This includes the first network-side device acquiring the first information from the second network-side device, wherein the first information stored in the second network-side device is transmitted by the terminal to the second network-side device via the third network-side device.

[0137] As can be seen from this, the terminal can transmit the first information to the third network-side device, which in turn transmits it to the second network-side device, and the second network-side device can then provide the first information to the first network-side device, where the first network-side device may be a GMLC, the second network-side device may be a UDM, and the third network-side device may be an AMF.

[0138] Step 702: The first network-side device acquires event reporting configuration information that matches the first information.

[0139] Here, the first piece of information is used to indicate the relevant information (i.e., at least one of the relevant parameter information, capabilities, or reporting behavior) for the terminal to report an event outside the first domain. Therefore, the event reporting configuration information matches the first piece of information, i.e., the event reporting configuration information matches at least one of the relevant parameter information, capabilities, or reporting behavior for the terminal to report an event outside the first domain.

[0140] Selectively, the event reporting configuration information includes at least one of the following items C-1 to C-2.

[0141] Section C-1: Target instruction information for indicating whether the terminal needs to report an event outside the first area, Section C-2: A reporting policy that specifies at least one constraint condition under which a terminal should report events.

[0142] For a detailed interpretation of the above sections C-1 and C-2, please refer to the previous explanation; no further explanation will be provided here.

[0143] Step 703: The first network-side device transmits the reporting configuration information to the terminal.

[0144] Selectively, step 703 "The first network-side device transmits the event reporting configuration information to the terminal" is, The first network-side device transmits the event reporting configuration information to the terminal via the third and fifth network-side devices.

[0145] Here, the third network-side device may be an AMF, and the fifth network-side device may be an LMF.

[0146] As can be seen, the first network-side device transmits the reporting configuration information to the third network-side device, which in turn transmits the reporting configuration information to the fifth network-side device, and the fifth network-side device of the LMF can then transmit the reporting configuration information to the terminal.

[0147] As can be seen from steps 701 to 703 above, in the embodiments of this application, a terminal can transmit first information to a first network-side device, and the first network-side device can transmit event reporting configuration information to the terminal by obtaining event reporting configuration information that matches the first information, thereby enabling the terminal to perform event reporting based on the event reporting configuration information, where the first information is used to indicate relevant information for which the terminal will perform event reporting outside a first area, and the first area (i.e., event report allowed area) is an area in which the terminal is permitted to perform event reporting. As can be seen thereafter, in the embodiments of this application, a terminal can report to the first network-side device relevant information (i.e., first information) for which it will perform event reporting outside the event report allowed area, thereby enabling the first network-side device to configure appropriate event reporting configuration information for the terminal based on this relevant information, and further enabling the terminal to perform more appropriate event reporting outside the event report allowed area. Therefore, embodiments of this application provide a method for a terminal to perform event reporting outside the event report allowed area.

[0148] Selectively, the reporting policy includes at least one of the following items D-1 to D-3:

[0149] Section D-1: Maximum number of event reports, Item D-2: Minimum time interval between two adjacent event reports, Item D-3: Trigger conditions for event reporting to specify threshold information other than the minimum time interval and the maximum number of reports.

[0150] For a detailed interpretation of items D-1 and D-2 above, please refer to the previous explanation; no further explanation will be provided here.

[0151] Selectively, when the event reporting configuration information includes the reporting policy, the first network-side device obtaining event reporting configuration information that matches the first information includes one of the following F-1 to F-2.

[0152] Section F-1: When a reporting instruction indicates that the terminal supports event reporting outside the first area, or that the terminal reports events outside the first area, or indicates a second or third level, the first network-side device determines the event reporting configuration information (i.e., determines the reporting policy included in the event reporting configuration information) based on the location service type and subscription information related to the terminal's location, In Section F-1, the first network-side device may further determine the reporting policy that needs to be sent to the terminal, in combination with the first area, the second area, reporting instructions, area usage instructions, location service type, and subscription information related to the terminal's location.

[0153] In other words, in one embodiment, the first network side is, The fourth type of network-side equipment (i.e., the type of equipment requesting location services (e.g., LCS client / AF)), Location-based work type (i.e., deferred 5GC-MT-LR type (area, periodic, or motion)), Subscription information related to the device's location, The first area and, The second area and, Reporting instructions, Based on at least one piece of information, such as area usage instructions, a reporting policy that needs to be sent to the terminal may be determined.

[0154] Section F-2: When the reporting instruction indicates that the terminal supports event reporting outside the first area, or that the terminal reports events outside the first area, or indicates the second or third level, the first network-side device determines the event reporting configuration information (i.e., determines the reporting policy included in the event reporting configuration information) based on the reporting policy received from the fourth network-side device, As can be seen therein, the fourth network-side device (i.e., the device requesting location services) may send a reporting policy to the first network-side device so that the first network-side device can determine which reporting policy needs to be sent to the terminal based on the reporting policy sent by the fourth network-side device.

[0155] Here, selectively, the process by which the first network-side device receives a reporting policy transmitted by the fourth network-side device includes the first network-side device receiving a location service request transmitted by the fourth network-side device, which carries the reporting policy.

[0156] In other words, the fourth network-side device may carry the reporting policy that needs to be sent to the first network-side device in the location service request.

[0157] Section F-3: If the first information further includes a policy set, and the reporting instruction indicates that the terminal supports event reporting outside the first area, or that the terminal reports events outside the first area, or indicates the second or third level, the first network-side device selects a candidate reporting policy from the policy set based on the location service type, determines the event reporting configuration information based on the selected candidate reporting policy (i.e., determines the reporting policy to be included in the event reporting configuration information), where the policy set includes at least one candidate reporting policy.

[0158] As can be seen from Section F-3, a terminal can send a policy set to a first network-side device (for example, the terminal sends the policy set to a third network-side device, which then sends it to a second network-side device, which then provides the policy set to the first network-side device), and in this way, the first network-side device can select one candidate reporting policy from this policy set and, based on this selected candidate reporting policy, determine which reporting policy needs to be sent to the terminal.

[0159] Here, when the first network-side device selects a candidate reporting policy from the policy set, it may consider the location-based work type, and may also combine this with subscription information related to the terminal's location.

[0160] Here, the first network-side device may select a candidate reporting policy from the policy set as the reporting policy that needs to be sent to the terminal, and may select some constraints from this candidate reporting policy as constraints for the reporting policy that needs to be sent to the terminal.

[0161] Furthermore, if the reporting configuration information includes target instruction information, the first network-side device determines the target instruction information based on the reporting instruction, that is, it understands the reporting instruction based on "Understanding Method 1" above, and if the reporting instruction is characterized by capability, then if the reporting instruction indicates that the terminal supports reporting events outside the first area, the target instruction information indicates that the terminal reports events outside the first area; if the reporting instruction indicates that the terminal does not support reporting events outside the first area, the target instruction information indicates that the terminal does not report events outside the first area. If the reporting instruction is based on "Understanding Method 2 or 3" above, there is no need to determine the target instruction information based on this reporting instruction, that is, in such cases, the event reporting configuration information does not include target instruction information.

[0162] Selectively, the above method, The first network-side device further transmits second information to a fourth network-side device, wherein the second information includes at least one of the following items G-1 to G-5.

[0163] Section G-1: The first area mentioned above, Section G-2: A reporting instruction to indicate whether the terminal supports reporting events outside the first area, or a reporting instruction to indicate whether the terminal reports events outside the first area. Section G-3: The event reporting configuration information (which may include at least one of the target instruction information and the reporting policy), Section G-4: Area usage instruction for indicating whether to use the first area in the forward direction or the first area in the reverse direction. Section G-5: A Target area error indication for indicating that there is no overlapping area between the Target area and the second area (Power saving area) or that a logical error exists in the Target area, wherein the Target area is the area in which the terminal wishes to report events (i.e., the area in which the network side wishes the terminal to report events; for example, a location service request may include one area in which the network side wishes to obtain location information of the terminal in this area, and this area is the Target area), and the second area is used to indicate the area in which the terminal wishes to report events.

[0164] For the related interpretations of clauses G-1 to G-4, please refer to the previous explanation; no further explanation will be provided here.

[0165] Furthermore, regarding Section G-5, the type that applies only to location service requests is area-based event reporting, where the target area error cause may be understood as the reason in a rejection message that rejects a location service request message, characterized by an incorrect Target area requested by the LCS location server request message, for example, if the Target area and the Power saving area do not overlap or there is a logical error, the Target area needs to be corrected. For example, if the Power saving area is region A, but the Target area is the country to which region A belongs, then in area-based event reporting, if the user has never left this country, it will never trigger a leaving or enter type report, and the user always needs to report their location within this country, then the Target area here is considered too large and falls under the category of having a logical error.

[0166] To make it easier to understand, the target area error cause may be used to indicate that there is no overlap between the target area and the first area (i.e., the event report allowed area).

[0167] Furthermore, if the fourth network-side device receives a target area error cause indicating that the target area is incorrect, the fourth network-side device may restart a location service request, which carries the re-determined target area.

[0168] Selectively, the above method, If the first network-side device subscribes to the terminal's information, the first network-side device further includes obtaining third information provided by the second network-side device, wherein the third information includes changed information from the first information, and the third information stored in the second network-side device is transmitted by the terminal to the second network-side device via the third network-side device.

[0169] As can be seen, if at least one of the pieces of information among "second area, reporting instructions, area usage instructions, and policy sets" changes, the terminal can send the changed information (i.e., third information) to the second network-side device, and if the first network-side device has subscribed to the terminal's information from the second network-side device, the second network-side device can provide the third information to the first network-side device after receiving it.

[0170] Selectively, the above method, The first network-side device updates a fourth piece of information, which includes at least one of the first area and the event reporting configuration information, based on the third piece of information. The first network-side device further includes transmitting the updated fourth information to the terminal.

[0171] As can be seen, if at least one piece of information among the terminal's "second area, reporting instructions, area usage instructions, and policy set" changes, the first network-side device may further update the first area and event reporting configuration information (including at least one of the target instruction information and the reporting policy) based on the changed information, thereby sending the updated information (i.e., the fourth piece of information) to the terminal so that the terminal can perform event reporting based on this fourth piece of information. In this way, the event reporting status can be adapted to the actual situation of the terminal.

[0172] Here, the first network-side device transmits the fourth information to the third network-side device, which then transmits it to the fifth network-side device (e.g., LMF), and the fifth network-side device then transmits it to the terminal.

[0173] Furthermore, the first network-side device may determine the fourth piece of information based on the third piece of information, in combination with the target area, the first area currently in use, the reporting policy currently in use, and the current reporting status (i.e., report status, such as the number of reports to date, reporting duration, etc.).

[0174] According to a third aspect, embodiments of the present application further provide an event reporting method, the method comprising the following step H-1.

[0175] Step H-1: The fourth network-side device sends a reporting policy to the first network-side device that specifies at least one constraint that the terminal must use to report events.

[0176] Here, the fourth network-side device may be an LCS client / AF.

[0177] Here, the first network-side device may determine which reporting policy needs to be sent to the terminal based on the reporting policy sent by the fourth network-side device.

[0178] Selectively, step H-1 "The fourth network-side device transmits the reporting policy to the first network-side device" is, The fourth network-side device includes transmitting a location service request carrying the reporting policy to the first network-side device.

[0179] As can be seen, the fourth network-side device (i.e., the device requesting location services) may carry a reporting policy in the location service request sent to the first network-side device, so that the first network-side device can determine which reporting policy needs to be sent to the terminal based on the reporting policy carried in the location service request.

[0180] Selectively, the above method, The fourth network-side device further includes receiving second information transmitted by the first network-side device, wherein the second information includes at least one of the following items G-1 to G-5.

[0181] Section G-1: The first area mentioned above, Section G-2: A reporting instruction to indicate whether the terminal supports reporting events outside the first area, or a reporting instruction to indicate whether the terminal reports events outside the first area. Section G-3: The event reporting configuration information (which may include at least one of the target instruction information and the reporting policy), Section G-4: Area usage instruction for indicating whether to use the first area in the forward direction or the first area in the reverse direction. Section G-5: A Target area error indication for indicating that there is no overlapping area between the Target area and the second area (Power saving area) or that a logical error exists in the Target area, wherein the Target area is the area in which the terminal wishes to report events (i.e., the area in which the network side wishes the terminal to report events; for example, a location service request may include one area in which the network side wishes to obtain location information of the terminal in this area, and this area is the Target area), and the second area is used to indicate the area in which the terminal wishes to report events.

[0182] For the related interpretations of paragraphs G-1 to G-5, please refer to the previous explanation; no further explanation will be provided here.

[0183] Furthermore, if the fourth network-side device receives a target area error, the fourth network-side device may restart a location service request, which carries the re-determined target area.

[0184] According to a fourth aspect, the embodiments of the present application further provide an event reporting method comprising the following steps K-1 to K-2.

[0185] Step K-1: The second network-side device acquires the first information of the terminal and stores the first information.

[0186] Here, the first information is used to indicate relevant information for which the terminal reports events outside the first area, and the first area is an area in which the terminal is permitted to report events.

[0187] Furthermore, the second network-side device may receive the first information transmitted by the terminal via the third network-side device.

[0188] Step K-2: The second network-side device provides the first network-side device with the first information.

[0189] Selectively, the second network-side device may acquire the first information of the terminal. This includes the second network-side device receiving the first information transmitted by the terminal via the third network-side device.

[0190] Here, the second network-side device may be a UDM, the third network-side device may be an AMF, and the first network-side device may be a GMLC.

[0191] Here, the first network-side device may, after acquiring the first information, acquire event reporting configuration information that matches the first information, and then transmit the event reporting configuration information to the terminal so that the terminal can perform event reporting based on this event reporting configuration information.

[0192] Selectively, the first piece of information includes at least one of the following items A-1 to A-3.

[0193] A-1: A second area for the terminal to indicate the area where it wishes to report events. Section A-2: Reporting instructions (i.e., Power saving class) to indicate whether the terminal supports reporting events outside the first area, or whether the terminal reports events outside the first area, or to indicate at least one level regarding the terminal reporting events outside the first area. Section A-3: Area usage indication for indicating whether the first area is to be used in the forward direction or in the reverse direction.

[0194] For a detailed interpretation of items A-1 to A-3 above, please refer to the previous explanation; no further explanation will be provided here.

[0195] Selectively, the first information further includes a set of policies, the set of policies including at least one candidate reporting policy.

[0196] Selectively, the above method, The second network-side device receives the third information transmitted by the first terminal and stores the third information, including the changed information from the first information. The second network-side device further provides the first network-side device with the third information.

[0197] As can be seen, if at least one of the pieces of information among "second area, reporting instructions, area usage instructions, and policy set" changes, the terminal can send the changed information (i.e., third information) to the second network-side device, and if the first network-side device has subscribed to the terminal's information from the second network-side device, the second network-side device can provide the third information to the first network-side device after receiving it.

[0198] In summary, specific embodiments of the event reporting method of the embodiment of this application may be as shown in the following embodiments 1 to 4.

[0199] Embodiment 1: As shown in Figure 8, the following steps 81 to 819 are included.

[0200] Step 81: The terminal sends a NAS signaling to the AMF, which carries the first information, and this first information includes at least one of the following items (1) to (5).

[0201] (1) UE ID (i.e., terminal identifier), (2) Message type, (3) Power saving area (i.e., the second area, i.e., the area represented by coordinates or TA / cell, which is used to describe the execution of event reports within this area when the terminal is in a power-saving state), (4) Power saving class (i.e., reporting instruction), where there may be three ways of understanding the power saving class.

[0202] Understanding Method 1: Represents the terminal's ability to characterize whether the terminal supports reporting events outside the event report allowed area (i.e., the first area), and in one embodiment, the reporting instruction includes two global mutually exclusive settings: one in which the terminal supports reporting events outside the event report allowed area, and the other in which the terminal does not support reporting events outside the event report allowed area, the latter being the default setting.

[0203] Understanding Method 2: This instructs the terminal whether to perform an event report outside the event report allowed area, i.e., it instructs the terminal to perform an event report outside the event report allowed area.

[0204] Understanding Method 3: This indicates the level at which the terminal reports events outside the event report allowed area, i.e., the terminal is in a power-saving state.

[0205] Here, the mode for carrying out the invention with respect to the above understanding method 2 may be as follows.

[0206] In one embodiment, the Power saving class has two values: 0 indicates that it will not be executed, and 1 indicates that it will be executed conditionally.

[0207] Regarding the above understanding method 3, the form for carrying out the invention may be as follows.

[0208] In one embodiment, the power saving class includes two levels, high and low, which characterize whether the terminal performs an event report outside the event report allowed area, with high indicating no event report and low indicating conditional event report performance.

[0209] In another embodiment, the type applicable to LCS client / AF requests is area-based event reporting, where the Power saving class includes different levels: high, medium, and low. At the high level, the policy is that the terminal performs event reporting only within the event reporting allowed area. At the medium level, the policy is that the terminal must perform event reporting within the event reporting allowed area and conditional reporting outside the event reporting allowed area and within the Power saving area. At the low level, the policy is that the terminal must perform event reporting within the event reporting allowed area and conditional reporting outside the event reporting allowed area.

[0210] (5) Area usage indication (i.e., area usage instruction) that indicates whether the event report allowed area is used in the forward or reverse direction. In one embodiment, the reporting instruction includes two global mutually exclusive settings for the following event report allowed area: one for reverse use and the other for forward use, the latter being the default setting.

[0211] Here, the terminal may carry the first information into 5GMM capability information and package this 5GMM capability information into a registration request message, thereby sending this registration request to the AMF. Alternatively, the terminal may send this registration request to the AMF by packaging the first information into a new IE (registration request) message. Alternatively, the device may send the first information to the AMF via a UE Location Privacy Setting Request message. Alternatively, the terminal may transmit the first information to the AMF via an uplink non-access layer transmission (UL NAS TRASPORT) message.

[0212] Step 82: The AMF sends a Nudm_ParameterProvision_Update message to the UDM, which contains the first piece of information mentioned above (i.e., UE ID, Power saving area, Power saving class, area usage indication, etc.).

[0213] Step 83: The UDM stores the initial information received (i.e., the Power saving area, Power saving class, and area usage indication for this UE ID).

[0214] Step 84: The LCS client / AF sends a Location Service Request (LCS service request) to the GMLC, i.e., requests the terminal to perform delay reporting.

[0215] Here, it should be explained that an untrusted AF needs to perform service verification as an intermediate network element via the NEF, the AF starts subscribing to the NEF, and the NEF starts a location request to the GMLC.

[0216] Step 85: GMLC sends a Nudm_SDM_get or UDM Network Element Subscription Data Subscribe Request message (Nudm_SDM_subscribe) to the UDM to query subscription information related to the UE ID location, retrieves the first information (i.e., information such as Power saving area, Power saving class, area usage indication, etc.) and stores it.

[0217] This step may be a one-time query or a subscription; only in the case of a subscription does step 115 in the subsequent Example 4 occur.

[0218] Step 86: GMLC performs at least one of the following (1) to (3).

[0219] (1) Determine the event report allowed area (i.e., the first area), which may be determined based on, for example, the power saving area. (2) Determine target instruction information, which is used to characterize whether the terminal needs to perform an event report outside the event report allowed area. In other words, based on "Understanding Method 1" above, i.e., if the Power saving class in step 81 is capability, the GMLC here determines whether the terminal needs to report outside the area. However, based on "Understanding Method 2 or Understanding Method 3" above, i.e., if the Power saving class in step 81 indicates that the terminal is at a power saving level, the GMLC does not need to determine this target instruction information.

[0220] (3) Determine a strategy (i.e., reporting policy) to characterize the constraints under which a terminal reports events outside the event report allowed area, and include at least one of the following parameters (a) to (c):

[0221] (a) Maximum number of reports (i.e., maximum number of event reports), (b) Minimum reporting time interval (i.e., minimum time interval between two adjacent event reports), (c) Trigger conditions for event reporting to specify threshold information other than the minimum time interval and maximum number of reports, one implementation method being to execute an event report only when the straight-line distance traveled reaches a certain threshold (e.g., 100 meters).

[0222] Here, GMLC may determine the values ​​of one or more of the above parameters (a) to (c) based on the business type of the location service request in step 84 (i.e., the type of deferred 5GC-MT-LR (area, periodic, or motion)) and the subscription information related to the location obtained from step 85.

[0223] Furthermore, one embodiment in which GMLC determines a strategy is, for example, that a terminal is required to periodically report within the event report allowed area, but outside the event report allowed area, the periodicity is reduced, i.e., the reporting time interval becomes twice as long as before, there is an upper limit on the number of reports, and after the upper limit is reached, reporting outside the event report allowed area stops.

[0224] Furthermore, if the Power saving class adopts the "Understanding Method 1" described above, the GMLC may determine the target instruction information based on the specific content instructed by the Power saving class. That is, if the Power saving class instructs the terminal to support event reporting outside the event reporting allowed area, the target instruction information instructs the terminal to report events outside the event reporting allowed area. If the Power saving class instructs the terminal not to support event reporting outside the event reporting allowed area, the target instruction information instructs the terminal to report events outside the event reporting allowed area. One implicit embodiment of the target instruction information indicates that when the GMLC sends the target instruction information to the terminal, it instructs the terminal to report events outside the event reporting allowed area. If the GMLC does not send the target instruction information to the terminal, it instructs the terminal to report events outside the event reporting allowed area.

[0225] If the Power saving class indicates that the terminal supports event reporting outside the event reporting allowed area (or if the target instruction information indicates that the terminal reports events outside the event reporting allowed area), the GMLC may further determine at least one constraint of the strategy based on the terminal's location-based work type and location-related subscription information. However, if the Power saving class indicates that the terminal does not support event reporting outside the event reporting allowed area, the GMLC does not need to determine a strategy.

[0226] For example, if the Power saving class adopts the "Understanding Method 2" described above, and the Power saving class instructs the terminal to report events outside the event report allowed area for periodic or motion-based event reporting, the GMLC may further combine this with location-related subscription information to determine at least one constraint of the strategy. However, if the Power saving class instructs the terminal not to report events outside the event report allowed area, the GMLC does not need to determine the strategy.

[0227] For example, if the Power saving class adopts the "Understanding Method 3" described above, and the Power saving class indicates "Medium Level" for area-based event reporting, the GMLC may further determine at least one constraint condition of the strategy, and in this way the terminal performs conditional reporting based on the strategy outside the event reporting allowed area and within the Power saving area. If the Power saving class indicates "Low Level," the GMLC may further determine at least one constraint condition of the strategy, and in this way the terminal performs conditional reporting based on the strategy outside the event reporting allowed area. If the Power saving class indicates "High Level," the GMLC does not need to determine the strategy.

[0228] Step 87: GMLC sends a Namf_Location_ProvidePositioningInfo Request to AMF, which carries the event report allowed area and the target instruction information described above. Furthermore, if GMLC determined a strategy in step 86, this message may also carry the strategy determined by GMLC.

[0229] Step 88: AMF sends a Namf_Location_ProvidePositioningInfo Response to GMLC, confirming that it received the message in Step 87.

[0230] Step 89: GMLC sends second information to the LCS client / AF, where the second information includes at least one of the following (1) to (5):

[0231] (1) Event report allowed area (i.e., as determined by GMLC in step 86), (2) Power saving class, (3) strategy (i.e., what GMLC decided in step 86), (4) Area usage indication, (5) Target area error indication (the type applicable only to LCS client / AF requests is an area-based event report), which may be understood as the cause in the rejection message that rejects the request message in step 84, characterized by an incorrect Target area requested by the LCS client / AF, for example, that the Target area and the Power saving area have no overlapping areas or a logical error and the Target area needs to be corrected.

[0232] Step 810: The AMF, RAN, and UE perform steps 39-313 described in the preamble, wait for the terminal to enter a connected state, establish a connection with the terminal, and complete user privacy verification.

[0233] Step 811: The AMF sends an Nlmf_Location_DetermineLocation Request to the LMF, where this message carries the event report allowed area and the target instruction information mentioned above. Furthermore, if the AMF received a strategy in step 87, this message may also carry the strategy received by the AMF. Step 812: Terminal Location Flow, i.e., LMF executes one or more location flows to request and obtain the terminal's location. Step 813: The LMF sends an LCS Periodic-Triggered Invoke Request message to the UE, which carries the event report allowed area and the target instruction information. Furthermore, if the LMF received a strategy in step 811, this message may also carry the strategy received by the LMF. Step 814: The UE sends an LCS Periodic-Triggered Invoke Return to the LMF. Step 815: LMF sends Nlmf_Location_DetermineLocation Response to AMF, Step 816: AMF sends Namf_Location_EventNotify to GMLC, Step 817: GMLC sends an LCS Service Response to the LCS Client / AF. Step 818: The terminal detects the event and performs the corresponding operation. In other words, the UE detects an event trigger and, if it is outside the event report allowed area, performs at least one of the following actions (1) to (10).

[0234] (1) If the Power saving class instructs the UE not to perform reporting outside the event report allowed area, the UE will not perform reporting (i.e., step 819 will not exist), (2) If the Power saving class instructs the UE to perform event reporting outside the event reporting allowed area and the UE receives a strategy in step 813, the UE will perform conditional event reporting outside the event reporting allowed area in accordance with the strategy. (3) If the Power saving class instructs the UE to perform event reporting outside the event report allowed area, but the strategy has not been received in step 813, the UE will not perform event reporting outside the event report allowed area, or the UE will perform event reporting based on the realization. (4) If the target instruction information received in step 813 indicates that the UE does not perform event reporting outside the event report allowed area or has not received target instruction information, the UE does not perform event reporting (i.e., step 819 does not exist), (5) If the target instruction information received in step 813 instructs the UE to perform event reporting outside the event report allowed area, and if a strategy is received in step 813, the UE will perform conditional event reporting outside the event report allowed area in accordance with the strategy. (6) If the target instruction information received in step 813 instructs the UE to perform event reporting outside the event report allowed area, but no strategy is received in step 813, the UE will not perform event reporting outside the event report allowed area, or the UE will perform event reporting based on the realization. (7) If the power saving class indicates "high level", the UE does not perform the report (i.e., step 819 does not exist), (8) If the Power saving class is set to "Medium level" and the strategy is received in step 813, the UE will perform conditional event reporting according to the strategy, outside the event report allowed area and within the Power saving area. (9) If the Power saving class is set to "low level" and the strategy is received in step 813, the UE will perform conditional event reporting according to the strategy outside the event report allowed area. (10) If the Power saving class indicates “medium or low level” but no strategy is received in step 813, the UE will either not perform event reporting outside the event report allowed area, or the UE will perform event reporting based on the realization.

[0235] Here, regarding the UE performing conditional reporting according to the strategy, in combination with the example in step 86, for example, if the strategy includes two parameters, a maximum number of reports and a minimum time interval, then when the UE is outside the event report allowed area, the time interval for each report must be greater than the minimum time interval, and the number of reports must not be greater than the maximum number of reports.

[0236] Step 819: Execute the event reporting flow, which is the same as steps 323-330b-2 described in the preceding paragraph, and will not be explained further here.

[0237] Embodiment 2: As shown in Figure 9, this includes the following steps 91 to 919.

[0238] Steps 91 to 93 are the same as steps 81 to 83 in the above embodiment 1, and will not be explained further here.

[0239] Step 94: The LCS client / AF sends an LCS service request to the GMLC, that is, requests the terminal to execute a delay report. Here, the strategy is carried in the LCS service request. Step 95 is the same as Step 95 in the above Embodiment 1, and will not be described herein again.

[0240] Step 96: The GMLC executes at least one of the following (1) to (3).

[0241] (1) Determine the event report allowed area (i.e., the first area), for example, it may be determined based on the power saving area. (2) Determine the target indication information, which is used to characterize whether the terminal needs to execute an event report outside the event report allowed area. That is, based on the above "Understanding Method 1", that is, when the power saving class in the above Step 81 is the capability, the GMLC determines here whether the terminal needs to report outside the area. Based on the above "Understanding Method 2", that is, when the power saving class in the above Step 81 represents that the terminal is at the power saving level, the GMLC does not need to determine this target indication information.

[0242] (3) Determine a strategy (i.e., a reporting policy) for characterizing the constraint conditions for the terminal to perform an event report outside the event report allowed area, including at least one parameter of the following (a) to (c).

[0243] (a) The maximum number of reports (i.e., the maximum number of event reports). (b) The minimum reporting time interval (i.e., the minimum time interval between two adjacent event reports). (c) Trigger conditions for event reporting to specify threshold information other than the minimum time interval and maximum number of reports, one implementation method being to execute an event report only when the straight-line distance traveled reaches a certain threshold (e.g., 100 meters).

[0244] It should be explained here that, since a strategy is carried in the LCS service request in step 95 above, if the Power saving class instructs the terminal to support event reporting outside the event reporting allowed area, or to report an event outside the event reporting allowed area, or to instruct "medium level or low level", then in step 96, the GMLC may make the strategy carried in the LCS service request the strategy that needs to be sent to the UE (i.e., in such cases the GMLC does not need to determine the strategy in step 96), or it may select some of the constraints (i.e., parameters) included in the strategy carried in the LCS service request as constraints (i.e., parameters) of the strategy that needs to be sent to the UE.

[0245] Steps 97 and 98 are the same as steps 87 and 88 in the above embodiment 1, and will not be explained further here.

[0246] Step 99: GMLC sends second information to the LCS client / AF, where the second information includes at least one of the following (1) to (5):

[0247] (1) Event report allowed area (i.e., as determined by GMLC in step 86), (2) Power saving class, (4) Area usage indication, (5)Target area error indication.

[0248] In other words, in Embodiment 2, step 99 is the same as step 89 in Embodiment 1, in that the second information sent from GMLC to LCS client / AF does not include strategy.

[0249] Steps 99 to 919 are the same as steps 89 to 819 in the above embodiment 1, and will not be explained further here.

[0250] Embodiment 3: As shown in Figure 10, this includes the following steps 101 to 1019.

[0251] Step 101: The terminal sends a NAS signaling to the AMF, which carries the first information, and this first information includes at least one of the following items (1) to (5).

[0252] (1) UE ID (i.e., terminal identifier), (2) Message type, (3) Power saving area, (4) Power saving class, (5) A policy set containing at least one candidate strategy, where different strategies in this policy set are applied to different location types, and GMLC can then select the appropriate strategy from the policy set according to different subsequent tasks.

[0253] Step 102: AMF sends Nudm_ParameterProvision_Update to the UDM, which carries the first piece of information mentioned above (i.e., UE ID, Power saving area, Power saving class, area usage indication, policy set, etc.).

[0254] Step 103: The UDM stores the received first piece of information (i.e., stores the power saving area, power saving class, area usage indication, and policy set of this UE ID).

[0255] Step 104 is the same as Step 84 in Embodiment 1 above and will not be described further here.

[0256] Step 105: The GMLC sends a Nudm_SDM_get or Nudm_SDM_subscribe message to the UDM to query the subscription information related to the location of the UE ID, and obtains and stores the first piece of information (i.e., information such as the power saving area, power saving class, area usage indication, and policy set).

[0257] Step 106: The GMLC executes at least one of the following (1) to (3).

[0258] (1) Determine the event report allowed area (i.e., the first area), which may be determined based on, for example, the power saving area. (2) Determine the target indication information, which is used to characterize whether the terminal needs to execute an event report outside the event report allowed area. That is, based on the above "Understanding Method 1", that is, when the power saving class in Step 81 above is the capability, the GMLC determines here whether the terminal needs to report outside the area. Based on the above "Understanding Method 2", that is, when the power saving class in Step 81 above represents that the terminal is at the power saving level, the GMLC does not need to determine this target indication information.

[0259] (3) Determine a strategy (i.e., reporting policy) to characterize the constraints under which a terminal reports events outside the event report allowed area, and include at least one of the following parameters (a) to (c):

[0260] (a) Maximum number of reports (i.e., maximum number of event reports), (b) Minimum reporting time interval (i.e., minimum time interval between two adjacent event reports), (c) Trigger conditions for event reporting to specify threshold information other than the minimum time interval and maximum number of reports, one implementation method being to execute an event report only when the straight-line distance traveled reaches a certain threshold (e.g., 100 meters).

[0261] It should be explained that if the Power saving class instructs the terminal to support event reporting outside the event report allowed area, or to report events outside the event report allowed area, or to instruct "medium level or low level", in step 106, the GMLC may select a candidate strategy from the policy set based on the network selection or depending on the type of LCS client (area, periodic, or motion), subscription information related to the terminal's location obtained from step 105, and then determine which strategy should be sent to the UE based on the selected candidate strategy.

[0262] Steps 107 to 1019 are the same as steps 87 to 819 in Embodiment 1 described above, and will not be explained further here.

[0263] Embodiment 4: As shown in Figure 11, the following steps 111 to 116 are included.

[0264] Step 111: The primary information of the device changes, that is, at least one of the following changes: the device's power saving area, power saving class, area usage indication, and policy set. Step 112: The terminal sends a NAS message to the AMF carrying a third piece of information, which includes at least one modified version of the following:

[0265] (1) Power saving area, (2) Power saving class, (3) Area usage indication, (4) Policy set.

[0266] Here, the terminal may carry the third piece of information into 5GMM capability information and package this 5GMM capability information into a registration request message, thereby sending this registration request to the AMF. Alternatively, the terminal may send this registration request to the AMF by packaging the third piece of information as a new IE in a registration request message. Alternatively, the device may send third-party information to the AMF via a UE Location Privacy Setting Request message. Alternatively, the terminal may transmit third information to the AMF via an uplink non-access layer transmission (UL NAS TRASPORT) message.

[0267] Step 113: The AMF sends Nudm_ParameterProvision_Update to the UDM, which carries the third piece of information mentioned above (i.e., Power saving area, Power saving class, area usage indication, and at least one of the changes in the policy set).

[0268] Step 114: The UDM stores the received third piece of information (i.e., Power saving area, Power saving class, area usage indication, and at least one of the changes in the policy set).

[0269] Step 115: The UDM provides the GMLC with a third piece of information (i.e., Power saving area, Power saving class, area usage indication, and at least one of the changes in the policy set).

[0270] That is, in step 85 of the above-described embodiment 1, if the GMLC has subscribed to terminal information, in this step the UDM provides the GMLC with updated information such as power saving area, power saving class, area usage indication, and policy set.

[0271] Step 116: Based on the updated Power saving area, Power saving class, area usage indication, and policy set, GMLC updates at least one of the following, in combination with the target area, current event report allowed area, current strategy, and current report status (i.e., report status, e.g., number of reports to date, report duration, etc.):

[0272] (1) event report allowed area, (2) strategy (i.e., strategy that needs to be sent to the UE), (3) First instruction information.

[0273] Step 117: The GMLC sends at least one of the updated event report allowed area, strategy, or target instruction information to the terminal via the AMF or LMF.

[0274] In summary, in the embodiments of this application, the terminal may indicate whether it will use the event report allowed area in the forward or reverse direction by reporting its power saving class and area usage indication, and whether it will support conditionally performing reporting outside the event allowed area. Furthermore, the terminal may provide a set of policies, and the GMLC may select one candidate reporting policy from the set based on the location task and determine which reporting policies need to be sent to the terminal. Alternatively, the LCS client / AF may provide the reporting policies directly. If neither the terminal nor the LCS client / AF provides any, the GMLC itself determines which reporting policies need to be sent to the terminal.

[0275] Furthermore, the device may update its Power saving class, policy set, and area usage indication, save them to the UDM, and allow GMLC to update its out-of-area execution behavior based on the updated information.

[0276] In short, the embodiments of this application solve the problem of whether and how a terminal performs event reporting outside the event report allowed area by setting different power saving classes and reporting policies, and the problem of whether the area is used in reverse by indicating area usage indication.

[0277] In the event reporting method according to the embodiment of this application, the execution body may be an event reporting device. In the embodiment of this application, the event reporting device according to the embodiment of this application will be described as an example in which the event reporting device executes the event reporting method.

[0278] According to a fifth aspect, an embodiment of the present application provides an event reporting device that can be used in a terminal, and as shown in Figure 12, this event reporting device 120 is A first transmission module 1201 for transmitting first information, wherein the first information is used to indicate relevant information for which a terminal reports an event outside a first area, and the first area is an area in which the terminal is permitted to report an event. A first receiving module 1202 for receiving event reporting configuration information that matches the first information, It includes a first processing module 1203 for performing event reporting based on the aforementioned event reporting configuration information.

[0279] Selectively, the first information is, A second area for the terminal to indicate the area where it wishes to report events, Reporting instructions for indicating whether the terminal supports reporting events outside the first area, or whether the terminal reports events outside the first area, or for indicating at least one level regarding the terminal reporting events outside the first area, The system includes at least one of the following: a region usage instruction for using the first region in the forward direction or a region usage instruction for using the first region in the reverse direction.

[0280] Selectively, the event reporting configuration information is Target instruction information for indicating whether the terminal needs to report an event outside the first area, This includes at least one reporting policy that specifies at least one constraint condition under which the terminal should report an event.

[0281] Selectively, the first processing module 1203 performs event reporting based on the event reporting configuration information, specifically, If the event reporting configuration information includes the target instruction information, and the target instruction information indicates that the terminal does not need to perform event reporting outside the first area, then event reporting will not be performed outside the first area. The event reporting configuration information includes the target instruction information and the reporting policy, and the target instruction information indicates that the terminal needs to report an event outside the first area, and the event reporting is performed outside the first area based on the reporting policy. If the event reporting configuration information includes the target instruction information, and the reporting configuration information does not include the reporting policy, and the target instruction information indicates that the terminal needs to report an event outside the first area, then either the event report is not performed outside the first area, or the event report is performed outside the first area based on the realization, If the first information includes the reporting instruction, and the reporting instruction instructs not to report an event outside the first area, then not to report an event outside the first area, If the first information includes the reporting instruction, and the reporting instruction instructs to perform event reporting outside the first area, and the event reporting configuration information includes the reporting policy, then performing event reporting outside the first area based on the reporting policy, If the first information includes the reporting instruction, and the reporting instruction instructs to perform event reporting outside the first domain, and the event reporting configuration information does not include the reporting policy, then either event reporting is not performed outside the first domain, or event reporting is performed outside the first domain based on the realization, If the first information includes the reporting instruction, and the reporting instruction indicates a first level, and the event reporting configuration information does not include the reporting policy, then event reporting will not be performed outside the first area. If the first information includes the reporting instruction, and the reporting instruction indicates a second level, and the event reporting configuration information includes the reporting policy, then event reporting is performed outside the first area and within the second area based on the reporting policy. If the first information includes the reporting instruction, and the reporting instruction indicates a third level, and the event reporting configuration information includes the reporting policy, then event reporting is performed outside the first area based on the reporting policy. If the first information includes the reporting instruction, and the reporting instruction indicates the second or third level, and the event reporting configuration information does not include the reporting policy, then this is used to either not perform event reporting outside the first domain or to perform event reporting outside the first domain based on realization.

[0282] Selectively, the reporting policy is: The maximum number of event reports and The minimum time interval between two adjacent event reports, The system includes at least one of the following: the minimum time interval, the maximum number of reports, and a trigger condition for event reporting to specify threshold information other than the minimum time interval and the maximum number of reports.

[0283] Selectively, the first processing module 1203 performs event reporting based on the reporting policy, specifically, This is used to perform conditional event reporting based on at least one of the maximum number of reports, the minimum time interval, and the trigger condition.

[0284] Selectively, the first information further includes a policy set, wherein the policy set includes at least one candidate reporting policy, and the reporting policy included in the event reporting configuration information is determined based on one candidate reporting policy in the policy set.

[0285] Selectively, the apparatus, The system further includes a third transmission module for transmitting a third piece of information containing the changed information from the first piece of information when at least one piece of information contained in the first piece of information changes.

[0286] Selectively, the apparatus, A second receiving module for receiving a fourth piece of information, wherein the fourth piece of information includes at least one of the first area and the event reporting configuration information, and the fourth piece of information is determined based on the third piece of information. The system further includes a second processing module for reporting events based on the aforementioned fourth piece of information.

[0287] Selectively, the first transmitting module specifically, Used to send a target message carrying the aforementioned first information, Here, the target message is, Registration request message and, Location privacy settings request message, It includes at least one of the following: an uplink non-access layer transmission message.

[0288] The event reporting device in the embodiments of this application may be an electronic device, such as an electronic device having an operating system, or a component of an electronic device, such as an integrated circuit or a chip. This electronic device may be a terminal, and exemplary the terminal may include, but is not limited to, the types of terminals 11 listed above. The embodiments of this application are not specifically limited.

[0289] The event reporting device according to the embodiment of this application can implement each process realized by the embodiment of the method shown in Figure 4 and achieve the same technical effects, and to avoid repetition of the explanation, it will not be explained further here.

[0290] According to the sixth aspect, an embodiment of the present application provides an event reporting device that can be used in a first network-side device, and as shown in Figure 13, this event reporting device 130 is A first acquisition module 1301 for acquiring first information of a terminal, wherein the first information is used to indicate relevant information for which the terminal reports events outside a first area, and the first area is an area in which the terminal is permitted to report events. A second acquisition module 1302 for obtaining event reporting configuration information that matches the first information, It includes a second transmission module 1303 for transmitting the aforementioned report configuration information to the terminal.

[0291] Selectively, the first information is, A second area for the terminal to indicate the area where it wishes to report events, Reporting instructions for indicating whether the terminal supports reporting events outside the first area, or whether the terminal reports events outside the first area, or for indicating the level of event reporting by the terminal outside the first area, The system includes at least one of the following: a region usage instruction for using the first region in the forward direction or a region usage instruction for using the first region in the reverse direction.

[0292] Selectively, the event reporting configuration information is Target instruction information for indicating whether the terminal needs to report an event outside the first area, This includes at least one reporting policy that specifies at least one constraint condition under which the terminal should report an event.

[0293] Selectively, the reporting policy is: The maximum number of event reports and The minimum time interval between two adjacent event reports, The system includes at least one of the following: the minimum time interval, the maximum number of reports, and a trigger condition for event reporting to specify threshold information other than the minimum time interval and the maximum number of reports.

[0294] Selectively, if the event reporting configuration information includes the reporting policy, the second acquisition module 1302 specifically: When a reporting instruction indicates that the terminal supports event reporting outside the first area, or that the terminal reports events outside the first area, or indicates a second or third level, the event reporting configuration information is determined based on the location service type and subscription information related to the location of the terminal. Or, When the reporting instruction indicates that the terminal supports reporting events outside the first area, or that the terminal reports events outside the first area, or indicates the second or third level, the event reporting configuration information is determined based on the reporting policy received from the fourth network-side device. Or, If the first information further includes a policy set, and the reporting instruction indicates that the terminal supports event reporting outside the first area, or that the terminal reports an event outside the first area, or indicates the second or third level, then the method of selecting a candidate reporting policy from the policy set based on the location operation type and determining the event reporting configuration information based on the selected candidate reporting policy is used, wherein the policy set includes at least one candidate reporting policy.

[0295] Selectively, the process by which the second acquisition module 1302 receives the reporting policy transmitted by the fourth network-side device is as follows: This includes receiving a location service request, which carries a reporting policy, transmitted by the fourth network-side device.

[0296] Selectively, the second transmitting module 1303 specifically, It is used to transmit the event reporting configuration information to the terminal via the third and fifth network-side devices.

[0297] Selectively, the apparatus, The system further includes a fourth transmission module for transmitting the second information to a fourth network-side device, wherein the second information is: The first region mentioned above, A reporting instruction to indicate whether the terminal supports reporting events outside the first area, or to indicate whether the terminal reports events outside the first area, The aforementioned event reporting configuration information, A region usage instruction for instructing to use the first region in the forward direction or to use the first region in the reverse direction, A target region error cause for indicating that there is no overlapping region between a target region and a second region or that a logical error exists in the target region, wherein the target region is a region for which the terminal wishes to report an event, and the second region includes at least one of the target region error causes used to indicate a region for which the terminal wishes to report an event.

[0298] Selectively, the first acquisition module 1301 specifically, This is used to obtain the first information from the second network-side device, where the first information stored in the second network-side device is transmitted by the terminal to the second network-side device via the third network-side device.

[0299] Selectively, the apparatus, The system further includes a third acquisition module for acquiring third information provided by a second network-side device when the first network-side device subscribes to the terminal's information, wherein the third information includes altered information from the first information, and the third information stored in the second network-side device is transmitted by the terminal to the second network-side device via the third network-side device.

[0300] Selectively, the apparatus, An update module for updating a fourth piece of information, which includes at least one of the first area and the event reporting configuration information, based on the third piece of information, The system further includes a fifth transmission module for transmitting the updated fourth information to the terminal.

[0301] The event reporting device in the embodiments of this application may be an electronic device, such as an electronic device having an operating system, or a component of an electronic device, such as an integrated circuit or a chip. This electronic device may also be a network-side device. Exemplarily, the network-side device may include, but is not limited to, the types of network-side devices 12 listed above, and the embodiments of this application are not specifically limited.

[0302] The event reporting device according to the embodiment of this application can implement each process realized by the embodiment of the method shown in Figure 7 and achieve the same technical effects, and to avoid repetition of the explanation, it will not be explained further here.

[0303] According to the seventh aspect, an embodiment of the present application provides an event reporting device that can be used in a fourth network-side device, the event reporting device is The system may include a sixth transmission module for sending a reporting policy to a first network-side device that specifies at least one constraint condition under which the terminal should report an event.

[0304] Selectively, the sixth transmission module is used to transmit location service requests carrying reporting policies to the first network-side equipment.

[0305] Selectively, the apparatus, The system further includes a third receiving module for receiving second information transmitted by the first network-side device, wherein the second information is: The first region mentioned above, A reporting instruction to indicate whether the terminal supports reporting events outside the first area, or to indicate whether the terminal reports events outside the first area, The aforementioned event reporting configuration information, A region usage instruction for instructing to use the first region in the forward direction or to use the first region in the reverse direction, A target region error cause for indicating that there is no overlapping region between a target region and a second region or that a logical error exists in the target region, wherein the target region is a region for which the terminal wishes to report an event, and the second region includes at least one of the target region error causes used to indicate a region for which the terminal wishes to report an event.

[0306] The event reporting device in the embodiments of this application may be an electronic device, such as an electronic device having an operating system, or a component of an electronic device, such as an integrated circuit or a chip. This electronic device may be a network-side device, and exemplary the network-side device may include, but is not limited to, the types of network-side devices 12 listed above. The embodiments of this application are not specifically limited.

[0307] The event reporting device according to the embodiment of this application can implement each process realized by the embodiment of the third embodiment of the method described above and achieve the same technical effects, and to avoid repetition of the explanation, it will not be explained further here.

[0308] According to the eighth aspect, the embodiment of the present application further provides an event reporting device that can be used in a second network-side device, the event reporting device is A fourth acquisition module for acquiring first information from a terminal and storing the first information, It may also include a first providing module for providing the first information to the first network-side device.

[0309] Selectively, the first information is, A second area for the terminal to indicate the area where it wishes to report events, Reporting instructions for indicating whether the terminal supports reporting events outside the first area, or whether the terminal reports events outside the first area, or for indicating at least one level regarding the terminal reporting events outside the first area, The system includes at least one of the following: a region usage instruction for using the first region in the forward direction or a region usage instruction for using the first region in the reverse direction.

[0310] Selectively, the apparatus, A fourth receiving module for receiving third information transmitted by the first terminal and for storing the third information including the changed information from the first information, The system further includes a second providing module for providing the third information to the first network-side device.

[0311] The event reporting device in the embodiments of this application may be an electronic device, such as an electronic device having an operating system, or a component of an electronic device, such as an integrated circuit or a chip. This electronic device may be a network-side device, and exemplary the network-side device may include, but is not limited to, the types of network-side devices 12 listed above. The embodiments of this application are not specifically limited.

[0312] The event reporting device according to the embodiment of this application can implement each process realized by the embodiment of the fourth embodiment of the method described above and achieve the same technical effects, and to avoid repetition of the explanation, it will not be explained further here.

[0313] As shown in Figure 14, an embodiment of the present application further provides a communication device 1400 which includes a processor 1401 and a memory 1402, the memory 1402 storing a program or instruction that can be executed on the processor 1401, for example, if the communication device 1400 is a terminal, when this program or instruction is executed by the processor 1401, each step of the embodiment of the event reporting method described above can be realized and the same technical effect can be achieved. If the communication device 1400 is a network-side device, when this program or instruction is executed by the processor 1401, each step of the embodiment of the event reporting method described above can be realized and the same technical effect can be achieved, and to avoid repetition of the explanation, this will not be explained further here.

[0314] Embodiments of this application further provide a terminal comprising a processor and a communication interface, wherein the communication interface is coupled with the processor, and the processor is used to execute programs or instructions and to implement the steps in the embodiment of the method shown in Figure 4. Embodiments of this terminal correspond to embodiments of the terminal-side method described above, and each implementation process and implementation method of the embodiment of the method described above can be applied to embodiments of this terminal and achieve the same technical effects. Specifically, Figure 15 is a schematic diagram of the hardware structure realizing the terminal of the embodiment of this application.

[0315] This terminal 1500 includes, but is not limited to, some of the following components: a radio frequency unit 1501, a network module 1502, an audio output unit 1503, an input unit 1504, a sensor 1505, a display unit 1506, a user input unit 1507, an interface unit 1508, a memory 1509, and a processor 1510.

[0316] As those skilled in the art will understand, the terminal 1500 may further include a power supply (e.g., a battery) to power each component, and the power supply may be logically connected to the processor 1510 by a power management system, thereby enabling functions such as charge / discharge management and power consumption management by the power management system. The terminal structure shown in Figure 15 does not constitute a limitation on terminals, and a terminal may include more or fewer components than those shown, or combinations of some components, or different arrangements of components, which will not be described further here.

[0317] It should be understood that, in the embodiments of this application, the input unit 1504 may include a graphics processing unit (GPU) 15041 and a microphone 15042, and the graphics processor 15041 processes still images or video image data obtained by an image capture device (e.g., a camera) in video capture mode or image capture mode. The display unit 1506 may include a display panel 15061, which may be configured in the form of a liquid crystal display, organic light-emitting diodes, etc. The user input unit 1507 includes at least one of a touch panel 15071 and other input devices 15072. The touch panel 15071 is also called a touchscreen. The touch panel 15071 may include two parts: a touch detection device and a touch controller. The other input devices 15072 may include, but are not limited to, a physical keyboard, function keys (e.g., volume control buttons, switch buttons, etc.), a trackball, a mouse, or an operating lever, and will not be described further here.

[0318] In the embodiments of this application, the radio frequency unit 1501 can receive downlink data from network-side equipment and transmit it to the processor 1510 for processing, and the radio frequency unit 1501 can also transmit uplink data to network-side equipment. Generally, the radio frequency unit 1501 includes, but is not limited to, an antenna, amplifier, transceiver, coupler, low-noise amplifier, duplexer, etc.

[0319] Memory 1509 may be used to store software programs or instructions and various data. Memory 1509 may include a first storage area mainly for storing programs or instructions and a second storage area for storing data, wherein the first storage area can store an operating system, an application program or instructions necessary for at least one function (e.g., audio playback function, image playback function, etc.). Memory 1509 may include volatile memory or non-volatile memory 15. Non-volatile memory may be read-only memory (ROM), programmable read-only memory (PROM), erasable programmable read-only memory (Erasable PROM, EPROM), electrically erasable programmable read-only memory (Electrically EPROM, EEPROM), or flash memory. Volatile memory may include Random Access Memory (RAM), Static Random Access Memory (SRAM), Dynamic Random Access Memory (DRAM), Synchronous Dynamic Random Access Memory (SDRAM), Double Data Rate Synchronous Dynamic Random Access Memory (DDRSDRAM), Enhanced Synchronous Dynamic Random Access Memory (ESDRAM), Synch-link Dynamic Random Access Memory (SLDRAM), and Direct Rambus Random Access Memory (DRRAM). Memory 1509 in the embodiments of this application includes, but is not limited to, these and any other suitable types of memory.

[0320] The processor 1510 may include one or more processing units. Selectively, the processor 1510 integrates an application processor and a modem processor, where the application processor primarily handles operations related to the operating system, user interface, and application programs, and the modem processor primarily handles wireless communication signals, such as a baseband processor. To be clear, the above-mentioned modem processor does not have to be integrated into the processor 1510.

[0321] The radio frequency unit 1501 is used by the terminal to transmit first information, where the first information is used to indicate relevant information for which the terminal reports an event outside a first area, and the first area is an area in which the terminal is permitted to report an event. The radio frequency unit 1501 is further used to receive event reporting configuration information that matches the first information, The processor 1510 is used to perform event reporting based on the event reporting configuration information.

[0322] Selectively, the first information is, A second area for the terminal to indicate the area where it wishes to report events, Reporting instructions for indicating whether the terminal supports reporting events outside the first area, or whether the terminal reports events outside the first area, or for indicating at least one level regarding the terminal reporting events outside the first area, The system includes at least one of the following: a region usage instruction for using the first region in the forward direction or a region usage instruction for using the first region in the reverse direction.

[0323] Selectively, the event reporting configuration information is Target instruction information for indicating whether the terminal needs to report an event outside the first area, This includes at least one reporting policy that specifies at least one constraint condition under which the terminal should report an event.

[0324] Selectively, the processor 1510 may perform event reporting based on the event reporting configuration information. If the event reporting configuration information includes the target instruction information, and the target instruction information indicates that the terminal does not need to perform event reporting outside the first area, then event reporting will not be performed outside the first area. The event reporting configuration information includes the target instruction information and the reporting policy, and the target instruction information indicates that the terminal needs to report an event outside the first area, and the event reporting is performed outside the first area based on the reporting policy. If the event reporting configuration information includes the target instruction information, and the reporting configuration information does not include the reporting policy, and the target instruction information indicates that the terminal needs to report an event outside the first area, then either the event report is not performed outside the first area, or the event report is performed outside the first area based on the realization, If the first information includes the reporting instruction, and the reporting instruction instructs not to report an event outside the first area, then not to report an event outside the first area, If the first information includes the reporting instruction, and the reporting instruction instructs to perform event reporting outside the first area, and the event reporting configuration information includes the reporting policy, then performing event reporting outside the first area based on the reporting policy, If the first information includes the reporting instruction, and the reporting instruction instructs to perform event reporting outside the first domain, and the event reporting configuration information does not include the reporting policy, then either event reporting is not performed outside the first domain, or event reporting is performed outside the first domain based on the realization, If the first information includes the reporting instruction, and the reporting instruction indicates a first level, and the event reporting configuration information does not include the reporting policy, then event reporting will not be performed outside the first area. If the first information includes the reporting instruction, and the reporting instruction indicates a second level, and the event reporting configuration information includes the reporting policy, then event reporting is performed outside the first area and within the second area based on the reporting policy. If the first information includes the reporting instruction, and the reporting instruction indicates a third level, and the event reporting configuration information includes the reporting policy, then event reporting is performed outside the first area based on the reporting policy. If the first information includes the reporting instruction, and the reporting instruction indicates the second or third level, and the event reporting configuration information does not include the reporting policy, then the event reporting outside the first domain is to be either not to perform event reporting or to perform event reporting outside the first domain based on the realization.

[0325] Selectively, the reporting policy is: The maximum number of event reports and The minimum time interval between two adjacent event reports, The system includes at least one of the following: the minimum time interval, the maximum number of reports, and a trigger condition for event reporting to specify threshold information other than the minimum time interval and the maximum number of reports.

[0326] Selectively, the processor 1510 may report events based on the aforementioned reporting policy. This includes performing conditional event reporting based on at least one of the maximum number of reports, the minimum time interval, and the trigger condition.

[0327] Selectively, the first information further includes a policy set, wherein the policy set includes at least one candidate reporting policy, and the reporting policy included in the event reporting configuration information is determined based on one candidate reporting policy in the policy set.

[0328] Selectively, the radio frequency unit 1501 further, This is used to transmit a third piece of information that includes the changed information from the first piece of information when at least one piece of information included in the first piece of information changes.

[0329] Selectively, the radio frequency unit 1501 further, Used to receive a fourth piece of information, wherein the fourth piece of information includes at least one of the first area and the event reporting configuration information, and the fourth piece of information is determined based on the third piece of information. The processor 1510 is further used to report events based on the fourth piece of information.

[0330] Selectively, the radio frequency unit 1501 transmits the first information. This includes sending a target message in which the aforementioned first information is carried, Here, the target message is, Registration request message and, Location privacy settings request message, It includes at least one of the following: an uplink non-access layer transmission message.

[0331] To ensure understanding, the implementation process of each implementation method mentioned in this embodiment can be referenced to the relevant description of the implementation example event reporting method, and the same or applicable technical effects can be achieved. To avoid repetition of the explanation, it will not be described further here.

[0332] Embodiments of this application further provide a network-side device comprising a processor and a communication interface, wherein the communication interface is coupled with the processor, and the processor is used to execute programs or instructions and to implement steps of the embodiments of the method described in the second, third, or fourth embodiment described above. Embodiments of this network-side device correspond to embodiments of the network-side device method described above, and each implementation process and implementation method of the embodiments of the method described above can be applied to embodiments of this network-side device and achieve the same technical effects.

[0333] Specifically, embodiments of this application further provide network-side equipment. As shown in Figure 16, this network-side equipment 1600 includes a processor 1601, a network interface 1602, and memory 1603. Here, the network interface 1602 is, for example, a common public radio interface (CPRI).

[0334] Specifically, the network-side device 1600 of the embodiment of the present invention further includes instructions or programs stored in memory 1603 and operable on processor 1601, the processor 1601 calling instructions or programs in memory 1603, performing the method described in the second, third, or fourth embodiment described above, and achieving the same technical effect, which will not be described further here in order to avoid repetition of the description.

[0335] Embodiments of this application further provide a readable storage medium in which a program or instruction is stored, and when this program or instruction is executed by a processor, each process of the embodiment of the event reporting method described above can be realized and the same technical effects can be achieved, and to avoid repetition of the description, no further explanation is provided here.

[0336] Here, the processor is the processor in the terminal described in the above embodiment. The readable storage medium includes computer-readable storage media such as computer read-only memory ROM, random access memory RAM, magnetic disk, or optical disk. In some examples, the readable storage medium may be a non-temporarily readable storage medium.

[0337] Embodiments of this application further provide a chip comprising a processor and a communication interface, the communication interface being coupled with the processor, the processor running a program or instructions and used to implement each process of the embodiment of the event reporting method described above and achieving the same technical effects, which are not described further here to avoid repetition of the description.

[0338] It should be understood that the chips referred to in the embodiments of this application may also be called system-level chips, system chips, chip systems, or system-on-a-chip, etc.

[0339] Embodiments of this application further provide a computer program / program product which is stored in a storage medium and executed by at least one processor to realize each process of the embodiment of the event reporting method described above and achieve the same technical effects, which will not be described further here in order to avoid repetition of the description.

[0340] Embodiments of the present application further provide a wireless communication system comprising a terminal and a first network-side device, wherein the terminal may be used to perform the steps of the event reporting method described in the first embodiment above, and the first network-side device may be used to perform the steps of the event reporting method described in the second embodiment above, and further, the wireless communication system further comprises a fourth network-side device and a second network-side device, wherein the fourth network-side device may be used to perform the steps of the event reporting method described in the third embodiment above, and the second network-side device may be used to perform the steps of the event reporting method described in the fourth embodiment above.

[0341] It should be noted that, in this specification, the terms “include,” “incorporate,” or any other variation thereof are intended to cover the non-exclusive “include,” thereby including not only those elements but also other elements not explicitly listed, or elements specific to such process, method, article, or apparatus. Unless otherwise specified, an element limited by the phrase “includes one of…” is not excluded from the existence of other identical elements in a process, method, article, or apparatus that includes that element. It should also be noted that the scope of methods and apparatus in embodiments of this application is not limited to performing functions in the order illustrated or discussed, but may include performing functions in a manner that is essentially simultaneous or in reverse order based on the functions involved, and methods described in a different procedure than those described, for example, may be performed, and various steps may be added, omitted, or combined. Furthermore, features described by reference to some examples may be combined with other examples.

[0342] As will be clearly apparent to those skilled in the art from the above description of the embodiments, the methods of the above embodiments may be implemented by combining a computer software product with a necessary general-purpose hardware platform, or of course, by hardware alone. This computer software product is stored in a storage medium (e.g., ROM, RAM, magnetic disk, optical disk, etc.) and includes some instructions for causing a terminal or network-side device to perform the methods of each embodiment of this application.

[0343] The above describes embodiments of this application, accompanied by drawings; however, this application is not limited to the specific embodiments described above. The specific embodiments described above are merely illustrative and not restrictive. Those skilled in the art will know that, by the suggestion of this application, many forms of embodiments are possible, as long as they do not deviate from the spirit and claims of this application, and all of these embodiments fall within the scope of protection of this application.

Claims

1. Event reporting method, The terminal transmits first information, the first information is used to indicate relevant information for which the terminal reports an event outside of a first area, and the first area is an area in which the terminal is permitted to report an event. The terminal receives event reporting configuration information that matches the first information, An event reporting method, comprising the terminal performing an event report based on the event reporting configuration information.

2. The first piece of information mentioned above is, A second area for the terminal to indicate the area where it wishes to report events, Reporting instructions for indicating whether the terminal supports reporting events outside the first area, or whether the terminal reports events outside the first area, or for indicating at least one level regarding the terminal reporting events outside the first area, The method according to claim 1, comprising at least one of a region usage instruction for instructing to use the first region in a forward direction or to use the first region in a reverse direction.

3. The method according to claim 2, wherein the reporting instruction is a global mutual exclusion setting for the first area.

4. The method according to any one of claims 1 to 3, wherein the first region is determined based on the second region.

5. The aforementioned event reporting configuration information is: Target instruction information for indicating whether the terminal needs to report an event outside the first area, The method according to any one of claims 1 to 4, comprising at least one of a reporting policy for specifying at least one constraint condition under which a terminal reports an event.

6. The terminal performs event reporting based on the event reporting configuration information, If the event reporting configuration information includes the target instruction information, and the target instruction information indicates that the terminal does not need to report an event outside the first area, the terminal shall not report an event outside the first area. The event reporting configuration information includes the target instruction information and the reporting policy, and the target instruction information indicates that the terminal needs to report an event outside the first area, and the terminal reports an event outside the first area based on the reporting policy, If the event reporting configuration information includes the target instruction information, and the reporting configuration information does not include the reporting policy, and the target instruction information indicates that the terminal needs to report an event outside the first area, then the terminal does not report an event outside the first area, or the terminal reports an event outside the first area based on the realization, If the first information includes the reporting instruction, and the reporting instruction instructs not to report an event outside the first area, the terminal shall not report an event outside the first area. If the first information includes the reporting instruction, and the reporting instruction instructs to perform event reporting outside the first area, and the event reporting configuration information includes the reporting policy, then the terminal performs event reporting outside the first area based on the reporting policy, If the first information includes the reporting instruction, and the reporting instruction instructs to perform event reporting outside the first area, and the event reporting configuration information does not include the reporting policy, then the terminal does not perform event reporting outside the first area, or the terminal performs event reporting outside the first area based on the realization, If the first information includes the reporting instruction, and the reporting instruction indicates a first level, and the event reporting configuration information does not include the reporting policy, the terminal will not report an event outside the first area. When the first information includes the reporting instruction, and the reporting instruction indicates a second level, and the event reporting configuration information includes the reporting policy, the terminal performs event reporting based on the reporting policy outside the first area and within the second area, wherein the second area is used to indicate the area in which the terminal wishes to report events. When the first information includes the reporting instruction, and the reporting instruction indicates a third level, and the event reporting configuration information includes the reporting policy, the terminal performs event reporting outside the first area based on the reporting policy, The method of claim 5, wherein the first information includes the reporting instruction, and the reporting instruction indicates the second level or the third level, and the event reporting configuration information does not include the reporting policy, the terminal does not report an event outside the first area, or the terminal reports an event outside the first area based on an event.

7. The aforementioned reporting policy is: The maximum number of event reports and The minimum time interval between two adjacent event reports, The method according to claim 5 or 6, further comprising at least one of the following: the minimum time interval and an event reporting trigger condition for specifying threshold information other than the maximum number of reports.

8. The terminal performs event reporting based on the reporting policy, The method according to claim 7, wherein the terminal performs conditional event reporting based on at least one of the maximum number of reports, the minimum time interval, and the trigger condition.

9. The method according to any one of claims 5 to 8, wherein the first information further comprises a policy set, wherein the policy set comprises at least one candidate reporting policy, and the reporting policy included in the event reporting configuration information is determined based on one candidate reporting policy in the policy set.

10. The aforementioned method, The method according to any one of claims 1 to 9, further comprising the terminal transmitting a third piece of information including the changed information from the first piece of information when at least one piece of information included in the first piece of information changes.

11. The aforementioned method, The terminal receives a fourth piece of information, wherein the fourth piece of information includes at least one of the first area and the event reporting configuration information, and the fourth piece of information is determined based on the third piece of information. The method according to claim 10, further comprising the terminal reporting an event based on the fourth piece of information.

12. The terminal transmits the first information. The terminal transmits a target message in which the first information is carried, Here, the target message is, Registration request message and, Location privacy settings request message, The method according to any one of claims 1 to 11, comprising at least one of the following: an uplink non-access layer transmission message.

13. Event reporting method, The first network-side device acquires first information of the terminal, the first information is used to indicate relevant information for which the terminal reports events outside of the first area, and the first area is an area in which the terminal is permitted to report events. The first network-side device acquires event reporting configuration information that matches the first information, An event reporting method comprising the first network-side device transmitting the reporting configuration information to the terminal.

14. The first piece of information mentioned above is, A second area for the terminal to indicate the area where it wishes to report events, Reporting instructions for indicating whether the terminal supports reporting events outside the first area, or whether the terminal reports events outside the first area, or for indicating the level of event reporting by the terminal outside the first area, The method according to claim 13, comprising at least one of a region usage instruction for instructing to use the first region in a forward direction or to use the first region in a reverse direction.

15. The method according to claim 14, wherein the reporting instruction is a global mutual exclusion setting for the first area.

16. The method according to any one of claims 13 to 15, wherein the first region is determined based on the second region.

17. The aforementioned event reporting configuration information is: Target instruction information for indicating whether the terminal needs to report an event outside the first area, The method according to any one of claims 13 to 16, further comprising at least one of a reporting policy for specifying at least one constraint condition under which a terminal should report an event.

18. The aforementioned reporting policy is: The maximum number of event reports and The minimum time interval between two adjacent event reports, The method according to claim 17, further comprising at least one of the following: the minimum time interval and an event reporting trigger condition for specifying threshold information other than the maximum number of reports.

19. When the event reporting configuration information includes the reporting policy, the first network-side device obtains event reporting configuration information that matches the first information. When a reporting instruction indicates that the terminal supports event reporting outside the first area, or that the terminal reports events outside the first area, or indicates a second or third level, the first network-side device determines the event reporting configuration information based on the location service type and subscription information related to the terminal's location. Or, When the reporting instruction indicates that the terminal supports reporting events outside the first area, or that the terminal reports events outside the first area, or indicates the second or third level, the first network-side device determines the event reporting configuration information based on the reporting policy received from the fourth network-side device. Or, The method according to claim 17 or 18, wherein the first information further includes a policy set, and the reporting instruction indicates that the terminal supports event reporting outside the first area, or that the terminal reports an event outside the first area, or that the second or third level is indicated, the first network-side device selects a candidate reporting policy from the policy set based on the location work type, and determines the event reporting configuration information based on the selected candidate reporting policy, wherein the policy set includes at least one candidate reporting policy.

20. The process by which the first network-side device receives the reporting policy transmitted by the fourth network-side device is as follows: The method according to claim 19, wherein the first network-side device receives a location service request, which carries a reporting policy, transmitted by the fourth network-side device.

21. The first network-side device transmits the event reporting configuration information to the terminal. The method according to any one of claims 13 to 20, wherein the first network-side device transmits the event reporting configuration information to the terminal via the third network-side device and the fifth network-side device.

22. The aforementioned method, The first network-side device further includes transmitting the second information to the fourth network-side device, wherein the second information is: The first region mentioned above, A reporting instruction to indicate whether the terminal supports reporting events outside the first area, or to indicate whether the terminal reports events outside the first area, The aforementioned event reporting configuration information, A region usage instruction for instructing to use the first region in the forward direction or to use the first region in the reverse direction, The method according to any one of claims 13 to 21, comprising at least one of a target region error cause for indicating that there is no overlapping region between a target region and a second region or that a logical error exists in the target region, wherein the target region is a region for which the terminal wishes to report an event, and the second region is a target region error cause used to indicate a region for which the terminal wishes to report an event.

23. The acquisition of the first information of the terminal by the first network-side device is: The method according to any one of claims 13 to 22, comprising the first network-side device obtaining the first information from the second network-side device, wherein the first information stored in the second network-side device is transmitted by the terminal to the second network-side device via the third network-side device.

24. The aforementioned method, The method according to any one of claims 13 to 23, further comprising the first network-side device obtaining third information provided by a second network-side device when the first network-side device subscribes to the terminal's information, wherein the third information includes altered information from the first information, and the third information stored in the second network-side device is transmitted by the terminal to the second network-side device via the third network-side device.

25. The aforementioned method, The first network-side device updates a fourth piece of information, which includes at least one of the first area and the event reporting configuration information, based on the third piece of information. The method according to claim 24, further comprising the first network-side device transmitting the updated fourth information to the terminal.

26. An event reporting device, A first transmission module for transmitting first information, wherein the first information is used to indicate relevant information for which a terminal reports an event outside a first area, and the first area is an area in which the terminal is permitted to report an event. A first receiving module for receiving event reporting configuration information that matches the first information, An event reporting device, comprising a first processing module for performing event reporting based on the aforementioned event reporting configuration information.

27. The first piece of information mentioned above is, A second area for the terminal to indicate the area where it wishes to report events, Reporting instructions for indicating whether the terminal supports reporting events outside the first area, or whether the terminal reports events outside the first area, or for indicating at least one level regarding the terminal reporting events outside the first area, The apparatus according to claim 26, comprising at least one of a region usage instruction for instructing the first region to be used in a forward direction or in a reverse direction.

28. The apparatus according to claim 27, wherein the reporting instruction is a global mutual exclusion setting for the first region.

29. The apparatus according to any one of claims 26 to 28, wherein the first region is determined based on the second region.

30. The aforementioned event reporting configuration information is: Target instruction information for indicating whether the terminal needs to report an event outside the first area, The apparatus according to any one of claims 26 to 29, comprising at least one of a reporting policy for specifying at least one constraint condition under which a terminal reports an event.

31. An event reporting device, A first acquisition module for acquiring first information of a terminal, wherein the first information is used to indicate relevant information for which the terminal reports events outside a first area, and the first area is an area in which the terminal is permitted to report events; A second acquisition module for obtaining event reporting configuration information that matches the first piece of information, An event reporting device, comprising a second transmission module for transmitting the aforementioned reporting configuration information to the terminal.

32. The first piece of information mentioned above is, A second area for the terminal to indicate the area where it wishes to report events, Reporting instructions for indicating whether the terminal supports reporting events outside the first area, or whether the terminal reports events outside the first area, or for indicating at least one level regarding the terminal reporting events outside the first area, The apparatus according to claim 31, comprising at least one of a region usage instruction for instructing the first region to be used in a forward direction or in a reverse direction.

33. The apparatus according to claim 32, wherein the reporting instruction is a global mutual exclusion setting for the first region.

34. The apparatus according to any one of claims 31 to 33, wherein the first region is determined based on the second region.

35. The aforementioned event reporting configuration information is: Target instruction information for indicating whether the terminal needs to report an event outside the first area, The apparatus according to any one of claims 31 to 34, comprising at least one of a reporting policy for specifying at least one constraint condition under which a terminal reports an event.

36. A terminal comprising a processor and memory, wherein the memory stores a program or instruction that can be executed on the processor, and when the program or instruction is executed by the processor, the terminal realizes a step of the event reporting method described in any one of claims 1 to 12.

37. A network-side device, the network-side device comprising a processor and memory, wherein the memory stores a program or instruction that can be executed on the processor, and when the program or instruction is executed by the processor, the network-side device realizes a step of the event reporting method described in any one of claims 13 to 25.

38. A readable storage medium wherein a program or instruction is stored in the readable storage medium, and when the program or instruction is executed by a processor, the event reporting method described in any one of claims 1 to 12 is realized, or the steps of the event reporting method described in any one of claims 13 to 25 are realized.

Images