Communication method and apparatus

Abstract

The present application relates to the technical field of communications. Provided are a communication method and apparatus. In the method, a first mobility management network element or an access network element may acquire the position of a terminal and directly perform terminal position verification on the basis of the position of the terminal, wherein a terminal position verification method, which is suitable for various terminals such as IoT devices, is provided; and by means of the method, a cell identifier can be indicated to the first mobility management network element or a second mobility management network element in a timely manner on the basis of a terminal position verification result, thereby facilitating an improvement in the efficiency of a terminal accessing a network.

Description

A communication method and apparatus

[0001] Cross-references to related applications

[0002] This application claims priority to Chinese Patent Application No. 202410055120.5, filed on January 15, 2024, entitled "A Communication Method and Apparatus", the entire contents of which are incorporated herein by reference. Technical Field

[0003] This application relates to the field of communication technology, and in particular to a communication method and apparatus. Background Technology

[0004] Third Generation Partnership Program (3) rd The Generation Partnership Project (3GPP) proposed using location services (LCS) for terminal location verification (or compliance verification, location verification, or validation) to determine whether the terminal's location is within the service area of ​​the public land mobile network (PLMN) currently serving the terminal. However, in satellite communication scenarios, there is currently no corresponding solution for terminal location verification. Summary of the Invention

[0005] This application provides a communication method and apparatus for providing a terminal location verification scheme.

[0006] Firstly, embodiments of this application provide a communication method. This method can be executed by a first communication device, which may be, for example, a first mobility management network element, a software or hardware module (such as a chip) within the first mobility management network element, an access network element, or a software or hardware module (such as a chip) within the access network element, etc. This application does not limit the scope of the method. For ease of description, the method is illustrated using the execution of this communication method by a first communication device as an example. The method includes: receiving first information from a second communication device, the first information indicating the location of a terminal; if the terminal's location is within the service range permitted by a first public land mobile network (which can be considered as the terminal's location verification being compliant or successful), sending a cell identifier corresponding to the location to the first mobility management device; or, if the terminal's location is not within the service range permitted by the first public land mobile network (which can be considered as the terminal's location verification being non-compliant or unsuccessful), sending the cell identifier corresponding to the location to the second mobility management device.

[0007] The first communication device is a first mobility management network element, and the second communication device is the terminal. In this case, optionally, the first information is carried in a non-access stratum message. The first communication device is an access network element, and the second communication device is a mobility management network element. In this case, optionally, the first information is carried in an N2 interface message or an S1 interface message. The first mobility management network element can be understood as a mobility management network element in a first public land mobile network used to provide services to the terminal. The second mobility management network element can be understood as a mobility management network element in a second public land mobile network used to provide services to the terminal. The permitted service range of a certain public land mobile network can also be referred to as the service range of a certain public land mobile network, the permitted operating range of a certain public land mobile network, the operating range of a certain public land mobile network, or the signal coverage range of a certain public land mobile network, etc. The prohibited service range of a certain public land mobile network can also be referred to as exceeding the service range of a certain public land mobile network, the prohibited operating range of a certain public land mobile network, or exceeding (or not within) the signal coverage range of a certain public land mobile network, etc., without specific limitations. The cell identifier indicates the identifier of the cell corresponding to the terminal's location. The cell identifier can be the identifier corresponding to a physical cell or a logical cell; there is no limitation on this. Furthermore, as standards evolve, mobility management network elements, access network elements, or public land mobile networks may have other names; there are no specific limitations on these either.

[0008] In this embodiment, the first mobility management network element (MMU) can obtain the terminal's location from the terminal. Based on the terminal's location verification compliance, it adaptively sends a cell identifier to either the first MMU or the second MMU, providing a method for terminal location verification. Furthermore, it can promptly feed back the cell identifier to the MMU, enabling the MMU to register or serve the terminal in a timely manner based on the cell identifier. This improves the efficiency of terminal registration or service and allows for the timely correction of non-compliant location verification terminals registering in compliant networks. Optionally, the first MMU can obtain the terminal's location through non-access stratum messages, or the access network element can obtain the terminal's location from the first MMU. Non-access stratum messages have high encryption reliability, thus improving the security of the terminal's location.

[0009] In one possible implementation, the method further includes: determining whether the location of the terminal is within the service range permitted by the first public terrestrial mobile network. An alternative description is: determining whether the location of the terminal is within the service range permitted by the first public terrestrial mobile network, or not within the service range permitted by the first public terrestrial mobile network (or may be described as being outside the service range permitted by the first public terrestrial mobile network).

[0010] In one possible implementation, the first information further indicates that: the location of the terminal is not within the service range permitted by the first public terrestrial mobile network; or, the location of the terminal is within the service range permitted by the first public terrestrial mobile network.

[0011] If the first communication device determines whether the terminal's location is within the service area permitted by the first public terrestrial mobile network, the first information does not need to indicate whether the terminal's location is within or outside the service area permitted by the first public terrestrial mobile network. Alternatively, if the first information indicates whether the terminal's location is within or outside the service area permitted by the first public terrestrial mobile network, the first communication device may not need to determine whether the terminal's location is within or outside the service area permitted by the first public terrestrial mobile network. Or, if the first information indicates whether the terminal's location is within or outside the service area permitted by the first public terrestrial mobile network, the first communication device may also determine whether the terminal's location is within or outside the service area permitted by the first public terrestrial mobile network. In this case, it is equivalent to verifying whether the terminal's location is within the service area permitted by the first public terrestrial mobile network twice, which is beneficial to the reliability of the terminal location verification result.

[0012] Thus, the first communication device does not need to determine whether the terminal's location is within the service area permitted by the first public terrestrial mobile network, thereby reducing the processing load of the first communication device. Furthermore, the first information can indicate the terminal's location and whether its location is within the service area permitted by the first public terrestrial mobile network, which can relatively reduce the number of interactions between the first and second communication devices.

[0013] In one possible implementation, if the terminal's location is not within the service range permitted by the first public terrestrial mobile network, the method further includes: sending a second message to the terminal indicating that the terminal is not within the service range permitted by the first public terrestrial mobile network; and / or sending a third message to the terminal indicating one of the following: the terminal enters an idle state; or the terminal enters an inactive state.

[0014] If the first communication device is a first mobility management network element, then the first communication device can send second information and / or third information to the terminal through the access network element.

[0015] In this way, if the terminal location verification is non-compliant, the terminal can be notified of the non-compliance in a timely manner, and / or the terminal can be controlled to access an idle or inactive state to save terminal power and avoid the terminal attempting to engage in invalid communication with the first mobility management network element, thus saving resources.

[0016] In one possible implementation, the terminal's location is determined by a Global Navigation Satellite System (GNSS) location. This makes the implementation suitable for verifying the location of terminals such as IoT devices, thus demonstrating its broad applicability.

[0017] Secondly, embodiments of this application provide a communication method. This method can be executed by a first mobility management network element, or by software or hardware modules (such as chips) within the first mobility management network element; this application does not limit the specific implementation. For ease of description, the method is illustrated using the execution of this communication method by a first mobility management network element as an example. The method includes: receiving fourth information from a terminal, the fourth information indicating the location of the terminal; and sending first information to an access network element, the first information indicating the location of the terminal.

[0018] In one possible implementation, before sending the first information to the access network element, the method further includes: determining that a first condition is met, the first condition including at least one of the following: determining that the terminal type is a first type; determining that the access type used by the terminal is satellite access; determining that the access network element supports terminal location verification; or, the access network element is deployed on a first satellite.

[0019] In one possible implementation, the terminal's location is its GNSS location.

[0020] Thirdly, this application provides a communication method that can be executed by a location compliance agent network element, or by a software or hardware module (such as a chip) within the location compliance agent network element; this application does not limit this. As standards evolve, location compliance agent network elements may have other names, which are not specifically limited here. For ease of description, this application uses the execution of the communication method by a location compliance agent network element as an example. The method includes: receiving first information from a terminal, the first information being used to request registration or service of the terminal; if the terminal is within the service range permitted by a first public land mobile network, then sending second information to a first mobility management network element, the second information requesting registration or service of the terminal; or, if the terminal is not within the service range permitted by the first public land mobile network, then sending third information to the terminal, the third information being used to indicate refusal of registration or service.

[0021] The first public land mobile network currently serves the terminal, and the first mobility management network element belongs to the first public land mobile network. The compliance agent network element can be deployed on the first satellite, which may be the terminal's current serving satellite or the satellite that will provide service to the terminal next time, without specific limitations. The satellite that will provide service to the terminal next time can be understood as a satellite that will provide service to the terminal in the future; for example, it could be a satellite serving the terminal within the first time period, or a satellite serving the terminal at its next location, etc. The start (or initial) time of the first time period can be the current time.

[0022] In this embodiment, the location-compliant network element deployed on the first satellite can perform terminal location verification without relying on the core network element to perform terminal location verification, so that terminal location verification can still be performed even when the power supply link corresponding to the terminal is abnormal.

[0023] In one possible implementation, the method further includes: receiving fourth information from a first mobility management network element, the fourth information being used to trigger a location compliance agent network element to perform terminal location verification, the first mobility management network element belonging to the first public land mobile network and currently serving the terminal.

[0024] In this way, the location compliance agent network element is essentially authorized or triggered by the first mobility management network element to perform terminal location verification, which allows the location compliance agent network element or the first mobility management network element to perform terminal location verification based on specific circumstances, thereby improving the flexibility of terminal location verification.

[0025] In one possible implementation, the fourth information includes the identifier of the terminal; or, the fourth information includes the identifier of the terminal and the identifier of the first public land mobile network.

[0026] This allows the location compliance agent to identify the terminal performing the location verification based on fourth information, as well as the public terrestrial mobile network currently serving the terminal, facilitating terminal location verification.

[0027] In one possible implementation, the method further includes: receiving fifth information from an access network element, the fifth information indicating a first location of the terminal; and determining, based on the fifth information, that the terminal is located in a preset area.

[0028] The preset region can be, for example, a national border region or a provincial border region, and there are no restrictions on this. The preset region can be pre-stored, pre-configured, or pre-defined in the location compliance agent network element.

[0029] In this way, the location compliance agent network element can determine that the terminal is located in the preset area, perform terminal location verification, avoid multiple terminal location verifications, reduce unnecessary terminal location verifications, and minimize the processing load of the location compliance agent network element while ensuring terminal location compliance.

[0030] In one possible implementation, the method further includes: sending a sixth message to an access network element, the sixth message further indicating one of the following: deleting (or releasing) the terminal's context information; the terminal entering an inactive state; or the terminal entering an idle state.

[0031] In one possible implementation, the method further includes: sending seventh information to a first positioning network element, the seventh information being used to request the location of the terminal, the first positioning network element being deployed on a first satellite; receiving eighth information from the first positioning network element, the eighth information indicating a second location of the terminal; and determining, based on the second location, whether the terminal is within the service range permitted by a first public terrestrial mobile network.

[0032] In this way, the location compliance agent network element can directly obtain the second location of the terminal based on the first positioning network element on the first satellite, and perform terminal location verification based on the second location, providing a way to obtain the location of the terminal. Furthermore, determining the second location does not require relying on the core network element, reducing the interaction between the location compliance agent network element and the core network element.

[0033] In one possible implementation, the method further includes: receiving ninth information from an access network element, the ninth information indicating a third location of the terminal; and determining, based on the third location, whether the terminal is within the service range permitted by the first public terrestrial mobile network.

[0034] In this way, the location compliance agent network element obtains the terminal's third location from the access network element and performs terminal location verification based on the third location, providing a way to obtain the terminal's location. Furthermore, determining the second location does not require dependence on the core network element, reducing the interaction between the location compliance agent network element and the core network element.

[0035] In one possible implementation, the method further includes: receiving key information from a first mobility management network element; and decrypting the ninth information based on the key information to obtain the third location of the terminal.

[0036] In this way, the ninth information can carry the encrypted third location, which ensures the security of the third location while guaranteeing that the location compliance agent network element obtains the terminal's third location.

[0037] In one possible implementation, if the terminal is within the service range permitted by the first public terrestrial mobile network, it sends the cell identifier corresponding to the third location to the first mobility management network element.

[0038] In one possible implementation, the second or third position is the GNSS position of the terminal.

[0039] In one possible implementation, the method further includes: receiving tenth information, which is used to trigger the cessation of terminal location verification; and stopping terminal location verification based on the tenth information. Optionally, the tenth information may carry the terminal's identifier to facilitate explicit cessation of the terminal location verification. The tenth information may be received from a first mobility management network element.

[0040] In this way, the location compliance agent network element can stop terminal location verification, allowing the location compliance agent network element to perform terminal location verification or not perform terminal location verification relatively flexibly.

[0041] Fourthly, this application provides a communication method, which can be executed by a first mobility management network element, or by a software or hardware module (such as a chip) within the first mobility management network element; this application does not limit this. For ease of description, the method is illustrated using a location compliance agent network element executing the communication method as an example. The method includes: determining that a store-and-forward service is provided to a terminal, the terminal supports the store-and-forward function, or the terminal has subscribed to the store-and-forward service; sending fourth information to the location compliance agent network element, the fourth information being used to trigger the location compliance agent network element to perform terminal location verification, the location compliance agent network element being deployed on a first satellite.

[0042] In one possible implementation, the method further includes: receiving second information from a location compliance agent network element, wherein the second information requests registration or service terminal.

[0043] In one possible implementation, the method further includes: receiving eleventh information from the terminal, the eleventh information triggering the deregistration of the terminal or the release of the session corresponding to the terminal; and sending tenth information to the location compliance agent network element according to the eleventh information, the tenth information being used to trigger the cessation of terminal location verification.

[0044] In one possible implementation, the first satellite is the satellite currently serving the terminal; or, the first satellite is the satellite that will provide services to the terminal in the next instance.

[0045] In one possible implementation, the method further includes sending the terminal's key information to the location compliance agent network element.

[0046] Fifthly, this application provides a communication method, which can be executed by an access network element or by a software or hardware module (such as a chip) within the access network element; this application does not limit the method in this regard. For ease of description, the method is illustrated using an access network element executing the communication method as an example. The method includes: receiving sixth information from a location compliance agent network element, wherein the sixth information indicates one of the following: deleting the context information of a terminal, the terminal entering a deactivated state, or the terminal entering an idle state; the location compliance agent network element is deployed on a first satellite; and according to the sixth information, deleting the context information of the terminal, instructing the terminal to enter a deactivated state, or instructing the terminal to enter an idle state.

[0047] In one possible implementation, the method further includes: receiving first information from a terminal, the first information being used to request registration or service of the terminal; and sending the first information to a location compliance agent network element.

[0048] In one possible implementation, the method further includes: sending a ninth message to the location compliance agent network element, wherein the fifth message indicates the third location of the terminal.

[0049] Sixthly, this application provides a communication method, which can be executed by an access network element or by a software or hardware module (such as a chip) within the access network element; this application does not limit the specific implementation. For ease of description, the method is illustrated using an access network element executing the communication method as an example. The method includes: receiving first information from a location compliance agent network element, the first information indicating the location of the terminal, all of which are deployed on a first satellite; if the terminal is within the service range of a first public terrestrial mobile network, then, based on the first information, sending second information to a first mobility management device, wherein the second information indicates a cell identifier, the first mobility management device belongs to the first public terrestrial mobile network, and is currently serving the terminal; or, if the terminal is not within the service range of the first public terrestrial mobile network, then sending third information to the terminal, wherein the third information is used to indicate rejection of the terminal's registration or service; wherein the first public terrestrial mobile network is currently serving the terminal.

[0050] In this embodiment, the access network element deployed on the first satellite can perform terminal location verification without relying on the core network element to perform terminal location verification, so that terminal location verification can still be performed even when the power supply link corresponding to the terminal is abnormal.

[0051] In one possible implementation, the method further includes: receiving fourth information from the terminal, the fourth information carrying the location of the terminal; and based on the fourth information, sending fifth information to the location compliance agent network element, the fifth information indicating the location of the terminal.

[0052] In one possible implementation, the method further includes: determining whether the location of the terminal is within the service area of ​​a first public terrestrial mobile network; or receiving sixth information from a location compliance agent network element, the sixth information indicating whether the location of the terminal is within the service area of ​​the first public terrestrial mobile network or not.

[0053] In one possible implementation, the method further includes sending a seventh message to the terminal, the seventh message indicating that the terminal is not within the service range permitted by the first public terrestrial mobile network.

[0054] In one possible implementation, the method further includes sending an eighth message to the terminal, the eighth message indicating either that the terminal enters an inactive state or that the terminal enters an idle state.

[0055] In one possible implementation, the first satellite is the satellite currently serving the terminal; or, the first satellite is the satellite that will provide service to the terminal in the next instance.

[0056] In one possible implementation, the terminal's location is its Global Navigation Satellite System (GNSS) location.

[0057] Seventhly, this application provides a communication method, which can be executed by a location compliance agent network element, or by a software or hardware module (such as a chip) within the location compliance agent network element; this application does not limit the method in this regard. For ease of description, the method is illustrated using an example of a location compliance agent network element executing the communication method. The method includes: receiving fifth information from an access network element, the fifth information carrying the location of a terminal, the access network element being deployed on a first satellite; receiving key information from a terminal from a first mobility management network element; decrypting the fifth information based on the key information to obtain the location of the terminal; and sending first information to the access network element, the first information indicating the location of the terminal.

[0058] In one possible implementation, the first satellite is the satellite currently serving the terminal; or, the first satellite is the satellite that will provide service to the terminal in the next instance.

[0059] In one possible implementation, the fifth piece of information is carried in a non-access stratum message.

[0060] In one possible implementation, the terminal's location is its GNSS location.

[0061] Eighthly, this application provides a communication method, which can be executed by a first mobility management network element, or by a software or hardware module (such as a chip) within the first mobility management network element; this application does not limit the specific implementation. For ease of description, the method is illustrated using the execution of this communication method by a first mobility management network element as an example. The method includes: obtaining key information of a terminal; and sending the key information of the terminal to a location compliance agent network element deployed on a first satellite.

[0062] In one possible implementation, the first satellite is the satellite currently serving the terminal; or, the first satellite is the satellite that will provide service to the terminal in the next instance.

[0063] In one possible implementation, the method further includes: determining to provide store-and-forward service to the terminal; receiving a ninth message from the terminal, the ninth message indicating that the terminal supports the store-and-forward function; or, receiving a tenth message from a unified data management function, the tenth message indicating that the terminal has subscribed to the store-and-forward service.

[0064] In one possible implementation, the method further includes: sending an eleventh message to the location compliance agent network element, the eleventh message being used to trigger the location compliance agent network element to perform the terminal location verification.

[0065] Ninthly, this application provides a communication method, which can be executed by a terminal or by software or hardware modules (such as chips) within the terminal; this application does not limit the specific method. For ease of description, the method is illustrated using a terminal executing the communication method as an example. The method includes: sending ninth information to a first mobility management network element, the ninth information indicating that the terminal supports store-and-forward functionality; and sending fourth information to an access network element, the fourth information carrying the location of the terminal.

[0066] In one possible implementation, the method further includes: receiving third information from an access network element, wherein the third information is used to indicate rejection of the terminal's registration or service.

[0067] In one possible implementation, the method further includes: receiving seventh information from an access network element, the seventh information indicating that the terminal is not within the service range permitted by the first public terrestrial mobile network.

[0068] In one possible implementation, the method further includes: receiving eighth information from an access network element, the eighth information indicating one of the following: the terminal enters an inactive state; or, the terminal enters an idle state.

[0069] In one possible implementation, the terminal's location is its GNSS location.

[0070] In a tenth aspect, embodiments of this application provide a communication device. This communication device may be the first communication device described in the first aspect above, or a software or hardware module (such as a chip or chip system) configured in the first communication device, or a device having the functions of the first communication device described in the first aspect. The communication device includes corresponding means or modules for performing the first aspect or any possible implementation described above. For example, the communication device includes a transceiver module. Optionally, the communication device further includes a processing module (sometimes also called a processing unit).

[0071] For example, the transceiver module is used to receive first information from the second communication device; if the terminal's location is within the service range allowed by the first public land mobile network, it sends the cell identifier corresponding to the location to the first mobility management device; or, if the terminal's location is not within the service range allowed by the first public land mobile network, it sends the cell identifier corresponding to the location to the second mobility management device.

[0072] The communication device can also perform the methods in any of the possible implementations of the first aspect, which will not be listed here one by one.

[0073] Eleventhly, embodiments of this application provide a communication device. This communication device can be a first mobility management network element as described in the second aspect above, or a software or hardware module (such as a chip or chip system) configured in the first mobility management network element, or a device having the functions of the first mobility management network element as described in the second aspect. The communication device includes corresponding means or modules for performing the second aspect or any possible implementation described above. For example, the communication device includes a transceiver module. Optionally, the communication device further includes a processing module (sometimes also called a processing unit).

[0074] For example, the transceiver module is used to receive third information from the terminal, the third information indicating the location of the terminal, and to send first information to the access network element, the first information indicating the location of the terminal.

[0075] The communication device can also perform the methods in any of the possible implementations of the second aspect, which will not be listed here one by one.

