Method and apparatus for implementing mobility restrictions

Abstract

This disclosure provides a method and apparatus for implementing mobility restrictions, applicable to the field of communication technology. The method, executed by a terminal device, includes: receiving a mapping relationship between a Geographic Area Description (GAD) and a Tracking Area (TA) sent by a core network device; and determining the target TA where the terminal device is located based on the mapping relationship and the terminal device's current Global Navigation Satellite System (GNSS) information. This allows the target TA of the terminal device to be determined, enabling the terminal device and the core network device to implement mobility restrictions on the terminal device based on the target TA.

Description

Technical Field

[0001] This disclosure relates to the field of communication technology, and in particular to a method and apparatus for implementing mobility restrictions. Background Technology

[0002] In related technologies, when a terminal device uses satellite access, the basis for determining whether to restrict communication for the terminal device is as follows: if all TAs (tracking areas) broadcast to the terminal device are located within the prohibited access area, the terminal device is prohibited from accessing the network at its current location; if at least one is not located within the prohibited access area, the terminal device is allowed to access the network at its current location. Similarly, if all TAs broadcast to the terminal device are located within the non-allowed area, the terminal device is prohibited from communicating with the network at its current location; if at least one is not located within the non-allowed area, the terminal device is allowed to communicate with the network at its current location. However, the broadcast TAs may include TAs corresponding to the terminal device's currently registered network RPLMN (registered public land mobile network) and TAs corresponding to other eRPLMNs (equivalent registered public land mobile networks). If all broadcast TAs belonging to the RPLMN are located within the non-allowed area, according to the rules, the terminal device is prohibited from communicating with the RPLMN at its current location. However, if at least one broadcast TA belonging to another eRPLMN is located within the allowed area, according to the rules, the UE is allowed to communicate with the eRPLMN at its current location. According to the rules for mobility restrictions defined in the relevant technologies, situations like the one described above can occur where mobility restrictions fail.

[0003] Therefore, how to solve the problem of mobility restrictions failing due to existing rules is an urgent issue that needs to be addressed. Summary of the Invention

[0004] This disclosure provides a mobility restriction implementation method and apparatus, which can determine the target TA (Traffic Area) of a terminal device, so that the terminal device and the core network device can implement mobility restrictions on the terminal device based on the target TA.

[0005] In a first aspect, embodiments of this disclosure provide a mobility restriction implementation method, which is executed by a terminal device. The method includes: obtaining a mapping relationship between a geographic area description (GAD) and a tracking area (TA); and determining the target TA where the terminal device is located based on the mapping relationship and the current Global Navigation Satellite System (GNSS) information of the terminal device.

[0006] In this technical solution, the terminal device receives the mapping relationship between the geographical area description (GAD) and the tracking area (TA) sent by the core network device. Based on the mapping relationship and the terminal device's current Global Navigation Satellite System (GNSS) information, the target TA where the terminal device is located is determined. This allows the target TA of the terminal device to be determined, enabling the terminal device and the core network device to implement mobility restrictions on the terminal device based on the target TA.

[0007] Secondly, embodiments of this disclosure provide another method for implementing mobility restrictions, which is executed by a core network device. The method includes: obtaining a mapping relationship between a geographic region description (GAD) and a tracking area (TA); and sending the mapping relationship between the GAD and the TA to a terminal device, wherein the mapping relationship is used by the terminal device to determine the target TA it is in.

[0008] Thirdly, this disclosure provides another method for implementing mobility restrictions, which is executed by a core network device. The method includes: determining the target TA where the terminal device is located, wherein the target TA is obtained from the access network device used by the terminal device to access the network, or the target TA is determined based on the mapping relationship between the geographical region description GAD and the tracking area TA, and the current GNSS information of the terminal device.

[0009] Fourthly, embodiments of this disclosure provide a communication device that implements some or all of the functions of the terminal device described in the first aspect above. For example, the communication device may have the functions of some or all of the embodiments in this disclosure, or it may have the functions of any one embodiment in this disclosure implemented individually. The functions may be implemented by hardware or by hardware executing corresponding software. The hardware or software includes one or more units or modules corresponding to the above functions.

[0010] In one implementation, the communication device may include a transceiver module and a processing module, the processing module being configured to support the communication device in performing the corresponding functions described in the above method. The transceiver module supports communication between the communication device and other devices. The communication device may also include a storage module, coupled to the transceiver module and the processing module, which stores necessary computer programs and data for the communication device.

[0011] In one implementation, the communication device includes: a transceiver module configured to acquire the mapping relationship between the geographic area description (GAD) and the tracking area (TA); and a processing module configured to determine the target TA where the terminal device is located based on the mapping relationship and the current GNSS information of the terminal device.

[0012] Fifthly, embodiments of this disclosure provide another communication device that implements some or all of the functions of the core network device in the method example described in the second aspect above. For example, the communication device may have the functions of some or all of the embodiments in this disclosure, or it may have the functions of any one embodiment in this disclosure implemented individually. The functions may be implemented by hardware or by hardware executing corresponding software. The hardware or software includes one or more units or modules corresponding to the above functions.

[0013] In one implementation, the communication device may include a transceiver module and a processing module, the processing module being configured to support the communication device in performing the corresponding functions described in the above method. The transceiver module is used to support communication between the communication device and other devices. The communication device may also include a storage module, which is coupled to the transceiver module and the processing module, and stores the necessary computer programs and data of the communication device.

[0014] In one implementation, the communication device includes: a processing module configured to acquire a mapping relationship between a geographic region description (GAD) and a tracking area (TA); and a transceiver module configured to send the mapping relationship between the geographic region description (GAD) and the tracking area (TA) to a terminal device, wherein the mapping relationship is used by the terminal device to determine its target TA.

[0015] In one implementation, the communication device includes a processing module configured to determine the target TA of the terminal device, wherein the target TA is obtained from the access network device used by the terminal device to access the network, or the target TA is determined based on the mapping relationship between the geographical region description GAD and the tracking area TA, and the current GNSS information of the terminal device.

[0016] In a sixth aspect, embodiments of this disclosure provide a communication device including a processor that, when the processor invokes a computer program in memory, executes the method described in the first aspect.

[0017] In a seventh aspect, embodiments of this disclosure provide a communication device including a processor that, when the processor invokes a computer program in memory, executes the method described in the second or third aspect above.

[0018] Eighthly, embodiments of this disclosure provide a communication device including a processor and a memory, the memory storing a computer program; the processor executes the computer program stored in the memory to cause the communication device to perform the method described in the first aspect above.

[0019] Ninthly, embodiments of this disclosure provide a communication device including a processor and a memory, the memory storing a computer program; the processor executes the computer program stored in the memory to cause the communication device to perform the methods described in the second or third aspect above.

[0020] In a tenth aspect, embodiments of this disclosure provide a communication device including a processor and an interface circuit. The interface circuit is configured to receive code instructions and transmit them to the processor, which is configured to execute the code instructions to cause the device to perform the method described in the first aspect above.

[0021] Eleventhly, embodiments of this disclosure provide a communication device including a processor and an interface circuit. The interface circuit is used to receive code instructions and transmit them to the processor, which is used to execute the code instructions to cause the device to perform the methods described in the second or third aspect above.

[0022] In a twelfth aspect, embodiments of this disclosure provide a system for determining a tracking area (TA), the system comprising the communication device described in the fourth aspect and the communication device described in the fifth aspect, or the system comprising the communication device described in the sixth aspect and the communication device described in the seventh aspect, or the system comprising the communication device described in the eighth aspect and the communication device described in the ninth aspect, or the system comprising the communication device described in the tenth aspect and the communication device described in the eleventh aspect.

[0023] In a thirteenth aspect, embodiments of the present invention provide a computer-readable storage medium for storing instructions for use by the aforementioned terminal device, which, when executed, cause the terminal device to perform the method described in the first aspect.

[0024] In a fourteenth aspect, embodiments of the present invention provide a readable storage medium for storing instructions for use by the core network device described above, which, when executed, cause the core network device to perform the methods described in the second or third aspect above.

[0025] In a fifteenth aspect, this disclosure also provides a computer program product including a computer program that, when run on a computer, causes the computer to perform the method described in the first aspect above.

[0026] In a sixteenth aspect, this disclosure also provides a computer program product including a computer program that, when run on a computer, causes the computer to perform the methods described in the second or third aspect above.

[0027] In a seventeenth aspect, this disclosure provides a chip system including at least one processor and an interface for supporting a terminal device in implementing the functions involved in the first aspect, such as determining or processing at least one of the data and information involved in the above methods. In one possible design, the chip system further includes a memory for storing computer programs and data necessary for the terminal device. The chip system may be composed of chips or may include chips and other discrete devices.

[0028] In an eighteenth aspect, this disclosure provides a chip system including at least one processor and an interface for supporting core network equipment in implementing the functions involved in the second or third aspect, such as determining or processing at least one of the data and information involved in the above methods. In one possible design, the chip system further includes a memory for storing computer programs and data necessary for the core network equipment. The chip system may be composed of chips or may include chips and other discrete devices.

[0029] In a nineteenth aspect, this disclosure provides a computer program that, when run on a computer, causes the computer to perform the method described in the first aspect above.

[0030] In a twentieth aspect, this disclosure provides a computer program that, when run on a computer, causes the computer to perform the methods described in the second or third aspect above. Attached Figure Description

[0031] To more clearly illustrate the technical solutions in the embodiments or background art of this disclosure, the accompanying drawings used in the embodiments or background art of this disclosure will be described below.

[0032] Figure 1 This is an architecture diagram of a communication system provided in an embodiment of this disclosure;

[0033] Figure 2 This is a flowchart of a mobility restriction implementation method provided in an embodiment of this disclosure;

[0034] Figure 3 This is a flowchart illustrating how a core network device sends a mapping relationship between GAD and TA to a terminal device during the initial registration process, as provided in this embodiment of the disclosure.

[0035] Figure 4 This is a flowchart of a mobility management method provided in an embodiment of this disclosure;

[0036] Figure 5 This is a flowchart of another mobility management method provided in this embodiment of the disclosure;

[0037] Figure 6This is a flowchart of another mobility restriction implementation method provided in this disclosure embodiment;

[0038] Figure 7 This is a flowchart of yet another mobility restriction implementation method provided in this disclosure embodiment;

[0039] Figure 8 This is a flowchart of yet another mobility management method provided in this disclosure embodiment;

