Method and device for verifying coarse position information of user terminal, electronic equipment and computer program product

Abstract

The invention discloses a method and a device for verifying coarse position information of a user terminal, electronic equipment and a computer program product. The method comprises the steps that a communication request sent by a user terminal is received through a mobility management entity, the communication request comprises an attachment request, a tracking area updating request or a service request, the communication request carries rough position information of the user terminal, and the rough position information is used for preliminarily determining the position of the user terminal; extracting coarse position information of the user terminal from the communication request; and performing position verification on the coarse position information of the user terminal to obtain a position verification result. The technical problem that redundancy exists in coarse position verification in the prior art is solved.

Description

Technical Field

[0001] The present invention relates to the field of communications, and in particular to a method, device, electronic equipment and computer program product for verifying coarse location information of a user terminal. Background Art

[0002] Due to the limited satellite resources, it is a mandatory function for IoT NTN terminals to verify their location and ensure that the terminals can access areas that meet regulatory requirements. In the prior art, the interaction between MME (i.e., mobility management entity) and UE (i.e., user terminal) regarding coarse location information is an optional option based on UE capability indication.

[0003] However, the prior art describes that when the MME receives an attach / TAU / service request from the UE, the MME is required to perform location verification first; after the UE completes authentication with the network, the MME interacts with the UE based on the UE's capability information (i.e., whether coarse location reporting capability is allowed), and performs location verification again, resulting in verification redundancy.

[0004] In addition, for NB IoT accessed by satellite, the terminal interaction in the existing technology requires that the network actively obtains the information from the UE after the UE and the network have interacted securely. After receiving the network's request to obtain information, the UE then feeds back its rough location information to the network, resulting in signaling redundancy between the UE and the network regarding location information, and wasting satellite air interface resources.

[0005] There is a redundancy problem in the above-mentioned prior art for rough position verification, and no effective solution has been proposed yet. Summary of the invention

[0006] The embodiments of the present invention provide a method, device, electronic device and computer program product for verifying coarse location information of a user terminal, so as to at least solve the technical problem of redundancy in coarse location verification in the prior art.

[0007] According to one aspect of an embodiment of the present invention, a method for verifying coarse location information of a user terminal is provided, comprising: receiving, through a mobility management entity, a communication request sent by a user terminal, wherein the communication request comprises: an attachment request, a tracking area update request or a service request, the communication request carries coarse location information of the user terminal, and the coarse location information is used to preliminarily determine the location of the user terminal; extracting the coarse location information of the user terminal from the communication request; performing location verification on the coarse location information of the user terminal to obtain the location verification result.

[0008] Optionally, extracting the coarse location information of the user terminal from the communication request includes: identifying the user terminal capability information carried in the communication request; detecting whether the user terminal capability information contains a preset identification bit, wherein the preset identification bit is used to indicate whether the user terminal supports reporting the coarse location information of the user terminal; in a case where the preset identification bit exists in the user terminal capability information, detecting whether the preset identification bit is a preset value, wherein, in a case where the preset identification bit is the preset value, it indicates that the user terminal supports reporting the coarse location information of the user terminal, and in a case where the preset identification bit is not the preset value, it indicates that the user terminal does not support reporting the coarse location information of the user terminal; in a case where the preset identification bit is the preset value, extracting the coarse location information of the user terminal from the communication request.

[0009] Optionally, the method further includes: when the preset identification bit does not exist in the user terminal capability information, detecting whether the coarse location information of the user terminal exists in the communication request; when the coarse location information of the user terminal exists in the communication request, extracting the coarse location information of the user terminal.

[0010] Optionally, the method also includes: sending a first security mode command message to the user terminal in response to the communication request, wherein the first security mode command message does not carry a location request for obtaining the coarse location information of the user terminal; receiving a first security mode completion message returned by the user terminal in response to the first security mode command message, wherein the first security mode completion message does not carry the coarse location information of the user terminal.

[0011] According to another aspect of an embodiment of the present invention, a method for verifying the coarse location information of a user terminal is also provided, comprising: receiving a communication request sent by a user terminal through a mobility management entity, wherein the communication request is: an attachment request, a tracking area update request, or a service request, and the communication request carries user terminal capability information, and the user terminal capability information is at least used to indicate that the user terminal supports reporting the coarse location information of the user terminal; in response to the communication request, sending a second security mode command message to the user terminal, wherein the second security mode command message carries at least a location request for obtaining the coarse location information of the user terminal; receiving a second security mode completion message returned by the user terminal in response to the second security mode command message, wherein the second security mode completion message carries the coarse location information of the user terminal; performing location verification on the coarse location information of the user terminal to obtain the location verification result.

[0012] Optionally, in response to the communication request, sending a second security mode command message to the user terminal includes: in response to the communication request, authenticating the identity of the user terminal to a mobility management entity to which the user terminal has historically accessed; after the identity authentication is completed, verifying whether the user terminal supports reporting the coarse location information of the user terminal based on the user terminal capability information carried in the communication request; and sending the second security mode command message to the user terminal when the user terminal capability information indicates that the user terminal supports reporting the coarse location information of the user terminal.

[0013] Optionally, in response to the communication request, sending a second security mode command message to the user terminal includes: in response to the communication request, verifying whether the user terminal supports reporting the coarse location information of the user terminal based on the user terminal capability information carried in the communication request, and obtaining a reporting capability verification result; in response to the communication request, authenticating the identity of the mobility management entity to which the user terminal has historically accessed; after the identity authentication is completed and the reporting capability verification result indicates that the user terminal supports reporting the coarse location information of the user terminal, sending the second security mode command message to the user terminal.

[0014] According to another aspect of an embodiment of the present invention, a device for verifying coarse location information of a user terminal is also provided, comprising: a first receiving module, used to receive a communication request sent by a user terminal through a mobility management entity, wherein the communication request comprises: an attachment request, a tracking area update request or a service request, the communication request carries coarse location information of the user terminal, and the coarse location information is used to preliminarily determine the location of the user terminal; an extraction module, used to extract the coarse location information of the user terminal from the communication request; and a first verification module, used to perform location verification on the coarse location information of the user terminal to obtain the location verification result.

[0015] According to another aspect of an embodiment of the present invention, a device for verifying coarse location information of a user terminal is also provided, comprising: a second receiving module, used to receive a communication request sent by a user terminal through a mobility management entity, wherein the communication request is: an attachment request, a tracking area update request, or a service request, and the communication request carries user terminal capability information, and the user terminal capability information is at least used to indicate that the user terminal supports reporting the coarse location information of the user terminal; a sending module, used to send a second security mode command message to the user terminal in response to the communication request, wherein the second security mode command message carries at least a location request for obtaining the coarse location information of the user terminal; a third receiving module, used to receive a second security mode completion message returned by the user terminal in response to the second security mode command message, wherein the second security mode completion message carries the coarse location information of the user terminal; a second verification module, used to perform location verification on the coarse location information of the user terminal to obtain the location verification result.

[0016] According to another aspect of an embodiment of the present invention, there is further provided an electronic device, including a memory and a processor, wherein the memory stores a computer program, and the processor is configured to execute the above-mentioned method for verifying coarse location information of a user terminal through the computer program.

[0017] According to another aspect of an embodiment of the present invention, a computer program product is further provided, comprising computer instructions, which implement the steps of the above-mentioned method for verifying the rough location information of a user terminal when executed by a processor.

[0018] In an embodiment of the present invention, a communication request sent by a user terminal is received by a mobility management entity, wherein the communication request includes: an attachment request, a tracking area update request or a service request, and the communication request carries coarse location information of the user terminal, and the coarse location information is used to preliminarily determine the location of the user terminal; the coarse location information of the user terminal is extracted from the communication request; the coarse location information of the user terminal is positionally verified to obtain a position verification result, thereby achieving the purpose of performing a position verification on the coarse location information of the user terminal once, thereby achieving the technical effect of avoiding redundant verification of the coarse location information of the user terminal, and further solving the redundant technical problem of coarse location verification in the prior art. BRIEF DESCRIPTION OF THE DRAWINGS

[0019] The drawings described herein are used to provide a further understanding of the present invention and constitute a part of this application. The exemplary embodiments of the present invention and their descriptions are used to explain the present invention and do not constitute an improper limitation of the present invention. In the drawings:

[0020] Figure 1 A method for verifying rough location information of a user terminal according to an embodiment of the present invention is provided. Figure 1;

[0021] Figure 2 is a schematic diagram for an E-UTRAN initial attachment according to an embodiment of the present invention;

[0022] Figure 3 is a schematic diagram of a tracking area update involving a serving gateway change according to an embodiment of the present invention;

[0023] Figure 4 is a schematic diagram of a tracking area update that does not involve a serving gateway change according to an embodiment of the present invention;

[0024] Figure 5 is a schematic diagram of a service request triggered by a UE according to an embodiment of the present invention;

[0025] Figure 6 A schematic diagram of verifying the rough location information of a user terminal for an initial attachment to an E-UTRAN according to an embodiment of the present invention Figure 1 ;

[0026] Figure 7 A method for verifying rough location information of a user terminal according to an embodiment of the present invention is provided. Figure 2 ;

[0027] Figure 8 A schematic diagram of verifying the rough location information of a user terminal for an initial attachment to an E-UTRAN according to an embodiment of the present invention Figure 2 ;

[0028] Fig. 9 A schematic diagram of verifying the rough location information of a user terminal for an initial attachment to an E-UTRAN according to an embodiment of the present invention Figure 3 ;

[0029] Fig.10 A schematic diagram of a rough location information verification device for a user terminal according to an embodiment of the present invention Figure 1 ;

[0030] Fig.11 A schematic diagram of a rough location information verification device for a user terminal according to an embodiment of the present invention Figure 2 ;

[0031] Fig.12 It is a structural block diagram of a computer terminal according to an embodiment of the present invention. DETAILED DESCRIPTION