[0076] In a twelfth aspect, embodiments of this application provide a communication device. This communication device can be a location compliance proxy network element as described in the third aspect above, or a software or hardware module (such as a chip or chip system) configured in a location compliance proxy network element, or a device having the functions of a location compliance proxy network element as described in the third aspect. The communication device includes corresponding means or modules for performing the third aspect or any possible implementation described above. For example, the communication device includes a transceiver module. Optionally, the communication device further includes a processing module (sometimes also called a processing unit).

[0077] For example, the transceiver module is used to receive first information from the terminal, which is used to request registration or service of the terminal; if the terminal is within the service range permitted by the first public land mobile network, it sends second information to the first mobility management network element, which requests registration or service of the terminal; or, if the terminal is not within the service range permitted by the first public land mobile network, it sends third information to the terminal, which is used to indicate refusal of registration or service.

[0078] The communication device can also perform the methods in any of the possible implementations of the third aspect, which will not be listed here one by one.

[0079] In a thirteenth aspect, embodiments of this application provide a communication device. This communication device can be a first mobility management network element as described in the fourth aspect above, or a software or hardware module (such as a chip or chip system) configured in the first mobility management network element, or a device having the functions of the first mobility management network element as described in the fourth aspect. The communication device includes corresponding means or modules for performing the fourth aspect or any possible implementation described above. For example, the communication device includes a transceiver module and a processing module (sometimes also called a processing unit).

[0080] For example, the processing module is used to determine whether to provide store-and-forward services to the terminal, whether the terminal supports the store-and-forward function, or whether the terminal has signed up for store-and-forward services; the transceiver module is used to send fourth information to the location compliance agent network element, which triggers the location compliance agent network element to perform terminal location verification, and the location compliance agent network element is deployed on the first satellite.

[0081] The communication device may also perform the methods in any of the possible implementations of the fourth aspect, which will not be listed here one by one.

[0082] In a fourteenth aspect, embodiments of this application provide a communication device. This communication device can be an access network element as described in the fifth aspect above, or a software or hardware module (such as a chip or chip system) configured in the access network element, or a device having the functions of an access network element as described in the fifth aspect. The communication device includes corresponding means or modules for performing the fifth aspect or any possible implementation described above. For example, the communication device includes a transceiver module and a processing module (sometimes also called a processing unit).

[0083] The transceiver module is used to receive the sixth information from the location compliance agent network element, wherein the sixth information indicates one of the following: deleting the terminal's context information, the terminal entering an inactive state, or the terminal entering an idle state, and the location compliance agent network element is deployed on the first satellite; the processing module is used to delete the terminal's context information according to the sixth information, or the transceiver module is used to instruct the terminal to enter an inactive state, or instruct the terminal to enter an idle state.

[0084] The communication device may also perform the methods in any of the possible implementations of the fifth aspect, which will not be listed here one by one.

[0085] In a fifteenth aspect, embodiments of this application provide a communication device. This communication device can be an access network element as described in the sixth aspect above, or a software or hardware module (such as a chip or chip system) configured in the access network element, or a device having the functions of an access network element as described in the sixth aspect. The communication device includes corresponding means or modules for performing the sixth aspect or any possible implementation described above. For example, the communication device includes a transceiver module. Optionally, the communication device further includes a processing module (sometimes also called a processing unit).

[0086] The transceiver module is used to receive first information from the location compliance agent network element, the first information indicating the location of the terminal, and the location compliance agent network element is deployed on the first satellite; if the terminal is within the service range of the first public terrestrial mobile network, then the second information is sent to the first mobility management device according to the first information; or, if the terminal is not within the service range of the first public terrestrial mobile network, then the third information is sent to the terminal.

[0087] The communication device may also perform the methods in any of the possible implementations of the sixth aspect, which will not be listed here one by one.

[0088] In a sixteenth aspect, embodiments of this application provide a communication device. This communication device can be a location compliance proxy network element as described in the seventh aspect above, or a software or hardware module (such as a chip or chip system) configured in a location compliance proxy network element, or a device having the functions of a location compliance proxy network element as described in the seventh aspect. The communication device includes corresponding means or modules for performing the seventh aspect or any possible implementation described above. For example, the communication device includes a transceiver module. Optionally, the communication device further includes a processing module (sometimes also called a processing unit).

[0089] The transceiver module is used to receive key information from the terminal from the first mobility management network element; decrypt the fifth information according to the key information to obtain the location of the terminal; and send the first information to the access network element, the first information indicating the location of the terminal.

[0090] The communication device may also perform the methods in any of the possible implementations of the seventh aspect, which will not be listed here one by one.

[0091] In a seventeenth aspect, embodiments of this application provide a communication device. This communication device can be a first mobility management network element as described in the eighth aspect above, or a software or hardware module (such as a chip or chip system) configured in the first mobility management network element, or a device having the functions of the first mobility management network element as described in the eighth aspect. The communication device includes corresponding means or modules for performing the eighth aspect or any possible implementation described above. For example, the communication device includes a transceiver module. Optionally, the communication device further includes a processing module (sometimes also called a processing unit).

[0092] The transceiver module is used to obtain the terminal's key information and send the terminal's key information to the location compliance agent network element, which is deployed on the first satellite.

[0093] The communication device may also perform the methods in any of the possible implementations of the eighth aspect, which will not be listed here one by one.

[0094] In an eighteenth aspect, embodiments of this application provide a communication device. This communication device can be a terminal as described in the ninth aspect above, or a software or hardware module (such as a chip or chip system) configured in a terminal, or a device having the functions of a terminal as described in the ninth aspect. The communication device includes corresponding means or modules for performing the ninth aspect or any possible implementation described above. For example, the communication device includes a transceiver module. Optionally, the communication device further includes a processing module (sometimes also called a processing unit).

[0095] The transceiver module is used to send a ninth message to a first mobility management network element, the ninth message indicating that the terminal supports store-and-forward functionality; and to send a fourth message to an access network element, the fourth message carrying the location of the terminal.

[0096] The communication device may also perform the methods in any of the possible implementations of the ninth aspect, which will not be listed here one by one.

[0097] In a nineteenth aspect, embodiments of this application provide a communication device. The communication device includes a processor and an interface circuit. The interface circuit is configured to receive signals from other communication devices besides the communication device and transmit them to the processor, or to send signals from the processor to other communication devices besides the communication device. The processor, through logic circuitry or executable code instructions, implements any of the methods described in the first to ninth aspects.

[0098] In the specific implementation process, the communication device can be a chip, and the processor can be a transistor, gate circuit, flip-flop, and various logic circuits, etc. The specific implementation method of the processor is not limited in the embodiments of this application.

[0099] In one implementation, the communication device can be a wireless communication device, i.e., a computer device that supports wireless communication functionality. Specifically, the wireless communication device can be a terminal device such as a smartphone, or a network device such as a wireless access network device (e.g., a base station).

[0100] In another implementation, the communication device can be a component of a wireless communication device, such as an integrated circuit product like a system-on-a-chip (SoC) or communication chip. A SoC can be a system-on-a-chip (SoC) or simply a SoC chip. The communication chip may include a baseband processing chip and a radio frequency (RF) processing chip. The baseband processing chip is sometimes called a modem or baseband chip. The RF processing chip is sometimes called a transceiver or RF chip. In physical implementation, some or all of the communication chips can be integrated within the SoC chip. For example, the baseband processing chip may be integrated into the SoC chip, while the RF processing chip may not be integrated. The interface circuit can be the RF processing chip in the wireless communication device, and the processor can be the baseband processing chip in the wireless communication device. The interface circuit can be an input / output interface, interface circuit, output circuit, input circuit, pin, or related circuit on the chip or chip system. The processor can also be a processing circuit or logic circuit.

[0101] In another implementation, the communication device can be a chip system, which may consist of chips or include chips and other discrete devices. Chip systems may include, for example, field-programmable gate arrays (FPGAs), application-specific integrated circuits (ASICs), system-on-chips (SoCs), CPUs, network processors (NPs), DSPs, microcontroller units (MCUs), programmable logic devices (PLDs), or other integrated chips.

[0102] In a twentieth aspect, embodiments of this application provide a communication device. This communication device includes a processor; when the communication device is in operation, the processor executes any of the methods described in the first to ninth aspects. Optionally, the communication device further includes a memory storing one or more computer programs, the processor being able to execute the one or more computer programs to implement any of the methods described in the first to ninth aspects.

[0103] Optionally, the communication device may also include other components, such as antennas, input / output modules, interfaces (such as communication interfaces), etc. These components may be hardware, software, or a combination of software and hardware.

[0104] In a twentieth aspect, embodiments of this application provide a communication system. The communication system can implement any of the methods described in the first to ninth aspects.

[0105] In one possible embodiment, the communication system includes any of the communication devices described in the tenth aspect and any of the communication devices described in the eleventh aspect.

[0106] In another possible embodiment, the communication system includes any of the communication devices described in the twelfth aspect, the thirteenth aspect, and the fourteenth aspect.

[0107] In another possible embodiment, any of the communication devices described in the fifteenth aspect, the sixteenth aspect, the seventeenth aspect, and the eighteenth aspect.

[0108] In a twenty-second aspect, embodiments of this application provide a chip system. The chip system includes a processor. Optionally, the chip system may further include an interface (such as a communication interface). The processor can be used to implement any of the methods described in aspects one through nine. Optionally, the chip system also includes a memory. The memory is used to store a computer program (also referred to as code or instructions). The processor is used to call and run the computer program from the memory, causing a device equipped with the chip system to perform any of the methods described in aspects one through nine. Implementation methods of the chip system can be referred to the preceding descriptions of chip systems, and will not be listed here.

[0109] In a twentieth aspect, embodiments of this application provide a computer-readable storage medium. This computer-readable storage medium is used to store a computer program or instructions that, when executed, implement any of the methods described in the first to ninth aspects.

[0110] In a twentieth aspect, embodiments of this application provide a computer program product. When run on a computer, it implements any of the methods described in the first to ninth aspects.

[0111] In one possible implementation, the computer program product includes a computer program that, when run on a computer, causes the computer to perform any of the methods described in the first to ninth aspects.

[0112] In another possible implementation, the computer program product includes instructions that, when executed on a computer, cause the computer to perform any of the methods described in the first to ninth aspects.

[0113] Regarding the beneficial effects of any of the technical solutions in the second, fourth, fifth, and seventh to twenty-fourth aspects mentioned above, refer to the discussion of the beneficial effects of the corresponding technical solutions in the first, third, or sixth aspects; repeated examples will not be listed here. Attached Figure Description

[0114] Figure 1 is a schematic diagram of the architecture of a communication system applicable to an embodiment of this application;

[0115] Figure 2 is a schematic diagram of the architecture of a communication system applicable to an embodiment of this application;

[0116] Figure 3 is a schematic diagram of a terminal location verification process;

[0117] Figure 4 is a schematic diagram of a scenario with discontinuous coverage;

[0118] Figure 5 is a schematic diagram of the architecture of a communication system provided in an embodiment of this application;

[0119] Figures 6 to 13 are schematic diagrams of six communication methods provided in the embodiments of this application;

[0120] Figures 14 to 16 are schematic diagrams of the structures of three communication devices provided in the embodiments of this application. Detailed Implementation

[0121] To make the objectives, technical solutions, and advantages of the embodiments of this application clearer, the embodiments of this application will be further described in detail below with reference to the accompanying drawings.

[0122] To facilitate understanding, some technical terms involved in the embodiments of this application are described below. These explanations are intended to make the embodiments of this application easier to understand and should not be regarded as limiting the scope of protection claimed by the embodiments of this application.

[0123] 1. A cell can be understood as an area that provides wireless communication services to terminal devices, and is a unit of a communication network. Alternatively, a cell can be considered a unit for dividing communication coverage. An access network element (such as a base station) can correspond to one or more cells, or these one or more cells can be considered as one or more cells belonging to that access network element. Optionally, a cell is a cell managed by an access network element. For example, if the access network element is a base station, one base station can manage one cell or multiple cells. For example, a cell is a coverage area centered on a base station. For example, when one base station manages multiple cells, the base station can have antennas in multiple directions. One antenna is used to cover a certain geographical area in the corresponding direction, and this geographical area is called a sector. A sector uses one or more radio carrier frequencies to complete wireless coverage. One radio carrier frequency uses one carrier frequency point. The sector and carrier frequency constitute the smallest service unit providing access to terminal devices, i.e., a cell.

[0124] A physical cell can be divided into one or more logical cells, or multiple physical cells can be combined into one logical cell. Alternatively, logical cells can also correspond one-to-one with geographical regions. For example, a network operator can divide multiple geographical regions, with each geographical region corresponding to a logical cell. In this case, logical cells are unrelated to physical cells. For instance, if a geographical region A corresponds to logical cell 1, when a satellite moves over geographical region A, devices accessing the network via the satellite within geographical region A can be considered to be accessing the network from the corresponding logical cell 1.

[0125] Both logical and physical cells can be represented using a cell identifier (cell ID). For example, a physical cell identifier (PCI) can be used. The cell identifier used in this application can be either a physical cell identifier or a logical cell identifier; there is no limitation on this.

[0126] 2. The PLMN identifier (ID), also known as the PLMN identifier, is used to indicate the PLMN. The PLMN identifier may include, for example, the Mobile Country Code (MCC) and the Mobile Network Code (MNC). The MCC is uniformly assigned and managed by the ITU and is used to uniquely identify the country to which a mobile user belongs; the MCC can be a specific value. The MNC is used to identify the mobile network to which the mobile customer belongs and can be a 2-3 digit number. Within the same country, if there are multiple PLMNs, they can be distinguished by the MNC. The PLMN identifier corresponding to the location of a terminal not only indicates the PLMN but also reflects the PLMN the terminal is currently in; that is, the PLMN identifier can serve to indicate the terminal's location.

[0127] 3. The location of the terminal can be the specific (or precise) location of the terminal or the coarse location of the terminal (UE location).

[0128] The specific (or precise) location of a terminal can represent its exact location point or its high-precision location. For example, the specific location of a terminal is its position (or coordinates) in a coordinate system (such as the world coordinate system or other coordinate systems). When the terminal's location is in the world coordinate system, it can be considered its geographical location, specifically including its longitude and latitude, and optionally, its relative altitude. The relative altitude of a terminal is, for example, its height relative to the ground or the horizon.

[0129] The coarse location of a terminal indicates its approximate location, but it may not specify the exact location. Furthermore, the coarse location may have significant uncertainty or low accuracy, such as only guaranteeing an accuracy within 2km. The coarse location of a terminal can also be its GNSS position, which can be referred to as GNSS coordinates or the area where the terminal is located.

[0130] GNSS location includes the terminal's longitude and latitude (longitude and latitude can be collectively referred to as latitude and longitude). Optionally, GNSS location also includes the terminal's relative altitude. For example, a terminal's GNSS location of (30, 60, 10) indicates that the terminal is located at a longitude of 30 degrees (°), a latitude of 60°, and an altitude of 10 meters (m).

[0131] The region where the terminal is located can be represented in one of the following ways, or the region where the terminal is located can include one of the following: the PLMN corresponding to the terminal's geographical location, for example, the terminal's location is represented as PLMN1, which means that the terminal's geographical location corresponds to PLMN1; the cell corresponding to the terminal's geographical location, for example, the terminal's location is represented as cell2, which means that the terminal's geographical location corresponds to cell2; the index of the synchronization signal corresponding to the terminal's geographical location, for example, if the network side issues synchronization signals with different indices in different regions, then the coarse location corresponding to the terminal can be indicated by the synchronization signal; or, the physical region where the terminal is located, where the physical region can be the same as or different from the geographical region used to map logical cells mentioned above, without specific limitations. The synchronization signal includes / can be replaced by any one or more of the following: synchronization signal (SS), synchronization signal block (SSB), or synchronization signal block and PBCH block (or, SS / PBCH block, SSB).

[0132] Different network elements or devices may be able to obtain the terminal's location, but the terminal locations obtained by different network elements or devices may be of the same type, such as the specific location of the terminal or a coarse location of the terminal. However, the terminal locations obtained by different network elements or devices may differ. Alternatively, the terminal locations obtained by different network elements may be of different types, which is not limited. For ease of distinction, the terminal locations obtained by different network elements or devices will be referred to as the terminal's first location, the terminal's second location, or the terminal's third location, etc., respectively.

[0133] Of course, the location of the terminal may be represented in other ways, and the various embodiments of this application do not specifically limit this.

[0134] 4. Terminal Identifier (ID): Used to identify the terminal. Terminal identifiers include permanent and / or temporary identifiers. Permanent identifiers include, for example, a subscription permanent identifier (SUPI), a permanent equipment identifier (PEI), or a generic public subscription identifier (GPSI). Temporary identifiers include, for example, a subscription concealed identifier (SUCI) or a globally unique temporary identity (GUTI).

[0135] 5. A registration request, also known as a registration request message, is used to request the registration of a terminal, or in other words, to register the terminal with the network so that the network can serve the terminal. A registration request can be used for initial terminal registration, in which case it can also be called an initial registration request, such as when a terminal initiates an initial registration request after powering on. Alternatively, it can be used to request an update to the terminal's registration, in which case it can also be called a registration update request, such as when a terminal moves from one country to another. Optionally, the registration request may include the terminal's identifier, such as SUPI. Optionally, the registration request may also include network slice selection assistance information (NSSAI). NSSAI is used to identify a network slice. For example, the NSSAI value of a network slice is 0x01000000.

[0136] 6. A service request, also known as a service request message, is used to request services to a terminal. Specifically, it may be used to establish a session for the terminal, such as a Protocol Data Unit (PDU) session. Optionally, a service request may include the terminal's identifier and / or information about the type of service requested by the terminal.

[0137] 7. PLMN, a communication network that provides mobile communication services. PLMN can be operated by a government or an operator approved by it.

[0138] 8. The permitted service area of ​​a PLMN can be understood as the business area or operating area that the PLMN can provide, or the signal coverage area of ​​the PLMN, or the agreed business area of ​​the PLMN, etc. The permitted service area of ​​a PLMN can be described in one of the following ways: the permitted service area of ​​the PLMN, the service area of ​​the PLMN, the service range of the PLMN, the PLMN, the permitted operating range of the PLMN, the operating range of the PLMN, or the signal coverage range of the PLMN, etc., without specific limitations.

[0139] The first service area may include one or more location areas, which are areas covered by gateway stations. In other words, the first service area may include areas covered by one or more gateway stations. The area covered by a gateway station can be understood as a partial area covered by the gateway station, and a partial area can be understood as the area that provides actual services, or a portion of the theoretically coverable area.

[0140] 9. The terminal is located within the service area permitted by the PLMN or the terminal is not located within the service area permitted by the PLMN.

[0141] The term "terminal located within the PLMN's permitted service area" can also be described as follows: the terminal's location is within the PLMN's permitted service area; the terminal's location (or terminal) is within the PLMN's service area (or service zone); the terminal's location (or terminal) is within the PLMN's signal coverage area (signal coverage zone); the terminal's location (or terminal) is within the PLMN's operating area (or operating zone); or, the terminal's location (or terminal) is within the PLMN's permitted operating area (or operating zone), without specific limitations. Similarly, the term "terminal not located within the PLMN's permitted service area" can also be described as follows: the terminal's location is not within (or exceeds) the PLMN's permitted service area; the terminal's location (or terminal) is not within (or exceeds) the PLMN's service area (or service zone); the terminal's location (or terminal) is not within (or exceeds) the PLMN's signal coverage area (signal coverage zone); the terminal's location (or terminal) is not within (or exceeds) the PLMN's operating area (or operating zone); or, the terminal's location (or terminal) is not within (or exceeds) the PLMN's permitted operating area (or operating zone), without specific limitations.

[0142] The terminal being located within the PLMN's permitted service range can be defined as follows: the terminal's current location actually falls within (or is within) the PLMN's permitted service range; the terminal's signal coverage overlaps with the PLMN's permitted service range; the overlap between the terminal's signal coverage and the PLMN's permitted service range is greater than or equal to a first preset range; the terminal is able to receive signals sent by network elements within the PLMN; or the overlap between the geographical or physical area corresponding to the logical cell of the terminal and the PLMN's permitted service range is greater than or equal to a second preset range. No limitation is imposed on these aspects.

[0143] Similarly, the terminal not being within the PLMN's permitted service range can be due to the terminal's current location not falling within (or being within) the PLMN's permitted service range, or the overlap between the terminal's signal coverage range and the PLMN's permitted service range being less than a first preset range, or the terminal being unable to receive signals sent by network elements within the PLMN, or the overlap between the geographical or physical area corresponding to the logical cell of the terminal and the PLMN's permitted service range being less than a second preset range, etc., without limitation.

[0144] For example, if a PLMN's permitted service area includes the entire region of country C, and the terminal's current location is within a specific location in country C, then the terminal is within the PLMN's permitted service area. Conversely, if the terminal is not within the PLMN's permitted service area, it means that the terminal's current location is not within that area. For instance, if a PLMN's permitted service area includes the entire region of country C, and the terminal's current location is within a specific location in country B, then the terminal is not within the PLMN's permitted service area.

[0145] In this application embodiment, the number of nouns, unless otherwise specified, refers to "singular nouns or plural nouns," that is, "one or more." "At least one" means one or more, and "more than one" means two or more. "And / or" describes the relationship between related objects, indicating that three relationships can exist. For example, A and / or B can mean: A exists alone, A and B exist simultaneously, or B exists alone, where A and B can be singular or plural. The character " / " generally indicates that the related objects before and after are in an "or" relationship. For example, A / B means: A or B. "At least one of the following" or similar expressions refer to any combination of these items, including any combination of single or plural items. For example, at least one of a, b, or c means: a, b, c, a and b, a and c, b and c, or a and b and c, where a, b, and c can be single or multiple.