[0040] Figure 9 This is a flowchart of yet another mobility management method provided in this disclosure embodiment;

[0041] Figure 10 This is a flowchart of yet another mobility management method provided in this disclosure embodiment;

[0042] Figure 11 This is a structural diagram of a communication device provided in an embodiment of this disclosure;

[0043] Figure 12 This is a structural diagram of another communication device provided in an embodiment of this disclosure;

[0044] Figure 13 This is a schematic diagram of the structure of a chip provided in an embodiment of this disclosure. Detailed Implementation

[0045] To better understand the mobility restriction implementation method and apparatus disclosed in this disclosure, the communication system to which this disclosure applies will be described first.

[0046] Exemplary embodiments will now be described in detail, examples of which are illustrated in the accompanying drawings. Unless otherwise indicated, the same numerals in different drawings denote the same or similar elements in the following description relating to the drawings. The embodiments described in the following exemplary embodiments do not represent all embodiments consistent with this disclosure. Rather, they are merely examples of apparatuses and methods consistent with some aspects of this disclosure as detailed in the appended claims.

[0047] The terminology used in this disclosure is for the purpose of describing particular embodiments only and is not intended to be limiting of the disclosure. The singular forms “a,” “the,” and “the” as used in this disclosure and the appended claims are also intended to include the plural forms unless the context clearly indicates otherwise. It should also be understood that the term “and / or” as used herein refers to and includes any and all possible combinations of one or more of the associated listed items.

[0048] It should be understood that although the terms first, second, third, etc., may be used in this disclosure to describe various information, such information should not be limited to these terms. These terms are used only to distinguish information of the same type from one another. For example, without departing from the scope of this disclosure, first information may also be referred to as second information, and similarly, second information may also be referred to as first information. Depending on the context, for example, the word "if" as used herein may be interpreted as "when," "when," or "in response to determination."

[0049] It should be noted that the information (including but not limited to user device information, user personal information, etc.), data (including but not limited to data used for analysis, data stored, data displayed, etc.) and signals involved in this disclosure are all authorized by the user or fully authorized by all parties, and the collection, use and processing of related data must comply with the relevant laws, regulations and standards of the relevant countries and regions.

[0050] To better understand the mobility restriction implementation method and apparatus disclosed in this disclosure, the communication system to which this disclosure applies will be described first.

[0051] like Figure 1 As shown, this disclosure provides a communication system including: core network equipment (e.g., 5th generation core (5GC) 11, evolved packet core (EPC) 12), access network equipment (e.g., evolved node B (gNB) 13, evolved node B (eNB) 14), and terminal equipment 15.

[0052] Core network equipment 11 refers to equipment in the core network (CN) that provides service support for terminal equipment. Currently, some core network equipment includes: access and mobility management function (AMF) entities, session management function (SMF) entities, user plane function (UPF) entities, etc., which are not listed here. Among them, the AMF entity is responsible for access management and mobility management of terminal equipment. The SMF entity is responsible for session management, such as user session establishment. The UPF entity can be a user plane functional entity, mainly responsible for connecting to external networks. It should be noted that in this disclosure, entities can also be referred to as network elements or functional entities. For example, an AMF entity can also be called an AMF network element or an AMF functional entity, and an SMF entity can also be called an SMF network element or an SMF functional entity, etc.

[0053] Access network equipment 13 refers to a radio access network (RAN) node (or device) that connects terminal devices to a wireless network; it can also be called a base station. Examples of RAN nodes currently include: gNB, eNB, transmission reception point (TRP), radio network controller (RNC), Node B (NB), base station controller (BSC), base transceiver station (BTS), home base station (e.g., home evolved Node B, or home node B, HNB), base band unit (BBU), or wireless fidelity (Wi-Fi) access point (AP), etc. Furthermore, in a network architecture, access network equipment may include a centralized unit (CU), a distributed unit (DU), or RAN equipment including both CU and DU. This includes RAN devices for CU and DU that separate the protocol layer from a logical function perspective. Some protocol layer functions are centrally controlled by the CU, while the remaining part or all of the protocol layer functions are distributed in the DU, which is centrally controlled by the CU.

[0054] Terminal equipment 15, also known as user equipment (UE), mobile station (MS), mobile terminal (MT), etc., refers to devices that provide voice and / or data connectivity to users. Examples include handheld devices with wireless connectivity and in-vehicle devices. Currently, some examples of terminal equipment include: mobile phones, tablets, laptops, PDAs, mobile internet devices (MID), wearable devices, virtual reality (VR) devices, augmented reality (AR) devices, wireless terminals in industrial control, wireless terminals in self-driving, wireless terminals in remote medical surgery, wireless terminals in smart grids, wireless terminals in transportation safety, wireless terminals in smart cities, and wireless terminals in smart homes.

[0055] In this communication system, both access network device 13 and access network device 14 can communicate with multiple terminal devices 15. However, it should be understood that the terminal devices communicating with access network device 13 and the terminal devices communicating with access network device 14 can be the same or different. Figure 2 The terminal device 15 shown can communicate with both access network device 13 and access network device 14 simultaneously, but this only shows one possible scenario. In some scenarios, the terminal device may only communicate with access network device 13 or access network device 14, and this disclosure does not limit this.

[0056] It should be understood that Figure 1 This is a simplified diagram for ease of understanding only. The communication system may also include other access network devices, terminal devices, or core network devices. Figure 1 It was not drawn in the middle.

[0057] It is understood that the communication system described in the embodiments of this disclosure is for the purpose of more clearly illustrating the technical solutions of the embodiments of this disclosure, and does not constitute a limitation on the technical solutions provided in the embodiments of this disclosure. As those skilled in the art will know, with the evolution of system architecture and the emergence of new business scenarios, the technical solutions provided in the embodiments of this disclosure are also applicable to similar technical problems.

[0058] In addition, the following points are provided to facilitate understanding of the embodiments disclosed herein.

[0059] First, in this embodiment of the disclosure, "for indicating" can include both direct and indirect indication. When describing information as indicating A, it can include whether the information directly indicates A or indirectly indicates A, but does not necessarily mean that the information carries A.

[0060] The information indicated by the information is called the information to be indicated. In the specific implementation process, there are many ways to indicate the information to be indicated, such as, but not limited to, directly indicating the information to be indicated, such as the information to be indicated itself or its index. It can also be indirectly indicated by indicating other information, where there is a relationship between the other information and the information to be indicated. It can also indicate only a part of the information to be indicated, while the other parts are known or pre-agreed upon. For example, the indication of specific information can be achieved by using a pre-agreed (e.g., protocol-defined) arrangement of various pieces of information, thereby reducing the indication overhead to some extent.

[0061] The information to be instructed can be sent as a whole or divided into multiple sub-information messages, and the sending period and / or timing of these sub-information messages can be the same or different. This disclosure does not limit the specific sending method. The sending period and / or timing of these sub-information messages can be predefined, for example, according to a protocol.

[0062] Second, in this disclosure, the terms "first," "second," and various numerical designations (e.g., "#1," "#2") are merely distinctions for ease of description and are not intended to limit the scope of the embodiments of this disclosure. For example, they are used to distinguish different TAs, etc.

[0063] Third, in this disclosure, the terminal equipment has GNSS (Global Navigation Satellite System) capability.

[0064] Fourth, the “protocol” involved in the embodiments of this disclosure may refer to standard protocols in the field of communication, such as LTE protocol, NR protocol, WLAN protocol and related protocols in other communication systems, and this disclosure does not limit it.

[0065] Fifth, this disclosure provides multiple implementation methods to clearly illustrate the technical solutions of this disclosure. Of course, those skilled in the art will understand that the multiple embodiments provided in this disclosure can be executed individually, or in combination with the methods of other embodiments in this disclosure, or individually or in combination with some methods in other related technologies; this disclosure does not limit these aspects.

[0066] To address the issue that existing mobility restriction rules may cause mobility restrictions to fail in related technologies, this disclosure provides a mobility restriction implementation method and apparatus. A terminal device receives a mapping relationship between a GAD (Geographical Area Description) and a TA (Target Area) sent by a core network device. Based on this mapping relationship and the terminal device's current GNSS information, the target TA where the terminal device is located can be determined. This allows the terminal device and the core network device to implement mobility restrictions on the terminal device based on the target TA.

[0067] The following description, in conjunction with the accompanying drawings, details a method and apparatus for implementing mobility restrictions provided in this disclosure.

[0068] Please see Figure 2 , Figure 2 This is a flowchart of a mobility restriction implementation method provided in an embodiment of this disclosure.

[0069] like Figure 2 As shown, the method may include, but is not limited to, the following steps:

[0070] S21: Core network equipment obtains the mapping relationship between GAD and TA.

[0071] In this embodiment of the disclosure, the core network device may be, for example, an AMF (access and mobility management function) that obtains the mapping relationship between GAD and TA.

[0072] The mapping relationship between GAD and TA obtained by the core network can be configured by itself, or it can be obtained based on the protocol agreement, or it can be obtained based on the configuration of the access network equipment, etc. This disclosure does not impose specific limitations on this.

[0073] The mapping relationship between GAD and TA can include the mapping relationship between GAD and TA of all contracted PLMN (public land mobile network).

[0074] In some possible implementations, when the core network device obtains the mapping relationship between GAD and TA, it can obtain the current GNSS information of the terminal device, such as the current location information of the terminal device, so as to determine the corresponding target GAD based on the GNSS information of the terminal device. Furthermore, it can determine the target TA where the terminal device is located based on the target GAD and the mapping relationship, or determine the target TA where the terminal device is located based on the TA representing the location of the terminal device reported by the access network device and the mapping relationship.

[0075] Understandably, when the core network device obtains the mapping relationship between GAD and TA, it can send the mapping relationship between GAD and TA to the terminal device, and the core network device executes S22.

[0076] S22: The core network equipment sends the mapping relationship between GAD and TA to the terminal equipment.

[0077] In this embodiment of the disclosure, the core network device can send the mapping relationship between GAD and TA to the terminal device after obtaining the mapping relationship between GAD and TA.

[0078] The core network equipment can send the mapping relationship between GAD and TA to the terminal equipment at any stage of the terminal equipment's access to the network. For example, it can send the mapping relationship between GAD and TA to the terminal equipment during the initial registration process, registration update process, UCU (UE Configuration Update) process, service request process, etc., and this disclosure does not impose any restrictions on this.

