Location verification method and device of user equipment, and electronic equipment

By receiving registration request messages and obtaining cell identifiers and satellite epoch times in the user equipment location verification method, the existence of target combinations is determined, which solves the problems of signaling overload and excessive network load in non-terrestrial network environments, and achieves efficient location verification and fast access.

CN121547759APending Publication Date: 2026-02-17CHINA TELECOM CORP LTD SATELLITE COMMUNICATIONS BRANCH
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
CN202511714004.0
Authority / Receiving Office
CN · China
Patent Type
Applications(China)
Current Assignee / Owner
Filing Date
2025-11-20
Publication Date
2026-02-17

AI Technical Summary

Technical Problem

In non-terrestrial network environments, frequent location verification processes triggered by user equipment can lead to signaling overload and excessive network load.

Method used

By receiving the user equipment registration request message, obtaining the cell identifier and satellite epoch time, determining whether a target combination exists, and if not, instructing the local management function entity to perform the location verification process, and searching for a matching combination in the storage medium, generating a response message to reduce signaling interaction.

Benefits of technology

It significantly reduced the number of signaling interactions and network load, shortened the reconnection time for user equipment, and improved network efficiency and user experience.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN121547759A_ABST
    Figure CN121547759A_ABST
Patent Text Reader

Abstract

The invention discloses a position verification method and device of user equipment and electronic equipment. The method comprises the following steps: receiving a registration request message sent by first user equipment; under the condition that the target combination is not found in the storage medium, the local management function entity is indicated to execute a position verification process; receiving a position verification result sent by the local management function entity, and sending a first registration response message to the first user equipment; receiving a second registration request message sent by second user equipment; if it is determined that the cell identifier, the satellite time and the public land mobile network number in the second registration request message are completely consistent with the target combination in the storage medium, generating a second registration response message according to the position verification result; and sending a second registration response message to the second user equipment. According to the method and the device, the technical problems of signaling overload and overhigh network load caused by the fact that the terminal equipment frequently triggers a position verification process in a non-ground network environment are solved.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] This application relates to the fields of satellite communication and wireless communication, and more specifically, to a method, apparatus, and electronic device for verifying the location of user equipment. Background Technology

[0002] With the continuous evolution of 5G / 6G technologies, non-terrestrial networks (NTNs) have become a key component of the space-ground convergence system, providing wide-area access and data transmission services to user equipment (UEs) through non-terrestrial nodes such as satellites. Simultaneously, non-geostationary orbit (NGSO) satellite technology is maturing, and medium Earth orbit / low Earth orbit (MEO / LEO) constellations are gradually achieving effective coverage of remote areas, oceans, and aviation—areas lacking terrestrial network coverage—providing users with secure, reliable, and global communication capabilities. Against this backdrop, the global operation of NTN services has moved from a vision to large-scale deployment, thus placing clearer and more urgent demands on cross-regional regulatory and compliance matters.

[0003] In cross-border operation scenarios, regulatory service requirements such as emergency calls, lawful interception, public warnings, and billing / charging present challenges in relying solely on traditional UE location reporting methods, including issues of accuracy, reliability, and privacy protection. On one hand, satellite beams may span multiple countries, and relying solely on serving cell information may not accurately determine the correct core network the UE is connecting to. On the other hand, malicious UEs may forge Public Land Mobile Network (PLMN) connections for access, or the location information reported by the UE may become unreliable due to malicious tampering or interference, affecting the accuracy of network selection. Furthermore, UEs reporting precise locations (such as GNSS) may lead to privacy breaches and security issues.

[0004] In Release 18 NR-NTN enhancements, 3GPP supports network verification of UE location, based on single-satellite multi-RTT single positioning enhancements, with positioning accuracy in the 5-10km range.

[0005] According to TS23.501, when the Access and Mobility Management Function (AMF) in the core network receives an initial registration or service request from an NTN gNB, if the AMF can determine that the UE is in a prohibited area, it must reject any NAS request or deregister any registered UE. It must also send a clear cause value. For UEs with inaccurate or unreliable location information, the AMF can adopt two strategies depending on the UE's capabilities: first, allow it to complete the mobility or session management process to achieve temporary access; second, trigger the Location Management Function (LMF) to initiate location acquisition according to the procedure defined in TS23.273, and make a final admission decision after obtaining a reliable location.

[0006] To support the aforementioned location verification process, 3GPP has added key measurement capabilities to several protocols. In the TS 37.355 LPP protocol, two new types of UE measurements have been added, requiring the UE to support positioning capabilities: UE transmit-receive time difference (UE Rx-Tx time difference subframe offset) and downlink timing drift (DL timing drift). In the TS38.455 NRPPa protocol, positioning based on the base station transmit-receive time difference (gNB Rx-Tx time difference) has been added, and it supports the reporting of common timing advance parameters (TA parameters) for positioning assistance. Simultaneously, the LMF can obtain auxiliary information such as ephemeris and epoch time from the gNB.

[0007] In terms of the specific execution mechanism, the AMF initiates a UE location verification request in the RRC_CONNECTED state to the LMF. After receiving the request, the LMF issues instructions to the gNB via the NGAP and NRPPa protocols, requesting the gNB to provide measurement data and auxiliary information. The LMF combines the ephemeris information, epoch world, and measurement results reported by the gNB to assess whether the target PLMN is allowed to operate in the area and the consistency between the UE's reported location and the network-estimated location, and then feeds back the verification results to the AMF.