[0146] In this application's embodiments, ordinal numbers such as "first" and "second" are used to distinguish multiple objects, and are not used to limit the size, content, order, timing, priority, or importance of the multiple objects. For example, "first information" and "second information" refer to two pieces of information, and do not indicate that the content, priority, or importance of these two pieces of information are different.

[0147] In the embodiments of this application, "when," "if," and "if" all refer to the device taking corresponding actions under certain objective circumstances, and are not time-limited, nor do they require the device to perform a judgment action, nor do they imply any other limitations. Unless otherwise specified, "if" and "if" can be substituted, and "when" and "in the case of" can be substituted. "When" and "if" / "if" can be substituted.

[0148] In the embodiments of this application, "instruction" can include direct instruction, indirect instruction, explicit instruction, and implicit instruction. When describing a certain instruction information to indicate A, it can be understood that the instruction information carries A, directly indicates A, or indirectly indicates A. In this application, the information indicated by the instruction information is called the information to be instructed. In the specific implementation process, there are many ways to indicate the information to be instructed, such as, but not limited to, directly indicating the information to be instructed, such as the information to be instructed itself or its index. It can also indirectly indicate the information to be instructed by indicating other information, wherein there is an association between the other information and the information to be instructed. It can also indicate only a part of the information to be instructed, while the other parts of the information to be instructed are known or agreed upon in advance. For example, the instruction of specific information can also be achieved by using the arrangement order of various information in advance (e.g., protocol stipulation), thereby reducing the instruction overhead to a certain extent. In addition, the information to be instructed can be sent as a whole or divided into multiple sub-information to be sent separately, and the sending period and / or sending time of these sub-information can be the same or different.

[0149] In the embodiments of this application, "send" and "receive" indicate the direction of signal transmission. For example, "send information to XX" can be understood as the destination of the information being XX, which may include direct transmission via the air interface or indirect transmission by other units or modules via the air interface. "Receive information from YY" can be understood as the source of the information being YY, which may include direct reception from YY via the air interface or indirect reception from YY by other units or modules via the air interface. "Send" can also be understood as the "output" of the chip interface, and "receive" can also be understood as the "input" of the chip interface. In other words, sending and receiving can occur between devices, such as between network devices and terminal devices, or within a device, such as between components, modules, chips, software modules, or hardware modules within the device via a bus, wiring, or interface.

[0150] In this application, the terms "exemplary" or "for example" are used to indicate that something is an example, illustration, or description. Any embodiment or design described as "exemplary" or "for example" in this application should not be construed as being more preferred or advantageous than other embodiments or designs. Specifically, the use of terms such as "exemplary" or "for example" is intended to present the relevant concepts in a specific manner.

[0151] 3GPP proposed the fifth-generation mobile communication system (the 5GPP). th 5GS (5G Generation System) possesses capabilities such as high bandwidth, high reliability, and low latency. With the development of satellite communication technology, the bandwidth capacity of communication satellites has significantly increased while costs have decreased. The convergence of satellite networks and 5G networks is emerging, and their powerful coverage capabilities can help 5G networks reach sparsely populated remote areas, as well as areas difficult for terrestrial networks to reach, such as oceans and isolated islands.

[0152] 3GPP proposes using satellites as radio frequency modules for base stations, providing transparent forwarding capabilities, i.e., satellite communication systems in transparent mode. In addition, 3GPP also proposes that satellites support data processing, i.e., satellites provide non-transparent forwarding capabilities (or regenerative capabilities), i.e., satellite communication systems in regenerative mode.

[0153] For example, Figure 1 illustrates a satellite communication system in regenerative mode. As shown in Figure 1, access network elements (such as base stations) in the radio access network (RAN) are deployed on the satellite. Terminals access the 5G core network (CN) (which can be abbreviated as 5GC) through the RAN. The RAN deployed on the satellite can also be called a spaceborne RAN or spaceborne base station, etc., and it has regenerative capabilities.

[0154] Alternatively, Figure 2 illustrates a satellite communication system in another regenerative mode. As shown in Figure 2, the RAN and user plane functions (UPFs) are deployed on the satellite. UPFs deployed on the satellite are called onboard UPFs, and they possess user plane data forwarding capabilities.

[0155] The following provides examples of the implementation methods for the various devices or network elements mentioned above.

[0156] A terminal is a device with wireless transceiver capabilities. It may also be called user equipment (UE), terminal equipment, access station, UE station, remote station, wireless communication equipment, or user device. It can be a fixed device, mobile device, handheld device, wearable device, vehicle-mounted device, or a wireless device (e.g., communication module or chip system) built into the above devices. The terminal is used to connect people, things, machines, etc., and can be widely used in various scenarios, including but not limited to the following: cellular communication, device-to-device (D2D) communication, vehicle-to-everything (V2X) communication, machine-to-machine / machine-type communications (M2M / MTC) communication, Internet of Things (IoT), virtual reality (VR), augmented reality (AR), industrial control, self-driving, remote medical care, smart grid, smart furniture, smart office, smart wearables, smart transportation, smart city, drones, robots, and other scenarios.

[0157] The RAN involved in the embodiments of this application can be a 3GPP-related cellular system, such as a 5G / new radio (NR) mobile communication system, or a future-oriented communication system (or future evolution communication system). The RAN can also be an open RAN (O-RAN or ORAN), a cloud radio access network (CRAN), or a virtualized RAN (vRAN), etc. The RAN can also be a communication system that integrates two or more of the above systems. Access network elements in the RAN can also be referred to as RAN equipment, RAN nodes, RAN entities, or access nodes, etc.

[0158] In one possible scenario, access network elements can be base stations, evolved NodeBs (eNodeBs), access points (APs), transmission reception points (TRPs), next-generation NodeBs (gNBs), next-generation base stations in future communication systems (or future evolved communication systems), and base stations in future mobile communication systems. Access network elements can also be macro base stations, micro base stations, indoor stations, relay nodes, donor / host nodes, or radio controllers. Access network elements can also be servers, wearable devices, vehicles, or in-vehicle equipment. For example, in V2X technology, the access network element can be a roadside unit (RSU).

[0159] In another possible scenario, the access network element can be a module or unit that performs some of the functions of the base station; or multiple access network elements can collaborate to assist terminal devices in achieving wireless access, with different access network elements performing some of the functions of the base station. For example, the access network element can be a central unit (CU), a distributed unit (DU), or a radio unit (RU). The function of the CU can be implemented by a single entity or by different entities. For example, the function of the CU can be further divided, that is, the control plane and the user plane can be separated and implemented by different entities, namely the control plane CU entity (i.e., CU-control plane (CP) entity) and the user plane CU entity (i.e., CU-user plane (UP) entity). The CU-CP entity and the CU-UP entity can be coupled with the DU to jointly complete the function of the access network element. The CU and DU can be set up separately or included in the same network element, such as in the baseband unit (BBU).

[0160] In different systems, CU (or CU-CP and CU-UP), DU, or RU may have different names, but those skilled in the art will understand their meaning. For example, in an ORAN system, CU can also be called an open CU (O-CU), DU can also be called O-DU, CU-CP can also be called O-CU-CP, CU-UP can also be called O-CU-UP, and RU can also be called O-RU. The access network element in the embodiments of this application can be any unit among CU, CU-CP, CU-UP, DU, and RU, and can be implemented through software modules, hardware modules, or a combination of software modules and hardware modules.

[0161] The CU and DU can be configured according to the protocol layer functions of the wireless network they implement. For example, the CU can be configured to implement the functions of the Packet Data Convergence Protocol (PDCP) layer and above (e.g., the Radio Resource Control (RRC) layer and / or the Service Data Adaptation Protocol (SDAP) layer); the DU can be configured to implement the functions of the protocol layers below the PDCP layer (e.g., the Radio Link Control (RLC) layer, the Media Access Control (MAC) layer, and / or the Physical (PHY) layer). Alternatively, the CU can be configured to implement the functions of the protocol layers above the PDCP layer (e.g., the RRC and / or SDAP layers), and the DU can be configured to implement the functions of the protocol layers below the PDCP layer (e.g., the RLC, MAC, and / or PHY layers). For specific descriptions of the above protocol layers, please refer to the relevant 3GPP technical specifications or the technical specifications of other applicable communication protocols. The above-described division of the processing functions of CU and DU according to protocol layers is merely an example; other division methods are also possible, and this application does not limit the scope. For example, in one design, CU or DU can be further divided into processing functions with protocol layers. In one design, some functions of the RLC layer and the functions of the protocol layer above the RLC layer are located in the CU, while the remaining functions of the RLC layer and the functions of the protocol layer below the RLC layer are located in the DU.

[0162] 5GC may include one or more core network elements, such as the access and mobility management function (AMF), unified data repository (UDR), authentication server function (AUSF), and location management function (LMF), etc., without specific limitations. AMF is mainly responsible for access management functions, UDM is used to store subscription data and policy data, etc. AUSF is used to implement user authentication. LMF is used to locate terminals.

[0163] In this application embodiment, the device used to implement the function of a terminal can be a device or a means to support the terminal in implementing that function, such as a chip system or a chip. This means can be installed in the terminal, and there is no limitation on its use. In this application embodiment, a network element can be a single device, or a means integrating multiple devices, or a software or hardware module (such as a chip or chip system) within a device. The network element shown in this application embodiment can also be a logical concept, such as a software module, or a network function corresponding to the services provided by various network elements. A network function can be understood as a virtualized function implemented under virtualization, or as a network function providing services under a service-oriented network. This application embodiment does not specifically limit its use in this regard.

[0164] In one possible implementation, core network elements may utilize the 3GPP-defined location service (LCS) to perform UE location verification (also known as terminal location check or terminal location verification) in certain situations. This verifies that the physical location of the terminal falls within the permitted service area (or operating area) of the access PLMN, thus meeting regulatory compliance requirements. For example, if the terminal is located at a national border, and the cell information reported by the RAN is insufficient to accurately reflect the UE's location, or due to distrust of the UE's own GNSS-reported location, the core network may invoke the LCS service to verify the terminal's location.

[0165] Specifically, the Access and Mobility Management (AM) network element or Mobility Management Entity (MME) sends a terminal location request to the Location Management Function (LMF) or Evolved Serving Mobile Location Center (E-SMLC). The LMF / E-SMLC calculates the terminal's location by exchanging location-related messages with the RAN and the terminal, and then returns the terminal's location to the AM or MME. The AM / MME relies on the terminal location returned by the LMF / E-SMLC to perform terminal location verification, that is, to determine whether the area represented by the terminal location is within the service range permitted by the current PLMN. If it is found that the terminal is not within the service range permitted by the PLMN currently serving the terminal, the network will initiate deregistration, that is, disallow the terminal from accessing the network to meet compliance requirements.

[0166] The LMF / E-SMLC can determine the terminal location through multiple round-trip times (RTT) (abbreviated as Multi-RTT / multi-RTT). The following is an example of the multi-RTT positioning process.

[0167] LMF / E-SMLC can measure the signal transmission and reception times between the access network element and the terminal to obtain the round-trip time (RTD) of signal transmission between the terminal and the access network element. Based on the RTD of the signal transmission between the terminal and the access network element, the distance from the terminal to the access network element can be obtained, thus allowing the terminal's location to be inferred. For example, a circle can be defined with the access network element as the center and the distance from the terminal to the access network element as the radius. The intersection of the three circles is the location of the terminal. Therefore, this positioning method relies on at least three access network elements.

[0168] Specifically, Multi-RTT combines uplink and downlink positioning, requiring the terminal and multiple access network elements, or transmission receive points (TRPs), to send reference signals to each other. LMF / E-SMLC determines the terminal's location based on the time difference between the terminal's received and transmitted signals, and the time difference between the access network elements' received and transmitted signals.

[0169] The positioning process requires both the terminal and the transmitting node (access network element) to measure the signal arrival time. For downlink signals, the access network element records the transmission time t0 using its local clock, and the terminal measures the downlink signal arrival time t1 using its local clock. For uplink signals, the terminal records the transmission time t2 using its local clock, and the access network element measures the uplink signal arrival time t3 using its local clock. The final measured RTT is (t3-t0)-(t2-t1). This RTT can then be used to estimate the terminal's location.

[0170] In terrestrial 5GS, the RAN and core network elements (such as LMF) can exchange New Radio Positioning Protocol A (NRPPa) messages to transmit RAN measurement-related information; the terminal and LMF can also exchange NRPPa messages to transmit terminal measurement-related information; the LMF can calculate the terminal's location based on the obtained measurement information.

[0171] The LMF can send a request to the access network element via NRPPa to request measurement results from the access network element. This request can carry uplink-sounding reference signaling (UL-SRS) transmission characteristics, including the number / duration of requested UL-SRS transmissions, bandwidth, resource type, requested SRS resource set, the number of each SRS resource set, and the carrier frequency of the SRS transmission bandwidth. The LMF can also send a request to the RAN via NRPPa, carrying TRP measurement request information, including the TRP ID, the NR cell global identifier (NCGI) of the TRP receiving the UL-SRS, terminal-SRS configuration, measurement period, measurement quality, and response time.

[0172] The RAN can send uplink information / terminal configuration data to the LMF via NRPPa. Configuration data includes the terminal's Sounding Reference Signal (SRS) configuration, as well as auxiliary information such as the cell global identifier and TRP ID. It can also send measurement results, including the corresponding cell ID, TRP ID, RAN Rx-Tx (transmit-receive) time difference, and measurement timestamp.

[0173] LMF can send requests to the terminal via the LPP protocol, carrying auxiliary data, including the cell global identifier and downlink-positioning reference signaling (DL-PRS) configurations for candidate TRPs. LMF can also request positioning methods / capabilities supported by the terminal via LPP.

[0174] The terminal can send measurement results to the LMF via the LPP protocol, including the cell ID and TRP ID corresponding to the measurement results, the terminal's Rx-Tx (transmit-receive) time difference, and the measurement timestamp. The terminal can also return the positioning methods it supports to the LMF via LPP, such as supporting Multiple-RTT-based positioning in satellite access scenarios.

[0175] In 4G systems, the NRPPa protocol involved in the above positioning process can be replaced by the LTE positioning protocol (LPP). LMF can be replaced by E-SMLC.

[0176] The following example illustrates terminal location verification using Figure 3 as a schematic diagram. As shown in Figure 3, the PLMN currently serving the terminal is PLMN#1. If the terminal's location is actually within the service area allowed by PLMN#1, the terminal location verification is compliant; if the terminal's location is not within the service area allowed by PLMN#1, the terminal location verification is non-compliant.

[0177] In addition, due to the relative motion of non-geosynchronous satellites such as low earth orbit (LEO) and medium earth orbit (MEO) with respect to the ground, a single satellite or multiple satellites that do not yet have inter-satellite link networking, or a constellation with a few sparse inter-satellite links, will result in discontinuous coverage when the terminal uses satellite access.