[0079] For example, such as Figure 3 As shown, core network devices can send the mapping relationship between GAD and TA to terminal devices during the initial registration process. Specifically, the interaction process is as follows:

[0080] 0. The terminal device obtains its current location (GNSS information) and, based on the prohibited access area information in the stored mobility restriction information, determines the PLMN that the terminal device can access at its current location.

[0081] 1. The terminal device sends a registration request to the core network equipment (AMF). For example, the terminal device can send a registration request to the core network equipment through the base station (NR (LEO)).

[0082] 2. The AMF processes registration requests from terminal devices, registering them for access and defining their Registration Area (RA) and mobility restriction information. Mobility restriction information may include forbidden area information and service area restriction information (non-allowed or allowed area). The forbidden area, non-allowed area, and allowed area can each be composed of a set of Tracking Area Identity (TAI).

[0083] 3 and 4, AMF obtains the mapping relationship between GAD and TA belonging to PLMN from the network management center (NMC).

[0084] 5. The AMF sends a registration response to the terminal device, distributing the registration area, mobility restriction information [forbidden area, non-allowed area, or allowed area], and the mapping relationship between GAD and TA to the terminal device.

[0085] 6. Based on the received information, the terminal device updates the already stored mobility restriction information [forbidden area, non-allowed area, or allowed area] and saves the mapping relationship between GAD and TA.

[0086] Through the above process, the terminal obtains the mapping relationship between GAD and TA.

[0087] It should be noted that the above examples are for illustrative purposes only. In this embodiment of the disclosure, the core network device may also send the mapping relationship between GAD and TA to the terminal device through the registration update process, or the UCU process, or the service request process, etc. This embodiment of the disclosure does not impose specific limitations on this.

[0088] In this embodiment of the disclosure, the terminal device can acquire and save the mapping relationship between GAD and TA. When the terminal device receives information including new mapping relationships, it can update the saved mapping relationships. When the terminal device is powered off, the saved mapping relationship between GAD and TA will not be deleted. When the terminal device deletes the USIM (Universal Subscriber Identity Module), the saved mapping relationship between GAD and TA is also deleted.

[0089] It is understandable that, upon receiving the mapping relationship between GAD and TA sent by the core network equipment, the terminal device can further execute S23.

[0090] S23: The terminal device determines the target TA where it is located based on the mapping relationship and the current GNSS information of the terminal device.

[0091] In this embodiment of the disclosure, the terminal device can determine the target TA where the terminal device is located based on the mapping relationship and the current GNSS information of the terminal device.

[0092] In some embodiments, the terminal device determines the corresponding target GAD based on the current GNSS information of the terminal device; and determines the target TA where the terminal device is located based on the target GAD and the mapping relationship.

[0093] In this embodiment of the present disclosure, the terminal device can determine the target GAD corresponding to the current GNSS information based on the current GNSS information of the terminal device, and then determine the target TA where the terminal device is located based on the target GAD and the mapping relationship.

[0094] By implementing the embodiments of this disclosure, the terminal device receives the mapping relationship between GAD and TA sent by the core network device; based on the mapping relationship and the current GNSS information of the terminal device, the target TA where the terminal device is located is determined. Thus, the target TA where the terminal device is located can be determined, enabling the terminal device and the core network device to implement mobility restrictions on the terminal device based on the target TA.

[0095] Please see Figure 4 , Figure 4 This is a flowchart of a mobility management method provided in an embodiment of this disclosure.

[0096] like Figure 4 As shown, this method is executed by a terminal device, and the method may include, but is not limited to, the following steps:

[0097] S41: The terminal device determines whether to access the PLMN based on the first target TA and the prohibited access domain information, wherein the target TA is the first target TA corresponding to the PLMN.

[0098] In this embodiment of the disclosure, the method by which the terminal device determines the target TA where the terminal device is located can be found in the relevant description in the above embodiments, and will not be repeated here.

[0099] Here, target TA is the first target TA corresponding to PLMN.

[0100] It should be noted that the method by which the terminal device determines the first target TA corresponding to the PLMN where the terminal device is located in this embodiment is the same as the method by which the terminal device determines the target TA where the terminal device is located in the above embodiments. Please refer to the relevant descriptions in the above embodiments; they will not be repeated here. Of course, it should be understood that the terminal device can also determine its TA using other methods.

[0101] In this embodiment of the disclosure, the terminal device can determine whether to access the PLMN based on the first target TA and the prohibited access domain information.

[0102] In some embodiments, the terminal device determines whether to access the PLMN based on the first target TA and the prohibited access domain information, including:

[0103] In response to the first target TA being included in the prohibited access domain of the PLMN, it is determined that access to the PLMN by the first target TA is prohibited; or

[0104] In response to the fact that the first target TA is not included in the prohibited access domain of the PLMN, it is determined that access to the PLMN is permitted by the first target TA, wherein the prohibited access domain information is used to indicate the prohibited access domain of the PLMN.

[0105] In this embodiment of the disclosure, the forbidden access domain information is used to indicate the forbidden access domain of the PLMN.

[0106] In this embodiment of the present disclosure, the terminal device can determine whether to access the PLMN based on the first target TA and the prohibited access domain information. In the case that the first target TA is included in the prohibited access domain of the PLMN, it is determined that access to the PLMN is prohibited at the first target TA.

[0107] In this embodiment of the present disclosure, the terminal device can determine whether to access the PLMN based on the first target TA and the prohibited access domain information. In the case that the first target TA is not included in the prohibited access domain of the PLMN, it is determined that access to the PLMN is allowed by the first target TA.

[0108] Understandably, if the terminal device determines that access to the PLMN is allowed in the first target TA, the terminal device can choose to access the PLMN in the first target TA, or it can choose not to access the PLMN in the first target TA.

[0109] It should be noted that in the embodiments of this disclosure, S41 can be implemented alone or in combination with any other step in the embodiments of this disclosure, such as in combination with S21 to S23 in the embodiments of this disclosure. The embodiments of this disclosure do not limit this.

[0110] By implementing the embodiments of this disclosure, the terminal device determines whether to access the PLMN based on the first target TA and the prohibited access domain information, wherein the target TA is the first target TA corresponding to the PLMN. Therefore, based on determining the target TA where the terminal device is located, accurate control of the prohibited access domain information can be ensured, avoiding the failure of the prohibited access domain information restrictions.

[0111] Please see Figure 5 , Figure 5 This is a flowchart of another mobility management method provided in this embodiment of the disclosure.

[0112] like Figure 5 As shown, this method is executed by a terminal device, and the method may include, but is not limited to, the following steps:

[0113] S51: The terminal device determines whether to communicate with the registered public land mobile network RPLMN based on the second target TA and the service domain restriction information, wherein the target TA is the second target TA corresponding to the RPLMN.

[0114] In this embodiment of the disclosure, the method by which the terminal device determines the target TA where the terminal device is located can be found in the relevant description in the above embodiments, and will not be repeated here.

[0115] Among them, the target TA is the second target TA corresponding to the RPLMN (registered PLMN).

[0116] It should be noted that the method by which the terminal device determines the second target TA corresponding to the RPLMN where the terminal device is located in this embodiment is the same as the method by which the terminal device determines the target TA where the terminal device is located in the above embodiments. Please refer to the relevant description in the above embodiments, and it will not be repeated here.

[0117] In this embodiment of the disclosure, the terminal device can determine whether to communicate with a registered public land mobile network (RPLMN) based on the second target TA and the service domain restriction information.

[0118] In some embodiments, the terminal device determines whether to communicate with the RPLMN based on the second target TA and service domain restriction information, including:

[0119] In response to the second target TA being included in the non-allowed area of ​​RPLMN, it is determined that communication between the second target TA and RPLMN is prohibited, wherein the service domain restriction information is used to indicate the non-allowed area of ​​RPLMN; or

[0120] In response to the second target TA being included in the non-allowed zone of an RPLLMN, it is determined that communication between the second target TA and any eRPLMN is prohibited, wherein service domain restriction information is used to indicate the non-allowed zone of the RPLLMN; or

[0121] In response to the fact that the second target TA is included in the allowed area of ​​RPLMN, it is determined that communication between the second target TA and RPLMN is permitted, wherein service domain restriction information is used to indicate the allowed area of ​​RPLMN.

[0122] In this embodiment of the disclosure, service domain restriction information is used to indicate the non-allowed area of ​​RPLMN or to indicate the allowed area of ​​RPLMN.

[0123] In this embodiment of the present disclosure, the terminal device can determine whether to communicate with RPLMN based on the second target TA and the service domain restriction, wherein if the second target TA is included in the non-allowed area of ​​RPLMN, it is determined that communication with RPLMN is prohibited on the second target TA.

[0124] In this embodiment of the disclosure, the terminal device can determine whether to communicate with an RPLMN based on a second target TA and service domain restrictions. If the second target TA is included in the non-permitted area of ​​the RPLMN, it is determined that communication between the second target TA and any eRPLMN (equivalent registered PLMN) is prohibited.

[0125] In this embodiment of the present disclosure, the terminal device can determine whether to communicate with the RPLMN based on the second target TA and the service domain restrictions, wherein if the second target TA is included in the allowed area of ​​the RPLMN, it is determined that communication with the RPLMN is allowed on the second target TA.

[0126] Among them, if the terminal device determines that communication between the second target TA and RPLMN is permitted, it may initiate a communication request to communicate with RPLMN, or it may choose not to initiate a communication request to communicate with RPLMN.

[0127] It is understandable that service area restriction information may include permitted or prohibited areas (e.g., specified using a tracking area identifier).

[0128] The permitted area is the zone in which the terminal device is allowed to initiate communication with the network.

[0129] The non-permitted area is where terminal devices are subject to service restrictions. Terminal devices are not permitted to initiate service requests to the network, or any connection requests for user plane data or control plane data.

[0130] Allowed and prohibited regions can be specified using tracking region identifiers. For example, an allowed region can contain one or more (e.g., up to 16) tracking areas, or all tracking areas can be placed in the allowed region.

[0131] The core network equipment (AMF) can assign service area restriction information to terminal devices based on their subscriptions and can update it as needed. This information can be provided to terminal devices through a registration program or a UCU program. When provided to terminal devices, it can only contain either permitted or unpermitted areas, not both simultaneously.

[0132] If a terminal device uses satellite access, and the access network device broadcasts multiple TAIs to the terminal device, during the terminal device's network access process, the access network device reports the broadcast multiple TAIs to the core network device. The core network device will then execute the following service area restriction rules:

