[go: up one dir, main page]
More Web Proxy on the site http://driver.im/

WO2024208363A1 - 事件上报方法、装置、设备及存储介质 - Google Patents

事件上报方法、装置、设备及存储介质 Download PDF

Info

Publication number
WO2024208363A1
WO2024208363A1 PCT/CN2024/086448 CN2024086448W WO2024208363A1 WO 2024208363 A1 WO2024208363 A1 WO 2024208363A1 CN 2024086448 W CN2024086448 W CN 2024086448W WO 2024208363 A1 WO2024208363 A1 WO 2024208363A1
Authority
WO
WIPO (PCT)
Prior art keywords
area
event
reporting
terminal
information
Prior art date
Application number
PCT/CN2024/086448
Other languages
English (en)
French (fr)
Inventor
于航
张迪
Original Assignee
维沃移动通信有限公司
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 维沃移动通信有限公司 filed Critical 维沃移动通信有限公司
Publication of WO2024208363A1 publication Critical patent/WO2024208363A1/zh

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
    • H04W4/02—Services making use of location information
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
    • H04W4/02—Services making use of location information
    • H04W4/029—Location-based management or tracking services

Definitions

  • the present application belongs to the field of communication technology, and specifically relates to an event reporting method, device, equipment and storage medium.
  • the third-party application (LCS client) would request the network side to obtain the UE's event report (event report) when a certain event requirement (including periodic, area-based, and motion-based) was met.
  • a certain event requirement including periodic, area-based, and motion-based
  • R18 introduces event report allowed area, that is, UE can report an area to indicate that UE only reports its position in this area (this area is called Power saving area).
  • GMLC will determine event report allowed area based on Power saving area, generally converting fine-grained areas into coarse-grained areas, such as converting a rectangular area (i.e., an area composed of coordinate points) into a Tracking Area (TA) or a list of cells. Therefore, the current usage of event report allowed area is: only when UE is in event report allowed area, UE will execute event report.
  • the embodiments of the present application provide an event reporting method, apparatus, device and storage medium to provide a method for a terminal to perform event reporting outside the event report allowed area.
  • a method for reporting an event comprising:
  • the terminal sends first information, wherein the first information is used to indicate relevant information that the terminal reports an event outside a first area, and the first area is an area where the terminal is allowed to report an event;
  • the terminal receives event reporting configuration information matching the first information
  • the terminal reports the event according to the event reporting configuration information.
  • a method for reporting an event comprising:
  • the first network side device acquires first information of the terminal, wherein the first information is used to indicate relevant information of the terminal reporting an event outside a first area, and the first area is an area where the terminal is allowed to report an event;
  • the first network side device obtains event reporting configuration information matching the first information
  • the first network side device sends the reporting configuration information to the terminal.
  • an event reporting device comprising:
  • a first sending module configured to send first information, wherein the first information is used to indicate relevant information of an event reporting by a terminal outside a first area, where the first area is an area where the terminal is allowed to report an event;
  • a first receiving module used to receive event reporting configuration information matching the first information
  • the first processing module is used to report an event according to the event reporting configuration information.
  • an event reporting device including:
  • a first acquisition module is used to acquire first information of a terminal, wherein the first information is used to indicate the terminal Related information for event reporting outside a first area, where the first area is an area where the terminal is allowed to report events;
  • a second acquisition module used to acquire event reporting configuration information matching the first information
  • the second sending module is used to send the reporting configuration information to the terminal.
  • a terminal comprising a processor and a memory, wherein the memory stores 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 described in the first aspect are implemented.
  • a network side device which includes a processor and a memory, wherein the memory stores programs or instructions that can be run on the processor, and when the program or instructions are executed by the processor, the steps of the method described in the second aspect are implemented.
  • a terminal including a processor and a communication interface, wherein the communication interface is used to send first information, wherein the first information is used to indicate relevant information that the terminal reports an event outside a first area, and the first area is an area where the terminal is allowed to report an event;
  • the communication interface is also used to receive event reporting configuration information matching the first information
  • the processor is used for reporting an event according to the event reporting configuration information.
  • a network side device including a processor and a communication interface, wherein the communication interface is used to obtain first information of a terminal, wherein the first information is used to indicate relevant information for the terminal to report an event outside a first area, and the first area is an area where the terminal is allowed to report an event;
  • the processor is used to obtain event reporting configuration information matching the first information
  • the communication interface is also used to send the reporting configuration information to the terminal.
  • a readable storage medium on which a program or instruction is stored.
  • the program or instruction is executed by a processor, the steps of the method described in the first aspect are implemented, or the steps of the method described in the second aspect are implemented.
  • a wireless communication system including: a terminal and a network side device, wherein the terminal can be used to execute the steps of the method described in the first aspect, and the network side device can be used to execute the steps of the method described in the second aspect.
  • a chip comprising a processor and a communication interface, wherein the communication interface is coupled to the processor, and the processor is used to run a program or instruction to implement the method described in the first aspect, or to implement the method described in the second aspect.
  • a computer program/program product is provided, wherein the computer program/program product is stored in a storage medium, and the program/program product is executed by at least one processor to implement the steps of the event reporting method as described in the first aspect or the second aspect.
  • an embodiment of the present application provides an event reporting device, which is used to execute the steps of the event reporting method described in the first aspect or the second aspect.
  • the terminal can send the first information to the first network side device, so that the first network side device obtains the event reporting configuration information matching the first information, and then sends the event reporting configuration information to the terminal, so that the terminal can report the event according to the event reporting configuration information, wherein the first information is used to indicate the relevant information of the terminal reporting the event outside the first area, and the first area (i.e., event report allowed area) is the area where the terminal is allowed to report the event. It can be seen that in an embodiment of the present application, the terminal can send the first network side device to the first network side device.
  • the first network side device reports the relevant information (i.e., the first information) of the event reporting outside the event report allowed area, so that the first network side device can configure appropriate event reporting configuration information for the terminal according to the relevant information, thereby enabling the terminal to implement more appropriate event reporting outside the event report allowed area. Therefore, an embodiment of the present application provides a method for a terminal to perform event reporting outside the event report allowed area.
  • FIG1 is a block diagram of a wireless communication system to which an embodiment of the present application can be applied;
  • FIG2 is a schematic diagram of an architecture for implementing location services
  • FIG3 is a flow chart of a Mobile Terminated Location Request (MT-LR) process
  • FIG4 is a flow chart of an event reporting method in an embodiment of the present application.
  • FIG5 is a schematic diagram of determining the event report allowed area based on power saving in an embodiment of the present application
  • FIG6 is a schematic diagram of “forward use” and “reverse use” in an embodiment of the present application.
  • FIG7 is a flow chart of another event reporting method in an embodiment of the present application.
  • FIG8 is a flowchart of a specific implementation method 1 of an event reporting method according to an embodiment of the present application.
  • FIG. 10 is a flowchart of a specific implementation method of the event reporting method of the embodiment of the present application.
  • FIG. 11 is a flowchart of a specific implementation method 4 of the event reporting method of the embodiment of the present application.
  • FIG12 is a structural block diagram of an event reporting device in an embodiment of the present application.
  • FIG13 is a structural block diagram of another event reporting device in an embodiment of the present application.
  • FIG14 is a block diagram of a communication device in an embodiment of the present application.
  • FIG15 is a block diagram of a terminal in an embodiment of the present application.
  • FIG16 is a structural block diagram of a network-side device in an embodiment of the present application.
  • first, second, etc. of the present application are used to distinguish similar objects, and are not used to describe a specific order or sequence. It should be understood that the terms used in this way are interchangeable where appropriate, so that the embodiments of the present application can be implemented in an order other than those illustrated or described herein, and the objects distinguished by “first” and “second” are generally of one type, and the number of objects is not limited, for example, the first object can be one or more.
  • “or” in the present application represents at least one of the connected objects.
  • “A or B” covers three schemes, namely, Scheme 1: including A but not including B; Scheme 2: including B but not including A; Scheme 3: including both A and B.
  • the character "/" generally indicates that the objects associated with each other are in an "or” relationship.
  • indication in this application can be either a direct indication (or explicit indication) or an indirect indication (or implicit indication).
  • a direct indication can be understood as the sender explicitly informing the receiver of specific information, operations to be performed, or request results in the sent indication;
  • an indirect indication can be understood as the receiver determining the corresponding information according to the indication sent by the sender, or making a judgment and determining the operations to be performed or request results according to the judgment result.
  • LTE-Advanced Long Term Evolution
  • LTE-A LTE/LTE evolution
  • CDMA Code Division Multiple Access
  • TDMA Time Division Multiple Access
  • FDMA Frequency Division Multiple Access
  • OFDMA Orthogonal Frequency Division Multiple Access
  • SC-FDMA Single-carrier Frequency-Division Multiple Access
  • NR New Radio
  • 6G 6th Generation
  • FIG1 shows a block diagram of a wireless communication system applicable to an embodiment of the present application.
  • the wireless communication system includes a terminal 11 and a network side device 12 .
  • the terminal 11 can be a mobile phone, a tablet computer (Tablet Personal Computer), a laptop computer (Laptop Computer), a notebook computer, a personal digital assistant (Personal Digital Assistant, PDA), a handheld computer, a netbook, an ultra-mobile personal computer (Ultra-mobile Personal Computer, UMPC), a mobile Internet device (Mobile Internet Device, MID), an augmented reality (Augmented Reality, AR), a virtual reality (Virtual Reality, VR) device, a robot, a wearable device (Wearable Device), a flight vehicle (flight vehicle), a vehicle user equipment (VUE), a shipborne equipment, a pedestrian terminal (Pedestrian User Equipment, PUE), a smart home (home appliances with wireless communication functions, such as refrigerators, televisions, washing machines or furniture, etc.), a game console, a personal computer (
  • Wearable devices include: smart watches, smart bracelets, smart headphones, smart glasses, smart jewelry (smart bracelets, smart bracelets, smart rings, smart necklaces, smart anklets, smart anklets, etc.), smart wristbands, smart clothing, etc.
  • the vehicle-mounted device can also be called a vehicle-mounted terminal, a vehicle-mounted controller, a vehicle-mounted module, a vehicle-mounted component, a vehicle-mounted chip or a vehicle-mounted unit, etc. It should be noted that the specific type of the terminal 11 is not limited in the embodiment of the present application.
  • the network side device 12 may include an access network device or a core network device, wherein the access network device may also be called a radio access network (Radio Access Network, RAN) device, a radio access network function or a radio access network unit.
  • the access network device may include a base station, a wireless local area network (Wireless Local Area Network, WLAN) access point (Access Point, AS) or a wireless fidelity (Wireless Fidelity, WiFi) node, etc.
  • WLAN wireless Local Area Network
  • AS Access Point
  • WiFi wireless Fidelity
  • the base station can be called Node B (Node B, NB), Evolved Node B (Evolved Node B, eNB), the next generation Node B (the next generation Node B, gNB), New Radio Node B (New Radio Node B, NR Node B), access point, Relay Base Station (Relay Base Station, RBS), Serving Base Station (Serving Base Station, SBS), Base Transceiver Station (Base Transceiver Station, BTS), radio base station, radio transceiver, base
  • the base station is not limited to specific technical terms as long as the same technical effect is achieved. It should be noted that in the embodiments of the present application, only the base station in the NR system is taken as an example for introduction, and the specific type of the base station is not limited.
  • the core network device may include the core network device may include but is not limited to at least one of the following: a core network node, a core network function, a mobility management entity (Mobility Management Entity, MME), an access mobility management function (Access and Mobility Management Function, AMF), a session management function (Session Management Function, SMF), a user plane function (User Plane Function, UPF), a policy control function (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 Function (AF), etc.
  • MME mobility management entity
  • AMF Access and Mobility Management Function
  • SMF Session Management Function
  • PCF Policy Control Function
  • PCF Policy and Charging Rules Function
  • core network device in the NR system is taken as an example for introduction, and the specific type of the core network device is not limited. But not limited to at least one of the following: core network node, core network function, mobility management entity (Mobility Management Entity, MME), access mobility management function (Access and Mobility Management Function, AMF), session management function (Session Management Function, SMF), user plane function (User Plane Function, UPF), policy control function (Policy Control Function, PCF), policy and charging rules function unit (Policy and Charging Rules Function, PCRF), edge application service discovery function (Edge Application Server Discovery Function, EASDF), unified data management (Unified Data Management, UDM), unified data storage (Unified Data Repository, UDR), home user server (Home Subscriber Server, HSS), centralized network configuration (CNC), network storage function (Network Repository Function, NRF), network exposure function (Network Exposure Function, NEF), local NEF (Local NEF, or L
  • MME mobility management entity
  • AMF Access Mobility Management Function
  • the positioning service is implemented and provided by network elements such as AMF and Location Management Function (LMF) in the core network.
  • LCS messages are exchanged between the UE and the LCS entity (client) or AF.
  • a typical process is the MT-LR process.
  • the MT-LR process is initiated by an external third-party application (LCS client) or by AF through the NEF network element, and finally obtains the UE's location information through the Gateway Mobile Location Center (GMLC), AMF, LMF and other network elements.
  • LCS client third-party application
  • GMLC Gateway Mobile Location Center
  • AMF Access Management Function
  • LMF Layer Management Function
  • N1, N2, N51, N33, N52, N8, NL1, NL2, NL5, NL6, NL7, and Le in Figure 2 represent different interfaces respectively.
  • the method specifically includes the following steps 31 to 331 :
  • Step 31a LCS client c sends an LCS Service Request message to the Home Gateway Mobile Location Centre (H-GMLC);
  • H-GMLC Home Gateway Mobile Location Centre
  • Step 31b-1 AF sends an event exposure subscription request message (Nnef_EventExposure_Subscribe Request) of the NEF network element to NEF;
  • Step 31b-2 NEF sends a GMLC network element location provision request message (Ngmlc_Location_ProvideLocation Request) to H-GMLC;
  • the LCS client or AF accesses the H-GMLC through the NEF and initiates a service request to the LCS system, requesting a periodic or triggered location report.
  • the LCS client carries the category of the periodic or triggered location report and related parameters. The category includes UE availability, area, periodic location, and motion.
  • the LCS service request message carries: detailed information about the geographic area, whether to report when the UE enters, stays, or leaves the area, the duration of the report, the interval between two successful reports, the maximum sampling interval, whether the location estimate is carried in the report message, and whether one or more reports are required. If the target area is represented as a local location coordinate or a geographic name, the H-GMLC converts the target area into a geographic area expressed as a shape.
  • Step 32 H-GMLC exchanges the subscription data management request message (Nudm_SDM_Get) of the UDM network element with UDM, that is, H-GMLC confirms the privacy check of the UE and obtains the change of the UE privacy information in time by obtaining the update of the UE privacy information from UDM.
  • Nudm_SDM_Get subscription data management request message
  • Step 33 H-GMLC and UDM exchange the UE context management request message (Nudm_UECM_Get) of the UDM network element, that is, H-GMLC obtains the address of AMF from UDM.
  • Step 34 H-GMLC sends a location request (Ngmlc_Location_ProvideLocation Request) to the Visited Gateway Mobile Location Centre (V-GMLC). If the UE is under H-GMLC, this step can be skipped.
  • Step 35 H-GMLC or V-GMLC initiates a location request to the serving AMF (e.g. V-GMLC sends a Namf_Location_ProvidePositioningInfo Request message to AMF). For area-based event reporting, the target geographic area is mapped to a list of cell or TA identifiers.
  • Step 36 AMF sends the AMF network element location providing response message (Namf_Location_ProvidePositioningInfo Response) to 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 LCS Service Response to LCS Client
  • Step 38b-1 H-GMLC sends a GMLC network element location provision response message (Ngmlc_Location_ProvideLocation Response) to NEF;
  • Step 38b-2 NEF sends an event exposure subscription response message (Nnef_EventExposure_Subscribe Response) of the NEF network element to AF;
  • Step 39 AMF waits for the UE to be accessible, that is, if the UE is not currently reachable, for example, using extended discontinuous reception parameters (Extended-Discontinuous Reception, eDRX), AMF will wait for the UE to be reachable.
  • extended discontinuous reception parameters Extended-Discontinuous Reception, eDRX
  • Step 310 AMF triggers a network triggered service request (Network Triggered Service Request), that is, until the UE is reachable. If the UE is in the idle state (connection management-IDLE, CM-IDLE), the AMF starts the network triggered location request process to establish a signaling connection between the UE and the network side.
  • Network Triggered Service Request Network Triggered Service Request
  • Step 311 AMF sends a NAS Location Notification Invoke Request to the UE.
  • Step 312 UE sends a NAS Location Notification Return Result to AMF.
  • the AMF informs the UE of the location request and related privacy check requirements, the category of periodic or triggered location reporting and other information.
  • Step 313 AMF executes the LMF selection process, that is, selects an LMF to perform the delayed location request task.
  • Step 314 AMF sends a location confirmation request message (Nlmf_Location_DetermineLocation Request) of the LMF network element to the selected LMF, that is, AMF sends a request message to LMF to locate the delayed position.
  • this message will carry the LCS association identifier, AMF identifier, serving cell identifier, client type, and may carry indication information to indicate: UE supports long term evolution positioning protocol (LPP) messages, desired positioning service quality (Quality of Service, QoS) and geographic area description type.
  • LPP long term evolution positioning protocol
  • QoS desired positioning service quality
  • Step 315 UE positioning, that is, LMF executes one or more positioning processes to request and obtain the UE's location.
  • Step 316 LMF sends a periodic or triggered invocation request message (LCS Periodic-Triggered Invoke Request) to the UE. That is, for delayed location reporting, LMF will send a supplementary LCS periodic or triggered request to the UE through the serving AMF.
  • the request carries the location request message obtained by LMF from AMF in step 314, informing the UE to subsequently perform the corresponding delayed periodic or triggered location reporting.
  • Step 317 The UE sends a positioning periodic or triggered call return message (LCS Periodic-Triggered Invoke Return) to the LMF. That is, if the UE supports the request in step 316, the UE returns a confirmation message to the LMF.
  • LCS Periodic-Triggered Invoke Return a positioning periodic or triggered call return message
  • Step 318 LMF sends a LMF network element location provision response message (Nlmf_Location_DetermineLocation Response) to AMF;
  • Step 319 AMF sends a location event notification message (Namf_Location_EventNotify) of the AMF network element to V-GMLC;
  • Step 320 V-GMLC sends a location event notification message (Ngmlc_Location_EventNotify) of the GMLC network element to H-GMLC;
  • Step 321a H-GMLC sends a positioning service response (LCS Service Response) to LCS Client;
  • Step 321b-1 H-GMLC sends a location event notification message (Ngmlc_Location_EventNotify) of the GMLC network element to NEF;
  • Step 321b-2 NEF sends an event exposure notification message (Nnef_EventExposure_Notify) of the NEF network element to AF;
  • the LMF informs the LCS client of this information through the AMF and GMLC, where this information may include information such as the UE positioning capability.
  • Step 322 An event is detected, i.e., if the periodic or triggered location request of steps 316 and 317 occurs successfully, the UE monitors the occurrence of the event requested in step 316. For area events or motion events, the UE monitors at a time interval equal to or less than the maximum event sampling interval.
  • the UE will trigger an event report:
  • the UE When an event trigger is detected, and if the UE is camped on or connected to an access type allowed by the LMF in step 316, the UE will proceed to step 323. If the UE cannot access the allowed access type, the UE may skip reporting the triggering event, or report the triggering event when the allowed access type becomes available according to the request received from the LMF in step 316.
  • Step 323 Positioning measurement, that is, the UE obtains positioning measurement information or the position estimation information requested or allowed in step 316.
  • Step 324 The UE initiates a UE triggered service request (UE Triggered Service Request) process, that is, if the UE is in the CMM idle state, the UE executes the service request process to establish an N1 signaling connection with the AMF.
  • UE Triggered Service Request UE Triggered Service Request
  • Step 325 The UE sends an event report to the LMF, i.e., the UE sends a supplementary event report message to the AMF corresponding to the LMF, which is finally delivered to the LMF, where the AMF transparently transmits this message.
  • This message may carry the event type and an embedded LPP message carrying the location estimation information.
  • Step 326 LMF sends an event report confirmation to the UE, that is, LMF accepts and processes the event report, LMF updates the status of the event report (for example, the number of reports to date, the reporting duration, etc.), and returns a confirmation message to the UE.
  • Step 327 UE positioning process, that is, if the event reporting requires location estimation information, then LMF may perform one or more positioning processes. LMF uses at least one of the measurement information and the location estimation to determine the location of the UE, where the timestamp information will also be determined.
  • 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 LCS Service Response to LCS Client
  • Step 330b-1 H-GMLC sends Ngmlc_Location_EventNotify to NEF
  • Step 330b-2 NEF sends Nnef_EventExposure_Notify to AF;
  • LMF performs event reporting to the LCS client through GMLC and reports the UE location to the LCS client.
  • an embodiment of the present application provides an event reporting method, which may include the following steps 401 to 403:
  • Step 401 The terminal sends first information.
  • the first information is used to indicate the relevant information of the terminal reporting an event outside the first area
  • the first area is an area where the terminal is allowed to report an event, that is, the first area is the event report allowed area mentioned above.
  • the terminal reports an event outside the first area, which can be specifically: the terminal reports an event conditionally outside the first area.
  • the constraint condition for implementing the conditional event reporting can be the constraint condition indicated by the reporting policy configured on the network side.
  • the terminal can report the Power saving area to the network side (used to instruct the terminal to report events within the area), and the network side can determine the event report allowed area based on the Power saving area, generally by converting fine-grained areas into coarse-grained areas, such as converting a rectangular area into a TA list or a cell list, as shown in Figure 5.
  • the first information is used to indicate relevant information of event reporting by the terminal outside the first area, that is, the first information is used to indicate at least one of relevant parameter information, capability, and whether to report an event by the terminal outside the first area.
  • the first information includes at least one of the following items A-1 to A-3:
  • Item A-1 a second area, where the second area is used to indicate an area where the terminal expects to report an event;
  • reporting indication i.e., Power saving class
  • the reporting indication is used to indicate whether the terminal supports event reporting outside the first area, or indicates whether the terminal reports events outside the first area, or indicates at least one level of event reporting by the terminal outside the first area;
  • Item A-3 area usage indication, wherein the area usage indication is used to indicate forward use of the first area or reverse use of the first area.
  • the above-mentioned second area is the Power saving area, which serves as the basis for the network side to determine the event report allowed area.
  • the specific implementation method can be: the reporting indication has two values, 0 indicates not reporting events, and 1 indicates conditional event reporting.
  • the reporting indication may indicate two levels, high and low, representing whether the terminal performs event reporting outside the first area, high indicating that event reporting is not performed, and low indicating that conditional event reporting is performed.
  • the reporting indication may indicate the first level (i.e., high level), the second level (i.e., medium level), and the third level (i.e., low level); when the level is the first level, the terminal only reports events within the first area (i.e., no event reporting is performed outside the first area); when the level is the second level, the terminal needs to report events within the first area, and conditionally report events outside the first area and within the second area; when the level is the third level, the terminal needs to report events within the first area, and conditionally report events outside the first area.
  • terminals often report events within a certain area.
  • users who are active in a fixed area for a long time in order to save power, there is no need to report periodic events. It is only valuable to report events when leaving a certain area.
  • the elderly in nursing homes are active in nursing homes all year round. After leaving the nursing homes, they report their locations to prevent getting lost (elderly mobile phones); kindergarten children leave the school during class time and need to report their locations to their parents' mobile phones to prevent getting lost (children's watches). Therefore, for some special terminals (such as elderly mobile phones, children's watches, etc.), the network side can configure them to use the first area in reverse, so as to meet the positioning needs and power saving needs in the corresponding scenarios.
  • the terminal does not provide this parameter, and it is determined by the first network side device based on information such as the type of the fourth network side device, the type of positioning service, and the contract information related to the terminal and positioning.
  • step 401 “the terminal sends first information” includes:
  • the terminal sends a target message, where the target message carries the first information
  • the target message includes at least one of the following items B-1 to B-3:
  • Item B-1 Registration request message
  • Item B-2 Location privacy setting request message
  • Item B-3 Uplink non-access layer transmission message.
  • the terminal can send the first information to the third network side device, which is then sent by the third network side device to the second network side device, and then the second network side device provides the first information to the first network side device, and then the first network side device obtains the event reporting configuration information matching the first information and sends it to the terminal.
  • the first network side device can be GMLC
  • the second network side device can be UDM
  • the third network side device can be AMF.
  • the terminal may carry the first information in 5G Mobility Management (5GMM) capability information, and encapsulate the 5GMM capability information in a registration request message, thereby sending the registration request to the AMF; or, the terminal may encapsulate the first information as a new IE in a registration request message, thereby sending the registration request to the AMF;
  • 5GMM 5G Mobility Management
  • Item B-2 above indicates that the terminal may send the first information to the AMF via a UE Location Privacy Setting Request message
  • Item B-3 above indicates that the terminal can also send the first information to the AMF via an uplink non-access layer transmission (UL NAS TRASPORT) message.
  • UL NAS TRASPORT uplink non-access layer transmission
  • Step 402 The terminal receives event reporting configuration information matching the first information.
  • the first information is used to indicate the relevant information of the terminal for event reporting outside the first area (that is, at least one of the relevant parameter information, capabilities, and whether to report). Therefore, the event reporting configuration information matches the first information, that is, the event reporting configuration information matches at least one of the relevant parameter information, capabilities, and whether to report the terminal for event reporting outside the first area.
  • the event reporting configuration information includes at least one of the following items C-1 to C-2:
  • Item C-1 target indication information, the target indication information is used to indicate whether the terminal needs to report an event outside the first area;
  • Item C-2 Reporting policy, where the reporting policy is used to indicate at least one constraint condition for the terminal to report an event.
  • the reporting indication it can be determined based on the reporting indication in the first information, wherein, if the reporting indication is understood based on the above-mentioned "understanding method one", that is, the reporting indication represents a capability, then, if the reporting indication indicates that the terminal supports event reporting outside the first area, the target indication information indicates that the terminal reports events outside the first area; if the reporting indication indicates that the terminal does not support event reporting outside the first area, the target indication information indicates that the terminal does not report events outside the first area. If the reporting indication is based on the above-mentioned "understanding method two or three", then, it is not necessary to determine the target indication information based on the reporting indication, that is, in this case, the event reporting configuration information does not include the target indication information.
  • the reporting indication in the first information indicates that the terminal supports event reporting outside the first area, or indicates that the terminal reports events outside the first area, or indicates the above second level or the above third level, indicating that the terminal needs to perform conditional event reporting. Therefore, in this case, the event reporting configuration information needs to include the reporting strategy to indicate how the terminal should implement conditional event reporting.
  • 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 of the candidate reporting policies in the policy set.
  • 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 is then sent to the second network side device by the third network side device, and then the second network side device provides the policy set to the first network side device).
  • the first network side device can select a candidate reporting policy from the policy set, and thus determine the reporting policy that needs to be sent to the terminal based on the selected candidate reporting policy.
  • the first network side may also determine the reporting strategy to be sent to the terminal according to at least one of the following information:
  • the type of the fourth network-side device i.e., the type of the device requesting the positioning service (e.g., LCS client/AF));
  • Positioning service type i.e. type of deferred 5GC-MT-LR (area, periodic or motion)
  • 5GC-MT-LR area, periodic or motion
  • the fourth network side device i.e., the device requesting the positioning service
  • Step 403 The terminal reports an event according to the event reporting configuration information.
  • the event report includes the location information of the terminal. Therefore, when the terminal reports the event, the location information of the terminal can be reported to the network side.
  • the terminal can send the first information to the first network side device, so that the first network side device obtains the event reporting configuration information matching the first information, thereby sending the event reporting configuration information to the terminal, so that the terminal can report the event according to the event reporting configuration information, wherein the first information is used to indicate the relevant information of the terminal reporting the event outside the first area, and the first area (i.e. The event report allowed area is the area where the terminal is allowed to report events.
  • the terminal can report the relevant information (i.e., the first information) of the event report outside the event report allowed area to the first network side device, so that the first network side device can configure appropriate event report configuration information for the terminal according to the relevant information, thereby enabling the terminal to implement more appropriate event reporting outside the event report allowed area. Therefore, the embodiment of the present application provides a method for the terminal to perform event reporting outside the event report allowed area.
  • the terminal supports event reporting only when it is within the event report allowed area, but when the terminal is outside the event report allowed area, whether the terminal is allowed to report the event, and if allowed, how the terminal should report the event, the related art does not provide a specific solution.
  • the problem with not reporting events outside the event report allowed area is that when the terminal does not report events for a long time, the LCS client/AF may think that the terminal has disconnected the positioning service session (LCS session), resulting in cancellation of the positioning process.
  • LCS session positioning service session
  • Area-based event reporting In this type, the LCS client/AF will provide a target area. If the target area is larger than the event report allowed area, this will result in the location information not being collected within the target area and outside the event report allowed area, thus reducing the amount of location data collected and the LCS client/AF experience.
  • event reporting can be conditionally performed outside the event report allowed area, this will allow the LCS client/AF to know the terminal's location outside the event report allowed area to a certain extent, and still maintain the LCS session (positioning service period); at the same time, it also takes power saving into consideration. For example, it can occasionally report according to the UE terminal's own power saving situation, or reduce the reporting frequency, so that the network side knows that the terminal's event reporting is still active.
  • Area-based event reporting In this type, the terminal is allowed to report its location within the target area and outside the event report allowed area, which not only meets the needs of LCS client/AF to collect location information, but also takes into account the actual power of the terminal;
  • conditionally performing event reporting outside the event report allowed area can take into account both the needs of positioning services and the needs of terminal power saving.
  • the above step 403 "the terminal reports the event according to the event reporting configuration information" includes at least one of the following E-1 to E-10:
  • Item E-1 When the event reporting configuration information includes the target indication information, and the target indication information indicates that the terminal does not need to report the event outside the first area, the terminal does not report the event outside the first area; that is, when the above-mentioned reporting indication is understood based on the above-mentioned "understanding method one", if the target indication information received by the terminal indicates that the event does not need to be reported outside the first area, then the terminal does not report the event when it is outside the first area.
  • Item E-2 When the event reporting configuration information includes the target indication information and the reporting policy, and the target indication information indicates that the terminal needs to report an event outside the first area, the terminal reports the event outside the first area according to the reporting policy; that is, when the above-mentioned reporting indication is understood based on the above-mentioned "understanding method one", if the terminal receives the target indication information and the reporting policy, and the target indication information indicates that event reporting is required outside the first area, then when the terminal is outside the first area, conditional event reporting is performed according to the reporting policy.
  • Item E-3 When the event reporting configuration information includes the target indication information, and the reporting configuration information does not include the reporting policy, and the target indication information indicates that the terminal needs to report an event outside the first area, the terminal does not report an event outside the first area, or, the terminal reports an event outside the first area based on implementation; that is, when the above-mentioned reporting indication is understood based on the above-mentioned "Understanding Method One", if the terminal receives the target indication information but does not receive the reporting policy, and the target indication information indicates that event reporting is required outside the first area, then when the terminal is outside the first area, the event may not be reported, or the event may be reported based on the actual situation of the terminal.
  • Item E-4 When the first information includes the reporting indication, and the reporting indication indicates that no event reporting is performed outside the first area, the terminal does not report the event outside the first area; that is, when the above-mentioned reporting indication is understood based on the above-mentioned "understanding method two", if the reporting indication indicates that no event reporting is performed outside the first area, then the network side may not send a reporting policy to the terminal, so that no event reporting is performed when the terminal is outside the first area.
  • Item E-5 When the first information includes the reporting indication, and the reporting indication indicates that an event is to be reported outside the first area, and the event reporting configuration information includes the reporting policy, the terminal is outside the first area and reports the event according to the reporting policy; that is, when the above-mentioned reporting indication is understood based on the above-mentioned "understanding method two", if the reporting indication indicates that an event is to be reported outside the first area, then the network side can send a reporting policy to the terminal, so that when the terminal is outside the first area, it can conditionally report the event according to the reporting policy.
  • Item E-6 When the first information includes the reporting indication, and the reporting indication indicates event reporting outside the first area, and the event reporting configuration information does not include the reporting policy, the terminal does not report the event outside the first area, or the terminal reports the event outside the first area based on implementation; that is, when the above-mentioned reporting indication is understood based on the above-mentioned "understanding method two", if the reporting indication indicates event reporting outside the first area, then the network side may not send a reporting policy to the terminal. In this way, when the terminal is outside the first area, it may not report the event, or it may report the event according to the actual situation of the terminal.
  • Item E-7 When the first information includes the reporting indication, and the reporting indication indicates the first level, and the event reporting configuration information does not include the reporting policy, the terminal does not perform reporting outside the first area.
  • Event reporting that is, when the above-mentioned reporting indication is understood based on the above-mentioned "Understanding Method Three", the first level indicates that the terminal does not report events outside the first area (that is, the first level is an implicit indication of "the terminal does not report events outside the first area").
  • the reporting indication indicates the first level, the network side may not send a reporting policy to the terminal. In this way, when the terminal is outside the first area, it may not report events.
  • the first information includes the reporting indication
  • the reporting indication indicates the second level
  • the event reporting configuration information includes the reporting policy
  • the terminal is outside the first area and within the second area, and reports the event according to the reporting policy; that is, when the above-mentioned reporting indication is understood based on the above-mentioned "understanding method three"
  • the second level represents that the terminal is conditionally reporting the event within the first area and within the second area (that is, the second level is an implicit indication of "the terminal is outside the first area and within the second area and reports the event conditionally").
  • the reporting indication indicates the second level
  • the network side can send a reporting policy to the terminal, so that when the terminal is outside the first area and within the second area, it can report the event conditionally according to the reporting policy.
  • the terminal is outside the first area and reports the event according to the reporting policy; that is, when the above-mentioned reporting indication is understood based on the above-mentioned "understanding method three", the third level represents that the terminal performs conditional event reporting in the first area (that is, the third level is an implicit indication of "the terminal performs conditional event reporting outside the first area").
  • the reporting indication indicates the third level
  • the network side can send a reporting policy to the terminal. In this way, when the terminal is outside the first area, it can perform conditional event reporting according to the reporting policy.
  • Item E-10 When the first information includes the reporting indication, and the reporting indication 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 events outside the first area, or the terminal reports events outside the first area based on implementation. That is, when the above-mentioned reporting indication is understood based on the above-mentioned "understanding method three", if the reporting indication indicates the above-mentioned second level or the above-mentioned third level, the network side may not send a reporting policy to the terminal. In this way, when the terminal is outside the first area, it may not report events, or it may report events based on the actual situation of the terminal.
  • the reporting strategy includes at least one of the following items D-1 to D-3:
  • Item D-2 Minimum time interval between two consecutive event reports
  • Item D-3 triggering conditions for event reporting, wherein the triggering conditions are used to indicate threshold information other than the minimum time interval and the maximum number of reporting times.
  • item D-1 is used to indicate that when the terminal performs conditional event reporting, the number of reports cannot exceed the maximum number of reports. For example, when the terminal performs conditional event reporting outside the first area, after the number of event reports outside the first area reaches the maximum number of reports, the terminal will no longer continue to report events outside the first area.
  • Item D-2 is used to indicate that when the terminal performs conditional event reporting, the event interval between two adjacent event reports cannot exceed the minimum time interval.
  • Item D-3 indicates other constraints for conditional event reporting, for example, event reporting is performed only when the moving straight-line distance reaches 100m.
  • the terminal reports the event according to the reporting strategy, including:
  • the terminal performs conditional event reporting according to at least one of the maximum reporting times, the minimum time interval, and the trigger condition.
  • the reporting strategy includes the maximum number of reports (x), the minimum time interval (t), and the trigger condition (F condition), then the terminal performs conditional time reporting outside the first area according to the reporting strategy, that is: when the terminal is outside the first area, upon detecting the F condition, it reports the event according to t, and stops reporting when the number of reports reaches x; compared with the reporting parameters within the first area, the reporting constraints outside the first area are more stringent, such as a smaller maximum number of reports, a longer minimum reporting interval, a longer moving distance limit, etc.
  • the method further comprises:
  • the terminal sends third information, wherein the third information includes the changed information in the first information.
  • the terminal can send the changed information to the first network side device.
  • the way in which the terminal sends the above-mentioned third information is the same as the way in which the terminal sends the first information as described above, that is, the terminal sends the third information to the third network side device, which is then sent by the third network side device to the second network side device, and then the second network side device provides the third information to the first network side device.
  • the method further comprises:
  • the terminal receives fourth information, wherein the fourth information includes at least one of the first area and the event reporting configuration information, and the fourth information is determined according to the third information;
  • the terminal reports an event according to the fourth information.
  • the first network side device can further update the first area and event reporting configuration information (including target indication information, at least one of the reporting policies) based on the changed information, thereby sending the updated information (i.e., the fourth information) to the terminal, so that the terminal can report the event based on the fourth information, so that the event reporting situation can conform to the actual situation of the terminal.
  • the updated information i.e., the fourth information
  • the first network side device can send the fourth information to the third network side device, which is then sent by the third network side device to the fifth network side device (such as LMF), and then sent by the fifth network side device to the terminal.
  • the third network side device such as LMF
  • the fifth network side device such as LMF
  • the embodiment of the present application further provides an event reporting method, which may include the following steps 701 to 703:
  • Step 701 A first network-side device obtains first information of a terminal.
  • the first information is used to indicate the relevant information of the terminal reporting an event outside the first area
  • the first area is an area where the terminal is allowed to report an event, that is, the first area is the event report allowed area mentioned above.
  • the terminal reports an event outside the first area, which can be specifically: the terminal reports an event conditionally outside the first area.
  • the constraint condition for implementing the conditional event reporting can be the constraint condition indicated by the reporting policy configured on the network side.
  • the terminal can report the Power saving area to the network side (used to instruct the terminal to report events within the area), and the network side can determine the event report allowed area based on the Power saving area, generally by converting fine-grained areas into coarse-grained areas, such as converting a rectangular area into a TA list or cell list, as shown in Figure 5.
  • the first information is used to indicate the relevant information of the terminal reporting the event outside the first area, that is, the first information is used to indicate the relevant parameter information, capability, and whether to report the event when the terminal reports the event outside the first area. At least one of the behaviors.
  • the first information includes at least one of the following items A-1 to A-3:
  • Item A-1 a second area, where the second area is used to indicate an area where the terminal expects to report an event;
  • reporting indication i.e., Power saving class
  • the reporting indication is used to indicate whether the terminal supports event reporting outside the first area, or indicates whether the terminal reports events outside the first area, or indicates at least one level of event reporting by the terminal outside the first area;
  • Item A-3 area usage indication, wherein the area usage indication is used to indicate forward use of the first area or reverse use of the first area.
  • step “701, the first network side device obtains first information of the terminal” includes:
  • the first network side device obtains the first information from the second network side device, wherein the first information stored in the second network side device is sent by the terminal to the second network side device through the third network side device.
  • the terminal can send the first information to the third network side device, which is then sent by the third network side device to the second network side device, and then the second network side device provides the first information to the first network side device.
  • the first network side device can be GMLC
  • the second network side device can be UDM
  • the third network side device can be AMF.
  • Step 702 The first network-side device obtains event reporting configuration information matching the first information.
  • the first information is used to indicate the relevant information of the terminal for event reporting outside the first area (that is, at least one of the relevant parameter information, capabilities, and whether to report). Therefore, the event reporting configuration information matches the first information, that is, the event reporting configuration information matches at least one of the relevant parameter information, capabilities, and whether to report the terminal for event reporting outside the first area.
  • the event reporting configuration information includes at least one of the following items C-1 to C-2:
  • Item C-1 target indication information, the target indication information is used to indicate whether the terminal needs to report an event outside the first area;
  • Item C-2 Reporting policy, where the reporting policy is used to indicate at least one constraint condition for the terminal to report an event.
  • Step 703 The first network side device sends the reporting configuration information to the terminal.
  • step 703 “the first network side device sends the event reporting configuration information to the terminal” includes:
  • the first network side device sends the event reporting configuration information to the terminal through the third network side device and the fifth network side device.
  • the third network side device can be AMF
  • the fifth network side device can be LMF.
  • the first network side device can send the reporting configuration information to the third network side device, so that the third network side device sends the reporting configuration information to the fifth network side device, and then the LMF fifth network side device sends the reporting configuration information to the terminal.
  • the terminal can send the first information to the first network side device, so that the first network side device obtains the event reporting configuration information matching the first information, thereby sending the event reporting configuration information to the terminal, so that the terminal can report the event according to the event reporting configuration information, wherein the first information is used to indicate the relevant information of the terminal reporting the event outside the first area, and the first area (i.e. The event report allowed area is the area where the terminal is allowed to report events.
  • the terminal can report the relevant information (i.e., the first information) of the event report outside the event report allowed area to the first network side device, so that the first network side device can configure appropriate event report configuration information for the terminal according to the relevant information, thereby enabling the terminal to implement more appropriate event reporting outside the event report allowed area. Therefore, the embodiment of the present application provides a method for the terminal to perform event reporting outside the event report allowed area.
  • the reporting strategy includes at least one of the following items D-1 to D-3:
  • Item D-2 Minimum time interval between two consecutive event reports
  • Item D-3 triggering conditions for event reporting, wherein the triggering conditions are used to indicate threshold information other than the minimum time interval and the maximum number of reporting times.
  • the first network side device obtains event reporting configuration information matching the first information, including one of the following F-1 to F-2:
  • the first network side device determines the event reporting configuration information (i.e., determines the reporting strategy included in the event reporting configuration information) according to the positioning service type and the contract information related to positioning of the terminal;
  • the first network side device can also combine the first area, the second area, the reporting indication, the area usage indication, the positioning service type and the contract information related to the terminal and positioning to determine the reporting strategy that needs to be sent to the terminal.
  • the first network side may determine the reporting strategy to be sent to the terminal according to at least one of the following information:
  • the type of the fourth network-side device i.e., the type of the device requesting the positioning service (e.g., LCS client/AF));
  • Positioning service type i.e. type of deferred 5GC-MT-LR (area, periodic or motion)
  • 5GC-MT-LR area, periodic or motion
  • Item F-2 When the reporting indication indicates that the terminal supports event reporting outside the first area, or indicates that the terminal reports an event outside the first area, or indicates the second level or the third level, the first network side device determines the event reporting configuration information (i.e., determines the reporting strategy included in the event reporting configuration information) according to the reporting strategy received from the fourth network side device;
  • the fourth network side device i.e., the device requesting the positioning service
  • the process in which the first network side device receives the reporting strategy sent by the fourth network side device includes: the first network side device receives the positioning service request sent by the fourth network side device, wherein: The positioning service request carries a reporting strategy.
  • the fourth network-side device may carry the reporting policy that needs to be sent to the first network-side device in the positioning service request.
  • the first network side device selects a candidate reporting strategy from the policy set according to the positioning service type, and determines the event reporting configuration information (i.e., determines the reporting strategy included in the event reporting configuration information) based on the selected candidate reporting strategy, wherein the policy set includes at least one candidate reporting strategy.
  • 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, and then the second network side device provides the policy set to the first network side device).
  • the first network side device can select a candidate reporting policy from the policy set, and thus determine the reporting policy that needs to be sent to the terminal based on the selected candidate reporting policy.
  • the first network-side device when the first network-side device selects a candidate reporting strategy from the strategy set, in addition to considering the positioning service type, it may further combine the subscription information related to positioning of the terminal.
  • the first network side device can use the candidate reporting policy selected from the policy set as the reporting policy that needs to be sent to the terminal, and can also select some constraints from the candidate reporting policy as the constraints of the reporting policy that needs to be sent to the terminal.
  • the first network side device determines the target indication information according to the reporting indication, that is, if the reporting indication is understood based on the above-mentioned "understanding method one", that is, the reporting indication represents a capability, then, if the reporting indication indicates that the terminal supports event reporting outside the first area, the target indication information indicates that the terminal reports the event outside the first area; if the reporting indication indicates that the terminal does not support event reporting outside the first area, the target indication information indicates that the terminal does not report the event outside the first area. If the reporting indication is based on the above-mentioned "understanding method two or three", then, it is not necessary to determine the target indication information according to the reporting indication, that is, in this case, the event reporting configuration information does not include the target indication information.
  • the method further comprises:
  • the first network side device sends second information to the fourth network side device, wherein the second information includes at least one of the following items G-1 to G-5:
  • G-1 the first region
  • Item G-2 reporting indication, where the reporting indication is used to indicate whether the terminal supports event reporting outside the first area, or indicates whether the terminal performs event reporting outside the first area;
  • Item G-3 the event reporting configuration information (which may include at least one of the above-mentioned target indication information and reporting strategy);
  • Item G-4 area use indication, the area use indication is used to indicate forward use of the first area, or reverse use of the first area;
  • Target area error indication where the target area error indication is used to indicate that there is no overlap between the target area (Target area) and the second area (Power saving area) or there is a logical error in the target area, and the target area is the area where the terminal is expected to report an event. (i.e., the area where the network side expects the terminal to report events.
  • a positioning service request may include an area where the network side hopes to obtain the terminal's location information in the area, and the area is the target area).
  • the second area is used to indicate the area where the terminal expects to report events.
  • the target area error reason can be understood as a reason in a rejection message of a location service request message, indicating that the Target area requested by the LCS location server request message is incorrect, such as the Target area and the Power saving area have no overlapping areas or there is a logical error, and the Target area needs to be corrected.
  • the Power saving area is area A, but the Target area is the country to which the A area belongs.
  • the leaving (leaving) or entering (enter) type report will never be triggered, and the user needs to report the location within the country all the time, then it is considered that the Target area here is too large, which is a logical error.
  • target area error reason may also be used to indicate that there is no overlapping area between the target area and the first area (i.e., the event report allowed area).
  • the fourth network side device can re-initiate a positioning service request, which carries the re-determined target area.
  • the method further comprises:
  • the first network side device obtains third information provided by the second network side device, wherein the third information includes information that has changed in the first information, and the third information stored in the second network side device is sent by the terminal to the second network side device through the third network side device.
  • the terminal can send the changed information (i.e., the third information) to the second network side device, wherein, if the first network side device has subscribed to the terminal information in the second network side device, the second network side device can provide the third information to the first network side device after receiving it.
  • the changed information i.e., the third information
  • the method further comprises:
  • the first network side device updates fourth information according to the third information, wherein the fourth information includes at least one of the first area and the event reporting configuration information;
  • the first network side device sends the updated fourth information to the terminal.
  • the first network side device can further update the first area and event reporting configuration information (including target indication information, at least one of the reporting policies) based on the changed information, thereby sending the updated information (i.e., the fourth information) to the terminal, so that the terminal can report the event based on the fourth information, so that the event reporting situation can conform to the actual situation of the terminal.
  • the updated information i.e., the fourth information
  • the first network side device can send the fourth information to the third network side device, which is then sent by the third network side device to the fifth network side device (such as LMF), and then sent by the fifth network side device to the terminal.
  • the third network side device such as LMF
  • the fifth network side device such as LMF
  • the first network side device can also determine the above-mentioned fourth information based on the third information by further combining the target area, the currently used first area, the currently used reporting strategy and the current reporting status (i.e., report status, such as the number of reports to date, reporting duration, etc.).
  • an embodiment of the present application further provides an event reporting method, comprising the following step H-1:
  • Step H-1 The fourth network-side device sends a reporting policy to the first network-side device, wherein the reporting policy is used to indicate at least one constraint condition for the terminal to report an event.
  • the fourth network side device can be LCS client/AF.
  • the first network-side device can determine the reporting policy that needs to be sent to the terminal according to the reporting policy sent by the fourth network-side device.
  • step H-1 “the fourth network side device sends a reporting strategy to the first network side device” includes:
  • the fourth network side device sends a positioning service request to the first network side device, wherein the positioning service request carries a reporting strategy.
  • the fourth network side device i.e., the device requesting the positioning service
  • the fourth network side device can also carry a reporting strategy in the positioning service request sent to the first network side device, so that the first network side device can determine the reporting strategy that needs to be sent to the terminal based on the reporting strategy carried in the positioning service request.
  • the method further comprises:
  • the fourth network side device receives the second information sent by the first network side device, wherein the second information includes at least one of the following items G-1 to G-5:
  • G-1 the first region
  • Item G-2 reporting indication, where the reporting indication is used to indicate whether the terminal supports event reporting outside the first area, or indicates whether the terminal performs event reporting outside the first area;
  • Item G-3 the event reporting configuration information (which may include at least one of the above-mentioned target indication information and reporting strategy);
  • Item G-4 area use indication, the area use indication is used to indicate forward use of the first area, or reverse use of the first area;
  • Target area error indication wherein the target area error indication is used to indicate that there is no overlapping area between the target area (Target area) and the second area (Power saving area) or there is a logical error in the target area, the target area is the area where the terminal is expected to report an event (that is, the area where the network side expects the terminal to report an event, for example, a positioning service request may include an area where it is hoped to obtain the terminal's location information in the area, and the area is the target area), and the second area is used to indicate the area where the terminal expects to report an event.
  • the target area error indication is used to indicate that there is no overlapping area between the target area (Target area) and the second area (Power saving area) or there is a logical error in the target area
  • the target area is the area where the terminal is expected to report an event (that is, the area where the network side expects the terminal to report an event, for example, a positioning service request may include an area where it is hoped to obtain the terminal's location
  • the fourth network side device may re-initiate a positioning service request, which carries the re-determined target area.
  • an embodiment of the present application further provides an event reporting method, comprising the following steps K-1 to K-2:
  • Step K-1 The second network side device obtains the first information of the terminal and stores the first information.
  • the first information is used to indicate relevant information of the terminal reporting an event outside a first area, and the first area is an area where the terminal is allowed to report an event.
  • the second network side device can receive the first information sent by the terminal through the third network side device.
  • Step K-2 the second network side device provides the first information to the first network side device.
  • the second network side device acquires the first information of the terminal, including:
  • the second network side device receives the first information sent by the terminal through the third network side device.
  • the second network side device may be UDM
  • the third network side device may be AMF
  • the first network side device may be GMLC.
  • the first network side device After the first network side device obtains the first information, it can obtain event reporting configuration information matching the first information, and send the event reporting configuration information to the terminal, so that the terminal reports the event according to the event reporting configuration information.
  • the first information includes at least one of the following items A-1 to A-3:
  • Item A-1 a second area, where the second area is used to indicate an area where the terminal expects to report an event;
  • reporting indication i.e., Power saving class
  • the reporting indication is used to indicate whether the terminal supports event reporting outside the first area, or indicates whether the terminal reports events outside the first area, or indicates at least one level of event reporting by the terminal outside the first area;
  • Item A-3 area usage indication, wherein the area usage indication is used to indicate forward use of the first area or reverse use of the first area.
  • the first information also includes a policy set, and the policy set includes at least one candidate reporting policy.
  • the method further comprises:
  • the second network side device receives the third information sent by the first terminal, and stores the third information, wherein the third information includes the changed information in the first information;
  • the second network side device provides the third information to the first network side device.
  • the terminal can send the changed information (i.e., the third information) to the second network side device, wherein, if the first network side device has subscribed to the terminal information in the second network side device, the second network side device can provide the third information to the first network side device after receiving it.
  • the changed information i.e., the third information
  • Implementation method 1 as shown in FIG8 , including the following steps 81 to 819:
  • Step 81 The terminal sends NAS signaling to the AMF.
  • the NAS signaling carries first information.
  • the first information includes at least one of the following items (1) to (5):
  • UE ID terminal identification
  • Power saving area i.e., the second area, i.e., an area represented by coordinates or TA/cell, used to describe the execution of event report in the area when the terminal is in power saving state
  • Power saving class i.e., reporting instructions
  • Power saving class can be understood in the following three ways:
  • the reporting indication includes the following two global mutually exclusive settings, one is that the terminal supports event reporting outside the event report allowed area, and the other is that the terminal does not support event reporting outside the event report allowed area, and the latter is the default setting.
  • the Power saving class has two values, 0 for not executing and 1 for conditionally executing.
  • the Power saving class includes two levels, high and low, which represent whether the terminal executes the event report outside the event report allowed area. High means no execution, and low means conditional execution.
  • Another implementation method may be applicable to an LCS client/AF request type which is an area-based event report, namely, the Power saving class includes different levels: high, medium and low; when the level is high, the policy is that the terminal only executes event report within the event report allowed area; when the level is medium, the policy is that the terminal needs to execute event report within the event report allowed area, and perform conditional reporting outside the event report allowed area and within the Power saving area; when the level is low, the policy is that the terminal needs to execute event report within the event report allowed area, and perform conditional reporting outside the event report allowed area.
  • the Power saving class includes different levels: high, medium and low; when the level is high, the policy is that the terminal only executes event report within the event report allowed area; when the level is medium, the policy is that the terminal needs to execute event report within the event report allowed area, and perform conditional reporting outside the event report allowed area and within the Power saving area; when the level is low, the policy is that the terminal needs to execute event report within the event report allowed area, and perform conditional reporting
  • the reporting indication includes the following two global mutually exclusive settings for the event report allowed area, one for reverse use and the other for forward use, the latter being the default setting.
  • the terminal may carry the first information in the 5GMM capability information, and encapsulate the 5GMM capability information in a registration request message, thereby sending the registration request to the AMF;
  • the terminal may also encapsulate the first information as a new IE in a registration request message, thereby sending the registration request to the AMF;
  • the terminal may also send the first information to the AMF through a terminal location privacy setting request (UE Location Privacy Setting Request) message;
  • UE Location Privacy Setting Request UE Location Privacy Setting Request
  • the terminal may also send the first information to the AMF via an uplink non-access layer transmission (UL NAS TRASPORT) message.
  • UL NAS TRASPORT uplink non-access layer transmission
  • Step 82 AMF sends an update data configuration message (Nudm_ParameterProvision_Update) of the UDM network element to UDM, where Nudm_ParameterProvision_Update carries the above-mentioned first information (i.e., UE ID, Power saving area, Power saving class, area usage indication, etc.).
  • Nudm_ParameterProvision_Update carries the above-mentioned first information (i.e., UE ID, Power saving area, Power saving class, area usage indication, etc.).
  • Step 83 UDM stores the received first information (i.e., the Power saving area, Power saving class, and area usage indication of the UE ID).
  • the received first information i.e., the Power saving area, Power saving class, and area usage indication of the UE ID.
  • Step 84 LCS client/AF sends a positioning service request (LCS service request) to GMLC, requesting the terminal to perform delayed reporting.
  • LCS service request a positioning service request
  • the untrusted AF needs to use NEF as an intermediate network element to perform service verification.
  • the AF initiates a subscription to the NEF, and the NEF initiates a positioning request to the GMLC.
  • Step 85 GMLC sends Nudm_SDM_get or UDM network element's contract data subscription request message (Nudm_SDM_subscribe) message to UDM to query the contract information related to the positioning of UE ID, obtain the first information (i.e. Power saving area, Power saving class, area usage indication, etc.) and save it.
  • Nudm_SDM_get or UDM network element's contract data subscription request message Nudm_SDM_subscribe
  • This step can be a one-time query or a subscription. If this is a subscription, the steps in the subsequent embodiment 4 are Step 115 will occur.
  • Step 86 The GMLC performs at least one of the following (1) to (3):
  • Minimum reporting time interval i.e., the minimum time interval between two consecutive event reports
  • Trigger conditions for event reporting wherein the trigger conditions are used to indicate threshold information other than the minimum time interval and the maximum number of reports.
  • One implementation method may be: event reporting is performed only when the moving straight-line distance reaches a certain threshold (for example, 100 meters).
  • GMLC can determine the values of one or more parameters in (a) to (c) above according to the service type of the positioning service request in the aforementioned step 84 (i.e., the type of deferred 5GC-MT-LR (area or periodic or motion)) and the positioning-related contract information obtained in step 85.
  • the service type of the positioning service request in the aforementioned step 84 i.e., the type of deferred 5GC-MT-LR (area or periodic or motion)
  • the positioning-related contract information obtained in step 85 i.e., the type of deferred 5GC-MT-LR (area or periodic or motion)
  • one implementation method of GMLC determination strategy can be, for example, the terminal needs to report periodically in the event report allowed area, but outside the event report allowed area, the periodicity will be reduced, that is, the reporting time interval becomes twice as long as before, and the number of reports has an upper limit. After the upper limit is reached, no report will be made outside the event report allowed area.
  • the GMLC can determine the target indication information according to the specific content indicated by the Power saving class, that is, if the Power saving class indicates that the terminal supports event reporting outside the event report allowed area, then the target indication information indicates that the terminal needs to report events outside the event report allowed area; if the Power saving class indicates that the terminal does not support event reporting outside the event report allowed area, then the target indication information indicates that the terminal does not need to report events outside the event report allowed area); an implicit implementation method of the target indication information is that if the GMLC sends the target indication information to the terminal, it means that the terminal is instructed to report events outside the event report allowed area; if the GMLC does not send the target indication information to the terminal, it means that the terminal is instructed to not report events outside the event report allowed area.
  • the GMLC can further determine at least one constraint in the strategy based on the terminal's positioning service type and positioning-related contract information; if the Power saving class indicates that the terminal does not support event reporting outside the event report allowed area, the GMLC does not need to determine the strategy.
  • the Power saving class adopts the above "understanding method 2". For event reporting based on periodic or motion, the Power saving class instructs the terminal to report events outside the event report allowed area.
  • GMLC can further combine the subscription information related to positioning to determine at least one constraint in the strategy; when the Power saving class instructs the terminal not to report events outside the event report allowed area, GMLC does not need to determine the strategy.
  • the above-mentioned Power saving class adopts the above-mentioned "understanding method three".
  • the GMLC can further determine at least one constraint condition in the strategy, so that the terminal is outside the event report allowed area and within the Power saving area, and reports conditionally according to the strategy;
  • the Power saving class indicates "low”
  • the GMLC can further determine at least one constraint condition in the strategy, so that the terminal is outside the event report allowed area, and reports conditionally according to the strategy;
  • the Power saving class indicates "high”
  • the GMLC does not need to determine the strategy.
  • Step 87 GMLC sends a Namf_Location_ProvidePositioningInfo Request to AMF, wherein the message carries the event report allowed area and the above-mentioned target indication information. Furthermore, if the GMLC determines the strategy in the above-mentioned step 86, the message may also carry the strategy determined by the GMLC.
  • Step 88 AMF responds with Namf_Location_ProvidePositioningInfo Response to GMLC, confirming receipt of the message in step 87.
  • Step 89 The GMLC sends a second message to the LCS client/AF, wherein the second message includes at least one of the following (1) to (5):
  • event report allowed area i.e., determined by the GMLC in step 86
  • Target area error indication (only applicable to the type of LCS client/AF request based on area event reporting).
  • Target area error indication can be understood as a reason (cause) in the rejection message of the request message in step 84, indicating that the Target area requested by the LCS client/AF is incorrect, for example, the Target area does not overlap with the Power saving area or there is a logical error, and the Target area needs to be corrected.
  • Step 810 AMF, RAN, and UE execute steps 39 to 313 described above, wait for the terminal to enter the connected state, establish a connection with the terminal, and complete the user's privacy verification.
  • Step 811 AMF sends Nlmf_Location_DetermineLocation Request to LMF, wherein the message carries event report allowed area and the above target indication information. Furthermore, if AMF receives strategy in the above step 87, the message may also carry the strategy received by AMF.
  • Step 812 terminal positioning process, that is, the LMF executes one or more positioning processes to request and obtain the location of the terminal;
  • Step 813 LMF sends an LCS Periodic-Triggered Invoke Request message to the UE, wherein the message carries the event report allowed area and the above target indication information. Furthermore, if the LMF receives the strategy in the above step 811, the message may also carry the strategy received by the LMF.
  • Step 814 UE sends LCS Periodic-Triggered Invoke Return to LMF;
  • Step 815 LMF sends Nlmf_Location_DetermineLocation Response to AMF;
  • Step 816 AMF sends Namf_Location_EventNotify to GMLC;
  • Step 817 GMLC sends LCS Service Response to LCS Client/AF;
  • Step 818 The terminal detects the event and performs corresponding operations
  • the UE detects an event trigger and is outside the event report allowed area, it performs at least one of the following actions (1) to (10):
  • step 819 If the Power saving class indicates that the UE does not perform reporting outside the event report allowed area, the UE does not perform reporting (i.e., step 819 does not exist);
  • step 813 If the Power saving class instructs the UE to report events outside the event report allowed area, and a strategy is received in step 813, the UE performs conditional event reporting outside the event report allowed area according to the strategy;
  • step 813 If the Power saving class instructs the UE to perform event reporting outside the event report allowed area, but no strategy is received in step 813, the UE does not perform event reporting outside the event report allowed area, or the UE performs event reporting based on the implementation;
  • step 813 If the target indication information received in step 813 indicates that the UE does not perform event reporting outside the event report allowed area or the target indication information is not received, the UE does not perform event reporting (i.e., step 819 does not exist);
  • step 813 If the target indication information received in step 813 indicates that the UE reports events outside the event report allowed area, and a strategy is received in step 813, the UE performs conditional event reporting outside the event report allowed area according to the strategy;
  • step 813 If the target indication information received in step 813 indicates that the UE should report an event outside the event report allowed area, but no strategy is received in step 813, the UE does not perform event reporting outside the event report allowed area, or the UE performs event reporting based on the implementation;
  • step 819 If the Power saving class indicates “high”, the UE does not perform reporting (i.e., step 819 does not exist);
  • step 813 If the power saving class indicates "medium” and the strategy is received in step 813, the UE performs conditional event reporting according to the strategy when it is outside the event report allowed area and within the power saving area;
  • step 813 If the Power saving class indicates "low” and the strategy is received in step 813, the UE performs conditional event reporting outside the event report allowed area according to the strategy;
  • step 813 If the Power saving class indicates "medium or low”, but no strategy is received in step 813, the UE does not perform event reporting outside the event report allowed area, or the UE performs event reporting based on the implementation.
  • the UE performs conditional reporting according to the strategy. For example, in combination with the example in step 86, when the strategy includes two parameters, namely the maximum number of reports and the minimum time interval, 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 cannot be greater than the maximum number of reports.
  • Step 819 Execute the event reporting process, which is the same as steps 323 to 330b-2 described above and will not be repeated here.
  • Steps 91 to 93 are respectively the same as steps 81 to 83 in the above-mentioned first embodiment, and will not be repeated here.
  • Step 94 LCS client/AF sends an LCS service request to GMLC, requesting the terminal to perform delay reporting, wherein the LCS service request carries a strategy;
  • Step 95 is the same as step 95 in the above-mentioned embodiment 1 and will not be described again here.
  • Step 96 The GMLC performs at least one of the following (1) to (3):
  • Minimum reporting time interval i.e., the minimum time interval between two consecutive event reports
  • Trigger conditions for event reporting wherein the trigger conditions are used to indicate threshold information other than the minimum time interval and the maximum number of reports.
  • One implementation method may be: event reporting is performed only when the moving straight-line distance reaches a certain threshold (for example, 100 meters).
  • the GMLC may use the strategy carried by the LCS service request as the strategy that needs to be sent to the UE (that is, in this case, the GMLC does not need to determine the strategy in step 96), or select some constraints (that is, parameters) included in the strategy carried by the LCS service request as the constraints (that is, parameters) of the strategy that needs to be sent to the UE.
  • Steps 97 to 98 are respectively the same as steps 87 to 88 in the above-mentioned first embodiment, and are not described again here.
  • Step 99 The GMLC sends a second message to the LCS client/AF, wherein the second message includes at least one of the following (1) to (5):
  • event report allowed area i.e., determined by the GMLC in step 86
  • step 99 is relative to step 89 in the first implementation mode, and the second information sent by GMLC to LCS client/AF does not include strategy.
  • Steps 99 to 919 are respectively the same as steps 89 to 819 in the above-mentioned first embodiment, and are not repeated here.
  • Step 101 The terminal sends NAS signaling to the AMF.
  • the NAS signaling carries first information.
  • the first information includes at least one of the following items (1) to (5):
  • UE ID terminal identification
  • a strategy set which includes at least one candidate strategy. Different strategies in the strategy set are suitable for different positioning types.
  • the GMLC can subsequently select the appropriate strategy from the strategy set according to different services. strategy.
  • Step 102 AMF sends Nudm_ParameterProvision_Update to UDM, where Nudm_ParameterProvision_Update carries the above-mentioned first information (i.e., UE ID, Power saving area, Power saving class, area usage indication, policy set and other information).
  • Nudm_ParameterProvision_Update carries the above-mentioned first information (i.e., UE ID, Power saving area, Power saving class, area usage indication, policy set and other information).
  • Step 103 UDM stores the received first information (i.e., the Power saving area, Power saving class, area usage indication, and policy set of the UE ID).
  • the received first information i.e., the Power saving area, Power saving class, area usage indication, and policy set of the UE ID.
  • Step 104 is the same as step 84 in the above-mentioned first embodiment and will not be described again here.
  • Step 105 GMLC sends a Nudm_SDM_get or Nudm_SDM_subscribe message to UDM to query the contract information related to the positioning of the UE ID, obtain the first information (i.e., Power saving area, Power saving class, area usage indication, policy set, etc.) and save it.
  • the first information i.e., Power saving area, Power saving class, area usage indication, policy set, etc.
  • Step 106 The GMLC performs at least one of the following (1) to (3):
  • Minimum reporting time interval i.e., the minimum time interval between two consecutive event reports
  • Trigger conditions for event reporting wherein the trigger conditions are used to indicate threshold information other than the minimum time interval and the maximum number of reports.
  • One implementation method may be: event reporting is performed only when the moving straight-line distance reaches a certain threshold (for example, 100 meters).
  • the GMLC can select a candidate strategy from the strategy set based on the network selection or the type of LCS client (area or periodic or motion), the terminal and positioning-related contract information obtained in step 105, etc., and then determine the strategy to be sent to the UE based on the selected candidate strategy.
  • Steps 107 to 1019 are respectively the same as steps 87 to 819 in the above-mentioned first embodiment, and are not repeated here.
  • Implementation method 4 as shown in FIG11 , including the following steps 111 to 116:
  • Step 111 The first information of the terminal changes, that is, at least one of the power saving area, power saving class, area usage indication, and policy set of the terminal changes;
  • Step 112 The terminal sends a NAS message to the AMF, carrying the third information, where the third information includes at least one of the following changes:
  • the terminal may carry the third information in the 5GMM capability information, and encapsulate the 5GMM capability information in a registration request message, thereby sending the registration request to the AMF;
  • the terminal may also encapsulate the third information as a new IE in a registration request message, thereby sending the registration request to the AMF;
  • the terminal may also send the third information to the AMF through a UE Location Privacy Setting Request message;
  • the terminal may also send the third information to the AMF via an uplink non-access layer transmission (UL NAS TRASPORT) message.
  • UL NAS TRASPORT uplink non-access layer transmission
  • Step 113 AMF sends Nudm_ParameterProvision_Update to UDM, where Nudm_ParameterProvision_Update carries the third information mentioned above (i.e., at least one of the changes in Power saving area, Power saving class, area usage indication, and policy set).
  • Step 114 UDM stores the received third information (i.e., Power saving area, Power saving class, area usage indication, and at least one item that has changed in the policy set).
  • the received third information i.e., Power saving area, Power saving class, area usage indication, and at least one item that has changed in the policy set.
  • Step 115 UDM provides the third information to GMLC (i.e., Power saving area, Power saving class, area usage indication, and at least one item that has changed in the policy set).
  • GMLC i.e., Power saving area, Power saving class, area usage indication, and at least one item that has changed in the policy set.
  • UDM provides GMLC with updated information such as Power saving area, Power saving class, area usage indication, policy set, etc.
  • Step 116 The GMLC updates at least one of the following based on the updated power saving area, power saving class, area usage indication, policy set, combined with the target area, the current event report allowed area, the current strategy, and the current report status (i.e., report status, such as the number of reports to date, the reporting duration, etc.):
  • Step 117 GMLC sends at least one of the updated event report allowed area, strategy, and target indication information to the terminal through AMF and LMF.
  • the terminal can report its own Power saving class and area usage indication to indicate whether the terminal uses the event report allowed area in a positive or reverse direction, and whether the terminal supports conditional reporting outside the event allowed area; further, the terminal can also provide a policy set, and the GMLC selects a candidate reporting policy from the policy set according to the positioning service, and then determines the reporting policy that needs to be sent to the terminal; or, the LCS client/AF can directly provide the reporting policy; or, when neither the terminal nor the LCS client/AF provides it, the GMLC determines the reporting policy that needs to be sent to the terminal.
  • the terminal can also update its power saving class, policy set, and area usage indication and save them in the UDM so that the GMLC can update the terminal's execution actions outside the area based on the updated information.
  • the execution subject may be an event reporting device.
  • the event reporting device performing the event reporting method is taken as an example to illustrate the event reporting device provided in the embodiment of the present application.
  • an embodiment of the present application provides an event reporting device, which can be applied to a terminal.
  • the event reporting device 120 includes:
  • a first sending module 1201 is used to send first information, wherein the first information is used to indicate relevant information of an event reporting by a terminal outside a first area, and the first area is an area where the terminal is allowed to report an event;
  • the first processing module 1203 is used to report an event according to the event reporting configuration information.
  • the first information includes at least one of the following:
  • a second area where the second area is used to indicate an area where the terminal expects to report an event
  • reporting indication is used to indicate whether the terminal supports event reporting outside the first area, or whether the terminal reports an event outside the first area, or indicates at least one level of event reporting by the terminal outside the first area;
  • An area use indication is used to indicate whether the first area is used in a forward direction or in a reverse direction.
  • the event reporting configuration information includes at least one of the following:
  • Target indication information where the target indication information is used to indicate whether the terminal needs to report an event outside the first area
  • a reporting policy where the reporting policy is used to indicate at least one constraint condition for a terminal to report an event.
  • the first processing module 1203 performs event reporting according to the event reporting configuration information, specifically for:
  • the event reporting configuration information includes the target indication information, and the target indication information indicates that the terminal does not need to report the event outside the first area, the event is not reported outside the first area;
  • the event reporting configuration information includes the target indication information and the reporting policy, and the target indication information indicates that the terminal needs to report an event outside the first area, the event is reported outside the first area according to the reporting policy;
  • the event reporting configuration information includes the target indication information, and the reporting configuration information does not include the reporting policy, and the target indication information indicates that the terminal needs to report an event outside the first area, no event reporting is performed outside the first area, or event reporting is performed outside the first area based on implementation;
  • the first information includes the reporting indication, and the reporting indication indicates that the event is not to be reported outside the first area, the event is not to be reported outside the first area;
  • the first information includes the reporting indication, and the reporting indication indicates that the event is reported outside the first area, and the event reporting configuration information includes the reporting policy, outside the first area, the event is reported according to the reporting policy;
  • the first information includes the reporting indication
  • the reporting indication indicates that the event is reported outside the first area
  • the event reporting configuration information does not include the reporting policy
  • the first information includes the reporting indication, and the reporting indication indicates the first level, and the event reporting configuration information does not include the reporting policy, no event reporting is performed outside the first area;
  • the first information includes the reporting indication
  • the reporting indication indicates the second level
  • the event reporting configuration information includes the reporting policy, outside the first area and within the second area, reporting the event according to the reporting policy
  • the first information includes the reporting indication
  • the reporting indication indicates the third level
  • the event reporting configuration information includes the reporting policy, outside the first area, reporting the event according to the reporting policy
  • the first information includes the reporting indication, and the reporting indication indicates the second level or the third level, and the event reporting configuration information does not include the reporting policy, event reporting is not performed outside the first area, or event reporting is performed outside the first area based on implementation.
  • the reporting strategy includes at least one of the following:
  • the triggering condition for event reporting wherein the triggering condition is used to indicate threshold information other than the minimum time interval and the maximum number of reporting times.
  • the first processing module 1203 reports the event according to the reporting strategy, specifically for:
  • Conditional event reporting is performed according to at least one of the maximum reporting times, the minimum time interval, and the trigger condition.
  • 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 of the candidate reporting policies in the policy set.
  • the device further comprises:
  • the third sending module is used to send third information when at least one item of information included in the first information changes, wherein the third information includes the changed information in the first information.
  • the device further comprises:
  • a second receiving module configured to receive fourth information, wherein the fourth information includes at least one of the first area and the event reporting configuration information, and the fourth information is determined according to the third information;
  • the second processing module is used to report an event according to the fourth information.
  • the first sending module is specifically configured to:
  • the target message includes at least one of the following:
  • the event reporting device in the embodiment of the present application can be an electronic device, such as an electronic device with an operating system, or a component in an electronic device, such as an integrated circuit or a chip.
  • the electronic device can be a terminal, and the terminal can include but is not limited to the types of terminals 11 listed above, which are not specifically limited in the embodiment of the present application.
  • the event reporting device provided in the embodiment of the present application can implement each process implemented by the method embodiment of Figure 4 and achieve the same technical effect. To avoid repetition, it will not be repeated here.
  • an embodiment of the present application provides an event reporting device, which can be applied to a first network side device.
  • the event reporting device 130 includes the following modules:
  • a first acquisition module 1301 is used to acquire first information of a terminal, wherein the first information is used to indicate relevant information of the terminal reporting an event outside a first area, and the first area is an area where the terminal is allowed to report an event;
  • a second acquisition module 1302 is used to acquire event reporting configuration information matching the first information
  • the second sending module 1303 is used to send the reporting configuration information to the terminal.
  • the first information includes at least one of the following:
  • a second area where the second area is used to indicate an area where the terminal expects to report an event
  • reporting indication is used to indicate whether the terminal supports event reporting outside the first area, or whether the terminal reports an event outside the first area, or indicates a level of event reporting by the terminal outside the first area;
  • An area use indication is used to indicate whether the first area is used in a forward direction or in a reverse direction.
  • the event reporting configuration information includes at least one of the following:
  • Target indication information where the target indication information is used to indicate whether the terminal needs to report an event outside the first area
  • a reporting policy where the reporting policy is used to indicate at least one constraint condition for a terminal to report an event.
  • the reporting strategy includes at least one of the following:
  • the triggering condition for event reporting wherein the triggering condition is used to indicate threshold information other than the minimum time interval and the maximum number of reporting times.
  • the second obtaining module 1302 is specifically configured to:
  • the reporting indication indicates that the terminal supports event reporting outside the first area, or indicates that the terminal reports events outside the first area, or indicates the second level or the third level, determining the event reporting configuration information according to the positioning service type and the subscription information related to positioning of the terminal;
  • the reporting indication indicates that the terminal supports event reporting outside the first area, or indicates that the terminal reports an event outside the first area, or indicates the second level or the third level, determining the event reporting configuration information according to the reporting policy received from the fourth network side device;
  • the first information also includes a policy set
  • the reporting indication indicates that the terminal supports event reporting outside the first area, or indicates that the terminal reports an event outside the first area, or indicates the second level or the third level
  • a candidate reporting strategy is selected from the policy set according to the positioning service type, and the event reporting configuration information is determined according to the selected candidate reporting strategy, wherein the The strategy set includes at least one candidate reporting strategy.
  • the process in which the second acquisition module 1302 receives the reporting policy sent by the fourth network side device includes:
  • a positioning service request sent by the fourth network side device is received, wherein the positioning service request carries a reporting strategy.
  • the second sending module 1303 is specifically configured to:
  • the event reporting configuration information is sent to the terminal through the third network side device and the fifth network side device.
  • the device further comprises:
  • the fourth sending module is configured to send second information to a fourth network side device, wherein the second information includes at least one of the following:
  • reporting indication is used to indicate whether the terminal supports event reporting outside the first area, or to indicate whether the terminal performs event reporting outside the first area;
  • an area use indication where the area use indication is used to indicate forward use of the first area or reverse use of the first area
  • Target area error cause wherein the target area error cause is used to indicate that there is no overlapping area between the target area and the second area or there is a logical error in the target area, the target area is the area where the terminal is expected to report an event, and the second area is used to indicate the area where the terminal is expected to report an event.
  • the first acquisition module 1301 is specifically used for:
  • the first information is acquired from a second network side device, wherein the first information stored in the second network side device is sent by the terminal to the second network side device via a third network side device.
  • the device further comprises:
  • the third acquisition module is used to obtain third information provided by the second network side device when the first network side device has subscribed to the information of the terminal, wherein the third information includes information that has changed in the first information, and the third information stored in the second network side device is sent by the terminal to the second network side device via the third network side device.
  • the device further comprises:
  • An updating module configured to update fourth information according to the third information, wherein the fourth information includes at least one of the first area and the event reporting configuration information;
  • the fifth sending module is used to send the updated fourth information to the terminal.
  • the event reporting device in the embodiment of the present application may be an electronic device, such as an electronic device with an operating system, or a component in an electronic device, such as an integrated circuit or a chip.
  • the electronic device may be a network side device.
  • the network side device may include but is not limited to the types of network side devices 12 listed above, and the embodiment of the present application does not specifically limit this.
  • the event reporting device provided in the embodiment of the present application can implement each process implemented by the method embodiment of Figure 7 and achieve the same technical effect. To avoid repetition, it will not be repeated here.
  • an embodiment of the present application provides an event reporting device, which can be applied to a fourth network side device.
  • the event reporting device may include the following modules:
  • the sixth sending module is used to send a reporting policy to the first network side device, wherein the reporting policy is used to indicate at least one constraint condition for the terminal to report an event.
  • the sixth sending module is specifically used to: send a positioning service request to the first network side device, wherein the positioning service request carries a reporting strategy.
  • the device further comprises:
  • the third receiving module is configured to receive second information sent by the first network side device, wherein the second information includes at least one of the following:
  • reporting indication is used to indicate whether the terminal supports event reporting outside the first area, or to indicate whether the terminal performs event reporting outside the first area;
  • an area use indication where the area use indication is used to indicate forward use of the first area or reverse use of the first area
  • Target area error cause wherein the target area error cause is used to indicate that there is no overlapping area between the target area and the second area or there is a logical error in the target area, the target area is the area where the terminal is expected to report an event, and the second area is used to indicate the area where the terminal is expected to report an event.
  • the event reporting device in the embodiment of the present application can be an electronic device, such as an electronic device with an operating system, or a component in an electronic device, such as an integrated circuit or a chip.
  • the electronic device can be a network side device.
  • the network side device can include but is not limited to the types of network side devices 12 listed above, and the embodiment of the present application does not specifically limit it.
  • the event reporting device provided in the embodiment of the present application can implement the various processes implemented by the method embodiment of the third aspect mentioned above and achieve the same technical effect. To avoid repetition, it will not be repeated here.
  • an embodiment of the present application further provides an event reporting device, which can be applied to a second network side device.
  • the event reporting device may include the following modules:
  • the fourth acquisition module is used to acquire first information of the terminal and store the first information.
  • the first providing module is used to provide the first information to the first network side device.
  • the first information includes at least one of the following:
  • a second area where the second area is used to indicate an area where the terminal expects to report an event
  • reporting indication is used to indicate whether the terminal supports event reporting outside the first area, or whether the terminal reports an event outside the first area, or indicates at least one level of event reporting by the terminal outside the first area;
  • An area use indication is used to indicate whether the first area is used in a forward direction or in a reverse direction.
  • the device further comprises:
  • a fourth receiving module configured to receive third information sent by the first terminal, and store the third information, wherein the third information includes information that has changed in the first information
  • the second providing module is used to provide the third information to the first network side device.
  • the event reporting device in the embodiment of the present application can be an electronic device, such as an electronic device with an operating system, or a component in an electronic device, such as an integrated circuit or a chip.
  • the electronic device can be a network side device, for example,
  • the network side device may include, but is not limited to, the types of network side devices 12 listed above, and the embodiments of the present application do not make specific limitations.
  • the event reporting device provided in the embodiment of the present application can implement the various processes implemented by the method embodiment of the fourth aspect mentioned above and achieve the same technical effect. To avoid repetition, it will not be repeated here.
  • the embodiment of the present application further provides a communication device 1400, including a processor 1401 and a memory 1402, and the memory 1402 stores a program or instruction that can be run on the processor 1401.
  • the communication device 1400 is a terminal
  • the program or instruction is executed by the processor 1401 to implement the various steps of the above-mentioned event reporting method embodiment, and can achieve the same technical effect.
  • the communication device 1400 is a network side device
  • the program or instruction is executed by the processor 1401 to implement the various steps of the above-mentioned event reporting method embodiment, and can achieve the same technical effect. To avoid repetition, it will not be repeated here.
  • the embodiment of the present application also provides a terminal, including a processor and a communication interface, the communication interface is coupled to the processor, and the processor is used to run a program or instruction to implement the steps in the method embodiment shown in Figure 4.
  • This terminal embodiment corresponds to the above-mentioned terminal side method embodiment, and each implementation process and implementation method of the above-mentioned method embodiment can be applied to the terminal embodiment and can achieve the same technical effect.
  • Figure 15 is a schematic diagram of the hardware structure of a terminal implementing an embodiment of the present application.
  • the terminal 1500 includes but is not limited to: 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 at least some of the components of the processor 1510.
  • the terminal 1500 may also include a power source (such as a battery) for supplying power to each component, and the power source may be logically connected to the processor 1510 through a power management system, so as to implement functions such as managing charging, discharging, and power consumption management through the power management system.
  • a power source such as a battery
  • the terminal structure shown in FIG15 does not constitute a limitation on the terminal, and the terminal may include more or fewer components than shown in the figure, or combine certain components, or arrange components differently, which will not be described in detail here.
  • the input unit 1504 may include a graphics processing unit (GPU) 15041 and a microphone 15042, and the graphics processor 15041 processes the image data of the static picture or video obtained by the image capture device (such as a camera) in the video capture mode or the image capture mode.
  • the display unit 1506 may include a display panel 15061, and the display panel 15061 may be configured in the form of a liquid crystal display, an organic light emitting diode, etc.
  • the user input unit 1507 includes a touch panel 15071 and at least one of other input devices 15072.
  • the touch panel 15071 is also called a touch screen.
  • the touch panel 15071 may include two parts: a touch detection device and a touch controller.
  • Other input devices 15072 may include, but are not limited to, a physical keyboard, function keys (such as a volume control key, a switch key, etc.), a trackball, a mouse, and a joystick, which will not be repeated here.
  • the radio frequency unit 1501 can transmit the data to the processor 1510 for processing; in addition, the radio frequency unit 1501 can send uplink data to the network side device.
  • the radio frequency unit 1501 includes but is not limited to an antenna, an amplifier, a transceiver, a coupler, a low noise amplifier, a duplexer, etc.
  • the memory 1509 can be used to store software programs or instructions and various data.
  • the memory 1509 can mainly include a first storage area 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 instruction required for at least one function (such as a sound playback function, an image playback function, etc.), etc.
  • the memory 1509 can include a volatile memory or a non-volatile memory 15.
  • the non-volatile memory can be a read-only memory (ROM), a programmable read-only memory (ROM), or a programmable read-only memory (ROM).
  • the volatile memory may be a random access memory (Random Access Memory, RAM), a static random access memory (Static RAM, SRAM), a dynamic random access memory (Dynamic RAM, DRAM), a synchronous dynamic random access memory (Synchronous DRAM, SDRAM), a double data rate synchronous dynamic random access memory (Double Data Rate SDRAM, DDRSDRAM), an enhanced synchronous dynamic random access memory (Enhanced SDRAM, ESDRAM), a synchronous connection dynamic random access memory (Synch link DRAM, SLDRAM) and a direct memory bus random access memory (Direct Rambus RAM, DRRAM).
  • RAM Random Access Memory
  • SRAM static random access memory
  • DRAM dynamic random access memory
  • DRAM synchronous dynamic random access memory
  • SDRAM double data rate synchronous dynamic random access memory
  • Enhanced SDRAM, ESDRAM enhanced synchronous dynamic random access memory
  • Synch link DRAM, SLDRAM synchronous connection dynamic random access memory
  • Direct Rambus RAM Direct Rambus RAM
  • the processor 1510 may include one or more processing units; optionally, the processor 1510 integrates an application processor and a modem processor, wherein the application processor mainly processes operations related to an operating system, a user interface, and application programs, and the modem processor mainly processes wireless communication signals, such as a baseband processor. It is understandable that the modem processor may not be integrated into the processor 1510.
  • the radio frequency unit 1501 is used for the terminal to send first information, wherein the first information is used to indicate relevant information that the terminal reports an event outside a first area, and the first area is an area where the terminal is allowed to report an event;
  • the radio frequency unit 1501 is further configured to receive event reporting configuration information matching the first information
  • the processor 1510 is configured to perform event reporting according to the event reporting configuration information.
  • the first information includes at least one of the following:
  • a second area where the second area is used to indicate an area where the terminal expects to report an event
  • reporting indication is used to indicate whether the terminal supports event reporting outside the first area, or whether the terminal reports an event outside the first area, or indicates at least one level of event reporting by the terminal outside the first area;
  • An area use indication is used to indicate whether the first area is used in a forward direction or in a reverse direction.
  • the event reporting configuration information includes at least one of the following:
  • Target indication information where the target indication information is used to indicate whether the terminal needs to report an event outside the first area
  • a reporting policy where the reporting policy is used to indicate at least one constraint condition for a terminal to report an event.
  • the processor 1510 performs event reporting according to the event reporting configuration information, including:
  • the event reporting configuration information includes the target indication information, and the target indication information indicates that the terminal does not need to report the event outside the first area, the event is not reported outside the first area;
  • the event reporting configuration information includes the target indication information and the reporting policy, and the target indication information indicates that the terminal needs to report an event outside the first area, the event is reported outside the first area according to the reporting policy;
  • the reporting configuration information does not include the reporting policy, and the target indication information indicates that the terminal needs to report an event outside the first area, no event reporting is performed outside the first area, or, based on the implementation of the event reporting configuration information, the terminal performs event reporting outside the first area. Report the incident;
  • the first information includes the reporting indication, and the reporting indication indicates that the event is not to be reported outside the first area, the event is not to be reported outside the first area;
  • the first information includes the reporting indication, and the reporting indication indicates that the event is reported outside the first area, and the event reporting configuration information includes the reporting policy, outside the first area, the event is reported according to the reporting policy;
  • the first information includes the reporting indication, and the reporting indication indicates that the event is reported outside the first area, and the event reporting configuration information does not include the reporting policy, the event is not reported outside the first area, or the event is reported outside the first area based on implementation;
  • the first information includes the reporting indication, and the reporting indication indicates the first level, and the event reporting configuration information does not include the reporting policy, no event reporting is performed outside the first area;
  • the first information includes the reporting indication
  • the reporting indication indicates the second level
  • the event reporting configuration information includes the reporting policy, outside the first area and within the second area, reporting the event according to the reporting policy
  • the first information includes the reporting indication
  • the reporting indication indicates the third level
  • the event reporting configuration information includes the reporting policy, outside the first area, reporting the event according to the reporting policy
  • the first information includes the reporting indication, and the reporting indication indicates the second level or the third level, and the event reporting configuration information does not include the reporting policy, event reporting is not performed outside the first area, or event reporting is performed outside the first area based on implementation.
  • the reporting strategy includes at least one of the following:
  • the triggering condition for event reporting wherein the triggering condition is used to indicate threshold information other than the minimum time interval and the maximum number of reporting times.
  • the processor 1510 reports the event according to the reporting strategy, including:
  • Conditional event reporting is performed according to at least one of the maximum reporting times, the minimum time interval, and the trigger condition.
  • 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 of the candidate reporting policies in the policy set.
  • the radio frequency unit 1501 is further configured to:
  • third information is sent, wherein the third information includes the changed information in the first information.
  • the radio frequency unit 1501 is further configured to:
  • the fourth information includes at least one of the first area and the event reporting configuration information, and the fourth information is determined according to the third information
  • the processor 1510 is further configured to report an event according to the fourth information.
  • the radio frequency unit 1501 sends the first information, including:
  • the target message includes at least one of the following:
  • the embodiment of the present application also provides a network side device, including a processor and a communication interface, the communication interface is coupled to the processor, and the processor is used to run a program or instruction to implement the steps of the method embodiment described in the second aspect, the third aspect, or the fourth aspect.
  • the network side device embodiment corresponds to the above network side device method embodiment, and each implementation process and implementation method of the above method embodiment can be applied to the network side device embodiment and can achieve the same technical effect.
  • the embodiment of the present application further provides a network side device.
  • the network side device 1600 includes: a processor 1601, a network interface 1602, and a memory 1603.
  • the network interface 1602 is, for example, a common public radio interface (CPRI).
  • CPRI common public radio interface
  • the network side device 1600 of an embodiment of the present invention also includes: instructions or programs stored in the memory 1603 and executable on the processor 1601.
  • the processor 1601 calls the instructions or programs in the memory 1603 to execute the method described in the second aspect, the third aspect, or the fourth aspect above and achieve the same technical effect. To avoid repetition, they will not be described here.
  • An embodiment of the present application also provides a readable storage medium, on which a program or instruction is stored.
  • a program or instruction is stored.
  • each process of the above-mentioned event reporting method embodiment is implemented, and the same technical effect can be achieved. To avoid repetition, it will not be repeated here.
  • the processor is the processor in the terminal described in the above embodiment.
  • the readable storage medium includes a computer readable storage medium, such as a computer read-only memory ROM, a random access memory RAM, a magnetic disk or an optical disk.
  • the readable storage medium may be a non-transient readable storage medium.
  • An embodiment of the present application further provides a chip, which includes a processor and a communication interface, wherein the communication interface is coupled to the processor, and the processor is used to run programs or instructions to implement the various processes of the above-mentioned event reporting method embodiment, and can achieve the same technical effect. To avoid repetition, it will not be repeated here.
  • the chip mentioned in the embodiments of the present application can also be called a system-level chip, a system chip, a chip system or a system-on-chip chip, etc.
  • the embodiment of the present application further provides a computer program/program product, which is stored in a storage medium, and is executed by at least one processor to implement the various processes of the above-mentioned event reporting method embodiment, and can achieve the same technical effect. To avoid repetition, it will not be repeated here.
  • An embodiment of the present application also provides a wireless communication system, including: a terminal and a first network side device, wherein the terminal can be used to execute the steps of the event reporting method described in the first aspect as described above, and the first network side device can be used to execute the steps of the event reporting method described in the second aspect as described above.
  • the wireless communication system also includes a fourth network side device and a second network side device, and the fourth network side device can be used to execute the steps of the event reporting method described in the third aspect as described above, and the second network side device can be used to execute the steps of the event reporting method described in the fourth aspect as described above.

Landscapes

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

Abstract

本申请公开了一种事件上报方法、装置、设备及存储介质，属于通信技术领域，本申请实施例的事件上报方法包括：终端发送第一信息，其中，所述第一信息用于指示所述终端在第一区域之外进行事件上报的相关信息，所述第一区域为允许所述终端进行事件上报的区域；所述终端接收与所述第一信息相匹配的事件上报配置信息；所述终端根据所述事件上报配置信息，进行事件上报。

Description

事件上报方法、装置、设备及存储介质
相关申请的交叉引用
本申请要求在2023年4月6日提交中国专利局、申请号为202310366782.X、名称为“事件上报方法、装置、设备及存储介质”的中国专利申请的优先权，其全部内容通过引用结合在本申请中。
技术领域
本申请属于通信技术领域，具体涉及一种事件上报方法、装置、设备及存储介质。
背景技术
在R18以前的定位中，第三方应用(LCS client)会请求网络侧满足某一事件要求(包括周期性、基于区域、基于运动)的时候，获取UE的事件报告(event report)。
目前，对于事件报告，R18中引入了event report allowed area，即UE可以上报一个区域表示UE只在该区域内上报自己的位置(该区域叫做Power saving area)，GMLC会根据Power saving area确定event report allowed area，一般是将细粒度的区域转变为粗粒度，比如将某个矩形区域(即坐标点组成的区域)转变为一个跟踪区(Tracking Area，TA)或小区(cell)列表。因此，目前event report allowed area的用法是：只有当UE处于event report allowed area，UE才会执行event report。
然而，UE在event report allowed area之外是否可以执行event report，目前并未给出可实现的方案。
发明内容
本申请实施例提供一种事件上报方法、装置、设备及存储介质，以给出终端在event report allowed area之外执行事件上报的方法。
第一方面，提供了一种事件上报方法，所述方法包括：
终端发送第一信息，其中，所述第一信息用于指示所述终端在第一区域之外进行事件上报的相关信息，所述第一区域为允许所述终端进行事件上报的区域；
所述终端接收与所述第一信息相匹配的事件上报配置信息；
所述终端根据所述事件上报配置信息，进行事件上报。
第二方面，提供了一种事件上报方法，所述方法包括：
第一网络侧设备获取终端的第一信息，其中，所述第一信息用于指示所述终端在第一区域之外进行事件上报的相关信息，所述第一区域为允许所述终端进行事件上报的区域；
所述第一网络侧设备获取与所述第一信息相匹配的事件上报配置信息；
所述第一网络侧设备发送所述上报配置信息给所述终端。
第三方面，提供了一种事件上报装置，包括：
第一发送模块，用于发送第一信息，其中，所述第一信息用于指示终端在第一区域之外进行事件上报的相关信息，所述第一区域为允许所述终端进行事件上报的区域；
第一接收模块，用于接收与所述第一信息相匹配的事件上报配置信息；
第一处理模块，用于根据所述事件上报配置信息，进行事件上报。
第四方面，提供了一种事件上报装置，包括：
第一获取模块，用于获取终端的第一信息，其中，所述第一信息用于指示所述终端 在第一区域之外进行事件上报的相关信息，所述第一区域为允许所述终端进行事件上报的区域；
第二获取模块，用于获取与所述第一信息相匹配的事件上报配置信息；
第二发送模块，用于发送所述上报配置信息给所述终端。
第五方面，提供了一种终端，该终端包括处理器和存储器，所述存储器存储可在所述处理器上运行的程序或指令，所述程序或指令被所述处理器执行时实现如第一方面所述的方法的步骤。
第六方面，提供了一种网络侧设备，该网络侧设备包括处理器和存储器，所述存储器存储可在所述处理器上运行的程序或指令，所述程序或指令被所述处理器执行时实现如第二方面所述的方法的步骤。
第七方面，提供了一种终端，包括处理器及通信接口，其中，通信接口用于发送第一信息，其中，所述第一信息用于指示所述终端在第一区域之外进行事件上报的相关信息，所述第一区域为允许所述终端进行事件上报的区域；
所述通信接口还用于接收与所述第一信息相匹配的事件上报配置信息；
所述处理器用于根据所述事件上报配置信息，进行事件上报。
第八方面，提供了一种网络侧设备，包括处理器及通信接口，其中，所述通信接口用于获取终端的第一信息，其中，所述第一信息用于指示所述终端在第一区域之外进行事件上报的相关信息，所述第一区域为允许所述终端进行事件上报的区域；
所述处理器用于获取与所述第一信息相匹配的事件上报配置信息；
所述通信接口还用于发送所述上报配置信息给所述终端。
第九方面，提供了一种可读存储介质，所述可读存储介质上存储程序或指令，所述程序或指令被处理器执行时实现如第一方面所述的方法的步骤，或者实现如第二方面所述的方法的步骤。
第十方面，提供了一种无线通信系统，包括：终端及网络侧设备，所述终端可用于执行如第一方面所述的方法的步骤，所述网络侧设备可用于执行如第二方面所述的方法的步骤。
第十一方面，提供了一种芯片，所述芯片包括处理器和通信接口，所述通信接口和所述处理器耦合，所述处理器用于运行程序或指令，实现如第一方面所述的方法，或实现如第二方面所述的方法。
第十二方面，提供了一种计算机程序/程序产品，所述计算机程序/程序产品被存储在存储介质中，所述程序/程序产品被至少一个处理器执行以实现如第一方面或第二方面所述的事件上报方法的步骤。
第十三方面，本申请实施例提供了一种事件上报装置，所述装置用于执行如第一方面或第二方面所述的事件上报方法的步骤。
在本申请实施例中，终端能够发送第一信息给第一网络侧设备，以使得第一网络侧设备获取与第一信息匹配的事件上报配置信息，从而将该事件上报配置信息发送给终端，这样，终端则可以根据事件上报配置信息进行事件上报，其中，第一信息用于指示终端在第一区域之外进行事件上报的相关信息，第一区域(即event report allowed area)为允许终端进行事件上报的区域。由此可知，在本申请实施例中，终端可以向第一网络侧设 备上报其在event report allowed area之外进行事件上报的相关信息(即第一信息)，以使得第一网络侧设备可以根据该相关信息为终端配置合适的事件上报配置信息，进而使得终端可以在event report allowed area之外实现更加合适的事件上报。因此，本申请的实施例，给出了终端在event report allowed area之外执行事件上报的方法。
附图说明
图1是本申请实施例可应用的一种无线通信系统的框图；
图2是实现定位服务的架构示意图；
图3是移动端终止定位请求(Mobile Terminated Location Request，MT-LR)流程示意图；
图4是本申请实施例中的一种事件上报方法的流程图；
图5是本申请实施例中基于power saving确定event report allowed area的示意图；
图6是本申请实施例中“正向使用”与“反向使用”的示意图；
图7是本申请实施例中的另一种事件上报方法的流程图；
图8是本申请实施例的事件上报方法的具体实施方式一的流程示意图；
图9是本申请实施例的事件上报方法的具体实施方式二的流程示意图；
图10是本申请实施例的事件上报方法的具体实施方式三的流程示意图；
图11是本申请实施例的事件上报方法的具体实施方式四的流程示意图；
图12是本申请实施例中的一种事件上报装置的结构框图；
图13是本申请实施例中的另一种事件上报装置的结构框图；
图14是本申请实施例中的一种通信设备的结构框图；
图15是本申请实施例中的一种终端的结构框图；
图16是本申请实施例中的一种网络侧设备的结构框图。
具体实施例
下面将结合本申请实施例中的附图，对本申请实施例中的技术方案进行清楚描述，显然，所描述的实施例是本申请一部分实施例，而不是全部的实施例。基于本申请中的实施例，本领域普通技术人员所获得的所有其他实施例，都属于本申请保护的范围。
本申请的术语“第一”、“第二”等是用于区别类似的对象，而不用于描述特定的顺序或先后次序。应该理解这样使用的术语在适当情况下可以互换，以便本申请的实施例能够以除了在这里图示或描述的那些以外的顺序实施，且“第一”、“第二”所区别的对象通常为一类，并不限定对象的个数，例如第一对象可以是一个，也可以是多个。此外，本申请中的“或”表示所连接对象的至少其中之一。例如“A或B”涵盖三种方案，即，方案一：包括A且不包括B；方案二：包括B且不包括A；方案三：既包括A又包括B。字符“/”一般表示前后关联对象是一种“或”的关系。
本申请的术语“指示”既可以是一个直接的指示(或者说显式的指示)，也可以是一个间接的指示(或者说隐含的指示)。其中，直接的指示可以理解为，发送方在发送的指示中明确告知了接收方具体的信息、需要执行的操作或请求结果等内容；间接的指示可以理解为，接收方根据发送方发送的指示确定对应的信息，或者进行判断并根据判断结果确定需要执行的操作或请求结果等。
值得指出的是，本申请实施例所描述的技术不限于长期演进型(Long Term Evolution， LTE)/LTE的演进(LTE-Advanced，LTE-A)系统，还可用于其他无线通信系统，诸如码分多址(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)或其他系统。本申请实施例中的术语“系统”和“网络”常被可互换地使用，所描述的技术既可用于以上提及的系统和无线电技术，也可用于其他系统和无线电技术。以下描述出于示例目的描述了新空口(New Radio，NR)系统，并且在以下大部分描述中使用NR术语，但是这些技术也可应用于NR系统以外的系统，如第6代(6th Generation，6G)通信系统。
图1示出本申请实施例可应用的一种无线通信系统的框图。无线通信系统包括终端11和网络侧设备12。其中，终端11可以是手机、平板电脑(Tablet Personal Computer)、膝上型电脑(Laptop Computer)、笔记本电脑、个人数字助理(Personal Digital Assistant，PDA)、掌上电脑、上网本、超级移动个人计算机(Ultra-mobile Personal Computer，UMPC)、移动上网装置(Mobile Internet Device，MID)、增强现实(Augmented Reality，AR)、虚拟现实(Virtual Reality，VR)设备、机器人、可穿戴式设备(Wearable Device)、飞行器(flight vehicle)、车载设备(Vehicle User Equipment，VUE)、船载设备、行人终端(Pedestrian User Equipment，PUE)、智能家居(具有无线通信功能的家居设备，如冰箱、电视、洗衣机或者家具等)、游戏机、个人计算机(Personal Computer，PC)、柜员机或者自助机等终端侧设备。可穿戴式设备包括：智能手表、智能手环、智能耳机、智能眼镜、智能首饰(智能手镯、智能手链、智能戒指、智能项链、智能脚镯、智能脚链等)、智能腕带、智能服装等。其中，车载设备也可以称为车载终端、车载控制器、车载模块、车载部件、车载芯片或车载单元等。需要说明的是，在本申请实施例并不限定终端11的具体类型。网络侧设备12可以包括接入网设备或核心网设备，其中，接入网设备也可以称为无线接入网(Radio Access Network,RAN)设备、无线接入网功能或无线接入网单元。接入网设备可以包括基站、无线局域网(Wireless Local Area Network，WLAN)接入点(Access Point，AS)或无线保真(Wireless Fidelity，WiFi)节点等。其中，基站可被称为节点B(Node B，NB)、演进节点B(Evolved Node B，eNB)、下一代节点B(the next generation Node B，gNB)、新空口节点B(New Radio Node B，NR Node B)、接入点、中继站(Relay Base Station，RBS)、服务基站(Serving Base Station，SBS)、基收发机站(Base Transceiver Station，BTS)、无线电基站、无线电收发机、基本服务集(Basic Service Set，BSS)、扩展服务集(Extended Service Set，ESS)、家用B节点(home Node B，HNB)、家用演进型B节点(home evolved Node B)、发送接收点(Transmission Reception Point，TRP)或所述领域中其他某个合适的术语，只要达到相同的技术效果，所述基站不限于特定技术词汇，需要说明的是，在本申请实施例中仅以NR系统中的基站为例进行介绍，并不限定基站的具体类型。
核心网设备可以包含核心网设备可以包含但不限于如下至少一项：核心网节点、核心网功能、移动管理实体(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)、本地NEF(Local NEF，或L-NEF)、绑定支持功能(Binding Support Function，BSF)、应用功能(Application Function，AF)等。需要说明的是，在本申请实施例中仅以NR系统中的核心网设备为例进行介绍，并不限定核心网设备的具体类型。但不限于如下至少一项：核心网节点、核心网功能、移动管理实体(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)、本地NEF(Local NEF，或L-NEF)、绑定支持功能(Binding Support Function，BSF)、应用功能(Application Function，AF)等。需要说明的是，在本申请实施例中仅以NR系统中的核心网设备为例进行介绍，并不限定核心网设备的具体类型。
为了便于理解本申请实施例的事件上报方法，现对如下相关技术进行介绍：
一、关于定位服务(Location Service，LCS)
如图2所示，定位服务是核心网中由AMF和定位服务功能(Location Management Function，LMF)等网元负责执行并提供的。LCS消息在UE和LCS实体(client)或者AF之间交互，一个比较典型的流程就是MT-LR流程。
其中，MT-LR流程由外部第三方应用(LCS client)或者由AF经由NEF网元发起，经由网关移动位置中心(Gateway Mobile Location Centre，GMLC)、AMF、LMF等网元，最终获取到UE的位置信息。
其中，图2中的N1、N2、N51、N33、N52、N8、NL1、NL2、NL5、NL6、NL7、Le分别表示不同的接口。
二、MT-LR流程
如图3所示，具体包括如下步骤31至331：
步骤31a：LCS clientc向归属地网关移动位置中心(Home Gateway Mobile Location Centre，H-GMLC)发送LCS服务请求(LCS Service Request)消息；
步骤31b-1：AF向NEF发送NEF网元的事件暴露签约请求消息(Nnef_EventExposure_Subscribe Request)；
步骤31b-2：NEF向H-GMLC发送GMLC网元的位置提供请求消息(Ngmlc_Location_ProvideLocation Request)；
即LCS client或者AF通过NEF接入H-GMLC，向LCS系统发起服务请求，请求周期性或者触发性的位置报告。在请求中，LCS client携带周期性或者触发性的位置报告的类别以及相关的参数。该类别包括UE可达性(availability)、区域(area)、周期性定位(periodic location)、运动(motion)。
其中，对于基于area的事件上报，LCS服务请求消息中携带：地理区域的详细信息，当UE进入、停留、离开该区域是否上报，上报的持续时间，两次成功上报的间隔，最大采样间隔，位置估计是否携带在上报消息中，是否需要一次或多次上报。如果目标区域表示为一个本地位置坐标或者一个地理名称，那么H-GMLC将目标区域转化为一个以形状表达的地理区域。
步骤32：H-GMLC与UDM交互UDM网元的签约数据管理请求消息(Nudm_SDM_Get)，即H-GMLC确认UE的隐私检查，通过向UDM获取UE隐私信息的更新来及时获取UE隐私信息的变化。
步骤33：H-GMLC与UDM交互UDM网元的UE上下文管理请求消息(Nudm_UECM_Get)，即H-GMLC向UDM获取AMF的地址。
步骤34：H-GMLC向漫游地网关移动位置中心(Visited Gateway Mobile Location Centre，V-GMLC)发送位置请求(Ngmlc_Location_ProvideLocation Request)，如果UE就在H-GMLC下，这一步可以跳过，。
步骤35.H-GMLC或者V-GMLC向serving AMF发起位置请求(例如V-GMLC向AMF发送AMF网元的位置提供请求消息(Namf_Location_ProvidePositioningInfo Request))。对于基于area的事件上报，目标地理区域被映射为cell或者TA标识的列表。
步骤36：AMF向V-GMLC发送AMF网元的位置提供响应消息(Namf_Location_ProvidePositioningInfo Response)；
步骤37：V-GMLC向H-GMLC发送GMLC网元的位置提供响应消息(Ngmlc_Location_ProvideLocation Response)；
步骤38a：H-GMLC向LCS Client发送LCS服务响应(LCS Service Response)；
步骤38b-1：H-GMLC向NEF发送GMLC网元的位置提供响应消息(Ngmlc_Location_ProvideLocation Response)；
步骤38b-2：NEF向AF发送NEF网元的事件暴露签约响应消息(Nnef_EventExposure_Subscribe Response)；
由上述步骤36-38可知，如果AMF支持上述周期性或者触发性的延迟位置上报，那么AMF返回确认给LCSclient或者AF。
步骤39：AMF等待UE可访问，即如果UE当前并不可达，例如使用拓展的非连续接收参数(Extended-Discontinuous Reception，eDRX)，AMF将会等待UE可达。
步骤310：AMF触发网络触发的服务请求(Network Triggered Service Request)，即直到UE可达，如果UE在空闲态(connection management-IDLE，CM-IDLE)态，则AMF启动网络触发的位置请求流程建立UE和网络侧信令连接。
步骤311:AMF给UE发送非接入层位置通知调用请求(NAS Location Notification Invoke Request)；
步骤312：UE给AMF发送非接入层位置通知返回结果(NAS Location Notification Return Result)；
即通过步骤311-312，AMF告知UE位置请求和相关隐私检查要求，周期性或者触发性的位置报告的类别等信息。
步骤313：AMF执行LMF选择过程，即选择一个LMF执行延迟位置请求任务。
步骤314：AMF向选择的LMF发送LMF网元的位置确认请求消息(Nlmf_Location_DetermineLocation Request)，即AMF向LMF发送请求消息，进行延迟位置的定位。对于所有类型的事件，此消息中会携带LCS关联标识、AMF标识、服务小区的标识、客户端(client)类型，可能携带指示信息用于指示：UE支持长期演进定位协议(long term evolution positioning protocol，LPP)消息、希望的定位服务质量(Quality of Service，QoS)和地理区域描述类型。
步骤315：UE定位，即LMF执行一个或多个定位流程，请求以及获取到UE的位置。
步骤316：LMF给UE发送定位的周期或触发的调用请求消息(LCS Periodic-Triggered Invoke Request)，即对于延迟位置上报，LMF会通过服务的AMF向UE发送一个补充的LCS周期性或触发性的请求，请求中携带步骤314中LMF从AMF获取到的位置请求消息，告知UE后续执行对应的延迟的周期性或者触发性的位置上报。
步骤317：UE向LMF发送定位的周期或触发的调用返回消息(LCS Periodic-Triggered Invoke Return)，即如果UE支持步骤316中的请求，则UE返回确认消息给LMF。
步骤318：LMF向AMF发送LMF网元的位置提供响应消息(Nlmf_Location_DetermineLocation Response)；
步骤319：AMF向V-GMLC发送AMF网元的位置事件通知消息(Namf_Location_EventNotify)；
步骤320：V-GMLC向H-GMLC发送GMLC网元的位置事件通知消息(Ngmlc_Location_EventNotify)；
步骤321a：H-GMLC向LCS Client发送定位服务响应(LCS Service Response)；
步骤321b-1：H-GMLC向NEF发送GMLC网元的位置事件通知消息(Ngmlc_Location_EventNotify)；
步骤321b-2：NEF向AF发送NEF网元的事件暴露通知消息(Nnef_EventExposure_Notify)；
即通过步骤318-21，如果UE支持请求，则LMF通过AMF、GMLC告知LCS client这一信息，其中，这一信息中可能包含UE定位能力等信息。
步骤322：检测到事件，即如果步骤316和317的周期或触发位置请求成功发生了，则UE监视步骤316中请求的事件的发生。对于area事件或motion事件，UE以等于或小于最大事件采样间隔的时间间隔进行监视。
其中，当发生以下任何情况时，UE会触发事件上报:
(1)已检测到请求的area事件或motion事件，并且自上次报告(如果这不是第一次事件报告)以来已经过了最小报告时间间隔；
(2)所要求的periodic事件发生了；
(3)area事件或motion事件的最大报告时间已过期。
当检测到事件触发，并且如果UE在步骤316中驻留或连接到LMF允许的访问类型，则UE将继续执行步骤323。如果UE不能访问允许的访问类型，UE可以跳过报告触发事件，或者根据步骤316从LMF接收到的要求，在允许的访问类型变得可用时报告触发事件。
步骤323.定位测量，即UE得到定位测量信息或者在步骤316请求或者允许的位置估计信息。
步骤324.UE发起UE触发的服务请求(UE Triggered Service Request)流程，即如果UE出处于CMM idle态，UE执行service request流程建立与AMF的N1信令连接。
步骤325.UE向LMF发送事件报告，即UE向LMF对应的AMF发送补充的事件上报消息，最终送达LMF，其中AMF透传这一消息。在这条消息可能携带事件类型以及携带位置估计信息的嵌入的LPP消息。
步骤326：LMF向UE发送事件报告确认，即LMF接受并且处理事件上报，LMF更新事件上报的状态(例如，迄今为止的上报次数，汇报持续时间等)，并且返回确认消息给UE。
步骤327：UE定位流程，即如果事件上报需要位置估计信息，那么LMF可能执行一次或多次定位流程。LMF使用测量信息和位置估计中的至少一项确定UE的位置，这里，时间戳信息也会被确定。
步骤328：LMF向V-GMLC发送Nlmf_Location_EventNotify；
步骤329：V-GMLC向H-GMLC发送Ngmlc_Location_EventNotify；
步骤330a：H-GMLC向LCS Client发送LCS Service Response；
步骤330b-1：H-GMLC向NEF发送Ngmlc_Location_EventNotify
步骤330b-2：NEF向AF发送Nnef_EventExposure_Notify；
即在步骤328-330中，LMF通过GMLC向LCS client执行事件上报，将UE位置上报给LCS client。
31.UE持续监控后续事件。
下面结合附图，通过一些实施例及其应用场景对本申请实施例提供的事件上报方法进行详细地说明。
第一方面，参见图1，本申请的实施例提供了一种事件上报方法，该方法可以包括如下步骤401至403：
步骤401：终端发送第一信息。
其中，所述第一信息用于指示所述终端在第一区域之外进行事件上报的相关信息，所述第一区域为允许所述终端进行事件上报的区域，即第一区域为前文所述的event report allowed area。可选地，终端在第一区域之外进行事件上报，具体可以为：终端在第一区域之外进行有条件地事件上报。这里，实现所述有条件地事件上报的约束条件可以为网络侧配置的上报策略指示的约束条件。
另外，在本申请实施例中，终端可以向网络侧上报Power saving area(用于指示终端在该区域内进行事件上报)，网络侧则可以根据Power saving area确定event report allowed area，一般是将细粒度的区域转变为粗粒度，比如将某个矩形区域转变为一个TA列表或cell列表，例如图5所示。
此外，上述第一信息用于指示终端在第一区域之外进行事件上报的相关信息，即第一信息用于指示终端在第一区域之外进行事件上报的相关参数信息、能力、是否上报的行为中的至少一项。
可选地，所述第一信息包括以下A-1至A-3项中至少一项：
A-1项：第二区域，所述第二区域用于指示所述终端期望进行事件上报的区域；
A-2项：上报指示(即Power saving class)，所述上报指示用于指示所述终端是否支持在所述第一区域之外进行事件上报，或者指示所述终端在所述第一区域之外是否进行事件上报，或者指示关于所述终端在所述第一区域之外进行事件上报的至少一个等级；
A-3项：区域使用指示(area usage indication)，所述区域使用指示用于指示正向使用所述第一区域，或反向使用所述第一区域。
其中，在A-1项中，上述第二区域即为Power saving area，其作为网络侧确定event report allowed area的依据。
对于A-2项，上报指示可以存在如下三种理解：
理解方式一：表示一种终端的能力，表征终端是否支持在第一区域之外进行事件上报。
理解方式二：指示终端在第一区域之外是否进行事件上报，即表示终端在第一区域之外执行事件上报的指示。在该理解方式下，具体实施方式可以为：上报指示存在两种取值，0表示不执行事件上报，1表示执行有条件地事件上报。
理解方式三：指示终端在第一区域之外进行事件上报的等级，即表示终端处于省电的级别。在该理解方式下，具体实施方式可以如下所述：
一种实施方式中，上报指示可以指示高(high)、低(low)两种级别，表征终端是否在第一区域外部执行事件上报，high表示不执行事件上报，low表示执行有条件地事件上报。
另一种实施方式，可以适用于基于area的事件上报，例如：上报指示可以指示第一等级(即高等级)、第二等级(即中等级)、第三等级(即低等级)；级别为第一等级时，终端只在第一区域内进行事件上报(即在第一区域之外不进行事件上报)；级别为第二等级时，终端需在第一区域内进行事件上报，在第一区域外且在第二区域内进行有条件地事件上报；级别为第三等级时，终端需在第一区域内进行事件上报，在第一区域外进行有条件地事件上报。
对于A-3项，如图6所示，正向使用时，A区域为内部(inside)区域，B区域为外部(outside)区域；而反向使用的时候，A区域则为outside区域，B区域为inside区域。因此，正向使用第一区域，即为第一区域之内作为inside区域，第一区域之外作为outside区域；反向使用第一区域，即为第一区域之外作为inside区域，第一区域之内作为outside区域。其中，可以通过区域使用指示的不同取值，表示第一区域的正向使用或反向使用，例如表1所示。默认情况是正向使用，即后文使用的第一区域之外可以理解为正向使用下的outside区域。
表1区域使用指示的示例
其中，正常情况下，终端往往在一定区域内进行事件上报。然而，对于长期活跃在固定区域的用户，为节约电量，没有必要做周期性事件上报，只有在离开某区域时进行事件上报才有价值，比如敬老院的老人常年在敬老院活动，走出敬老院之后上报位置防止走丢(老人手机)；幼儿园孩子在上课时间段离开学校范围，需上报位置至父母手机防止走丢(儿童手表)。因此，对于某些特殊的终端(例如老人手机、儿童手表等)，网络侧可以配置其反向使用第一区域，从而可以满足相应场景下的定位需求和省电需求。
需要说明的是，区域使用指示的一种实施方式是终端不提供该参数，由第一网络侧设备根据第四网络侧设备的类型、定位业务类型、终端与定位相关的签约信息等信息确定的。
可选地，步骤401“所述终端发送第一信息”，包括：
所述终端发送目标消息，所述目标消息携带有所述第一信息；
其中，所述目标消息包括以下B-1项至B-3项中至少一项：
B-1项：注册请求(registration request)消息；
B-2项：位置隐私设置请求消息；
B-3项：上行非接入层传输消息。
其中，终端可以发送第一信息给第三网络侧设备，从而由第三网络侧设备发送给第二网络侧设备，进而由第二网络侧设备向第一网络侧设备提供第一信息，进而由第一网络侧设备获取与第一信息匹配的事件上报配置信息，并发送给终端，这里，第一网络侧设备可以为GMLC，第二网络侧设备可以为UDM，第三网络侧设备可以为AMF。
对于B-1项，例如终端可以将第一信息携带在5G移动性管理(5GMobility Management，5GMM)能力信息中，并将该5GMM能力信息封装在注册请求消息中，从而将该registration request发送给AMF；或者，终端也可以将第一信息作为新IE封装在registration request消息中，从而将该registration request发送给AMF；
上述B-2项，表示终端可以通过终端位置隐私设置请求(UE Location Privacy Setting Request)消息将第一信息发送给AMF；
上述B-3项，表示终端也可以通过上行非接入层传输(UL NAS TRASPORT)消息将第一信息发送给AMF。
步骤402：所述终端接收与所述第一信息相匹配的事件上报配置信息。
其中，第一信息用于指示终端在第一区域之外进行事件上报的相关信息(即相关参数信息、能力、是否上报的行为中的至少一项)，因此，事件上报配置信息与第一信息相匹配，即为事件上报配置信息与终端在第一区域之外进行事件上报的相关参数信息、能力、是否上报的行为中的至少一项相匹配。
可选地，所述事件上报配置信息包括以下C-1至C-2项中至少一项：
C-1项：目标指示信息，所述目标指示信息用于指示所述终端在所述第一区域之外是否需要进行事件上报；
C-2项：上报策略，所述上报策略用于指示终端进行事件上报的至少一个约束条件。
对于C-1项，可以根据第一信息中的上报指示确定，其中，如果基于上述“理解方式一”理解上报指示，即该上报指示表征的是一种能力，那么，若该上报指示指示终端支持在第一区域之外进行事件上报，则目标指示信息指示终端在第一区域之外进行事件上报；若该上报指示指示终端不支持在第一区域之外进行事件上报，则目标指示信息指示终端在第一区域之外不进行事件上报。如果该上报指示是基于上述“理解方式二或三”，那么，则不需要根据该上报指示确定目标指示信息，即此种情况下，事件上报配置信息中不包括目标指示信息。
对于C-2项，用于指示终端实现有条件地事件上报的约束条件。其中，在第一信息中的上报指示指示终端支持在第一区域之外进行事件上报，或者指示终端在所述第一区域之外进行事件上报，或者指示上述第二等级或上述第三等级的情况下，表示终端需要进行有条件地事件上报，因此，此种情况下，事件上报配置信息中需要包括该上报策略，以指示终端该如何实现有条件地事件上报。
可选地，所述第一信息还包括策略集，其中，所述策略集包括至少一个候选的上报策略，所述事件上报配置信息中包括的上报策略，是根据所述策略集中的其中一个候选的上报策略确定的。
由此可知，终端可以给第一网络侧设备发送策略集(例如终端将策略集发送给第三网络侧设备，从而由第三网络侧设备发送给第二网络侧设备，进而由第二网络侧设备将策略集提供给第一网络侧设备)，这样，第一网络侧设备可以从该策略集中选择一个候选的上报策略，从而根据选择的该候选的上报策略，确定需要发送给终端的上报策略。
另外，第一网络侧也可以根据如下中至少一项信息，确定需要发送给终端的上报策略：
第四网络侧设备的类型(即请求定位业务的设备(例如LCS client/AF)的类型)；
定位业务类型(即deferred 5GC-MT-LR的类型(area或periodic或motion))；
终端与定位相关的签约信息；
第一区域；
第二区域；
上报指示；
区域使用指示。
或者，第四网络侧设备(即请求定位业务的设备)也可以在发送给第一网络侧设备的定位服务请求中携带上报策略，从而使得第一网络侧设备可以根据定位服务请求中携带的上报策略，确定需要发送给终端的上报策略。
步骤403：所述终端根据所述事件上报配置信息，进行事件上报。
其中，所述事件上报中包括终端的位置信息。因此，终端进行事件上报，可以将终端的位置信息上报给网络侧。
由上述步骤401至403可知，在本申请实施例中，终端能够发送第一信息给第一网络侧设备，以使得第一网络侧设备获取与第一信息匹配的事件上报配置信息，从而将该事件上报配置信息发送给终端，这样，终端则可以根据事件上报配置信息进行事件上报，其中，第一信息用于指示终端在第一区域之外进行事件上报的相关信息，第一区域(即 event report allowed area)为允许终端进行事件上报的区域。由此可知，在本申请实施例中，终端可以向第一网络侧设备上报其在event report allowed area之外进行事件上报的相关信息(即第一信息)，以使得第一网络侧设备可以根据该相关信息为终端配置合适的事件上报配置信息，进而使得终端可以在event report allowed area之外实现更加合适的事件上报。因此，本申请的实施例，给出了终端在event report allowed area之外执行事件上报的方法。
此外，在相关技术中终端支持处于event report allowed area内才进行事件上报，但当终端处于event report allowed area之外时，终端是否允许进行事件上报，以及如果允许，终端应该如何进行事件上报，相关技术中并未给出具体方案。
而且，对于在event report allowed area之外不进行事件上报，其问题在于当终端长时间不进行事件上报时，LCS client/AF可能会认为终端已经断开定位服务会话(LCS session)，从而导致取消定位流程。
下面进一步针对事件上报的不同类型，说明不进行事件上报的后果：
(1)基于area的事件上报：在这一类型中，LCS client/AF会提供一个目标区域(target area)，假如target area比event report allowed area大，这会导致在target area里且在event report allowed area之外，是搜集不到位置信息的，降低了定位数据的搜集数量和LCS client/AF的体验；
(2)基于Periodic的事件上报：在event report allowed area外，终端直接不会上报位置，会导致LCS client/AF认为终端不可达从而断开连接，影响一些商业服务的位置提供；
(3)基于motion的事件上报：假设event report allowed area区域较小，预先设定的直线移动距离可能离开了event report allowed area，则并不会触发上报，会导致上报信息减少。
而如果在event report allowed area之外可以有条件地进行事件上报，这样在一定程度上让LCS client/AF知道终端在event report allowed area之外的位置情况，并且依旧维持在LCS session(定位服务期间)；与此同时也兼顾了省电考虑。比如可以根据UE终端自身省电情况偶尔进行上报，或者降低上报频率，让网络侧知道终端的事件上报依旧活跃。
下面进一步针对事件上报的不同类型，说明在event report allowed area外，进行有条件地事件上报的好处：
(1)基于area的事件上报：在这一类型中，会允许终端在target area里且在event report allowed area之外上报位置，既满足了LCS client/AF搜集位置信息的需求，也考虑了终端的实际电量；
(2)基于Periodic的事件上报：在区域外，终端考虑自身电量进行有条件的上报，可以依旧保持一些商业服务的连接；
(3)基于motion的事件上报：假设event report allowed area区域较小，预先设定的直线移动距离可能离开了区域外，在这种情况下依旧会保持事件上报。
由此可知，在event report allowed area之外进行有条件地执行事件上报，可以兼顾定位服务的需求和终端省电的需求。
可选地，上述步骤403“所述终端根据所述事件上报配置信息，进行事件上报”，包括如下E-1至E-10中至少一项：
E-1项：在所述事件上报配置信息包括所述目标指示信息，且所述目标指示信息指示所述终端在所述第一区域之外不需要进行事件上报的情况下，所述终端在所述第一区域之外不进行事件上报；即上述上报指示基于上述“理解方式一”进行理解时，如果终端收到的目标指示信息指示在第一区域之外不需要进行事件上报，则终端处于第一区域之外时，不进行事件上报。
E-2项：在所述事件上报配置信息包括所述目标指示信息和所述上报策略，且所述目标指示信息指示所述终端在所述第一区域之外需要进行事件上报的情况下，所述终端在所述第一区域之外，根据所述上报策略进行事件上报；即上述上报指示基于上述“理解方式一”进行理解时，如果终端收到了目标指示信息和上报策略，且目标指示信息指示在第一区域之外需要进行事件上报，则终端处于第一区域之外时，根据上报策略进行有条件地事件上报。
E-3项：在所述事件上报配置信息包括所述目标指示信息，且所述上报配置信息不包括所述上报策略，且所述目标指示信息指示所述终端在所述第一区域之外需要进行事件上报的情况下，所述终端在所述第一区域之外不进行事件上报，或者，所述终端在所述第一区域之外基于实现进行事件上报；即上述上报指示基于上述“理解方式一”进行理解时，如果终端收到了目标指示信息，但未收到上报策略，且目标指示信息指示在第一区域之外需要进行事件上报，则终端处于第一区域之外时，可以不进行事件上报，也可以根据终端的实际情况进行事件上报。
E-4项：在所述第一信息包括所述上报指示，且所述上报指示指示在所述第一区域之外不进行事件上报的情况下，所述终端在所述第一区域之外不进行事件上报；即上述上报指示基于上述“理解方式二”进行理解时，如果该上报指示指示在第一区域之外不进行事件上报，那么网络侧可以不给终端发送上报策略，这样，终端处于第一区域之外时，不进行事件上报。
E-5项：在所述第一信息包括所述上报指示，且所述上报指示指示在所述第一区域之外进行事件上报，且所述事件上报配置信息包括所述上报策略的情况下，所述终端在所述第一区域之外，根据所述上报策略进行事件上报；即上述上报指示基于上述“理解方式二”进行理解时，如果该上报指示指示在第一区域之外进行事件上报，那么网络侧可以给终端发送上报策略，这样，终端处于第一区域之外时，则可以根据上报策略进行有条件地事件上报。
E-6项：在所述第一信息包括所述上报指示，且所述上报指示指示在所述第一区域之外进行事件上报，且所述事件上报配置信息不包括所述上报策略的情况下，所述终端在所述第一区域之外不进行事件上报，或者，所述终端在所述第一区域之外基于实现进行事件上报；即上述上报指示基于上述“理解方式二”进行理解时，如果该上报指示指示在第一区域之外进行事件上报，那么网络侧也可以不给终端发送上报策略，这样，终端处于第一区域之外时，可以不进行事件上报，也可以根据终端的实际情况进行事件上报。
E-7项：在所述第一信息包括所述上报指示，且所述上报指示指示第一等级，且所述事件上报配置信息不包括所述上报策略的情况下，所述终端在所述第一区域之外不进行 事件上报；即上述上报指示基于上述“理解方式三”进行理解时，第一等级表征终端在第一区域之外不进行事件上报(即第一等级是“终端在第一区域之外不进行事件上报”的一种隐式指示)，则上报指示指示第一等级时，网络侧可以不给终端发送上报策略，这样，终端处于第一区域之外时，可以不进行事件上报。
E-8项：在所述第一信息包括所述上报指示，且所述上报指示指示第二等级，且所述事件上报配置信息包括所述上报策略的情况下，所述终端在所述第一区域之外且在所述第二区域之内，根据所述上报策略进行事件上报；即上述上报指示基于上述“理解方式三”进行理解时，第二等级表征终端在第一区域之且在第二区域之内进行有条件地事件上报(即第二等级是“终端在第一区域之外且第二区域之内进行有条件地事件上报”的一种隐式指示)，则上报指示指示第二等级时，网络侧可以给终端发送上报策略，这样，终端处于第一区域之外且第二区域之内时，可以根据上报策略进行有条件地事件上报。
E-9项：在所述第一信息包括所述上报指示，且所述上报指示指示第三等级，且所述事件上报配置信息包括所述上报策略的情况下，所述终端在所述第一区域之外，根据与所述上报策略进行事件上报；即上述上报指示基于上述“理解方式三”进行理解时，第三等级表征终端在第一区域之进行有条件地事件上报(即第三等级是“终端在第一区域之外进行有条件地事件上报”的一种隐式指示)，则上报指示指示第三等级时，网络侧可以给终端发送上报策略，这样，终端处于第一区域之外时，可以根据上报策略，进行有条件地事件上报。
E-10项：在所述第一信息包括所述上报指示，且所述上报指示指示所述第二等级或所述第三等级，且所述事件上报配置信息不包括所述上报策略的情况下，所述终端在所述第一区域之外不进行事件上报，或者，所述终端在所述第一区域之外基于实现进行事件上报。即上述上报指示基于上述“理解方式三”进行理解时，如果上报指示指示上述第二等级或上述第三等级，那么网络侧也可以不给终端发送上报策略，这样，终端处于第一区域之外时，可以不进行事件上报，也可以根据终端的实际情况进行事件上报。
可选地，所述上报策略包括以下D-1至D-3项中至少一项：
D-1项：事件上报的最多上报次数；
D-2项：相邻两次事件上报的最小时间间隔；
D-3项：事件上报的触发条件，其中，所述触发条件用于指示除所述最小时间间隔、所述最多上报次数之外的门限信息。
其中，D-1项用于指示终端进行有条件地事件上报时，上报次数不能超过所述最多上报次数，例如终端在第一区域之外进行有条件地事件上报时，在第一区域之外的事件上报次数达到所述最多上报次数之后，则不再继续在第一区域之外进行事件上报。
D-2项用于指示终端进行有条件地事件上报时，相邻两次事件上报的事件间隔不能超过所述最小时间间隔。
D-3项表示实现有条件地事件上报的其他约束条件，例如只有移动直线距离达到100m才进行事件上报。
可选地，所述终端根据所述上报策略进行事件上报，包括：
所述终端根据所述最多上报次数、所述最小时间间隔、所述触发条件中的至少一项，执行有条件地事件上报。
例如上报策略包括所述最多上报次数(x)、所述最小时间间隔(t)、所述触发条件(F条件)，则终端在第一区域之外根据该上报策略进行有条件地时间上报，即为：终端在第一区域之外，在检测到F条件的情况下，按照t进行事件上报，并在上报次数达到x时，停止上报；相较于第一区域之内的上报参数，在第一区域之外上报的约束条件更加苛刻，比如，更少的最多上报次数，更长的最短上报间隔，更长的只限移动距离等。
可选地，所述方法还包括：
在所述第一信息中包括的至少一项信息发生变化的情况下，所述终端发送第三信息，其中，所述第三信息包括所述第一信息中发生变化的信息。
由此可知，在“第二区域、上报指示、区域使用指示、策略集”中至少一项信息发生变化的情况下，终端可以将发生变化的信息发送给第一网络侧设备。
其中，终端发送上述第三信息的方式，与前文所述的终端发送第一信息的方式相同，即终端将第三信息发送给第三网络侧设备，从而由第三网络侧设备发送给第二网络侧设备，进而由第二网络侧设备将第三信息提供给第一网络侧设备。
可选地，所述方法还包括：
所述终端接收第四信息，其中，所述第四信息包括所述第一区域和所述事件上报配置信息中的至少一项，所述第四信息是根据所述第三信息确定的；
所述终端根据所述第四信息，进行事件上报。
由此可知，在终端的“第二区域、上报指示、区域使用指示、策略集”中至少一项信息发生变化的情况下，第一网络侧设备可以进一步基于变化后的信息，对所述第一区域和事件上报配置信息(包括目标指示信息、上报策略中的至少一项)进行更新，从而将更新后的信息(即第四信息)发送给终端，以使得终端可以根据该第四信息进行事件上报，这样，使得事件上报情况能够符合终端的实际情况。
其中，第一网络侧设备可以将第四信息发送给第三网络侧设备，从而由第三网络侧设备发送给第五网络侧设备(例如LMF)，进而由第五网络侧设备发送给终端。
第二方面，如图7所示，本申请实施例还提供了一种事件上报方法，可以包括如下步骤701至703：
步骤701：第一网络侧设备获取终端的第一信息。
其中，所述第一信息用于指示所述终端在第一区域之外进行事件上报的相关信息，所述第一区域为允许所述终端进行事件上报的区域，即第一区域为前文所述的event report allowed area。可选地，终端在第一区域之外进行事件上报，具体可以为：终端在第一区域之外进行有条件地事件上报。这里，实现所述有条件地事件上报的约束条件可以为网络侧配置的上报策略指示的约束条件。
另外，在本申请实施例中，终端可以向网络侧上报Power saving area(用于指示终端在该区域内进行事件上报)，网络侧则可以根据Power saving area确定event report allowed area，一般是将细粒度的区域转变为粗粒度，比如将某个矩形区域转变为一个TA列表或cell列表，例如图5所示。
此外，上述第一信息用于指示终端在第一区域之外进行事件上报的相关信息，即第一信息用于指示终端在第一区域之外进行事件上报的相关参数信息、能力、是否上报的 行为中的至少一项。
可选地，所述第一信息包括以下A-1至A-3项中至少一项：
A-1项：第二区域，所述第二区域用于指示所述终端期望进行事件上报的区域；
A-2项：上报指示(即Power saving class)，所述上报指示用于指示所述终端是否支持在所述第一区域之外进行事件上报，或者指示所述终端在所述第一区域之外是否进行事件上报，或者指示关于所述终端在所述第一区域之外进行事件上报的至少一个等级；
A-3项：区域使用指示(area usage indication)，所述区域使用指示用于指示正向使用所述第一区域，或反向使用所述第一区域。
其中，对于上述A-1至A-3项的具体解释可参见前文所述，此处不再赘述。
可选地，步骤“701所述第一网络侧设备获取终端的第一信息”，包括：
所述第一网络侧设备从第二网络侧设备中获取所述第一信息，其中，所述第二网络侧设备中存储的所述第一信息是所述终端通过第三网络侧设备发送给所述第二网络侧设备的。
由此可知，终端可以发送第一信息给第三网络侧设备，从而由第三网络侧设备发送给第二网络侧设备，进而由第二网络侧设备向第一网络侧设备提供第一信息，这里，第一网络侧设备可以为GMLC，第二网络侧设备可以为UDM，第三网络侧设备可以为AMF。
步骤702：所述第一网络侧设备获取与所述第一信息相匹配的事件上报配置信息。
其中，第一信息用于指示终端在第一区域之外进行事件上报的相关信息(即相关参数信息、能力、是否上报的行为中的至少一项)，因此，事件上报配置信息与第一信息相匹配，即为事件上报配置信息与终端在第一区域之外进行事件上报的相关参数信息、能力、是否上报的行为中的至少一项相匹配。
可选地，所述事件上报配置信息包括以下C-1至C-2项中至少一项：
C-1项：目标指示信息，所述目标指示信息用于指示所述终端在所述第一区域之外是否需要进行事件上报；
C-2项：上报策略，所述上报策略用于指示终端进行事件上报的至少一个约束条件。
其中，对于上述C-1至C-2项的具体解释可参见前文所述，此处不再赘述。
步骤703：所述第一网络侧设备发送所述上报配置信息给所述终端。
可选地，步骤703“所述第一网络侧设备发送所述事件上报配置信息给所述终端”，包括：
所述第一网络侧设备通过第三网络侧设备和第五网络侧设备，将所述事件上报配置信息发送给所述终端。
其中，第三网络侧设备可以为AMF，第五网络侧设备可以为LMF。
由此可知，第一网络侧设备可以将上报配置信息发送给第三网络侧设备，从而由第三网络侧设备将上报配置信息发送给第五网络侧设备，进而由LMF第五网络侧设备将上报配置信息发送给终端。
由上述步骤701至703可知，在本申请实施例中，终端能够发送第一信息给第一网络侧设备，以使得第一网络侧设备获取与第一信息匹配的事件上报配置信息，从而将该事件上报配置信息发送给终端，这样，终端则可以根据事件上报配置信息进行事件上报，其中，第一信息用于指示终端在第一区域之外进行事件上报的相关信息，第一区域(即 event report allowed area)为允许终端进行事件上报的区域。由此可知，在本申请实施例中，终端可以向第一网络侧设备上报其在event report allowed area之外进行事件上报的相关信息(即第一信息)，以使得第一网络侧设备可以根据该相关信息为终端配置合适的事件上报配置信息，进而使得终端可以在event report allowed area之外实现更加合适的事件上报。因此，本申请的实施例，给出了终端在event report allowed area之外执行事件上报的方法。
可选地，所述上报策略包括以下D-1至D-3项中至少一项：
D-1项：事件上报的最多上报次数；
D-2项：相邻两次事件上报的最小时间间隔；
D-3项：事件上报的触发条件，其中，所述触发条件用于指示除所述最小时间间隔、所述最多上报次数之外的门限信息。
其中，对于上述D-1至D-2项的具体解释可参见前文所述，此处不再赘述。
可选地，在所述事件上报配置信息中包括所述上报策略的情况下，所述第一网络侧设备获取与所述第一信息相匹配的事件上报配置信息，包括如下F-1至F-2中其中一项：
F-1项：在上报指示指示所述终端支持在所述第一区域之外进行事件上报，或者指示所述终端在所述第一区域之外进行事件上报，或者指示第二等级或第三等级的情况下，所述第一网络侧设备根据定位业务类型和所述终端与定位相关的签约信息，确定所述事件上报配置信息(即确定事件上报配置信息中包括的上报策略)；
在F-1项中，进一步地，第一网络侧设备还可以结合第一区域、第二区域、上报指示、区域使用指示，与定位业务类型和终端与定位相关的签约信息，确定需要发送给终端的上报策略。
即一种实施方式中，第一网络侧可以根据如下中至少一项信息，确定需要发送给终端的上报策略：
第四网络侧设备的类型(即请求定位业务的设备(例如LCS client/AF)的类型)；
定位业务类型(即deferred 5GC-MT-LR的类型(area或periodic或motion))；
终端与定位相关的签约信息；
第一区域；
第二区域；
上报指示；
区域使用指示。
F-2项：在所述上报指示指示所述终端支持在所述第一区域之外进行事件上报，或者指示所述终端在所述第一区域之外进行事件上报，或者指示所述第二等级或所述第三等级的情况下，所述第一网络侧设备根据从第四网络侧设备中接收到的上报策略，确定所述事件上报配置信息(即确定事件上报配置信息中包括的上报策略)；
由此可知，第四网络侧设备(即请求定位业务的设备)也可以给第一网络侧设备发送上报策略，从而使得第一网络侧设备可以根据第四网络侧设备发送的上报策略，确定需要发送给终端的上报策略。
这里，可选地，所述第一网络侧设备接收所述第四网络侧设备发送的上报策略的过程，包括：所述第一网络侧设备接收所述第四网络侧设备发送的定位服务请求，其中， 所述定位服务请求中携带有上报策略。
即第四网络侧设备可以将需要发送给第一网络侧设备的上报策略，携带在定位服务请求中。
F-3项：在所述第一信息还包括策略集，且所述上报指示指示所述终端支持在所述第一区域之外进行事件上报，或者指示所述终端在所述第一区域之外进行事件上报，或者指示所述第二等级或所述第三等级的情况下，所述第一网络侧设备根据定位业务类型，从所述策略集中选择一个候选的上报策略，并根据选出的候选的上报策略，确定所述事件上报配置信息(即确定事件上报配置信息中包括的上报策略)，其中，所述策略集包括至少一个候选的上报策略。
由F-3项可知，终端可以给第一网络侧设备发送策略集(例如终端将策略集发送给第三网络侧设备，从而由第三网络侧设备发送给第二网络侧设备，进而由第二网络侧设备将策略集提供给第一网络侧设备)，这样，第一网络侧设备可以从该策略集中选择一个候选的上报策略，从而根据选择的该候选的上报策略，确定需要发送给终端的上报策略。
这里，第一网络侧设备从策略集中选择一个候选的上报策略时，除了考虑定位业务类型之外，还可以进一步结合终端的与定位相关的签约信息。
其中，第一网络侧设备可以将从策略集中选出的候选的上报策略，作为需要发送给终端的上报策略，也可以从该候选的上报策略中选出部分约束条件，作为需要发送给终端的上报策略的约束条件。
此外，当上报配置信息包括目标指示信息时，第一网络侧设备根据上报指示确定目标指示信息，即如果基于上述“理解方式一”理解上报指示，即该上报指示表征的是一种能力，那么，若该上报指示指示终端支持在第一区域之外进行事件上报，则目标指示信息指示终端在第一区域之外进行事件上报；若该上报指示指示终端不支持在第一区域之外进行事件上报，则目标指示信息指示终端在第一区域之外不进行事件上报。如果该上报指示是基于上述“理解方式二或三”，那么，则不需要根据该上报指示确定目标指示信息，即此种情况下，事件上报配置信息中不包括目标指示信息。
可选地，所述方法还包括：
所述第一网络侧设备发送第二信息给第四网络侧设备，其中，所述第二信息包括以下G-1项至G-5项中至少一项：
G-1项：所述第一区域；
G-2项：上报指示，所述上报指示用于指示所述终端是否支持在所述第一区域之外进行事件上报，或者指示所述终端在所述第一区域之外是否进行事件上报；
G-3项：所述事件上报配置信息(可以包括上述目标指示信息、上报策略中的至少一项)；
G-4项：区域使用指示，所述区域使用指示用于指示正向使用所述第一区域，或反向使用所述第一区域；
G-5项：目标区域错误原因(Target area error indication)，其中，所述目标区域错误原因用于指示目标区域(Target area)与第二区域(Power saving area)之间无重合区域或者所述目标区域存在逻辑错误，所述目标区域为期望所述终端进行事件上报的区域 (即网络侧期望终端进行事件上报的区域，例如在定位服务请求中可以包括一个区域希望获取终端在该区域的位置信息，该区域即为target area)，所述第二区域用于指示所述终端期望进行事件上报的区域。
其中，关于G-1项至G-4项的相关解释可参见前文所述，此处不再赘述。
另外，对于G-5项，只适用于定位业务请求的类型是基于area的事件上报，其中，目标区域错误原因可以理解为一种拒绝定位服务请求消息的拒绝消息中的理由，表征LCS定位服务器请求消息所请求的Target area有误，比如Target area与Power saving area的区域无重合区域或者有逻辑错误，需要对Target area进行修正。例如：Power saving area为A地区，但是Target area为该A地区所属的国家，此时在基于area的事件上报中，如果用户从未出过该国家，则永久不会触发离开(leaving)或者进入(enter)的类型上报，并且用户需要在该国境内一直上报位置，那么则认为这里的Target area太大，属于有逻辑错误。
可以理解的是，目标区域错误原因也可以用于指示目标区域与第一区域(即event report allowed area)之间无重合区域。
此外，如果第四网络侧设备接收到了目标区域错误原因，指示目标区域有误，则第四网络侧设备可以重新发起一个定位服务请求，该请求中携带有重新确定的目标区域。
可选地，所述方法还包括：
在所述第一网络侧设备订阅了所述终端的信息的情况下，所述第一网络侧设备获取第二网络侧设备提供的第三信息，其中，所述第三信息包括所述第一信息中发生变化的信息，所述第二网络侧设备中存储的所述第三信息是所述终端通过第三网络侧设备发送给所述第二网络侧设备的。
由此可知，在“第二区域、上报指示、区域使用指示、策略集”中至少一项信息发生变化的情况下，终端可以将发生变化的信息(即第三信息)发送给第二网络侧设备，其中，如果第一网络侧设备在第二网络侧设备中订阅了终端的信息，则第二网络侧设备接收到第三信息之后，可以提供给第一网络侧设备。
可选地，所述方法还包括：
所述第一网络侧设备根据所述第三信息更新第四信息，其中，所述第四信息包括所述第一区域和所述事件上报配置信息中的至少一项；
所述第一网络侧设备将更新后的所述第四信息发送给所述终端。
由此可知，在终端的“第二区域、上报指示、区域使用指示、策略集”中至少一项信息发生变化的情况下，第一网络侧设备可以进一步基于变化后的信息，对所述第一区域和事件上报配置信息(包括目标指示信息、上报策略中的至少一项)进行更新，从而将更新后的信息(即第四信息)发送给终端，以使得终端可以根据该第四信息进行事件上报，这样，使得事件上报情况能够符合终端的实际情况。
其中，第一网络侧设备可以将第四信息发送给第三网络侧设备，从而由第三网络侧设备发送给第五网络侧设备(例如LMF)，进而由第五网络侧设备发送给终端。
另外，进一步地，第一网络侧设备还可以在第三信息的基础上，进一步结合所述目标区域、当前使用的第一区域、当前使用的上报策略和当前报告状态(即report status，例如迄今为止的上报次数，汇报持续时间等)，来确定上述第四信息。
第三方面，本申请的实施例还提供了一种事件上报方法，包括如下步骤H-1：
步骤H-1：第四网络侧设备发送上报策略给第一网络侧设备，其中，所述上报策略用于指示终端进行事件上报的至少一个约束条件。
这里，第四网络侧设备可以为LCS client/AF。
其中，第一网络侧设备可以根据第四网络侧设备发送的上报策略，确定需要发送给终端的上报策略。
可选地，步骤H-1“所述第四网络侧设备发送上报策略给第一网络侧设备”，包括：
所述第四网络侧设备发送定位服务请求给所述第一网络侧设备，其中，所述定位服务请求中携带有上报策略。
由此可知，第四网络侧设备(即请求定位业务的设备)也可以在发送给第一网络侧设备的定位服务请求中携带上报策略，从而使得第一网络侧设备可以根据定位服务请求中携带的上报策略，确定需要发送给终端的上报策略。
可选地，所述方法还包括：
所述第四网络侧设备接收所述第一网络侧设备发送的第二信息，其中，所述第二信息包括以下G-1项至G-5项中至少一项：
G-1项：所述第一区域；
G-2项：上报指示，所述上报指示用于指示所述终端是否支持在所述第一区域之外进行事件上报，或者指示所述终端在所述第一区域之外是否进行事件上报；
G-3项：所述事件上报配置信息(可以包括上述目标指示信息、上报策略中的至少一项)；
G-4项：区域使用指示，所述区域使用指示用于指示正向使用所述第一区域，或反向使用所述第一区域；
G-5项：目标区域错误原因(Target area error indication)，其中，所述目标区域错误原因用于指示目标区域(Target area)与第二区域(Power saving area)之间无重合区域或者所述目标区域存在逻辑错误，所述目标区域为期望所述终端进行事件上报的区域(即网络侧期望终端进行事件上报的区域，例如在定位服务请求中可以包括一个区域希望获取终端在该区域的位置信息，该区域即为target area)，所述第二区域用于指示所述终端期望进行事件上报的区域。
其中，关于G-1项至G-5项的相关解释可参见前文所述，此处不再赘述。
此外，如果第四网络侧设备接收到了目标区域错误原因，则第四网络侧设备可以重新发起一个定位服务请求，该请求中携带有重新确定的目标区域。
第四方面，本申请的实施例还提供了一种事件上报方法，包括如下步骤K-1至K-2：
步骤K-1：第二网络侧设备获取终端的第一信息，并存储所述第一信息。
其中，所述第一信息用于指示所述终端在第一区域之外进行事件上报的相关信息，所述第一区域为允许所述终端进行事件上报的区域。
另外，第二网络侧设备可以通过第三网络侧设备接收终端发送的第一信息。
步骤K-2：所述第二网络侧设备向第一网络侧设备提供所述第一信息。
可选地，所述第二网络侧设备获取终端的第一信息，包括：
所述第二网络侧设备通过第三网络侧设备，接收所述终端发送的所述第一信息。
这里，第二网络侧设可以为UDM，第三网络侧设备可以为AMF，第一网络侧设备可以为GMLC。
其中，第一网络侧设备获取到第一信息后，可以获取与第一信息相匹配的事件上报配置信息，从而将事件上报配置信息发送给终端，以使得终端根据该事件上报配置信息进行事件上报。
可选地，所述第一信息包括以下A-1至A-3项中至少一项：
A-1项：第二区域，所述第二区域用于指示所述终端期望进行事件上报的区域；
A-2项：上报指示(即Power saving class)，所述上报指示用于指示所述终端是否支持在所述第一区域之外进行事件上报，或者指示所述终端在所述第一区域之外是否进行事件上报，或者指示关于所述终端在所述第一区域之外进行事件上报的至少一个等级；
A-3项：区域使用指示(area usage indication)，所述区域使用指示用于指示正向使用所述第一区域，或反向使用所述第一区域。
其中，对于上述A-1至A-3项的具体解释可参见前文所述，此处不再赘述。
可选地，所述第一信息中还包括策略集，所述策略集包括至少一个候选的上报策略。
可选地，所述方法还包括：
所述第二网络侧设备接收所述第一终端发送的第三信息，并存储所述第三信息，其中，所述第三信息包括所述第一信息中发生变化的信息；
所述第二网络侧设备向所述第一网络侧设备提供所述第三信息。
由此可知，在“第二区域、上报指示、区域使用指示、策略集”中至少一项信息发生变化的情况下，终端可以将发生变化的信息(即第三信息)发送给第二网络侧设备，其中，如果第一网络侧设备在第二网络侧设备中订阅了终端的信息，则第二网络侧设备接收到第三信息之后，可以提供给第一网络侧设备。
综上所述，本申请实施例的事件上报方法的具体实施方式可如下实施方式一至四所述：
实施方式一：如图8所示，包括如下步骤81至819：
步骤81：终端向AMF发送NAS信令，该NAS信令中携带有第一信息，该第一信息包括以下(1)至(5)项中至少一项：
(1)UE ID(即终端标识)；
(2)消息类型；
(3)Power saving area(即第二区域，即使用坐标或者TA/cell表示的区域，用于描述终端处于省电状态时在该区域内执行event report)；
(4)Power saving class(即上报指示)；这里，Power saving class可以存在如下三种理解方式：
理解方式一：表示一种终端的能力，表征终端是否支持在event report allowed area(即第一区域)之外进行事件上报；一种实施方式中，上报指示包括以下两种全局互斥设置，一种是终端支持在event report allowed area之外进行事件上报，另一种是终端不支持在event report allowed area之外进行事件上报，后者是默认设置。
理解方式二：指示终端在event report allowed area之外是否进行事件上报即表示终端在event report allowed area之外执行event report的指示。
理解方式三：指示终端在event report allowed area之外进行事件上报的等级，即表示终端处于省电的级别。
其中，对于上述理解方式二，具体实施方式可如下所述：
一种实施方式中，Power saving class存在两种取值，0表示不执行，1表示有条件地执行。
对于上述理解方式三，具体实施方式可以如下所述：
一种实施方式中，Power saving class包括high、low两种级别，表征终端是否在event report allowed area外部执行event report，high表示不执行，low表示有条件地执行。
另一种实施方式，可以适用于LCS client/AF请求的类型是基于area的事件上报，即：Power saving class包括高、中、低不同的级别；级别为高时，策略为：终端只在event report allowed area内执行event report；级别为中时，策略为终端需在event report allowed area内执行event report，在event report allowed area外且在Power saving area内执行有条件地上报；级别为低时，策略为：终端需在event report allowed area内执行event report，在event report allowed area外执行有条件地上报。
(5)area usage indication(即区域使用指示)，表示正向使用还是反向使用event report allowed area。一种实施方式中，上报指示包括以下两种对于event report allowed area的全局互斥设置，一种是反向使用，一种是正向使用，后者是默认设置。
其中，终端可以将第一信息携带在5GMM能力信息中，并将该5GMM能力信息封装在注册请求(registration request)消息中，从而将该registration request发送给AMF；
或者，终端也可以将第一信息作为新IE封装在registration request)消息中，从而将该registration request发送给AMF；
或者，终端也可以通过终端位置隐私设置请求(UE Location Privacy Setting Request)消息将第一信息发送给AMF；
或者，终端也可以通过上行非接入层传输(UL NAS TRASPORT)消息将第一信息发送给AMF。
步骤82：AMF向UDM发送UDM网元的更新数据配置消息(Nudm_ParameterProvision_Update)，其中，Nudm_ParameterProvision_Update携带有上述第一信息(即UE ID、Power saving area、Power saving class、area usage indication等信息)。
步骤83：UDM存储接收到的第一信息(即存储该UE ID的Power saving area、Power saving class、area usage indication)。
步骤84：LCS client/AF向GMLC发送定位服务请求(LCS service request)，即请求终端执行延迟上报。
这里，需要说明的是，其中不可信AF需要通过NEF作为中间网元进行服务验证，AF向NEF发起订阅，NEF向GMLC发起定位请求。
步骤85：GMLC向UDM发送Nudm_SDM_get或UDM网元的签约数据订阅请求消息(Nudm_SDM_subscribe)消息，以查询UE ID的定位相关的签约信息，获取第一信息(即Power saving area、Power saving class、area usage indication等信息)并保存。
本步骤可以是一次性的查询，可以是订阅，如果这里是订阅，后续实施例四中的步 骤115才会发生。
步骤86：GMLC执行如下(1)至(3)中至少一项：
(1)确定event report allowed area(即第一区域)，例如可以根据Power saving area来确定；
(2)确定目标指示信息，该目标指示信息用于表征终端在event report allowed area外是否需要执行event report；即如果基于上述“理解方式一”，即上述步骤81中的Power saving class是一种能力，则GMLC在此处确定终端是否需要在区域外上报；而如果基于上述“理解方式二或理解方式三”即上述步骤81中的Power saving class表示终端处于省电的级别，则GMLC不需要确定该目标指示信息。
(3)确定strategy(即上报策略)，用于表征终端在event report allowed area之外进行事件上报的约束条件，包括以下(a)至(c)中至少一项参数：
(a)最多上报的次数(即事件上报的最多上报次数)；
(b)最小上报的时间间隔(即相邻两次事件上报的最小时间间隔)；
(c)事件上报的触发条件，其中，所述触发条件用于指示除最小时间间隔、最多上报次数之外的门限信息，一种实施方法可以为：只有移动直线距离达到一定阈值(例如100米)才执行event report)。
其中，GMLC可以根据前述步骤84中定位服务请求的业务类型(即deferred 5GC-MT-LR的类型(area或periodic或motion)、步骤85中获取到的与定位相关的签约信息来确定上述(a)至(c)中的一条或多条参数的取值。
另外，GMLC确定strategy的一种实施方式可以为，比如终端需要在event report allowed area进行周期性上报，但是在event report allowed area之外，周期性会降低，即上报的时间间隔变成原来的两倍，上报的次数有上限限制，达到上限之后在event report allowed area之外就不会上报。
此外，例如上述Power saving class采用上述“理解方式一”，则GMLC可以根据Power saving class指示的具体内容，确定目标指示信息，即若Power saving class指示终端支持在event report allowed area之外进行事件上报，则目标指示信息指示终端在event report allowed area之外需要进行事件上报；若Power saving class指示终端不支持在event report allowed area之外进行事件上报，则目标指示信息指示终端在event report allowed area之外不需要进行事件上报)；目标指示信息的一种隐式的实施方式为，如果GMLC将目标指示信息发送给终端，即代表指示终端在event report allowed area之外需要进行事件上报；如果GMLC没有将目标指示信息发送给终端，即代表指示终端在event report allowed area之外不需要进行事件上报。
其中，如果Power saving class指示终端支持在event report allowed area之外进行事件上报(或目标指示信息指示终端在event report allowed area之外进行事件上报)，则GMLC可以进一步根据终端的定位业务类型和与定位相关的签约信息，确定strategy中的至少一个约束条件；而如果Power saving class指示终端不支持在event report allowed area之外进行事件上报，则GMLC不需要确定strategy。
例如上述Power saving class采用上述“理解方式二”，对于基于periodic或motion的事件上报，在Power saving class指示终端在event report allowed area之外进行事件上报的 情况下，GMLC可以进一步结合与定位相关的签约信息，确定strategy中的至少一个约束条件；在Power saving class指示终端在event report allowed area之外不进行事件上报的情况下，GMLC不需要确定strategy。
例如上述Power saving class采用上述“理解方式三”，对于基于area的事件上报，在Power saving class指示“中级”的情况下，GMLC可以进一步确定strategy中的至少一个约束条件，这样终端在event report allowed area外且在Power saving area内，根据strategy执行有条件地上报；在Power saving class指示“低级”的情况下，GMLC可以进一步确定strategy中的至少一个约束条件，这样终端在event report allowed area外，根据strategy执行有条件地上报；在Power saving class指示“高级”的情况下，GMLC不需要确定strategy。
步骤87：GMLC向AMF发送Namf_Location_ProvidePositioningInfo Request，其中，该消息中携带有event report allowed area和上述目标指示信息，进一步地，如果上述步骤86中GMLC确定了strategy，则该消息中还可以携带有GMLC确定的strategy。
步骤88：AMF向GMLC回复Namf_Location_ProvidePositioningInfo Response，确认收到步骤87中的消息。
步骤89：GMLC发送第二信息给LCS client/AF，其中，第二信息包括以下(1)至(5)中至少一项：
(1)event report allowed area(即GMLC在步骤86中确定的)；
(2)Power saving class；
(3)strategy(即GMLC在步骤86中确定的)；
(4)area usage indication；
(5)Target area error indication；(只适用于LCS client/AF请求的类型是基于area的事件上报)，Target area error indication可以理解为一种拒绝步骤84请求消息的拒绝消息中的理由(cause)，表征LCS client/AF请求的Target area有误，比如Target area与Power saving area的区域无重合区域或者有逻辑错误，需要对Target area进行修正。
步骤810：AMF、RAN、UE执行前文所述的步骤39到313，等待终端进入连接态，建立与终端的连接，并完成用户的隐私验证。
步骤811：AMF向LMF发送Nlmf_Location_DetermineLocation Request，其中，该消息中携带有event report allowed area和上述目标指示信息，进一步地，如果上述步骤87AMF收到了strategy，则该消息中还可以携带有AMF收到的strategy；
步骤812：终端定位流程，即LMF执行一个或多个定位流程，请求以及获取到终端的位置；
步骤813：LMF向UE发送LCS Periodic-Triggered Invoke Request消息，其中，该消息中携带有event report allowed area和上述目标指示信息，进一步地，如果上述步骤811LMF收到了strategy，则该消息中还可以携带有LMF收到的strategy；
步骤814：UE向LMF发送LCS Periodic-Triggered Invoke Return；
步骤815：LMF向AMF发送Nlmf_Location_DetermineLocation Response；
步骤816：AMF向GMLC发送Namf_Location_EventNotify；
步骤817：GMLC向LCS Client/AF发送LCS Service Response；
步骤818：终端检测事件，并执行相应操作；
即如果UE在检测到事件触发时，并且处于event report allowed area之外，执行以下(1)至(10)至少一项动作：
(1)如果Power saving class指示UE在event report allowed area之外不执行上报，则UE不执行上报(即不存在步骤819)；
(2)如果Power saving class指示UE在event report allowed area之外进行事件上报，并且步骤813收到了strategy，则UE在event report allowed area之外按照strategy执行有条件地事件上报；
(3)如果Power saving class指示UE在event report allowed area之外进行事件上报，但是步骤813没有收到strategy，则UE在event report allowed area之外不执行事件上报，或者UE基于实现执行事件上报；
(4)如果步骤813中收到的目标指示信息指示UE在event report allowed area之外不执行事件上报或者没有收到目标指示信息，则UE不执行事件上报(即不存在步骤819)；
(5)如果步骤813中收到的目标指示信息指示UE在event report allowed area之外进行事件上报，并且步骤813收到了strategy，则UE在event report allowed area之外按照strategy执行有条件地事件上报；
(6)如果步骤813中收到的目标指示信息指示UE在event report allowed area之外进行事件上报，但是步骤813没有收到strategy，则UE在event report allowed area之外不执行事件上报，或者UE基于实现执行事件上报；
(7)如果Power saving class指示“高级”，则UE不执行上报(即不存在步骤819)；
(8)如果Power saving class指示“中级”，并且步骤813收到了strategy，则UE在event report allowed area之外且在power saving area内，按照strategy执行有条件地事件上报；
(9)如果Power saving class指示“低级”，并且步骤813收到了strategy，则UE在event report allowed area之外，按照strategy执行有条件地事件上报；
(10)如果Power saving class指示“中级或低级”，但是步骤813没有收到strategy，则UE在event report allowed area之外不执行事件上报，或者UE基于实现执行事件上报。
这里，对于UE按照strategy执行有条件地上报，例如：结合步骤86中的例子，当strategy包括最多上报次数和最小时间间隔两个参数时，UE在event report allowed area之外时，每次上报的时间间隔必须大于最小时间间隔，上报的次数不能大于最多上报次数。
步骤819：执行事件上报流程，即与前文所述的步骤323至330b-2相同，此处不再赘述。
实施方式二：如图9所示，包括如下步骤91至919：
步骤91至93分别与上述实施方式一中的步骤81至83相同，此处不再赘述。
步骤94：LCS client/AF向GMLC发送LCS service request，即请求终端执行延迟上报，其中，LCS service request中携带有strategy；
步骤95与上述实施方式一中的步骤95相同，此处不再赘述。
步骤96：GMLC执行如下(1)至(3)中至少一项：
(1)确定event report allowed area(即第一区域)，例如可以根据Power saving area 来确定；
(2)确定目标指示信息，该目标指示信息用于表征终端在event report allowed area外是否需要执行event report；即如果基于上述“理解方式一”，即上述步骤81中的Power saving class是一种能力，则GMLC在此处确定终端是否需要在区域外上报；而如果基于上述“理解方式二”即上述步骤81中的Power saving class表示终端处于省电的级别，则GMLC不需要确定该目标指示信息。
(3)确定strategy(即上报策略)，用于表征终端在event report allowed area之外进行事件上报的约束条件，包括以下(a)至(c)中至少一项参数：
(a)最多上报的次数(即事件上报的最多上报次数)；
(b)最小上报的时间间隔(即相邻两次事件上报的最小时间间隔)；
(c)事件上报的触发条件，其中，所述触发条件用于指示除最小时间间隔、最多上报次数之外的门限信息，一种实施方法可以为：只有移动直线距离达到一定阈值(例如100米)才执行event report。
此处需要说明的是，由于前述步骤95中的LCS service request携带有strategy，所以，如果Power saving class指示终端支持在event report allowed area之外进行事件上报，或者指示终端在event report allowed area之外进行事件上报，或者指示“中级或低级”，则在步骤96中，GMLC可以将LCS service request携带的strategy，作为需要发送给UE的strategy(即此种情况下，在步骤96中GMLC不需要确定strategy)，或者，选择LCS service request携带的strategy包括的部分约束条件(即参数)，作为需要发送给UE的strategy的约束条件(即参数)。
步骤97至步骤98分别与上述实施方式一中的步骤87至88相同，此处不再赘述。
步骤99：GMLC发送第二信息给LCS client/AF，其中，第二信息包括以下(1)至(5)中至少一项：
(1)event report allowed area(即GMLC在步骤86中确定的)；
(2)Power saving class；
(4)area usage indication；
(5)Target area error indication。
即在实施方式二中，步骤99相对于实施方式一中的步骤89而言，GMLC发送给LCS client/AF的第二信息不包括strategy。
步骤99至步骤919分别与上述实施方式一中的步骤89至819相同，此处不再赘述。
实施方式三：如图10所示，包括如下步骤101至1019：
步骤101：终端向AMF发送NAS信令，该NAS信令中携带有第一信息，该第一信息包括以下(1)至(5)项中至少一项：
(1)UE ID(即终端标识)；
(2)消息类型；
(3)Power saving area；
(4)Power saving class；
(5)策略集，该策略集包括至少一个候选的strategy，其中，该策略集中的不同strategy适用于不同的定位类型，GMLC后续可以根据不同的业务来从策略集中挑选合适的 strategy。
步骤102：AMF向UDM发送Nudm_ParameterProvision_Update，其中，Nudm_ParameterProvision_Update携带有上述第一信息(即UE ID、Power saving area、Power saving class、area usage indication、策略集等信息)。
步骤103：UDM存储接收到的第一信息(即存储该UE ID的Power saving area、Power saving class、area usage indication、策略集)。
步骤104与上述实施方式一中的步骤84相同，此处不再赘述。
步骤105：GMLC向UDM发送Nudm_SDM_get或Nudm_SDM_subscribe消息，以查询UE ID的定位相关的签约信息，获取第一信息(即Power saving area、Power saving class、area usage indication、策略集等信息)并保存。
步骤106：GMLC执行如下(1)至(3)中至少一项：
(1)确定event report allowed area(即第一区域)，例如可以根据Power saving area来确定；
(2)确定目标指示信息，该目标指示信息用于表征终端在event report allowed area外是否需要执行event report；即如果基于上述“理解方式一”，即上述步骤81中的Power saving class是一种能力，则GMLC在此处确定终端是否需要在区域外上报；而如果基于上述“理解方式二”即上述步骤81中的Power saving class表示终端处于省电的级别，则GMLC不需要确定该目标指示信息。
(3)确定strategy(即上报策略)，用于表征终端在event report allowed area之外进行事件上报的约束条件，包括以下(a)至(c)中至少一项参数：
(a)最多上报的次数(即事件上报的最多上报次数)；
(b)最小上报的时间间隔(即相邻两次事件上报的最小时间间隔)；
(c)事件上报的触发条件，其中，所述触发条件用于指示除最小时间间隔、最多上报次数之外的门限信息，一种实施方法可以为：只有移动直线距离达到一定阈值(例如100米)才执行event report)。
需要说明的是，如果Power saving class指示终端支持在event report allowed area之外进行事件上报，或者指示终端在event report allowed area之外进行事件上报，或者指示“中级或低级”，则在步骤106中，GMLC可以基于网络的选择或者根据LCS client的类型(area或periodic或motion)、步骤105中获取到的终端与定位相关的签约信息等，从策略集中选择一个候选的strategy，然后根据所选择的候选的strategy，确定需要发送给UE的strategy。
步骤107至步骤1019分别与上述实施方式一中的步骤87至819相同，此处不再赘述。
实施方式四：如图11所示，包括如下步骤111至116：
步骤111：终端的第一信息改变，即终端的Power saving area、Power saving class、area usage indication、策略集中的至少一者发生变化；
步骤112：终端向AMF发送NAS message，携带第三信息，其中，第三信息包括如下中发生变化的至少一项：
(1)Power saving area；
(2)Power saving class；
(3)area usage indication；
(4)策略集。
其中，终端可以将第三信息携带在5GMM能力信息中，并将该5GMM能力信息封装在注册请求(registration request)消息中，从而将该registration request发送给AMF；
或者，终端也可以将第三信息作为新IE封装在registration request)消息中，从而将该registration request发送给AMF；
或者，终端也可以通过终端位置隐私设置请求(UE Location Privacy Setting Request)消息将第三信息发送给AMF；
或者，终端也可以通过上行非接入层传输(UL NAS TRASPORT)消息将第三信息发送给AMF。
步骤113：AMF向UDM发送Nudm_ParameterProvision_Update，其中，Nudm_ParameterProvision_Update携带有上述第三信息(即Power saving area、Power saving class、area usage indication、策略集中发生变化的至少一项)。
步骤114：UDM存储接收到的第三信息(即Power saving area、Power saving class、area usage indication、策略集中发生变化的至少一项)。
步骤115：UDM向GMLC提供第三信息(即Power saving area、Power saving class、area usage indication、策略集中发生变化的至少一项)。
即如果前述实施方式一的步骤85中GMLC订阅了终端的信息，则本步骤中，UDM向GMLC提供更新的Power saving area、Power saving class、area usage indication、策略集等信息。
步骤116：GMLC根据更新之后的Power saving area、Power saving class、area usage indication、策略集、结合target area、当前的event report allowed area、当前的strategy和当前报告状态(即report status，例如迄今为止的上报次数，汇报持续时间等)，更新以下至少一项：
(1)event report allowed area，
(2)strategy(即需要发送给UE的strategy)；
(3)第一指示信息。
步骤117：GMLC通过AMF、LMF，将更新的event report allowed area、strategy、目标指示信息中的至少一项，发送给终端。
综上所述，本申请的实施例中，终端可以上报自己的Power saving class和area usage indication，以此来指示终端对event report allowed area是正向使用还是反向使用，以及终端是否支持在event allowed area外部有条件地执行上报；进一步地，终端也可以提供策略集，由GMLC根据定位业务来从策略集中选择一个候选的上报策略，进而确定需要发送给终端的上报策略；或者，也可以由LCS client/AF直接提供上报策略；或者，终端和LCS client/AF均不提供时，由GMLC自己确定需要发送给终端的上报策略。
此外，终端也可以更新自己的Power saving class、策略集、area usage indication，保存在UDM中，以使得GMLC可以根据更新之后的信息来更新终端在区域外的执行动作。
总之，在本申请实施例中，通过设定不同的Power saving class和上报策略的方法， 来解决终端在event report allowed area之外是否执行以及如何执行事件上报的问题，并通过指示area usage indication来解决是否反向使用区域的问题。
本申请实施例提供的事件上报方法，执行主体可以为事件上报装置。本申请实施例中以事件上报装置执行事件上报方法为例，说明本申请实施例提供的事件上报装置。
第五方面，本申请的实施例提供了一种事件上报装置，可以应用于终端，如图12所示，该事件上报装置120包括：
第一发送模块1201，用于发送第一信息，其中，所述第一信息用于指示终端在第一区域之外进行事件上报的相关信息，所述第一区域为允许所述终端进行事件上报的区域；
第一接收模块1202，用于接收与所述第一信息相匹配的事件上报配置信息；
第一处理模块1203，用于根据所述事件上报配置信息，进行事件上报。
可选地，所述第一信息包括以下至少一项：
第二区域，所述第二区域用于指示所述终端期望进行事件上报的区域；
上报指示，所述上报指示用于指示所述终端是否支持在所述第一区域之外进行事件上报，或者指示所述终端在所述第一区域之外是否进行事件上报，或者指示关于所述终端在所述第一区域之外进行事件上报的至少一个等级；
区域使用指示，所述区域使用指示用于指示正向使用所述第一区域，或反向使用所述第一区域。
可选地，所述事件上报配置信息包括以下至少一项：
目标指示信息，所述目标指示信息用于指示所述终端在所述第一区域之外是否需要进行事件上报；
上报策略，所述上报策略用于指示终端进行事件上报的至少一个约束条件。
可选地，第一处理模块1203根据所述事件上报配置信息，进行事件上报，具体用于：
在所述事件上报配置信息包括所述目标指示信息，且所述目标指示信息指示所述终端在所述第一区域之外不需要进行事件上报的情况下，在所述第一区域之外不进行事件上报；
在所述事件上报配置信息包括所述目标指示信息和所述上报策略，且所述目标指示信息指示所述终端在所述第一区域之外需要进行事件上报的情况下，在所述第一区域之外，根据所述上报策略进行事件上报；
在所述事件上报配置信息包括所述目标指示信息，且所述上报配置信息不包括所述上报策略，且所述目标指示信息指示所述终端在所述第一区域之外需要进行事件上报的情况下，在所述第一区域之外不进行事件上报，或者，在所述第一区域之外基于实现进行事件上报；
在所述第一信息包括所述上报指示，且所述上报指示指示在所述第一区域之外不进行事件上报的情况下，在所述第一区域之外不进行事件上报；
在所述第一信息包括所述上报指示，且所述上报指示指示在所述第一区域之外进行事件上报，且所述事件上报配置信息包括所述上报策略的情况下，在所述第一区域之外，根据所述上报策略进行事件上报；
在所述第一信息包括所述上报指示，且所述上报指示指示在所述第一区域之外进行事件上报，且所述事件上报配置信息不包括所述上报策略的情况下，在所述第一区域之 外不进行事件上报，或者，在所述第一区域之外基于实现进行事件上报；
在所述第一信息包括所述上报指示，且所述上报指示指示第一等级，且所述事件上报配置信息不包括所述上报策略的情况下，在所述第一区域之外不进行事件上报；
在所述第一信息包括所述上报指示，且所述上报指示指示第二等级，且所述事件上报配置信息包括所述上报策略的情况下，在所述第一区域之外且在所述第二区域之内，根据所述上报策略进行事件上报；
在所述第一信息包括所述上报指示，且所述上报指示指示第三等级，且所述事件上报配置信息包括所述上报策略的情况下，在所述第一区域之外，根据与所述上报策略进行事件上报；
在所述第一信息包括所述上报指示，且所述上报指示指示所述第二等级或所述第三等级，且所述事件上报配置信息不包括所述上报策略的情况下，在所述第一区域之外不进行事件上报，或者，在所述第一区域之外基于实现进行事件上报。
可选地，所述上报策略包括以下至少一项：
事件上报的最多上报次数；
相邻两次事件上报的最小时间间隔；
事件上报的触发条件，其中，所述触发条件用于指示除所述最小时间间隔、所述最多上报次数之外的门限信息。
可选地，第一处理模块1203根据所述上报策略进行事件上报，具体用于：
根据所述最多上报次数、所述最小时间间隔、所述触发条件中的至少一项，执行有条件地事件上报。
可选地，所述第一信息还包括策略集，其中，所述策略集包括至少一个候选的上报策略，所述事件上报配置信息中包括的上报策略，是根据所述策略集中的其中一个候选的上报策略确定的。
可选地，所述装置还包括：
第三发送模块，用于在所述第一信息中包括的至少一项信息发生变化的情况下，发送第三信息，其中，所述第三信息包括所述第一信息中发生变化的信息。
可选地，所述装置还包括：
第二接收模块，用于接收第四信息，其中，所述第四信息包括所述第一区域和所述事件上报配置信息中的至少一项，所述第四信息是根据所述第三信息确定的；
第二处理模块，用于根据所述第四信息，进行事件上报。
可选地，所述第一发送模块具体用于：
发送目标消息，所述目标消息携带有所述第一信息；
其中，所述目标消息包括以下至少一项：
注册请求消息；
位置隐私设置请求消息；
上行非接入层传输消息。
本申请实施例中的事件上报装置可以是电子设备，例如具有操作系统的电子设备，也可以是电子设备中的部件，例如集成电路或芯片。该电子设备可以是终端，示例性的，终端可以包括但不限于上述所列举的终端11的类型，本申请实施例不作具体限定。
本申请实施例提供的事件上报装置能够实现图4的方法实施例实现的各个过程，并达到相同的技术效果，为避免重复，这里不再赘述。
第六方面，本申请的实施例提供了一种事件上报装置，可以应用于第一网络侧设备，如图13所示，该事件上报装置130包括以下模块：
第一获取模块1301，用于获取终端的第一信息，其中，所述第一信息用于指示所述终端在第一区域之外进行事件上报的相关信息，所述第一区域为允许所述终端进行事件上报的区域；
第二获取模块1302，用于获取与所述第一信息相匹配的事件上报配置信息；
第二发送模块1303，用于发送所述上报配置信息给所述终端。
可选地，所述第一信息包括以下至少一项：
第二区域，所述第二区域用于指示所述终端期望进行事件上报的区域；
上报指示，所述上报指示用于指示所述终端是否支持在所述第一区域之外进行事件上报，或者指示所述终端在所述第一区域之外是否进行事件上报，或者指示关于所述终端在所述第一区域之外进行事件上报的等级；
区域使用指示，所述区域使用指示用于指示正向使用所述第一区域，或反向使用所述第一区域。
可选地，所述事件上报配置信息包括以下至少一项：
目标指示信息，所述目标指示信息用于指示所述终端在所述第一区域之外是否需要进行事件上报；
上报策略，所述上报策略用于指示终端进行事件上报的至少一个约束条件。
可选地，所述上报策略包括以下至少一项：
事件上报的最多上报次数；
相邻两次事件上报的最小时间间隔；
事件上报的触发条件，其中，所述触发条件用于指示除所述最小时间间隔、所述最多上报次数之外的门限信息。
可选地，在所述事件上报配置信息中包括所述上报策略的情况下，所述第二获取模块1302具体用于：
在上报指示指示所述终端支持在所述第一区域之外进行事件上报，或者指示所述终端在所述第一区域之外进行事件上报，或者指示第二等级或第三等级的情况下，根据定位业务类型和所述终端与定位相关的签约信息，确定所述事件上报配置信息；
或者，
在所述上报指示指示所述终端支持在所述第一区域之外进行事件上报，或者指示所述终端在所述第一区域之外进行事件上报，或者指示所述第二等级或所述第三等级的情况下，根据从第四网络侧设备中接收到的上报策略，确定所述事件上报配置信息；
或者，
在所述第一信息还包括策略集，且所述上报指示指示所述终端支持在所述第一区域之外进行事件上报，或者指示所述终端在所述第一区域之外进行事件上报，或者指示所述第二等级或所述第三等级的情况下，根据定位业务类型，从所述策略集中选择一个候选的上报策略，并根据选出的候选的上报策略，确定所述事件上报配置信息，其中，所 述策略集包括至少一个候选的上报策略。
可选地，所述第二获取模块1302接收所述第四网络侧设备发送的上报策略的过程，包括：
接收所述第四网络侧设备发送的定位服务请求，其中，所述定位服务请求中携带有上报策略。
可选地，所述第二发送模块1303具体用于：
通过第三网络侧设备和第五网络侧设备，将所述事件上报配置信息发送给所述终端。
可选地，所述装置还包括：
第四发送模块，用于发送第二信息给第四网络侧设备，其中，所述第二信息包括以下至少一项：
所述第一区域；
上报指示，所述上报指示用于指示所述终端是否支持在所述第一区域之外进行事件上报，或者指示所述终端在所述第一区域之外是否进行事件上报；
所述事件上报配置信息；
区域使用指示，所述区域使用指示用于指示正向使用所述第一区域，或反向使用所述第一区域；
目标区域错误原因，其中，所述目标区域错误原因用于指示目标区域与第二区域之间无重合区域或者所述目标区域存在逻辑错误，所述目标区域为期望所述终端进行事件上报的区域，所述第二区域用于指示所述终端期望进行事件上报的区域。
可选地，第一获取模块1301具体用于：
从第二网络侧设备中获取所述第一信息，其中，所述第二网络侧设备中存储的所述第一信息是所述终端通过第三网络侧设备发送给所述第二网络侧设备的。
可选地，所述装置还包括：
第三获取模块，用于在所述第一网络侧设备订阅了所述终端的信息的情况下，获取第二网络侧设备提供的第三信息，其中，所述第三信息包括所述第一信息中发生变化的信息，所述第二网络侧设备中存储的所述第三信息是所述终端通过第三网络侧设备发送给所述第二网络侧设备的。
可选地，所述装置还包括：
更新模块，用于根据所述第三信息更新第四信息，其中，所述第四信息包括所述第一区域和所述事件上报配置信息中的至少一项；
第五发送模块，用于将更新后的所述第四信息发送给所述终端。
本申请实施例中的事件上报装置可以是电子设备，例如具有操作系统的电子设备，也可以是电子设备中的部件，例如集成电路或芯片。该电子设备可以是网络侧设备。示例性的，网络侧设备可以包括但不限于上述所列举的网络侧设备12的类型，本申请实施例不作具体限定。
本申请实施例提供的事件上报装置能够实现图7的方法实施例实现的各个过程，并达到相同的技术效果，为避免重复，这里不再赘述。
第七方面，本申请的实施例提供了一种事件上报装置，可以应用于第四网络侧设备，该事件上报装置可以包括如下模块：
第六发送模块，用于发送上报策略给第一网络侧设备，其中，所述上报策略用于指示终端进行事件上报的至少一个约束条件。
可选地，第六发送模块具体用于：发送定位服务请求给所述第一网络侧设备，其中，所述定位服务请求中携带有上报策略。
可选地，所述装置还包括：
第三接收模块，用于接收所述第一网络侧设备发送的第二信息，其中，所述第二信息包括以下至少一项：
所述第一区域；
上报指示，所述上报指示用于指示所述终端是否支持在所述第一区域之外进行事件上报，或者指示所述终端在所述第一区域之外是否进行事件上报；
所述事件上报配置信息；
区域使用指示，所述区域使用指示用于指示正向使用所述第一区域，或反向使用所述第一区域；
目标区域错误原因，其中，所述目标区域错误原因用于指示目标区域与第二区域之间无重合区域或者所述目标区域存在逻辑错误，所述目标区域为期望所述终端进行事件上报的区域，所述第二区域用于指示所述终端期望进行事件上报的区域。
本申请实施例中的事件上报装置可以是电子设备，例如具有操作系统的电子设备，也可以是电子设备中的部件，例如集成电路或芯片。该电子设备可以是网络侧设备，示例性的，网络侧设备可以包括但不限于上述所列举的网络侧设备12的类型，本申请实施例不作具体限定。
本申请实施例提供的事件上报装置能够实现前述第三方面的方法实施例实现的各个过程，并达到相同的技术效果，为避免重复，这里不再赘述。
第八方面，本申请实施例还提供了一种事件上报装置，可以应用于第二网络侧设备，该事件上报装置可以包括如下模块：
第四获取模块，用于获取终端的第一信息，并存储所述第一信息。
第一提供模块，用于向第一网络侧设备提供所述第一信息。
可选地，所述第一信息包括以下至少一项：
第二区域，所述第二区域用于指示所述终端期望进行事件上报的区域；
上报指示，所述上报指示用于指示所述终端是否支持在所述第一区域之外进行事件上报，或者指示所述终端在所述第一区域之外是否进行事件上报，或者指示关于所述终端在所述第一区域之外进行事件上报的至少一个等级；
区域使用指示，所述区域使用指示用于指示正向使用所述第一区域，或反向使用所述第一区域。
可选地，所述装置还包括：
第四接收模块，用于接收所述第一终端发送的第三信息，并存储所述第三信息，其中，所述第三信息包括所述第一信息中发生变化的信息；
第二提供模块，用于向所述第一网络侧设备提供所述第三信息。
本申请实施例中的事件上报装置可以是电子设备，例如具有操作系统的电子设备，也可以是电子设备中的部件，例如集成电路或芯片。该电子设备可以是网络侧设备，示 例性的，网络侧设备可以包括但不限于上述所列举的网络侧设备12的类型，本申请实施例不作具体限定。
本申请实施例提供的事件上报装置能够实现前述第四方面的方法实施例实现的各个过程，并达到相同的技术效果，为避免重复，这里不再赘述。
如图14所示，本申请实施例还提供一种通信设备1400，包括处理器1401和存储器1402，存储器1402上存储有可在所述处理器1401上运行的程序或指令，例如，该通信设备1400为终端时，该程序或指令被处理器1401执行时实现上述事件上报方法实施例的各个步骤，且能达到相同的技术效果。该通信设备1400为网络侧设备时，该程序或指令被处理器1401执行时实现上述事件上报方法实施例的各个步骤，且能达到相同的技术效果，为避免重复，这里不再赘述。
本申请实施例还提供一种终端，包括处理器和通信接口，所述通信接口和所述处理器耦合，所述处理器用于运行程序或指令，实现如图4所示方法实施例中的步骤。该终端实施例与上述终端侧方法实施例对应，上述方法实施例的各个实施过程和实现方式均可适用于该终端实施例中，且能达到相同的技术效果。具体地，图15为实现本申请实施例的一种终端的硬件结构示意图。
该终端1500包括但不限于：射频单元1501、网络模块1502、音频输出单元1503、输入单元1504、传感器1505、显示单元1506、用户输入单元1507、接口单元1508、存储器1509以及处理器1510等中的至少部分部件。
本领域技术人员可以理解，终端1500还可以包括给各个部件供电的电源(比如电池)，电源可以通过电源管理系统与处理器1510逻辑相连，从而通过电源管理系统实现管理充电、放电以及功耗管理等功能。图15中示出的终端结构并不构成对终端的限定，终端可以包括比图示更多或更少的部件，或者组合某些部件，或者不同的部件布置，在此不再赘述。
应理解的是，本申请实施例中，输入单元1504可以包括图形处理单元(Graphics Processing Unit，GPU)15041和麦克风15042，图形处理器15041对在视频捕获模式或图像捕获模式中由图像捕获装置(如摄像头)获得的静态图片或视频的图像数据进行处理。显示单元1506可包括显示面板15061，可以采用液晶显示器、有机发光二极管等形式来配置显示面板15061。用户输入单元1507包括触控面板15071以及其他输入设备15072中的至少一种。触控面板15071，也称为触摸屏。触控面板15071可包括触摸检测装置和触摸控制器两个部分。其他输入设备15072可以包括但不限于物理键盘、功能键(比如音量控制按键、开关按键等)、轨迹球、鼠标、操作杆，在此不再赘述。
本申请实施例中，射频单元1501接收来自网络侧设备的下行数据后，可以传输给处理器1510进行处理；另外，射频单元1501可以向网络侧设备发送上行数据。通常，射频单元1501包括但不限于天线、放大器、收发信机、耦合器、低噪声放大器、双工器等。
存储器1509可用于存储软件程序或指令以及各种数据。存储器1509可主要包括存储程序或指令的第一存储区和存储数据的第二存储区，其中，第一存储区可存储操作系统、至少一个功能所需的应用程序或指令(比如声音播放功能、图像播放功能等)等。此外，存储器1509可以包括易失性存储器或非易失性存储器15。其中，非易失性存储器可以是只读存储器(Read-Only Memory，ROM)、可编程只读存储器(Programmable ROM， PROM)、可擦除可编程只读存储器(Erasable PROM，EPROM)、电可擦除可编程只读存储器(Electrically EPROM，EEPROM)或闪存。易失性存储器可以是随机存取存储器(Random Access Memory，RAM)，静态随机存取存储器(Static RAM，SRAM)、动态随机存取存储器(Dynamic RAM，DRAM)、同步动态随机存取存储器(Synchronous DRAM，SDRAM)、双倍数据速率同步动态随机存取存储器(Double Data Rate SDRAM，DDRSDRAM)、增强型同步动态随机存取存储器(Enhanced SDRAM，ESDRAM)、同步连接动态随机存取存储器(Synch link DRAM，SLDRAM)和直接内存总线随机存取存储器(Direct Rambus RAM，DRRAM)。本申请实施例中的存储器1509包括但不限于这些和任意其它适合类型的存储器。
处理器1510可包括一个或多个处理单元；可选地，处理器1510集成应用处理器和调制解调处理器，其中，应用处理器主要处理涉及操作系统、用户界面和应用程序等的操作，调制解调处理器主要处理无线通信信号，如基带处理器。可以理解的是，上述调制解调处理器也可以不集成到处理器1510中。
射频单元1501用于终端发送第一信息，其中，所述第一信息用于指示所述终端在第一区域之外进行事件上报的相关信息，所述第一区域为允许所述终端进行事件上报的区域；
射频单元1501还用于接收与所述第一信息相匹配的事件上报配置信息；
处理器1510用于根据所述事件上报配置信息，进行事件上报。
可选地，所述第一信息包括以下至少一项：
第二区域，所述第二区域用于指示所述终端期望进行事件上报的区域；
上报指示，所述上报指示用于指示所述终端是否支持在所述第一区域之外进行事件上报，或者指示所述终端在所述第一区域之外是否进行事件上报，或者指示关于所述终端在所述第一区域之外进行事件上报的至少一个等级；
区域使用指示，所述区域使用指示用于指示正向使用所述第一区域，或反向使用所述第一区域。
可选地，所述事件上报配置信息包括以下至少一项：
目标指示信息，所述目标指示信息用于指示所述终端在所述第一区域之外是否需要进行事件上报；
上报策略，所述上报策略用于指示终端进行事件上报的至少一个约束条件。
可选地，所述处理器1510根据所述事件上报配置信息，进行事件上报，包括：
在所述事件上报配置信息包括所述目标指示信息，且所述目标指示信息指示所述终端在所述第一区域之外不需要进行事件上报的情况下，在所述第一区域之外不进行事件上报；
在所述事件上报配置信息包括所述目标指示信息和所述上报策略，且所述目标指示信息指示所述终端在所述第一区域之外需要进行事件上报的情况下，在所述第一区域之外，根据所述上报策略进行事件上报；
在所述事件上报配置信息包括所述目标指示信息，且所述上报配置信息不包括所述上报策略，且所述目标指示信息指示所述终端在所述第一区域之外需要进行事件上报的情况下，在所述第一区域之外不进行事件上报，或者，在所述第一区域之外基于实现进 行事件上报；
在所述第一信息包括所述上报指示，且所述上报指示指示在所述第一区域之外不进行事件上报的情况下，在所述第一区域之外不进行事件上报；
在所述第一信息包括所述上报指示，且所述上报指示指示在所述第一区域之外进行事件上报，且所述事件上报配置信息包括所述上报策略的情况下，在所述第一区域之外，根据所述上报策略进行事件上报；
在所述第一信息包括所述上报指示，且所述上报指示指示在所述第一区域之外进行事件上报，且所述事件上报配置信息不包括所述上报策略的情况下，在所述第一区域之外不进行事件上报，或者，在所述第一区域之外基于实现进行事件上报；
在所述第一信息包括所述上报指示，且所述上报指示指示第一等级，且所述事件上报配置信息不包括所述上报策略的情况下，在所述第一区域之外不进行事件上报；
在所述第一信息包括所述上报指示，且所述上报指示指示第二等级，且所述事件上报配置信息包括所述上报策略的情况下，在所述第一区域之外且在所述第二区域之内，根据所述上报策略进行事件上报；
在所述第一信息包括所述上报指示，且所述上报指示指示第三等级，且所述事件上报配置信息包括所述上报策略的情况下，在所述第一区域之外，根据与所述上报策略进行事件上报；
在所述第一信息包括所述上报指示，且所述上报指示指示所述第二等级或所述第三等级，且所述事件上报配置信息不包括所述上报策略的情况下，在所述第一区域之外不进行事件上报，或者，在所述第一区域之外基于实现进行事件上报。
可选地，所述上报策略包括以下至少一项：
事件上报的最多上报次数；
相邻两次事件上报的最小时间间隔；
事件上报的触发条件，其中，所述触发条件用于指示除所述最小时间间隔、所述最多上报次数之外的门限信息。
可选地，处理器1510根据所述上报策略进行事件上报，包括：
根据所述最多上报次数、所述最小时间间隔、所述触发条件中的至少一项，执行有条件地事件上报。
可选地，所述第一信息还包括策略集，其中，所述策略集包括至少一个候选的上报策略，所述事件上报配置信息中包括的上报策略，是根据所述策略集中的其中一个候选的上报策略确定的。
可选地，射频单元1501还用于：
在所述第一信息中包括的至少一项信息发生变化的情况下，发送第三信息，其中，所述第三信息包括所述第一信息中发生变化的信息。
可选地，射频单元1501还用于：
接收第四信息，其中，所述第四信息包括所述第一区域和所述事件上报配置信息中的至少一项，所述第四信息是根据所述第三信息确定的；
处理器1510还用于根据所述第四信息，进行事件上报。
可选地，射频单元1501发送第一信息，包括：
发送目标消息，所述目标消息携带有所述第一信息；
其中，所述目标消息包括以下至少一项：
注册请求消息；
位置隐私设置请求消息；
上行非接入层传输消息。
可以理解，本实施例中提及的各实现方式的实现过程可以参照方法实施例事件上报方法的相关描述，并达到相同或相应的技术效果，为避免重复，在此不再赘述。
本申请实施例还提供一种网络侧设备，包括处理器和通信接口，所述通信接口和所述处理器耦合，所述处理器用于运行程序或指令，实现前述第二方面或第三方面或第四方面所述的方法实施例的步骤。该网络侧设备实施例与上述网络侧设备方法实施例对应，上述方法实施例的各个实施过程和实现方式均可适用于该网络侧设备实施例中，且能达到相同的技术效果。
具体地，本申请实施例还提供了一种网络侧设备。如图16所示，该网络侧设备1600包括：处理器1601、网络接口1602和存储器1603。其中，网络接口1602例如为通用公共无线接口(common public radio interface，CPRI)。
具体地，本发明实施例的网络侧设备1600还包括：存储在存储器1603上并可在处理器1601上运行的指令或程序，处理器1601调用存储器1603中的指令或程序执行前述第二方面或第三方面或第四方面所述的方法，并达到相同的技术效果，为避免重复，故不在此赘述。
本申请实施例还提供一种可读存储介质，所述可读存储介质上存储有程序或指令，该程序或指令被处理器执行时实现上述事件上报方法实施例的各个过程，且能达到相同的技术效果，为避免重复，这里不再赘述。
其中，所述处理器为上述实施例中所述的终端中的处理器。所述可读存储介质，包括计算机可读存储介质，如计算机只读存储器ROM、随机存取存储器RAM、磁碟或者光盘等。在一些示例中，可读存储介质可以是非瞬态的可读存储介质。
本申请实施例另提供了一种芯片，所述芯片包括处理器和通信接口，所述通信接口和所述处理器耦合，所述处理器用于运行程序或指令，实现上述事件上报方法实施例的各个过程，且能达到相同的技术效果，为避免重复，这里不再赘述。
应理解，本申请实施例提到的芯片还可以称为系统级芯片，系统芯片，芯片系统或片上系统芯片等。
本申请实施例另提供了一种计算机程序/程序产品，所述计算机程序/程序产品被存储在存储介质中，所述计算机程序/程序产品被至少一个处理器执行以实现上述事件上报方法实施例的各个过程，且能达到相同的技术效果，为避免重复，这里不再赘述。
本申请实施例还提供了一种无线通信系统，包括：终端及第一网络侧设备，所述终端可用于执行如上所述的第一方面所述的事件上报方法的步骤，所述第一网络侧设备可用于执行如上第二方面所述的事件上报方法的步骤，进一步地，该无线通信系统还包括第四网络侧设备和第二网络侧设备，第四网络侧设备可用于执行如上第三方面所述的事件上报方法的步骤，第二网络侧设备可用于执行如上第四方面所述的事件上报方法的步骤。
需要说明的是，在本文中，术语“包括”、“包含”或者其任何其他变体意在涵盖非排他性的包含，从而使得包括一系列要素的过程、方法、物品或者装置不仅包括那些要素，而且还包括没有明确列出的其他要素，或者是还包括为这种过程、方法、物品或者装置所固有的要素。在没有更多限制的情况下，由语句“包括一个……”限定的要素，并不排除在包括该要素的过程、方法、物品或者装置中还存在另外的相同要素。此外，需要指出的是，本申请实施方式中的方法和装置的范围不限按示出或讨论的顺序来执行功能，还可包括根据所涉及的功能按基本同时的方式或按相反的顺序来执行功能，例如，可以按不同于所描述的次序来执行所描述的方法，并且还可以添加、省去或组合各种步骤。另外，参照某些示例所描述的特征可在其他示例中被组合。
通过以上的实施方式的描述，本领域的技术人员可以清楚地了解到上述实施例方法可借助计算机软件产品加必需的通用硬件平台的方式来实现，当然也可以通过硬件。该计算机软件产品存储在存储介质(如ROM、RAM、磁碟、光盘等)中，包括若干指令，用以使得终端或者网络侧设备执行本申请各个实施例所述的方法。
上面结合附图对本申请的实施例进行了描述，但是本申请并不局限于上述的具体实施方式，上述的具体实施方式仅仅是示意性的，而不是限制性的，本领域的普通技术人员在本申请的启示下，在不脱离本申请宗旨和权利要求所保护的范围情况下，还可做出很多形式的实施方式，这些实施方式均属于本申请的保护之内。