[0178] To prevent terminals from continuously searching for signals when there is no satellite coverage, enhancements have been implemented. After losing satellite coverage, the terminal deactivates the access stratum (AS) function and enters sleep mode. Based on ephemeris data obtained from the RAN and timers set based on coverage availability information obtained from the core network, the terminal wakes up when satellite coverage resumes (the terminal stores the AS information). Correspondingly, high-latency communication also supports discontinuous coverage scenarios. The MME considers discontinuous satellite access coverage when configuring the buffer timer (setting the storage duration based on the terminal's reachability).

[0179] In reality, terminals may be located in areas such as the sea or polar regions. When covered by a satellite, the satellite cannot establish a connection with the ground station, meaning there is no available power supply link. For example, Figure 4 illustrates a scenario of discontinuous coverage. As shown in Figure 4, at time #1, the satellite is over the ocean and can cover the terminal, but because there is no power supply link, the satellite cannot establish a connection with the 5GC on land through the ground gateway station; at time #2, the satellite moves to over land and can access the 5GC through the ground gateway station; at time #3, the satellite covers the terminal over the ocean again. In this case of discontinuous coverage, to enable the terminal to send and receive data, the satellite needs to support store-and-forward, and the satellite needs to support uplink and downlink data caching to achieve latency and interruption tolerance. Therefore, 3GPP is discussing support for store-and-forward services in this scenario (i.e., when the service link and the power supply link are not available simultaneously) based on the regenerator satellite model.

[0180] Based on the above, the method of terminal location verification based on LCS service may have the following two problems:

[0181] The first problem is that Internet of Things (IoT) devices may be unable to support LCS services due to hardware limitations, and therefore cannot be used for the aforementioned terminal location verification. Therefore, how to verify the location of IoT devices in satellite access scenarios is an urgent problem to be solved.

[0182] The second issue is that since LCS services rely on network elements in the core network, and the satellite and ground station cannot establish a connection when the power supply link is disconnected, how to perform terminal location verification in this scenario needs to be addressed.

[0183] To address the first problem mentioned above, this application provides a first communication method. In this method, a first communication device can obtain first information indicating the location of a terminal from a second communication device. If the terminal's location is within the service range permitted by a first public land mobile network, the first device sends the cell identifier corresponding to the terminal's location to a first mobility management device. If the terminal's location is not within the service range permitted by the first public land mobile network, the first device sends the cell identifier corresponding to the terminal's location to a compliant mobility management network element (such as a second mobility management device). This allows for direct terminal location verification based on the terminal's location, providing a terminal location verification mechanism. Furthermore, if the terminal location verification is non-compliant, the second device sends the cell identifier corresponding to the terminal's location to the second mobility management network element, enabling the second mobility management network element to promptly page the terminal based on the cell identifier, thus improving the efficiency of terminal registration or service.

[0184] To address the second problem mentioned above, this application provides a second communication method in which network elements (such as location regulation proxy (LRP) network elements) can be deployed on the satellite. The location regulation proxy network element can perform terminal location verification. Thus, terminal location verification can be performed without relying on core network elements, enabling the method to perform terminal location verification even when the power supply link is unavailable.

[0185] To address the second problem mentioned above, this application also provides a third communication method. In this method, an access network element can be deployed on the satellite. The access network element can clearly determine the terminal location verification result. For example, the access network element can directly perform the terminal location verification, or the access network element can obtain the terminal location verification result from the location compliance agent network element. Thus, there is no need to rely on core network elements or the like to perform terminal location verification, enabling the method to perform terminal location verification even when the power supply link is unavailable.

[0186] Any of the communication methods provided in the embodiments of this application can be applied to the communication systems involved in Figures 1 to 4. Furthermore, the first communication method described above can be applied to satellite communication systems in transparent access mode or regenerative mode, without limitation. In addition, any of the communication methods provided in the embodiments of this application can also be applied to the communication scenario shown in Figure 5 below. The communication scenario shown in Figure 5 will be described below.

[0187] As shown in Figure 5, this communication scenario includes terminals, satellites, and mobility management network elements (such as a first mobility management network element or a second mobility management network element). Access network elements can be deployed on the satellite. Optionally, location compliance agent network elements and positioning network elements can also be deployed on the satellite.

[0188] Access network elements can be used to connect terminals to the network. Location compliance agent network elements can receive uplink and / or downlink messages, such as when the serving link and power supply are not established simultaneously, and forward location-related messages. Location network elements can be used to receive location requests and determine the terminal's location, for example, by invoking NRPPa and LPP messages. Location network elements may be, for example, LMF / E-SMLC. Mobility management network elements can be used for terminal access to the network, such as AMF / MME.

[0189] The location compliance agent network element is deployed on a satellite. This can be understood as the function for terminal location verification being deployed on a satellite. The location compliance agent network element may be an independent network element on the satellite, or it may be an addition to an existing network element on the satellite, or it may integrate the terminal location verification function onto the first satellite. This application embodiment does not specifically limit the specific implementation method of the location compliance agent network element, nor does it specifically limit the name of the location compliance agent network element; that is, the location compliance agent network element may have other names, which are not specifically limited. A new interface can be added between the location compliance agent network element and the mobility management network element. This interface is used for communication between the two. Figure 5 uses the Np2 or Sp1 interface as an example, but the actual interface name is not limited. The location compliance agent network element and the access network element can communicate through the N2 or S1 interface; the interface name is not specifically limited. The location compliance agent network element and the positioning network element can communicate through the NL1 or SLs interface.

[0190] The first mobility management network element in Figure 5 belongs to the first PLMN; in other words, the first mobility management network element provides services to terminals accessing the first PLMN. The second mobility management network element belongs to the second PLMN; in other words, the second mobility management network element provides services to terminals accessing the second PLMN.

[0191] In one possible implementation, the first communication device mentioned in the first communication method provided in this application embodiment may be the first mobility management network element involved in FIG5, and the second communication device may be the terminal involved in FIG5. Alternatively, the first communication device may be the access network element involved in FIG5, and the second communication device may be the first mobility management network element involved in FIG5.

[0192] The above is a detailed description of some scenarios applicable to the embodiments of this application. In fact, the embodiments of this application can be applied to various similar scenarios, and no specific limitations are made here.

[0193] The communication scheme provided by the embodiments of this application is described below with reference to the accompanying drawings. In the accompanying drawings corresponding to the various embodiments of this application, all steps indicated by dashed lines are optional steps. Furthermore, the access network elements involved in the various embodiments of this application may be, for example, the RAN involved in Figure 1, the RAN involved in Figure 2, or the access network elements involved in Figure 5; the first mobility management network element involved in the various embodiments of this application may be, for example, the first mobility management network element involved in Figure 5; the second mobility management network element involved in the various embodiments of this application may be, for example, the second mobility management network element involved in Figure 5; the terminal involved in the various embodiments of this application may be, for example, any of the terminals involved in Figures 1 to 4 or Figure 5; the location compliance agent network element involved in the various embodiments of this application may be the LRP involved in Figure 5; the first satellite involved in the various embodiments of this application may be, for example, any of the satellites involved in Figures 1 to 5; and the first positioning network element may be, for example, the positioning network element involved in Figure 5. Furthermore, as standards continue to evolve, the names and / or functions of network elements, information, or messages involved in various embodiments of this application may change, but this is not a limitation.

[0194] The first communication method provided in the embodiments of this application will be introduced below.

[0195] Please refer to Figure 6, which is a schematic diagram of the first communication method provided in an embodiment of this application. The steps involved in Figure 6 will be described below.

[0196] S601, the second communication device sends first information to the first communication device. Correspondingly, the first communication device receives the first information from the second communication device. The first information indicates the location of the terminal. For example, the first information may include N bits, where N is a positive integer, and these N bits may indicate the location of the terminal.

[0197] The location information of the terminal differs, and correspondingly, the way the first information indicates the location of the terminal (specifically, the way the N bits indicate the location of the terminal) also differs, which will be introduced separately below.

[0198] The first scenario involves the terminal's location being its geographic location. In this case, the primary information includes the terminal's geographic location. The details of the terminal's geographic location can be found in the previously discussed section on geographic locations, and will not be repeated here. For example, the terminal's geographic location could be its GNSS location, and the details of the GNSS location can also be found in the previously discussed section on GNSS locations.

[0199] For example, the terminal's geographical location information can be its latitude and longitude, and may also include relative altitude, etc. These N bits can carry the terminal's latitude and longitude, and may also include relative altitude, etc. In this way, the terminal's location can be indicated intuitively and precisely.

[0200] For example, N1 bits out of N bits can be used to carry the longitude of the terminal, and N2 bits out of N bits can be used to carry the latitude of the terminal. N1 and N2 are both positive integers, and the sum of N1 and N2 is less than or equal to N. N1 bits can be N1 bits starting from the most significant bit, the least significant bit, or a preset bit out of the N bits. N2 bits can be N2 bits starting after N1 bits, or N2 bits starting from the most significant bit, the least significant bit, or a preset bit out of the N bits, etc. The position of the starting bit of N1 bits or N2 bits within the N bits is not limited.

[0201] Optionally, N3 bits out of the N bits can be used to carry the relative height of the terminal, where N3 is a positive integer, and the sum of N1, N2, and N3 can be equal to N. The N3 bits can be N3 bits starting from the end of N1 bits, or N3 bits starting from the end of N2 bits, or N3 bits starting from the most significant bit, least significant bit, or a preset bit, etc., without limitation.

[0202] For example, if the terminal's geographical location is (20, 20, 100), the second communication device can use N bits, such as 10100101001100100, which is equivalent to the first information indicating the terminal's location. Of these N bits, the first 5 bits from left to right represent longitude, the 6th to 10th bits from left to right represent latitude, and the 6th to 12th bits represent the terminal's relative altitude.

[0203] The second type is where the terminal's location is the PLMN to which the terminal's geographical location belongs. In this case, the first piece of information includes the PLMN's identifier.

[0204] For example, N bits in the first information are used to carry the identifier of the PLMN. For instance, if the PLMN to which the terminal's geographical location belongs is the first PLMN and the identifier of the first PLMN is 1, then N bits can carry 1, which is equivalent to indicating the location of the terminal; or, if the PLMN to which the terminal's geographical location belongs is the second PLMN and the identifier of the second PLMN is 2, then N bits can carry 2, which is equivalent to indicating the location of the terminal.

[0205] The third type involves the terminal's location being the cell identifier corresponding to its geographic location. In this case, the first piece of information includes the cell identifier. The content of the cell identifier can be found in the previous discussion and will not be listed here again.

[0206] For example, if the location of the terminal is the cell identifier corresponding to the terminal's geographical location, then N bits can carry 1, which is equivalent to indicating the location of the terminal.

[0207] Fourthly, if the terminal's location is the synchronization signal corresponding to the terminal, then the first information can indicate the index of that synchronization signal.

[0208] For example, if the synchronization signal corresponding to the terminal is SSB2, then N bits can carry 2, which is equivalent to indicating the location of the terminal.

[0209] Fifthly, if the physical region where the terminal is located (for ease of distinction, the physical region where the terminal is located will be referred to as the first physical region below), then the first information can indicate the number of the physical region where the terminal is located. The N bits in the first information carry the number of the first physical region, which is equivalent to the first information indicating the location of the terminal. The number of the first physical region can be negotiated between the second communication device and the first communication device, or it can be pre-configured or predefined by the protocol, such as being determined by the protocol; no specific limitation is made. Optionally, the number of the first physical region can be, for example, the administrative region code corresponding to the location of the terminal. Using a number indicating the geographical location of the terminal helps to save bit overhead.

[0210] For example, the first physical region is numbered 1, which corresponds to the terminal's geographical location belonging to province A, meaning that the terminal is located in a certain location within province A.

[0211] Of course, there are many other ways to indicate the location of the terminal with the first information, and this application does not specifically limit this.

[0212] Since the first communication device and the second communication device are different, the implementation form of the first information and the way the second communication device sends the first information to the first communication device may also differ. These will be described separately below.

[0213] A1. The first communication device is an access network element, and the second communication device is a first mobility management network element. The first mobility management network element is the mobility management network element currently serving the terminal. The first mobility management network element belongs to the first PLMN, or can be understood as the first mobility management network element serving the terminal in the first PLMN. Optionally, the first mobility management network element can directly send first information to the access network element. The type of the first information can be a NAS message. The first information can be specifically carried in a registration request or service request.

[0214] Optionally, under A1, the second communication device determines whether the terminal's location is within the service range permitted by the first PLMN. Furthermore, the second communication device further indicates, via the first information, that the terminal is within the service range permitted by the first PLMN, or that the terminal is not within the service range permitted by the first PLMN. Thus, by receiving the first information, the first communication device can clearly determine whether the terminal's location is within the service range permitted by the first PLMN.

[0215] For example, the second communication device may determine the PLMN currently serving the terminal as the first PLMN based on the first information, or the second communication device may pre-store the PLMN currently serving the terminal as the first PLMN. For instance, the second communication device may pre-store the first PLMN currently serving the terminal during the terminal access process, and then the second communication device may directly determine whether the terminal's location is within the service range allowed by the first PLMN based on the terminal's location.

[0216] The determination of whether the terminal's location is within the service range permitted by the first PLMN can be described as follows: determining whether the terminal's location is within the service range permitted by the first PLMN (or not within the service range permitted by the first PLMN); determining whether the terminal is within the service range permitted by the first PLMN; or determining whether the terminal is within the service range permitted by the first PLMN (or not within the service range permitted by the first PLMN), without specific limitations.

[0217] Since the specific details of the terminal's location differ, the second communication device will determine whether the terminal's location falls within the service area permitted by the first PLMN in different ways, which will be described below.

[0218] B1. The location of the terminal is its geographical location.

[0219] Under B1, the second communication device can directly determine whether the terminal's geographical location is within the service range permitted by the first PLMN.

[0220] If the terminal's geographical location is within the service area permitted by the first PLMN, then the terminal's location is within the service area permitted by the first PLMN. If the terminal's geographical location is not within the service area permitted by the first PLMN, then the terminal's location is not within the service area permitted by the first PLMN.

[0221] B2. The location of the terminal is the cell corresponding to the terminal.

[0222] If the cell represents a physical cell, then the second communication device can directly determine whether the physical cell corresponding to the terminal is within the service range allowed by the first PLMN.

[0223] For example, if all cells corresponding to the terminal are within the service range allowed by the first PLMN, or the center of the cell corresponding to the terminal is within the service range allowed by the first PLMN, or a first specific area of ​​the cell corresponding to the terminal is within the service range allowed by the first PLMN, or the overlapping area between the cell corresponding to the terminal and the service range allowed by the first PLMN is greater than or equal to a second preset range, then the terminal's location is within the service range allowed by the first PLMN. The first specific area is, for example, the central area of ​​the cell. If none of the cells corresponding to the terminal are within the service range allowed by the first PLMN, or the center of the cell corresponding to the terminal is not within the service range allowed by the first PLMN, or the first specific area of ​​the cell corresponding to the terminal is not within the service range allowed by the first PLMN, or the edge area corresponding to the terminal is not within the service range allowed by the first PLMN, or the overlapping area between the cell corresponding to the terminal and the service range allowed by the first PLMN is less than the second preset range, then the terminal's location is not within the service range allowed by the first PLMN. The ranges of the first specific area, the edge area, and the second preset range can all be pre-configured or pre-defined in the second communication device, or determined by the second communication device itself; there is no limitation on this.

[0224] If the cell represents a logical cell and the logical cell corresponds to a physical cell, then the second communication device can directly determine whether the physical cell corresponding to the logical cell of the terminal is within the service range allowed by the first PLMN. The method for determining whether the physical cell is within the service range allowed by the first PLMN can be referred to the content discussed above, and will not be listed here.

[0225] If the cell is identified as a logical cell and the logical cell corresponds to a geographical area, then the second communication device can directly determine whether the geographical area is within the service range allowed by the first PLMN.

[0226] For example,

[0227] B3. The location of the terminal is the PLMN corresponding to the terminal.

[0228] Under B3, the second communication device can directly determine whether the PLMN to which the terminal's geographical location belongs is the first PLMN.

[0229] If the PLMN to which the terminal's geographical location belongs is the first PLMN, then the terminal's location is within the service area permitted by the first PLMN. If the PLMN to which the terminal's geographical location belongs is not the first PLMN, then the terminal's location is not within the service area permitted by the first PLMN.

[0230] If the entire geographical area is within the service range permitted by the first PLMN, or if the geographical area is within the service range permitted by the first PLMN, or if the second specific area of ​​the geographical area is within the service range permitted by the first PLMN, or if the geographical area overlaps with the service range permitted by the first PLMN, or if the overlapping area of ​​the geographical area and the service range permitted by the first PLMN is greater than or equal to the second preset range, then the terminal's location is within the service range permitted by the first PLMN. The second specific area is, for example, the central area of ​​the geographical area. If the geographical area is not within the service range permitted by the first PLMN, or if the center of the geographical area is not within the service range permitted by the first PLMN, or if the second specific area of ​​the geographical area is not within the service range permitted by the first PLMN, or if the edge area of ​​the geographical area is not within the service range permitted by the first PLMN, or if the overlapping area of ​​the geographical area and the service range permitted by the first PLMN is less than the second preset range, then the terminal's location is not within the service range permitted by the first PLMN. The ranges of the second specific area, the edge area, and the second preset range can all be pre-configured or pre-defined in the second communication device, or determined by the second communication device itself; there are no limitations on this.

[0231] B4. The location of the terminal is the synchronization signal corresponding to the terminal.

[0232] Under B4, the second communication device can directly determine whether the region corresponding to the synchronization channel (hereinafter referred to as the first region for ease of description) is located in the first PLMN.

[0233] If all first regions are within the service range permitted by the first PLMN, or if all third specific regions of the first region are within the service range permitted by the first PLMN, or if the overlap between the first region and the first PLMN's service range is greater than or equal to a second preset range, then the terminal's location is within the service range permitted by the first PLMN. The third specific region is, for example, the central region of the first region. If none of the first regions are within the service range permitted by the first PLMN, or if the center of the first region is not within the service range permitted by the first PLMN, or if the third specific region of the first region is not within the service range permitted by the first PLMN, or if the edge region of the first region is not within the service range permitted by the first PLMN, or if the overlap between the first region and the first PLMN's service range is less than the second preset range, then the terminal's location is not within the service range permitted by the first PLMN. The ranges of the third specific region, the edge region, and the second preset range can all be pre-configured or pre-defined in the second communication device, or determined by the second communication device itself; there are no limitations on this.

[0234] B5. The location of the terminal is the physical area corresponding to the terminal.

[0235] Under B5, the second communication device can directly determine whether the PLMN to which the physical area corresponding to the terminal belongs is the first PLMN.

[0236] If all physical areas are within the service range permitted by the first PLMN, or if all fourth specific areas of the physical areas are within the service range permitted by the first PLMN, or if the overlap between the physical areas and the first PLMN's service range is greater than or equal to the second preset range, then the terminal's location is within the service range permitted by the first PLMN. The fourth specific area is, for example, the center area of ​​the physical areas. If none of the physical areas are within the service range permitted by the first PLMN, or if the center of the physical areas is not within the service range permitted by the first PLMN, or if the fourth specific area of ​​the physical areas is not within the service range permitted by the first PLMN, or if the edge areas of the physical areas are not within the service range permitted by the first PLMN, or if the overlap between the physical areas and the first PLMN's service range is less than the second preset range, then the terminal's location is not within the service range permitted by the first PLMN. The ranges of the fourth specific area, the edge areas, and the second preset range can all be pre-configured or pre-defined in the second communication device, or determined by the second communication device itself; there are no limitations on this.

[0237] A2. The first communication device is a first mobility management network element, and the second communication device is a terminal.

[0238] The first information can be of various types, such as N2 interface messages or S1 interface messages, without specific limitations. The first information can be carried in a registration request or service request. The content of the registration request and service request can be referred to the previous discussion, and will not be listed again unless repeated. Optionally, under A2, the terminal can send the first information to the first mobility management network element through the access network element.

[0239] S602. When the terminal is within the service range permitted by the first PLMN, the first communication device sends the cell identifier to the first mobility management network element.

[0240] If the first information indicates that the terminal's location is within the service range permitted by the first PLMN, or if the terminal's location is not within the service range permitted by the first PLMN, the first communication device, after receiving the first information, can determine whether the terminal is within the service range permitted by the first PLMN. Alternatively, the first communication device can determine whether the terminal is within the service range permitted by the first PLMN based on the terminal's location. The method by which the first communication device determines whether the terminal is within the service range permitted by the first PLMN can refer to the previous section on the second communication device determining whether the terminal is within the service range permitted by the first PLMN based on its location; repetitions will not be listed here.

[0241] In summary, the first communication device can determine whether the terminal's location is within the service area permitted by the first PLMN, or whether the terminal's location is not within the service area permitted by the first PLMN. If the terminal's location is within the service area permitted by the first PLMN, then the first communication device can send the cell identifier to the first mobility management network element.

[0242] For example, the first communication device may be pre-configured or pre-defined with a first correspondence, which includes a correspondence between geographical regions and cell identifiers. Thus, the first communication device can determine the geographical region corresponding to the terminal's location based on the first correspondence and the terminal's location, and then determine the cell identifier corresponding to that geographical region, which is the cell identifier corresponding to the terminal's location. Multiple geographical regions corresponding to multiple cell identifiers may partially overlap, and this is not limited. Alternatively, if the first information indicates the terminal's location through a cell identifier, then the first communication device can directly determine the cell identifier based on the first information.

[0243] The content of the cell identifier is similar to that described earlier and will not be repeated here. The cell identifier essentially indicates the location of the terminal and can be used to pinpoint the terminal's location, as well as for paging the terminal. In satellite communication systems, satellites move at high speeds, so the first communication device promptly sends the cell identifier to the first mobility management network element. This allows the first mobility management network element to promptly detect the terminal's location, register the terminal more quickly, and provide services to the terminal.

[0244] In addition to sending the cell identifier to the first mobility management network element, if the first information is carried in the registration request or service request, the first communication device may optionally forward the registration request or service request to the first mobility management network element as well, enabling the first mobility management network element to register the terminal in a timely manner or provide services to the terminal. In this case, the first communication device may carry the cell identifier in the registration request or service request and send it to the first mobility management network element together.

[0245] S603. If the terminal is not within the service range permitted by the first PLMN, the first communication device sends the cell identifier to the second mobility management network element.

[0246] The second mobility management element belongs to the PLMN corresponding to the terminal's location, or it can be understood as the mobility management element serving the terminal within the second PLMN. That is, the mobility management element currently serving the terminal is the first mobility management element, but the actual PLMN corresponding to the terminal's location may not be the first PLMN to which the first mobility management element belongs; it could be the second PLMN. In this case, the first communication device can send the cell identifier to the second mobility management element within the second PLMN. Thus, the second mobility management element can page the terminal earlier based on the cell identifier and provide services to the terminal, facilitating rapid handover and network access for the terminal.

[0247] The following is an example of how the first communication device determines the second mobility management network element.

[0248] The first communication device may pre-store a second correspondence, which indicates the correspondence between the second PLMN and the mobility management network element. For example, the second correspondence includes the correspondence between the identifier of the second PLMN and the identifier of the mobility management network element. In this way, the first communication device can directly determine that the mobility management network element corresponding to the second PLMN is the second mobility management network element, and send the cell identifier to the second mobility management network element.

[0249] When there are multiple mobility management network elements corresponding to the second PLMN, the first communication device may determine the mobility management network element that is closest to the terminal among these multiple mobility management network elements as the second mobility management network element, or determine the mobility management network element with the best communication quality with the terminal among these multiple mobility management network elements as the second mobility management network element, without making specific limitations on this.

[0250] In addition to sending the cell identifier to the second mobility management network element, if the first information is carried in the registration request or service request, the first communication device may optionally forward the registration request or service request to the second mobility management network element, enabling the second mobility management network element to register the terminal or provide services to the terminal in a timely manner. In this case, the first communication device may optionally include the cell identifier in the registration request or service request and send it to the second mobility management network element. This eliminates the need for the terminal to separately initiate registration or service requests to the second mobility management network element, reducing the number of interactions in the communication system.

[0251] S602 and S603 represent two possible scenarios. During a terminal location verification process, either step S602 or step S603 will be executed.

[0252] In this embodiment, the second communication device can send the terminal's location to the first communication device, enabling the first communication device to perform terminal location verification itself, or the first communication device can obtain the terminal location verification result from the first mobility management network element. This provides a mechanism applicable to various terminal devices such as IoT devices for terminal location verification. Furthermore, if the terminal location verification is compliant, the first communication device can map the terminal's location into a cell identifier and send it to the first mobility management network element, allowing the first mobility management network element to quickly register the terminal for service. If the terminal location verification is non-compliant, the first communication device can reselect a mobility management network element based on the terminal's actual location, allowing the newly selected mobility management network element to quickly register the terminal for service, reducing the time the terminal spends switching networks.

[0253] The first and second communication devices differ, and the interaction processes between the various network elements involved also differ. The following is an example illustrating the interaction between the various network elements, using a schematic diagram of a communication method shown in Figure 7. Figure 7 uses the situation shown in A1 above (i.e., the first communication device is an access network element, and the second communication device is a first mobility management element) as an example. The steps shown in Figure 7 are described below.

[0254] S701. A non-access stratum (NAS) connection is established between the terminal and the first mobility management network element. The first mobility management network element currently serves the terminal, belongs to the first PLMN, and the first PLMN currently serves the terminal.

[0255] For example, a terminal may request a first mobility management network element (MMI) to send a connection establishment request message. Optionally, this connection request message may carry the terminal's identifier. After receiving the connection establishment request message, the first MMI may send a NAS security mode command message to the terminal. This NAS security mode command message includes key information used to encrypt messages between the terminal and the first MMI. Optionally, the NAS security mode command message may also include algorithm information, enabling the terminal to specify the algorithm used with the first MMI, or the algorithm information may be pre-configured or predefined in the terminal.

[0256] In this way, the terminal can establish a NAS connection with the first mobility management network element through the access network element, which facilitates subsequent communication between the terminal and the first mobility management network element based on the NAS connection. Furthermore, if the terminal is an IoT device, specifically an NB-IoT device, the terminal may not support AS or AS communication may be insecure; in such cases, the terminal can utilize the established NAS connection to communicate with the first mobility management network element.

[0257] If the terminal has already established a NAS connection with the first mobility management network element, or has established other communication connections, then there is no need to execute step S701. That is, step S701 is optional and is shown as a dashed line in Figure 7.

[0258] S702, the terminal sends fourth information to the access network element. Correspondingly, the access network element receives the fourth information from the terminal. The fourth information indicates the terminal's location.

[0259] The fourth information can be a NAS message or other messages, and there is no specific limitation on it. For example, the fourth information can be carried in a registration request or service request, and the embodiments of this application do not limit the specific form of the fourth information. The way the fourth information indicates the location of the terminal can be referred to the content of the first information indicating the location of the terminal discussed in Figure 6 above, and the repetition will not be listed again. The meaning of the location of the terminal can be referred to the content of the location of the terminal involved in Figure 6 above, and will not be listed here.

[0260] For example, the terminal measures GNSS signals from the network side (such as access network elements) to obtain its location, specifically its GNSS location. Alternatively, the terminal may pre-store its own location. This application does not limit the method by which the terminal obtains its location.

[0261] When the terminal receives key information from the first mobility management network element, the terminal can also use the key information to encrypt the first information, or to encrypt the information carried in the first information that indicates the location of the terminal, so as to ensure the security of the terminal's location.

[0262] Optionally, in addition to indicating the location of the terminal, the fourth information may also include the terminal's identifier. Optionally, the fourth information may also include the identifier of the PLMN currently serving the terminal (i.e., the identifier of the first PLMN), etc. The content of the terminal's identifier and the PLMN's identifier can be referred to the content of the terminal's identifier and the PLMN's identifier mentioned above, and will not be listed here.

[0263] S703. The access network element sends the fifth information to the first mobility management network element. Correspondingly, the first mobility management network element receives the fifth information from the access network element. The fifth information indicates the location of the terminal.

[0264] The fifth information indicating the terminal's location can be referenced from the first information indicating the terminal's location discussed in Figure 6 above, and will not be listed here again. The fifth information can also be a NAS message. The third information can also be carried in the registration request or service request, without limitation. The content of the registration request and service request can refer to the content of the registration request or service request discussed above, and will not be listed here again. In addition to indicating the terminal's location, the fifth information can also include the terminal's identifier. Optionally, the fifth information can also include the identifier of the PLMN currently serving the terminal (i.e., the identifier of the first PLMN), etc.

[0265] The fifth piece of information can be exactly the same as the fourth piece of information, or they can be different. For example, the access network element can obtain the fifth piece of information by converting or encapsulating the fourth piece of information, and there is no limitation on this.

[0266] S704, the first mobility management network element determines whether the location of the terminal is within the service range permitted by the first PLMN.

[0267] If the third information indicates the identifier of the first PLMN, then the first mobility management network element can determine the PLMN currently serving the terminal as the first PLMN based on the fifth information. Alternatively, if the first mobility management network element corresponds to only one PLMN (or exclusively occupies one PLMN), then the first mobility management network element can independently determine its corresponding PLMN as the first PLMN. Alternatively, the first mobility management network element can pre-store the first PLMN serving the terminal. Furthermore, the first mobility management network element can directly determine whether the terminal's location is within the service range allowed by the first PLMN. The method by which the first mobility management network element determines whether the terminal's location is within the service range allowed by the first PLMN can be referred to the discussion in Figure 6 above regarding the second communication device determining whether the terminal's location is within the service range allowed by the first PLMN; repetitions will not be repeated.

[0268] Before the first mobility management network element determines whether the terminal's location is within the service range permitted by the first PLMN, optionally, if the fifth information is encrypted using key information, or if the information in the fifth information used to indicate the terminal's location is encrypted, then the first mobility management network element can use the key information corresponding to the terminal to decrypt the fifth information and obtain the terminal's location.

[0269] S705. The first mobility management network element sends first information to the access network element. Correspondingly, the access network element receives the first information from the first mobility management network element.

[0270] The content of the first information can refer to the content of the first information discussed in S601 above, and the repetition will not be listed again. In this case, the information in the first information used to indicate the location of the terminal can be unencrypted, so that the access network element can directly obtain the location of the terminal.

[0271] If the third information includes the terminal's identifier, the first information may optionally also include the terminal's identifier. If the third information also includes the identifier of the PLMN currently serving the terminal (i.e., the identifier of the first PLMN), the first information may optionally also include the identifier of the PLMN currently serving the terminal (i.e., the identifier of the first PLMN), etc.

[0272] When executing S704, optionally, the first information may also indicate whether the terminal's location (or the terminal itself) is within or outside the service area permitted by the first PLMN. Thus, the access network element can directly determine, based on the first information, whether the terminal's location is within or outside the service area permitted by the first PLMN.

[0273] [Correction based on Rule 91, February 18, 2025] The first mobility management network element may directly execute step S705 after obtaining the location of the terminal. Alternatively, the first mobility management network element may execute step S705 when the following first condition is met. The first condition includes at least one of C1 to C3 below.

[0274] C1. The terminal type is Type 1. For example, Type 1 means a terminal that belongs to the category of IoT devices, or Type 1 means a terminal that does not support LCS services, etc. There are no restrictions on this.

[0275] The first type can be pre-configured or pre-defined in the first mobility management network element, or it can be obtained by the first mobility management network element from the terminal, thereby determining whether the terminal type is the first type.

[0276] C2. The terminal uses satellite access. The access type used by the terminal can be any access technology or method that the terminal supports, or it can be the access technology used by the terminal for this specific access. Satellite access can be understood as the terminal accessing a network (such as the core network) via satellite, or the terminal providing network services via satellite.

[0277] The access type used by the terminal can be pre-configured or pre-defined in the first mobility management network element, or it can be obtained by the first mobility management network element from the terminal, thereby determining whether the terminal's access type is satellite access.

[0278] C3. Access network elements support terminal location verification. Supporting terminal location verification by access network elements can be understood as the access network element having the capability (or function) of terminal location verification, or the access network element having the capability to assist in terminal location verification.

[0279] For example, the terminal location verification supported by the access network element can be obtained by the first mobility management element from the access network element.

[0280] The above S704 to S705 can be regarded as a method one in which the access network element determines whether the location of the terminal is within or outside the service range allowed by the first PLMN.

[0281] S706, The access network element determines whether the terminal's location is within the service range allowed by the first PLMN.

[0282] The methods by which the access network element determines whether the terminal's location is within the service range permitted by the first PLMN can be referred to in S704, respectively, as well as the methods by which the first mobility management network element determines whether the terminal's location is within the service range permitted by the first PLMN. These methods will not be listed here.

[0283] The above S705 to S706 are the second method for the access network element to determine whether the location of the terminal is within or outside the service range allowed by the first PLMN.

[0284] In actual execution, only steps S704-S705 or only steps S705-S706 can be executed. Therefore, one of steps S704 and S706 is optional, and these two steps are indicated by dashed lines in Figure 7. Alternatively, both steps S704 and S706 can be executed, which is equivalent to performing terminal location verification twice, thus improving the reliability of terminal location verification.

[0285] S707. When the terminal is located within the service range permitted by the first PLMN, the access network element sends the cell identifier to the first mobility management network element.

[0286] When an access network element can determine the terminal's location (or whether the terminal is within the service range allowed by the first PLMN) based on the first information, or can independently determine that the terminal's location is within the service range allowed by the first PLMN, the access network element can map the terminal's location to a cell identifier. The method by which the access network element determines the cell identifier can be referred to the method described in Figure 6 above, which describes the determination of the cell identifier by the first communication device; it will not be listed here. Alternatively, when the first information indicates the terminal's location through the cell identifier, the access network element can directly obtain the cell identifier based on the first information. Then, the access network element sends the cell identifier to the first mobility management network element. The cell identifier can also be carried in the N2 interface message or the S1 interface message; there are no specific limitations on this. The content of the cell identifier can be referred to the content of the cell identifier described above; it will not be listed here. The cell identifier essentially represents the terminal's location and can be used to determine the terminal's location, as well as for paging the terminal, etc. In satellite communication systems, satellites move at high speeds; therefore, the access network element promptly sends the cell identifier to the first mobility management network element, facilitating the first mobility management network element to promptly perceive the terminal's location, register the terminal more quickly, and provide services to the terminal, etc.

[0287] S708. If the terminal's location is not within the service range permitted by the first PLMN, the access network element sends the cell identifier to the second mobility management network element. Correspondingly, the second mobility management network element receives the cell identifier from the access network element.

[0288] The method by which access network elements determine cell identifiers can be referred to the content discussed above, as can the meaning of cell identifiers, and will not be repeated here.

[0289] If the access network element can determine, based on the first information, that the terminal's location (or the terminal) is not within the service range permitted by the first PLMN, or can determine on its own that the terminal's location is not within the service range permitted by the first PLMN, then the terminal's location verification is non-compliant (or fails). Therefore, the access network element can determine the PLMN actually corresponding to the terminal's location (in this embodiment, the second PLMN is used as an example). The access network element can send a cell identifier to the second mobility management network element in the second PLMN. This cell identifier can also be carried in the N2 interface message or the S1 interface message, without limitation. The method by which the access network element determines the second mobility management network element can refer to the content of the first communication device determining the second mobility management network element discussed in Figure 6 above, and will not be listed here.

[0290] If the first piece of information is carried in the registration request or service request, optionally, the access network element can also forward the registration request or service request to the second mobility management network element, enabling the second mobility management network element to register the terminal in a timely manner or provide services to the terminal. In this case, optionally, the cell identifier can be carried in the registration request or service request.

[0291] The above S707 and S708 represent two possible scenarios. During a terminal location verification process, either step S707 or step S708 will be executed.

[0292] S709, the access network element sends second information to the terminal. Correspondingly, the terminal receives the second information from the access network element. The second information indicates that the terminal is not within the service range permitted by the first PLMN. This makes it clear to the terminal that its location verification is non-compliant.

[0293] S710, the access network element sends the sixth information to the first mobility management network element. Correspondingly, the first mobility management network element receives the sixth information from the first mobility management network element. The sixth information indicates the context information for unregistering or releasing the terminal.

[0294] If the terminal's location is outside the service range permitted by the first PLMN, the access network element can notify the first mobility management network element to unregister the terminal or release (or delete) the terminal's context information. This allows the first mobility management network element to release (or delete) the terminal's context information, effectively meaning the first mobility management network element will not provide service to that terminal. The terminal's context information refers to stored information related to the terminal, such as at least one of the terminal's session information, key information, or encryption algorithms stored by the first mobility management network element. Optionally, the sixth piece of information may include the terminal's identifier, so that the first mobility management network element can clearly identify which terminal is being unregistered.

[0295] S711, the first mobility management network element sends the seventh information to the access network element. Correspondingly, the access network element receives the seventh information from the first mobility management network element. The sixth information indicates completion of deregistration. Optionally, the seventh information includes the terminal's identifier.

[0296] After the first mobility management network element deregisters the terminal, it can also send a seventh message to the access network element to notify the terminal that deregistration is complete. Optionally, the seventh message may include the terminal's identifier so that the access network element can clearly identify which terminal has completed deregistration.

[0297] S712. The access network element sends third information to the terminal. Correspondingly, the terminal receives the third information from the access network element. The third information indicates whether the terminal enters an idle state or an inactive state.

[0298] The access network element can also notify the terminal to enter an idle state or an inactive state, so as to prevent the first PLMN from continuing to serve the terminal, or to prevent the terminal from continuing to make invalid attempts to communicate with the first mobility management network element, which would result in wasted resources.

[0299] Access network elements all execute steps S709 and S712. Access network elements may also execute one of steps S709 and S712, or neither S709 nor S712; there are no restrictions on this. In short, S709 and S712 are optional steps, which are shown as dashed lines in Figure 7.

[0300] In another possible design, the access network element sends third information to the terminal, which is equivalent to indicating that the terminal is not within the service range allowed by the first PLMN. In this case, sending the third information can be regarded as an implementation of sending the second information (in other words, S712 can be regarded as an implementation of S709). In this case, there is no need to execute the steps of S709.

[0301] S709 to S712 are steps that may be performed when the terminal is not located within the service range permitted by the first PLMN. Of course, these steps may not be performed, or some of these steps may be performed (e.g., performing S709, performing S710 and S711, performing S712, or performing S710 to S712, etc.). In short, S709 to S712 are all optional steps, which are shown as dashed lines in Figure 7.

[0302] In this embodiment, the first mobility management network element (MMI) can reroute the terminal's location to the access network element, enabling the access network element to perform terminal location verification independently, or the first MMI can perform terminal location verification independently based on the terminal's location and notify the access network element of the terminal location verification result. This provides a mechanism applicable to various terminal devices such as IoT devices for terminal location verification. Furthermore, if the terminal location verification is compliant, the access network element can map the terminal's location into a cell identifier and send it to the first MMI, allowing the first MMI to quickly register the terminal as a terminal service provider. If the terminal location verification is non-compliant, the access network element can reselect a MMI based on the terminal's actual location, or directly release the terminal's connection and / or notify the first MMI to release the terminal's connection, facilitating rapid network switching for the terminal.

[0303] The first and second communication devices differ, and the interaction processes between the various network elements involved also differ. The following is an example illustrating the interaction between the various network elements, using a schematic diagram of a communication method shown in Figure 8. Figure 8 uses the situation shown in A2 above (i.e., the first communication device is the first mobility management device, and the second communication device is the terminal) as an example. The steps shown in Figure 8 are described below.

[0304] S801. A NAS connection is established between the terminal and the first mobility management network element. The content of establishing a NAS connection is the same as that discussed in S701 above, and the repeated parts will not be listed again.

[0305] S802, the terminal sends fourth information to the access network element. Correspondingly, the access network element receives the fourth information from the terminal. The fourth information indicates the terminal's location. The content of the fourth information and the terminal's location can be referred to in Figure 7 above for the content of the fourth information and the content of the terminal's location, respectively; repetitions will not be listed again.

[0306] S803. The access network element sends first information to the first mobility management network element. Correspondingly, the first mobility management network element receives the first information from the access network element. The first information indicates the location information of the terminal.

[0307] The first information can be a NAS message. For example, the first information can be carried in a registration request or service request; the embodiments of this application do not limit the specific form of the fourth information. The content of the registration request and service request can be referred to the registration request and service request mentioned above, and repeated details will not be listed again. The first information can also indicate the identifier of the terminal. Optionally, the first information may also indicate the identifier of the PLMN currently serving the terminal (i.e., the identifier of the first PLMN), etc.

[0308] S804, the first mobility management network element determines whether the location of the terminal is within the service range permitted by the first PLMN.

[0309] The method by which the first mobility management network element determines the first PLMN, whether the terminal's location is within the service range allowed by the first PLMN, and the method for determining whether the terminal's location is within the service range allowed by the first PLMN can be referred to in Figure 7 above. Repeated descriptions will not be repeated.

[0310] S805, the first mobility management element determines the cell identifier corresponding to the terminal's location. S805 can also be equivalent to the first mobility management element specifying the cell identifier.

[0311] The content of the cell identifier and the content of the cell identifier corresponding to the location of the terminal determined by the first mobility management network element can be referred to the content of the cell identifier involved in Figure 7 above, and the content of the cell identifier corresponding to the location of the terminal determined by the access network element. The repeated parts will not be listed again.

[0312] S806. When the terminal is located within the service range permitted by the first PLMN, the first mobility management network element registers the terminal or provides services to the terminal based on the cell identifier.

[0313] If the terminal's location is within the service range permitted by the first PLMN, it indicates that the first mobility management element should provide services to the terminal. Therefore, if the first information is a registration request, the first mobility management element registers the terminal based on the cell identifier; or, if the first information is a service request, the first mobility management element provides the corresponding service to the terminal based on the cell identifier.

[0314] S807. If the terminal's location is not within the service range permitted by the first PLMN, the first mobility management network element sends a cell identifier to the second mobility management network element. Correspondingly, the second mobility management network element receives the cell identifier from the first mobility management network element.

[0315] If the terminal's location (or the terminal itself) is not within the service range permitted by the first PLMN, it indicates that the terminal location verification is non-compliant (or fails). Therefore, the first mobility management network element can determine the PLMN actually corresponding to the terminal's location (in this embodiment, the second PLMN is used as an example). The first mobility management network element can send a cell identifier to the second mobility management network element in the second PLMN. This cell identifier can also be carried in the N2 interface message or the S1 interface message, and there is no limitation on this. The method by which the first mobility management network element determines the second mobility management network element can be referred to the content of the second communication device determining the second mobility management network element discussed in Figure 6 above, and will not be listed here.

[0316] In addition to sending the cell identifier to the second mobility management network element, if the fourth information is a registration request or a service request, the first mobility management network element may optionally forward the registration request or service request to the second mobility management network element, so that the second mobility management network element can register the terminal in a timely manner or provide services to the terminal.

[0317] S806 and S807 above represent two possible scenarios. During a terminal location verification process, either step S806 or step S807 will be executed.

[0318] S808, First Mobility Management Element Deregistration Terminal. The method of deregistering the first mobility management element can be referred to the content of the first mobility management element deregistration terminal discussed in Figure 6 above, and will not be listed here.

[0319] S809, the first mobility management network element sends second information to the terminal. Correspondingly, the terminal receives the second information from the first mobility management network element. The second information indicates that the terminal is not within the service range permitted by the first PLMN.

[0320] For example, the first mobility management network element can send second information to the terminal through the access network element. The type of the second information is, for example, a NAS message. If the terminal's location is not within the service range permitted by the first PLMN, the first mobility management network element can also notify the terminal that it is not within the service range permitted by the first PLMN. This makes it clear to the terminal that its location verification is non-compliant.

[0321] S810, the first mobility management network element sends third information to the terminal. Correspondingly, the terminal receives the third information from the first mobility management network element. The third information instructs the terminal to enter an idle state or an inactive state.

[0322] For example, the first mobility management network element can send third information to the terminal through the access network element. The type of the third information is, for example, a NAS message. If the terminal's location is not within the service range allowed by the first PLMN, the first mobility management network element sends the third information to the terminal, causing the terminal not to access the first mobility management network element.

[0323] The first mobility management network element may execute steps S809 and S810. The first mobility management network element may also execute one of steps S809 and S810, or may not execute either steps S809 or S810. There is no limitation on this.

[0324] In another possible design, the first mobility management network element sends third information to the terminal, which is equivalent to indicating that the terminal is not within the service range allowed by the first PLMN. In this case, sending the third information can be regarded as an implementation of sending the second information (i.e., S810 can be regarded as an implementation of S809). In this case, there is no need to execute the steps of S809.

[0325] S808 to S810 are steps that may be executed if the terminal is located within the service range allowed by the first PLMN. Of course, these steps may not be executed, or some of these steps may be executed (e.g., executing S808, executing S809 and S810, or executing S810, or executing S808 to S810, etc.). In short, S808 to S810 are all optional steps, which are shown as dashed lines in Figure 8.

[0326] In this embodiment, the first mobility management network element can perform terminal location verification based on the terminal's location, providing a mechanism for location verification of various terminal devices. Furthermore, if the terminal location verification is compliant, the first mobility management network element can directly provide services to the terminal based on the cell identifier corresponding to the terminal's location; if the terminal location verification is non-compliant, the first mobility management network element can reselect a mobility management network element based on the terminal's actual location, or directly release the terminal's connection and / or notify the first mobility management network element to release the terminal's connection, which facilitates rapid network switching for the terminal.

[0327] It should be noted that the access network elements involved in the first communication method mentioned above (as shown in Figure 6, Figure 7 or Figure 8) may or may not be deployed on a satellite, and no specific limitation is made in this regard.

[0328] The second communication method provided in the embodiments of this application is described below.

[0329] The second communication method described above will be illustrated below with reference to a schematic diagram of a communication method shown in Figure 9. The steps shown in Figure 9 will be explained in detail below.

[0330] S901, the terminal sends the first information to the location compliance agent network element. Correspondingly, the location compliance agent network element receives the first information from the terminal. The first information is used to request registration or service from the terminal.

[0331] The terminal can directly send the first message to the location compliance agent network element. Alternatively, the terminal can send the first message to the location compliance agent network element via the access network element. The access network element is deployed on the first satellite. For example, if the terminal sends the first message to the access network element, and the access network element determines that the power supply link is disconnected, it can directly forward the first message to the location compliance agent network element. The first message can be a NAS message.

[0332] The initial information can be included in the registration request or service request. The content of the registration request and service request can be found in the previous sections, and will not be listed here again. Optionally, the initial information may include the terminal's identifier, the content of which can be found in the previous sections, and will not be listed here again.

[0333] S902. When the terminal is within the service range permitted by the first PLMN, the location compliance agent network element sends second information to the first mobility management network element. Correspondingly, the first mobility management network element receives the second information from the location compliance agent network element. The second information is used to request registration or service of the terminal. Optionally, the second information may also carry the terminal's identifier.

[0334] The location compliance agent network element can obtain information from other network elements indicating whether the terminal is within or outside the service range permitted by the first PLMN. Thus, the location compliance agent network element can clearly determine whether the terminal is within the service range permitted by the first PLMN. Alternatively, the location compliance agent network element can determine whether the terminal is within the service range permitted by the first PLMN based on the terminal's location. The method by which the location compliance agent network element determines whether the terminal is within the service range permitted by the first PLMN can be referred to the discussion in Figure 6 above regarding the second communication device determining whether the terminal is within the service range permitted by the first PLMN; repetitions will not be repeated. This involves how the location compliance agent network element obtains the terminal's location; the method for obtaining the terminal's location is described below.

[0335] D1. The location compliance agent network element obtains the terminal's second location from the first location network element. Based on this second location, the location compliance agent network element determines whether the terminal is within the service range permitted by the first PLMN.

[0336] D2. The location compliance agent network element obtains the terminal's third location from the access network element. Based on this third location, the location compliance agent network element determines whether the terminal is within the service range permitted by the first PLMN. The third location may be, for example, the terminal's GNSS location.

[0337] The second and third positions mentioned above both represent the location of the terminal, but the location comes from different network elements. The specific location indicated by the second and third positions can be the same type of location of the terminal, such as both being GNSS locations, or different types of locations, without specific limitations.

[0338] When the terminal is within the service range permitted by the first PLMN, the location-compliant agent network element can directly request the first mobility management network element to register or serve the terminal, enabling the first mobility management network element to provide compliant and timely services to the registered terminal or to the terminal.

[0339] S903. If the terminal is not within the service range permitted by the first PLMN, the location compliance agent network element sends third information to the terminal. Correspondingly, the terminal receives the third information from the location compliance agent network element. The third information indicates a refusal to register or provide service.

[0340] If the terminal is not located within the service range permitted by the first PLMN, the location compliance agent network element can directly report a refusal of registration or service to the terminal, enabling the terminal to promptly detect its location verification non-compliance. Optionally, the third information also includes a reason value, which indicates that the terminal is not located within the service range permitted by the first PLMN.

[0341] The above S902 and S903 represent two possible scenarios. During a terminal location verification process, either step S902 or step S903 will be executed.

[0342] In this embodiment, the terminal location verification can be performed directly by the location compliance agent network element deployed on the first satellite, without relying on the core network element. This allows for continued terminal location verification even in the event of a power supply link anomaly. Furthermore, after determining that the terminal location verification is compliant, the location compliance agent network element can promptly report this to the first mobility management network element, enabling the first mobility management network element to quickly register the terminal or provide registration services. Alternatively, if it determines that the terminal location verification is non-compliant, it can promptly report this to the terminal, facilitating timely execution of subsequent steps.

[0343] The interaction process between various network elements differs depending on the method used by the location compliance agent network element to obtain the terminal's location. The following example, using the communication method diagram shown in Figure 10, illustrates the interaction between the various network elements in the scenario described in D1 (i.e., the location compliance agent network element obtains the terminal's second location from the first positioning network element). The steps shown in Figure 10 are described below.