[0133] If all the broadcast TAIs are contained within the non-allowed area, then both the terminal device and the AMF consider the terminal device to be located within the non-allowed area.

[0134] If at least one of the TAIs broadcast is not contained in the non-allowed area, then both the terminal device and the AMF consider the terminal device to be in the allowed area.

[0135] In related technologies, for situations where a satellite access network is shared by multiple networks (e.g., PLMN-A and PLMN-B share the same satellite access),

[0136] The satellite access network broadcasts multiple TAIs of available PLMNs to the terminal device. During the registration process of the terminal device accessing the network, the satellite access device reports the broadcast multiple TAIs to the core network. The core network assigns a registration area to it. In addition to the registered PLMN (RPLMN), the registration area also contains at least one equivalent registered PLMN (eRPLMN). That is, the registration area contains a list of TAIs from the RPLMN and the equivalent RPLMN.

[0137] At the same time, the core network also allocates an allowed area for terminal devices, which also includes the TAI of RPLLMN and the TAI of eRPLMN.

[0138] Subsequently, due to the movement of the terminal device, the following situation may occur:

[0139] 1. All broadcast TAIs belonging to RPLMN in the received broadcast TAIs are not within the allowed area. However,

[0140] 2. Within the permitted area, there must be at least one broadcast TAI belonging to an eRPLMN.

[0141] In this scenario, based on the current solution: According to option 1, the terminal device at the current location is not allowed to communicate with the network, while according to option 2, the terminal device at the current location can communicate using eRPLMN. In this case, imposing service area restrictions on the terminal device at the current location is ineffective.

[0142] Based on this, in this embodiment of the present disclosure, the terminal device can determine whether to communicate with the RPLMN based on the second target TA and the service domain restriction information. In the case that the second target TA is included in the non-permitted area of ​​the RPLMN, it is determined that communication between the second target TA and any eRPLMN (equivalent registered PLMN) is prohibited, which can avoid the failure of the service domain restriction.

[0143] Furthermore, in some embodiments, if the second target TA is included in the allowed area of ​​an RPLLMN, the terminal device determines whether to communicate with the eRPLMN based on the third target TA and the service domain restriction information, wherein the target TA is the third target TA corresponding to the eRPLMN.

[0144] Here, the target TA is the third target TA corresponding to eRPLMN.

[0145] It should be noted that the method by which the terminal device determines the third target TA corresponding to the eRPLMN where the terminal device is located in this embodiment is the same as the method by which the terminal device determines the target TA where the terminal device is located in the above embodiments. Please refer to the relevant description in the above embodiments, and it will not be repeated here.

[0146] In this embodiment of the disclosure, if the second target TA is contained within the allowed area of ​​an RPLLMN, the terminal device can determine whether to communicate with the eRPLMN based on the third target TA and the service domain restriction information.

[0147] In some embodiments, the terminal device determines whether to communicate with the eRPLMN based on a third target TA and service domain restriction information, including:

[0148] In response to the fact that the third target TA is included in the allowed area of ​​the eRPLMN, it is determined that communication between the third target TA and the eRPLMN is permitted, wherein service domain restriction information is used to indicate the allowed area of ​​the eRPLMN; or

[0149] In response to the fact that the third target TA is included in the non-allowed area of ​​the eRPLMN, it is determined that communication between the third target TA and the eRPLMN is prohibited, wherein the service domain restriction information is used to indicate the non-allowed area of ​​the eRPLMN.

[0150] In this embodiment of the disclosure, service domain restriction information is used to indicate the non-allowed area of ​​the eRPLMN or to indicate the allowed area of ​​the eRPLMN.

[0151] In this embodiment of the present disclosure, the terminal device can determine whether to communicate with the eRPLMN based on the third target TA and the service domain restriction information. If the third target TA is included in the allowed area of ​​the eRPLMN, it is determined that communication with the eRPLMN is allowed through the third target TA.

[0152] Among them, if the terminal device determines that communication with the eRPLMN is permitted at the third target TA, it may initiate a communication request to communicate with the eRPLMN, or it may choose not to initiate a communication request to communicate with the eRPLMN.

[0153] In this embodiment of the present disclosure, the terminal device can determine whether to communicate with the eRPLMN based on the third target TA and the service domain restriction information. In the case that the third target TA is included in the non-permitted area of ​​the eRPLMN, it is determined that communication with the eRPLMN is prohibited on the third target TA.

[0154] Based on this, in this embodiment of the disclosure, when the second target TA is contained within the allowed area of ​​an RPLLMN, the terminal device can determine the third target TA corresponding to the eRPLMN where the terminal device is located, and determine whether to communicate with the eRPLMN based on the third target TA and service domain restriction information. Specifically, if the third target TA is contained within the allowed area of ​​the eRPLMN, communication with the eRPLMN is permitted through the third target TA; if the third target TA is contained within the unpermitted area of ​​the eRPLMN, communication with the eRPLMN is prohibited through the third target TA. This avoids the failure of service domain restrictions.

[0155] It should be noted that in the embodiments of this disclosure, S51 can be implemented alone or in combination with any other step in the embodiments of this disclosure, such as in combination with S21 to S23 and / or S31 and / or S41 in the embodiments of this disclosure. The embodiments of this disclosure do not limit this.

[0156] By implementing the embodiments of this disclosure, the terminal device determines whether to communicate with a registered public terrestrial mobile network (RPLMN) based on a second target TA and service domain restriction information, wherein the target TA is the second target TA corresponding to the RPLMN. Therefore, by determining the target TA to which the terminal device is located, accurate control of the service domain restriction information can be ensured, preventing the service domain restriction information from becoming ineffective.

[0157] Please see Figure 6 , Figure 6 This is a flowchart of another mobility restriction implementation method provided in this embodiment.

[0158] like Figure 6As shown, the method may include, but is not limited to, the following steps:

[0159] S61: The core network equipment determines the target TA where the terminal equipment is located. The target TA is obtained from the access network equipment used by the terminal equipment to access the network, or the target TA is determined based on the mapping relationship between GAD and TA and the current GNSS information of the terminal equipment.

[0160] In this embodiment of the disclosure, the relevant description of the mapping relationship between GAD and TA obtained by the core network device can be found in the relevant description in the above embodiments, and will not be repeated here.

[0161] In this embodiment of the disclosure, after determining the mapping relationship between GAD and TA, the core network device can further obtain the current GNSS information of the terminal device. Furthermore, based on the mapping relationship and the current GNSS information of the terminal device, the target TA where the terminal device is located can be determined, or the target TA can be determined based on the TA representing the current location of the terminal device reported by the access network device and the mapping relationship.

[0162] The method by which core network equipment obtains the current GNSS information of terminal equipment can be determined based on protocol agreements, or it can be determined based on the configuration of access network equipment, and so on.

[0163] In some embodiments, the core network device determines the corresponding target GAD based on the current GNSS information of the terminal device; and determines the target TA where the terminal device is located based on the target GAD and the mapping relationship.

[0164] In this embodiment of the disclosure, the core network device can determine the target GAD corresponding to the current GNSS information based on the current GNSS information of the terminal device, and then determine the target TA where the terminal device is located based on the target GAD and the mapping relationship.

[0165] Understandably, core network equipment can determine the target TA of a terminal device at any stage where it is able to determine the current GNSS information of the terminal device, based on the mapping relationship between GAD and TA and the current GNSS information of the terminal device.

[0166] For example, when a terminal device accesses the network, the core network device can determine the target TA where the terminal device is located based on the mapping relationship between GAD and TA and the current GNSS information of the terminal device.

[0167] For example, when a terminal device initiates a communication request with the RPLMN, the core network can determine the target TA where the terminal device is located based on the mapping relationship between GAD and TA and the current GNSS information of the terminal device.

[0168] For example, when a terminal device initiates a communication request with the eRPLMN, the core network can determine the target TA where the terminal device is located based on the mapping relationship between GAD and TA and the current GNSS information of the terminal device.

[0169] It should be noted that the above examples are for illustrative purposes only and are not intended to limit the specific embodiments of this disclosure.

[0170] It should be noted that in the embodiments of this disclosure, S61 can be implemented alone or in combination with any other step in the embodiments of this disclosure, such as in combination with S21 to S23 and / or S41 and / or S51 in the embodiments of this disclosure. The embodiments of this disclosure do not limit this.

[0171] By implementing embodiments of this disclosure, the core network device determines the target TA where the terminal device is located based on the mapping relationship between GAD and TA, and the current GNSS information of the terminal device. This enables the determination of the target TA, allowing the terminal device and the core network device to implement mobility restrictions on the terminal device based on the target TA.

[0172] Please see Figure 7 , Figure 7 This is a flowchart of another mobility restriction implementation method provided in this disclosure embodiment.

[0173] like Figure 7 As shown, the method may include, but is not limited to, the following steps:

[0174] S71: The terminal device reports its GNSS information to the core network device.

[0175] In this embodiment of the disclosure, the terminal device reports its GNSS information to the core network device. The terminal device may report its GNSS information to the core network device during the positioning process.

[0176] S72: The core network equipment determines the target TA where the terminal equipment is located based on the mapping relationship between GAD and TA, as well as the current GNSS information of the terminal equipment.

[0177] The relevant description of S72 can be found in the relevant description in the above embodiments, and will not be repeated here.

[0178] It should be noted that in the embodiments of this disclosure, S71 and S72 can be implemented individually or in combination with any other step in the embodiments of this disclosure, such as in combination with S21 to S23 and / or S41 and / or S51 and / or S61 in the embodiments of this disclosure. The embodiments of this disclosure do not limit this.

[0179] By implementing the embodiments of this disclosure, the core network device receives GNSS information reported by the terminal device, and determines the target TA where the terminal device is located based on the mapping relationship between GAD and TA and the current GNSS information of the terminal device. Thus, the target TA where the terminal device is located can be determined, enabling the terminal device and the core network device to implement mobility restrictions on the terminal device based on the target TA.

[0180] Please see Figure 8 , Figure 8 This is a flowchart of another mobility management method provided in this disclosure.

[0181] like Figure 8 As shown, this method is executed by the core network device, and the method may include, but is not limited to, the following steps:

[0182] S81: The core network equipment determines whether to allow the terminal equipment to access the PLMN based on the first target TA and the prohibited access domain information, where the target TA is the first target TA corresponding to the PLMN.

[0183] In this embodiment of the disclosure, the method by which the core network device determines the target TA where the terminal device is located can be found in the relevant description in the above embodiments, and will not be repeated here.