[0008] In summary, each UE access or location update within the same satellite beam (low-orbit diameter can reach 25km, accommodating a large number of users) may trigger the network to verify the UE's location, leading to frequent signaling interactions between AMF, LMF, gNB, and UE. This is especially problematic in border areas where UEs can move around, easily causing signaling overload and excessive network load.

[0009] There is currently no effective solution to the above problems. Summary of the Invention

[0010] This application provides a location verification method, apparatus, and electronic device for user equipment, which at least solves the technical problems of signaling overload and excessive network load caused by the frequent triggering of the location verification process by terminal equipment in non-terrestrial network environments.

[0011] According to one aspect of this application, a location verification method for a user equipment is provided, comprising: receiving a registration request message sent by a first user equipment and receiving a cell identifier and a satellite epoch time sent by a base station, wherein the registration request message includes at least a Public Land Mobile Network (PLN) number; if a target combination is not found in a storage medium, instructing a local management function entity to perform a location verification process, wherein the target combination includes: a cell identifier, a satellite epoch time, and a PLANT number; receiving a location verification result sent by the local management function entity and sending a first registration response message to the first user equipment; receiving a second registration request message sent by a second user equipment, wherein the second registration request message includes at least: a cell identifier, a satellite epoch time, and a PLANT number, and the second user equipment and the first user equipment access the network through the same satellite beam; if it is determined in the storage medium that the cell identifier, satellite epoch time, and PLANT number in the second registration request message are completely consistent with the target combination, generating a second registration response message based on the location verification result; and sending the second registration response message to the second user equipment.

[0012] Optionally, the location verification result includes: access denied or access allowed; the first registration response message and the second registration response message include: registration rejection message or registration consent message.

[0013] Optionally, the registration rejection message includes: optional fields, wherein the optional fields include at least: target public land mobile network number, which is the public land mobile network number of the satellite operator network that is allowed to be accessed in the area where the user equipment is located.

[0014] Optionally, the location verification method for user equipment further includes: upon receiving a new satellite epoch time from the base station, determining that the target combination in the storage medium is invalid; and if a registration request message from a second user equipment is received upon determining that the target combination in the storage medium is invalid, instructing the local management function entity to execute a new location verification process.

[0015] Optionally, the first user equipment and the second user equipment are terminal equipment that support non-terrestrial networks.

[0016] Optionally, both the first and second user equipment have signed contracts for international satellite roaming services.

[0017] Optionally, the first user equipment and the second user equipment have the ability to access multiple satellite operator networks.

[0018] According to another aspect of this application, a location verification device for a user equipment is also provided, comprising: a first receiving module, configured to receive a registration request message sent by a first user equipment and receive a cell identifier and a satellite epoch time sent by a base station, wherein the registration request message includes at least a Public Land Mobile Network (PLN) number; an instruction module, configured to instruct a local management function entity to perform a location verification process when the target combination is not found in the storage medium, wherein the target combination includes: a cell identifier, a satellite epoch time, and a PLANT number; a first sending module, configured to receive the location verification result sent by the local management function entity and send a first registration response message to the first user equipment; a second receiving module, configured to receive a second registration request message sent by a second user equipment, wherein the second registration request message includes at least: a cell identifier, a satellite epoch time, and a PLANT number, and the second user equipment and the first user equipment access the network through the same satellite beam; a generation module, configured to generate a second registration response message based on the location verification result if the cell identifier, satellite epoch time, and PLANT number in the second registration request message are found to be completely consistent with the target combination in the storage medium; and a second sending module, configured to send the second registration response message to the second user equipment.

[0019] According to another aspect of this application, a non-volatile storage medium is also provided, the storage medium including a stored program, wherein the program, when running, controls the device where the storage medium is located to execute the above-mentioned user equipment location verification method.

[0020] According to another aspect of this application, an electronic device is also provided, comprising: a memory and a processor, the processor being configured to run a program stored in the memory, wherein the program executes the above-described user device location verification method during runtime.

[0021] According to another aspect of this application, a computer program is also provided, wherein when the computer program is executed by a processor, it implements the above-described location verification method for user equipment.

[0022] According to another aspect of this application, a computer program product is also provided, the computer program product including a non-volatile computer-readable storage medium, wherein the non-volatile computer-readable storage medium stores a computer program, and the computer program, when executed by a processor, implements the above-described user equipment location verification method.

[0023] In this application, the method involves receiving a registration request message from a first user equipment and receiving a cell identifier and satellite epoch time from a base station, wherein the registration request message includes at least a Public Land Mobile Network (PLN) number; if the target combination is not found in the storage medium, instructing a local management function entity to perform a location verification process, wherein the target combination includes: cell identifier, satellite epoch time, and PRN number; receiving the location verification result from the local management function entity and sending a first registration response message to the first user equipment; and receiving a second registration request message from a second user equipment, wherein the second registration request message includes at least: cell identifier, satellite epoch time, and PRN number. The second user equipment and the first user equipment access the network through the same satellite beam. If the cell identifier, satellite epoch time, and public land mobile network number in the second registration request message are found to be completely consistent with the target combination, a second registration response message is generated based on the location verification result. The method of sending the second registration response message to the second user equipment achieves the purpose of efficient location verification, thereby significantly reducing the number of signaling interactions and network load in non-terrestrial network environments, and shortening the user equipment re-access time. This solves the technical problem of signaling overload and excessive network load caused by frequent triggering of the location verification process by terminal equipment in non-terrestrial network environments. Attached Figure Description