Claims (38)

  1. 一种事件上报方法，所述方法包括：
    终端发送第一信息，其中，所述第一信息用于指示所述终端在第一区域之外进行事件上报的相关信息，所述第一区域为允许所述终端进行事件上报的区域；
    所述终端接收与所述第一信息相匹配的事件上报配置信息；
    所述终端根据所述事件上报配置信息，进行事件上报。
  2. 根据权利要求1所述的方法，其中，所述第一信息包括以下至少一项：
    第二区域，所述第二区域用于指示所述终端期望进行事件上报的区域；
    上报指示，所述上报指示用于指示所述终端是否支持在所述第一区域之外进行事件上报，或者指示所述终端在所述第一区域之外是否进行事件上报，或者指示关于所述终端在所述第一区域之外进行事件上报的至少一个等级；
    区域使用指示，所述区域使用指示用于指示正向使用所述第一区域，或反向使用所述第一区域。
  3. 根据权利要求2所述的方法，其中，所述上报指示为对于所述第一区域的全局互斥设置。
  4. 根据权利要求1至3任一项所述的方法，其中，所述第一区域是根据所述第二区域确定的。
  5. 根据权利要求1至4任一项所述的方法，其中，所述事件上报配置信息包括以下至少一项：
    目标指示信息，所述目标指示信息用于指示所述终端在所述第一区域之外是否需要进行事件上报；
    上报策略，所述上报策略用于指示终端进行事件上报的至少一个约束条件。
  6. 根据权利要求5所述的方法，其中，所述终端根据所述事件上报配置信息，进行事件上报，包括以下至少一项：
    在所述事件上报配置信息包括所述目标指示信息，且所述目标指示信息指示所述终端在所述第一区域之外不需要进行事件上报的情况下，所述终端在所述第一区域之外不进行事件上报；
    在所述事件上报配置信息包括所述目标指示信息和所述上报策略，且所述目标指示信息指示所述终端在所述第一区域之外需要进行事件上报的情况下，所述终端在所述第一区域之外，根据所述上报策略进行事件上报；
    在所述事件上报配置信息包括所述目标指示信息，且所述上报配置信息不包括所述上报策略，且所述目标指示信息指示所述终端在所述第一区域之外需要进行事件上报的情况下，所述终端在所述第一区域之外不进行事件上报，或者，所述终端在所述第一区域之外基于实现进行事件上报；
    在所述第一信息包括所述上报指示，且所述上报指示指示在所述第一区域之外不进行事件上报的情况下，所述终端在所述第一区域之外不进行事件上报；
    在所述第一信息包括所述上报指示，且所述上报指示指示在所述第一区域之外进行事件上报，且所述事件上报配置信息包括所述上报策略的情况下，所述终端在所述第一区域之外，根据所述上报策略进行事件上报；
    在所述第一信息包括所述上报指示，且所述上报指示指示在所述第一区域之外进行事件上报，且所述事件上报配置信息不包括所述上报策略的情况下，所述终端在所述第一区域之外不进行事件上报，或者，所述终端在所述第一区域之外基于实现进行事件上报；
    在所述第一信息包括所述上报指示，且所述上报指示指示第一等级，且所述事件上报配置信息不包括所述上报策略的情况下，所述终端在所述第一区域之外不进行事件上报；
    在所述第一信息包括所述上报指示，且所述上报指示指示第二等级，且所述事件上报配置信息包括所述上报策略的情况下，所述终端在所述第一区域之外且在第二区域之内，根据所述上报策略进行事件上报，所述第二区域用于指示所述终端期望进行事件上报的区域；
    在所述第一信息包括所述上报指示，且所述上报指示指示第三等级，且所述事件上报配置信息包括所述上报策略的情况下，所述终端在所述第一区域之外，根据与所述上报策略进行事件上报；
    在所述第一信息包括所述上报指示，且所述上报指示指示所述第二等级或所述第三等级，且所述事件上报配置信息不包括所述上报策略的情况下，所述终端在所述第一区域之外不进行事件上报，或者，所述终端在所述第一区域之外基于实现进行事件上报。
  7. 根据权利要求5或6所述的方法，其中，所述上报策略包括以下至少一项：
    事件上报的最多上报次数；
    相邻两次事件上报的最小时间间隔；
    事件上报的触发条件，其中，所述触发条件用于指示除所述最小时间间隔、所述最多上报次数之外的门限信息。
  8. 根据权利要求7所述的方法，其中，所述终端根据所述上报策略进行事件上报，包括：
    所述终端根据所述最多上报次数、所述最小时间间隔、所述触发条件中的至少一项，执行有条件地事件上报。
  9. 根据权利要求5至8中任一项所述的方法，其中，所述第一信息还包括策略集，其中，所述策略集包括至少一个候选的上报策略，所述事件上报配置信息中包括的上报策略，是根据所述策略集中的其中一个候选的上报策略确定的。
  10. 根据权利要求1至9中任一项所述的方法，其中，所述方法还包括：
    在所述第一信息中包括的至少一项信息发生变化的情况下，所述终端发送第三信息，其中，所述第三信息包括所述第一信息中发生变化的信息。
  11. 根据权利要求10所述的方法，其中，所述方法还包括：
    所述终端接收第四信息，其中，所述第四信息包括所述第一区域和所述事件上报配置信息中的至少一项，所述第四信息是根据所述第三信息确定的；
    所述终端根据所述第四信息，进行事件上报。
  12. 根据权利要求1至11中任一项所述的方法，其中，所述终端发送第一信息，包括：
    所述终端发送目标消息，所述目标消息携带有所述第一信息；
    其中，所述目标消息包括以下至少一项：
    注册请求消息；
    位置隐私设置请求消息；
    上行非接入层传输消息。
  13. 一种事件上报方法，所述方法包括：
    第一网络侧设备获取终端的第一信息，其中，所述第一信息用于指示所述终端在第一区域之外进行事件上报的相关信息，所述第一区域为允许所述终端进行事件上报的区域；
    所述第一网络侧设备获取与所述第一信息相匹配的事件上报配置信息；
    所述第一网络侧设备发送所述上报配置信息给所述终端。
  14. 根据权利要求13所述的方法，其中，所述第一信息包括以下至少一项：
    第二区域，所述第二区域用于指示所述终端期望进行事件上报的区域；
    上报指示，所述上报指示用于指示所述终端是否支持在所述第一区域之外进行事件上报，或者指示所述终端在所述第一区域之外是否进行事件上报，或者指示关于所述终端在所述第一区域之外进行事件上报的等级；
    区域使用指示，所述区域使用指示用于指示正向使用所述第一区域，或反向使用所述第一区域。
  15. 根据权利要求14所述的方法，其中，所述上报指示为对于所述第一区域的全局互斥设置。
  16. 根据权利要求13至15任一项所述的方法，其中，所述第一区域是根据所述第二区域确定的。
  17. 根据权利要求13至16任一项所述的方法，其中，所述事件上报配置信息包括以下至少一项：
    目标指示信息，所述目标指示信息用于指示所述终端在所述第一区域之外是否需要进行事件上报；
    上报策略，所述上报策略用于指示终端进行事件上报的至少一个约束条件。
  18. 根据权利要求17所述的方法，其中，所述上报策略包括以下至少一项：
    事件上报的最多上报次数；
    相邻两次事件上报的最小时间间隔；
    事件上报的触发条件，其中，所述触发条件用于指示除所述最小时间间隔、所述最多上报次数之外的门限信息。
  19. 根据权利要求17或18所述的方法，其中，在所述事件上报配置信息中包括所述上报策略的情况下，所述第一网络侧设备获取与所述第一信息相匹配的事件上报配置信息，包括以下至少一项：
    在上报指示指示所述终端支持在所述第一区域之外进行事件上报，或者指示所述终端在所述第一区域之外进行事件上报，或者指示第二等级或第三等级的情况下，所述第一网络侧设备根据定位业务类型和所述终端与定位相关的签约信息，确定所述事件上报配置信息；
    或者，
    在所述上报指示指示所述终端支持在所述第一区域之外进行事件上报，或者指示所 述终端在所述第一区域之外进行事件上报，或者指示所述第二等级或所述第三等级的情况下，所述第一网络侧设备根据从第四网络侧设备中接收到的上报策略，确定所述事件上报配置信息；
    或者，
    在所述第一信息还包括策略集，且所述上报指示指示所述终端支持在所述第一区域之外进行事件上报，或者指示所述终端在所述第一区域之外进行事件上报，或者指示所述第二等级或所述第三等级的情况下，所述第一网络侧设备根据定位业务类型，从所述策略集中选择一个候选的上报策略，并根据选出的候选的上报策略，确定所述事件上报配置信息，其中，所述策略集包括至少一个候选的上报策略。
  20. 根据权利要求19所述的方法，其中，所述第一网络侧设备接收所述第四网络侧设备发送的上报策略的过程，包括：
    所述第一网络侧设备接收所述第四网络侧设备发送的定位服务请求，其中，所述定位服务请求中携带有上报策略。
  21. 根据权利要求13至20中任一项所述的方法，其中，所述第一网络侧设备发送所述事件上报配置信息给所述终端，包括：
    所述第一网络侧设备通过第三网络侧设备和第五网络侧设备，将所述事件上报配置信息发送给所述终端。
  22. 根据权利要求13至21中任一项所述的方法，其中，所述方法还包括：
    所述第一网络侧设备发送第二信息给第四网络侧设备，其中，所述第二信息包括以下至少一项：
    所述第一区域；
    上报指示，所述上报指示用于指示所述终端是否支持在所述第一区域之外进行事件上报，或者指示所述终端在所述第一区域之外是否进行事件上报；
    所述事件上报配置信息；
    区域使用指示，所述区域使用指示用于指示正向使用所述第一区域，或反向使用所述第一区域；
    目标区域错误原因，其中，所述目标区域错误原因用于指示目标区域与第二区域之间无重合区域或者所述目标区域存在逻辑错误，所述目标区域为期望所述终端进行事件上报的区域，所述第二区域用于指示所述终端期望进行事件上报的区域。
  23. 根据权利要求13至22中任一项所述的方法，其中，所述第一网络侧设备获取终端的第一信息，包括：
    所述第一网络侧设备从第二网络侧设备中获取所述第一信息，其中，所述第二网络侧设备中存储的所述第一信息是所述终端通过第三网络侧设备发送给所述第二网络侧设备的。
  24. 根据权利要求13至23中任一项所述的方法，其中，所述方法还包括：
    在所述第一网络侧设备订阅了所述终端的信息的情况下，所述第一网络侧设备获取第二网络侧设备提供的第三信息，其中，所述第三信息包括所述第一信息中发生变化的信息，所述第二网络侧设备中存储的所述第三信息是所述终端通过第三网络侧设备发送给所述第二网络侧设备的。
  25. 根据权利要求24所述的方法，其中，所述方法还包括：
    所述第一网络侧设备根据所述第三信息更新第四信息，其中，所述第四信息包括所述第一区域和所述事件上报配置信息中的至少一项；
    所述第一网络侧设备将更新后的所述第四信息发送给所述终端。
  26. 一种事件上报装置，所述装置包括：
    第一发送模块，用于发送第一信息，其中，所述第一信息用于指示终端在第一区域之外进行事件上报的相关信息，所述第一区域为允许所述终端进行事件上报的区域；
    第一接收模块，用于接收与所述第一信息相匹配的事件上报配置信息；
    第一处理模块，用于根据所述事件上报配置信息，进行事件上报。
  27. 根据权利要求26所述的装置，其中，所述第一信息包括以下至少一项：
    第二区域，所述第二区域用于指示所述终端期望进行事件上报的区域；
    上报指示，所述上报指示用于指示所述终端是否支持在所述第一区域之外进行事件上报，或者指示所述终端在所述第一区域之外是否进行事件上报，或者指示关于所述终端在所述第一区域之外进行事件上报的至少一个等级；
    区域使用指示，所述区域使用指示用于指示正向使用所述第一区域，或反向使用所述第一区域。
  28. 根据权利要求27所述的装置，其中，所述上报指示为对于所述第一区域的全局互斥设置。
  29. 根据权利要求26至28任一项所述的装置，其中，所述第一区域是根据所述第二区域确定的。
  30. 根据权利要求26至29任一项所述的装置，其中，所述事件上报配置信息包括以下至少一项：
    目标指示信息，所述目标指示信息用于指示所述终端在所述第一区域之外是否需要进行事件上报；
    上报策略，所述上报策略用于指示终端进行事件上报的至少一个约束条件。
  31. 一种事件上报装置，所述装置包括：
    第一获取模块，用于获取终端的第一信息，其中，所述第一信息用于指示所述终端在第一区域之外进行事件上报的相关信息，所述第一区域为允许所述终端进行事件上报的区域；
    第二获取模块，用于获取与所述第一信息相匹配的事件上报配置信息；
    第二发送模块，用于发送所述上报配置信息给所述终端。
  32. 根据权利要求31所述的装置，其中，所述第一信息包括以下至少一项：
    第二区域，所述第二区域用于指示所述终端期望进行事件上报的区域；
    上报指示，所述上报指示用于指示所述终端是否支持在所述第一区域之外进行事件上报，或者指示所述终端在所述第一区域之外是否进行事件上报，或者指示关于所述终端在所述第一区域之外进行事件上报的至少一个等级；
    区域使用指示，所述区域使用指示用于指示正向使用所述第一区域，或反向使用所述第一区域。
  33. 根据权利要求32所述的装置，其中，所述上报指示为对于所述第一区域的全局互 斥设置。
  34. 根据权利要求31至33任一项所述的装置，其中，所述第一区域是根据所述第二区域确定的。
  35. 根据权利要求31至34任一项所述的装置，其中，所述事件上报配置信息包括以下至少一项：
    目标指示信息，所述目标指示信息用于指示所述终端在所述第一区域之外是否需要进行事件上报；
    上报策略，所述上报策略用于指示终端进行事件上报的至少一个约束条件。
  36. 一种终端，其中，所述终端包括处理器和存储器，所述存储器存储可在所述处理器上运行的程序或指令，所述程序或指令被所述处理器执行时实现如权利要求1至12中任一项所述的事件上报方法的步骤。
  37. 一种网络侧设备，其中，所述网络侧设备包括处理器和存储器，所述存储器存储可在所述处理器上运行的程序或指令，所述程序或指令被所述处理器执行时实现如权利要求13至25中任一项所述的事件上报方法的步骤。
  38. 一种可读存储介质，其中，所述可读存储介质上存储程序或指令，所述程序或指令被处理器执行时实现如权利要求1-12任一项所述的事件上报方法，或者实现如权利要求13至25中任一项所述的事件上报方法的步骤。