[0184] Here, target TA is the first target TA corresponding to PLMN.

[0185] It should be noted that the method by which the core network device determines the first target TA corresponding to the PLMN where the terminal device is located in this embodiment is the same as the method by which the core network device determines the target TA where the terminal device is located in the above embodiments. Please refer to the relevant descriptions in the above embodiments, and they will not be repeated here.

[0186] In this embodiment of the disclosure, the core network device can determine whether to allow the terminal device to access the PLMN based on the first target TA and the prohibited access domain information.

[0187] In some embodiments, the core network device determines whether to allow the terminal device to access the PLMN based on the first target TA and the prohibited access domain information, including:

[0188] In response to the first target TA being included in the prohibited access domain of the PLMN, it is determined that the terminal device is prohibited from accessing the PLMN via the first target TA, wherein the prohibited access domain information is used to indicate the prohibited access domain of the PLMN; or

[0189] In response to the fact that the first target TA is not included in the prohibited access domain of the PLMN, it is determined that the terminal device is allowed to access the PLMN through the first target TA, wherein the prohibited access domain information is used to indicate the prohibited access domain of the PLMN.

[0190] In this embodiment of the disclosure, the forbidden access domain information is used to indicate the forbidden access domain of the PLMN.

[0191] In this embodiment of the disclosure, the core network device can determine whether to allow the terminal device to access the PLMN based on the first target TA and the prohibited access domain information. If the first target TA is included in the prohibited access domain of the PLMN, the device is prohibited from accessing the PLMN through the first target TA.

[0192] In this embodiment of the disclosure, the core network device can determine whether to allow the terminal device to access the PLMN based on the first target TA and the prohibited access domain information. In the case that the first target TA is not included in the prohibited access domain of the PLMN, the device is allowed to access the PLMN through the first target TA.

[0193] It should be noted that in the embodiments of this disclosure, S81 can be implemented alone or in combination with any other step in the embodiments of this disclosure, such as in combination with S21 to S23 and / or S41 and / or S51 and / or S61 and / or S71 and S72 in the embodiments of this disclosure. The embodiments of this disclosure do not limit this.

[0194] By implementing the embodiments of this disclosure, the terminal device determines whether to access the PLMN based on the first target TA and the prohibited access domain information, wherein the target TA is the first target TA corresponding to the PLMN. Therefore, based on determining the target TA where the terminal device is located, accurate control of the prohibited access domain information can be ensured, avoiding the failure of the prohibited access domain information restrictions.

[0195] Please see Figure 9 , Figure 9 This is a flowchart of another mobility management method provided in this disclosure.

[0196] like Figure 9 As shown, this method is executed by the core network device, and the method may include, but is not limited to, the following steps:

[0197] S91: The core network equipment determines whether to allow the terminal equipment to communicate with the RPLMN via the second target TA based on the second target TA and the service domain restriction information, wherein the target TA is the second target TA corresponding to the RPLMN.

[0198] In this embodiment of the disclosure, the method by which the core network device determines the target TA where the terminal device is located can be found in the relevant description in the above embodiments, and will not be repeated here.

[0199] Wherein, the target TA is the second target TA corresponding to RPLMN.

[0200] It should be noted that the method by which the core network device determines the second target TA corresponding to the RPLMN where the terminal device is located in this embodiment is the same as the method by which the core network device determines the target TA where the terminal device is located in the above embodiments. Please refer to the relevant descriptions in the above embodiments, and they will not be repeated here.

[0201] In this embodiment of the disclosure, the core network device can determine whether to allow the terminal device to communicate with the RPLMN at the second target TA based on the second target TA and the service domain restriction information.

[0202] In some embodiments, the core network device determines whether to allow the terminal device to communicate with the RPLMN at the second target TA based on the second target TA and the service domain restriction information, including:

[0203] In response to the second target TA being included in the unauthorized area of ​​the RPLMN, it is determined that communication between the terminal device and the RPLMN is prohibited on the second target TA, wherein the service domain restriction information is used to indicate the unauthorized area of ​​the RPLMN; or

[0204] In response to the second target TA being included in the non-allowed area of ​​the RPLLMN, it is determined that the terminal device is prohibited from communicating with any eRPLMN on the second target TA, wherein the service domain restriction information is used to indicate the non-allowed area of ​​the RPLLMN; or

[0205] In response to the fact that the second target TA is included in the allowed area of ​​the RPLMN, it is determined that the terminal device is allowed to communicate with the RPLMN through the second target TA, wherein the service domain restriction information is used to indicate the allowed area of ​​the RPLMN.

[0206] In this embodiment of the disclosure, service domain restriction information is used to indicate the non-allowed area of ​​RPLMN or to indicate the allowed area of ​​RPLMN.

[0207] In this embodiment of the disclosure, the core network device can determine whether to allow the terminal device to communicate with the RPLMN at the second target TA based on the second target TA and the service domain restriction information. If the second target TA is included in the non-allowed area of ​​the RPLMN, the device is prohibited from communicating with the RPLMN at the second target TA.

[0208] In this embodiment of the disclosure, the core network device can determine whether to allow the terminal device to communicate with the RPLMN at the second target TA based on the second target TA and the service domain restriction information. If the second target TA is included in the non-allowed area of ​​the RPLMN, the device is prohibited from communicating with any eRPLMN at the second target TA.

[0209] In this embodiment of the disclosure, the core network device can determine whether to allow the terminal device to communicate with the RPLMN at the second target TA based on the second target TA and the service domain restriction information. If the second target TA is included in the allowed area of ​​the RPLMN, it is determined that the terminal device is allowed to communicate with the RPLMN at the second target TA.

[0210] It is understandable that service area restriction information may include permitted or prohibited areas (e.g., specified using a tracking area identifier).

[0211] The permitted area is the zone in which the terminal device is allowed to initiate communication with the network.

[0212] The non-permitted area is where terminal devices are subject to service restrictions. Terminal devices are not permitted to initiate service requests to the network, or any connection requests for user plane data or control plane data.

[0213] Allowed and prohibited regions can be specified using tracking region identifiers. For example, an allowed region can contain one or more (e.g., up to 16) tracking areas, or all tracking areas can be placed in the allowed region.

[0214] The core network equipment (AMF) can assign service area restriction information to terminal devices based on their subscriptions and can update it as needed. This information can be provided to terminal devices through a registration program or a UCU program. When provided to terminal devices, it can only contain either permitted or unpermitted areas, not both simultaneously.

[0215] If a terminal device uses satellite access, and the access network device broadcasts multiple TAIs to the terminal device, during the terminal device's network access process, the access network device reports the broadcast multiple TAIs to the core network device. The core network device will then execute the following service area restriction rules:

[0216] If all the broadcast TAIs are contained within the non-allowed area, then both the terminal device and the AMF consider the terminal device to be located within the non-allowed area.

[0217] If at least one of the TAIs broadcast is not contained in the non-allowed area, then both the terminal device and the AMF consider the terminal device to be in the allowed area.

[0218] In related technologies, for situations where a satellite access network is shared by multiple networks (e.g., PLMN-A and PLMN-B share the same satellite access),

[0219] The satellite access network broadcasts multiple TAIs of available PLMNs to the terminal device. During the registration process of the terminal device accessing the network, the satellite access device reports the broadcast multiple TAIs to the core network. The core network assigns a registration area to it. In addition to the registered PLMN (RPLMN), the registration area also contains at least one equivalent registered PLMN (eRPLMN). That is, the registration area contains a list of TAIs from the RPLMN and the equivalent RPLMN.

[0220] At the same time, the core network also allocates an allowed area for terminal devices, which also includes the TAI of RPLLMN and the TAI of eRPLMN.

[0221] Subsequently, due to the movement of the terminal device, the following situation may occur:

[0222] 1. All broadcast TAIs belonging to RPLMN in the received broadcast TAIs are not within the allowed area. However,

[0223] 2. Within the permitted area, there must be at least one broadcast TAI belonging to an eRPLMN.

[0224] In this scenario, based on the current solution: According to option 1, the terminal device at the current location is not allowed to communicate with the network, while according to option 2, the terminal device at the current location can communicate using eRPLMN. In this case, imposing service area restrictions on the terminal device at the current location is ineffective.

[0225] Based on this, in this embodiment of the disclosure, the core network device can determine whether to allow the terminal device to communicate with the RPLMN at the second target TA based on the second target TA and the service domain restriction information. In the case that the second target TA is included in the non-allowed area of ​​the RPLMN, it is determined that the terminal device is prohibited from communicating with any eRPLMN at the second target TA, which can avoid the failure of the service domain restriction.

[0226] Furthermore, in some embodiments, if the second target TA is included in the allowed area of ​​the RPLLMN, the core network device determines whether to allow the terminal device to communicate with the eRPLMN in the third target TA based on the third target TA and the service domain restriction information, wherein the target TA is the third target TA corresponding to the eRPLMN.

[0227] Here, the target TA is the third target TA corresponding to eRPLMN.

[0228] It should be noted that the method by which the core network device determines the third target TA corresponding to the eRPLMN where the terminal device is located in this embodiment is the same as the method by which the core network device determines the target TA where the terminal device is located in the above embodiments. Please refer to the relevant descriptions in the above embodiments, and they will not be repeated here.

[0229] In this embodiment of the disclosure, if the second target TA is included in the allowed area of ​​an RPLLMN, the core network device can determine whether to allow the terminal device to communicate with the eRPLMN in the third target TA based on the third target TA and the service domain restriction information.

[0230] In some embodiments, the core network device determines whether to allow the terminal device to communicate with the eRPLMN at the third target TA based on the third target TA and the service domain restriction information, including:

[0231] In response to the fact that the third target TA is included in the allowed area of ​​the eRPLMN, it is determined that the terminal device is allowed to communicate with the eRPLMN in the third target TA, wherein the service domain restriction information is used to indicate the allowed area of ​​the eRPLMN; or

[0232] In response to the fact that the third target TA is included in the non-allowed area of ​​the eRPLMN, it is determined that the terminal device is prohibited from communicating with the eRPLMN in the third target TA, wherein the service domain restriction information is used to indicate the non-allowed area of ​​the eRPLMN.

[0233] In this embodiment of the disclosure, service domain restriction information is used to indicate the non-allowed area of ​​the eRPLMN or to indicate the allowed area of ​​the eRPLMN.