[0344] S1001, the terminal sends the twelfth information to the first mobility management network element. Correspondingly, the first mobility management network element receives the twelfth information from the terminal. The twelfth information indicates that the terminal supports store-and-forward and / or communication plans.

[0345] The term "terminal supports store-and-forward" can be replaced by describing the terminal's function (or capability) of supporting store-and-forward. It can be understood as the terminal having the ability to cooperate in implementing store-and-forward, rather than the terminal itself being capable of store-and-forward. The communication plan is used to indicate the satellites serving the terminal at different times. The communication plan includes the identifier of at least one satellite that the terminal intends to use; or, it includes one or more sets of location information and one or more sets of time information for the terminal. The one or more sets of location information indicate the terminal's location when it intends to use satellite communication, and the one or more sets of time information indicate the time corresponding to the terminal's intended use of satellite communication. Optionally, the twelfth message can be a NAS message. For example, the twelfth message can carry a registration request. The content of the registration request can be referred to the content of the registration request discussed above; repeated details will not be listed again.

[0346] In another possible implementation, the first mobility management network element may have already clearly defined that the terminal supports store-and-forward and / or the terminal's communication plan, or arbitrarily default that the terminal supports store-and-forward functionality. In this case, step S1001 may not be required, i.e., S1001 is an optional step, which is shown as a dashed line in Figure 10.