PCT/CN2024/086448 2023-04-06 2024-04-07 事件上报方法、装置、设备及存储介质 WO2024208363A1 (zh)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN202310366782.XA CN118785081A (zh) 2023-04-06 2023-04-06 事件上报方法、装置、设备及存储介质
CN202310366782.X 2023-04-06

Publications (1)

Publication Number Publication Date
WO2024208363A1 true WO2024208363A1 (zh) 2024-10-10

Family

ID=92971254

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2024/086448 WO2024208363A1 (zh) 2023-04-06 2024-04-07 事件上报方法、装置、设备及存储介质

Country Status (2)

Country Link
CN (1) CN118785081A (zh)
WO (1) WO2024208363A1 (zh)

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN112584319A (zh) * 2019-09-30 2021-03-30 大唐移动通信设备有限公司 一种位置报告周期调整方法、装置、网络设备及终端
WO2021201552A1 (ko) * 2020-03-30 2021-10-07 삼성전자 주식회사 무선 통신 시스템에서 단말 이동에 따른 측위 제어 방법 및 장치
WO2022170630A1 (en) * 2021-02-15 2022-08-18 Telefonaktiebolaget Lm Ericsson (Publ) Methods, network function nodes and computer readable media for event subscription management
CN115349275A (zh) * 2021-03-12 2022-11-15 北京小米移动软件有限公司 一种位置信息发送方法、装置、设备及存储介质

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN112584319A (zh) * 2019-09-30 2021-03-30 大唐移动通信设备有限公司 一种位置报告周期调整方法、装置、网络设备及终端
WO2021201552A1 (ko) * 2020-03-30 2021-10-07 삼성전자 주식회사 무선 통신 시스템에서 단말 이동에 따른 측위 제어 방법 및 장치
WO2022170630A1 (en) * 2021-02-15 2022-08-18 Telefonaktiebolaget Lm Ericsson (Publ) Methods, network function nodes and computer readable media for event subscription management
CN115349275A (zh) * 2021-03-12 2022-11-15 北京小米移动软件有限公司 一种位置信息发送方法、装置、设备及存储介质