[0234] In this embodiment of the disclosure, the core network device can determine whether to allow the terminal device to communicate with the eRPLMN on the third target TA and the service domain restriction information. If the third target TA is included in the allowed area of ​​the eRPLMN, it is determined that the terminal device is allowed to communicate with the eRPLMN on the third target TA.

[0235] In this embodiment of the disclosure, the core network device can determine whether to allow the terminal device to communicate with the eRPLMN in the third target TA and the service domain restriction information. In the case that the third target TA is included in the non-permitted area of ​​the eRPLMN, the terminal device is prohibited from communicating with the eRPLMN in the third target TA.

[0236] Based on this, in this embodiment of the disclosure, when the second target TA is contained within the allowed area of ​​an RPLLMN, the core network device can determine the third target TA corresponding to the eRPLMN where the terminal device is located. Based on the third target TA and service domain restriction information, it determines that the terminal device is allowed to communicate with the eRPLMN within the third target TA. Specifically, if the third target TA is contained within the allowed area of ​​the eRPLMN, communication between the terminal device and the eRPLMN is permitted; if the third target TA is contained within the unpermitted area of ​​the eRPLMN, communication between the terminal device and the eRPLMN is prohibited. This avoids the failure of service domain restrictions.

[0237] For example, such as Figure 10 As shown in the embodiments of this disclosure, a method for core network equipment to perform mobility management is provided.

[0238] 0. After the terminal device connects to the PLMN, it needs to initiate a service request to restore the user plane connection. The terminal device obtains its current location information (GNSS information) and determines its current target TA based on the mapping relationship between GAD and TA.

[0239] 1. The terminal device checks if the target TA is contained in a non-allowed zone of RPLMN. At this point, according to the rules, the terminal device will not initiate a service request for the current target TA. However, a malicious terminal device might initiate this process.

[0240] 2. The process of the terminal device initiating a service request at the current target TA.

[0241] 3. The AMF obtains the target TA of the terminal device and determines whether the target TA is contained within the non-allowed zone of the RPLLMN. If so, the AMF must reject the service request from the terminal device. If the terminal device uses another eRPLMN for access, and if the current target TA of the terminal device has not changed, the terminal device is still in the non-allowed zone of the RPLLMN. In this case, even if the terminal device uses another eRPLMN for access, the AMF still will not allow the initiation of a service request process.

[0242] 4. The AMF returns a service rejection message to the terminal device. The service rejection message can state the reason for the rejection: the terminal device is in an unauthorized area and is not allowed to initiate a service request process.

[0243] It should be noted that in the embodiments of this disclosure, S91 can be implemented alone or in combination with any other step in the embodiments of this disclosure, such as in combination with S21 to S23 and / or S41 and / or S51 and / or S61 and / or S71 and S72 and / or S81 in the embodiments of this disclosure. The embodiments of this disclosure do not limit this.

[0244] By implementing the embodiments of this disclosure, the core network device determines whether to allow the terminal device to communicate with the RPLMN via the second target TA based on the second target TA and the service domain restriction information, wherein the target TA is the second target TA corresponding to the RPLMN. Therefore, by determining the target TA where the terminal device is located, accurate control of the service domain restriction information can be ensured, avoiding the failure of the service domain restriction information.

[0245] The methods provided in the embodiments of this disclosure above are described from the perspectives of terminal devices, core network devices, and the interaction between terminal devices and core network devices.

[0246] Please see Figure 11 This is a schematic diagram of the structure of a communication device 1 provided in an embodiment of the present disclosure. Figure 11 The communication device 1 shown may include a transceiver module 101 and a processing module 102. The transceiver module may include a sending module and / or a receiving module. The sending module is used to implement the sending function, and the receiving module is used to implement the receiving function. The transceiver module can implement both sending and / or receiving functions.

[0247] Communication device 1 can be a terminal device, a device within a terminal device, or a device compatible with a terminal device. Alternatively, communication device 1 can be a core network device, a device within a core network device, or a device compatible with a core network device.

[0248] Communication device 1 is a terminal device:

[0249] The device includes a transceiver module 101 and a processing module 102.

[0250] The transceiver module 101 is configured to obtain the mapping relationship between GAD and TA.

[0251] The processing module 102 is configured to determine the target TA of the terminal device based on the mapping relationship and the current GNSS information of the terminal device.

[0252] In some embodiments, the processing module 102 is further configured to determine the corresponding target GAD based on the current GNSS information of the terminal device; and to determine the target TA where the terminal device is located based on the target GAD and the mapping relationship.

[0253] In some embodiments, the processing module 102 is further configured to determine whether to access the Public Land Mobile Network (PLMN) based on the first target TA and the prohibited access domain information, wherein the target TA is the first target TA corresponding to the PLMN.

[0254] In some embodiments, the processing module 102 is further configured to determine that access to the PLMN is prohibited for the first target TA in response to the first target TA being included in the prohibited access domain of the PLMN; or to determine that access to the PLMN is permitted for the first target TA in response to the first target TA not being included in the prohibited access domain of the PLMN, wherein the prohibited access domain information is used to indicate the prohibited access domain of the PLMN.

[0255] In some embodiments, the processing module 102 is further configured to determine whether to communicate with a registered public land mobile network (RPLMN) based on a second target TA and service domain restriction information, wherein the target TA is the second target TA corresponding to the RPLMN.

[0256] In some embodiments, the processing module 102 is further configured to, in response to the second target TA being included in a non-permitted area of ​​the RPLMN, determine to prohibit communication between the second target TA and the RPLMN, wherein the service domain restriction information is used to indicate the non-permitted area of ​​the RPLMN; or in response to the second target TA being included in a non-permitted area of ​​the RPLMN, determine to prohibit communication between the second target TA and any equivalent registered public land mobile network eRPLMN, wherein the service domain restriction information is used to indicate the non-permitted area of ​​the RPLMN; or in response to the second target TA being included in a permitted area of ​​the RPLMN, determine to allow communication between the second target TA and the RPLMN, wherein the service domain restriction information is used to indicate the permitted area of ​​the RPLMN.

[0257] In some embodiments, the processing module 102 is further configured to determine whether to communicate with the eRPLMN based on the third target TA and service domain restriction information, if the second target TA is contained in an allowed area of ​​an RPLLMN, wherein the target TA is the third target TA corresponding to the eRPLMN.

[0258] In some embodiments, the processing module 102 is further configured to determine, in response to the third target TA being included in the allowed area of ​​the eRPLMN, to allow communication between the third target TA and the eRPLMN, wherein service domain restriction information is used to indicate the allowed area of ​​the eRPLMN; or in response to the third target TA being included in the unallowed area of ​​the eRPLMN, to determine to prohibit communication between the third target TA and the eRPLMN, wherein service domain restriction information is used to indicate the unallowed area of ​​the eRPLMN.

[0259] In some embodiments, the transceiver module 101 is further configured to report the GNSS information of the terminal device to the core network device.

[0260] Communication device 1 is a core network device:

[0261] The device includes a transceiver module 101 and a processing module 102.

[0262] Processing module 102 is configured to obtain the mapping relationship between GAD and TA;

[0263] The transceiver module 101 is configured to send the mapping relationship between GAD and TA to the terminal device, wherein the mapping relationship is used by the terminal device to determine the target TA it is in.

[0264] Communication device 1 is a core network device:

[0265] The device includes a transceiver module 101 and a processing module 102.

[0266] The processing module 102 is configured to determine the target TA where the terminal device is located. The target TA is obtained from the access network equipment used by the terminal device to access the network, or the target TA is determined based on the mapping relationship between GAD and TA and the current GNSS information of the terminal device.

[0267] In some embodiments, the transceiver module 101 is configured to receive the current GNSS information of the terminal device reported by the terminal device.

[0268] In some embodiments, the processing module 102 is further configured to determine the corresponding target GAD based on the current GNSS information of the terminal device; and to determine the target TA where the terminal device is located based on the target GAD and the mapping relationship.

[0269] In some embodiments, the processing module 102 is further configured to determine whether to allow the terminal device to access the PLMN based on the first target TA and the prohibited access domain information, wherein the target TA is the first target TA corresponding to the PLMN.

[0270] In some embodiments, the processing module 102 is further configured to determine, in response to the first target TA being included in the prohibited access domain of the PLMN, to prohibit the terminal device from accessing the PLMN via the first target TA, wherein the prohibited access domain information is used to indicate the prohibited access domain of the PLMN; or in response to the first target TA not being included in the prohibited access domain of the PLMN, to determine to allow the terminal device to access the PLMN via the first target TA, wherein the prohibited access domain information is used to indicate the prohibited access domain of the PLMN.

[0271] In some embodiments, the processing module 102 is further configured to determine whether to allow the terminal device to communicate with the RPLMN via the second target TA based on the second target TA and the service domain restriction information, wherein the target TA is the second target TA corresponding to the RPLMN.

[0272] In some embodiments, the processing module 102 is further configured to, in response to the second target TA being included in the non-allowed area of ​​the RPLMN, determine to prohibit the terminal device from communicating with the RPLMN on the second target TA, wherein the service domain restriction information is used to indicate the non-allowed area of ​​the RPLMN; or in response to the second target TA being included in the non-allowed area of ​​the RPLMN, determine to prohibit the terminal device from communicating with any eRPLMN on the second target TA, wherein the service domain restriction information is used to indicate the non-allowed area of ​​the RPLMN; or in response to the second target TA being included in the allowed area of ​​the RPLMN, determine to allow the terminal device to communicate with the RPLMN on the second target TA, wherein the service domain restriction information is used to indicate the allowed area of ​​the RPLMN.

[0273] In some embodiments, the processing module 102 is further configured to, if the second target TA is included in the allowed area of ​​the RPLLMN, determine whether to allow the terminal device to communicate with the eRPLMN on the third target TA based on the third target TA and service domain restriction information, wherein the target TA is the third target TA corresponding to the eRPLMN.

[0274] In some embodiments, the processing module 102 is further configured to determine, in response to the third target TA being included in the allowed area of ​​the eRPLMN, to allow the terminal device to communicate with the eRPLMN in the third target TA, wherein the service domain restriction information is used to indicate the allowed area of ​​the eRPLMN; or to determine, in response to the third target TA being included in the unallowed area of ​​the eRPLMN, to prohibit the terminal device from communicating with the eRPLMN in the third target TA, wherein the service domain restriction information is used to indicate the unallowed area of ​​the eRPLMN.