[0024] The accompanying drawings, which are included to provide a further understanding of this application and form part of this application, illustrate exemplary embodiments of this application and are used to explain this application, but do not constitute an undue limitation of this application. In the drawings:

[0025] Figure 1 This is a flowchart of a user equipment location verification method according to an embodiment of this application;

[0026] Figure 2 This is a flowchart of another user equipment location verification method according to an embodiment of this application;

[0027] Figure 3 This is a structural diagram of a user equipment location verification device according to an embodiment of this application;

[0028] Figure 4 This is a hardware structure block diagram of a computer terminal for a user equipment location verification method according to an embodiment of this application. Detailed Implementation

[0029] To enable those skilled in the art to better understand the present application, the technical solutions in the embodiments of the present application will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some embodiments of the present application, and not all embodiments. Based on the embodiments in the present application, all other embodiments obtained by those of ordinary skill in the art without creative effort should fall within the scope of protection of the present application.

[0030] It should be noted that the terms "first," "second," etc., in the specification, claims, and accompanying drawings of this application are used to distinguish similar objects and are not necessarily used to describe a specific order or sequence. It should be understood that such data can be interchanged where appropriate so that the embodiments of this application described herein can be implemented in orders other than those illustrated or described herein. Furthermore, the terms "comprising" and "having," and any variations thereof, are intended to cover non-exclusive inclusion; for example, a process, method, system, product, or apparatus that comprises a series of steps or units is not necessarily limited to those steps or units explicitly listed, but may include other steps or units not explicitly listed or inherent to such processes, methods, products, or apparatus.

[0031] To better understand the embodiments of this application, the technical terms involved in the embodiments of this application are explained below:

[0032] According to an embodiment of this application, a method embodiment for location verification of a user equipment is provided. It should be noted that the steps shown in the flowchart in the accompanying drawings can be executed in a computer system such as a set of computer-executable instructions. Furthermore, although a logical order is shown in the flowchart, in some cases, the steps shown or described may be executed in a different order than that shown here.

[0033] Figure 1 This is a flowchart of a location verification method for a user equipment according to an embodiment of this application. The method is applied to an access and mobility management function entity, such as... Figure 1 As shown, the method includes the following steps:

[0034] Step S102: Receive a registration request message sent by the first user equipment and receive the cell identifier and satellite epoch time sent by the base station. The registration request message includes at least the Public Land Mobile Network number.

[0035] In step S102, the AMF receives a registration request message sent by the first user equipment (UE1), wherein the registration request message includes at least the public terrestrial mobile network number of the user equipment's home network. Simultaneously, the AMF receives the cell ID and satellite epoch time from a satellite base station in a non-terrestrial network to accurately locate the network coverage area currently occupied by UE1 and the time reference for satellite operation.

[0036] Step S104: If the target combination is not found in the storage medium, instruct the local management function entity to perform a location verification procedure, wherein the target combination includes: cell identifier, satellite epoch time, and public land mobile network number.

[0037] In step S104, the AMF queries its internal cache database to check if there is a "target combination" related to the current registration request, i.e., a record containing the same Cell ID, the same Epoch Time, and the same PLMN ID. If the query result is empty, it indicates that this is the first time a position verification is performed for this PLMN under the current satellite beam, and the AMF instructs the LMF to start the position verification process.

[0038] Step S106: Receive the location verification result sent by the local management function entity and send a first registration response message to the first user equipment.

[0039] In step S106, the LMF completes location verification and returns the location verification result. The AMF determines whether the UE is located in the permitted service area of ​​its PLMN based on the location verification result. If the UE is determined to be in a prohibited area, the AMF generates a rejection message; if the UE is determined to be in an permitted area, the AMF generates an acceptance message.

[0040] Step S108: Receive a second registration request message sent by the second user equipment, wherein the second registration request message includes at least: cell identifier, satellite epoch time, and public land mobile network number, and the second user equipment and the first user equipment access the network through the same satellite beam.

[0041] In step S108, when the second user equipment (UE2) accesses the network through the same satellite beam as UE1, the AMF receives the second registration request message sent by it. Similar to UE1, UE2's request also includes at least its home PLMN ID, the Cell ID of the current service, and the Epoch Time.

[0042] Step S110: If the cell identifier, satellite epoch time, and public land mobile network number in the second registration request message are found to be completely consistent with the target combination in the storage medium, a second registration response message is generated based on the location verification result.

[0043] In step S110, the AMF queries its cache database again to determine whether the CellID, Epoch Time, and PLMN ID in the second registration request message are completely consistent with the target combination in the location verification process previously performed for UE1. If they are consistent, the location verification result for UE2 can be based on the verification result previously obtained for UE1, without the need for location verification again, thereby significantly reducing signaling interaction and processing time.

[0044] Step S112: Send a second registration response message to the second user equipment.