Also Published As

Publication number Publication date
CN118785081A (zh) 2024-10-15

Similar Documents

Publication Publication Date Title
WO2024208363A1 (zh) 事件上报方法、装置、设备及存储介质
CN117939560A (zh) 执行结果上报方法、接收方法、终端及网络侧设备
WO2024032543A1 (zh) 信息获取方法、终端及接入网设备
WO2024104150A1 (zh) 定位方法、装置及通信设备
WO2024032537A1 (zh) 通信方法、设备及可读存储介质
WO2024022398A1 (zh) 托管网络的选网信息的获取方法、终端及网络侧设备
WO2023213242A1 (zh) Ue策略信息的配置方法、装置、第一网络功能及终端
WO2024017035A1 (zh) 位置信息的获取方法、终端及网络侧设备
WO2023185810A1 (zh) 终端路由选择策略ursp确定方法、终端及网络侧设备
WO2024037512A1 (zh) 网络接入方法、装置、终端及通信设备
WO2023198068A1 (zh) 移动性管理方法、装置、终端、网络侧设备及介质
WO2024037632A1 (zh) 通信方法、终端及网络侧设备
WO2023179595A1 (zh) 非3gpp设备的会话通道建立方法、装置及设备
WO2024017023A1 (zh) 允许的nssai的获取方法、终端及网络侧设备
WO2024078589A1 (zh) 信息上报方法、装置、通信设备及存储介质
WO2024208125A1 (zh) Srs配置方法、装置及相关设备
WO2024164189A1 (zh) 参数配置方法及装置、存储介质
EP4398658A1 (en) Information processing method and apparatus, communication device, and readable storage medium
WO2023185727A1 (zh) 信息传输方法及网元
WO2024208325A1 (zh) 定时同步状态变化的处理方法、装置、设备及存储介质
CN116744346A (zh) 网络故障的处理方法、终端、接入网设备及核心网设备
CN117295133A (zh) 通信方法及装置
CN117956568A (zh) 去注册控制方法、装置、终端设备、网元及存储介质
CN117440325A (zh) 连接恢复方法、装置、终端及网络侧设备
CN116634506A (zh) 时间信息应用方法、发送方法、终端及网络侧设备