[0032] In order to enable those skilled in the art to better understand the scheme of the present invention, the technical scheme in the embodiments of the present invention will be clearly and completely described below in conjunction with the drawings in the embodiments of the present invention. Obviously, the described embodiments are only part of the embodiments of the present invention, not all of the embodiments. Based on the embodiments of the present invention, all other embodiments obtained by ordinary technicians in this field without creative work should fall within the scope of protection of the present invention.

[0033] It should be noted that the terms "first", "second", etc. in the specification and claims of the present invention and the above-mentioned drawings are used to distinguish similar objects, and are not necessarily used to describe a specific order or sequence. It should be understood that the data used in this way can be interchanged where appropriate, so that the embodiments of the present invention described herein can be implemented in an order other than those illustrated or described herein. In addition, the terms "including" and "having" and any variations thereof are intended to cover non-exclusive inclusions, for example, a process, method, system, product or device that includes a series of steps or units is not necessarily limited to those steps or units that are clearly listed, but may include other steps or units that are not clearly listed or inherent to these processes, methods, products or devices.

[0034] According to an embodiment of the present invention, an embodiment of a method for verifying coarse location information of a user terminal is provided. It should be noted that the steps shown in the flowchart of the accompanying drawings can be executed in a computer system such as a set of computer executable instructions, and although a logical order is shown in the flowchart, in some cases, the steps shown or described may be executed in an order different from that shown here.

[0035] Figure 1 A method for verifying rough location information of a user terminal according to an embodiment of the present invention is provided. Figure 1 ,like Figure 1 As shown, the method comprises the following steps:

[0036] Step S102, receiving a communication request sent by a user terminal through a mobility management entity, wherein the communication request includes: an attach request, a tracking area update request or a service request, and the communication request carries coarse location information of the user terminal, and the coarse location information is used to preliminarily determine the location of the user terminal;

[0037] Step S104, extracting the rough location information of the user terminal from the communication request;

[0038] Step S106: verify the rough location information of the user terminal to obtain a location verification result.

[0039] In an embodiment of the present invention, a communication request sent by a user terminal is received by a mobility management entity, wherein the communication request includes: an attachment request, a tracking area update request or a service request, and the communication request carries coarse location information of the user terminal, and the coarse location information is used to preliminarily determine the location of the user terminal; the coarse location information of the user terminal is extracted from the communication request; the coarse location information of the user terminal is positionally verified to obtain a position verification result, thereby achieving the purpose of performing a position verification on the coarse location information of the user terminal once, thereby achieving the technical effect of avoiding redundant verification of the coarse location information of the user terminal, and further solving the redundant technical problem of coarse location verification in the prior art.

[0040] In the above step S102, the Mobility Management Entity (MME) is a core network element in the new generation wireless communication system, especially in LTE and EPS networks. It is mainly responsible for processing the user's mobility management function to ensure that the user equipment can successfully access the network and perform data transmission.

[0041] In the above step S102, user equipment (UE) refers to a terminal device used by a user in a wireless communication network.

[0042] In the above step S102, the communication request may be a request initiated by the user terminal to the wireless communication network, and the communication request may be any one of an attach request, a tracking area update request and a service request.

[0043] In the above step S102, the attachment request may be an initial attachment to E-UTRAN, indicating a process of establishing a connection between a user terminal and a network, wherein E-UTRAN is an Evolved UMTS Terrestrial Radio Access Network, which is an evolved UMTS terrestrial radio access network and an access network part in an LTE (Long Term Evolution) network. Compared with a traditional UTRAN architecture, E-UTRAN adopts a flatter network structure; UMTS (Universal Mobile Telecommunications System) is a universal mobile communications system and an important representative of the third generation (3G) mobile phone technology.

[0044] Figure 2 is a schematic diagram for an E-UTRAN initial attachment according to an embodiment of the present invention, such as Figure 2As shown, the eNodeB derives the MME (mobile management entity) address from the RRC (radio resource control) parameters carrying the old GUMMEI (globally unique MME identity), the indicated selected network, and the radio access technology (NB-IoT or broadband E-UTRAN). If the MME is not associated with the eNodeB, or the old GUMMEI is not available, the eNodeB selects an MME according to the preset "MME selection function". The eNodeB forwards the attachment request message in the S1-MME control message (initial UE message), and sends the selected network of the cell from which the message is received, the CSG (closed subscriber group) access mode, the CSG ID, the L-GW (local gateway) address, and the TAI (tracking area identifier) ​​+ ECGI (E-UTRAN cell global identifier) ​​to the new MME. If the UE attaches through a CSG cell or a hybrid cell, the CSG ID is provided. If the UE attaches through a hybrid cell, the CSG access mode is provided. If the CSG access mode is not provided but the CSG ID is provided, the MME shall treat the cell as a CSG cell. If the eNodeB has a co-located L-GW, it includes the L-GW address in the Initial UE message sent to the MME.

[0045] Optionally, if an IAB indication is received from the UE, the eNodeB selects an MME that supports IAB operation and includes the IAB indication in an initial UE message sent to the MME.

[0046] Optionally, if the MME is not configured to support emergency connections, the MME shall reject any connection request indicating a connection type of "Emergency".

[0047] Optionally, if the MME is not configured to support RLOS attach, the MME shall reject any attach request indicating attach type "RLOS".

[0048] Optionally, if the UE has included a preferred network behavior and the content supported by the UE in the preferred network behavior is incompatible with the network support, for example, the UE indicates that only control plane CIoT EPS optimization is supported and the MME only supports user plane CIoTEPS optimization, then the MME should reject the attachment request using an appropriate cause value (for example, a cause value to avoid retrying on this PLMN).

[0049] Optionally, to assist positioning services, the eNodeB indicates the coverage level of the UE to the MME.

[0050] Optionally, if the UE supports MT-EDT as indicated in the UE network capabilities, the MME shall take this parameter into account in order to provide the MT-EDT indication to the Serving GW during PDN connection establishment or mobility procedures and to handle data size information that may be received during the MME's downlink data notification procedure.

[0051] Optionally, in the case of satellite access for cellular IoT, the MME may verify the UE location and determine whether a public land mobile network PLMN is allowed to operate at the UE location. If the UE receives an Attach Reject message with a cause value indicating that the selected PLMN is not allowed to operate at the current UE location, the UE shall attempt to select a preset PLMN.

[0052] Optionally, if there is no UE context for the UE anywhere in the network, if the attach request is not integrity protected, or if the integrity check fails, authentication and NAS security setup must be performed to activate integrity protection and NAS encryption. Otherwise, it is optional. If you want to change the NAS security algorithm, perform NAS security setup in this step. Among them, the authentication and NAS security setup functions are defined in the preset "Security Function" rule.

[0053] Optionally, if the UE supports RACS as indicated in the UE Network Capabilities and if the UE has a UE Radio Capability ID assigned for the selected PLMN, authentication and NAS security setup must be performed to activate integrity protection and NAS ciphering. The MME shall request the UE to provide the UE Radio Capability Identifier in the Security Mode Command and the UE shall include the UE Radio Capability Identifier in the Security Mode Command Accept for the supported UE radio capabilities.

[0054] Optionally, for satellite access over NB-IoT, if the UE indicates support for reporting its coarse location information, the MME can request the UE to send its coarse location information by setting the coarse location information request in the security mode command message, and then the UE reports its coarse location information to the MME in the security mode complete message. In order to perform UE location verification, the MME provides the reported coarse location information to the E-SMLC.

[0055] Optionally, if the MME is configured to support emergency attach for unauthenticated IMSIs and the UE indicates the attach type is "emergency", the MME skips authentication and security setup, or the MME accepts that authentication may have failed and continues with the attach procedure.

[0056] Optionally, if the MME is configured to support RLOS attachment and the UE indicates an attachment type "RLOS" in accordance with local regulations and operator policy, the MME may skip authentication and security setup, or if security information is available or obtainable from the HSS, the MME may perform authentication and continue with the attachment procedure regardless of the authentication result.

[0057] Optionally, all NAS messages shall be protected by the NAS security capabilities (integrity and ciphering) indicated by the MME, unless the UE is in emergency state or RLOS connected state and has not been successfully authenticated.

[0058] In the above step S102, the tracking area update request is used to trigger a tracking area update process (Tracking Area Update, TAU), which includes: a tracking area update involving a serving gateway change, and a tracking area update not involving a serving gateway change.