[0045] In step S112, the AMF generates a second registration response message for UE2 based on the previously stored location verification results. The AMF sends the second registration response message to UE2 via the network, enabling UE2 to quickly attempt to access an operational PLMN according to network guidance, thereby improving user experience and shortening reconnection time.

[0046] For example, steps S102 to S112 above can be applied to the following scenario: For an LEO system with a satellite orbital altitude of 550km, the coverage diameter of a single beam is approximately 25km. A commercial vessel sails from permitted access sea area A into prohibited access sea area B. Multiple user equipment units (including UE1 and UE2) on board are 5G NTN-enabled terminals, belonging to satellite operator network A (PLMN A), and have signed international satellite roaming service contracts, possessing the ability to access other satellite operator networks. Assume that PLMN A is prohibited from providing service in sea area B, while the permitted satellite operators in this area are B1 (PLMN B1) and B2 (PLMN B2). During the vessel's movement, UE1 and UE2 continuously access the network through the same satellite beam. When the UE enters sea area B, the network needs to prevent it from continuing to access the network as PLMN A.

[0047] The above steps involve receiving a registration request message from a first user equipment (UAE) and receiving the cell identifier and satellite epoch time from a base station. The registration request message includes at least the Public Land Mobile Network (PLN) number. If the target combination is not found in the storage medium, the local management function entity is instructed to perform a location verification process. The target combination includes the cell identifier, satellite epoch time, and PLAN number. The location verification result is received from the local management function entity, and a first registration response message is sent to the first UAE. A second registration request message is received from a second UAE. The second registration request message includes at least the cell identifier, satellite epoch time, and PLAN number. The second UAE and the first UAE access the network through the same satellite beam. If the cell identifier, satellite epoch time, and PLAN number in the second registration request message are found to be completely consistent with the target combination in the storage medium, a second registration response message is generated based on the location verification result. The second registration response message is then sent to the second UAE. This method achieves efficient location verification, thereby significantly reducing the number of signaling interactions and network load in non-terrestrial network environments, and shortening the UAE re-access time.

[0048] The following are Figure 1 The steps shown are illustrated and explained by way of example.

[0049] According to some optional embodiments of this application, the location verification result may specifically include the following: access denied or access allowed; the first registration response message and the second registration response message include: registration rejection message or registration consent message.

[0050] In this embodiment, the location verification result includes a specific determination of "access denied" or "access allowed." The determination result directly guides the AMF to generate a first registration response message or a second registration response message for the UE. The message content is manifested as a "registration rejection message" or a "registration consent message." For each UE's registration request, the AMF first determines whether the UE is located in the allowed service area of ​​its PLMN based on the LMF's location verification result. Specifically, if the UE is located in a prohibited area, the AMF will send a registration rejection message containing a Cause Value, and simultaneously add an Allowed PLMN List to the message, listing the PLMNs allowed to operate at the current UE location. This guides the UE to quickly attempt to access the allowed network, avoiding blind searches and prolonged service interruptions. If the UE is located in an allowed service area, the AMF will send a registration consent message, allowing the UE to continue using the current PLMN to access the network.

[0051] For subsequent registration requests accessing via the same satellite beam, AMF will reuse the results of previous verifications to further reduce signaling interactions, improve network efficiency and user experience. Specifically, based on the location verification results stored in the cache ("Access Denied" or "Access Allowed"), AMF will directly send a registration rejection message or a registration consent message.

[0052] The above process optimization ensures that, in non-terrestrial network environments, it can both meet cross-domain regulatory requirements and effectively improve UE access efficiency and perception quality.

[0053] According to some alternative embodiments of this application, the registration rejection message may specifically include the following: optional fields, wherein the optional fields include at least: target public land mobile network number, the target public land mobile network number being the public land mobile network number of the satellite operator network that is allowed to be accessed in the area where the user equipment is located.

[0054] In this embodiment, when the AMF determines that the UE is located in a prohibited service area of ​​its PLMN based on the location verification result fed back by the LMF, it will generate a registration rejection message in response to the UE's registration request. It is worth noting that, to guide the UE to quickly find and access an allowed PLMN, the AMF adds an optional field to the registration rejection message: "Allowed PLMN List". The Allowed PLMN List details the target public terrestrial mobile network numbers that are allowed to access within the UE's current geographical location. The target PLMNs belong to satellite operator networks that are legally operating in the UE's area. After receiving the registration rejection message, the UE parses and reads the contents of the Allowed PLMN List, prioritizing attempts to register with PLMNs included in the list. This avoids the time and power consumption issues caused by blind scanning across the entire frequency band, thus significantly improving the network reselection efficiency and user experience when encountering location rejection.

[0055] In some optional embodiments of this application, the location verification method for user equipment may further include the following steps: upon receiving a new satellite epoch time sent by the base station, determining that the target combination in the storage medium is invalid; and upon determining that the target combination in the storage medium is invalid, if a registration request message sent by a second user equipment is received, instructing the local management function entity to execute a new location verification process.