[0347] S1002, the first mobility management network element sends fourth information to the location compliance agent network element. Correspondingly, the location compliance agent network element receives the fourth information from the first mobility management network element. The fourth information is used to trigger terminal location verification; specifically, the fourth information is used to trigger the location compliance agent network element to perform terminal location verification.

[0348] For example, the first mobility management network element sends fourth information to the location compliance agent network element on the satellite currently serving the terminal (i.e., an example of the first satellite). Alternatively, the first mobility management network element sends fourth information to the location compliance agent network element on the next satellite serving the terminal (i.e., an example of the first satellite). The next satellite serving the terminal can be understood as the satellite serving the terminal during a first time period, the start time of which is, for example, the current time, or the satellite serving the terminal at the next location, which is different from the terminal's current location. Optionally, the first mobility management network element can determine the next satellite serving the terminal according to a communication plan, and thus designate that satellite as the first satellite. For example, if the current time is 13:00, and the satellite serving the terminal is satellite A, and the first mobility management network element determines, according to the communication plan, that the satellite serving the terminal at 16:00 is satellite B, then the first mobility management network element can designate satellite B as the first satellite.

[0349] For example, the fourth information may indicate the identifier of the terminal, which indicates the trigger for performing the terminal location verification. Optionally, the fourth information may also indicate the identifier of the first PLMN currently serving the terminal.

[0350] In addition to triggering terminal location verification, the fourth piece of information can optionally indicate the conditions for stopping terminal location verification. For example, the fourth piece of information may include the number of times the location compliance agent network element performs terminal location verification, the time when the verification stops, or the duration of the verification. For instance, if the fourth piece of information indicates that the location compliance agent network element performs terminal location verification twice, then the network element can proactively stop the verification after performing the two verifications. Similarly, if the fourth piece of information indicates that the verification duration is 3 hours, then the network element can proactively stop the verification 3 hours after receiving the fourth piece of information.

[0351] In one possible design, the first mobility management network element may send fourth information to the location compliance agent network element if it determines that the second condition is met. The second condition includes at least one of the following: determining that store-and-forward service is provided to the terminal, the terminal supports the store-and-forward function, or the terminal has subscribed to store-and-forward service. Optionally, the second condition may also include the first condition discussed in Figure 7 above.

[0352] For example, the first mobility management network element, based on the communication plan indicated by the twelfth information, determines that the power supply link corresponding to the terminal is malfunctioning, and thus determines that the terminal requires store-and-forward service, i.e., determines to provide store-and-forward service to the terminal. As another example, the first mobility management network element, based on the twelfth information indicating that the terminal supports store-and-forward, determines that the terminal supports the store-and-forward function. Yet another example is that the first mobility management network element can query the unified data warehouse network element to determine whether the terminal has subscribed to store-and-forward service, thereby confirming that the terminal has subscribed to store-and-forward service.

[0353] Optionally, before executing S1002 or S1001, the first mobility management network element may establish a connection with the terminal (such as a NAS connection), and / or the terminal may also establish a session, etc., without specific limitations.

[0354] In another possible implementation, the location compliance agent network element may also have the fourth information pre-stored, or the location compliance agent network element may be pre-configured or predefined to perform terminal location verification. In these cases, the location compliance agent network element does not need to perform step S1002, that is, S1002 is an optional step, which is shown as a dashed line in Figure 10.

[0355] S1003. The terminal sends first information to the access network element. Correspondingly, the access network element receives the first information from the terminal. The first information is used to request registration or service for the terminal. This access network element may also be deployed on a first satellite, which may be, for example, the satellite currently serving the terminal, or the satellite that will serve the terminal next. The content of the satellite that will serve the terminal next can be referred to in S1002 above, and will not be repeated here.

[0356] The first information is a NAS message. It can also be included in a registration request or service request. The content of the registration request and service request can be referred to in Figure 7 above; repetitions will not be repeated. Optionally, the first information can also indicate the terminal's first location. The first location can be, for example, the terminal's GNSS location.

[0357] S1004. The access network element sends the first information to the location compliance agent network element. Correspondingly, the location compliance agent network element receives the first information from the access network element. The content of the first information can be referred to as the content of the first information in S1003 above, and is not limited thereto.

[0358] The access network element can carry the first information in the N2 interface message or the S1 interface message and send it to the location compliance agent network element. The access network element can send the first information to the location compliance agent network element when it determines that the power supply link corresponding to the terminal is abnormal, or when it determines that the first condition is met. The content of the first condition can be referred to the content of the first condition discussed in Figure 6 above, and the repeated parts will not be listed again.

[0359] S1005. The access network element sends the fifth information to the location compliance agent network element. Correspondingly, the location compliance agent network element receives the fifth information from the terminal. The fifth information indicates the terminal's first location.

[0360] For example, an access network element can map the terminal's first location to a cell identifier, and the fifth information can include this cell identifier. Thus, the fifth information indicates the terminal's first location through the cell identifier. Alternatively, the fifth information can directly include the terminal's first location; there is no limitation on this.

[0361] S1006, Location Compliance Agent Network Element determines that the terminal is located in the preset area.

[0362] For example, the location compliance agent network element can determine whether the terminal is located in a preset area based on the first location. The preset area can be pre-configured or pre-defined in the location compliance agent network element. The preset area can be a national border area or a provincial border area, etc., without limitation. The location compliance agent network element can also perform terminal location verification if it determines that the terminal is located in the preset area.

[0363] In another possible implementation, the location compliance agent network element can perform terminal location verification upon receiving the fourth information. In this implementation, steps S1005 and S1006 are optional and are shown as dashed lines in Figure 10.

[0364] S1007. The location compliance agent network element sends the seventh information to the first positioning network element. Correspondingly, the first positioning network element receives the seventh information from the location compliance agent network element. The seventh information is used to request the terminal's location. The first positioning network element can also be deployed on the first satellite; the content of the first satellite can be referred to the content of the first satellite discussed in S1003 above, and will not be listed here again.

[0365] S1008, the first positioning network element sends the eighth information to the location compliance agent network element. Correspondingly, the location compliance agent network element receives the eighth information from the first positioning network element. The eighth information indicates the terminal's second location. The specific content of the terminal's second location can be referred to the previously discussed content regarding the terminal's location; it will not be listed here again.

[0366] The first positioning network element can determine the terminal's second location based on LCS positioning technology, such as multi-RTT positioning technology. For example, the first positioning network element can measure the signal transmission and reception time between the access network element and the terminal, and obtain the distance between the access network element and the terminal by obtaining the signal transmission round-trip time delay between the access network element and the terminal, thereby determining the terminal's second location. For details on LCS positioning technology, please refer to the relevant content discussed above; repeated points will not be listed here again.

[0367] S1007 to S1008 are one way for the location compliance agent network element to obtain the second location of the terminal. When the location compliance agent network element obtains the second location of the terminal in other ways, it is not necessary to execute steps S1007 to S1008. That is, steps S1007 to S1008 are optional steps, which are shown as dashed lines in Figure 10.

[0368] S1009. When the terminal is within the service range permitted by the first PLMN, the location compliance agent network element sends second information to the first mobility management network element. Correspondingly, the first mobility management network element receives the second information from the location compliance agent network element. The second information is used to request registration or service for the terminal. Thus, the location compliance agent network element effectively provides a store-and-forward service for the terminal, enabling the first mobility management network element to promptly identify the terminal requiring registration or service, thereby improving the efficiency of terminal access or service.

[0369] For example, the location compliance agent network element can determine whether the terminal is within the service range permitted by the first PLMN based on the second location. If the second location is within (or belongs to) the service range permitted by the first PLMN, it means that the terminal is within the service range permitted by the first PLMN. If the second location is not within (or does not belong to) the service range permitted by the first PLMN, it means that the terminal is not within the service range permitted by the first PLMN.

[0370] Optionally, the location compliance agent network element can also map the second location to a cell identifier and carry the cell identifier in the second information, notifying the first mobility management network element. This allows the first mobility management network element to clearly identify the terminal's second location and to promptly page the terminal, etc.

[0371] S1009 can be executed when the power supply link corresponding to the terminal is restored.

[0372] S1010. If the terminal is not within the service range permitted by the first PLMN, the location compliance agent network element sends third information to the terminal. Correspondingly, the terminal receives the third information from the location compliance agent network element. The third information indicates that registration or service is refused for the terminal.

[0373] This allows the terminal to clearly understand whether its registration or service has been denied. Optionally, the third information may also carry a reason value for denying registration or service to the terminal, such as the reason value being that the terminal is not within the service range permitted by the first PLMN.

[0374] S1009 and S1010 represent two possible scenarios. During a terminal location verification process, either step S1009 or step S1010 will be executed.

[0375] S1011, if the second location is not within the service range permitted by the first PLMN, the location compliance agent network element sends the sixth information to the access network element. Correspondingly, the access network element receives the sixth information from the location compliance agent network element. The sixth information instructs the terminal to delete its context information and enter either an inactive state or an idle state.

[0376] The sixth message can be carried in either the N2 interface message or the S1 interface message; there is no limitation on this. Optionally, the sixth message indicates that the terminal enters an inactive state or an idle state, which is equivalent to indirectly indicating that the terminal's location verification is non-compliant.

[0377] When the sixth information indicates that the terminal's context information should be deleted (or released), the access network element can directly delete the terminal's context information.

[0378] S1012. If the second location is not within the service range permitted by the first PLMN, the access network element sends a thirteenth message to the terminal. Correspondingly, the terminal receives the thirteenth message from the access network element. The thirteenth message instructs the terminal to enter an inactive state or an idle state.

[0379] If the sixth message indicates that the terminal is inactive, then the thirteenth message can indicate that the terminal is inactive. If the sixth message indicates that the terminal is idle, then the thirteenth message can indicate that the terminal is idle.

[0380] S1011 to S1012 are optional steps, which are shown as dashed lines in Figure 10.

[0381] S1013, The terminal sends eleventh information to the first mobility management network element. Correspondingly, the first mobility management network element receives the eleventh information from the terminal. The eleventh information triggers the deregistration of the terminal or the release of the session corresponding to the terminal.

[0382] When a terminal deregisters, or if the terminal determines that the store-and-forward service has ended, the terminal can send an eleventh message to the first mobility management element to request deregistration or release the corresponding session. This provides a mechanism for a terminal to proactively deregister.

[0383] S1014. The first mobility management network element sends the tenth information to the location compliance agent network element. Correspondingly, the location compliance agent network element receives the tenth information from the first mobility management network element. The tenth information triggers the cessation of terminal location verification.

[0384] After receiving the tenth information, the location compliance agent network element can release (or delete) the locally stored terminal location verification-related information and / or terminal context information. The terminal location verification-related information includes, for example, the fourth information mentioned earlier, and the terminal context information includes, for example, the terminal's second location. The tenth information can be carried in Np2 interface messages or Sp1 interface messages; there is no limitation on this. Optionally, the tenth information can carry the terminal's identifier, allowing the location compliance agent network element to clearly identify which terminal location verification needs to be stopped.

[0385] Optionally, the location compliance agent network element returns a response message to the first mobility management network element, which indicates that terminal location verification has been stopped.

[0386] S1013 to S1014 are optional steps, which are shown as dashed lines in Figure 10.

[0387] In this embodiment, in the event of a power supply link anomaly, the location compliance agent network element can directly perform terminal location verification without relying on core network elements. Furthermore, after confirming that the terminal location verification is compliant, it can promptly report to the first mobility management network element, enabling the first mobility management network element to quickly register the terminal or provide registration services for the terminal; or, if it confirms that the terminal location verification is non-compliant, it can promptly report to the terminal, facilitating the terminal's timely execution of subsequent steps. Moreover, during the terminal location verification process, the location compliance agent network element can utilize the positioning network element on the first satellite for positioning, allowing for accurate terminal location acquisition without relying on the core network. Furthermore, the first mobility management network element can flexibly instruct or cancel the location compliance agent network element from performing terminal location verification, improving the flexibility of terminal location verification.

[0388] The following section, using the communication method diagram shown in Figure 11, provides an example of the interactions between the various network elements involved in the situation described in D2 above (i.e., the location compliance agent network element obtains the second location of the terminal from the access network element). The steps shown in Figure 11 are described below.

[0389] S1101, the terminal sends the twelfth information to the first mobility management network element. Correspondingly, the first mobility management network element receives the twelfth information from the terminal. The twelfth information indicates that the terminal supports store-and-forward and / or communication plans.

[0390] The content of the terminal's store-and-forward support, the content of the communication plan, and the content of the twelfth message can be referred to in Figure 10 above, respectively. Repeated parts will not be listed again.

[0391] In another possible implementation, the first mobility management network element may have already clearly defined that the terminal supports store-and-forward and / or the terminal's communication plan, or arbitrarily default that the terminal supports store-and-forward functionality. In this case, step S1101 may not be required, i.e., S1101 is an optional step, which is shown as a dashed line in Figure 11.

[0392] S1102, the first mobility management network element sends the fourth information to the location compliance agent network element. Correspondingly, the location compliance agent network element receives the fourth information from the first mobility management network element. The fourth information is used to trigger terminal location verification.

[0393] The method by which the first mobility management network element determines the compliant agent network element at this location can be referred to the content of the first mobility management network element determining the compliant agent network element at this location discussed in Figure 9 above. The repeated parts will not be repeated.

[0394] In one possible design, the first mobility management network element can send fourth information to the location compliance agent network element if it determines that the second condition is met. The content of the second condition and the content of the first mobility management network element's determination that the second condition is met can be referred to the content of the second condition and the content of the first mobility management network element's determination that the second condition is met as described in Figure 10 above, and will not be repeated here.

[0395] Optionally, before executing S1102 or S1101, the first mobility management network element may establish a connection with the terminal (such as a NAS connection), and / or the terminal may also establish a session, etc., without specific limitations.

[0396] In another possible implementation, the location compliance agent network element may also have the fourth information pre-stored, or the location compliance agent network element may be pre-configured or predefined to perform terminal location verification. In these cases, the location compliance agent network element does not need to perform step S1002, that is, S1002 is an optional step, which is shown as a dashed line in Figure 11.

[0397] S1103, the terminal sends first information to the access network element. Correspondingly, the access network element receives the first information from the terminal. The first information is used to request registration or service for the terminal. This access network element may also be deployed on a first satellite, such as the satellite currently serving the terminal or the satellite that will serve the terminal next. The content of the satellite that will serve the terminal next can be referred to in S1002 above, and will not be repeated here.

[0398] The content of the first information can be referred to in Figure 9 above, and will not be repeated here. Optionally, the first information can also indicate the terminal's third location. The third location can be, for example, the terminal's GNSS location.

[0399] S1104. The access network element sends the first information to the location compliance agent network element. Correspondingly, the location compliance agent network element receives the first information from the access network element. The content of the first information can be referred to as the content of the first information in S1103 above, and is not limited thereto.

[0400] The access network element can carry the first information in the N2 interface message or the S1 interface message and send it to the location compliance agent network element. Alternatively, the access network element can send the first information to the location compliance agent network element when it determines that the power supply link corresponding to the terminal is abnormal, or when it determines that the first condition is met. The content of the first condition can be referred to the first condition discussed in Figure 7 above; repeated details will not be listed again.

[0401] S1105. The first mobility management network element sends key information to the location compliance agent network element. Correspondingly, the location compliance agent network element receives the key information from the first mobility management network element. The key information is the terminal's key information, which can be used to decrypt NAS messages, etc. Optionally, the first mobility management network element can also send algorithm information to the location compliance agent network element, or the location compliance agent network element can pre-configure or pre-define the algorithm information. The first mobility management network element can pre-store the key information, or obtain the key information from the unified data warehouse network element or the authentication service network element; no specific limitations are imposed on this.

[0402] S1106. The terminal sends the fifteenth information to the access network element. Correspondingly, the access network element receives the fifteenth information from the terminal. The fifteenth information indicates the terminal's third location. The content of the terminal's third location can be referred to the previous section on terminal location; it will not be listed here individually. For example, the third location is the terminal's GNSS location. The fifteenth information can be carried in the NAS message.

[0403] Optionally, the first and fifteenth pieces of information can be carried in the same message or request, such as in a registration request or service request. The content of the registration request and service request can be referred to the content of the registration request and service request discussed in Figure 6 above.

[0404] S1107. The access network element sends the ninth information to the location compliance agent network element. Correspondingly, the location compliance agent network element receives the ninth information from the access network element. The ninth information indicates the terminal's third location.

[0405] Optionally, both the ninth and first information can be carried in the same message or request, such as both in a NAS message.

[0406] Thus, the location compliance agent network element can decrypt the ninth information based on the key information to determine the terminal's third location. In other words, in this case, although the ninth information indicates the terminal's location, it does so in encrypted form, thus ensuring the security of the terminal's location. Alternatively, if the location compliance agent network element pre-stores the key, or if the ninth information does not need to be decrypted, then step S1105 is unnecessary; that is, S1105 is an optional step.

[0407] Optionally, the access network element can map the terminal's third location to a cell identifier, and the fifth information may include this cell identifier. In this way, the fifth information indicates the terminal's third location through the cell identifier. Alternatively, the fifth information may directly include the terminal's third location; this is not limited. In this case, the third location can be equivalent to the first location mentioned above.

[0408] In one possible implementation, the location compliance agent network element determines that the terminal is located in a preset area.

[0409] For example, the location compliance agent network element can determine whether the terminal is located in a preset area based on a third location. The content of the preset area can be referred to the preset area content discussed in Figure 11 above.

[0410] S1108. When the terminal is within the service range permitted by the first PLMN, the location compliance agent network element sends second information to the first mobility management network element. Correspondingly, the first mobility management network element receives the second information from the location compliance agent network element. The second information is used to request registration or service for the terminal. Thus, the location compliance agent network element effectively provides a store-and-forward service for the terminal, enabling the first mobility management network element to promptly identify the terminal requiring registration or service, thereby improving the efficiency of terminal access or service.

[0411] For example, a location compliance agent network element can determine whether a terminal is within the service range permitted by the first PLMN based on a third location. If the third location is within (or belongs to) the service range permitted by the first PLMN, it means that the terminal is within the service range permitted by the first PLMN. If the third location is not within (or does not belong to) the service range permitted by the first PLMN, it means that the terminal is not within the service range permitted by the first PLMN.

[0412] Optionally, the location compliance agent network element can also map the third location to a cell identifier, or obtain the cell identifier from the access network element and carry the cell identifier in the second information to notify the first mobility management network element. This allows the first mobility management network element to clearly identify the terminal's third location and to promptly page the terminal, etc.

[0413] S1109. If the terminal is not located within the service range permitted by the first PLMN, the location compliance agent network element sends third information to the terminal. Correspondingly, the terminal receives the third information from the location compliance agent network element. The third information indicates that registration or service is refused for the terminal.