[0059] Figure 3 is a schematic diagram of a tracking area update involving a serving gateway change according to an embodiment of the present invention, such as Figure 3 As shown, the UE initiates the TAU procedure by sending a TAU Request (UE Core Network Capabilities, IMS Network Capabilities, Preferred Network Behavior, Support for Enhanced Coverage Usage Restriction, Old GUTI, Old GUT1 Type, Last Visited TAI, Active Flag, Signaling Active Flag, EPS Bearer Status, P TMSI Signature, Additional GUTI, eKSI, NAS Sequence Number, NAS-MAC, KSI, Voice Domain Preference and UE's Usage Settings, UE has UE Radio Capability ID assigned for the selected PLMN, Requested IMSI Offset, Release Request Indication, Paging Restriction Information, Unavailable Period Duration, Unavailable Period Start) message to the eNodeB along with RRC parameters indicating the selected network and the old GUT. MMEI. The exception is that if the TAU is triggered for the purpose of load rebalancing, the old GUTI is not included in the RRC parameters. The UE shall set the old GUTI type to indicate whether the old GUTI is a native GUTI or mapped from the P-TMSI and RAI.

[0060] Optionally, if the UE's TIN indicates "GUTI" or "RAT-related TMSI" and the UE holds a valid GUTI, the old GUTI indicates this valid GUTI. If the UE's TIN indicates "P TMSI" and the UE holds a valid P TMSI and related RAI, these two elements are indicated as the old GUTI. The P TMSI and RAI are mapped to the GUTI according to preset regulations. When the UE is in connected mode (e.g. in URA_PCH) when reselecting e UTRAN, the UE shall set its TIN to "P TMSI".

[0061] Optionally, if the UE holds a valid GUTI and the old GUTI indicates a GUTI mapped from P-TMSI and RAI, the UE indicates the GUTI as an additional GUTI. If the old GUTI indicates a GUTI mapped from P-TMSI and RAI and the UE has a valid P-TMSI signature, the P-TMSI signature shall be included.

[0062] Optionally, the additional GUTI in the TRACKING AREA UPDATE REQUEST message allows the new MME to find any existing UE context stored in the new MME when the old GUTI indicates a value mapped from P-TMSI and RAI; or, when the UE only supports E-UTRAN, it identifies itself with the old GUTI and sets the old GUTI type to "local".

[0063] Optionally, the RRC parameter "old GUMMEI" takes the value from the identifier signaled as the old GUTI according to the above rules. For a combined MME / SGSN, the eNodeB is configured to route the MME code of the combined node to the same combined node. The eNodeB is also configured to route the MME code of the GUTI generated by the mapping of the UE to the P TMSI allocated by the combined node. This eNodeB configuration can also be used for individual nodes to avoid changes in nodes in the pool caused by inter-RAT mobility.

[0064] Optionally, the last visited TAI should be included to help the MME generate a good TAI list for any subsequent TAU ​​Accept message. Selected Network indicates the selected network. Active Flag is a request by the UE to activate the radio and S1 bearers of all active EPS bearers through the TAU procedure when the UE is in ECM-IDLE state. Signaling Active Flag is a request by the UE to maintain the NAS signaling connection using control plane CIoT EPS optimization after the tracking area update procedure is completed in order to transfer pending data using data transmission or NAS signaling in control plane CIoT EPS optimization. The EPS bearer status indicates each EPS bearer active in the UE. The TAU Request message shall be integrity protected by NAS-MAC. If the UE has valid EPS security parameters, eKSI, NAS sequence number and NAS-MAC are included. NAS sequence number indicates the sequence number of the NAS message. KSI is included if the UE indicates GUTI mapped from P TMSI in the information element "Old GUTI".

[0065] Optionally, in the RRC connection establishment signaling associated with the TAU request, the UE indicates that it supports CIoT EPS optimization related to MME selection.

[0066] Optionally, for UEs using CIoT EPS optimization without any activated PDN connection, the TAU request message does not contain the active flag or EPS bearer status. For UEs with service gap timers running in the UE, the UE shall not set the active flag and signaling active flag in the TAU request message, except for network access for regulatory priority services such as emergency services or exception reporting.

[0067] Optionally, if the UE has any PDN connection with PDN type "non-IP" or "Ethernet", the UE shall send the EPS bearer status in the TAU request message.

[0068] Optionally, the UE sets the voice domain preference according to its configuration and the UE's usage settings.

[0069] Optionally, if the UE needs to enable extended idle mode DRX, the UE will include an extended idle mode-DRX parameters information element even if the DRX parameters of the extended idle mode have been negotiated before.

[0070] Optionally, if the UE supports allocation of WUS assistance information from the MME to assist the wake-up signal (WUS) group decision of the eNodeB, the UE may include UE paging probability information.

[0071] Optionally, if the UE includes a preferred network behavior, it defines the network behavior that the UE expects to be available in the network.

[0072] Optionally, if the UE supports RACS, and if the UE is provided with a UE Radio Capability ID for a selected PLMN (i.e. an assigned PLMN or an assigned manufacturer for a specific PLMN), the UE includes a flag indicating that it has an assigned UE Radio Capability ID for the selected PLMN, but the actual UE Radio Capability ID is provided to the MME after the security context is established.

[0073] Optionally, if the multi-USIM UE wants to enter the ECM-IDLE state, it includes a release request indication and optionally provides paging restriction information.

[0074] Optionally, if a multi-USIM UE needs to modify the paging occasion to avoid paging conflicts, it sends a requested IMSI offset to the MME in order to signal an alternative IMSI.

[0075] Optionally, in case of satellite access for Cellular IoT, the MME may verify the UE location and determine whether the PLMN is allowed to operate at the UE location. If the UE receives a TAU Reject message with a cause value indicating that the selected PLMN is not allowed to operate at the current UE location, the UE shall attempt to select the specified PLMN.

[0076] Optionally, if the eNodeB used by the UE provides discontinuous coverage (eg, for satellite access with discontinuous coverage), the UE may include the unavailability period duration and the unavailability period start.

[0077] Optionally, if the integrity check of the TAU Request message fails, authentication MUST be performed. The authentication function is defined in "Security Functions". The encryption procedure is described in "Security Functions". If GUTI allocation is to be performed and the network supports encryption, the NAS message SHOULD be encrypted.

[0078] Optionally, if this TAU Request is received for a UE already in ECM_CONNECTED state, and the PLMN-ID of the TAI sent by the eNodeB is different from the GUTI contained in the TAU Request message, the MME shall delay authentication of the UE until after the TAU Complete message.

[0079] It should be noted that the MME delays authentication so that the UE first updates its registered PLMN-ID to the new PLMN-ID selected by the RAN during handover. The MME provides the new PLMN-ID to the UE as part of the GUTI in the TAU Accept message. This ensures that the network and the UE use the same PLMN-ID when deriving the Kasme key.

[0080] It should be noted that if the new MME is configured to allow provision of emergency bearer services to unauthenticated UEs, the new MME behaves as follows:

[0081] - In the case where the UE has only emergency bearer services, the MME either skips the authentication and security procedures or accepts that authentication may fail and continues with the tracking area update procedure;

[0082] - In case the UE has both emergency and non-emergency bearer services and the authentication fails, the MME continues to track the area update procedure and deactivates all non-emergency PDN connections as specified.

[0083] It should be noted that if the new MME is configured to allow restricted local operator services, the new MME may skip the authentication and security procedures according to local regulations and operator policies, or may perform authentication if security parameters are available or obtainable from the HSS, and continue to track the area update process regardless of the authentication result.

[0084] It should be noted that if the UE has a UE Radio Capability ID assigned for the selected PLMN, the MME may request the UE to provide the UE Radio Capability Identifier in the Security Mode Command if the MME needs to obtain the UE Radio Capability Identifier from the UE, such as in inter-PLMN mobility. If the MME asks, the UE shall include the UE Radio Capability ID in the Security Mode Command Accept to support the UE radio capabilities.

[0085] It should be noted that in the case of satellite access of NB-IoT, if the UE indicates support for reporting its coarse location information, the MME can request the UE to report its coarse positioning information by setting the coarse location information request in the security mode command message, and then the UE reports its coarse location information in the security mode completion message. In order to perform UE location verification, the MME provides the reported coarse location information to the E-SMLC.

[0086] Figure 4 is a schematic diagram of a tracking area update that does not involve a serving gateway change according to an embodiment of the present invention, such as Figure 4 As shown, the eNodeB derives the MME address from the RRC parameters carrying the old GUMMEI, the indicated selected network and RAT (NB-IoT or WB-E-UTRAN). If the GUMMEI is not associated with the eNodeB, or the GUMMEI is not available, or the UE indicates that the TAU procedure is triggered by load rebalancing, the eNodeB selects the MME according to the "MME selection function". The eNodeB forwards the TAU request message to the MME together with the CSG access mode, CSG ID, the TAI+ECGI of the cell from which the message is received, and the selected network. If the UE sends the TAU request via a CSG cell or a hybrid cell, the CSG ID is provided by the RAN. If the UE sends the TAU request message via a hybrid cell, the CSG access mode is provided. If the CSG access mode is not provided, but the CSG ID is provided, the MME shall treat the cell as a CSG cell. For SIPTO on a local network with a standalone GW architecture, if the target cell is in the local home network, the eNodeB includes the local home network ID in the initial UE message and uplink NAS transport messages.

[0087] Optionally, to assist positioning services, the eNodeB indicates the coverage level of the UE to the MME.

[0088] Optionally, if the MME supports RACS, and the MME detects that the selected PLMN is different from the UE's currently registered PLMN, the MME provides the eNodeB with the UE radio capability ID of the newly selected PLMN in the UE context.

[0089] Optionally, in case of satellite access for Cellular IoT, the MME may verify the UE location and determine whether the PLMN is allowed to operate at the UE location. If the UE receives a TAU Reject message with a cause value indicating that the selected PLMN is not allowed to operate at the current UE location, the UE shall attempt to select the specified PLMN.

[0090] Optionally, if the integrity check of the TAU Request message fails, authentication MUST be performed. The authentication function is defined in "Security Functions". The encryption procedure is described in "Security Functions". If GUTI allocation is to be performed and the network supports encryption, the NAS message SHOULD be encrypted.

[0091] Optionally, if this TAU Request is received for a UE already in ECM_CONNECTED state, and the PLMN-ID of the TAI sent by the eNodeB is different from the GUTI contained in the TAU Request message, the MME shall delay authentication of the UE until after the TAU Complete message.

[0092] It should be noted that the MME delays authentication so that the UE first updates its registered PLMN-ID to the new PLMN-ID selected by the RAN during handover. The MME provides the new PLMN-ID to the UE as part of the GUTI in the TAU Accept message. This ensures that the network and the UE use the same PLMN-ID when deriving the Kasme key.

[0093] It should be noted that if the new MME is configured to allow provision of emergency bearer services to unauthenticated UEs, the new MME behaves as follows:

[0094] - In the case where the UE has only emergency bearer services, the MME either skips the authentication and security procedures or accepts that authentication may fail and continues with the tracking area update procedure;

[0095] - In case the UE has both emergency and non-emergency bearer services and authentication fails, the MME continues with the tracking area update procedure and deactivates all non-emergency PDN connections.

[0096] It should be noted that if the new MME is configured to support restricted local operator services, the new MME may skip the authentication and security procedures according to local regulations and operator policies, or may perform authentication if security parameters are available or obtainable from the HSS, and continue to track the area update process regardless of the authentication result.

[0097] It should be noted that if the UE has a UE Radio Capability ID assigned for the selected PLMN, the MME may request the UE to provide the UE Radio Capability Identifier in the Security Mode Command if the MME needs to obtain the UE Radio Capability Identifier from the UE, such as in inter-PLMN mobility. If the MME asks, the UE shall include the UE Radio Capability ID in the Security Mode Command Accept to support the UE radio capabilities.

[0098] It should be noted that in the case of satellite access of NB-IoT, if the UE indicates support for reporting its coarse location information, the MME can request the UE to report its coarse positioning information by setting the coarse location information request in the security mode command message, and then the UE reports its coarse location information to the MME in the security mode completion message. In order to perform UE location verification, the MME provides the reported coarse location information to the E-SMLC.

[0099] In the above step S102, the service request may be triggered by the UE, and is used to initiate to the network when the UE needs to establish or restore a wireless connection.

[0100] Figure 5 is a schematic diagram of a UE-triggered service request according to an embodiment of the present invention, such as Figure 5 As shown, the eNodeB forwards the NAS message to the MME. The NAS message is encapsulated in the S1-AP: Initial UE message (NAS message, TAI+ECGI of the serving cell, S-TMSI, CSG ID, CSG access mode, RRC establishment cause) or in another S1-AP message for the UE in ECM-CONNECTED (e.g. uplink NAS transport message). If the MME cannot process the service request, it shall reject it. If the UE sends the service request message via a CSG cell or a hybrid cell, the CSG ID is provided. If the UE sends the service request message via a hybrid cell, the CSG access mode is provided. If the CSG access mode is not provided, but the CSG ID is provided, the MME shall treat the cell as a CSG cell.

[0101] Optionally, if a CSG ID is indicated and no CSG access mode is provided and there is no subscription data for this CSG ID and associated PLMN, or the CSG subscription has expired, the MME shall reject the service request with an appropriate reason. The UE shall remove the CSG ID and associated PLMN of the cell from which the UE initiated the service request procedure from the allowed CSG list (if any).

[0102] Optionally, for a UE with emergency EPS bearers, i.e., at least one EPS bearer has an ARP value reserved for emergency services, if CSG access restrictions do not allow the UE to obtain normal services, the MME shall deactivate all non-emergency bearers and accept the service request.

[0103] Optionally, if LIPA is active for the PDN connection and if the cell accessed by the UE is not linked to the L-GW from which the UE initiated the LIPA PDN connection, the MME shall not request the eNodeB to establish the bearer for the LIPA PDN, but shall request to disconnect the LIPA PDN. If the UE has no other PDN connection, the MME shall reject the service request with an appropriate cause value, causing the UE to detach, skip the following steps of the procedure, and initiate the release of core network resources using an implicit MME-initiated detach procedure.

[0104] Optionally, if a "DDN post-failure availability" monitoring event or a "UE reachability" monitoring activity is configured for the UE in the MME, the MME sends an event notification.

[0105] Optionally, to assist positioning services, the eNodeB indicates the coverage level of the UE to the MME.

[0106] Optionally, if the MME supports RACS, and the MME detects that the selected PLMN is different from the UE's currently registered PLMN, the MME provides the eNodeB with the UE radio capability ID of the newly selected PLMN in the UE context.

[0107] Optionally, if a Service Request message is received from a UE in ECM-IDLE state without a Release Request indication, the MME shall delete any stored paging restriction information for the UE and stop restricting paging accordingly.

[0108] Optionally, if the service request message includes a release request indication or a paging rejection indication, then:

[0109] -If the service request message includes paging restriction information, the MME may accept or reject the paging restriction information requested by the UE based on the operator policy. If the MME rejects the paging restriction information, the MME deletes any stored paging restriction information from the UE context and discards the paging restriction message requested by the UE. If the MME accepts the paging restriction information from the UE, the MME stores the paging restriction information received from the UE in the UE context. The MME informs the UE of the acceptance / rejection of the requested paging restriction information in the service accept message. If no paging restriction information is provided, paging restriction is not applied;

[0110] - If no bearer is established to trigger the TAU procedure, the context request, response and confirmation process is skipped;

[0111] - The MME triggers the release procedure that initiated the TAU procedure and does not perform the further steps of this procedure. However, the MME may trigger NAS authentication / security before releasing the UE.

[0112] Optionally, in case of satellite access for Cellular IoT, the MME may verify the UE location and determine whether the PLMN is allowed to operate at the UE location. If the UE receives a Service Reject message with a cause value indicating that the selected PLMN is not allowed to operate at the current UE location, the UE shall attempt to select the specified PLMN.

[0113] Optionally, perform NAS authentication / security procedures defined in "Security Functions".

[0114] Optionally, if the MME is configured to support RLOS and the UE has indicated an attachment type "RLOS" in accordance with local regulations and operator policy, the MME may skip authentication and security setup, or if security information is available or obtainable from the HSS, the MME may perform authentication and continue with the service request process regardless of the authentication result.

[0115] Optionally, in the case of satellite access of NB-IoT, if the UE indicates support for reporting its coarse location information, the MME can request the UE to report its coarse positioning information by setting the coarse location information request in the security mode command message, and then the UE reports its coarse location information to the MME in the security mode completion message. In order to perform UE location verification, the MME provides the reported coarse location information to the E-SMLC.

[0116] In the above step S106, location verification is an important link in the mobile communication network, which is used to confirm whether the current location information of the user terminal (UE) is accurate. This process usually involves multiple network entities and signal interactions to ensure the reliability and accuracy of the location data. The specific implementation method of location verification of the rough location information of the user terminal is as follows:

[0117] Optionally, to ensure that regulatory requirements are met, the network can be configured to enforce that the selected PLMN is allowed to operate at the current UE location by verifying the UE location during the EMM and ESM procedures. In this case, the MME may decide to verify the UE's location when it receives the UE's User Location Information (ULI) using satellite access for Cellular IoT.

[0118] Optionally, in the case of NB-IoT, the UE and MME may support reporting of coarse location information from the UE to the MME during the NAS security mode command process. Such as the attachment process, TAU process and service request process, in the case of NB-IoT, if the UE supports it and the MME has obtained user consent according to the proprietary mechanism of local regulations, the MME may request the UE to report its coarse location information in the NAS security mode command message. If requested, the UE provides its coarse location information in the NAS security mode completion message. The MME provides the received coarse location information to the E-SMLC. The UE indicates that it supports providing coarse location information in the UE network capability IE.

[0119] It should be noted that providing rough UE location information during the SMC process is intended to provide basic support for UE location verification. If additional accuracy or other positioning features are required, it is assumed that the UE and the network support the procedures defined in LPP and TS.

[0120] It should be noted that the coarse location information is similar to the coarse location information field defined in 3GPP TS 36.331.

[0121] Optionally, if the MME determines that the UE is not allowed to operate at the current UE location based on the selected PLMN ID and the identity of the serving cell, or in the case of NB-IoT based on the reply of the E-SMLC and coarse location information is provided to the E-SMLC, the MME shall reject any NAS request with an appropriate cause value. If the UE is already registered to the network when the MME determines that the UE is not allowed to operate at the current UE location, the MME may initiate an explicit detach of the UE. The MME shall not reject the request or detach the UE unless it has sufficiently accurate UE location information to determine that the UE is located in a geographical area where the PLMN is not allowed to operate.

[0122] Alternatively, the area in which the PLMN is allowed to operate may be determined according to local regulations and licensing conditions.

[0123] Optionally, if the MME cannot determine the UE location with sufficient accuracy to make a decision, or if the received ULI is not reliable enough, the MME continues with the mobility management or session management procedure and may initiate the UE location procedure after the mobility management or session management procedure is completed to determine the UE location. If the information received from the E SMLC indicates that the UE is registered to a PLMN that is not allowed to operate at the UE location, the MME shall prepare to detach the UE. In the case of a NAS procedure, the MME shall reject any NAS request to a PLMN that is not allowed to operate at the known UE location and indicate an appropriate cause value, or accept the NAS procedure and initiate the Detach procedure after the UE location is known. In the Detach Request message sent to the UE, the MME shall include an appropriate cause value.

[0124] Optionally, in the case of NB-IoT, whether the interaction with E-SMLC is triggered based on the location information received by the MME during the NAS process, or the interaction with E-SMCL is triggered after the NAS process, depends on the operator's configuration.

[0125] As an optional embodiment, extracting the coarse location information of the user terminal from the communication request includes: identifying the user terminal capability information carried in the communication request; detecting whether there is a preset identification bit in the user terminal capability information, wherein the preset identification bit is used to indicate whether the user terminal supports reporting the coarse location information of the user terminal; in the case where there is a preset identification bit in the user terminal capability information, detecting whether the preset identification bit is a preset value, wherein, in the case where the preset identification bit is a preset value, it indicates that the user terminal supports reporting the coarse location information of the user terminal, and in the case where the preset identification bit is not a preset value, it indicates that the user terminal does not support reporting the coarse location information of the user terminal; in the case where the preset identification bit is a preset value, extracting the coarse location information of the user terminal from the communication request.

[0126] In the above-mentioned embodiment of the present application, the communication request may carry user terminal capability information, and the user terminal capability information has a preset identification bit for indicating whether the user terminal supports reporting the coarse location information of the user terminal, and then when the preset identification bit is a preset value, it indicates that the user terminal supports reporting the coarse location information of the user terminal, and the communication request also carries the user terminal coarse location information; when the preset identification bit is not a preset value, it indicates that the user terminal does not support reporting the coarse location information of the user terminal, and then when the preset identification bit is a preset value, the user terminal coarse location information can be extracted from the communication request to achieve the acquisition of the coarse location information of the user terminal.

[0127] As an optional embodiment, the method also includes: when there is no preset identification bit in the user terminal capability information, detecting whether there is coarse location information of the user terminal in the communication request; when there is coarse location information of the user terminal in the communication request, extracting the coarse location information of the user terminal.

[0128] In the above-mentioned embodiment of the present application, when there is coarse location information of the user terminal in the communication request, even if there is no preset identification bit in the user terminal capability information, it can also indicate that the user terminal supports reporting the coarse location information of the user terminal, and then the coarse location information of the user terminal can be directly extracted from the communication request to obtain the coarse location information of the user terminal.

[0129] As an optional embodiment, the method also includes: sending a first security mode command message to a user terminal in response to a communication request, wherein the first security mode command message does not carry a location request for obtaining coarse location information of the user terminal; and receiving a first security mode completion message returned by the user terminal in response to the first security mode command message, wherein the first security mode completion message does not carry the coarse location information of the user terminal.

[0130] In the above-mentioned embodiment of the present application, upon receiving a communication request, the security mode can be turned on in response to the communication request to perform security verification on the user terminal. During the security verification process, it is necessary to send a security mode command message to the user terminal, and receive a security mode completion message returned by the user terminal in response to the security mode command message. Furthermore, since the communication request carries the coarse location information of the user terminal, and the location verification has been performed after receiving the communication request, during the security verification process, the first security mode command message sent to the user terminal may not carry a request for obtaining the coarse location information of the user terminal; and further, the first security mode completion message returned by the user terminal may not carry the coarse location information of the user terminal.

[0131] Figure 6 A schematic diagram of verifying the rough location information of a user terminal for an initial attachment to an E-UTRAN according to an embodiment of the present invention Figure 1 ,like Figure 6 As shown, the steps include:

[0132] Steps 1 and 2: The UE sends an attachment request to the network. If the UE supports reporting of coarse location information, the UE sets its preset flag Spare to a preset value 1 according to the indication of its support for coarse location information reporting capability in the user terminal capability information UE network Capability, indicating that the UE supports reporting of coarse location information and carries it in the attachment request.

[0133] It should be noted that if the UE supports reporting of coarse location information, the UE may not carry the UE network capability but directly carry the UE coarse location information. Accordingly, the MME determines whether to make a decision based on the UE network capability and whether to obtain the coarse location information from the UE, or whether to receive the coarse location information in the UE request.

[0134] Step 3: The MME verifies the location of the UE according to the prior art based on the UE capability, the PLMN accessed, and the coarse location information reported by the UE.

[0135] It should be noted that the communication request of the present application carries the UE coarse location information; and the timing of the UE location verification based on the UE coarse location information of the present application is advanced.

[0136] Step 4: Figure 2 The same as steps 3 to 5a in .

[0137] Step 5: The MME no longer performs the UE location verification process based on the PLMN and UE coarse location information according to the prior art.

[0138] Step 6: The MME sends a Security Mode Command message (such as a first security mode command message) to the UE, and no longer sends a request for obtaining coarse location information to the UE.

[0139] Step 7: The UE responds to the MME with a Security Mode Command message and no longer sends the UE's coarse location information to the MME.

[0140] Step 8. Figure 2 The steps 7 to 26 are the same as in.

[0141] This application is illustrated by taking the verification of the coarse location information of the user terminal for an attachment request as an example. The principle of verifying the coarse location information of the user terminal for a tracking area update request or a service request is the same as the principle of verifying the coarse location information of the user terminal for an attachment request, and will not be repeated in the following text of this application.

[0142] Figure 7 A method for verifying rough location information of a user terminal according to an embodiment of the present invention is provided. Figure 2 ,like Figure 7 As shown, the method comprises the following steps:

[0143] Step S702: receiving a communication request sent by a user terminal through a mobility management entity, wherein the communication request is: an attach request, a tracking area update request, or a service request, and the communication request carries user terminal capability information, and the user terminal capability information is at least used to indicate that the user terminal supports reporting of user terminal coarse location information;

[0144] Step S704: In response to the communication request, a second security mode command message is sent to the user terminal, wherein the second security mode command message carries at least a location request for obtaining coarse location information of the user terminal;

[0145] Step S706, receiving a second security mode completion message returned by the user terminal in response to the second security mode command message, wherein the second security mode completion message carries the rough location information of the user terminal;

[0146] Step S708: verify the rough location information of the user terminal to obtain a location verification result.

[0147] In an embodiment of the present invention, a communication request sent by a user terminal is received through a mobility management entity, wherein the communication request is: an attachment request, a tracking area update request, or a service request, and the communication request carries user terminal capability information, and the user terminal capability information is at least used to indicate that the user terminal supports reporting of user terminal coarse location information; in response to the communication request, a second security mode command message is sent to the user terminal, wherein the second security mode command message carries at least a location request for obtaining the user terminal coarse location information; a second security mode completion message returned by the user terminal in response to the second security mode command message is received, wherein the second security mode completion message carries the user terminal coarse location information; location verification is performed on the user terminal coarse location information to obtain a location verification result, thereby achieving the purpose of performing a location verification on the user terminal coarse location information once, thereby achieving the technical effect of avoiding redundant verification of the user terminal coarse location information, and further solving the redundant technical problem of coarse location verification in the prior art.

[0148] It should be noted that before performing location verification, obtaining the rough location information of the user terminal can be performed based on message interaction in a security mode, which specifically includes the following steps:

[0149] 1. The MME confirms that the MME supports the coarse location information reporting capability based on the optional items in the UE Core Network Capability carried by the UE.

[0150] 2. The MME requests the UE to send its coarse location information (optionally carrying coarse location information) in a security mode command message (such as a second security mode command message) in a security mode.

[0151] 3. After receiving the security mode command message request, the UE reports its coarse location information (such as the second security mode completion message) to the MME.

[0152] 4.MME performs location verification.

[0153] In the above step S708, location verification is an important part of the mobile communication network, which is used to confirm whether the current location information of the user terminal (UE) is accurate. This process usually involves multiple network entities and signal interactions to ensure the reliability and accuracy of the location data. The specific implementation method of location verification of the rough location information of the user terminal is as follows:

[0154] Optionally, to ensure that regulatory requirements are met, the network can be configured to enforce that the selected PLMN is allowed to operate at the current UE location by verifying the UE location during the EMM and ESM procedures. In this case, the MME may decide to verify the UE's location when it receives the UE's User Location Information (ULI) using satellite access for Cellular IoT.

[0155] Optionally, in the case of NB-IoT, the UE and MME may support reporting of coarse location information from the UE to the MME during the NAS security mode command process. Such as the attachment process, TAU process and service request process, in the case of NB-IoT, if the UE supports it and the MME has obtained user consent according to the proprietary mechanism of local regulations, the MME may request the UE to report its coarse location information in the NAS security mode command message. If requested, the UE provides its coarse location information in the NAS security mode completion message. The MME provides the received coarse location information to the E-SMLC. The UE indicates that it supports providing coarse location information in the UE network capability IE.

[0156] It should be noted that providing rough UE location information during the SMC process is intended to provide basic support for UE location verification. If additional accuracy or other positioning features are required, it is assumed that the UE and the network support the procedures defined in LPP and TS.

[0157] It should be noted that the coarse location information is similar to the coarse location information field defined in 3GPP TS 36.331.

[0158] Optionally, if the MME determines that the UE is not allowed to operate at the current UE location based on the selected PLMN ID and the identity of the serving cell, or in the case of NB-IoT based on the reply of the E-SMLC and coarse location information is provided to the E-SMLC, the MME shall reject any NAS request with an appropriate cause value. If the UE is already registered to the network when the MME determines that the UE is not allowed to operate at the current UE location, the MME may initiate an explicit detach of the UE. The MME shall not reject the request or detach the UE unless it has sufficiently accurate UE location information to determine that the UE is located in a geographical area where the PLMN is not allowed to operate.

[0159] Alternatively, the area in which the PLMN is allowed to operate may be determined according to local regulations and licensing conditions.

[0160] Optionally, if the MME cannot determine the UE location with sufficient accuracy to make a decision, or if the received ULI is not reliable enough, the MME continues with the mobility management or session management procedure and may initiate the UE location procedure after the mobility management or session management procedure is completed to determine the UE location. If the information received from the E SMLC indicates that the UE is registered to a PLMN that is not allowed to operate at the UE location, the MME shall prepare to detach the UE. In the case of a NAS procedure, the MME shall reject any NAS request to a PLMN that is not allowed to operate at the known UE location and indicate an appropriate cause value, or accept the NAS procedure and initiate the Detach procedure after the UE location is known. In the Detach Request message sent to the UE, the MME shall include an appropriate cause value.

[0161] Optionally, in the case of NB-IoT, whether the interaction with E-SMLC is triggered based on the location information received by the MME during the NAS process, or the interaction with E-SMCL is triggered after the NAS process, depends on the operator's configuration.

[0162] As an optional embodiment, in response to a communication request, sending a second security mode command message to a user terminal includes: in response to the communication request, authenticating the identity of the user terminal to a mobility management entity to which the user terminal has historically accessed; after the identity authentication is completed, verifying whether the user terminal supports reporting the coarse location information of the user terminal based on the user terminal capability information carried in the communication request; and sending a second security mode command message to the user terminal when the user terminal capability information indicates that the user terminal supports reporting the coarse location information of the user terminal.

[0163] In the above-mentioned embodiment of the present application, after receiving a communication request, the location verification of the coarse location information of the user terminal may not be performed first, but operations such as identity authentication to the mobility management entity to which the user terminal has historically accessed may be performed. Then, after the identity authentication is completed, it is possible to verify whether the user terminal supports reporting the coarse location information of the user terminal based on the user terminal capability information carried in the request, and if the user terminal supports reporting the coarse location information of the user terminal, a second security mode command message is sent to the user terminal, and then based on the location request for obtaining the coarse location information of the user terminal carried in the second security mode command message, the acquisition of the coarse location information of the user terminal and the location verification can be completed in the data interaction in the security mode.

[0164] Figure 8 A schematic diagram of verifying the rough location information of a user terminal for an initial attachment to an E-UTRAN according to an embodiment of the present invention Figure 2 ,like Figure 8 As shown, the steps include:

[0165] Step 1. Figure 2 The steps 1 to 2 are the same as in .

[0166] Step 2: The MME does not perform location verification on the UE.

[0167] Step 3: Figure 2 The steps 3 to 26 are the same as in .

[0168] This application is illustrated by taking the verification of the coarse location information of the user terminal for an attachment request as an example. The principle of verifying the coarse location information of the user terminal for a tracking area update request or a service request is the same as the principle of verifying the coarse location information of the user terminal for an attachment request, and will not be repeated in the following text of this application.

[0169] As an optional embodiment, in response to a communication request, sending a second security mode command message to a user terminal includes: in response to the communication request, verifying whether the user terminal supports reporting the coarse location information of the user terminal based on the user terminal capability information carried in the communication request, and obtaining a reporting capability verification result; in response to the communication request, performing identity authentication on a mobility management entity that the user terminal has historically accessed; when the identity authentication is completed and the reporting capability verification result indicates that the user terminal supports reporting the coarse location information of the user terminal, sending a second security mode command message to the user terminal.

[0170] In the above-mentioned embodiment of the present application, after receiving a communication request, it is possible to first verify whether the user terminal supports reporting the coarse location information of the user terminal, and then perform operations such as identity authentication to the mobility management entity to which the user terminal has historically accessed. Then, after the identity authentication is completed, based on the aforementioned reporting capability verification result of the user terminal, if the user terminal supports reporting the coarse location information of the user terminal, a second security mode command message can be sent to the user terminal. Then, based on the location request for obtaining the coarse location information of the user terminal carried in the second security mode command message, the acquisition of the coarse location information of the user terminal and the location verification can be completed in the data interaction in the security mode.

[0171] Fig. 9 A schematic diagram of verifying the rough location information of a user terminal for an initial attachment to an E-UTRAN according to an embodiment of the present invention Figure 3 ,like Fig. 9 As shown, the steps include:

[0172] Step 1. Figure 2 The steps 1 to 2 are the same as in .

[0173] Step 2: Based on the capability reported by the UE, the MME determines that the current UE supports reporting of coarse location information, and the MME records this information. Location verification is not performed according to the prior art.

[0174] Step 3: Figure 2 The same as steps 3 to 5a in .

[0175] Step 4: The MME confirms that the MME needs to obtain the coarse location information from the UE based on the identifier or record of whether the UE supports the UE's capability of reporting location information.

[0176] Step 5: Figure 2 The same as steps 5a to 6 in .

[0177] This application is illustrated by taking the verification of the coarse location information of the user terminal for an attachment request as an example. The principle of verifying the coarse location information of the user terminal for a tracking area update request or a service request is the same as the principle of verifying the coarse location information of the user terminal for an attachment request, and will not be repeated in the following text of this application.

[0178] The present invention also provides a preferred embodiment, which provides a UE coarse position reporting optimization method based on IoT NTN, performing terminal enhancement and network enhancement respectively.

[0179] Optionally, for terminal enhancement, if the UE supports reporting of coarse location information, the preset identification bit Spare in the user terminal capability information UEnetwork Capability is set to a preset value 1, indicating that the UE supports reporting of coarse location information; the UE can carry the user terminal coarse location information UE Coarse Location Information in the attachment / TAU / service request.

[0180] Optionally, network enhancements include:

[0181] A. After receiving the Attach / TAU Request, the MME may not perform location verification, but may perform location verification according to the prior art after receiving the CoarseLocation Information.

[0182] B. Based on A, after receiving the attach / TAU request, the MME may also determine whether the current UE supports sending the coarse location information of the user terminal based on the capability information carried by the UE and the recorded identifier. After completing other steps of the existing process and before the end of the security authentication process, the MME makes a decision based on the information saved in the previous step whether it is necessary to obtain the coarse location information of the user terminal from the UE.

[0183] C. Based on the above B, the MME does not need to obtain the user terminal coarse location information from the UE through a security process according to the existing technology.

[0184] The technical solution provided in this application solves the problem of repeated redundancy in the UE location verification process in the prior art, simplifies the interaction process between the UE and the network, improves the interaction efficiency, and improves the utilization rate of satellite resources; clarifies the capability identification method of the UE to support the reporting of coarse location information, making the process clearer and more specific.

[0185] According to an embodiment of the present invention, an embodiment of a coarse position information verification device for a user terminal is also provided. It should be noted that the coarse position information verification device for the user terminal can be used to execute the coarse position information verification method for the user terminal in the embodiment of the present invention, and the coarse position information verification method for the user terminal in the embodiment of the present invention can be executed in the coarse position information verification device for the user terminal.

[0186] Fig.10 A schematic diagram of a rough location information verification device for a user terminal according to an embodiment of the present invention Figure 1 ,like Fig.10 As shown, the device may include: a first receiving module 1002, used to receive a communication request sent by a user terminal through a mobility management entity, wherein the communication request includes: an attachment request, a tracking area update request or a service request, and the communication request carries coarse location information of the user terminal, and the coarse location information is used to preliminarily determine the location of the user terminal; an extraction module 1004, used to extract the coarse location information of the user terminal from the communication request; a first verification module 1006, used to perform location verification on the coarse location information of the user terminal to obtain a location verification result.

[0187] It should be noted that the first receiving module 1002 in this embodiment can be used to execute step S102 in the embodiment of the present application, the extraction module 1004 in this embodiment can be used to execute step S104 in the embodiment of the present application, and the first verification module 1006 in this embodiment can be used to execute step S106 in the embodiment of the present application. The examples and application scenarios implemented by the above modules and corresponding steps are the same, but are not limited to the contents disclosed in the above embodiments.

[0188] In an embodiment of the present invention, a communication request sent by a user terminal is received by a mobility management entity, wherein the communication request includes: an attachment request, a tracking area update request or a service request, and the communication request carries coarse location information of the user terminal, and the coarse location information is used to preliminarily determine the location of the user terminal; the coarse location information of the user terminal is extracted from the communication request; the coarse location information of the user terminal is positionally verified to obtain a position verification result, thereby achieving the purpose of performing a position verification on the coarse location information of the user terminal once, thereby achieving the technical effect of avoiding redundant verification of the coarse location information of the user terminal, and further solving the redundant technical problem of coarse location verification in the prior art.

[0189] As an optional embodiment, the first extraction module includes: an identification unit, used to identify user terminal capability information carried in a communication request; a first detection unit, used to detect whether there is a preset identification bit in the user terminal capability information, wherein the preset identification bit is used to indicate whether the user terminal supports reporting the coarse location information of the user terminal; a second detection unit, used to detect whether the preset identification bit is a preset value when there is a preset identification bit in the user terminal capability information, wherein when the preset identification bit is a preset value, it indicates that the user terminal supports reporting the coarse location information of the user terminal, and when the preset identification bit is not a preset value, it indicates that the user terminal does not support reporting the coarse location information of the user terminal; the first extraction unit is used to extract the coarse location information of the user terminal from the communication request when the preset identification bit is a preset value.

[0190] As an optional embodiment, the device also includes: a third detection unit, used to detect whether there is coarse location information of the user terminal in the communication request when there is no preset identification bit in the user terminal capability information; a second extraction unit, used to extract the coarse location information of the user terminal when there is coarse location information of the user terminal in the communication request.

[0191] As an optional embodiment, the device also includes: a sending submodule, used to send a first security mode command message to the user terminal in response to a communication request, wherein the first security mode command message does not carry a location request for obtaining coarse location information of the user terminal; a receiving submodule, used to receive a first security mode completion message returned by the user terminal in response to the first security mode command message, wherein the first security mode completion message does not carry the coarse location information of the user terminal.

[0192] Fig.11 A schematic diagram of a rough location information verification device for a user terminal according to an embodiment of the present invention Figure 2 ,like Fig.11 As shown, the device may include: a second receiving module 1102, used to receive a communication request sent by a user terminal through a mobility management entity, wherein the communication request is: an attachment request, a tracking area update request, or a service request, and the communication request carries user terminal capability information, and the user terminal capability information is at least used to indicate that the user terminal supports reporting of user terminal coarse location information; a sending module 1104, used to send a second security mode command message to the user terminal in response to the communication request, wherein the second security mode command message carries at least a location request for obtaining the user terminal coarse location information; a third receiving module 1106, used to receive a second security mode completion message returned by the user terminal in response to the second security mode command message, wherein the second security mode completion message carries the user terminal coarse location information; a second verification module 1108, used to perform location verification on the user terminal coarse location information to obtain a location verification result.

[0193] It should be noted that the second receiving module 1102 in this embodiment can be used to execute step S702 in the embodiment of the present application, the sending module 1104 in this embodiment can be used to execute step S704 in the embodiment of the present application, the third receiving module 1106 in this embodiment can be used to execute step S706 in the embodiment of the present application, and the second verification module 1108 in this embodiment can be used to execute step S708 in the embodiment of the present application. The examples and application scenarios implemented by the above modules and corresponding steps are the same, but are not limited to the contents disclosed in the above embodiments.

[0194] In an embodiment of the present invention, a communication request sent by a user terminal is received through a mobility management entity, wherein the communication request is: an attachment request, a tracking area update request, or a service request, and the communication request carries user terminal capability information, and the user terminal capability information is at least used to indicate that the user terminal supports reporting of user terminal coarse location information; in response to the communication request, a second security mode command message is sent to the user terminal, wherein the second security mode command message carries at least a location request for obtaining the user terminal coarse location information; a second security mode completion message returned by the user terminal in response to the second security mode command message is received, wherein the second security mode completion message carries the user terminal coarse location information; location verification is performed on the user terminal coarse location information to obtain a location verification result, thereby achieving the purpose of performing a location verification on the user terminal coarse location information once, thereby achieving the technical effect of avoiding redundant verification of the user terminal coarse location information, and further solving the redundant technical problem of coarse location verification in the prior art.

[0195] As an optional embodiment, the sending module includes: a first verification unit, used to authenticate the identity of the mobility management entity to which the user terminal has historically accessed in response to a communication request; a second verification unit, used to verify, after the identity authentication is completed, whether the user terminal supports reporting the coarse location information of the user terminal based on the user terminal capability information carried in the communication request; and a first sending unit, used to send a second security mode command message to the user terminal when the user terminal capability information indicates that the user terminal supports reporting the coarse location information of the user terminal.

[0196] As an optional embodiment, the sending module includes: a third verification unit, used to respond to a communication request, verify whether the user terminal supports reporting the coarse location information of the user terminal based on the user terminal capability information carried in the communication request, and obtain a reporting capability verification result; a fourth verification unit, used to respond to the communication request, and authenticate the identity of the mobility management entity to which the user terminal has historically accessed; a second sending unit, used to send a second security mode command message to the user terminal when the identity authentication is completed and the reporting capability verification result indicates that the user terminal supports reporting the coarse location information of the user terminal.

[0197] An embodiment of the present invention may provide an electronic device, the electronic device being a computer terminal, and the computer terminal may be any computer terminal device in a computer terminal group. Optionally, in this embodiment, the computer terminal may also be replaced by a terminal device such as a mobile terminal.

[0198] Optionally, in this embodiment, the computer terminal may be located in at least one network device among a plurality of network devices of the computer network.

[0199] In this embodiment, the above-mentioned computer terminal can execute the program code of the following steps in the method for verifying the coarse location information of the user terminal: receiving a communication request sent by the user terminal through the mobility management entity, wherein the communication request includes: an attachment request, a tracking area update request or a service request, and the communication request carries the coarse location information of the user terminal, and the coarse location information is used to preliminarily determine the location of the user terminal; extracting the coarse location information of the user terminal from the communication request; performing location verification on the coarse location information of the user terminal to obtain a location verification result.

[0200] In this embodiment, the above-mentioned computer terminal can execute the program code of the following steps in the method for verifying the coarse location information of the user terminal: receiving a communication request sent by the user terminal through the mobility management entity, wherein the communication request is: an attachment request, a tracking area update request, or a service request, and the communication request carries user terminal capability information, and the user terminal capability information is at least used to indicate that the user terminal supports reporting the coarse location information of the user terminal; in response to the communication request, sending a second security mode command message to the user terminal, wherein the second security mode command message carries at least a location request for obtaining the coarse location information of the user terminal; receiving a second security mode completion message returned by the user terminal in response to the second security mode command message, wherein the second security mode completion message carries the coarse location information of the user terminal; performing location verification on the coarse location information of the user terminal to obtain a location verification result.

[0201] Fig.12 is a structural block diagram of a computer terminal according to an embodiment of the present invention. Fig.12As shown, the computer terminal 120 may include: one or more (only one is shown in the figure) processors 122 and a memory 124 .

[0202] Among them, the memory can be used to store software programs and modules, such as the program instructions / modules corresponding to the method and device for verifying the rough position information of the user terminal in the embodiment of the present invention. The processor executes various functional applications and data processing by running the software programs and modules stored in the memory, that is, the method for verifying the rough position information of the user terminal mentioned above is realized. The memory may include a high-speed random access memory, and may also include a non-volatile memory, such as one or more magnetic storage devices, flash memory, or other non-volatile solid-state memory. In some instances, the memory may further include a memory remotely arranged relative to the processor, and these remote memories may be connected to the terminal 120 via a network. Examples of the above-mentioned network include, but are not limited to, the Internet, an intranet, a local area network, a mobile communication network, and combinations thereof.

[0203] The processor can call the information and application stored in the memory through the transmission device to execute the following steps: receiving a communication request sent by a user terminal through a mobility management entity, wherein the communication request includes: an attachment request, a tracking area update request or a service request, and the communication request carries coarse location information of the user terminal, and the coarse location information is used to preliminarily determine the location of the user terminal; extracting the coarse location information of the user terminal from the communication request; and performing location verification on the coarse location information of the user terminal to obtain a location verification result.

[0204] Optionally, the processor may also execute the program code of the following steps: identifying the user terminal capability information carried in the communication request; detecting whether the user terminal capability information contains a preset identification bit, wherein the preset identification bit is used to indicate whether the user terminal supports reporting the coarse location information of the user terminal; in the case where the preset identification bit exists in the user terminal capability information, detecting whether the preset identification bit is a preset value, wherein, in the case where the preset identification bit is a preset value, it indicates that the user terminal supports reporting the coarse location information of the user terminal, and in the case where the preset identification bit is not a preset value, it indicates that the user terminal does not support reporting the coarse location information of the user terminal; in the case where the preset identification bit is a preset value, extracting the coarse location information of the user terminal from the communication request.

[0205] Optionally, the processor may also execute the program code of the following steps: if there is no preset identification bit in the user terminal capability information, detecting whether there is coarse location information of the user terminal in the communication request; if there is coarse location information of the user terminal in the communication request, extracting the coarse location information of the user terminal.

[0206] Optionally, the processor may also execute the program code of the following steps: in response to a communication request, sending a first security mode command message to a user terminal, wherein the first security mode command message does not carry a location request for obtaining coarse location information of the user terminal; and receiving a first security mode completion message returned by the user terminal in response to the first security mode command message, wherein the first security mode completion message does not carry the coarse location information of the user terminal.

[0207] The processor can call the information and application stored in the memory through the transmission device to perform the following steps: receiving a communication request sent by a user terminal through a mobility management entity, wherein the communication request is: an attachment request, a tracking area update request, or a service request, and the communication request carries user terminal capability information, and the user terminal capability information is at least used to indicate that the user terminal supports reporting the coarse location information of the user terminal; in response to the communication request, sending a second security mode command message to the user terminal, wherein the second security mode command message carries at least a location request for obtaining the coarse location information of the user terminal; receiving a second security mode completion message returned by the user terminal in response to the second security mode command message, wherein the second security mode completion message carries the coarse location information of the user terminal; performing location verification on the coarse location information of the user terminal to obtain a location verification result.

[0208] Optionally, the processor may also execute the program code of the following steps: in response to a communication request, authenticate the identity of the mobility management entity to which the user terminal has historically accessed; after the identity authentication is completed, verify whether the user terminal supports reporting the coarse location information of the user terminal based on the user terminal capability information carried in the communication request; and send a second security mode command message to the user terminal when the user terminal capability information indicates that the user terminal supports reporting the coarse location information of the user terminal.

[0209] Optionally, the processor may also execute the program code of the following steps: in response to a communication request, verifying whether the user terminal supports reporting the coarse location information of the user terminal based on the user terminal capability information carried in the communication request, and obtaining a reporting capability verification result; in response to the communication request, performing identity authentication on the mobility management entity to which the user terminal has historically accessed; when the identity authentication is completed and the reporting capability verification result indicates that the user terminal supports reporting the coarse location information of the user terminal, sending a second security mode command message to the user terminal.

[0210] It can be understood by those skilled in the art that Fig.12 The structure shown is for illustration only, and the computer terminal may also be a smart phone (such as an Android phone, an iOS phone, etc.), a tablet computer, a handheld computer, a mobile Internet device (Mobile Internet Devices, MID), a PAD, or other terminal devices. Fig.12The structure of the electronic device is not limited. For example, the computer terminal 120 may also include Fig.12 More or fewer components (such as network interfaces, display devices, etc.) shown in, or having Fig.12 Different configurations are shown.

[0211] A person of ordinary skill in the art can understand that all or part of the steps in the various methods of the above embodiments can be completed by instructing the hardware related to the terminal device through a computer program. The computer program can be stored in a non-volatile medium. The non-volatile storage medium may include: a flash drive, a read-only memory (ROM), a random access memory (RAM), a magnetic disk or an optical disk, etc.

[0212] The embodiment of the present invention further provides a non-volatile storage medium. Optionally, in this embodiment, the non-volatile storage medium can be used to store the program code executed by the method for verifying the rough location information of the user terminal provided in the above embodiment.

[0213] Optionally, in this embodiment, the non-volatile storage medium may be located in any computer terminal in a computer terminal group in a computer network, or in any mobile terminal in a mobile terminal group.

[0214] Optionally, in this embodiment, the non-volatile storage medium is configured to store program code for performing the following steps: receiving a communication request sent by a user terminal through a mobility management entity, wherein the communication request includes: an attachment request, a tracking area update request or a service request, and the communication request carries coarse location information of the user terminal, and the coarse location information is used to preliminarily determine the location of the user terminal; extracting the coarse location information of the user terminal from the communication request; performing location verification on the coarse location information of the user terminal to obtain a location verification result.

[0215] Optionally, in this embodiment, the non-volatile storage medium is configured to store program code for performing the following steps: identifying user terminal capability information carried in a communication request; detecting whether the user terminal capability information contains a preset identification bit, wherein the preset identification bit is used to indicate whether the user terminal supports reporting the coarse location information of the user terminal; in a case where a preset identification bit exists in the user terminal capability information, detecting whether the preset identification bit is a preset value, wherein, in a case where the preset identification bit is a preset value, it indicates that the user terminal supports reporting the coarse location information of the user terminal, and in a case where the preset identification bit is not a preset value, it indicates that the user terminal does not support reporting the coarse location information of the user terminal; in a case where the preset identification bit is a preset value, extracting the coarse location information of the user terminal from the communication request.

[0216] Optionally, in this embodiment, the non-volatile storage medium is configured to store program code for performing the following steps: in a case where there is no preset identification bit in the user terminal capability information, detecting whether there is coarse location information of the user terminal in the communication request; in a case where there is coarse location information of the user terminal in the communication request, extracting the coarse location information of the user terminal.

[0217] Optionally, in this embodiment, the non-volatile storage medium is configured to store program code for performing the following steps: sending a first security mode command message to a user terminal in response to a communication request, wherein the first security mode command message does not carry a location request for obtaining coarse location information of the user terminal; and receiving a first security mode completion message returned by the user terminal in response to the first security mode command message, wherein the first security mode completion message does not carry the coarse location information of the user terminal.

[0218] Optionally, in this embodiment, the non-volatile storage medium is configured to store program code for performing the following steps: receiving a communication request sent by a user terminal through a mobility management entity, wherein the communication request is: an attachment request, a tracking area update request, or a service request, and the communication request carries user terminal capability information, and the user terminal capability information is at least used to indicate that the user terminal supports reporting of user terminal coarse location information; in response to the communication request, sending a second security mode command message to the user terminal, wherein the second security mode command message carries at least a location request for obtaining the coarse location information of the user terminal; receiving a second security mode completion message returned by the user terminal in response to the second security mode command message, wherein the second security mode completion message carries the coarse location information of the user terminal; performing location verification on the coarse location information of the user terminal to obtain a location verification result.

[0219] Optionally, in this embodiment, the non-volatile storage medium is configured to store program code for performing the following steps: in response to a communication request, authenticating the user terminal to a mobility management entity to which the user terminal has historically accessed; after the identity authentication is completed, verifying whether the user terminal supports reporting the coarse location information of the user terminal based on the user terminal capability information carried in the communication request; and sending a second security mode command message to the user terminal when the user terminal capability information indicates that the user terminal supports reporting the coarse location information of the user terminal.

[0220] Optionally, in this embodiment, the non-volatile storage medium is configured to store program code for performing the following steps: in response to a communication request, verifying whether the user terminal supports reporting the coarse location information of the user terminal based on the user terminal capability information carried in the communication request, and obtaining a reporting capability verification result; in response to the communication request, authenticating the identity of the user terminal to the mobility management entity to which the user terminal has historically accessed; when the identity authentication is completed and the reporting capability verification result indicates that the user terminal supports reporting the coarse location information of the user terminal, sending a second security mode command message to the user terminal.

[0221] The embodiment of the present invention further provides a computer program product, including a computer program. Optionally, in this embodiment, the computer program is characterized in that when executed by a processor, the computer program implements the steps of the method for verifying the rough location information of the user terminal provided in the above embodiment.

[0222] The serial numbers of the above embodiments of the present invention are only for description and do not represent the advantages or disadvantages of the embodiments.

[0223] In the above embodiments of the present invention, the description of each embodiment has its own emphasis. For parts that are not described in detail in a certain embodiment, reference can be made to the relevant descriptions of other embodiments.

[0224] In the several embodiments provided in this application, it should be understood that the disclosed technical content can be implemented in other ways. Among them, the device embodiments described above are only schematic. For example, the division of the units can be a logical function division. There may be other division methods in actual implementation. For example, multiple units or components can be combined or integrated into another system, or some features can be ignored or not executed. Another point is that the mutual coupling or direct coupling or communication connection shown or discussed can be through some interfaces, indirect coupling or communication connection of units or modules, which can be electrical or other forms.

[0225] The units described as separate components may or may not be physically separated, and the components shown as units may or may not be physical units, that is, they may be located in one place or distributed on multiple units. Some or all of the units may be selected according to actual needs to achieve the purpose of the present embodiment.

[0226] In addition, each functional unit in each embodiment of the present invention may be integrated into one processing unit, or each unit may exist physically separately, or two or more units may be integrated into one unit. The above-mentioned integrated unit may be implemented in the form of hardware or in the form of software functional units.

[0227] If the integrated unit is implemented in the form of a software functional unit and sold or used as an independent product, it can be stored in a non-volatile storage medium. Based on this understanding, the technical solution of the present invention, in essence, or the part that contributes to the prior art, or all or part of the technical solution can be embodied in the form of a software product. The computer software product is stored in a non-volatile storage medium, including several instructions for a computer device (which can be a personal computer, server or network device, etc.) to perform all or part of the steps of the method described in each embodiment of the present invention. The aforementioned non-volatile storage medium includes: U disk, read-only memory (ROM, Read-Only Memory), random access memory (RAM, Random Access Memory), mobile hard disk, magnetic disk or optical disk and other media that can store program codes.

[0228] The above is only a preferred embodiment of the present invention. It should be pointed out that for ordinary technicians in this technical field, several improvements and modifications can be made without departing from the principle of the present invention. These improvements and modifications should also be regarded as the scope of protection of the present invention.

Claims

1. A method for verifying rough location information of a user terminal, characterized in that: include: Receiving, through a mobility management entity, a communication request sent by a user terminal, wherein the communication request includes: an attach request, a tracking area update request, or a service request, and the communication request carries coarse location information of the user terminal, and the coarse location information is used to preliminarily determine the location of the user terminal; Extracting the rough location information of the user terminal from the communication request; Performing location verification on the rough location information of the user terminal to obtain the location verification result.

2. The method according to claim 1, characterized in that Extracting the rough location information of the user terminal from the communication request includes: Identifying user terminal capability information carried in the communication request; Detecting whether the user terminal capability information has a preset flag, wherein the preset flag is used to indicate whether the user terminal supports reporting the rough location information of the user terminal; When the preset flag bit exists in the user terminal capability information, detecting whether the preset flag bit is a preset value, wherein when the preset flag bit is the preset value, indicating that the user terminal supports reporting the coarse location information of the user terminal, and when the preset flag bit is not the preset value, indicating that the user terminal does not support reporting the coarse location information of the user terminal; When the preset identification bit is the preset value, the rough location information of the user terminal is extracted from the communication request.

3. The method according to claim 2, characterized in that The method further comprises: In a case where the preset identification bit does not exist in the user terminal capability information, detecting whether the rough location information of the user terminal exists in the communication request; In a case where the rough location information of the user terminal exists in the communication request, the rough location information of the user terminal is extracted.

4. The method according to claim 1, characterized in that The method further comprises: In response to the communication request, sending a first security mode command message to the user terminal, wherein the first security mode command message does not carry a location request for obtaining coarse location information of the user terminal; A first security mode completion message is received, which is returned by the user terminal in response to the first security mode command message, wherein the first security mode completion message does not carry the coarse location information of the user terminal.

5. A method for verifying rough location information of a user terminal, characterized in that: include: Receiving, through a mobility management entity, a communication request sent by a user terminal, wherein the communication request is: an attach request, a tracking area update request, or a service request, and the communication request carries user terminal capability information, and the user terminal capability information is at least used to indicate that the user terminal supports reporting of user terminal coarse location information; In response to the communication request, sending a second security mode command message to the user terminal, wherein the second security mode command message carries at least a location request for obtaining coarse location information of the user terminal; receiving a second security mode completion message returned by the user terminal in response to the second security mode command message, wherein the second security mode completion message carries the coarse location information of the user terminal; Performing location verification on the rough location information of the user terminal to obtain the location verification result.

6. The method according to claim 5, characterized in that In response to the communication request, sending a second security mode command message to the user terminal includes: In response to the communication request, performing identity authentication on a mobility management entity that the user terminal has historically accessed; After the identity authentication is completed, verifying whether the user terminal supports reporting the rough location information of the user terminal based on the user terminal capability information carried in the communication request; In a case where the user terminal capability information indicates that the user terminal supports reporting the coarse location information of the user terminal, the second security mode command message is sent to the user terminal.

7. The method according to claim 5, characterized in that In response to the communication request, sending a second security mode command message to the user terminal includes: In response to the communication request, based on the user terminal capability information carried in the communication request, verify whether the user terminal supports reporting the coarse location information of the user terminal, and obtain a reporting capability verification result; In response to the communication request, performing identity authentication on a mobility management entity that the user terminal has historically accessed; When the identity authentication is completed and the reporting capability verification result indicates that the user terminal supports reporting the coarse location information of the user terminal, the second security mode command message is sent to the user terminal.

8. A rough location information verification device for a user terminal, characterized in that: include: A first receiving module, configured to receive a communication request sent by a user terminal through a mobility management entity, wherein the communication request includes: an attach request, a tracking area update request or a service request, and the communication request carries coarse location information of the user terminal, and the coarse location information is used to preliminarily determine the location of the user terminal; An extraction module, used to extract the rough location information of the user terminal from the communication request; The first verification module is used to perform location verification on the rough location information of the user terminal to obtain the location verification result.

9. A rough location information verification device for a user terminal, characterized in that: include: A second receiving module is configured to receive a communication request sent by a user terminal through a mobility management entity, wherein the communication request is: an attachment request, a tracking area update request, or a service request, and the communication request carries user terminal capability information, and the user terminal capability information is at least used to indicate that the user terminal supports reporting of user terminal coarse location information; A sending module, configured to send a second security mode command message to the user terminal in response to the communication request, wherein the second security mode command message carries at least a location request for obtaining coarse location information of the user terminal; A third receiving module is configured to receive a second security mode completion message returned by the user terminal in response to the second security mode command message, wherein the second security mode completion message carries the coarse location information of the user terminal; The second verification module is used to perform location verification on the rough location information of the user terminal to obtain the location verification result.

10. An electronic device comprising a memory and a processor, characterized in that: The memory stores a computer program, and the processor is configured to execute the method for verifying coarse location information of a user terminal according to any one of claims 1 to 7 through the computer program.

11. A computer program product comprising computer instructions, characterized in that: When the computer instructions are executed by a processor, the steps of the method for verifying the rough location information of a user terminal described in any one of claims 1 to 7 are implemented.

Images