[0056] In this embodiment, when the AMF receives a new satellite epoch time reported by the base station, it indicates that the satellite's ephemeris information has been updated, and the original position verification result based on the old ephemeris information may no longer be applicable due to minor changes in the satellite's orbit. Therefore, the AMF will determine that all target combinations (including NTN Cell ID, old epoch time, and NTN PLMN) related to the old epoch time in the storage medium are invalid, meaning that the previous position verification result can no longer be reused. In this case, if the AMF subsequently receives a registration request message from a second user equipment (UE2), even if UE2's request contains the same NTN Cell ID and NTN PLMN as the invalid combination, the AMF will not directly reuse the old result, but will instruct the LMF to execute a new position verification procedure. The LMF will remeasure parameters such as the Rx-Tx subframe offset and downlink timing offset between UE2 and the gNB based on the latest satellite ephemeris information, and combine this with the latest satellite orbit model to accurately calculate the actual position of UE2, ensuring the accuracy and timeliness of the position verification result, and then making a new decision of "allow access" or "deny access".

[0057] As some optional embodiments of this application, the first user equipment and the second user equipment are terminal devices that support non-terrestrial networks. Both the first user equipment and the second user equipment have signed up for international satellite roaming services. The first user equipment and the second user equipment have the ability to access the networks of multiple satellite operators.

[0058] In this embodiment, UE1 and UE2, as terminal devices supporting non-terrestrial networks, generate a "access allowed" or "access denied" decision based on the LMF's location verification result during their initial access attempt. When UE2 subsequently attempts to access the same satellite beam coverage area, the AMF checks whether a cached decision result based on the same NTN Cell ID, satellite epoch time, and PLMN already exists. If there is no new satellite epoch time update, it indicates that the satellite orbit model is stable, and the AMF can directly reuse the cached result, simplifying the UE2 access process.

[0059] Since UE1 and UE2 have signed up for international satellite roaming services, they have the ability to access multiple satellite operator networks in different countries and regions. When UE1 is denied access or deregistered by the AMF due to being located in a prohibited service area, the AMF will include an "Allowed PLMN List" in the rejection message, listing the satellite operator PLMNs allowed to operate at the UE's current location. Upon receiving a rejection message carrying the "Allowed PLMN List," UE2 does not need to perform a lengthy PLMN scanning process. It can directly attempt to access the allowed satellite operator networks based on the list information, achieving rapid roaming reselection. This reduces service interruption time and power consumption, thereby optimizing the user's network access experience in international satellite roaming scenarios.

[0060] Furthermore, as terminal devices capable of accessing multiple satellite operator networks, when UE1 and UE2 attempt to access the network of satellite communication operator A (PLMN A), if the AMF determines that UE1 is located in a prohibited service area based on the location verification result, the AMF not only rejects UE1's access but also includes an "Allowed PLMN List" in the rejection message, listing the satellite communication operator PLMNs allowed to operate at UE1's location (such as PLMN B1 of satellite communication operator B1 and PLMN B2 of satellite communication operator B2). Then, UE2 initiates a registration request under the same beam coverage, and the AMF quickly determines whether the LMF needs to re-verify the location through a caching mechanism. If the gNB reports a new satellite epoch time, the AMF considers the cached decision combination invalid and instructs the LMF to perform a new location verification for UE2. If the verification confirms that UE2 is also in a prohibited area, the AMF will use the previously generated "Allowed PLMN List" information to add this list to the rejection message sent to UE2, guiding UE2 to prioritize accessing satellite operator networks allowed in the list, such as PLMN B1 or PLMN B2, according to its international satellite roaming service agreement.

[0061] Figure 2 This is a flowchart of a user equipment location verification method according to an embodiment of this application, such as... Figure 2 As shown, the method includes the following steps:

[0062] In step S201, UE1 (PLMN A) initiates an initial registration request, and the core network determines that its home PLMN is China Telecom. Simultaneously, the gNB reports the current NTN Cell ID 1 and the satellite epoch time as Epoch T.

[0063] In step S202, the AMF checks the cache table for information with Cell ID 1, Epoch Time T, and PLMN A. An empty query result indicates the first verification within this beam, thus initiating the full position verification process.

[0064] In step S203, the AMF triggers the LMF to perform location verification. The LMF coordinates with the gNB and UE1 to report parameters such as Rx-Tx subframeoffset and DL timing drift, and calculates the location by combining the current satellite ephemeris information and epoch time. After completing the calculation, the LMF determines that UE1 is located in the prohibited service area B of China Telecom PLMNA and returns the access prohibition result.

[0065] In step S204, the AMF sends a Registration Reject message to UE1, carrying CauseValue as PLMN not allowed, and also includes the optional field allowedPlmnList=[PLMN B1,PLMNB2] in the message.

[0066] In step S205, a few seconds later, UE2 initiates a registration request, and AMF obtains its Cell ID as 1, Epoch Time as T, and PLMN as A.

[0067] It is worth noting that when the satellite epoch time reported by the gNB is not updated, it indicates that the current ephemeris is still valid, the satellite orbit model remains stable, and changes in the beam coverage area are within a predictable range. In this case, the location compliance judgment result stored by the AMF still applies to the same Cell ID and PLMN combination. When the gNB reports a new satellite epoch time, the AMF determines that the ephemeris has been updated, the original orbit prediction becomes invalid, the relevant cache becomes invalid, and subsequent UE access will trigger a new location verification process.