[0275] Regarding the communication device 1 in the above embodiments, the specific methods by which each module performs operations have been described in detail in the embodiments related to the method, and will not be elaborated here.

[0276] The communication device 1 provided in the above embodiments of this disclosure achieves the same or similar beneficial effects as the mobility restriction implementation method or mobility management method provided in some of the above embodiments, and will not be repeated here.

[0277] Please see Figure 12 , Figure 12This is a schematic diagram of another communication device 1000 provided in this embodiment. The communication device 1000 can be a terminal device, a core network device, or a chip, chip system, or processor that supports the terminal device in implementing the above methods. It can also be a chip, chip system, or processor that supports the core network device in implementing the above methods. This communication device 1000 can be used to implement the methods described in the above method embodiments; for details, please refer to the descriptions in the above method embodiments.

[0278] The communication device 1000 may include one or more processors 1001. The processor 1001 may be a general-purpose processor or a dedicated processor, such as a baseband processor or a central processing unit (CPU). The baseband processor can be used to process communication protocols and communication data, while the CPU can be used to control the communication device (e.g., core network equipment, baseband chip, terminal equipment, terminal equipment chip, DU or CU, etc.), execute computer programs, and process data from the computer programs.

[0279] Optionally, the communication device 1000 may further include one or more memories 1002, which may store a computer program 1004. The memories 1002 execute the computer program 1004 to cause the communication device 1000 to perform the methods described in the above method embodiments. Optionally, the memories 1002 may also store data. The communication device 1000 and the memories 1002 may be provided separately or integrated together.

[0280] Optionally, the communication device 1000 may further include a transceiver 1005 and an antenna 1006. The transceiver 1005 may be referred to as a transceiver unit, transceiver, or transceiver circuit, etc., and is used to implement the transmission and reception functions. The transceiver 1005 may include a receiver and a transmitter. The receiver may be referred to as a receiver or receiving circuit, etc., and is used to implement the receiving function; the transmitter may be referred to as a transmitter or transmitting circuit, etc., and is used to implement the transmitting function.

[0281] Optionally, the communication device 1000 may further include one or more interface circuits 1007. The interface circuit 1007 is used to receive code instructions and transmit them to the processor 1001. The processor 1001 executes the code instructions to cause the communication device 1000 to perform the method described in the above method embodiments.

[0282] Communication device 1000 is a terminal device: transceiver 1005 is used to perform... Figure 2 S22 in the middle; Figure 7 The S71 in the processor 1001 is used to execute... Figure 2 S23 in: Figure 4 S41 in; Figure 5 S51 in the middle.

[0283] Communication device 1000 is a core network device: processor 1001 is used to execute... Figure 2 S21 in: Figure 6 S61 in; Figure 7 S72 in the middle; Figure 8 S81 in; Figure 9 S91 in the transceiver 1005 is used to perform Figure 2 S22 in the middle; Figure 7 S71 in the middle.

[0284] In one implementation, the processor 1001 may include a transceiver for implementing receiving and transmitting functions. For example, the transceiver may be a transceiver circuit, an interface, or an interface circuit. The transceiver circuit, interface, or interface circuit for implementing receiving and transmitting functions may be separate or integrated. The aforementioned transceiver circuit, interface, or interface circuit can be used for reading and writing code / data, or it can be used for transmitting or relaying signals.

[0285] In one implementation, processor 1001 may store computer program 1003, which runs on processor 1001 and causes communication device 1000 to execute the methods described in the above method embodiments. Computer program 1003 may be embedded in processor 1001, in which case processor 1001 may be implemented in hardware.

[0286] In one implementation, the communication device 1000 may include circuitry capable of performing the functions of transmitting, receiving, or communicating as described in the foregoing method embodiments. The processor and transceiver described in this disclosure can be implemented on integrated circuits (ICs), analog ICs, radio frequency integrated circuits (RFICs), mixed-signal ICs, application-specific integrated circuits (ASICs), printed circuit boards (PCBs), electronic devices, etc. The processor and transceiver can also be manufactured using various IC process technologies, such as complementary metal oxide semiconductors (CMOS), n-metal-oxide-semiconductor (NMOS), positive-channel metal oxide semiconductors (PMOS), bipolar junction transistors (BJTs), bipolar CMOS (BiCMOS), silicon-germanium (SiGe), gallium arsenide (GaAs), etc.

[0287] The communication device described in the above embodiments may be a terminal device or a core network device, but the scope of the communication device described in this disclosure is not limited thereto, and the structure of the communication device may vary. Figure 12 The communication device may be a standalone device or part of a larger device. For example, the communication device may be:

[0288] (1) Independent integrated circuit IC, or chip, or chip system or subsystem;

[0289] (2) A collection of one or more ICs, optionally including storage components for storing data and computer programs;

[0290] (3) ASIC, such as modem;

[0291] (4) Modules that can be embedded in other devices;

[0292] (5) Receivers, terminal equipment, smart terminal equipment, cellular phones, wireless equipment, handheld devices, mobile units, vehicle-mounted equipment, network equipment, cloud equipment, artificial intelligence equipment, etc.

[0293] (6) Others, etc.

[0294] For cases where the communication device can be a chip or a chip system, please refer to [link / reference]. Figure 13 This is a structural diagram of a chip provided in an embodiment of this disclosure.

[0295] Chip 1100 includes processor 1101 and interface 1103. The number of processors 1101 can be one or more, and the number of interfaces 1103 can be multiple.

[0296] Regarding the case where the chip is used to implement the functions of the terminal device in the embodiments of this disclosure:

[0297] Interface 1103 is used to receive code instructions and transmit them to the processor.

[0298] Processor 1101 is configured to run code instructions to perform mobility restriction implementation methods as described in some of the embodiments above.

[0299] For cases where the chip is used to implement the functions of the core network device in the embodiments of this disclosure:

[0300] Interface 1103 is used to receive code instructions and transmit them to the processor.

[0301] Processor 1101 is configured to run code instructions to perform mobility restriction implementation methods as described in some of the embodiments above.

[0302] Optionally, chip 1100 may also include memory 1102, which is used to store necessary computer programs and data.

[0303] Those skilled in the art will also understand that the various illustrative logical blocks and steps listed in the embodiments of this disclosure can be implemented by electronic hardware, computer software, or a combination of both. Whether such functionality is implemented in hardware or software depends on the specific application and the overall system design requirements. Those skilled in the art can implement the described functionality using various methods for each specific application, but such implementation should not be construed as exceeding the scope of protection of the embodiments of this disclosure.

[0304] This disclosure also provides a mobility restriction implementation system, which includes the aforementioned... Figure 11 In the embodiments, the communication device serves as a terminal device and the communication device serves as a core network device; alternatively, the system includes the aforementioned components. Figure 12 The embodiments include a communication device as a terminal device and a communication device as a core network device.

[0305] This disclosure also provides a readable storage medium having instructions stored thereon that, when executed by a computer, implement the functions of any of the above method embodiments.

[0306] This disclosure also provides a computer program product that, when executed by a computer, implements the functions of any of the above method embodiments.

[0307] In the above embodiments, implementation can be achieved, in whole or in part, through software, hardware, firmware, or any combination thereof. When implemented using software, it can be implemented, in whole or in part, as a computer program product. The computer program product includes one or more computer programs. When the computer program is loaded and executed on a computer, all or part of the processes or functions described in the embodiments of this disclosure are generated. The computer can be a general-purpose computer, a special-purpose computer, a computer network, or other programmable device. The computer program can be stored in a computer-readable storage medium or transferred from one computer-readable storage medium to another. For example, the computer program can be transferred from one website, computer, server, or data center to another via wired (e.g., coaxial cable, fiber optic, digital subscriber line (DSL)) or wireless (e.g., infrared, wireless, microwave, etc.) means. The computer-readable storage medium can be any available medium accessible to a computer or a data storage device such as a server or data center that integrates one or more available media. The available media may be magnetic media (e.g., floppy disks, hard disks, magnetic tapes), optical media (e.g., high-density digital video discs (DVDs)), or semiconductor media (e.g., solid-state disks (SSDs)).

[0308] Those skilled in the art will understand that the various numerical designations such as "first," "second," etc., used in this disclosure are merely for the convenience of description and are not intended to limit the scope of the embodiments of this disclosure, nor do they indicate the order of events.

[0309] At least one of the features described in this disclosure can also be described as one or more, and multiple features can be two, three, four or more, and this disclosure does not impose any limitations. In the embodiments of this disclosure, for a technical feature, the technical features in that technical feature are distinguished by "first", "second", "third", "A", "B", "C" and "D", etc., and there is no sequential order or size order among the technical features described by "first", "second", "third", "A", "B", "C" and "D".

[0310] The correspondences shown in the tables of this disclosure can be configured or predefined. The values ​​of the information in each table are merely examples and can be configured to other values; this disclosure is not limiting. When configuring the correspondences between information and parameters, it is not necessarily required to configure all the correspondences shown in each table. For example, the correspondences shown in some rows of the tables in this disclosure may not be configured. Furthermore, appropriate modifications and adjustments can be made based on the above tables, such as splitting, merging, etc. The names of the parameters shown in the headers of the above tables can also use other names that the communication device can understand, and the values ​​or representations of the parameters can also be other values ​​or representations that the communication device can understand. In the implementation of the above tables, other data structures can also be used, such as arrays, queues, containers, stacks, linear lists, pointers, linked lists, trees, graphs, structures, classes, heaps, hash tables, or hash tables, etc.

[0311] The predefined terms in this disclosure can be understood as defined, predefined, stored, pre-stored, pre-negotiated, pre-configured, solidified, or pre-burned.

[0312] Those skilled in the art will recognize that the units and algorithm steps of the various examples described in conjunction with the embodiments disclosed herein can be implemented in electronic hardware, or a combination of computer software and electronic hardware. Whether these functions are implemented in hardware or software depends on the specific application and design constraints of the technical solution. Those skilled in the art can use different methods to implement the described functions for each specific application, but such implementation should not be considered beyond the scope of this disclosure.

[0313] Those skilled in the art will understand that, for the sake of convenience and brevity, the specific working processes of the systems, devices, and units described above can be referred to the corresponding processes in the foregoing method embodiments, and will not be repeated here.

[0314] The above description is merely a specific embodiment of this disclosure, but the scope of protection of this disclosure is not limited thereto. Any variations or substitutions that can be easily conceived by those skilled in the art within the scope of the technology disclosed in this disclosure should be included within the scope of protection of this disclosure. Therefore, the scope of protection of this disclosure should be determined by the scope of the claims.