[0414] This allows the terminal to clearly understand whether its registration or service has been denied. Optionally, the third information may also carry a reason value for denying registration or service to the terminal, such as the reason value being that the terminal is not within the service range permitted by the first PLMN.

[0415] S1108 and S1109 represent two possible scenarios: during a terminal location verification process, either step S1108 or step S1109 will be executed.

[0416] S1110. If the terminal is not within the service range permitted by the first PLMN, the location compliance agent network element sends the sixth information to the access network element. Correspondingly, the access network element receives the sixth information from the location compliance agent network element. The sixth information instructs the terminal to delete its context information and enter either an inactive state or an idle state.

[0417] The content of the sixth message can be referred to the content of the sixth message in Figure 10 above, and the repeated parts will not be listed again. When the sixth message indicates that the terminal's context information should be deleted (or released), the access network element can directly delete the terminal's context information.

[0418] S1111. If the terminal is not within the service range permitted by the first PLMN, the access network element sends a thirteenth message to the terminal. Correspondingly, the terminal receives the thirteenth message from the access network element. The thirteenth message instructs the terminal to enter an inactive state or an idle state.

[0419] If the sixth message indicates that the terminal is inactive, then the thirteenth message can indicate that the terminal is inactive. If the sixth message indicates that the terminal is idle, then the thirteenth message can indicate that the terminal is idle.

[0420] S1110 to S1111 are steps that may be performed if the second location is not within the service range allowed by the first PLMN. These steps may also not be performed, i.e., S1110 to S1111 are optional steps, which are shown in dashed lines in Figure 11.

[0421] S1112, The terminal sends eleventh information to the first mobility management network element. Correspondingly, the first mobility management network element receives the eleventh information from the terminal. The eleventh information triggers the deregistration of the terminal or the release of the session corresponding to the terminal.

[0422] When a terminal deregisters, or if the terminal determines that the store-and-forward service has ended, the terminal can send an eleventh message to the first mobility management element to request deregistration or release the corresponding session. This provides a mechanism for a terminal to proactively deregister.

[0423] S1113. The first mobility management network element sends the tenth information to the location compliance agent network element. Correspondingly, the location compliance agent network element receives the tenth information from the first mobility management network element. The tenth information triggers the cessation of terminal location verification.

[0424] After receiving the tenth information, the location compliance agent network element can release (or delete) the locally stored terminal location verification-related information and / or terminal context information. The terminal location verification-related information includes, for example, the fourth information mentioned earlier, and the terminal context information includes, for example, the terminal's second location. The tenth information can be carried in Np2 interface messages or Sp1 interface messages; there is no limitation on this. Optionally, the tenth information can carry the terminal's identifier.

[0425] Optionally, the location compliance agent network element returns a response message to the first mobility management network element, which indicates that terminal location verification has been stopped.

[0426] S1112 to S1113 are optional steps, which are shown as dashed lines in Figure 11.

[0427] In this embodiment, the location compliance agent network element can perform terminal location verification in the event of a power supply link anomaly, without relying on core network elements. Furthermore, during terminal location verification, the access network element can indicate the terminal's third location to the location compliance agent network element, enabling the location compliance agent network element to perform terminal location verification based on this third location. The location compliance agent network element can also obtain key information from the first mobility management network element to decrypt and obtain the terminal's third location, ensuring terminal information security while achieving terminal location verification. Moreover, the first mobility management network element can flexibly instruct or cancel the location compliance agent network element from performing terminal location verification, allowing either the first mobility management network element or the location compliance agent network element to flexibly perform terminal location verification, thus improving the flexibility of terminal location verification.

[0428] The third communication method provided in the embodiments of this application is described below.

[0429] The third communication method described above will be illustrated below with reference to a schematic diagram of a communication method shown in Figure 12. The steps shown in Figure 12 will be described below.

[0430] S1201, The location compliance agent network element sends the first information to the access network element. The first information indicates the location of the terminal.

[0431] The location of the terminal can be referred to the content on the location of the terminal discussed above, and the method of the first information indicating the location of the terminal can also be referred to the content on the first information indicating the location of the terminal discussed in Figure 6 above. Repeated parts will not be listed again.

[0432] In one possible implementation, the location compliance network element determines whether the terminal's location is within the service range permitted by the first PLMN. The method by which the location compliance network element determines whether the terminal's location is within the service range permitted by the first PLMN can be referenced from the method described in Figure 6 above, which describes how the second communication device determines whether the terminal's location is within the service range permitted by the first PLMN; details will not be repeated here. Furthermore, the location compliance network element also indicates, through the first information, whether the terminal is within the service range permitted by the first PLMN or not.

[0433] S1202. When the terminal is within the service range permitted by the first PLMN, the access network element sends second information to the first mobility management network element. Correspondingly, the first mobility management network element receives the second information from the access network element. The second information indicates the cell identifier.

[0434] If the first information also indicates that the terminal is within the service range permitted by the first PLMN, or that the terminal is not within the service range permitted by the first PLMN, then the access network element can determine whether the terminal is within the service range permitted by the first PLMN based on the first information. Alternatively, the access network element can also determine whether the terminal is within the service range permitted by the first PLMN based on the location of the terminal indicated by the first information. The method by which the access network element determines whether the terminal is within the service range permitted by the first PLMN can be referred to the discussion in Figure 6 above regarding the second communication device determining whether the terminal's location is within the service range permitted by the first PLMN, and will not be listed here.

[0435] The method by which access network elements determine cell identifiers, and the content of cell identifiers, can be referred to the discussion in Figure 6 above regarding the determination of cell identifiers by access network elements and the content of cell identifiers. Repeated details will not be listed again.

[0436] S1203. If the terminal is not within the service range permitted by the first PLMN, the access network element sends third information to the terminal. Correspondingly, the terminal receives the third information from the access network element. The third information indicates that registration or service of the terminal is refused. Optionally, the third information may include a reason value for refusing registration or service of the terminal, such as indicating that the terminal is not within the service range permitted by the first PLMN.

[0437] In this embodiment, the access network element performs terminal location verification, or the terminal location verification result is determined based on the location compliance agent network element deployed on the first satellite, without relying on the core network element for terminal location verification. This makes the method applicable to performing terminal location verification when the power supply link is abnormal.

[0438] The interaction between the various network elements involved in Figure 12 will be illustrated below with reference to the schematic diagram shown in Figure 13. The steps shown in Figure 13 will be described below.

[0439] S1301, the terminal sends the ninth information to the first mobility management network element. Correspondingly, the first mobility management network element receives the ninth information from the terminal. The ninth information indicates that the terminal supports store-and-forward and / or a communication plan. The content of the terminal's support for store-and-forward, the content of the communication plan, and the content of the ninth information can be referred to in Figure 9 above, respectively, as discussed regarding the terminal's support for store-and-forward, the content of the communication plan, and the content of the twelfth information; repetitions will not be listed again.

[0440] S1302, the unified data warehouse network element sends the tenth information to the first mobility management network element. Correspondingly, the first mobility management network element receives the tenth information from the unified data warehouse network element. The tenth information indicates that the terminal has subscribed to store-and-forward services.

[0441] Steps S1301 and S1302 may be performed, either one of them, both of them, or neither of them may be performed; there is no limitation on this. Steps S1301 and S1302 are optional steps, and are shown as dashed lines in Figure 13.

[0442] S1303, The terminal sends fourth information to the access network element. Correspondingly, the access network element receives the fourth information from the terminal. The fourth information indicates the terminal's location. The terminal's location can be its GNSS location.

[0443] The fourth piece of information can be included in the NAS message, for example. In addition to carrying the location of the terminal, the fourth piece of information can also request the registration or service of the terminal; in other words, the fourth piece of information can be included in the registration request or service request.

[0444] S1304. The access network element sends the fifth information to the location compliance agent network element. Correspondingly, the location compliance agent network element receives the fifth information from the access network element. The fifth information indicates the location of the terminal. Optionally, the access network element carries the fifth information in the N2 interface message or the S1 interface message.

[0445] S1303 to S1305 are one way for the location-compliant agent network element to obtain the location of the terminal. In fact, there is no restriction on the way the location-compliant agent network element obtains the location of the terminal. That is, S1303 to S1305 are optional steps, which are shown by dashed lines in Figure 13.

[0446] S1305. The first mobility management network element sends key information to the location compliance agent network element. Correspondingly, the location compliance agent network element receives the key information from the first mobility management network element.

[0447] The method by which the first mobility management network element obtains key information can be referred to the key information acquisition method in Figure 10 above, and the repetition will not be repeated. The content of the key information can be referred to the key information discussed in Figure 10 above, and the repetition will not be listed again. Optionally, the first mobility management network element can also send algorithm information to the location compliance agent network element. The content of the algorithm information can be referred to the algorithm information discussed above, and the repetition will not be listed again.

[0448] For example, after receiving the fifth information, the location compliance agent network element can decrypt the fifth information based on the key information to obtain the location of the terminal.

[0449] Optionally, in addition to sending key information to the location compliance agent network element, the first mobility management network element can also instruct the location compliance agent network element to perform terminal location verification. This enables the location compliance agent network element to drive the execution of terminal location verification.

[0450] In another possible design, the location compliance agent network element has pre-stored key information, or the fifth information does not need to be decrypted, so the step S1305 does not need to be executed.

[0451] S1306. The location compliance agent network element sends the first information to the access network element. Correspondingly, the access network element receives the first information from the location compliance agent network element. The first information indicates the location of the terminal.

[0452] The above S1305 and S1306 can be used as an independent embodiment to provide a mechanism for an access network element to obtain the location of a terminal.

[0453] S1307, Location Compliance Agent Network Element determines whether the terminal is within the service range permitted by the first PLMN.

[0454] The method by which the location compliance agent network element determines whether a terminal is within the service range permitted by the first PLMN is similar to the method described in Figure 6 above, which explains how the second communication device determines whether a terminal is within the service range permitted by the first PLMN; it will not be repeated here. If the terminal's location is within the service range permitted by the first PLMN, the location compliance agent network element determines that the terminal is within the service range permitted by the first PLMN. If the terminal's location is not within the service range permitted by the first PLMN, the location compliance agent network element determines that the terminal is not within the service range permitted by the first PLMN.

[0455] S1308, the location compliance agent network element sends the sixth information to the access network element. Correspondingly, the access network element receives the sixth information from the location compliance agent network element. The sixth information indicates whether the terminal is within or outside the service range permitted by the first PLMN; specifically, the sixth information indicates whether the terminal is within or outside the service range permitted by the first PLMN.

[0456] S1309. The access network element determines whether the terminal is within the service range permitted by the first PLMN.

[0457] For example, the access network element can determine whether the terminal is within the service range permitted by the first PLMN based on the location of the terminal indicated by the first information. The method by which the access network element determines whether the terminal is within the service range permitted by the first PLMN can be found in the description of the location compliance agent network element determining whether the terminal is within the service range permitted by the first PLMN in S1306; details that are repeated will not be listed here again.

[0458] S1308 and S1309 described above represent a second method for the access network element to determine whether the terminal's location is within or outside the service range permitted by the first PLMN. In actual execution, only steps S1307 and S1308, or only step S1309, may be executed. Therefore, one of steps S1307 and S1309 can be optional, as illustrated by dashed lines in Figure 13. Alternatively, if the first information indicates that the terminal's location (or the terminal itself) is within or outside the service range permitted by the first PLMN, step S1309 can also be executed. This is equivalent to performing terminal location verification twice, improving the reliability of the verification.

[0459] S1310. If the terminal is within the service range permitted by the first PLMN, the access network element sends second information to the first mobility management network element. Correspondingly, the first mobility management network element receives the second information from the access network element. The second information indicates the cell identifier.

[0460] The access network element can determine the cell identifier corresponding to the terminal's location based on the terminal's location indicated by the first information. The method by which the access network element determines the cell identifier, and the content of the cell identifier, can be referred to the descriptions of the access network element determining the cell identifier and the content of the cell identifier in Figure 6 above. Repeated descriptions will not be repeated.

[0461] S1311. If the terminal is not within the service range permitted by the first PLMN, the access network element sends third information to the terminal. Correspondingly, the terminal receives the third information from the access network element. The third information indicates that registration or service is refused.

[0462] S1310 and S1311 represent two possible scenarios. During a terminal location verification process, either step S1310 or step S1311 will be executed.

[0463] S1312. If the terminal is not within the service range permitted by the first PLMN, the access network element sends a seventh message to the terminal. Correspondingly, the terminal receives the seventh message from the access network element. The seventh message indicates that the terminal is not within the service range permitted by the first PLMN.

[0464] S1313. If the terminal is not within the service range permitted by the first PLMN, the access network element sends the eighth information to the terminal. Correspondingly, the terminal receives the eighth information from the access network element. The eighth information indicates that the terminal enters an inactive state or an idle state.

[0465] For example, the eighth piece of information may include the identifier of the terminal, which indicates that the terminal has entered an inactive or idle state.

[0466] In one possible design, the access network element can also determine the cell identifier corresponding to the terminal's location, determine the second mobility management network element corresponding to the terminal's location, and send the cell identifier to the second mobility management network element. The determination of the cell identifier and the determination of the second mobility management network element are described in Figure 7 above and will not be repeated here.

[0467] S1312 to S1313 are optional steps, which are shown as dashed lines in Figure 13.

[0468] In this embodiment, the location compliance agent network element can perform terminal location verification in the event of a power supply link anomaly, without relying on the core network element. Alternatively, the location compliance agent network element can obtain the terminal's location and indicate it to the access network element, enabling the access network element to perform terminal location verification. Furthermore, the location compliance agent network element can obtain key information from the first mobility management network element to decrypt and obtain the terminal's third location, ensuring the terminal's information security while achieving terminal location verification.

[0469] It is understood that, in order to achieve the functions in the above embodiments, the base station and terminal include hardware structures and / or software modules corresponding to perform each function. Those skilled in the art should readily recognize that, based on the units and method steps described in conjunction with the embodiments disclosed in this application, this application can be implemented in hardware or a combination of hardware and computer software. Whether a function is executed in hardware or by computer software driving hardware depends on the specific application scenario and design constraints of the technical solution.

[0470] This application provides a communication device. Please refer to Figure 14, which is a schematic diagram of the communication device. This communication device can be used to implement the functions of the access network element, the first mobility management network element, the location compliance agent network element, or the terminal in the above method embodiments, and thus can also achieve the beneficial effects of the above method embodiments. In the embodiments of this application, the communication device may be the RAN involved in Figure 1, the RAN involved in Figure 2, the access network element involved in Figure 5, the first mobility management network element involved in Figure 5, the terminal involved in any of Figures 1 to 4 or Figure 5, the LRP involved in Figure 5, etc., or it may be a software module or hardware module (such as a chip) applied in the terminal, the access network element, the first mobility management network element, or the location compliance agent network element.

[0471] As shown in Figure 14, the communication device 1400 includes a transceiver module 1410 and a processing module 1420. The communication device 1400 can be used to implement the functions of any of the access network elements, first mobility management network elements, location compliance agent network elements, or terminals involved in Figures 6 to 13.

[0472] In the first embodiment, the communication device 1400 can be used to implement the functions of the first communication device involved in FIG6 above.

[0473] For example, the transceiver module 1410 is used to receive first information. The transceiver module 1410 is also used to send a cell identifier to a first mobility management network element or to a second mobility management network element.

[0474] Optionally, the communication device 1400 can also be used to implement the remaining steps performed by the first communication device in Figure 6 above, which will not be listed one by one here.

[0475] In one possible implementation, the communication device 1400 can be used to implement the functions of the access network element involved in Figure 7 above.

[0476] For example, the transceiver module 1410 is used to receive first information. The transceiver module 1410 is also used to send a cell identifier to a first mobility management network element or to a second mobility management network element.

[0477] Optionally, the communication device 1400 can also perform the remaining steps executed by the access network element involved in Figure 7, which will not be listed here one by one.

[0478] In another possible implementation, the communication device 1400 can be used to implement the functions of the first mobility management network element involved in FIG8 above.

[0479] For example, the transceiver module 1410 is used to receive first information and send cell identifiers to the second mobility management network element.

[0480] Optionally, the communication device 1400 may also implement the remaining steps performed by the first mobility management network element involved in FIG8, which will not be listed one by one here.

[0481] In the second embodiment, the communication device 1400 can be used to implement the functions of the second communication device involved in FIG6 above.

[0482] For example, transceiver module 1410 is used to send first information to the first communication device.

[0483] Optionally, the communication device 1400 may also perform the remaining steps executed by the second communication device involved in FIG6, which will not be listed here one by one.

[0484] In one possible implementation, the communication device 1400 can be used to implement the functions of the first mobility management network element involved in FIG7 above.

[0485] For example, the transceiver module 1410 is used to send first information to the access network element. Optionally, the transceiver module 1410 can also be used to receive a cell identifier from the access network element.

[0486] Optionally, the communication device 1400 may also implement the remaining steps performed by the first mobility management network element involved in FIG7, which will not be listed one by one here.

[0487] In another possible implementation, the communication device 1400 can be used to implement the functions of the access network element involved in Figure 8 above.

[0488] For example, the transceiver module 1410 is used to send first information to the first mobility management network element.

[0489] Optionally, the communication device 1400 can also perform the remaining steps executed by the access network element involved in Figure 8, which will not be listed here one by one.

[0490] In the third embodiment, the communication device 1400 can be used to implement the functions of the location compliance agent network element involved in Figure 9 above.

[0491] For example, the transceiver module 1410 is used to receive first information and send second or third information, etc.

[0492] Optionally, the communication device 1400 can also perform the remaining steps executed by the location compliance agent network element involved in Figure 9, which will not be listed here.

[0493] In one possible implementation, the communication device 1400 can be used to implement the functions of the location compliance agent network element involved in Figure 10 above.

[0494] For example, the transceiver module 1410 is used to receive first information and send second or third information, etc.

[0495] Optionally, the communication device 1400 can also perform the remaining steps executed by the location compliance agent network element involved in Figure 10, which will not be listed here.

[0496] In another possible implementation, the communication device 1400 can be used to implement the functions of the location compliance agent network element involved in Figure 11 above.

[0497] For example, the transceiver module 1410 is used to receive first information and send second or third information, etc.

[0498] Optionally, the communication device 1400 may also perform the remaining steps executed by the location compliance agent network element involved in Figure 11, which will not be listed here.

[0499] In the fourth embodiment, the communication device 1400 can be used to implement the functions of the first mobility management network element involved in Figure 9 above.

[0500] For example, the transceiver module 1410 is used to receive second information, etc.

[0501] Optionally, the communication device 1400 may also perform the remaining steps executed by the first mobility management network element involved in FIG9, which will not be listed here one by one.

[0502] In one possible implementation, the communication device 1400 can be used to implement the functions of the first mobility management network element involved in FIG10 above.

[0503] For example, the transceiver module 1410 is used to receive the second information. Optionally, the first mobility management network element sends the fourth information, etc.

[0504] Optionally, the communication device 1400 may also perform the remaining steps executed by the first mobility management network element involved in FIG10, which will not be listed here one by one.

[0505] In another possible implementation, the communication device 1400 can be used to implement the functions of the first mobility management network element involved in FIG11 above.

[0506] For example, the transceiver module 1410 is used to receive the second information. Optionally, the first mobility management network element sends the fourth information or key information, etc.

[0507] Optionally, the communication device 1400 may also perform the remaining steps executed by the first mobility management network element involved in FIG11, which will not be listed here one by one.

[0508] In the fifth embodiment, the communication device 1400 can be used to implement the functions of the access network element involved in Figure 12 above.

[0509] For example, the transceiver module 1410 is used to receive first information and send second or third information, etc.

[0510] Optionally, the communication device 1400 may also perform the remaining steps executed by the access network element involved in Figure 12, which will not be listed here.

[0511] In one possible implementation, the communication device 1400 can realize the functions of the access network element involved in Figure 13 above.

[0512] For example, the transceiver module 1410 is used to receive first information and send second or third information, etc.

[0513] Optionally, the communication device 1400 may also perform the remaining steps executed by the access network element involved in Figure 13, which will not be listed here.

[0514] In the sixth embodiment, the communication device 1400 can be used to implement the functions of the first mobility management network element involved in FIG13 above.

[0515] For example, the transceiver module 1410 is used to send key information and receive second information, etc., under the control of the processing module 1420.

[0516] Optionally, the communication device 1400 may also perform the remaining steps executed by the first mobility management network element involved in FIG13, which will not be listed here.

[0517] In the seventh embodiment, the communication device 1400 can be used to implement the functions of the first mobility management network element involved in FIG13 above.

[0518] For example, the transceiver module 1410 is used to send key information and receive second information, etc., under the control of the processing module 1420.

[0519] Optionally, the communication device 1400 may also perform the remaining steps executed by the first mobility management network element involved in FIG11, which will not be listed here one by one.

[0520] In the eighth embodiment, the communication device 1400 can be used to implement the functions of the location compliance agent network element involved in Figure 13 above.

[0521] For example, the transceiver module 1410 is used to receive key information, and the processing module 1420 is used to decrypt the fifth information to obtain the location of the terminal. The transceiver module 1410 is also used to send the first information to the access network element.

[0522] Optionally, the communication device 1400 may also perform the remaining steps executed by the location compliance agent network element involved in Figure 13, which will not be listed here.

[0523] In the ninth embodiment, the communication device 1400 can be used to implement the functions of the terminal described in FIG13 above.