[0068] In step S206, the AMF query cache contains a combination result with Cell ID 1, Epoch Time T, and PLMN A. This result can be reused without performing the network verification of UE location. The decision result Registration Reject message in the cache is directly used, and no new location request is initiated to the LMF, thus saving signaling resources.

[0069] In general, UE1 (home PLMN A) sends an initial registration request to the network side (gNB) via satellite beam. The gNB reports its NTN Cell ID, satellite epoch time, and UE1's PLMN information to the AMF. The AMF checks its cache for a matching decision result. If no match is found, the AMF instructs the LMF to perform location verification on UE1. The LMF calculates UE1's actual location based on parameters such as Rx-Tx time difference and DL timing offset, combined with satellite ephemeris information. After location verification, the LMF reports back to the AMF whether UE1 is in an area where operation is permitted, and the AMF generates a registration response accordingly. If UE1 is in a prohibited area, the AMF sends a rejection message carrying a Cause Value and an Allowed PLMN List to UE1, while storing the decision result in its cache. UE2's access attempt involves UE2 initiating a registration request. The AMF again retrieves its NTN Cell ID, satellite epoch time, and PLMN information. If the satellite epoch time has not been updated, the AMF directly reuses the location verification result in its cache to avoid redundant location calculations by the LMF. Based on the cache or new location verification result, AMF sends a registration response to UE2. If access is denied, it includes an Allowed PLMN List. After receiving a rejection message containing the Allowed PLMN List, UE2 first attempts to access the allowed PLMNs in the list to complete the network reselection process.

[0070] The above steps address the issues of signaling overload and excessive network load by proposing a method of introducing decision result caching in the AMF. For the same PLMN under the same satellite beam and satellite epoch, the initial verification result can be reused by subsequent UEs, avoiding repeated calls to LMF and gNB measurements and reducing signaling overhead.

[0071] To address the issues of user experience disruption and inefficient network selection, a network selection assistance method is proposed. An "Allowed-PLMN-List" field is added to the network's rejection message, listing the PLMNs allowed for access at the current geographical location. Upon receiving this message, the UE prioritizes trying PLMNs in the list, avoiding blind searches across the entire frequency band and shortening re-access time.

[0072] Figure 3 This is a structural diagram of a user equipment location verification device according to an embodiment of this application, such as... Figure 3 As shown, the device includes:

[0073] The first receiving module 300 is used to receive a registration request message sent by the first user equipment and to receive the cell identifier and satellite epoch time sent by the base station. The registration request message includes at least the Public Land Mobile Network number.

[0074] The instruction module 302 is used to instruct the local management function entity to perform a location verification process when the target combination is not found in the storage medium, wherein the target combination includes: cell identifier, satellite epoch time and public land mobile network number.

[0075] The first sending module 304 is used to receive the location verification result sent by the local management function entity and send the first registration response message to the first user equipment.

[0076] The second receiving module 306 is used to receive a second registration request message sent by the second user equipment. The second registration request message includes at least: cell identifier, satellite epoch time, and public land mobile network number. The second user equipment and the first user equipment access the network through the same satellite beam.

[0077] The generation module 308 is used to generate a second registration response message if the cell identifier, satellite epoch time, and public land mobile network number in the second registration request message are found to be completely consistent with the target combination in the storage medium, based on the location verification result.

[0078] The second sending module 310 is used to send a second registration response message to the second user equipment.

[0079] Optionally, the location verification result may specifically include the following: access denied or access allowed; the first registration response message and the second registration response message include: registration rejection message or registration consent message.

[0080] Optionally, the registration rejection message may specifically include the following: optional fields, wherein the optional fields include at least: target public land mobile network number, which is the public land mobile network number of the satellite operator network that is allowed to be accessed in the area where the user equipment is located.

[0081] Optionally, the location verification device of the user equipment is also used to perform the following steps: upon receiving a new satellite epoch time sent by the base station, determining that the target combination in the storage medium is invalid; and if a registration request message sent by the second user equipment is received upon determining that the target combination in the storage medium is invalid, instructing the local management function entity to perform a new location verification process.

[0082] Optionally, the first user equipment and the second user equipment are terminal equipment that support non-terrestrial networks.

[0083] Optionally, both the first and second user equipment have signed contracts for international satellite roaming services.

[0084] Optionally, the first user equipment and the second user equipment have the ability to access multiple satellite operator networks.

[0085] It should be noted that the above Figure 3 The modules in can be program modules (e.g., a set of program instructions that implements a specific function) or hardware modules. For the latter, they can be represented in the following forms, but are not limited to these: each of the above modules is represented by a processor, or the functions of each of the above modules are implemented by a processor.

[0086] It should be noted that, Figure 3 Preferred embodiments of the shown examples can be found in [reference needed]. Figure 1 The relevant descriptions of the embodiments shown will not be repeated here.

[0087] Figure 4 A hardware block diagram of a computer terminal for implementing a location verification method for user equipment is shown. Figure 4 As shown, the computer terminal 40 may include one or more processors 402 (shown as 402a, 402b, ..., 402n in the figure) 402 (processor 402 may include, but is not limited to, a microprocessor MCU or a programmable logic device FPGA, etc.), a memory 404 for storing data, and a transmission module 406 for communication functions. In addition, it may also include: a display, an input / output interface (I / O interface), a universal serial bus (USB) port (which may be included as one of the ports of a BUS bus), a network interface, a power supply, and / or a camera. Those skilled in the art will understand that... Figure 4 The structure shown is for illustrative purposes only and does not limit the structure of the aforementioned electronic device. For example, computer terminal 40 may also include... Figure 4 The more or fewer components shown, or having the same Figure 4 The different configurations shown.