Claims

1. A method for implementing mobility restrictions, characterized in that, The method is executed by a terminal device and includes: Obtain the mapping relationship between the geographic region description (GAD) and the tracking area (TA); Based on the mapping relationship and the current GNSS information of the terminal device, the target TA of the terminal device is determined; The method further includes: determining whether to communicate with a registered public land mobile network (RPLMN) based on a second target TA and service domain restriction information, wherein the target TA is the second target TA corresponding to the RPLMN; The step of determining whether to communicate with an RPLLMN based on the second target TA and service domain restriction information includes: in response to the second target TA being included in the non-permitted area of ​​the RPLLMN, determining to prohibit communication between the second target TA and any equivalent registered public land mobile network eRPLMN, wherein the service domain restriction information is used to indicate the non-permitted area of ​​the RPLLMN.

2. The method as described in claim 1, characterized in that, Determining the target TA (Target Area) of the terminal device based on the mapping relationship and the current GNSS information of the terminal device includes: Based on the current GNSS information of the terminal device, determine the corresponding target GAD; Based on the target GAD and the mapping relationship, the target TA where the terminal device is located is determined.

3. The method as described in claim 1, characterized in that, The method further includes: Based on the first target TA and the prohibited access domain information, it is determined whether to access the Public Land Mobile Network (PLMN), wherein the target TA is the first target TA corresponding to the PLMN.

4. The method as described in claim 3, characterized in that, The step of determining whether to access the PLMN based on the first target TA and the prohibited access domain information includes at least one of the following: In response to the fact that the first target TA is included in the prohibited access domain of the PLMN, it is determined that access to the PLMN is prohibited for the first target TA; In response to the fact that the first target TA is not included in the prohibited access domain of the PLMN, it is determined that access to the PLMN is permitted through the first target TA, wherein the prohibited access domain information is used to indicate the prohibited access domain of the PLMN.

5. The method as described in claim 1, characterized in that, The step of determining whether to communicate with RPLMN based on the second target TA and the service domain restriction information further includes at least one of the following: In response to the second target TA being included in the non-allowed area of ​​the RPLMN, it is determined that communication between the second target TA and the RPLMN is prohibited, wherein the service domain restriction information is used to indicate the non-allowed area of ​​the RPLMN; In response to the second target TA being included in the allowed area of ​​the RPLMN, it is determined that communication between the second target TA and the RPLMN is permitted, wherein the service domain restriction information is used to indicate the allowed area of ​​the RPLMN.

6. The method as described in claim 5, characterized in that, The method further includes: If the second target TA is included in the allowed area of ​​the RPLLMN, it is determined whether to communicate with the eRPLMN based on the third target TA and service domain restriction information, wherein the target TA is the third target TA corresponding to the eRPLMN.

7. The method as described in claim 6, characterized in that, The step of determining whether to communicate with eRPLMN based on the third target TA and service domain restriction information includes at least one of the following: In response to the fact that the third target TA is included in the allowed area of ​​the eRPLMN, it is determined that communication between the third target TA and the eRPLMN is permitted, wherein the service domain restriction information is used to indicate the allowed area of ​​the eRPLMN; In response to the fact that the third target TA is included in the non-allowed area of ​​the eRPLMN, it is determined that communication between the third target TA and the eRPLMN is prohibited, wherein the service domain restriction information is used to indicate the non-allowed area of ​​the eRPLMN.

8. The method according to any one of claims 1 to 7, characterized in that, The method further includes: The GNSS information of the terminal device is reported to the core network equipment.

9. A method for implementing mobility restrictions, characterized in that, The method is executed by core network equipment and includes: Obtain the mapping relationship between the geographic region description (GAD) and the tracking area (TA); send the mapping relationship between the GAD and the TA to the terminal device, wherein the mapping relationship is used to enable the terminal device to determine the target TA it is in; Determine the target TA where the terminal device is located, wherein the target TA is obtained from the access network equipment used by the terminal device to access the network, or the target TA is determined based on the mapping relationship between the geographical region description GAD and the tracking area TA, and the current GNSS information of the terminal device; The method further includes: determining whether to allow the terminal device to communicate with the RPLMN on the second target TA based on the second target TA and service domain restriction information, wherein the target TA is the second target TA corresponding to the RPLMN; The step of determining whether to allow the terminal device to communicate with the RPLMN in the second target TA based on the second target TA and the service domain restriction information includes: in response to the second target TA being included in the non-allowed area of ​​the RPLMN, determining to prohibit the terminal device from communicating with any eRPLMN in the second target TA, wherein the service domain restriction information is used to indicate the non-allowed area of ​​the RPLMN.

10. The method as described in claim 9, characterized in that, The method further includes: Receive the current GNSS information of the terminal device reported by the terminal device.

11. The method as described in claim 9, characterized in that, The method further includes: Based on the current GNSS information of the terminal device, determine the corresponding target GAD; Based on the target GAD and the mapping relationship, the target TA where the terminal device is located is determined.

12. The method as described in claim 9, characterized in that, The method further includes: Based on the first target TA and the prohibited access domain information, it is determined whether the terminal device is allowed to access the PLMN through the first target TA, wherein the target TA is the first target TA corresponding to the PLMN.

13. The method as described in claim 12, characterized in that, The step of determining whether to allow the terminal device to access the PLMN through the first target TA based on the first target TA and the prohibited access domain information includes: In response to the first target TA being included in the prohibited access domain of the PLMN, it is determined that the terminal device is prohibited from accessing the PLMN through the first target TA, wherein the prohibited access domain information is used to indicate the prohibited access domain of the PLMN; or In response to the fact that the first target TA is not included in the prohibited access domain of the PLMN, it is determined that the terminal device is allowed to access the PLMN through the first target TA, wherein the prohibited access domain information is used to indicate the prohibited access domain of the PLMN.

14. The method according to any one of claims 9 to 13, characterized in that, The step of determining whether to allow the terminal device to communicate with the RPLMN on the second target TA based on the second target TA and the service domain restriction information includes: In response to the second target TA being included in the unauthorized area of ​​the RPLMN, it is determined that the terminal device is prohibited from communicating with the RPLMN in the second target TA, wherein the service domain restriction information is used to indicate the unauthorized area of ​​the RPLMN; or In response to the second target TA being included in the allowed area of ​​the RPLMN, it is determined that the terminal device is allowed to communicate with the RPLMN in the second target TA, wherein the service domain restriction information is used to indicate the allowed area of ​​the RPLMN.

15. The method as described in claim 14, characterized in that, The method further includes: If the second target TA is included in the allowed area of ​​the RPLLMN, based on the third target TA and service domain restriction information, it is determined whether the terminal device is allowed to communicate with the eRPLMN on the third target TA, wherein the target TA is the third target TA corresponding to the eRPLMN.

16. The method as described in claim 15, characterized in that, The step of determining whether to allow the terminal device to communicate with the eRPLMN on the third target TA based on the third target TA and the service domain restriction information includes: In response to the fact that the third target TA is included in the allowed area of ​​the eRPLMN, it is determined that the terminal device is allowed to communicate with the eRPLMN via the third target TA, wherein the service domain restriction information is used to indicate the allowed area of ​​the eRPLMN; or In response to the fact that the third target TA is included in the non-allowed area of ​​the eRPLMN, it is determined that the terminal device is prohibited from communicating with the eRPLMN in the third target TA, wherein the service domain restriction information is used to indicate the non-allowed area of ​​the eRPLMN.

17. A terminal device, characterized in that, The terminal device is used for: Obtain the mapping relationship between GAD and TA; Based on the mapping relationship and the current GNSS information of the terminal device, the target TA of the terminal device is determined; Based on the second target TA and service domain restriction information, determine whether to communicate with a registered public land mobile network (RPLMN), wherein the target TA is the second target TA corresponding to the RPLMN; The step of determining whether to communicate with an RPLLMN based on the second target TA and service domain restriction information includes: in response to the second target TA being included in the non-permitted area of ​​the RPLLMN, determining to prohibit communication between the second target TA and any equivalent registered public land mobile network eRPLMN, wherein the service domain restriction information is used to indicate the non-permitted area of ​​the RPLLMN.

18. A core network device, characterized in that, The core network equipment is used for: Obtain the mapping relationship between GAD and TA; send the mapping relationship between GAD and TA to the terminal device, wherein the mapping relationship is used by the terminal device to determine the target TA it is in; Determine the target TA where the terminal device is located, wherein the target TA is obtained from the access network equipment used by the terminal device to access the network, or the target TA is determined based on the mapping relationship between the geographical region description GAD and the tracking area TA, and the current GNSS information of the terminal device; Based on the second target TA and the service domain restriction information, determine whether the terminal device is allowed to communicate with the RPLMN on the second target TA, wherein the target TA is the second target TA corresponding to the RPLMN; The step of determining whether to allow the terminal device to communicate with the RPLMN in the second target TA based on the second target TA and the service domain restriction information includes: in response to the second target TA being included in the non-allowed area of ​​the RPLMN, determining to prohibit the terminal device from communicating with any eRPLMN in the second target TA, wherein the service domain restriction information is used to indicate the non-allowed area of ​​the RPLMN.

19. A communication system, characterized in that, The device includes a terminal device and a core network device, wherein the terminal device is configured to implement the method of any one of claims 1 to 8, and the core network device is configured to implement the method of any one of claims 9 to 16.

20. A communication device, characterized in that, The device includes a processor and a memory, the memory storing a computer program, the processor executing the computer program stored in the memory to cause the device to perform the method as claimed in any one of claims 1 to 8, or the processor executing the computer program stored in the memory to cause the device to perform the method as claimed in any one of claims 9 to 16.

21. A communication device, characterized in that, include: Processor and interface circuitry; The interface circuit is used to receive code instructions and transmit them to the processor; The processor is configured to execute the code instructions to perform the method as described in any one of claims 1 to 8, or to execute the code instructions to perform the method as described in any one of claims 9 to 16.

22. A computer-readable storage medium for storing instructions that, when executed, cause the method of any one of claims 1 to 8 to be implemented, or when executed, cause the method of any one of claims 9 to 16 to be implemented.

23. A program product comprising at least one of a program and instructions, characterized in that, When at least one of the programs or instructions is executed by the communication device, it implements the steps of the method according to any one of claims 1 to 8, 9 to 16.

Images