[0524] For example, the transceiver module 1410 is used to send the ninth message and receive the third message, etc., under the control of the processing module 1420.

[0525] Optionally, the communication device 1400 may also perform the remaining steps executed by the terminal involved in FIG13, which will not be listed here.

[0526] A more detailed description of the transceiver module 1410 and the processing module 1420 can be obtained directly from the relevant descriptions in any of the method embodiments shown in Figures 6 to 13, and will not be repeated here.

[0527] This application provides a communication device. Please refer to Figure 15, which is a schematic diagram of the communication device. As shown in Figure 15, the communication device 1500 includes a processor 1510 and an interface circuit 1520. The processor 1510 and the interface circuit 1520 are coupled to each other. It is understood that the interface circuit 1520 can be a transceiver or an input / output interface. Optionally, the communication device 1500 may further include a memory 1530 for storing instructions executed by the processor 1510, or storing input data required by the processor 1510 to execute instructions, or storing data generated after the processor 1510 executes instructions.

[0528] When the communication device 1500 is used to implement any of the methods shown in Figures 6 to 13, the processor 1510 is used to implement the functions of the processing module 1420, and the interface circuit 1520 is used to implement the functions of the transceiver module 1410.

[0529] When the aforementioned communication device is a chip applied to a terminal, the terminal chip implements the functions of the terminal in the above method embodiments. The terminal chip receives information from other modules (such as radio frequency modules or antennas) in the terminal, which is information sent to the terminal by the base station; or, the terminal chip sends information to other modules (such as radio frequency modules or antennas) in the terminal, which is information sent to the base station by the terminal.

[0530] When the aforementioned communication device is a module applied to a network element (such as an access network element, a location compliance agent network element, or a mobility management network element), the network element module implements the functions of the network element in the above method embodiments. The network element module receives information from other modules (such as radio frequency modules or antennas) within the network element; this information is sent by the terminal to the network element. Alternatively, the network element module sends information to other modules (such as radio frequency modules or antennas) within the network element; this information is sent by the network element to the terminal. Here, the access network element module can be the baseband chip of the access network element, or it can be a DU or other modules. The DU here can be a DU under an open radio access network (O-RAN) architecture.

[0531] This application provides another example of a communication device, which includes at least one processor and at least one memory coupled together. The at least one processor and the at least one memory are used to store instructions. When the instructions are executed by the at least one processor, the communication device performs the methods described in the above embodiments. Taking a communication device including a processor and a memory as an example, as shown in FIG16, the communication device 1600 includes a processor 1610 and a memory 1620. The processor 1610 and the memory 1620 are coupled together. The memory 1620 stores instructions. When the instructions stored in the memory 1620 are executed by the processor 1610, the communication device 1600 performs any of the methods in FIG6 to FIG13.

[0532] It is understood that the processors involved in the various embodiments of this application can be central processing units (CPUs), or other general-purpose processors, digital signal processors (DSPs), application-specific integrated circuits (ASICs), field-programmable gate arrays (FPGAs), or other programmable logic devices, transistor logic devices, hardware components, or any combination thereof. General-purpose processors can be microprocessors or any conventional processor. Furthermore, the memory involved in the various embodiments of this application can include volatile memory, such as random access memory (RAM). Memory can also include non-volatile memory, such as read-only memory (ROM), flash memory, hard disk drives (HDDs), or solid-state drives (SSDs).

[0533] This application provides a communication system that can be used to perform the method described in any of Figures 6 to 13 above.

[0534] For example, if the communication system is used to implement the method described in Figure 6 above, then the communication system includes a first communication device and a second communication device. Optionally, the communication system also includes at least one of a terminal and / or a second mobility management network element. The contents of the first communication device, the second communication device, the first mobility management network element, and the second mobility management network element are as discussed in Figure 6 above, and will not be listed here again.

[0535] For example, if the communication system is used to implement the method described in Figure 7 above, then the communication system includes an access network element. Optionally, the communication system also includes at least one of a terminal, a first mobility management network element, or a second mobility management network element. The contents of the access network element, the terminal, the first mobility management network element, and the second mobility management network element are as discussed in Figure 7 above and will not be listed here again.

[0536] Alternatively, if the communication system is used to implement the method described in Figure 8 above, then the communication system includes a first mobility management network element. Optionally, the communication system also includes at least one of a terminal, an access network element, a location compliance agent network element, or a second mobility management network element. The contents of the access network element, the terminal, the first mobility management network element, the location compliance agent network element, and the second mobility management network element are as discussed in Figure 8 above and will not be listed here again.

[0537] Alternatively, if the communication system is used to implement the methods described in Figures 9, 10, or 11 above, then the communication system includes a location compliance agent network element. Optionally, the communication system also includes at least one of a terminal, a first mobility management network element, an access network element, or a second mobility management network element. The contents of the access network element, terminal, first mobility management network element, location compliance agent network element, and second mobility management network element can be referred to the content discussed in Figures 9, 10, or 11 above, and will not be listed here again.

[0538] Alternatively, if the communication system is used to implement the method described in Figures 12 or 13 above, then the communication system includes an access network element. Optionally, the communication system also includes at least one of a terminal, a first mobility management network element, a location compliance agent network element, or a second mobility management network element. The contents of the access network element, the terminal, the first mobility management network element, the location compliance agent network element, and the second mobility management network element can be referred to the content discussed in Figures 12 or 13 above, and will not be listed here.

[0539] This application provides a chip system comprising a processor and an interface. The processor is configured to call and execute instructions from the interface, and when the processor executes the instructions, it implements the method described in any one of Figures 6 to 13 above.

[0540] This application provides a computer-readable storage medium for storing computer programs or instructions that, when run, implement the method described in any one of Figures 6 to 13 above.

[0541] This application provides a computer program product containing instructions that, when run on a computer, implements the method described in any one of Figures 6 to 13 above.

[0542] The method steps in the various embodiments of this application can be implemented in hardware or in software instructions executable by a processor. The software instructions can consist of corresponding software modules, which can be stored in random access memory, flash memory, read-only memory, programmable read-only memory, erasable programmable read-only memory, electrically erasable programmable read-only memory, registers, hard disks, portable hard disks, CD-ROMs, or any other form of storage medium known in the art. An exemplary storage medium is coupled to a processor, enabling the processor to read information from and write information to the storage medium. The storage medium can also be a component of the processor. The processor and storage medium can reside in an ASIC. Alternatively, the ASIC can reside in a base station or terminal. The processor and storage medium can also exist as discrete components in a base station or terminal.

[0543] In the above embodiments, implementation can be achieved entirely or partially through software, hardware, firmware, or any combination thereof. When implemented using software, it can be implemented entirely or partially in the form of a computer program product. The computer program product includes one or more computer programs or instructions. When the computer program or instructions are loaded and executed on a computer, the processes or functions described in the embodiments of this application are performed entirely or partially. The computer can be a general-purpose computer, a special-purpose computer, a computer network, a network device, a user equipment, or other programmable device. The computer program or instructions can be stored in a computer-readable storage medium or transferred from one computer-readable storage medium to another. For example, the computer program or instructions can be transferred from one website, computer, server, or data center to another website, computer, server, or data center via wired or wireless means. The computer-readable storage medium can be any available medium that a computer can access or a data storage device such as a server or data center that integrates one or more available media. The available medium can be a magnetic medium, such as a floppy disk, hard disk, or magnetic tape; it can also be an optical medium, such as a digital video optical disc; or it can be a semiconductor medium, such as a solid-state drive. The computer-readable storage medium may be a volatile or non-volatile storage medium, or may include both types of storage media.

[0544] In the various embodiments of this application, unless otherwise specified or in case of logical conflict, the terminology and / or descriptions of different embodiments are consistent and can be referenced by each other. The technical features of different embodiments can be combined to form new embodiments according to their inherent logical relationship.

[0545] It is understood that the various numerical designations used in the embodiments of this application are merely for descriptive convenience and are not intended to limit the scope of the embodiments of this application. The order of the process numbers described above does not imply the order of execution; the execution order of each process should be determined by its function and internal logic.

Claims

1. A communication method, characterized in that, Applied to a first communication device, the method includes: Receive first information from a second communication device, the first information indicating the location of the terminal, wherein the first communication device is a first mobility management network element and the second communication device is the terminal, or the first communication device is an access network element and the second communication device is the first mobility management network element; If the terminal's location is within the service range permitted by the first public terrestrial mobile network, then the cell identifier corresponding to the location is sent to the first mobility management device; or, If the location of the terminal is not within the service range permitted by the first public land mobile network, the cell identifier corresponding to the location is sent to the second mobility management device, which belongs to the second public land mobile network and the location of the terminal is within the service range permitted by the second public land mobile network. The first public land mobile network currently serves the terminal.

2. The method according to claim 1, characterized in that, The method further includes: Determine whether the location of the terminal is within the service range permitted by the first public terrestrial mobile network.

3. The method according to claim 1 or 2, characterized in that, The first information also indicates: The terminal's location is not within the service area permitted by the first public terrestrial mobile network; or... The terminal is located within the service area permitted by the first public terrestrial mobile network.

4. The method according to any one of claims 1-3, characterized in that, When the first communication device is a first mobility management network element and the second communication device is the terminal, the first information is carried in a non-access stratum message; or... When the first communication device is an access network element and the second communication device is a mobility management network element, the first information is carried in the N2 interface message or the S1 interface message.

5. The method according to any one of claims 1-4, characterized in that, The method further includes: A second message is sent to the terminal, indicating that the terminal is not within the service range permitted by the first public terrestrial mobile network.

6. The method according to any one of claims 1-5, characterized in that, The method further includes: If the terminal is not within the service range of the first public terrestrial mobile network, a third message is sent to the terminal, the third message indicating one of the following: The terminal enters an idle state; or, The terminal enters an inactive state.

7. The method according to any one of claims 1-6, characterized in that, The location of the terminal is its Global Navigation Satellite System (GNSS) location.

8. A communication method, characterized in that, Applied to a first mobility management network element, the method includes: Receive fourth information from the terminal, the fourth information indicating the location of the terminal; Send first information to the access network element, the first information indicating the location of the terminal.

9. The method according to claim 8, characterized in that, The method further includes at least one of the following: The terminal is determined to be of type 1; The terminal is identified as using satellite access. It is determined that the access network element supports the terminal location verification; or, The access network elements are deployed on the first satellite.

10. The method according to claim 7 or 8, characterized in that, The location of the terminal is its Global Navigation Satellite System (GNSS) location.

11. A communication method, characterized in that, The method, applied to a location compliance agent network element deployed on a first satellite, includes: Receive first information from the terminal, the first information being used to request registration or service of the terminal; If the terminal is within the service range permitted by the first public land mobile network, then based on the first information, a second information is sent to the first mobility management element, wherein the second information requests registration or service for the terminal, and the first mobility management element belongs to the first public land mobile network and is currently serving the terminal; or... If the terminal is not within the service range permitted by the first public terrestrial mobile network, a third message is sent to the terminal, wherein the third message is used to indicate rejection of the registration or the service; The first public land mobile network currently serves the terminal.

12. The method according to claim 11, characterized in that, The method further includes: The system receives fourth information from a first mobility management network element, which triggers the location compliance agent network element to perform terminal location verification. The first mobility management network element belongs to the first public land mobile network and is currently serving the terminal.

13. The method according to claim 12, characterized in that, The fourth piece of information includes the identifier of the terminal; or, The fourth piece of information includes the identifier of the terminal and the identifier of the first public land mobile network.

14. The method according to any one of claims 11-13, characterized in that, The first satellite is the terminal's currently serving satellite; or, The first satellite is the satellite that will provide services to the terminal in the next instance.

15. The method according to any one of claims 11-14, characterized in that, The method further includes: The terminal receives fifth information from an access network element, the fifth information indicating the first position of the terminal. Based on the fifth piece of information, it is determined that the terminal is located in a preset area.

16. The method according to any one of claims 11-15, characterized in that, The method further includes: Send a sixth message to the access network element, wherein the sixth message further indicates one of the following: Delete the context information of the terminal; The terminal enters an inactive state; or... The terminal enters an idle state.

17. The method according to any one of claims 11-16, characterized in that, The method further includes: Send a seventh message to the first positioning network element, the seventh message being used to request the location of the terminal, the first positioning network element being deployed on the first satellite; The terminal receives eighth information from the first positioning network element, the eighth information indicating the second location of the terminal; Based on the second location, it is determined whether the terminal is within the service range permitted by the first public terrestrial mobile network.

18. The method according to any one of claims 11-16, characterized in that, The method further includes: Receive ninth information from an access network element, the ninth information indicating the third location of the terminal; Based on the third location, it is determined whether the terminal is within the service range permitted by the first public terrestrial mobile network.

19. The method according to claim 18, characterized in that, The method further includes: Receive key information from the first mobility management network element; Based on the key information, the ninth information is decrypted to obtain the third location of the terminal.

20. The method according to claim 18 or 19, characterized in that, The method further includes: When the terminal is within the service range permitted by the first public terrestrial mobile network, the cell identifier corresponding to the third location is sent to the first mobility management network element.

21. The method according to any one of claims 18-20, characterized in that, The third location is the GNSS location of the terminal.

22. The method according to any one of claims 11-21, characterized in that, The method further includes: Receive the tenth message, which is used to trigger the cessation of the terminal location verification; Based on the tenth piece of information, the terminal location verification is stopped.

23. A communication method, characterized in that, Applied to a first mobility management network element, the method includes: It is determined that a store-and-forward service is provided to the terminal, wherein the terminal supports the store-and-forward function, or the terminal has subscribed to the store-and-forward service; A fourth message is sent to the location compliance agent network element, which triggers the location compliance agent network element to perform terminal location verification. The location compliance agent network element is deployed on the first satellite.

24. The method according to claim 23, characterized in that, The method further includes: The terminal receives a second message from the location compliance agent network element, the second message requesting registration or service of the terminal.

25. The method according to claim 23 or 24, characterized in that, The method further includes: Receive the eleventh message from the terminal, the eleventh message triggering the unregistration of the terminal or the release of the session corresponding to the terminal; Based on the eleventh information, the tenth information is sent to the location compliance agent network element, and the tenth information is used to trigger the cessation of the terminal location verification.

26. The method according to any one of claims 23-25, characterized in that, The first satellite is the terminal's currently serving satellite; or, The first satellite is the satellite that will provide services to the terminal in the next instance.

27. The method according to any one of claims 23-26, characterized in that, The method further includes: Send the terminal's key information to the location-compliant agent network element.

28. A communication method, characterized in that, Applied to an access network element deployed on a first satellite, the method includes: The sixth information is received from the location compliance agent network element, wherein the sixth information indicates one of the following: the terminal's context information is deleted, the terminal enters an inactive state, or the terminal enters an idle state, and the location compliance agent network element is deployed on the first satellite; Based on the sixth piece of information, delete the context information of the terminal, instruct the terminal to enter an inactive state, or instruct the terminal to enter an idle state.

29. The method according to claim 28, characterized in that, The method further includes: Receive first information from the terminal, the first information being used to request registration or service of the terminal; The first information is sent to the location-compliant agent network element.

30. The method according to claim 28 or 29, characterized in that, The method further includes: A ninth message is sent to the location compliance agent network element, the ninth message indicating the third location of the terminal.

31. A communication method, characterized in that, Applied to an access network element deployed on a first satellite, the method includes: The terminal receives first information from a location compliance agent network element, the first information indicating the location of the terminal, and the location compliance agent network elements are all deployed on the first satellite. If the terminal is within the service range of the first public terrestrial mobile network, then based on the first information, second information is sent to the first mobility management device, wherein the second information indicates a cell identifier, the first mobility management device belongs to the first public terrestrial mobile network, and is currently serving the terminal; or... If the terminal is not within the service range of the first public terrestrial mobile network, a third message is sent to the terminal, wherein the third message is used to indicate that the terminal's registration or service is rejected; The first public land mobile network currently serves the terminal.

32. The method according to claim 31, characterized in that, The method further includes: Receive fourth information from the terminal, the fourth information carrying the location of the terminal; Based on the fourth information, a fifth information is sent to the location compliance agent network element, the fifth information indicating the location of the terminal.

33. The method according to claim 31 or 32, characterized in that, The method further includes: Determine whether the location of the terminal is within the service area of ​​the first public terrestrial mobile network; or, The terminal receives a sixth piece of information from the location compliance agent network element, the sixth piece of information indicating whether the terminal's location is within the service area of ​​the first public terrestrial mobile network or not within the service area of ​​the first public terrestrial mobile network.

34. The method according to any one of claims 31-33, characterized in that, The method further includes: A seventh message is sent to the terminal, indicating that the terminal is not within the service range permitted by the first public terrestrial mobile network.

35. The method according to any one of claims 31-34, characterized in that, The method further includes: The terminal is sent an eighth message, which indicates one of the following: The terminal enters an inactive state; or... The terminal enters an idle state.

36. The method according to any one of claims 31-35, characterized in that, The first satellite is the terminal's currently serving satellite; or, The first satellite is the satellite that will provide services to the terminal in the next instance.

37. The method according to any one of claims 31-36, characterized in that, The location of the terminal is its Global Navigation Satellite System (GNSS) location.

38. A communication method, characterized in that, The method, applied to a location compliance agent network element deployed on a first satellite, includes: The system receives fifth information from an access network element, the fifth information carrying the location of the terminal, the access network element being deployed on the first satellite; Receive key information from the terminal from the first mobility management network element; Based on the key information, the fifth piece of information is decrypted to obtain the location of the terminal; Send first information to the access network element, wherein the first information indicates the location of the terminal.

39. The method according to claim 38, characterized in that, The first satellite is the terminal's currently serving satellite; or, The first satellite is the satellite that will provide services to the terminal in the next instance.

40. The method according to claim 38 or 39, characterized in that, The fifth piece of information is carried in the non-access stratum message.

41. The method according to any one of claims 38-40, characterized in that, The location of the terminal is its Global Navigation Satellite System (GNSS) location.

42. A communication method, characterized in that, Applied to a first mobility management network element, the method includes: Obtain the terminal's key information; The terminal's key information is sent to the location compliance agent network element, which is deployed on the first satellite.

43. The method according to claim 42, characterized in that, The first satellite is the terminal's currently serving satellite; or, The first satellite is the satellite that will provide services to the terminal in the next instance.

44. The method according to claim 42 or 43, characterized in that, The method further includes: The system determines to provide store-and-forward service to the terminal and receives a ninth message from the terminal, the ninth message indicating that the terminal supports the store-and-forward function; or, The terminal receives a tenth message from the unified data management function, the tenth message indicating that the terminal has subscribed to the store-and-forward service.

45. The method according to any one of claims 42-44, characterized in that, The method further includes: The eleventh message is sent to the location compliance agent network element, and the eleventh message is used to trigger the location compliance agent network element to perform the terminal location verification.

46. ​​A communication method, characterized in that, Applied to a terminal, the method includes: Send a ninth message to the first mobility management network element, the ninth message indicating that the terminal supports store-and-forward functionality; The fourth information, which carries the location of the terminal, is sent to the access network element.

47. The method according to claim 46, characterized in that, The method further includes: The system receives third information from the access network element, wherein the third information is used to indicate that the registration or service of the terminal is rejected.

48. The method according to claim 46 or 47, characterized in that, The method further includes: The terminal receives a seventh message from the access network element, the seventh message indicating that the terminal is not within the service range permitted by the first public terrestrial mobile network.

49. The method according to any one of claims 46-48, characterized in that, The method further includes: The terminal receives an eighth message from the access network element, the eighth message indicating one of the following: the terminal enters an inactive state; or the terminal enters an idle state.

50. A communication device, characterized in that, include: A module for performing the method as described in any one of claims 1-7; or, A module for performing the method as described in any one of claims 8-10; or, A module for performing the method as described in any one of claims 11-22; or, A module for performing the method as described in any one of claims 23-27; or, A module for performing the method as described in any one of claims 28-30; or, A module for performing the method as described in any one of claims 31-37; or, A module for performing the method as described in any one of claims 38-41; or, A module for performing the method as described in any one of claims 42-45; or, A module for performing the method as described in any one of claims 46-49.

51. A communication device, characterized in that, The device includes a processor and an interface circuit. The interface circuit is used to receive signals from other communication devices besides the communication device and transmit them to the processor, or to send signals from the processor to other communication devices besides the communication device. The processor is used through logic circuits or execution code instructions to implement the method as described in any one of claims 1-7, any one of claims 8-10, any one of claims 11-22, any one of claims 23-27, any one of claims 28-30, any one of claims 31-37, any one of claims 38-41, any one of claims 42-45, or any one of claims 46-49.

52. A computer program product containing instructions, characterized in that, When the instruction is executed by the communication device, the communication device performs the method as described in any one of claims 1-7, any one of claims 8-10, any one of claims 11-22, any one of claims 23-27, any one of claims 28-30, any one of claims 31-37, any one of claims 38-41, any one of claims 42-45, or any one of claims 46-49.

53. A computer-readable storage medium, characterized in that, The storage medium stores a computer program or instructions that, when executed by a communication device, implement the method as described in any one of claims 1-7, any one of claims 8-10, any one of claims 11-22, any one of claims 23-27, any one of claims 28-30, any one of claims 31-37, any one of claims 38-41, any one of claims 42-45, or any one of claims 46-49.

Images