[0088] It should be noted that the aforementioned one or more processors 402 and / or other data processing circuits are generally referred to herein as "data processing circuits". These data processing circuits may be embodied, in whole or in part, in software, hardware, firmware, or any other combination thereof. Furthermore, the data processing circuits may be a single, independent processing module, or may be integrated, in whole or in part, into any other element within the computer terminal 40. As involved in the embodiments of this application, the data processing circuits serve as processor control (e.g., selection of a variable resistor termination path connected to an interface).

[0089] The memory 404 can be used to store software programs and modules of application software, such as the program instructions / data storage device corresponding to the location verification method of the user equipment in this embodiment. The processor 402 executes various functional applications and data processing by running the software programs and modules stored in the memory 404, thereby realizing the aforementioned location verification method of the user equipment. The memory 404 may include high-speed random access memory, and may also include 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 404 may further include memory remotely located relative to the processor 402, and these remote memories can be connected to the computer terminal 40 via a network. Examples of such networks include, but are not limited to, the Internet, corporate intranets, local area networks, mobile communication networks, and combinations thereof.

[0090] The transmission module 406 is used to receive or send data via a network. Specific examples of the network described above may include a wireless network provided by the communication provider of the computer terminal 40. In one example, the transmission module 406 includes a network interface controller (NIC), which can connect to other network devices via a base station to communicate with the Internet. In another example, the transmission module 406 may be a radio frequency (RF) module, used for wireless communication with the Internet.

[0091] The display can be, for example, a touchscreen liquid crystal display (LCD) that allows the user to interact with the user interface of the computer terminal 40.

[0092] It should be noted here that, in some optional embodiments, the above... Figure 4 The computer terminal shown may include hardware components (including circuitry), software components (including computer code stored on a computer-readable medium), or a combination of both hardware and software components. It should be noted that... Figure 4 This is only one instance of a specific particular instance, and is intended to illustrate the types of components that may exist in the aforementioned computer terminal.

[0093] It should be noted that, Figure 4 The computer terminal shown is used to execute Figure 1 The location verification method for the user equipment shown above also applies to this electronic device, and will not be repeated here.

[0094] This application also provides a non-volatile storage medium, which includes a stored program, wherein the program, when running, controls the device where the storage medium is located to execute the above-mentioned user equipment location verification method.

[0095] A non-volatile storage medium performs the following functions: receiving a registration request message from a first user equipment (UE) and receiving a cell identifier and satellite epoch time from a base station, wherein the registration request message includes at least a Public Land Mobile Network (PLN) number; if the target combination is not found in the storage medium, instructing a local management function entity to perform a location verification procedure, wherein the target combination includes a cell identifier, satellite epoch time, and PLAN number; receiving the location verification result from the local management function entity and sending a first registration response message to the UE; receiving a second registration request message from a second UE, wherein the second registration request message includes at least a cell identifier, satellite epoch time, and PLAN number, and the UE and UE access the network through the same satellite beam; if the cell identifier, satellite epoch time, and PLAN number in the second registration request message are found to be completely consistent with the target combination in the storage medium, generating a second registration response message based on the location verification result; and sending the second registration response message to the UE.

[0096] This application also provides an electronic device, including a memory and a processor, wherein the processor is used to run a program stored in the memory, wherein the program executes the above-described user device location verification method during runtime.

[0097] The processor is configured to run a program that performs the following functions: receiving a registration request message from a first user equipment and receiving a cell identifier and satellite epoch time from a base station, wherein the registration request message includes at least a Public Land Mobile Network (PLN) number; if the target combination is not found in the storage medium, instructing a local management function entity to perform a location verification procedure, wherein the target combination includes a cell identifier, satellite epoch time, and PLAN number; receiving the location verification result from the local management function entity and sending a first registration response message to the first user equipment; receiving a second registration request message from a second user equipment, wherein the second registration request message includes at least a cell identifier, satellite epoch time, and PLAN number, and the second user equipment and the first user equipment access the network through the same satellite beam; if the cell identifier, satellite epoch time, and PLAN number in the second registration request message are found to be completely consistent with the target combination in the storage medium, generating a second registration response message based on the location verification result; and sending the second registration response message to the second user equipment.

[0098] The sequence numbers of the embodiments in this application are for descriptive purposes only and do not represent the superiority or inferiority of the embodiments.

[0099] In the above embodiments of this application, the descriptions of each embodiment have different focuses. For parts not described in detail in a certain embodiment, please refer to the relevant descriptions of other embodiments.

[0100] In the above embodiments of this application, the information collected is information and data authorized by the user or fully authorized by all parties, and the collection, storage, use, processing, transmission, provision, disclosure and application of the relevant data all comply with relevant laws, regulations and standards, take necessary protective measures, do not violate public order and good morals, and provide corresponding operation entry points for users to choose to authorize or refuse.

[0101] In the several embodiments provided in this application, it should be understood that the disclosed technical content can be implemented in other ways. The device embodiments described above are merely illustrative; for example, the division of units can be a logical functional division, and in actual implementation, there may be other division methods. For instance, multiple units or components may be combined or integrated into another system, or some features may be ignored or not executed. Furthermore, the displayed or discussed mutual coupling, direct coupling, or communication connection may be through some interfaces; the indirect coupling or communication connection between units or modules may be electrical or other forms.

[0102] The units described as separate components may or may not be physically separate. The components shown as units may or may not be physical units; that is, they may be located in one place or distributed across multiple units. Some or all of the units can be selected to achieve the purpose of this embodiment according to actual needs.

[0103] Furthermore, the functional units in the various embodiments of this application can be integrated into one processing unit, or each unit can exist physically separately, or two or more units can be integrated into one unit. The integrated unit can be implemented in hardware or as a software functional unit.

[0104] If the integrated unit is implemented as a software functional unit and sold or used as an independent product, it can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of this application, in essence, or the part that contributes to related technologies, or all or part of the technical solution, can be embodied in the form of a software product. This computer software product is stored in a storage medium and includes several instructions to cause a computer device (which may be a personal computer, server, or network device, etc.) to execute all or part of the steps of the methods described in the various embodiments of this application. The aforementioned storage medium includes various media capable of storing program code, such as USB flash drives, read-only memory (ROM), random access memory (RAM), portable hard drives, magnetic disks, or optical disks.

[0105] The above description is only a preferred embodiment of this application. It should be noted that for those skilled in the art, several improvements and modifications can be made without departing from the principle of this application, and these improvements and modifications should also be considered within the scope of protection of this application.

Claims

1. A method for verifying the location of a user equipment, characterized in that, Entities applied to access and mobility management functions include: The system receives a registration request message from a first user equipment and receives a cell identifier and satellite epoch time from a base station, wherein the registration request message includes at least: a public land mobile network number; If the target combination is not found in the storage medium, the local management function entity is instructed to perform a location verification procedure, wherein the target combination includes: the cell identifier, the satellite epoch time, and the public terrestrial mobile network number; Receive the location verification result sent by the local management function entity, and send a first registration response message to the first user equipment; The system receives a second registration request message sent by a second user equipment, wherein the second registration request message includes at least: a cell identifier, a satellite epoch time, and a public land mobile network number, and the second user equipment and the first user equipment access the network through the same satellite beam; If the cell identifier, satellite epoch time, and public land mobile network number in the second registration request message are found to be completely consistent with the target combination in the storage medium, a second registration response message is generated based on the location verification result. Send the second registration response message to the second user equipment.

2. The method according to claim 1, characterized in that, The location verification result includes: access denied or access allowed; the first registration response message and the second registration response message include: registration rejection message or registration consent message.

3. The method according to claim 2, characterized in that, The registration rejection message includes: optional fields, wherein the optional fields include at least: target public land mobile network number, the target public land mobile network number being the public land mobile network number of the satellite operator network that is allowed to be accessed in the area where the user equipment is located.

4. The method according to claim 1, characterized in that, The method further includes: Upon receiving a new satellite epoch time from the base station, the target combination in the storage medium is determined to be invalid. If the target combination in the storage medium is determined to be invalid, and a registration request message sent by the second user equipment is received, the local management function entity is instructed to execute a new location verification process.

5. The method according to claim 1, characterized in that, The first user equipment and the second user equipment are terminal devices that support non-terrestrial networks.

6. The method according to claim 1, characterized in that, Both the first user equipment and the second user equipment have signed contracts for international satellite roaming services.

7. The method according to any one of claims 1 to 6, wherein the first user equipment and the second user equipment have the ability to access multiple satellite operator networks.

8. A location verification device for user equipment, characterized in that, include: The first receiving module is configured to receive a registration request message sent by the first user equipment and to receive the cell identifier and satellite epoch time sent by the base station, wherein the registration request message includes at least: a public land mobile network number; The instruction module is used to instruct the local management function entity to perform a location verification process when the target combination is not found in the storage medium, wherein the target combination includes: the cell identifier, the satellite epoch time, and the public land mobile network number; The first sending module is used to receive the location verification result sent by the local management function entity and send a first registration response message to the first user equipment. The second receiving module is used to receive a second registration request message sent by the second user equipment, wherein the second registration request message includes at least: cell identifier, satellite epoch time and public land mobile network number, and the second user equipment and the first user equipment access the network through the same satellite beam; The generation module is configured to generate a second registration response message if the cell identifier, satellite epoch time, and public land mobile network number in the second registration request message are determined to be completely consistent with the target combination in the storage medium, based on the location verification result. The second sending module is used to send the second registration response message to the second user equipment.

9. A non-volatile storage medium, characterized in that, The non-volatile storage medium includes a stored program, wherein, when the program is executed, it controls the device where the non-volatile storage medium is located to execute the location verification method of the user equipment as described in any one of claims 1 to 7.

10. An electronic device, characterized in that, include: A memory and a processor, the processor being configured to run a program stored in the memory, wherein the program, when running, executes the location verification method for a user equipment according to any one of claims 1 to 7.

11. A computer program product, comprising a computer program, characterized in that, When the computer program is executed by the processor, it implements the location verification method for user equipment as described in any one of claims 1 to 7.