WO2024082233A1 - 移动性限制实现方法和装置 - Google Patents

移动性限制实现方法和装置 Download PDF

Info

Publication number
WO2024082233A1
WO2024082233A1 PCT/CN2022/126524 CN2022126524W WO2024082233A1 WO 2024082233 A1 WO2024082233 A1 WO 2024082233A1 CN 2022126524 W CN2022126524 W CN 2022126524W WO 2024082233 A1 WO2024082233 A1 WO 2024082233A1
Authority
WO
WIPO (PCT)
Prior art keywords
target
terminal device
rplmn
erplmn
information
Prior art date
Application number
PCT/CN2022/126524
Other languages
English (en)
French (fr)
Inventor
毛玉欣
Original Assignee
北京小米移动软件有限公司
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 北京小米移动软件有限公司 filed Critical 北京小米移动软件有限公司
Priority to PCT/CN2022/126524 priority Critical patent/WO2024082233A1/zh
Priority to CN202280004349.5A priority patent/CN115997416A/zh
Publication of WO2024082233A1 publication Critical patent/WO2024082233A1/zh

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W48/00—Access restriction; Network selection; Access point selection
    • H04W48/02—Access restriction performed under specific conditions
    • H04W48/04—Access restriction performed under specific conditions based on user or terminal location or mobility data, e.g. moving direction, speed
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W84/00—Network topologies
    • H04W84/02—Hierarchically pre-organised networks, e.g. paging networks, cellular networks, WLAN [Wireless Local Area Network] or WLL [Wireless Local Loop]
    • H04W84/04—Large scale networks; Deep hierarchical networks
    • H04W84/06—Airborne or Satellite Networks

Definitions

  • the present disclosure relates to the field of communication technology, and in particular to a method and device for implementing mobility restriction.
  • the basis for determining whether to implement communication restrictions on the terminal device is that when all TAs (tracking areas) broadcast to the terminal device are located in a prohibited access domain, the terminal device is prohibited from accessing the network at the current location; if at least one is not located in the prohibited access domain, the terminal device is allowed to access the network at the current location; when all TAs broadcast to the terminal device are located in a non-permitted area, the terminal device is prohibited from communicating with the network at the current location; if at least one is not located in the non-permitted area, the terminal device is allowed to communicate with the network at the current location.
  • TAs tracking areas
  • the broadcast TA may include the TA corresponding to the RPLMN (registered public land mobile network) of the terminal device's current registered network and other eRPLMN (equivalent registered public land mobile network) corresponding TAs. If all broadcast TAs belonging to the RLPMN are located in a non-permitted area, according to the rules, the terminal device is prohibited from communicating with the RPLMN at the current location. However, if at least one broadcast TA belonging to other eRPLMN is located in a permitted area, according to the rules, the UE is allowed to communicate with the eRPLMN at the current location. According to the rules of mobility restriction defined in the relevant technology, the mobility restriction failure as described above will occur.
  • the disclosed embodiments provide a method and apparatus for implementing mobility restriction, which can determine a target TA where a terminal device is located, so that the terminal device and a core network device can implement mobility restriction on the terminal device according to the target TA.
  • an embodiment of the present disclosure provides a method for implementing mobility restriction, which is executed by a terminal device, and the method includes: obtaining a mapping relationship between a geographic area description GAD and a tracking area TA, and determining a target TA where the terminal device is located based on the mapping relationship and the current global satellite navigation system GNSS information of the terminal device.
  • the terminal device receives the mapping relationship between the geographical area description GAD and the tracking area TA sent by the core network device, and determines the target TA where the terminal device is located based on the mapping relationship and the current global satellite navigation system GNSS information of the terminal device.
  • the target TA where the terminal device is located can be determined, so that the terminal device and the core network device implement mobility restrictions on the terminal device according to the target TA.
  • an embodiment of the present disclosure provides another method for implementing mobility restriction, which is executed by a core network device, and the method includes: obtaining a mapping relationship between a geographic area description GAD and a tracking area TA; sending a mapping relationship between a geographic area description GAD and a tracking area TA to a terminal device, wherein the mapping relationship is used by the terminal device to determine the target TA in which it is located.
  • an embodiment of the present disclosure provides another method for implementing mobility restriction, which is executed by a core network device, and the method includes: determining a target TA where a terminal device is located, wherein the target TA is obtained from an access network device used by the terminal device to access the network, or the target TA is determined based on a mapping relationship between a geographic area description GAD and a tracking area TA, and current GNSS information of the terminal device.
  • an embodiment of the present disclosure provides a communication device, which has some or all of the functions of the terminal device in the method described in the first aspect above.
  • the functions of the communication device may have some or all of the functions in the embodiments of the present disclosure, or may have the functions of implementing any one of the embodiments of the present disclosure alone.
  • the functions may be implemented by hardware, or may be implemented by hardware executing corresponding software.
  • the hardware or software includes one or more units or modules corresponding to the above functions.
  • the structure of the communication device may include a transceiver module and a processing module, and the processing module is configured to support the communication device to perform the corresponding functions 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 computer programs and data necessary for the communication device.
  • the communication device includes: a transceiver module configured to obtain a mapping relationship between a geographic area description GAD and a tracking area TA; and a processing module configured to determine a target TA where the terminal device is located based on the mapping relationship and current GNSS information of the terminal device.
  • an embodiment of the present disclosure provides another communication device, which has some or all of the functions of the core network device in the method example described in the second aspect above.
  • the functions of the communication device may have some or all of the functions in the embodiments of the present disclosure, or may have the functions of implementing any one of the embodiments of the present disclosure alone.
  • 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.
  • the structure of the communication device may include a transceiver module and a processing module, and the processing module is configured to support the communication device to perform the corresponding functions 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 computer programs and data necessary for the communication device.
  • the communication device includes: a processing module configured to obtain a mapping relationship between a geographic area description GAD and a tracking area TA; a transceiver module configured to send a mapping relationship between a geographic area description GAD and a tracking area TA to a terminal device, wherein the mapping relationship is used by the terminal device to determine the target TA in which it is located.
  • the communication device includes: a processing module configured to determine a target TA where a terminal device is located, wherein the target TA is obtained from an access network device used by the terminal device to access the network, or the target TA is determined based on a mapping relationship between a geographic area description GAD and a tracking area TA, and current GNSS information of the terminal device.
  • a processing module configured to determine a target TA where a terminal device is located, wherein the target TA is obtained from an access network device used by the terminal device to access the network, or the target TA is determined based on a mapping relationship between a geographic area description GAD and a tracking area TA, and current GNSS information of the terminal device.
  • an embodiment of the present disclosure provides a communication device, which includes a processor.
  • the processor calls a computer program in a memory, the method described in the first aspect is executed.
  • an embodiment of the present disclosure provides a communication device, which includes a processor.
  • the processor calls a computer program in a memory, the method described in the second or third aspect is executed.
  • an embodiment of the present disclosure provides a communication device, which includes a processor and a memory, in which a computer program is stored; the processor executes the computer program stored in the memory so that the communication device executes the method described in the first aspect above.
  • an embodiment of the present disclosure provides a communication device, which includes a processor and a memory, in which a computer program is stored; the processor executes the computer program stored in the memory so that the communication device executes the method described in the second or third aspect above.
  • an embodiment of the present disclosure provides a communication device, which includes a processor and an interface circuit, wherein the interface circuit is used to receive code instructions and transmit them to the processor, and the processor is used to run the code instructions to enable the device to execute the method described in the first aspect above.
  • an embodiment of the present disclosure provides a communication device, which includes a processor and an interface circuit, wherein the interface circuit is used to receive code instructions and transmit them to the processor, and the processor is used to run the code instructions to enable the device to execute the method described in the second or third aspect above.
  • an embodiment of the present disclosure provides 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.
  • an embodiment of the present invention provides a computer-readable storage medium for storing instructions for the above-mentioned terminal device, and when the instructions are executed, the terminal device executes the method described in the first aspect.
  • an embodiment of the present invention provides a readable storage medium for storing instructions used by the above-mentioned core network device.
  • the core network device executes the method described in the second or third aspect above.
  • the present disclosure further provides a computer program product comprising a computer program, which, when executed on a computer, enables the computer to execute the method described in the first aspect above.
  • the present disclosure further provides a computer program product comprising a computer program, which, when executed on a computer, enables the computer to execute the method described in the second or third aspect above.
  • the present disclosure provides a chip system, which includes at least one processor and an interface, and is used to support a terminal device to implement the functions involved in the first aspect, for example, determining or processing at least one of the data and information involved in the above method.
  • the chip system also includes a memory, and the memory is used to store computer programs and data necessary for the terminal device.
  • the chip system can be composed of a chip, or it can include a chip and other discrete devices.
  • the present disclosure provides a chip system, which includes at least one processor and an interface, and is used to support a core network device to implement the functions involved in the second aspect or the third aspect, for example, to determine or process at least one of the data and information involved in the above method.
  • the chip system also includes a memory, and the memory is used to store computer programs and data necessary for the core network device.
  • the chip system can be composed of chips, and can also include chips and other discrete devices.
  • the present disclosure provides a computer program, which, when executed on a computer, enables the computer to execute the method described in the first aspect.
  • the present disclosure provides a computer program, which, when executed on a computer, enables the computer to execute the method described in the second or third aspect above.
  • FIG1 is an architecture diagram of a communication system provided by an embodiment of the present disclosure.
  • FIG2 is a flow chart of a method for implementing mobility restriction provided by an embodiment of the present disclosure
  • FIG. 3 is a flowchart of a core network device sending a mapping relationship between a GAD and a TA to a terminal device through an initial registration process provided by an embodiment of the present disclosure
  • FIG4 is a flow chart of a mobility management method provided by an embodiment of the present disclosure.
  • FIG5 is a flow chart of another mobility management method provided by an embodiment of the present disclosure.
  • FIG6 is a flow chart of another method for implementing mobility restriction provided in an embodiment of the present disclosure.
  • FIG7 is a flowchart of another method for implementing mobility restriction provided in an embodiment of the present disclosure.
  • FIG8 is a flow chart of another mobility management method provided by an embodiment of the present disclosure.
  • FIG9 is a flow chart of another mobility management method provided by an embodiment of the present disclosure.
  • FIG10 is a flow chart of another mobility management method provided by an embodiment of the present disclosure.
  • FIG11 is a structural diagram of a communication device provided in an embodiment of the present disclosure.
  • FIG12 is a structural diagram of another communication device provided in an embodiment of the present disclosure.
  • FIG. 13 is a schematic diagram of the structure of a chip provided in an embodiment of the present disclosure.
  • first, second, third, etc. may be used in the present disclosure to describe various information, such information should not be limited to these terms. These terms are only used to distinguish the same type of information from each other.
  • first information may also be referred to as the second information, and similarly, the second information may also be referred to as the first information.
  • word “if” used herein may be interpreted as "at the time of” or "when” or "in response to determining”.
  • the information including but not limited to user device information, user personal information, etc.
  • data including but not limited to data used for analysis, stored data, displayed data, etc.
  • signals involved in this disclosure are all authorized by the user or fully authorized by all parties, and the collection, use and processing of relevant data need to comply with relevant laws, regulations and standards of relevant countries and regions.
  • an embodiment of the present disclosure provides a communication system, including: core network equipment (for example, 5G core network (5th generation core, 5GC) 11, evolved packet core network (evolved packet core, EPC) 12), access network equipment (for example, evolved node B (gNB) 13, evolved node B (evolved node B, eNB) 14), and terminal equipment 15.
  • core network equipment for example, 5G core network (5th generation core, 5GC) 11, evolved packet core network (evolved packet core, EPC) 12
  • access network equipment for example, evolved node B (gNB) 13, evolved node B (evolved node B, eNB) 14
  • terminal equipment for example, 5G core network (5th generation core, 5GC) 11, evolved packet core network (evolved packet core, EPC) 12
  • gNB evolved node B
  • evolved node B evolved node B
  • the core network device 11 refers to the device in the core network (CN) that provides service support for the terminal device.
  • some core network devices include: access and mobility management function (AMF) entity, session management function (SMF) entity, user plane function (UPF) entity, etc., which are not listed here one by one.
  • the AMF entity can be responsible for the access management and mobility management of the terminal device.
  • the SMF entity can be responsible for session management, such as user session establishment.
  • the UPF entity can be a functional entity of the user plane, mainly responsible for connecting to the external network.
  • the entity in the present disclosure can also be referred to as a network element or a functional entity.
  • the AMF entity can also be referred to as an AMF network element or an AMF functional entity
  • the SMF entity can also be referred to as an SMF network element or an SMF functional entity.
  • the access network device 13 refers to a radio access network (RAN) node (or device) that connects the terminal device to the wireless network, which can also be called a base station.
  • RAN nodes 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 NodeB, or homenode B, HNB), base band unit (BBU), or wireless fidelity (Wi-Fi) access point (AP), etc.
  • the access network device may include a centralized unit (CU), a distributed unit (DU), or a RAN device including a CU and a DU.
  • the RAN equipment including CU and DU splits the protocol layer from the perspective of logical functions. The functions of some protocol layers are centrally controlled by CU, and the functions of the remaining part or all of the protocol layers are distributed in DU, which is centrally controlled by CU.
  • the terminal device 15 also known as user equipment (UE), mobile station (MS), mobile terminal (MT), etc., refers to a device that provides voice and/or data connectivity to users.
  • UE user equipment
  • MS mobile station
  • MT mobile terminal
  • some examples of terminal devices include: mobile phones, tablet computers, 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, wireless terminals in smart homes, etc.
  • MID mobile internet devices
  • VR virtual reality
  • AR augmented reality
  • both the access network device 13 and the access network device 14 can communicate with multiple terminal devices 15.
  • the terminal device communicating with the access network device 13 and the terminal device communicating with the access network device 14 can be the same or different.
  • the terminal device 15 shown in FIG2 can communicate with the access network device 13 and the access network device 14 at the same time, but this only shows one possible scenario. In some scenarios, the terminal device may only communicate with the access network device 13 or the access network device 14, and the present disclosure does not limit this.
  • FIG1 is only a simplified schematic diagram for ease of understanding, and the communication system may also include other access network devices, terminal devices, or core network devices, which are not drawn in FIG1 .
  • the communication system described in the embodiment of the present disclosure is for the purpose of more clearly illustrating the technical solution of the embodiment of the present disclosure, and does not constitute a limitation on the technical solution provided by the embodiment of the present disclosure.
  • a person skilled in the art can know that with the evolution of the system architecture and the emergence of new business scenarios, the technical solution provided by the embodiment of the present disclosure is also applicable to similar technical problems.
  • used to indicate may include being used to indicate directly or indirectly.
  • the information may include that the information directly indicates A or indirectly indicates A, but it does not mean that the information must carry A.
  • the information indicated by the information is called the information to be indicated.
  • the information to be indicated 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 the index of the information to be indicated.
  • the information to be indicated can also be indirectly indicated by indicating other information, wherein there is an association between the other information and the information to be indicated. It is also possible to indicate only a part of the information to be indicated, while the other parts of the information to be indicated are known or agreed in advance.
  • the indication of specific information can also be achieved by means of the arrangement order of each information agreed in advance (such as specified by the protocol), thereby reducing the indication overhead to a certain extent.
  • the information to be indicated can be sent as a whole or divided into multiple sub-information and sent separately, and the sending period and/or sending time of these sub-information can be the same or different.
  • the specific sending method is not limited in this disclosure. Among them, the sending period and/or sending time of these sub-information can be pre-defined, for example, pre-defined according to a protocol.
  • the first, second and various numerical numbers are only used for the convenience of description and are not used to limit the scope of the embodiments of the present disclosure. For example, to distinguish different TAs, etc.
  • the terminal device has GNSS (Global Navigation Satellite System) capability.
  • GNSS Global Navigation Satellite System
  • the “protocol” involved in the embodiments of the present disclosure may refer to a standard protocol in the communication field, for example, it may include an LTE protocol, a NR protocol, a WLAN protocol, and related protocols in other communication systems, which is not limited in the present disclosure.
  • the embodiments of the present disclosure list multiple implementation methods to clearly illustrate the technical solutions of the embodiments of the present disclosure.
  • the multiple embodiments provided by the embodiments of the present disclosure can be executed separately, or can be executed together with the methods of other embodiments of the embodiments of the present disclosure, or can be executed together with some methods in other related technologies separately or in combination; the embodiments of the present disclosure do not limit this.
  • the present disclosure provides a method and apparatus for implementing mobility restriction in an embodiment, wherein a terminal device receives a mapping relationship between a GAD (Geographical Area Description) and a TA sent by a core network device, and the target TA of the terminal device can be determined based on the mapping relationship and the current GNSS information of the terminal device.
  • the target TA of the terminal device can be determined, so that the terminal device and the core network device can implement mobility restriction on the terminal device according to the target TA.
  • FIG. 2 is a flow chart of a method for implementing mobility restriction provided in an embodiment of the present disclosure.
  • the method may include but is not limited to the following steps:
  • the core network device obtains the mapping relationship between GAD and TA.
  • the core network device may be, for example, AMF (access and mobility management function), which obtains the mapping relationship between GAD and TA.
  • AMF access and mobility management function
  • the core network may obtain the mapping relationship between GAD and TA by configuring itself, or may obtain it based on a protocol agreement, or may obtain it based on the configuration of an access network device, etc.
  • the embodiments of the present disclosure do not impose specific restrictions on this.
  • the mapping relationship between GAD and TA may include the mapping relationship between GAD and TA of all subscribed PLMN (public land mobile network).
  • the core network device when obtaining the mapping relationship between GAD and TA, can obtain the current GNSS information of the terminal device, such as the current location information of the terminal device, to determine the corresponding target GAD based on the GNSS information of the terminal device. Furthermore, the target TA of the terminal device can be determined based on the target GAD and the mapping relationship, or the target TA of the terminal device can be determined based on the TA representing the location of the terminal device reported by the access network device and the mapping relationship.
  • the core network device 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.
  • the core network device sends the mapping relationship between GAD and TA to the terminal device.
  • the core network device may send the mapping relationship between GAD and TA to the terminal device after acquiring the mapping relationship between GAD and TA.
  • the core network device can send the mapping relationship between GAD and TA to the terminal device at any stage when the terminal device accesses the network.
  • the mapping relationship between GAD and TA can be sent to the terminal device during the initial registration process, the registration update process, the UCU (UE Configuration Update, terminal device configuration update) process, the service request process, etc., and the present disclosure does not limit this.
  • the core network device can send the mapping relationship between GAD and TA to the terminal device through the initial registration process.
  • the interaction process is as follows:
  • the terminal device obtains the current location (GNSS information) and determines that the terminal device can access the selected PLMN at the current location based on the prohibited access area information in the saved mobility restriction information.
  • the terminal device sends a registration request to the core network device (AMF).
  • AMF core network device
  • the terminal device can send a registration request to the core network device through the base station (NR (LEO)).
  • NR base station
  • AMF processes the registration request of the terminal device, registers the access of the terminal device, and formulates RA (Registration Area), mobility restriction information, etc.
  • the mobility restriction information may include forbidden access area (forbidden area) information, service area restriction (non-allowed area or allowed area) information.
  • Registration area among which, forbidden area, non-allowed area, and allowed area can be composed of a group of TAI (tracking area identity).
  • AMF obtains the mapping relationship between GAD and TA of the TA belonging to the PLMN from the network management center (NMC).
  • NMC network management center
  • AMF sends a registration response to the terminal device and sends 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.
  • the terminal device updates the saved mobility restriction information [forbidden area, non-allowed area or allowed area] according to the received information, and saves the mapping relationship between GAD and TA.
  • the terminal obtains the mapping relationship between GAD and TA.
  • the core network device can also send the mapping relationship between GAD and TA to the terminal device through a registration update process, a UCU process, or a service request process, and the embodiments of the present disclosure do not impose specific restrictions on this.
  • the terminal device can obtain and save the mapping relationship between GAD and TA.
  • the saved mapping relationship can be updated.
  • the terminal device is turned off, the saved mapping relationship between GAD and TA will not be deleted.
  • the terminal device deletes the USIM (Universal Subscriber Identity Module), the saved mapping relationship between GAD and TA is also deleted.
  • USIM Universal Subscriber Identity Module
  • the terminal device may further execute S23.
  • the terminal device determines the target TA where the terminal device is located according to the mapping relationship and the current GNSS information of the terminal device.
  • the terminal device may determine the target TA where the terminal device is located based on the mapping relationship and the current GNSS information of the terminal device.
  • 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.
  • the terminal device may determine the target GAD corresponding to the current GNSS information based on the current GNSS information of the terminal device, and further determine the target TA where the terminal device is located based on the target GAD and the mapping relationship.
  • the terminal device receives the mapping relationship between GAD and TA sent by the core network device; according to the mapping relationship and the current global satellite navigation system GNSS information of the terminal device, the target TA of the terminal device is determined.
  • the target TA of the terminal device can be determined, so that the terminal device and the core network device implement mobility restrictions on the terminal device according to the target TA.
  • FIG. 4 is a flow chart of a mobility management method provided by an embodiment of the present disclosure.
  • the method is executed by a terminal device, and the method may include but is not limited to the following steps:
  • the terminal device determines whether to access the PLMN according to the first target TA and the prohibited access domain information, wherein the target TA is the first target TA corresponding to the PLMN.
  • the method for the terminal device to determine the target TA where the terminal device is located can refer to the relevant description in the above embodiments, which will not be repeated here.
  • the target TA is the first target TA corresponding to the PLMN.
  • the method for the terminal device to determine the first target TA corresponding to the PLMN where the terminal device is located in the embodiment of the present disclosure is the same as the method for the terminal device to determine the target TA where the terminal device is located in the above embodiment. Please refer to the relevant description in the above embodiment, and no further description is given here. Of course, it should be understood that the terminal device can also determine the TA where it is located by other methods.
  • the terminal device may determine whether to access the PLMN based on the first target TA and the prohibited access domain information.
  • the terminal device determines whether to access the PLMN according to the first target TA and the prohibited access domain information, including:
  • the prohibited access domain information is used to indicate the prohibited access domain of the PLMN.
  • the prohibited access domain information is used to indicate the prohibited access domain of the PLMN.
  • the terminal device may determine whether to access the PLMN based on the first target TA and the prohibited access domain information, wherein when 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.
  • the terminal device may determine whether to access the PLMN based on the first target TA and the prohibited access domain information, wherein when 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 at the first target TA.
  • the terminal device may choose to access the PLMN in the first target TA, or may also choose not to access the PLMN in the first target TA.
  • S41 can be implemented alone or in combination with any other step in the embodiment of the present disclosure, for example, in combination with S21 to S23 in the embodiment of the present disclosure, and the embodiment of the present disclosure is not limited to this.
  • the terminal device determines whether to access the PLMN according to the first target TA and the prohibited access domain information, wherein the target TA is the first target TA corresponding to the PLMN.
  • the target TA is the first target TA corresponding to the PLMN.
  • FIG. 5 is a flow chart of another mobility management method provided by an embodiment of the present disclosure.
  • the method is executed by a terminal device, and the method may include but is not limited to the following steps:
  • the terminal device determines whether to communicate with the registered public land mobile network RPLMN according to the second target TA and service domain restriction information, wherein the target TA is the second target TA corresponding to the RPLMN.
  • the method for the terminal device to determine the target TA where the terminal device is located can refer to the relevant description in the above embodiments, which will not be repeated here.
  • the target TA is the second target TA corresponding to RPLMN (registered PLMN, registered public land mobile network).
  • the method for the terminal device to determine the second target TA corresponding to the RPLMN where the terminal device is located in the embodiment of the present disclosure is the same as the method for the terminal device to determine the target TA where the terminal device is located in the above embodiment. Please refer to the relevant description in the above embodiment and will not be repeated here.
  • the terminal device may determine whether to communicate with the registered public land mobile network RPLMN according to the second target TA and the service domain restriction information.
  • the terminal device determines whether to communicate with the RPLMN according to the second target TA and the service domain restriction information, including:
  • the service domain restriction information is used to indicate the allowed area of the RPLMN.
  • the service domain restriction information is used to indicate a non-allowed area of the RPLMN or to indicate an allowed area of the RPLMN.
  • the terminal device can determine whether to communicate with the RPLMN based on the second target TA and the service domain restriction, wherein when 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 the RPLMN is prohibited.
  • the terminal device can determine whether to communicate with the RPLMN based on the second target TA and the service domain restriction, wherein, when the second target TA is included in the non-permitted area of the RPLMN, it is determined that the second target TA is prohibited from communicating with any eRPLMN (equivalent registered PLMN).
  • the terminal device may determine whether to communicate with the RPLMN based on the second target TA and service domain restrictions, wherein when the second target TA is included in the allowed area of the RPLMN, it is determined that communication with the RPLMN is allowed in the second target TA.
  • the terminal device may initiate a communication request to communicate with the RPLMN, or may not initiate a communication request to communicate with the RPLMN.
  • the service area restriction information may include an allowed area or a non-allowed area (eg, specified using a tracking area identifier).
  • the allowed area the terminal device is allowed to initiate communication with the network in this area
  • non-permitted area the terminal device is in a service-restricted state in this area.
  • the terminal device is not allowed to initiate service requests to the network, or any connection requests for user plane data or control plane data.
  • the tracking area identifier may be used to specify the allowed area and the non-allowed area.
  • the allowed area may include one or more (eg, up to 16) TAs, or all TAs may be placed in the allowed area.
  • the core network equipment can distribute the service area restriction information to the terminal device according to the terminal device subscription, and can be updated as needed. It can be provided to the terminal device through the registration procedure or the UCU procedure. When provided to the terminal device, it can only contain the allowed area or the non-allowed area, but not both areas.
  • the access network device broadcasts multiple TAIs to the terminal device, during the process of the terminal device accessing the network, the access network device reports the broadcasted multiple TAIs to the core network device.
  • the core network device will execute the following service area restriction rules:
  • both the terminal device and the AMF consider that the terminal device is located in the non-allowed area.
  • the terminal device and the AMF both consider that the terminal device is located in the allowed area.
  • the satellite access broadcasts TAIs of multiple available PLMNs to the terminal device.
  • the terminal device accesses the network to perform registration
  • the satellite access device reports the broadcasted multiple TAIs to the core network, and the core network assigns a registration area for it.
  • the registration area also contains at least one equivalent registered PLMN (eRPLMN), that is, the registration area carries a TAI list including TAIs from RPLMN and equivalent RPLMNs.
  • the core network also allocates an allowed area for the terminal device, and the allowed area also includes the TAI of the RPLMN and the TAI of the eRPLMN.
  • All broadcast TAIs belonging to RPLMN in the received broadcast TAIs are not in the allowed area.
  • the allowed area includes at least one broadcast TAI belonging to an eRPLMN.
  • the terminal device at the current location is not allowed to communicate with the network, while according to 2, the terminal device at the current location can communicate using eRPLMN. In this case, it is invalid to implement service area restrictions on the terminal device at the current location.
  • the terminal device can determine whether to communicate with the RPLMN based on the second target TA and the service domain restriction information, wherein, when the second target TA is included in the non-permitted area of the RPLMN, it is determined that the second target TA is prohibited from communicating with any eRPLMN (equivalent registered PLMN), which can avoid the failure of the service domain restriction.
  • eRPLMN Equivalent registered PLMN
  • the terminal device determines 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.
  • the target TA is the third target TA corresponding to the eRPLMN.
  • the method for the terminal device to determine the third target TA corresponding to the eRPLMN where the terminal device is located in the embodiment of the present disclosure is the same as the method for the terminal device to determine the target TA where the terminal device is located in the above-mentioned embodiment. Please refer to the relevant description in the above-mentioned embodiment and it will not be repeated here.
  • the terminal device when the second target TA is included in the allowed area of an RPLMN, the terminal device can determine whether to communicate with the eRPLMN based on the third target TA and the service domain restriction information.
  • the terminal device determines whether to communicate with the eRPLMN according to the third target TA and the service domain restriction information, including:
  • the service domain restriction information is used to indicate a non-allowed area of the eRPLMN or to indicate an allowed area of the eRPLMN.
  • the terminal device may determine whether to communicate with the eRPLMN based on the third target TA and service domain restriction information, wherein, when the third target TA is included in the allowed area of the eRPLMN, it is determined that communication with the eRPLMN is allowed in the third target TA.
  • the terminal device may initiate a communication request to communicate with the eRPLMN, or may not initiate a communication request to communicate with the eRPLMN.
  • the terminal device may determine whether to communicate with the eRPLMN based on the third target TA and service domain restriction information, wherein, when the third target TA is included in a non-permitted area of the eRPLMN, it is determined that communication with the eRPLMN in the third target TA is prohibited.
  • the terminal device when the second target TA is included in the allowed area of an RPLMN, 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 the service domain restriction information.
  • the third target TA when the third target TA is included in the allowed area of the eRPLMN, it is determined that communication with the eRPLMN is allowed in the third target TA, and when the third target TA is included in the non-allowed area of the eRPLMN, it is determined that communication with the eRPLMN is prohibited in the third target TA. In this way, the failure of the service domain restriction can be avoided.
  • S51 can be implemented alone or in combination with any other steps in the embodiments of the present disclosure, for example, in combination with S21 to S23 and/or S31 and/or S41 in the embodiments of the present disclosure, and the embodiments of the present disclosure are not limited to this.
  • the terminal device determines whether to communicate with the registered public land mobile network RPLMN according to the second target TA and the service domain restriction information, wherein the target TA is the second target TA corresponding to the RPLMN.
  • the service domain restriction information can be accurately controlled to avoid the invalidation of the service domain restriction information.
  • FIG. 6 is a flow chart of another method for implementing mobility restriction provided in an embodiment of the present disclosure.
  • the method may include but is not limited to the following steps:
  • the core network device determines 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 GAD and TA and the current GNSS information of the terminal device.
  • the relevant description of how the core network device obtains the mapping relationship between GAD and TA can be found in the relevant description in the above embodiments, which will not be repeated here.
  • the core network device can further obtain the current GNSS information of the terminal device when determining the mapping relationship between GAD and TA, and further determine the target TA where the terminal device is located based on the mapping relationship and the current GNSS information of the terminal device, or determine the target TA based on the TA representing the current location of the terminal device reported by the access network device and the mapping relationship.
  • the method for the core network device to obtain the current GNSS information of the terminal device can be determined based on the protocol agreement, or can also be determined based on the access network device configuration, etc.
  • 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.
  • 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 further determine the target TA where the terminal device is located based on the target GAD and the mapping relationship.
  • 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 at any stage when the current GNSS information of the terminal device can be determined.
  • 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.
  • the core network may also determine the target TA where the terminal device is located according to the mapping relationship between the GAD and the TA and the current GNSS information of the terminal device.
  • the core network may also determine the target TA where the terminal device is located based on the mapping relationship between the GAD and the TA and the current GNSS information of the terminal device.
  • S61 can be implemented alone or in combination with any other steps in the embodiments of the present disclosure, for example, in combination with S21 to S23 and/or S41 and/or S51 in the embodiments of the present disclosure, and the embodiments of the present disclosure are not limited to this.
  • 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.
  • the target TA where the terminal device is located can be determined, so that the terminal device and the core network device implement mobility restrictions on the terminal device according to the target TA.
  • FIG. 7 is a flow chart of another method for implementing mobility restriction provided in an embodiment of the present disclosure.
  • the method may include but is not limited to the following steps:
  • the terminal device reports the GNSS information of the terminal device to the core network device.
  • the terminal device reports the GNSS information of the terminal device to the core network device, wherein the terminal device may report the GNSS information of the terminal device to the core network device during the positioning process.
  • the core network device determines the target TA where the terminal device is located according to the mapping relationship between GAD and TA and the current GNSS information of the terminal device.
  • S71 and S72 can be implemented separately or in combination with any other steps in the embodiments of the present disclosure, for example, in combination with S21 to S23 and/or S41 and/or S51 and/or S61 in the embodiments of the present disclosure, and the embodiments of the present disclosure are not limited to this.
  • the core network device receives the GNSS information of the terminal device reported by the terminal device, and determines the target TA where the terminal device is located according to the mapping relationship between GAD and TA and the current GNSS information of the terminal device.
  • the target TA where the terminal device is located can be determined, so that the terminal device and the core network device implement mobility restrictions on the terminal device according to the target TA.
  • FIG. 8 is a flow chart of another mobility management method provided by an embodiment of the present disclosure.
  • the method is performed by a core network device, and the method may include but is not limited to the following steps:
  • the core network device determines whether to allow the terminal device to access the PLMN in the first target TA according to the first target TA and the prohibited access domain information, wherein the target TA is the first target TA corresponding to the PLMN.
  • the method for the core network device to determine the target TA where the terminal device is located can refer to the relevant description in the above embodiments and will not be repeated here.
  • the target TA is the first target TA corresponding to the PLMN.
  • the method by which the core network device in the embodiment of the present disclosure determines the first target TA corresponding to the PLMN where the terminal device is located is the same as the method by which the core network device in the above embodiment determines the target TA where the terminal device is located. Please refer to the relevant description in the above embodiment and will not be repeated here.
  • the core network device may determine whether to allow the terminal device to access the PLMN in the first target TA according to the first target TA and the prohibited access domain information.
  • the core network device determines whether to allow the terminal device to access the PLMN in the first target TA according to the first target TA and the prohibited access domain information, including:
  • the terminal device In response to the first target TA not being included in the prohibited access domain of the PLMN, it is determined to allow the terminal device to access the PLMN at the first target TA, wherein the prohibited access domain information is used to indicate the prohibited access domain of the PLMN.
  • the prohibited access domain information is used to indicate the prohibited access domain of the PLMN.
  • the core network device can determine whether to allow the terminal device to access the PLMN in the first target TA based on the first target TA and the prohibited access domain information, wherein when the first target TA is included in the prohibited access domain of the PLMN, it is determined that the terminal device is prohibited from accessing the PLMN in the first target TA.
  • the core network device can determine whether to allow the terminal device to access the PLMN in the first target TA based on the first target TA and the prohibited access domain information, wherein, when 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 in the first target TA.
  • S81 can be implemented alone or in combination with any other steps in the embodiments of the present disclosure, for example, in combination with S21 to S23 and/or S41 and/or S51 and/or S61 and/or S71 and S72 in the embodiments of the present disclosure, and the embodiments of the present disclosure are not limited to this.
  • the terminal device determines whether to access the PLMN according to the first target TA and the prohibited access domain information, wherein the target TA is the first target TA corresponding to the PLMN.
  • the target TA is the first target TA corresponding to the PLMN.
  • FIG. 9 is a flow chart of another mobility management method provided by an embodiment of the present disclosure.
  • the method is performed by a core network device, and the method may include but is not limited to the following steps:
  • the core network device determines whether to allow the terminal device to communicate with the RPLMN in the second target TA according to the second target TA and the service domain restriction information, wherein the target TA is the second target TA corresponding to the RPLMN.
  • the method for the core network device to determine the target TA where the terminal device is located can refer to the relevant description in the above embodiments and will not be repeated here.
  • the target TA is the second target TA corresponding to the RPLMN.
  • the method by which the core network device in the embodiment of the present disclosure determines the second target TA corresponding to the RPLMN where the terminal device is located is the same as the method by which the core network device in the above embodiment determines the target TA where the terminal device is located. Please refer to the relevant description in the above embodiment and will not be repeated here.
  • the core network device may determine whether to allow the terminal device to communicate with the RPLMN in the second target TA according to the second target TA and the service domain restriction information.
  • the core network device determines whether to allow the terminal device to communicate with the RPLMN in the second target TA according to the second target TA and the service domain restriction information, including:
  • the terminal device 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.
  • the service domain restriction information is used to indicate a non-allowed area of the RPLMN or to indicate an allowed area of the RPLMN.
  • the core network device can determine 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, wherein when the second target TA is included in the non-permitted area of the RPLMN, it is determined that the terminal device is prohibited from communicating with the RPLMN in the second target TA.
  • the core network device can determine 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, wherein, when the second target TA is included in the non-permitted area of the RPLMN, it is determined that the terminal device is prohibited from communicating with any eRPLMN in the second target TA.
  • the core network device can determine 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, wherein when 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 in the second target TA.
  • the service area restriction information may include an allowed area or a non-allowed area (eg, specified using a tracking area identifier).
  • the allowed area the terminal device is allowed to initiate communication with the network in this area
  • non-permitted area the terminal device is in a service-restricted state in this area.
  • the terminal device is not allowed to initiate service requests to the network, or any connection requests for user plane data or control plane data.
  • the tracking area identifier may be used to specify the allowed area and the non-allowed area.
  • the allowed area may include one or more (eg, up to 16) TAs, or all TAs may be placed in the allowed area.
  • the core network equipment can distribute the service area restriction information to the terminal device according to the terminal device subscription, and can be updated as needed. It can be provided to the terminal device through the registration procedure or the UCU procedure. When provided to the terminal device, it can only contain the allowed area or the non-allowed area, but not both areas.
  • the access network device broadcasts multiple TAIs to the terminal device, during the process of the terminal device accessing the network, the access network device reports the broadcasted multiple TAIs to the core network device.
  • the core network device will execute the following service area restriction rules:
  • both the terminal device and the AMF consider that the terminal device is located in the non-allowed area.
  • the terminal device and the AMF both consider that the terminal device is located in the allowed area.
  • the satellite access broadcasts TAIs of multiple available PLMNs to the terminal device.
  • the terminal device accesses the network to perform registration
  • the satellite access device reports the broadcasted multiple TAIs to the core network, and the core network assigns a registration area for it.
  • the registration area also contains at least one equivalent registered PLMN (eRPLMN), that is, the registration area carries a TAI list including TAIs from RPLMN and equivalent RPLMNs.
  • the core network also allocates an allowed area for the terminal device, and the allowed area also includes the TAI of the RPLMN and the TAI of the eRPLMN.
  • All broadcast TAIs belonging to RPLMN in the received broadcast TAIs are not in the allowed area.
  • the allowed area includes at least one broadcast TAI belonging to an eRPLMN.
  • the terminal device at the current location is not allowed to communicate with the network, while according to 2, the terminal device at the current location can communicate using eRPLMN. In this case, it is invalid to implement service area restrictions on the terminal device at the current location.
  • the core network device can determine 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.
  • the second target TA is included in the non-permitted area of the RPLMN, it is determined that the terminal device is prohibited from communicating with any eRPLMN in the second target TA, which can avoid the failure of the service domain restriction.
  • 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.
  • the target TA is the third target TA corresponding to the eRPLMN.
  • the method by which the core network device in the embodiment of the present disclosure determines the third target TA corresponding to the eRPLMN where the terminal device is located is the same as the method by which the core network device in the above embodiment determines the target TA where the terminal device is located. Please refer to the relevant description in the above embodiment and will not be repeated here.
  • 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.
  • the core network device determines whether to allow the terminal device to communicate with the eRPLMN in the third target TA according to the third target TA and the service domain restriction information, including:
  • the terminal device In response to the third target TA being included in the allowed area of the eRPLMN, determining 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
  • the terminal device In response to the third target TA being 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.
  • the service domain restriction information is used to indicate a non-allowed area of the eRPLMN or to indicate an allowed area of the eRPLMN.
  • 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, wherein when 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.
  • 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, wherein, when the third target TA is included in the non-permitted area of the eRPLMN, it is determined that the terminal device is prohibited from communicating with the eRPLMN in the third target TA.
  • the core network device can determine the third target TA corresponding to the eRPLMN where the terminal device is located, and determine, based on the third target TA and the service domain restriction information, that the terminal device is allowed to communicate with the eRPLMN in the third target TA.
  • the third target TA when 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, and when 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. In this way, the failure of the service domain restriction can be avoided.
  • an embodiment of the present disclosure provides a method for a core network device to perform mobility management.
  • the terminal device After the terminal device accesses the PLMN, the terminal device needs to initiate a service request to restore the user plane connection.
  • the terminal device obtains the current location information (GNSS information) and determines the target TA where the terminal device is currently located based on the mapping relationship between GAD and TA.
  • GNSS information the current location information
  • the terminal device checks whether the target TA is included in the non-permitted area of the RPLMN. At this time, according to the rules, the terminal device will not initiate the service request process in the current target TA, but a malicious terminal device may initiate the above process.
  • the terminal device initiates a service request process at the current target TA.
  • AMF obtains the target TA where the terminal device is located, and determines that the target TA is included in the non-permitted area of RPLMN. AMF needs to reject the service request of the terminal device. If the terminal device uses other eRPLMNs to access, if the current target TA of the terminal device has not changed, the terminal device is still in the non-permitted area of RPLMN. At this time, the terminal device uses other eRPLMNs to access, and AMF still does not allow the service request process to be initiated.
  • AMF returns a service rejection message to the terminal device.
  • the service rejection message may state that the rejection reason is that the terminal device is in a non-permitted area and is not allowed to initiate the service request process.
  • S91 can be implemented alone or in combination with any other steps in the embodiments of the present disclosure, for example, 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 the present disclosure, and the embodiments of the present disclosure are not limited to this.
  • the core network device determines whether to allow the terminal device to communicate with the RPLMN in the second target TA according to the second target TA and the service domain restriction information, wherein the target TA is the second target TA corresponding to the RPLMN.
  • the service domain restriction information can be accurately controlled to avoid the invalidation of the service domain restriction information.
  • the methods provided by the embodiments of the present disclosure are introduced from the perspectives of the terminal device, the core network device, and the interaction between the terminal device and the core network device.
  • the communication device 1 shown in Figure 11 may include a transceiver module 11 and a processing module 12.
  • the transceiver module may include a sending module and/or a receiving module, the sending module is used to implement a sending function, the receiving module is used to implement a receiving function, and the transceiver module may implement a sending function and/or a receiving function.
  • the communication device 1 may be a terminal device, or a device in a terminal device, or a device that can be used in conjunction with a terminal device.
  • the communication device 1 may be a core network device, or a device in a core network device, or a device that can be used in conjunction with a core network device.
  • the communication device 1 is a terminal device:
  • the device includes: a transceiver module 11 and a processing module 12.
  • the transceiver module 11 is configured to obtain a mapping relationship between the GAD and the TA.
  • the processing module 12 is configured to determine the target TA where the terminal device is located according to the mapping relationship and the current GNSS information of the terminal device.
  • the processing module 12 is further configured to determine the corresponding target GAD according to the current GNSS information of the terminal device; and determine the target TA where the terminal device is located according to the target GAD and the mapping relationship.
  • the processing module 12 is further configured to determine whether to access a public land mobile network PLMN according to the first target TA and the prohibited access domain information, wherein the target TA is the first target TA corresponding to the PLMN.
  • the processing module 12 is further configured to determine that access to the PLMN is prohibited at 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 allowed at 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.
  • the processing module 12 is further configured to determine whether to communicate with the registered public land mobile network RPLMN according to the second target TA and the service domain restriction information, wherein the target TA is the second target TA corresponding to the RPLMN.
  • the processing module 12 is further configured to determine that, in response to the second target TA being included in the non-permitted area of the RPLMN, communication between the second target TA and the RPLMN is prohibited, 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 the non-permitted area of the RPLMN, determine that communication between the second target TA and any equivalent registered public land mobile network eRPLMN is prohibited, 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 the allowed area of the RPLMN, determine that communication between the second target TA and the RPLMN is allowed, wherein the service domain restriction information is used to indicate the allowed area of the RPLMN.
  • the processing module 12 is further configured to determine whether to communicate with the eRPLMN based on the third target TA and service domain restriction information when the second target TA is included in the allowed area of an RPLMN, wherein the target TA is the third target TA corresponding to the eRPLMN.
  • the processing module 12 is further configured to determine that communication with the eRPLMN is allowed in the third target TA in response to the third target TA being included in the allowed area of the eRPLMN, wherein the service domain restriction information is used to indicate the allowed area of the eRPLMN; or to determine that communication with the eRPLMN is prohibited in the third target TA in response to the third target TA being included in the non-permitted area of the eRPLMN, wherein the service domain restriction information is used to indicate the non-permitted area of the eRPLMN.
  • the transceiver module 11 is further configured to report the GNSS information of the terminal device to the core network device.
  • Communication device 1 is a core network device:
  • the device includes: a transceiver module 11 and a processing module 12.
  • the processing module 12 is configured to obtain a mapping relationship between GAD and TA;
  • the transceiver module 11 is configured to send a mapping relationship between GAD and TA to the terminal device, wherein the mapping relationship is used for the terminal device to determine the target TA in which it is located.
  • Communication device 1 is a core network device:
  • the device includes: a transceiver module 11 and a processing module 12.
  • the processing module 12 is configured to determine 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 GAD and TA, and the current GNSS information of the terminal device.
  • the transceiver module 11 is configured to receive current GNSS information of the terminal device reported by the terminal device.
  • the processing module 12 is further configured to determine the corresponding target GAD according to the current GNSS information of the terminal device; and determine the target TA where the terminal device is located according to the target GAD and the mapping relationship.
  • the processing module 12 is further configured to determine whether to allow the terminal device to access the PLMN in the first target TA according to the first target TA and the prohibited access domain information, wherein the target TA is the first target TA corresponding to the PLMN.
  • the processing module 12 is further configured to determine, in response to the first target TA being included in the prohibited access domain of the PLMN, that the terminal device is prohibited from accessing the PLMN at the first target TA, wherein the prohibited access domain information is used to indicate the prohibited access domain of the PLMN; or to determine, in response to the first target TA not being included in the prohibited access domain of the PLMN, that the terminal device is allowed to access the PLMN at the first target TA, wherein the prohibited access domain information is used to indicate the prohibited access domain of the PLMN.
  • the processing module 12 is further configured to determine whether to allow the terminal device to communicate with the RPLMN in the second target TA according to the second target TA and the service domain restriction information, wherein the target TA is the second target TA corresponding to the RPLMN.
  • the processing module 12 is further configured to determine, in response to the second target TA being included in the non-permitted area of the RPLMN, prohibiting the terminal device from communicating with the RPLMN in the second target TA, 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 the non-permitted area of the RPLMN, prohibiting 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-permitted area of the RPLMN; or in response to the second target TA being included in the allowed area of the RPLMN, determining to allow the terminal device 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.
  • the processing module 12 is further configured to determine whether the terminal device is allowed to communicate with the eRPLMN in the third target TA based on the third target TA and the service domain restriction information when the second target TA is included in the allowed area of the RPLMN, wherein the target TA is the third target TA corresponding to the eRPLMN.
  • the processing module 12 is further configured to, in response to the third target TA being included in the allowed area of the eRPLMN, determine 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, in response to the third target TA being included in the non-allowed area of the eRPLMN, determine 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.
  • the communication device 1 provided in the above embodiments of the present 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, which will not be described in detail here.
  • FIG 12 is a schematic diagram of the structure of another communication device 1000 provided in an embodiment of the present disclosure.
  • the communication device 1000 can be a terminal device, or a core network device, or a chip, a chip system, or a processor that supports the terminal device to implement the above method, or a chip, a chip system, or a processor that supports the core network device to implement the above method.
  • the communication device 1000 can be used to implement the method described in the above method embodiment, and the details can be referred to the description in the above method embodiment.
  • the communication device 1000 may include one or more processors 1001.
  • the processor 1001 may be a general-purpose processor or a dedicated processor, etc. For example, it may be a baseband processor or a central processing unit.
  • the baseband processor may be used to process the communication protocol and the communication data
  • the central processing unit may be used to control the communication device (such as a core network device, a baseband chip, a terminal device, a terminal device chip, a DU or a CU, etc.), execute a computer program, and process the data of the computer program.
  • the communication device 1000 may further include one or more memories 1002, on which a computer program 1004 may be stored, and the memory 1002 executes the computer program 1004 so that the communication device 1000 executes the method described in the above method embodiment.
  • data may also be stored in the memory 1002.
  • the communication device 1000 and the memory 1002 may be provided separately or integrated together.
  • 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, a transceiver, or a transceiver circuit, etc., for implementing a transceiver function.
  • the transceiver 1005 may include a receiver and a transmitter, the receiver may be referred to as a receiver or a receiving circuit, etc., for implementing a receiving function; the transmitter may be referred to as a transmitter or a transmitting circuit, etc., for implementing a transmitting function.
  • 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 enable the communication device 1000 to execute the method described in the above method embodiment.
  • the communication device 1000 is a terminal device: the transceiver 1005 is used to execute S22 in FIG. 2 ; S71 in FIG. 7 ; the processor 1001 is used to execute S23 in FIG. 2 : S41 in FIG. 4 ; S51 in FIG. 5 .
  • the communication device 1000 is a core network device: the processor 1001 is used to execute S21 in Figure 2: S61 in Figure 6; S72 in Figure 7; S81 in Figure 8; S91 in Figure 9; the transceiver 1005 is used to execute S22 in Figure 2; S71 in Figure 7.
  • the processor 1001 may include a transceiver for implementing receiving and sending functions.
  • the transceiver may be a transceiver circuit, an interface, or an interface circuit.
  • the transceiver circuit, interface, or interface circuit for implementing the receiving and sending functions may be separate or integrated.
  • the above-mentioned transceiver circuit, interface, or interface circuit may be used for reading and writing code/data, or the above-mentioned transceiver circuit, interface, or interface circuit may be used for transmitting or delivering signals.
  • the processor 1001 may store a computer program 1003, which runs on the processor 1001 and enables the communication device 1000 to perform the method described in the above method embodiment.
  • the computer program 1003 may be fixed in the processor 1001, in which case the processor 1001 may be implemented by hardware.
  • the communication device 1000 may include a circuit that can implement the functions of sending or receiving or communicating in the aforementioned method embodiments.
  • the processor and transceiver described in the present disclosure may be implemented in an integrated circuit (IC), an analog IC, a radio frequency integrated circuit RFIC, a mixed signal IC, an application specific integrated circuit (ASIC), a printed circuit board (PCB), an electronic device, etc.
  • the processor and transceiver may also be manufactured using various IC process technologies, such as complementary metal oxide semiconductor (CMOS), N-type metal oxide semiconductor (NMOS), P-type metal oxide semiconductor (positive channel metal oxide semiconductor, PMOS), bipolar junction transistor (BJT), bipolar CMOS (BiCMOS), silicon germanium (SiGe), gallium arsenide (GaAs), etc.
  • CMOS complementary metal oxide semiconductor
  • NMOS N-type metal oxide semiconductor
  • PMOS P-type metal oxide semiconductor
  • BJT bipolar junction transistor
  • BiCMOS bipolar CMOS
  • SiGe silicon germanium
  • GaAs gallium arsenide
  • the communication device described in the above embodiment may be a terminal device or a core network device, but the scope of the communication device described in the present disclosure is not limited thereto, and the structure of the communication device may not be limited by FIG. 12.
  • the communication device may be an independent device or may be part of a larger device.
  • the communication device may be:
  • the IC set may also include a storage component for storing data and computer programs;
  • ASIC such as modem
  • FIG. 13 is a structural diagram of a chip provided in an embodiment of the present disclosure.
  • the chip 1100 includes a processor 1101 and an interface 1103.
  • the number of the processor 1101 may be one or more, and the number of the interface 1103 may be multiple.
  • the interface 1103 is used to receive code instructions and transmit them to the processor.
  • the processor 1101 is configured to run code instructions to execute the mobility restriction implementation method as described in some of the above embodiments.
  • the interface 1103 is used to receive code instructions and transmit them to the processor.
  • the processor 1101 is configured to run code instructions to execute the mobility restriction implementation method as described in some of the above embodiments.
  • the chip 1100 further includes a memory 1102, and the memory 1102 is used to store necessary computer programs and data.
  • the disclosed embodiments also provide a system for implementing mobility restriction, which includes the communication device as a terminal device and the communication device as a core network device in the aforementioned embodiment of FIG. 11 , or the system includes the communication device as a terminal device and the communication device as a core network device in the aforementioned embodiment of FIG. 12 .
  • the present disclosure also provides a readable storage medium having instructions stored thereon, which, when executed by a computer, implement the functions of any of the above-mentioned method implementation examples.
  • the present disclosure also provides a computer program product, which implements the functions of any of the above method embodiments when executed by a computer.
  • the computer program product includes one or more computer programs.
  • 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 transmitted from one computer-readable storage medium to another computer-readable storage medium.
  • the computer program can be transmitted from a website site, computer, server or data center by wired (e.g., coaxial cable, optical fiber, digital subscriber line (digital subscriber line, DSL)) or wireless (e.g., infrared, wireless, microwave, etc.) mode to another website site, computer, server or data center.
  • the computer-readable storage medium can be any available medium that can be accessed by a computer or a data storage device such as a server or data center that includes one or more available media integrated.
  • the available medium may be a magnetic medium (e.g., a floppy disk, a hard disk, a magnetic tape), an optical medium (e.g., a high-density digital video disc (DVD)), or a semiconductor medium (e.g., a solid state disk (SSD)), etc.
  • a magnetic medium e.g., a floppy disk, a hard disk, a magnetic tape
  • an optical medium e.g., a high-density digital video disc (DVD)
  • DVD high-density digital video disc
  • SSD solid state disk
  • At least one in the present disclosure may also be described as one or more, and a plurality may be two, three, four or more, which is not limited in the present disclosure.
  • the technical features in the technical feature are distinguished by “first”, “second”, “third”, “A”, “B”, “C” and “D”, etc., and there is no order of precedence or size between the technical features described by the "first”, “second”, “third”, “A”, “B”, “C” and “D”.
  • the corresponding relationships shown in the tables in the present disclosure can be configured or predefined.
  • the values of the information in each table are only examples and can be configured as other values, which are not limited by the present disclosure.
  • the corresponding relationships shown in some rows may not be configured.
  • appropriate deformation adjustments can be made based on the above table, such as splitting, merging, etc.
  • the names of the parameters shown in the titles of the above tables can also use other names that can be understood by the communication device, and the values or representations of the parameters can also be other values or representations that can be understood by the communication device.
  • 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.
  • the predefined in the present disclosure may be understood as defined, predefined, stored, pre-stored, pre-negotiated, pre-configured, solidified, or pre-burned.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Computer Security & Cryptography (AREA)
  • Physics & Mathematics (AREA)
  • Astronomy & Astrophysics (AREA)
  • General Physics & Mathematics (AREA)
  • Mobile Radio Communication Systems (AREA)

Abstract

本公开实施例公开了一种移动性限制实现方法和装置，可应用于通信技术领域，由终端设备执行的方法包括：接收核心网设备发送的地理区域描述GAD与跟踪区TA的映射关系，根据映射关系，以及终端设备当前的全球卫星导航系统GNSS信息，确定终端设备所处的目标TA。由此，能够确定终端设备所处的目标TA，以使终端设备与核心网设备根据所述目标TA对所述终端设备实施移动性限制。

Description

移动性限制实现方法和装置 技术领域
本公开涉及通信技术领域，尤其涉及一种移动性限制实现方法和装置。
背景技术
相关技术中，在终端设备使用卫星接入的情况下，判断是否对终端设备实现通信限制的依据是当向终端设备广播的所有TA(tracking area，跟踪区)都位于禁止接入域内，则禁止终端设备在当前位置接入网络，至少有一个不位于禁止接入域内，则允许终端设备在当前位置接入网络；当向终端设备广播的所有TA都位于非允许区域内，则禁止终端设备在当前位置与网络进行通信，至少有一个不位于非允许区域内，则允许终端设备在当前位置与网络进行通信。然而所述广播TA中可能包含终端设备当前注册网络RPLMN(registered public land mobile network，已注册的公用陆地移动网络)对应的TA以及其他eRPLMN(equivalent registered public land mobile network，等效已注册的公用陆地移动网络)对应的TA，如果属于所述RLPMN的所有广播TA都位于非允许区域中，根据规则，则禁止终端设备在当前位置与RPLMN通信，但是如果属于其他eRPLMN的至少一个广播TA位于允许区域中，根据规则，则允许UE在当前位置可以和eRPLMN通信。根据相关技术中定义的移动性限制的规则就会出现如上述情况的移动性限制失效的情况。
因此如何解决现有规则引发的移动性限制失效为亟需解决的问题。
发明内容
本公开实施例提供一种移动性限制实现方法和装置，能够确定终端设备所处的目标TA，以使终端设备与核心网设备根据所述目标TA对所述终端设备实施移动性限制根据所述目标TA对所述终端设备实施移动性限制。
第一方面，本公开实施例提供一种移动性限制实现方法，该方法由终端设备执行，该方法包括：获取地理区域描述GAD与跟踪区TA的映射关系，根据映射关系，以及终端设备当前的全球卫星导航系统GNSS信息，确定终端设备所处的目标TA。
在该技术方案中，终端设备接收核心网设备发送的地理区域描述GAD与跟踪区TA的映射关系，根据映射关系，以及终端设备当前的全球卫星导航系统GNSS信息，确定终端设备所处的目标TA。由此，能够确定终端设备所处的目标TA，以使终端设备与核心网设备根据所述目标TA对所述终端设备实施移动性限制。
第二方面，本公开实施例提供另一种移动性限制实现方法，该方法由核心网设备执行，该方法包括：获取地理区域描述GAD与跟踪区TA的映射关系；向终端设备发送地理区域描述GAD与跟踪区TA的映射关系，其中，映射关系用于终端设备确定所处的目标TA。
第三方面，本公开实施例提供又一种移动性限制实现方法，该方法由核心网设备执行，该方法包括：确定终端设备所处的目标TA，其中，所述目标TA从所述终端设备接入网络所使用的接入网设备处获取，或者所述目标TA根据地理区域描述GAD与跟踪区TA的映射关系，以及终端设备当前的GNSS信息确定。
第四方面，本公开实施例提供一种通信装置，该通信装置具有实现上述第一方面所述的方法中终端设备的部分或全部功能，比如通信装置的功能可具备本公开中的部分或全部实施例中的功能，也可以具备单独实施本公开中的任一个实施例的功能。所述功能可以通过硬件实现，也可以通过硬件执行相应的软件实现。所述硬件或软件包括一个或多个与上述功能相对应的单元或模块。
在一种实现方式中，该通信装置的结构中可包括收发模块和处理模块，所述处理模块被配置为支持通信装置执行上述方法中相应的功能。所述收发模块用于支持通信装置与其他设备之间的通信。所述通信装置还可以包括存储模块，所述存储模块用于与收发模块和处理模块耦合，其保存通信装置必要的计算机程序和数据。
在一种实现方式中，所述通信装置包括：收发模块，被配置为获取地理区域描述GAD与跟踪区TA的映射关系；处理模块，被配置为根据映射关系，以及终端设备当前的GNSS信息，确定终端设备所处的目标TA。
第五方面，本公开实施例提供另一种通信装置，该通信装置具有实现上述第二方面所述的方法示例中核心网设备的部分或全部功能，比如通信装置的功能可具备本公开中的部分或全部实施例中的功能，也可以具备单独实施本公开中的任一个实施例的功能。所述功能可以通过硬件实现，也可以通过硬件执行相应的软件实现。所述硬件或软件包括一个或多个与上述功能相对应的单元或模块。
在一种实现方式中，该通信装置的结构中可包括收发模块和处理模块，该处理模块被配置为支持通信装置执行上述方法中相应的功能。收发模块用于支持通信装置与其他设备之间的通信。所述通信装置还可以包括存储模块，所述存储模块用于与收发模块和处理模块耦合，其保存通信装置必要的计算机程序和数据。
在一种实现方式中，所述通信装置包括：处理模块，被配置为获取地理区域描述GAD与跟踪区TA的映射关系；收发模块，被配置为向终端设备发送地理区域描述GAD与跟踪区TA的映射关系，其中，映射关系用于终端设备确定所处的目标TA。
在一种实现方式中，所述通信装置包括：处理模块，被配置为确定终端设备所处的目标TA，其中，所述目标TA从所述终端设备接入网络所使用的接入网设备处获取，或者所述目标TA根据地理区域描述GAD与跟踪区TA的映射关系，以及终端设备当前的GNSS信息确定。
第六方面，本公开实施例提供一种通信装置，该通信装置包括处理器，当该处理器调用存储器中的计算机程序时，执行上述第一方面所述的方法。
第七方面，本公开实施例提供一种通信装置，该通信装置包括处理器，当该处理器调用存储器中的计算机程序时，执行上述第二方面或第三方面所述的方法。
第八方面，本公开实施例提供一种通信装置，该通信装置包括处理器和存储器，该存储器中存储有计算机程序；所述处理器执行该存储器所存储的计算机程序，以使该通信装置执行上述第一方面所述的方法。
第九方面，本公开实施例提供一种通信装置，该通信装置包括处理器和存储器，该存储器中存储有计算机程序；所述处理器执行该存储器所存储的计算机程序，以使该通信装置执行上述第二方面或第三方面所述的方法。
第十方面，本公开实施例提供一种通信装置，该装置包括处理器和接口电路，该接口电路用于接收代码指令并传输至该处理器，该处理器用于运行所述代码指令以使该装置执行上述第一方面所述的方法。
第十一方面，本公开实施例提供一种通信装置，该装置包括处理器和接口电路，该接口电路用于接收代码指令并传输至该处理器，该处理器用于运行所述代码指令以使该装置执行上述第二方面或第三方面所述的方法。
第十二方面，本公开实施例提供一种跟踪区TA的确定系统，该系统包括第四方面所述的通信装置以及第五方面所述的通信装置，或者，该系统包括第六方面所述的通信装置以及第七方面所述的通信装置，或者，该系统包括第八方面所述的通信装置以及第九方面所述的通信装置，或者，该系统包括第十方面所述的通信装置以及第十一方面所述的通信装置。
第十三方面，本发明实施例提供一种计算机可读存储介质，用于储存为上述终端设备所用的指令，当所述指令被执行时，使所述终端设备执行上述第一方面所述的方法。
第十四方面，本发明实施例提供一种可读存储介质，用于储存为上述核心网设备所用的指令，当所述指令被执行时，使所述核心网设备执行上述第二方面或第三方面所述的方法。
第十五方面，本公开还提供一种包括计算机程序的计算机程序产品，当其在计算机上运行时，使得计算机执行上述第一方面所述的方法。
第十六方面，本公开还提供一种包括计算机程序的计算机程序产品，当其在计算机上运行时，使得计算机执行上述第二方面或第三方面所述的方法。
第十七方面，本公开提供一种芯片系统，该芯片系统包括至少一个处理器和接口，用于支持终端设备实现第一方面所涉及的功能，例如，确定或处理上述方法中所涉及的数据和信息中的至少一种。在一种可能的设计中，所述芯片系统还包括存储器，所述存储器，用于保存终端设备必要的计算机程序和数据。该芯片系统，可以由芯片构成，也可以包括芯片和其他分立器件。
第十八方面，本公开提供一种芯片系统，该芯片系统包括至少一个处理器和接口，用于支持核心网设备实现第二方面或第三方面所涉及的功能，例如，确定或处理上述方法中所涉及的数据和信息中的至少一种。在一种可能的设计中，所述芯片系统还包括存储器，所述存储器，用于保存核心网设备必要的计算机程序和数据。该芯片系统，可以由芯片构成，也可以包括芯片和其他分立器件。
第十九方面，本公开提供一种计算机程序，当其在计算机上运行时，使得计算机执行上述第一方面所述的方法。
第二十方面，本公开提供一种计算机程序，当其在计算机上运行时，使得计算机执行上述第二方面或第三方面所述的方法。
附图说明
为了更清楚地说明本公开实施例或背景技术中的技术方案，下面将对本公开实施例或背景技术中所 需要使用的附图进行说明。
图1是本公开实施例提供的一种通信系统的架构图；
图2是本公开实施例提供的一种移动性限制实现方法的流程图；
图3是本公开实施例提供的一种核心网设备通过初始注册的过程向终端设备发送GAD与TA的映射关系的流程图；
图4是本公开实施例提供的一种移动性管理方法的流程图；
图5是本公开实施例提供的另一种移动性管理方法的流程图；
图6是本公开实施例提供的另一种移动性限制实现方法的流程图；
图7是本公开实施例提供的又一种移动性限制实现方法的流程图；
图8是本公开实施例提供的又一种移动性管理方法的流程图；
图9是本公开实施例提供的又一种移动性管理方法的流程图；
图10是本公开实施例提供的又一种移动性管理方法的流程图；
图11是本公开实施例提供的一种通信装置的结构图；
图12是本公开实施例提供的另一种通信装置的结构图；
图13是本公开实施例提供的一种芯片的结构示意图。
具体实施方式
为了更好的理解本公开实施例公开的一种移动性限制实现方法和装置，下面首先对本公开实施例适用的通信系统进行描述。
这里将详细地对示例性实施例进行说明，其示例表示在附图中。下面的描述涉及附图时除非另有表示，不同附图中的相同数字表示相同或相似的要素。以下示例性实施例中所描述的实施方式并不代表与本公开相一致的所有实施方式。相反，它们仅是与如所附权利要求书中所详述的、本公开的一些方面相一致的装置和方法的例子。
在本公开使用的术语是仅仅出于描述特定实施例的目的，而非旨在限制本公开。在本公开和所附权利要求书中所使用的单数形式的“一种”、“所述”和“该”也是旨在包括多数形式，除非上下文清楚地表示其它含义。还应当理解，本文中使用的术语“和/或”是指并包含一个或多个相关联的列出项目的任何或所有可能组合。
应当理解，尽管在本公开可能采用术语第一、第二、第三等来描述各种信息，但这些信息不应限于这些术语。这些术语仅用来将同一类型的信息彼此区分开。例如，在不脱离本公开范围的情况下，第一信息也可以被称为第二信息，类似地，第二信息也可以被称为第一信息。取决于语境，例如，在此所使用的词语“如果”可以被解释成为“在……时”或“当……时”或“响应于确定”。
需要说明的是，本公开所涉及的信息(包括但不限于用户设备信息、用户个人信息等)、数据(包括但不限于用于分析的数据、存储的数据、展示的数据等)以及信号，均为经用户授权或者经过各方充分授权的，且相关数据的收集、使用和处理需要遵守相关国家和地区的相关法律法规和标准。
为了更好的理解本公开实施例公开的一种移动性限制实现方法和装置，下面首先对本公开实施例适用的通信系统进行描述。
如图1所示，本公开实施例提供了一种通信系统，包括：核心网设备(例如5G核心网(5th generation core，5GC)11、演进型分组核心网(evolved packet core，EPC)12)、接入网设备(例如继续演进的节点B(gNB)13、演进型节点B(evolved node B，eNB)14)、终端设备15。
核心网设备11，是指为终端设备提供业务支持的核心网(core network，CN)中的设备。目前，一些核心网设备包括：接入和移动性管理功能(access and mobilitymanagement function，AMF)实体、会话管理功能(session management function，SMF)实体、用户面功能(user plane function，UPF)实体等等，此处不一一列举。其中，AMF实体可以负责终端设备的接入管理和移动性管理。SMF实体可以负责会话管理，如用户的会话建立等。UPF实体可以是用户面的功能实体，主要负责连接外部网络。需要说明的是，本公开中实体也可以称为网元或功能实体，例如，AMF实体也可以称为AMF网元或AMF功能实体，SMF实体也可以称为SMF网元或SMF功能实体等。
接入网设备13，是指将终端设备接入到无线网络的无线接入网(radio accessnetwork，RAN)节点(或设备)，又可以称为基站。目前，一些RAN节点的举例包括：gNB、eNB、传输接收点(transmission reception point，TRP)、无线网络控制器(radio networkcontroller，RNC)、节点B(Node B，NB)、基站控制器(base station controller，BSC)、基站收发台(base transceiver station，BTS)、家庭基站(例如，home evolved NodeB，或homenode B，HNB)、基带单元(base band unit，BBU)，或无线保真(wireless fidelity，Wi-Fi)接入点(access point，AP)等。另外，在一种网络结构中，接入网设备可以包括集中单元(centralized unit，CU)、或分布 单元(distributed unit，DU)、或包括CU和DU的RAN设备。其中包括CU和DU的RAN设备从逻辑功能角度将协议层拆分开，部分协议层的功能放在CU集中控制，剩下部分或全部协议层的功能分布在DU中，由CU集中控制DU。
终端设备15，又称之为用户设备(user equipment，UE)、移动台(mobile station，MS)、移动终端(mobile terminal，MT)等，是指向用户提供语音和/或数据连通性的设备。例如，具有无线连接功能的手持式设备、车载设备等。目前，一些终端设备的举例包括：手机(mobile phone)、平板电脑、笔记本电脑、掌上电脑、移动互联网设备(mobile internetdevice，MID)、可穿戴设备、虚拟现实(virtual reality，VR)设备、增强现实(augmentedreality，AR)设备、工业控制(industrial control)中的无线终端、无人驾驶(selfdriving)中的无线终端、远程手术(remote medical surgery)中的无线终端、智能电网(smart grid)中的无线终端、运输安全(transportation safety)中的无线终端、智慧城市(smart city)中的无线终端、智慧家庭(smart home)中的无线终端等。
在该通信系统中，接入网设备13和接入网设备14均可以与多个终端设备15通信。但应理解，与接入网设备13通信的终端设备和与接入网设备14通信的终端设备可以是相同的，也可以是不同的。图2中示出的终端设备15可同时与接入网设备13和接入网设备14通信，但这仅示出了一种可能的场景，在某些场景中，终端设备可能仅与接入网设备13或接入网设备14通信，本公开对此不做限定。
应理解，图1仅为便于理解而示例的简化示意图，该通信系统中还可以包括其他接入网设备，终端设备，或者核心网设备，图1中未予以画出。
可以理解的是，本公开实施例描述的通信系统是为了更加清楚的说明本公开实施例的技术方案，并不构成对于本公开实施例提供的技术方案的限定，本领域普通技术人员可知，随着系统架构的演变和新业务场景的出现，本公开实施例提供的技术方案对于类似的技术问题，同样适用。
此外，为了便于理解本公开实施例，做出以下几点说明。
第一，本公开实施例中，“用于指示”可以包括用于直接指示和用于间接指示。当描述某一信息用于指示A时，可以包括该信息直接指示A或间接指示A，而并不代表该信息中一定携带有A。
将信息所指示的信息称为待指示信息，则具体实现过程中，对待指示信息进行指示的方式有很多种，例如但不限于，可以直接指示待指示信息，如待指示信息本身或者该待指示信息的索引等。也可以通过指示其他信息来间接指示待指示信息，其中该其他信息与待指示信息之间存在关联关系。还可以仅仅指示待指示信息的一部分，而待指示信息的其他部分则是已知的或者提前约定的。例如，还可以借助预先约定(例如协议规定)的各个信息的排列顺序来实现对特定信息的指示，从而在一定程度上降低指示开销。
待指示信息可以作为一个整体一起发送，也可以分成多个子信息分开发送，而且这些子信息的发送周期和/或发送时机可以相同，也可以不同。具体发送方法本公开不进行限定。其中，这些子信息的发送周期和/或发送时机可以是预先定义的，例如根据协议预先定义的。
第二，在本公开中第一、第二以及各种数字编号(例如，“#1”、“#2”)仅为描述方便进行的区分，并不用来限制本公开实施例的范围。例如，区分不同的TA等。
第三，在本公开中，终端设备具有GNSS(Global Navigation Satellite System，全球卫星导航系统)能力。
第四，本公开实施例中涉及的“协议”可以是指通信领域的标准协议，例如可以包括LTE协议、NR协议、WLAN协议以及其他通信系统中的相关协议，本公开对此不做限定。
第五，本公开实施例列举了多个实施方式以对本公开实施例的技术方案进行清晰地说明。当然，本领域内技术人员可以理解，本公开实施例提供的多个实施例，可以被单独执行，也可以与本公开实施例中其他实施例的方法结合后一起被执行，还可以单独或结合后与其他相关技术中的一些方法一起被执行；本公开实施例并不对此进行限定。
针对相关技术中确定现有移动性限制规则可能导致移动性限制失效的问题，本公开实施例中提供一种移动性限制实现方法和装置，终端设备接收核心网设备发送的GAD(Geographical Area Description，地理区域描述)与TA的映射关系，根据该映射关系以及终端设备当前的GNSS信息，可以确定终端设备所处的目标TA，由此能够确定终端设备所处的目标TA，以使终端设备与核心网设备根据所述目标TA对所述终端设备实施移动性限制。
下面结合附图对本公开所提供的一种移动性限制实现方法和装置进行详细地介绍。
请参见图2，图2是本公开实施例提供的一种移动性限制实现方法的流程图。
如图2所示，该方法可以包括但不限于如下步骤：
S21：核心网设备获取GAD与TA的映射关系。
本公开实施例中，核心网设备例如可以是AMF(access and mobility management function，接入和 移动管理功能)，获取GAD与TA的映射关系。
其中，核心网获取GAD与TA的映射关系，可以自行配置，或者还可以基于协议约定获取，或者还可以基于接入网设备配置获取，等等，本公开实施例对此不作具体限制。
其中，GAD与TA的映射关系，可以包括GAD与所有签约PLMN(public land mobile network，公用陆地移动网络)的TA的映射关系。
在一些可能的实现方式中，核心网设备在获取GAD与TA的映射关系的情况下，可以获取终端设备当前的GNSS信息，例如终端设备当前的位置信息，以根据终端设备的GNSS信息确定对应的目标GAD，进一步的，可以根据目标GAD以及映射关系，确定终端设备所处的目标TA或者根据接入网络设备上报的代表终端设备位置的TA和所述映射关系确定终端设备所处的目标TA。
可以理解的是，核心网设备在获取GAD与TA的映射关系的情况下，可以将GAD与TA的映射关系发送至终端设备，核心网设备执行S22。
S22：核心网设备向终端设备发送GAD与TA的映射关系。
本公开实施例中，核心网设备在获取GAD与TA的映射关系的情况下，可以向终端设备发送GAD与TA的映射关系。
其中，核心网设备可以在终端设备接入网络的任意阶段向终端设备发送GAD与TA的映射关系。例如：可以在初始注册过程、注册更新过程、UCU(UE Configuration Update，终端设备配置更新)过程、服务请求过程等等，向终端设备发送GAD与TA的映射关系，本公开对此不作限制。
示例性地，如图3所示，核心网设备可以通过初始注册的过程向终端设备发送GAD与TA的映射关系。具体地，交互流程如下：
0、终端设备获取当前位置(GNSS信息)，并根据保存的移动性限制信息中的禁止接入区域信息，确定终端设备在当前位置可以接入选择的PLMN。
1、终端设备向核心网设备(AMF)发送注册请求，例如，终稿设备可以通过基站(NR(LEO)向核心网设备发送注册请求)。
2、AMF处理终端设备的注册请求，为终端设备的接入注册，制定RA(Registration Area，注册区域)、移动性限制信息等。其中，移动性限制信息可以包括禁止接入区域(forbidden area)信息，服务区域限制(non-allowed area or allowed area，非允许区域或允许区域)信息。注册区区，其中，forbidden area,non-allowed area、allowed area可以由一组TAI(tracking area identity，跟踪区域标识)构成。
3和4、AMF向网络管理中心(network management center，NMC)获取属于PLMN的TA的GAD与TA的映射关系。
5、AMF向终端设备发送注册响应，将注册区、移动性限制信息[forbidden area,non-allowed area or allowed area]，GAD与TA的映射关系下发给终端设备。
6、终端设备根据收到的信息，对已经保存的移动性限制信息[forbidden area,non-allowed area or allowed area]信息进行更新，并保存GAD与TA的映射关系。
通过上述流程，终端获取GAD与TA的映射关系。
需要说明的是，上述示例仅作为示意，本公开实施例中，核心网设备还可以通过注册更新过程、或UCU过程、或服务请求过程等向终端设备发送GAD与TA的映射关系，本公开实施例对此不作具体限制。
本公开实施例中，终端设备可以获取并保存GAD与TA的映射关系。当终端设备接收到包括新的映射关系的信息时，可以对已保存的映射关系进行更新。当终端设备关机情况下，保存的GAD与TA的映射关系不会被删除。当终端设备删除USIM(Universal Subscriber Identity Module，全球用户识别模块)时，同时删除保存的GAD与TA的映射关系。
可以理解的是，终端设备在接收到核心网设备发送的GAD与TA的映射关系的情况下，可以进一步执行S23。
S23：终端设备根据映射关系，以及终端设备当前的GNSS信息，确定终端设备所处的目标TA。
本公开实施例中，终端设备可以根据映射关系，以及终端设备当前的GNSS信息，确定终端设备所处的目标TA。
在一些实施例中，终端设备根据终端设备当前的GNSS信息，确定所对应的目标GAD；根据目标GAD和映射关系，确定终端设备所处的目标TA。
本公开实施例中，终端设备可以根据终端设备当前的GNSS信息，确定当前的GNSS信息所对应的目标GAD，进而可以根据目标GAD和映射关系，确定终端设备所处的目标TA。
通过实施本公开实施例，终端设备接收核心网设备发送的GAD与TA的映射关系；根据映射关系，以及终端设备当前的全球卫星导航系统GNSS信息，确定终端设备所处的目标TA。由此，能够确定终 端设备所处的目标TA，以使终端设备与核心网设备根据目标TA对终端设备实施移动性限制。
请参见图4，图4是本公开实施例提供的一种移动性管理方法的流程图。
如图4所示，该方法由终端设备执行，该方法可以包括但不限于如下步骤：
S41：终端设备根据第一目标TA，以及禁止接入域信息，确定是否接入PLMN，其中，目标TA为PLMN对应的第一目标TA。
本公开实施例中，终端设备确定终端设备所处的目标TA的方法可以参见上述实施例中的相关描述，此处不再赘述。
其中，目标TA为PLMN对应的第一目标TA。
需要说明的是，本公开实施例中终端设备确定终端设备所处的PLMN对应的第一目标TA的方法，与上述实施例中终端设备确定该终端设备所处的目标TA的方法相同，可以参见上述实施例中的相关描述，此处不再赘述。当然，应当理解，终端设备也可以通过其他方法确定所处的TA。
本公开实施例中，终端设备可以根据第一目标TA，以及禁止接入域信息，确定是否接入PLMN。
在一些实施例中，终端设备根据第一目标TA，以及禁止接入域信息，确定是否接入PLMN，包括：
响应于第一目标TA包含在PLMN的禁止接入域，确定禁止在第一目标TA接入PLMN；或
响应于第一目标TA未包含在PLMN的禁止接入域，确定允许在第一目标TA接入PLMN，其中，禁止接入域信息用于指示PLMN的禁止接入域。
本公开实施例中，禁止接入域信息用于指示PLMN的禁止接入域。
本公开实施例中，终端设备可以根据第一目标TA，以及禁止接入域信息，确定是否接入PLMN，其中，在第一目标TA包含在PLMN的禁止接入域的情况下，确定禁止在第一目标TA接入PLMN。
本公开实施例中，终端设备可以根据第一目标TA，以及禁止接入域信息，确定是否接入PLMN，其中，在第一目标TA未包含在PLMN的禁止接入域的情况下，确定允许在第一目标TA接入PLMN。
可以理解的是，如果终端设备确定允许在第一目标TA接入PLMN，则终端设备可以选择在第一目标TA接入PLMN，或者还可以选择在第一目标TA不接入PLMN。
需要说明的是，本公开实施例中，S41可以单独被实施，也可以结合本公开实施例中的任何一个其他步骤一起被实施，例如结合本公开实施例中的S21至S23一起被实施，本公开实施例并不对此做出限定。
通过实施本公开实施例，终端设备根据第一目标TA，以及禁止接入域信息，确定是否接入PLMN，其中，目标TA为PLMN对应的第一目标TA。由此，在确定终端设备所处的目标TA的基础上，能够保证禁止接入域信息的准确控制，避免禁止接入域信息限制失效。
请参见图5，图5是本公开实施例提供的另一种移动性管理方法的流程图。
如图5所示，该方法由终端设备执行，该方法可以包括但不限于如下步骤：
S51：终端设备根据第二目标TA，以及服务域限制信息，确定是否与已注册的公用陆地移动网络RPLMN进行通信，其中，目标TA为RPLMN对应的第二目标TA。
本公开实施例中，终端设备确定终端设备所处的目标TA的方法可以参见上述实施例中的相关描述，此处不再赘述。
其中，目标TA为RPLMN(registered PLMN，已注册的公用陆地移动网络)对应的第二目标TA。
需要说明的是，本公开实施例中终端设备确定终端设备所处的RPLMN对应的第二目标TA的方法，与上述实施例中终端设备确定终端设备所处的目标TA的方法相同，可以参见上述实施例中的相关描述，此处不再赘述。
本公开实施例中，终端设备可以根据第二目标TA，以及服务域限制信息，确定是否与已注册的公用陆地移动网络RPLMN进行通信。
在一些实施例中，终端设备根据第二目标TA，以及服务域限制信息，确定是否与RPLMN进行通信，包括：
响应于第二目标TA包含在RPLMN的非允许区域，确定禁止在第二目标TA与RPLMN进行通信，其中，服务域限制信息用于指示RPLMN的非允许区域；或
响应于第二目标TA包含在RPLMN的非允许区域，确定禁止在第二目标TA与任何eRPLMN进行通信，其中，服务域限制信息用于指示RPLMN的非允许区域；或
响应于第二目标TA包含在RPLMN的允许区域，确定允许在第二目标TA与RPLMN进行通信，其中，服务域限制信息用于指示RPLMN的允许区域。
本公开实施例中，服务域限制信息用于指示RPLMN的非允许区域或用于指示RPLMN的允许区域。
本公开实施例中，终端设备可以根据第二目标TA，以及服务域限制，确定是否与RPLMN进行通信，其中，在第二目标TA包含在RPLMN的非允许区域的情况下，确定禁止在第二目标TA与RPLMN进行通信。
本公开实施例中，终端设备可以根据第二目标TA，以及服务域限制，确定是否与RPLMN进行通信，其中，在第二目标TA包含在RPLMN的非允许区域的情况下，确定禁止在第二目标TA与任何eRPLMN(equivalent registered PLMN，等效已注册的公用陆地移动网络)进行通信。
本公开实施例中，终端设备可以根据第二目标TA，以及服务域限制，确定是否与RPLMN进行通信，其中，在第二目标TA包含在RPLMN的允许区域的情况下，确定允许在第二目标TA与RPLMN进行通信。
其中，终端设备在确定允许在第二目标TA与RPLMN进行通信的情况下，可以发起与RPLMN进行通信的通信请求，或者还可以不发起与RPLMN进行通信的通信请求。
可以理解的是，服务区域限制信息可能包含允许区域或非允许区域(例如使用跟踪区域标识指定)。
其中，允许区域：终端设备在这个区域中，被允许发起与网络的通信
其中，非允许区域：终端设备在这个区域内，处于服务被限制状态。不允许终端设备向网络发起服务请求，或对用户面数据、控制面数据的任何连接请求。
其中，可以使用跟踪区域标识指定允许区域和非允许区域。例如，允许区域可包含一个或多个(例如最多16个)TAs，或将所有TA都置于允许区域。
其中，核心网设备(AMF)可以根据终端设备订阅将服务区域限制信息分配给终端设备，并且可以根据需要进行更新。它可以通过注册程序或UCU程序提供给终端设备。当提供给终端设备时，它只能包含允许区域或非允许区域，而不能同时包含这两个区域。
如果终端设备使用卫星接入，且接入网设备向终端设备广播多个TAI，在所述终端设备接入网络的过程中，所述接入网设备将所述广播的多个TAI上报给核心网设备。核心网设备将执行如下服务区域限制规则：
如果所述所有广播的TAI都包含在非允许区域内，则所述终端设备和AMF都认为终端设备位于非允许区域内。
如果所述所有广播的TAI中至少有一个TAI不包含在非允许区域，则所述终端设备和AMF都认为终端设备位于允许区域内。
相关技术中，对于卫星接入网络被多个网络共享的情况(例如，PLMN-A和PLMN-B共享相同的卫星接入),
所述卫星接入向终端设备广播多个可用PLMN的TAI。在终端设备接入网络执行注册过程中，卫星接入设备将所述广播的多个TAI上报给核心网络，核心网络为其指定一个注册区域，除了注册的PLMN(RPLMN)之外，该注册区域还包含至少一个等效的注册PLMN(eRPLMN)，即注册区域载有一份包括来自RPLMN的TAI及等效的RPLMN的TAI列表。
同时，核心网络还为终端设备分配一个允许区域，所述允许区域也包含了RPLMN的TAI和eRPLMN的TAI。
其后，由于终端设备的移动，会出现如下情况：
1，接收的广播TAI中所有属于RPLMN的广播TAI都不在允许区域内。但是
2，在允许区域内至少包括一个属于一个eRPLMN的广播TAI。
在这种情况下，基于当前的解决方案。根据1，则位于当前位置的终端设备不允许与网络通信，而根据2，位于当前位置的终端设备可以使用eRPLMN进行通信。在这种情况下，对当前位置的终端设备执行服务区域限制无效。
基于此，本公开实施例中，终端设备可以根据第二目标TA，以及服务域限制信息，确定是否与RPLMN进行通信，其中，在第二目标TA包含在RPLMN的非允许区域的情况下，确定禁止在第二目标TA与任何eRPLMN(equivalent registered PLMN，等效已注册的公用陆地移动网络)进行通信，能够避免服务域限制失效。
并且，在一些实施例中，终端设备在第二目标TA包含在一个RPLMN的允许区域的情况下，根据第三目标TA，以及服务域限制信息，确定是否与eRPLMN进行通信，其中，目标TA为eRPLMN对应的第三目标TA。
其中，目标TA为eRPLMN对应的第三目标TA。
需要说明的是，本公开实施例中终端设备确定终端设备所处的eRPLMN对应的第三目标TA的方法，与上述实施例中终端设备确定终端设备所处的目标TA的方法相同，可以参见上述实施例中的相关 描述，此处不再赘述。
本公开实施例中，在第二目标TA包含在一个RPLMN的允许区域的情况下，终端设备可以根据第三目标TA，以及服务域限制信息，确定是否与eRPLMN进行通信。
在一些实施例中，终端设备根据第三目标TA，以及服务域限制信息，确定是否与eRPLMN进行通信，包括：
响应于第三目标TA包含在eRPLMN的允许区域，确定允许在第三目标TA与eRPLMN进行通信，其中，服务域限制信息用于指示eRPLMN的允许区域；或
响应于第三目标TA包含在eRPLMN的非允许区域，确定禁止在第三目标TA与eRPLMN进行通信，其中，服务域限制信息用于指示eRPLMN的非允许区域。
本公开实施例中，服务域限制信息用于指示eRPLMN的非允许区域或用于指示eRPLMN的允许区域。
本公开实施例中，终端设备可以根据第三目标TA，以及服务域限制信息，确定是否与eRPLMN进行通信，其中，在第三目标TA包含在eRPLMN的允许区域的情况下，确定允许在第三目标TA与eRPLMN进行通信。
其中，终端设备在确定允许在第三目标TA与eRPLMN进行通信的情况下，可以发起与eRPLMN进行通信的通信请求，或者还可以不发起与eRPLMN进行通信的通信请求。
本公开实施例中，终端设备可以根据第三目标TA，以及服务域限制信息，确定是否与eRPLMN进行通信，其中，在第三目标TA包含在eRPLMN的非允许区域的情况下，确定禁止在第三目标TA与eRPLMN进行通信。
基于此，本公开实施例中，终端设备在第二目标TA包含在一个RPLMN的允许区域的情况下，可以确定终端设备所处的eRPLMN对应的第三目标TA，根据第三目标TA，以及服务域限制信息，确定是否与eRPLMN进行通信。其中，在第三目标TA包含在eRPLMN的允许区域的情况下，确定允许在第三目标TA与eRPLMN进行通信，在第三目标TA包含在eRPLMN的非允许区域的情况下，确定禁止在第三目标TA与eRPLMN进行通信。由此，能够避免服务域限制失效。
需要说明的是，本公开实施例中，S51可以单独被实施，也可以结合本公开实施例中的任何一个其他步骤一起被实施，例如结合本公开实施例中的S21至S23和/或S31和/或S41一起被实施，本公开实施例并不对此做出限定。
通过实施本公开实施例，终端设备根据第二目标TA，以及服务域限制信息，确定是否与已注册的公用陆地移动网络RPLMN进行通信，其中，目标TA为RPLMN对应的第二目标TA。由此，在确定终端设备所处的目标TA的基础上，能够保证服务域限制信息的准确控制，避免服务域限制信息限制失效。
请参见图6，图6是本公开实施例提供的另一种移动性限制实现方法的流程图。
如图6所示，该方法可以包括但不限于如下步骤：
S61：核心网设备确定终端设备所处的目标TA中，其中，目标TA从终端设备接入网络所使用的接入网设备处获取，或者目标TA根据GAD与TA的映射关系以及终端设备当前的GNSS信息确定。
本公开实施例中，核心网设备获取GAD与TA的映射的关系的相关描述可以参见上述实施例中的相关描述，此处不再赘述。
本公开实施例中，核心网设备在确定GAD与TA的映射关系的情况下，可以进一步获取终端设备当前的GNSS信息，进一步的，根据映射关系以及终端设备当前的GNSS信息，确定终端设备所处的目标TA或者根据接入网络设备上报的代表终端设备当前位置的TA和映射关系确定的目标TA。
其中，核心网设备获取终端设备当前的GNSS信息的方法，可以基于协议约定确定，或者还可以基于接入网设备配置确定，等等。
在一些实施例中，核心网设备根据终端设备当前的GNSS信息，确定所对应的目标GAD；根据目标GAD和映射关系，确定终端设备所处的目标TA。
本公开实施例中，核心网设备可以根据终端设备当前的GNSS信息，确定当前的GNSS信息所对应的目标GAD，进而可以根据目标GAD和映射关系，确定终端设备所处的目标TA。
可以理解的是，核心网设备可以在能够确定终端设备当前的GNSS信息的任一阶段，根据GAD与TA的映射关系，以及终端设备当前的GNSS信息，确定终端设备所处的目标TA。
示例性地，核心网设备可以在终端设备接入网络时，根据GAD与TA的映射关系，以及终端设备当前的GNSS信息，确定终端设备所处的目标TA。
示例性地，核心网还可以在终端设备发起和RPLMN的通信请求时，根据GAD与TA的映射关系， 以及终端设备当前的GNSS信息，确定终端设备所处的目标TA。
示例性地，核心网还可以在终端设备发起和eRPLMN的通信请求时，根据GAD与TA的映射关系，以及终端设备当前的GNSS信息，确定终端设备所处的目标TA。
需要说明的是，上述示例仅作为示意，不作为对本公开实施例的具体限制。
需要说明的是，本公开实施例中，S61可以单独被实施，也可以结合本公开实施例中的任何一个其他步骤一起被实施，例如结合本公开实施例中的S21至S23和/或S41和/或S51一起被实施，本公开实施例并不对此做出限定。
通过实施本公开实施例，核心网设备根据GAD与TA的映射关系，以及终端设备当前的GNSS信息，确定终端设备所处的目标TA。由此，能够确定终端设备所处的目标TA，以使终端设备与核心网设备根据目标TA对终端设备实施移动性限制。
请参见图7，图7是本公开实施例提供的又一种移动性限制实现方法的流程图。
如图7所示，该方法可以包括但不限于如下步骤：
S71：终端设备向核心网设备上报终端设备的GNSS信息。
本公开实施例中，终端设备向核心网设备上报终端设备的GNSS信息，其中，终端设备可以在定位过程中，向核心网设备上报终端设备的GNSS信息。
S72：核心网设备根据GAD与TA的映射关系，以及终端设备当前的GNSS信息，确定终端设备所处的目标TA。
其中，S72的相关描述可以参见上述实施例中的相关描述，此处不再赘述。
需要说明的是，本公开实施例中，S71与S72可以单独被实施，也可以结合本公开实施例中的任何一个其他步骤一起被实施，例如结合本公开实施例中的S21至S23和/或S41和/或S51和/或S61一起被实施，本公开实施例并不对此做出限定。
通过实施本公开实施例，核心网设备接收终端设备上报终端设备的GNSS信息，根据GAD与TA的映射关系，以及终端设备当前的GNSS信息，确定终端设备所处的目标TA。由此，能够确定终端设备所处的目标TA，以使终端设备与核心网设备根据目标TA对终端设备实施移动性限制。
请参见图8，图8是本公开实施例提供的又一种移动性管理方法的流程图。
如图8所示，该方法由核心网设备执行，该方法可以包括但不限于如下步骤：
S81：核心网设备根据第一目标TA，以及禁止接入域信息，确定是否允许终端设备在第一目标TA接入PLMN，其中，目标TA为PLMN对应的第一目标TA。
本公开实施例中，核心网设备确定终端设备所处的目标TA的方法可以参见上述实施例中的相关描述，此处不再赘述。
其中，目标TA为PLMN对应的第一目标TA。
需要说明的是，本公开实施例中核心网设备确定终端设备所处的PLMN对应的第一目标TA的方法，与上述实施例中核心网设备确定终端设备所处的目标TA的方法相同，可以参见上述实施例中的相关描述，此处不再赘述。
本公开实施例中，核心网设备可以根据第一目标TA，以及禁止接入域信息，确定是否允许终端设备在第一目标TA接入PLMN。
在一些实施例中，核心网设备根据第一目标TA，以及禁止接入域信息，确定是否允许终端设备在第一目标TA接入PLMN，包括：
响应于第一目标TA包含在PLMN的禁止接入域，确定禁止终端设备在第一目标TA接入PLMN，其中，禁止接入域信息用于指示PLMN的禁止接入域；或
响应于第一目标TA未包含在PLMN的禁止接入域，确定允许终端设备在第一目标TA接入PLMN，其中，禁止接入域信息用于指示PLMN的禁止接入域。
本公开实施例中，禁止接入域信息用于指示PLMN的禁止接入域。
本公开实施例中，核心网设备可以根据第一目标TA，以及禁止接入域信息，确定是否允许终端设备在第一目标TA接入PLMN，其中，在第一目标TA包含在PLMN的禁止接入域的情况下，确定禁止终端设备在第一目标TA接入PLMN。
本公开实施例中，核心网设备可以根据第一目标TA，以及禁止接入域信息，确定是否允许终端设备在第一目标TA接入PLMN，其中，在第一目标TA未包含在PLMN的禁止接入域的情况下，确定允许终端设备在第一目标TA接入PLMN。
需要说明的是，本公开实施例中，S81可以单独被实施，也可以结合本公开实施例中的任何一个其 他步骤一起被实施，例如结合本公开实施例中的S21至S23和/或S41和/或S51和/或S61和/或S71与S72一起被实施，本公开实施例并不对此做出限定。
通过实施本公开实施例，终端设备根据第一目标TA，以及禁止接入域信息，确定是否接入PLMN，其中，目标TA为PLMN对应的第一目标TA。由此，在确定终端设备所处的目标TA的基础上，能够保证禁止接入域信息的准确控制，避免禁止接入域信息限制失效。
请参见图9，图9是本公开实施例提供的又一种移动性管理方法的流程图。
如图9所示，该方法由核心网设备执行，该方法可以包括但不限于如下步骤：
S91：核心网设备根据第二目标TA，以及服务域限制信息，确定是否允许终端设备在第二目标TA与RPLMN进行通信，其中，目标TA为RPLMN对应的第二目标TA。
本公开实施例中，核心网设备确定终端设备所处的目标TA的方法可以参见上述实施例中的相关描述，此处不再赘述。
其中，目标TA为RPLMN对应的第二目标TA。
需要说明的是，本公开实施例中核心网设备确定终端设备所处的RPLMN对应的第二目标TA的方法，与上述实施例中核心网设备确定终端设备所处的目标TA的方法相同，可以参见上述实施例中的相关描述，此处不再赘述。
本公开实施例中，核心网设备可以根据第二目标TA，以及服务域限制信息，确定是否允许终端设备在第二目标TA与RPLMN进行通信。
在一些实施例中，核心网设备根据第二目标TA，以及服务域限制信息，确定是否允许终端设备在第二目标TA与RPLMN进行通信，包括：
响应于第二目标TA包含在RPLMN的非允许区域，确定禁止终端设备在第二目标TA与RPLMN进行通信，其中，服务域限制信息用于指示RPLMN的非允许区域；或
响应于第二目标TA包含在RPLMN的非允许区域，确定禁止终端设备在第二目标TA与任何eRPLMN进行通信，其中，服务域限制信息用于指示RPLMN的非允许区域；或
响应于第二目标TA包含在RPLMN的允许区域，确定允许终端设备在第二目标TA与RPLMN进行通信，其中，服务域限制信息用于指示RPLMN的允许区域。
本公开实施例中，服务域限制信息用于指示RPLMN的非允许区域或用于指示RPLMN的允许区域。
本公开实施例中，核心网设备可以根据第二目标TA，以及服务域限制信息，确定是否允许终端设备在第二目标TA与RPLMN进行通信，其中，在第二目标TA包含在RPLMN的非允许区域的情况下，确定禁止终端设备在第二目标TA与RPLMN进行通信。
本公开实施例中，核心网设备可以根据第二目标TA，以及服务域限制信息，确定是否允许终端设备在第二目标TA与RPLMN进行通信，其中，在第二目标TA包含在RPLMN的非允许区域的情况下，确定禁止终端设备在第二目标TA与任何eRPLMN进行通信。
本公开实施例中，核心网设备可以根据第二目标TA，以及服务域限制信息，确定是否允许终端设备在第二目标TA与RPLMN进行通信，其中，在第二目标TA包含在RPLMN的允许区域的情况下，确定允许终端设备在第二目标TA与RPLMN进行通信。
可以理解的是，服务区域限制信息可能包含允许区域或非允许区域(例如使用跟踪区域标识指定)。
其中，允许区域：终端设备在这个区域中，被允许发起与网络的通信
其中，非允许区域：终端设备在这个区域内，处于服务被限制状态。不允许终端设备向网络发起服务请求，或对用户面数据、控制面数据的任何连接请求。
其中，可以使用跟踪区域标识指定允许区域和非允许区域。例如，允许区域可包含一个或多个(例如最多16个)TAs，或将所有TA都置于允许区域。
其中，核心网设备(AMF)可以根据终端设备订阅将服务区域限制信息分配给终端设备，并且可以根据需要进行更新。它可以通过注册程序或UCU程序提供给终端设备。当提供给终端设备时，它只能包含允许区域或非允许区域，而不能同时包含这两个区域。
如果终端设备使用卫星接入，且接入网设备向终端设备广播多个TAI，在所述终端设备接入网络的过程中，所述接入网设备将所述广播的多个TAI上报给核心网设备。核心网设备将执行如下服务区域限制规则：
如果所述所有广播的TAI都包含在非允许区域内，则所述终端设备和AMF都认为终端设备位于非允许区域内。
如果所述所有广播的TAI中至少有一个TAI不包含在非允许区域，则所述终端设备和AMF都认为终端设备位于允许区域内。
相关技术中，对于卫星接入网络被多个网络共享的情况(例如，PLMN-A和PLMN-B共享相同的卫星接入),
所述卫星接入向终端设备广播多个可用PLMN的TAI。在终端设备接入网络执行注册过程中，卫星接入设备将所述广播的多个TAI上报给核心网络，核心网络为其指定一个注册区域，除了注册的PLMN(RPLMN)之外，该注册区域还包含至少一个等效的注册PLMN(eRPLMN)，即注册区域载有一份包括来自RPLMN的TAI及等效的RPLMN的TAI列表。
同时，核心网络还为终端设备分配一个允许区域，所述允许区域也包含了RPLMN的TAI和eRPLMN的TAI。
其后，由于终端设备的移动，会出现如下情况：
1，接收的广播TAI中所有属于RPLMN的广播TAI都不在允许区域内。但是
2，在允许区域内至少包括一个属于一个eRPLMN的广播TAI。
在这种情况下，基于当前的解决方案。根据1，则位于当前位置的终端设备不允许与网络通信，而根据2，位于当前位置的终端设备可以使用eRPLMN进行通信。在这种情况下，对当前位置的终端设备执行服务区域限制无效。
基于此，本公开实施例中，核心网设备可以根据第二目标TA，以及服务域限制信息，确定是否允许终端设备在第二目标TA与RPLMN进行通信，其中，在第二目标TA包含在RPLMN的非允许区域的情况下，确定禁止终端设备在第二目标TA与任何eRPLMN进行通信，能够避免服务域限制失效。
并且，在一些实施例中，核心网设备在第二目标TA包含在RPLMN的允许区域的情况下，根据第三目标TA，以及服务域限制信息，确定是否允许终端设备在第三目标TA与eRPLMN进行通信，其中，目标TA为eRPLMN对应的第三目标TA。
其中，目标TA为eRPLMN对应的第三目标TA。
需要说明的是，本公开实施例中核心网设备确定终端设备所处的eRPLMN对应的第三目标TA的方法，与上述实施例中核心网设备确定终端设备所处的目标TA的方法相同，可以参见上述实施例中的相关描述，此处不再赘述。
本公开实施例中，在第二目标TA包含在一个RPLMN的允许区域的情况下，核心网设备可以根据第三目标TA，以及服务域限制信息，确定是否允许终端设备在第三目标TA与eRPLMN进行通信。
在一些实施例中，核心网设备根据第三目标TA，以及服务域限制信息，确定是否允许终端设备在第三目标TA与eRPLMN进行通信，包括：
响应于第三目标TA包含在eRPLMN的允许区域，确定允许终端设备在第三目标TA与eRPLMN进行通信，其中，服务域限制信息用于指示eRPLMN的允许区域；或
响应于第三目标TA包含在eRPLMN的非允许区域，确定禁止终端设备在第三目标TA与eRPLMN进行通信，其中，服务域限制信息用于指示eRPLMN的非允许区域。
本公开实施例中，服务域限制信息用于指示eRPLMN的非允许区域或用于指示eRPLMN的允许区域。
本公开实施例中，核心网设备可以根据第三目标TA，以及服务域限制信息，确定是否允许终端设备在第三目标TA与eRPLMN进行通信，其中，在第三目标TA包含在eRPLMN的允许区域的情况下，确定允许终端设备在第三目标TA与eRPLMN进行通信。
本公开实施例中，核心网设备可以根据第三目标TA，以及服务域限制信息，确定是否允许终端设备在第三目标TA与eRPLMN进行通信，其中，在第三目标TA包含在eRPLMN的非允许区域的情况下，确定禁止终端设备在第三目标TA与eRPLMN进行通信。
基于此，本公开实施例中，核心网设备在第二目标TA包含在一个RPLMN的允许区域的情况下，可以确定终端设备所处的eRPLMN对应的第三目标TA，根据第三目标TA，以及服务域限制信息，确定允许终端设备在第三目标TA与eRPLMN进行通信。其中，在第三目标TA包含在eRPLMN的允许区域的情况下，确定允许终端设备在第三目标TA与eRPLMN进行通信，在第三目标TA包含在eRPLMN的非允许区域的情况下，确定禁止终端设备在第三目标TA与eRPLMN进行通信。由此，能够避免服务域限制失效。
示例性地，如图10所示，本公开实施例提供一种核心网设备进行移动性管理的方法。
0、终端设备接入PLMN之后，终端设备需要发起服务请求已恢复用户面连接。终端设备获取当前位置信息(GNSS信息)，并根据GAD与TA的映射关系，确定终端设备当前所处的目标TA。
1、终端设备检查目标TA被RPLMN的非允许区域包含。此时，按照规则，终端设备在当前目标TA不会发起服务请求的过程，但是恶意的终端设备可能会发起上述过程。
2、终端设备在当前目标TA发起服务请求过程。
3、AMF获取终端设备所处的目标TA，并判断目标TA被RPLMN的非允许区域包含，AMF需要拒绝终端设备的服务请求。如果终端设备使用其他eRPLMN接入，如果终端设备的当前目标TA没有发生变化，则终端设备仍然处于RPLMN的非允许区域，此时终端设备使用其他eRPLMN接入，AMF仍然不允许发起服务请求过程。
4、AMF向终端设备返回服务拒绝消息。在服务拒绝消息中可以说明拒绝原因是由于终端设备处于非允许区域，不允许发起服务请求过程。
需要说明的是，本公开实施例中，S91可以单独被实施，也可以结合本公开实施例中的任何一个其他步骤一起被实施，例如结合本公开实施例中的S21至S23和/或S41和/或S51和/或S61和/或S71与S72和/或S81一起被实施，本公开实施例并不对此做出限定。
通过实施本公开实施例，核心网设备根据第二目标TA，以及服务域限制信息，确定是否允许终端设备在第二目标TA与RPLMN进行通信，其中，目标TA为RPLMN对应的第二目标TA。由此，在确定终端设备所处的目标TA的基础上，能够保证服务域限制信息的准确控制，避免服务域限制信息限制失效。
上述本公开提供的实施例中，分别从终端设备、核心网设备、以及终端设备与核心网设备交互的角度对本公开实施例提供的方法进行了介绍。
请参见图11，为本公开实施例提供的一种通信装置1的结构示意图。图11所示的通信装置1可包括收发模块11和处理模块12。收发模块可包括发送模块和/或接收模块，发送模块用于实现发送功能，接收模块用于实现接收功能，收发模块可以实现发送功能和/或接收功能。
通信装置1可以是终端设备，也可以是终端设备中的装置，还可以是能够与终端设备匹配使用的装置。或者，通信装置1可以是核心网设备，也可以是核心网设备中的装置，还可以是能够与核心网设备匹配使用的装置。
通信装置1为终端设备：
该装置，包括：收发模块11和处理模块12。
收发模块11，被配置为获取GAD与TA的映射关系。
处理模块12，被配置为根据映射关系，以及终端设备当前的GNSS信息，确定终端设备所处的目标TA。
在一些实施例中，处理模块12，还被配置为根据终端设备当前的GNSS信息，确定所对应的目标GAD；根据目标GAD和映射关系，确定终端设备所处的目标TA。
在一些实施例中，处理模块12，还被配置为根据第一目标TA，以及禁止接入域信息，确定是否接入公用陆地移动网络PLMN，其中，目标TA为PLMN对应的第一目标TA。
在一些实施例中，处理模块12，还被配置为响应于第一目标TA包含在PLMN的禁止接入域，确定禁止在第一目标TA接入PLMN；或响应于第一目标TA未包含在PLMN的禁止接入域，确定允许在第一目标TA接入PLMN，其中，禁止接入域信息用于指示PLMN的禁止接入域。
在一些实施例中，处理模块12，还被配置为根据第二目标TA，以及服务域限制信息，确定是否与已注册的公用陆地移动网络RPLMN进行通信，其中，目标TA为RPLMN对应的第二目标TA。
在一些实施例中，处理模块12，还被配置为响应于第二目标TA包含在RPLMN的非允许区域，确定禁止在第二目标TA与RPLMN进行通信，其中，服务域限制信息用于指示RPLMN的非允许区域；或响应于第二目标TA包含在RPLMN的非允许区域，确定禁止在第二目标TA与任何等效已注册的公用陆地移动网络eRPLMN进行通信，其中，服务域限制信息用于指示RPLMN的非允许区域；或响应于第二目标TA包含在RPLMN的允许区域，确定允许在第二目标TA与RPLMN进行通信，其中，服务域限制信息用于指示RPLMN的允许区域。
在一些实施例中，处理模块12，还被配置为在第二目标TA包含在一个RPLMN的允许区域的情况下，根据第三目标TA，以及服务域限制信息，确定是否与eRPLMN进行通信，其中，目标TA为eRPLMN对应的第三目标TA。
在一些实施例中，处理模块12，还被配置为响应于第三目标TA包含在eRPLMN的允许区域，确定允许在第三目标TA与eRPLMN进行通信，其中，服务域限制信息用于指示eRPLMN的允许区域；或响应于第三目标TA包含在eRPLMN的非允许区域，确定禁止在第三目标TA与eRPLMN进行通信，其中，服务域限制信息用于指示eRPLMN的非允许区域。
在一些实施例中，收发模块11，还被配置为向核心网设备上报终端设备的GNSS信息。
通信装置1为核心网设备：
该装置，包括：收发模块11和处理模块12。
处理模块12，被配置为获取GAD与TA的映射关系；
收发模块11，被配置为向终端设备发送GAD与TA的映射关系，其中，映射关系用于终端设备确定所处的目标TA。
通信装置1为核心网设备：
该装置，包括：收发模块11和处理模块12。
处理模块12，被配置为确定终端设备所处的目标TA中，其中，目标TA从终端设备接入网络所使用的接入网设备处获取，或者目标TA根据GAD与TA的映射关系，以及终端设备当前的GNSS信息确定。
在一些实施例中，收发模块11，被配置为接收终端设备上报的终端设备当前的GNSS信息。
在一些实施例中，处理模块12，还被配置为根据终端设备当前的GNSS信息，确定所对应的目标GAD；根据目标GAD和映射关系，确定终端设备所处的目标TA。
在一些实施例中，处理模块12，还被配置为根据第一目标TA，以及禁止接入域信息，确定是否允许终端设备在第一目标TA接入PLMN，其中，目标TA为PLMN对应的第一目标TA。
在一些实施例中，处理模块12，还被配置为响应于第一目标TA包含在PLMN的禁止接入域，确定禁止终端设备在第一目标TA接入PLMN，其中，禁止接入域信息用于指示PLMN的禁止接入域；或响应于第一目标TA未包含在PLMN的禁止接入域，确定允许终端设备在第一目标TA接入PLMN，其中，禁止接入域信息用于指示PLMN的禁止接入域。
在一些实施例中，处理模块12，还被配置为根据第二目标TA，以及服务域限制信息，确定是否允许终端设备在第二目标TA与RPLMN进行通信，其中，目标TA为RPLMN对应的第二目标TA。
在一些实施例中，处理模块12，还被配置为响应于第二目标TA包含在RPLMN的非允许区域，确定禁止终端设备在第二目标TA与RPLMN进行通信，其中，服务域限制信息用于指示RPLMN的非允许区域；或响应于第二目标TA包含在RPLMN的非允许区域，确定禁止终端设备在第二目标TA与任何eRPLMN进行通信，其中，服务域限制信息用于指示RPLMN的非允许区域；或响应于第二目标TA包含在RPLMN的允许区域，确定允许终端设备在第二目标TA与RPLMN进行通信，其中，服务域限制信息用于指示RPLMN的允许区域。
在一些实施例中，处理模块12，还被配置为在第二目标TA包含在RPLMN的允许区域的情况下，根据第三目标TA，以及服务域限制信息，确定是否允许终端设备在第三目标TA与eRPLMN进行通信，其中，目标TA为eRPLMN对应的第三目标TA。
在一些实施例中，处理模块12，还被配置为响应于第三目标TA包含在eRPLMN的允许区域，确定允许终端设备在第三目标TA与eRPLMN进行通信，其中，服务域限制信息用于指示eRPLMN的允许区域；或响应于第三目标TA包含在eRPLMN的非允许区域，确定禁止终端设备在第三目标TA与eRPLMN进行通信，其中，服务域限制信息用于指示eRPLMN的非允许区域。
关于上述实施例中的通信装置1，其中各个模块执行操作的具体方式已经在有关该方法的实施例中进行了详细描述，此处将不做详细阐述说明。
本公开上述实施例中提供的通信装置1，与上面一些实施例中提供的移动性限制实现方法或移动性管理方法取得相同或相似的有益效果，此处不再赘述。
请参见图12，图12是本公开实施例提供的另一种通信装置1000的结构示意图。通信装置1000可以是终端设备，也可以是核心网设备，也可以是支持终端设备实现上述方法的芯片、芯片系统、或处理器等，还可以是支持核心网设备实现上述方法的芯片、芯片系统、或处理器等。该通信装置1000可用于实现上述方法实施例中描述的方法，具体可以参见上述方法实施例中的说明。
通信装置1000可以包括一个或多个处理器1001。处理器1001可以是通用处理器或者专用处理器等。例如可以是基带处理器或中央处理器。基带处理器可以用于对通信协议以及通信数据进行处理，中央处理器可以用于对通信装置(如，核心网设备、基带芯片，终端设备、终端设备芯片，DU或CU等)进行控制，执行计算机程序，处理计算机程序的数据。
可选的，通信装置1000中还可以包括一个或多个存储器1002，其上可以存有计算机程序1004，存储器1002执行所述计算机程序1004，以使得通信装置1000执行上述方法实施例中描述的方法。可选的，所述存储器1002中还可以存储有数据。通信装置1000和存储器1002可以单独设置，也可以集成在一起。
可选的，通信装置1000还可以包括收发器1005、天线1006。收发器1005可以称为收发单元、收发机、或收发电路等，用于实现收发功能。收发器1005可以包括接收器和发送器，接收器可以称为接收机或接收电路等，用于实现接收功能；发送器可以称为发送机或发送电路等，用于实现发送功能。
可选的，通信装置1000中还可以包括一个或多个接口电路1007。接口电路1007用于接收代码指令并传输至处理器1001。处理器1001运行所述代码指令以使通信装置1000执行上述方法实施例中描述的方法。
通信装置1000为终端设备：收发器1005用于执行图2中的S22；图7中的S71；处理器1001用于执行图2中的S23：图4中的S41；图5中的S51。
通信装置1000为核心网设备：处理器1001用于执行图2中的S21：图6中的S61；图7中的S72；图8中的S81；图9中的S91；收发器1005用于执行图2中的S22；图7中的S71。
在一种实现方式中，处理器1001中可以包括用于实现接收和发送功能的收发器。例如该收发器可以是收发电路，或者是接口，或者是接口电路。用于实现接收和发送功能的收发电路、接口或接口电路可以是分开的，也可以集成在一起。上述收发电路、接口或接口电路可以用于代码/数据的读写，或者，上述收发电路、接口或接口电路可以用于信号的传输或传递。
在一种实现方式中，处理器1001可以存有计算机程序1003，计算机程序1003在处理器1001上运行，可使得通信装置1000执行上述方法实施例中描述的方法。计算机程序1003可能固化在处理器1001中，该种情况下，处理器1001可能由硬件实现。
在一种实现方式中，通信装置1000可以包括电路，所述电路可以实现前述方法实施例中发送或接收或者通信的功能。本公开中描述的处理器和收发器可实现在集成电路(integrated circuit，IC)、模拟IC、射频集成电路RFIC、混合信号IC、专用集成电路(application specific integrated circuit，ASIC)、印刷电路板(printed circuit board，PCB)、电子设备等上。该处理器和收发器也可以用各种IC工艺技术来制造，例如互补金属氧化物半导体(complementary metal oxide semiconductor，CMOS)、N型金属氧化物半导体(nMetal-oxide-semiconductor，NMOS)、P型金属氧化物半导体(positive channel metal oxide semiconductor，PMOS)、双极结型晶体管(bipolar junction transistor，BJT)、双极CMOS(BiCMOS)、硅锗(SiGe)、砷化镓(GaAs)等。
以上实施例描述中的通信装置可以是终端设备或核心网设备，但本公开中描述的通信装置的范围并不限于此，而且通信装置的结构可以不受图12的限制。通信装置可以是独立的设备或者可以是较大设备的一部分。例如所述通信装置可以是：
(1)独立的集成电路IC，或芯片，或，芯片系统或子系统；
(2)具有一个或多个IC的集合，可选的，该IC集合也可以包括用于存储数据，计算机程序的存储部件；
(3)ASIC，例如调制解调器(Modem)；
(4)可嵌入在其他设备内的模块；
(5)接收机、终端设备、智能终端设备、蜂窝电话、无线设备、手持机、移动单元、车载设备、网络设备、云设备、人工智能设备等等；
(6)其他等等。
对于通信装置可以是芯片或芯片系统的情况，请参见图13，为本公开实施例中提供的一种芯片的结构图。
芯片1100包括处理器1101和接口1103。其中，处理器1101的数量可以是一个或多个，接口1103的数量可以是多个。
对于芯片用于实现本公开实施例中终端设备的功能的情况：
接口1103，用于接收代码指令并传输至所述处理器。
处理器1101，用于运行代码指令以执行如上面一些实施例所述的移动性限制实现方法。
对于芯片用于实现本公开实施例中核心网设备的功能的情况：
接口1103，用于接收代码指令并传输至所述处理器。
处理器1101，用于运行代码指令以执行如上面一些实施例所述的移动性限制实现方法。
可选的，芯片1100还包括存储器1102，存储器1102用于存储必要的计算机程序和数据。
本领域技术人员还可以了解到本公开实施例列出的各种说明性逻辑块(illustrative logical block)和步骤(step)可以通过电子硬件、电脑软件，或两者的结合进行实现。这样的功能是通过硬件还是软件来实现取决于特定的应用和整个系统的设计要求。本领域技术人员可以对于每种特定的应用，可以使用各种方法实现所述的功能，但这种实现不应被理解为超出本公开实施例保护的范围。
本公开实施例还提供一种移动性限制实现系统，该系统包括前述图11实施例中作为终端设备的通信装置和作为核心网设备的通信装置，或者，该系统包括前述图12实施例中作为终端设备的通信装置和作为核心网设备的通信装置。
本公开还提供一种可读存储介质，其上存储有指令，该指令被计算机执行时实现上述任一方法实施 例的功能。
本公开还提供一种计算机程序产品，该计算机程序产品被计算机执行时实现上述任一方法实施例的功能。
在上述实施例中，可以全部或部分地通过软件、硬件、固件或者其任意组合来实现。当使用软件实现时，可以全部或部分地以计算机程序产品的形式实现。所述计算机程序产品包括一个或多个计算机程序。在计算机上加载和执行所述计算机程序时，全部或部分地产生按照本公开实施例所述的流程或功能。所述计算机可以是通用计算机、专用计算机、计算机网络、或者其他可编程装置。所述计算机程序可以存储在计算机可读存储介质中，或者从一个计算机可读存储介质向另一个计算机可读存储介质传输，例如，所述计算机程序可以从一个网站站点、计算机、服务器或数据中心通过有线(例如同轴电缆、光纤、数字用户线(digital subscriber line，DSL))或无线(例如红外、无线、微波等)方式向另一个网站站点、计算机、服务器或数据中心进行传输。所述计算机可读存储介质可以是计算机能够存取的任何可用介质或者是包含一个或多个可用介质集成的服务器、数据中心等数据存储设备。所述可用介质可以是磁性介质(例如，软盘、硬盘、磁带)、光介质(例如，高密度数字视频光盘(digital video disc，DVD))、或者半导体介质(例如，固态硬盘(solid state disk，SSD))等。
本领域普通技术人员可以理解：本公开中涉及的第一、第二等各种数字编号仅为描述方便进行的区分，并不用来限制本公开实施例的范围，也表示先后顺序。
本公开中的至少一个还可以描述为一个或多个，多个可以是两个、三个、四个或者更多个，本公开不做限制。在本公开实施例中，对于一种技术特征，通过“第一”、“第二”、“第三”、“A”、“B”、“C”和“D”等区分该种技术特征中的技术特征，该“第一”、“第二”、“第三”、“A”、“B”、“C”和“D”描述的技术特征间无先后顺序或者大小顺序。
本公开中各表所示的对应关系可以被配置，也可以是预定义的。各表中的信息的取值仅仅是举例，可以配置为其他值，本公开并不限定。在配置信息与各参数的对应关系时，并不一定要求必须配置各表中示意出的所有对应关系。例如，本公开中的表格中，某些行示出的对应关系也可以不配置。又例如，可以基于上述表格做适当的变形调整，例如，拆分，合并等等。上述各表中标题示出参数的名称也可以采用通信装置可理解的其他名称，其参数的取值或表示方式也可以通信装置可理解的其他取值或表示方式。上述各表在实现时，也可以采用其他的数据结构，例如可以采用数组、队列、容器、栈、线性表、指针、链表、树、图、结构体、类、堆、散列表或哈希表等。
本公开中的预定义可以理解为定义、预先定义、存储、预存储、预协商、预配置、固化、或预烧制。
本领域普通技术人员可以意识到，结合本文中所公开的实施例描述的各示例的单元及算法步骤，能够以电子硬件、或者计算机软件和电子硬件的结合来实现。这些功能究竟以硬件还是软件方式来执行，取决于技术方案的特定应用和设计约束条件。专业技术人员可以对每个特定的应用来使用不同方法来实现所描述的功能，但是这种实现不应认为超出本公开的范围。
所属领域的技术人员可以清楚地了解到，为描述的方便和简洁，上述描述的系统、装置和单元的具体工作过程，可以参考前述方法实施例中的对应过程，在此不再赘述。
以上所述，仅为本公开的具体实施方式，但本公开的保护范围并不局限于此，任何熟悉本技术领域的技术人员在本公开揭露的技术范围内，可轻易想到变化或替换，都应涵盖在本公开的保护范围之内。因此，本公开的保护范围应以所述权利要求的保护范围为准。

Claims (25)

  1. 一种移动性限制实现方法，其特征在于，所述方法由终端设备执行，包括：
    获取地理区域描述GAD与跟踪区TA的映射关系；
    根据所述映射关系，以及所述终端设备当前的全球卫星导航系统GNSS信息，确定所述终端设备所处的目标TA。
  2. 如权利要求1所述的方法，其特征在于，所述根据所述映射关系，以及所述终端设备当前的GNSS信息，确定所述终端设备所处的目标TA，包括：
    根据所述终端设备当前的GNSS信息，确定所对应的目标GAD；
    根据所述目标GAD和所述映射关系，确定所述终端设备所处的所述目标TA。
  3. 如权利要求1或2所述的方法，其特征在于，所述方法还包括：
    根据第一目标TA，以及禁止接入域信息，确定是否接入公用陆地移动网络PLMN，其中，所述目标TA为所述PLMN对应的所述第一目标TA。
  4. 如权利要求3所述的方法，其特征在于，所述根据所述第一目标TA，以及禁止接入域信息，确定是否接入所述PLMN，包括以下至少一项：
    响应于所述第一目标TA包含在所述PLMN的禁止接入域中，确定禁止在所述第一目标TA接入所述PLMN；
    响应于所述第一目标TA未包含在所述PLMN的禁止接入域中，确定允许在所述第一目标TA接入所述PLMN，其中，所述禁止接入域信息用于指示所述PLMN的禁止接入域。
  5. 如权利要求1至4中任一项所述的方法，其特征在于，所述方法还包括：
    根据第二目标TA，以及服务域限制信息，确定是否与已注册的公用陆地移动网络RPLMN进行通信，其中，所述目标TA为所述RPLMN对应的所述第二目标TA。
  6. 如权利要求1至5中任一项所述的方法，其特征在于，所述根据所述第二目标TA，以及服务域限制信息，确定是否与RPLMN进行通信，包括以下中的至少一项：
    响应于所述第二目标TA包含在所述RPLMN的非允许区域中，确定禁止在所述第二目标TA与所述RPLMN进行通信，其中，所述服务域限制信息用于指示所述RPLMN的非允许区域；
    响应于所述第二目标TA包含在所述RPLMN的非允许区域中，确定禁止在所述第二目标TA与任何等效已注册的公用陆地移动网络eRPLMN进行通信，其中，所述服务域限制信息用于指示所述RPLMN的非允许区域；
    响应于所述第二目标TA包含在所述RPLMN的允许区域中，确定允许在所述第二目标TA与所述RPLMN进行通信，其中，所述服务域限制信息用于指示所述RPLMN的允许区域。
  7. 如权利要求6所述的方法，其特征在于，所述方法还包括：
    在所述第二目标TA包含在所述RPLMN的允许区域的情况下，根据第三目标TA，以及服务域限制信息，确定是否与eRPLMN进行通信，其中，所述目标TA为所述eRPLMN对应的所述第三目标TA。
  8. 如权利要求7所述的方法，其特征在于，所述根据所述第三目标TA，以及服务域限制信息，确定是否与eRPLMN进行通信，包括以下中的至少一项：
    响应于所述第三目标TA包含在所述eRPLMN的允许区域中，确定允许在所述第三目标TA与所述eRPLMN进行通信，其中，所述服务域限制信息用于指示所述eRPLMN的允许区域；
    响应于所述第三目标TA包含在所述eRPLMN的非允许区域中，确定禁止在所述第三目标TA与所述eRPLMN进行通信，其中，所述服务域限制信息用于指示所述eRPLMN的非允许区域。
  9. 如权利要求1至8中任一项所述的方法，其特征在于，所述方法还包括：
    向所述核心网设备上报所述终端设备的GNSS信息。
  10. 一种移动性限制实现方法，其特征在于，所述方法由核心网设备执行，包括：
    获取地理区域描述GAD与跟踪区TA的映射关系；
    向终端设备发送GAD与TA的映射关系，其中，所述映射关系用于使所述终端设备确定所处的目标TA。
  11. 一种移动性限制实现方法，其特征在于，所述方法由核心网设备执行，包括：
    确定终端设备所处的目标TA，其中，所述目标TA从所述终端设备接入网络所使用的接入网设备处获取，或者所述目标TA根据地理区域描述GAD与跟踪区TA的映射关系，以及终端设备当前的GNSS信息确定。
  12. 如权利要求11所述的方法，其特征在于，所述方法还包括：
    接收所述终端设备上报的所述终端设备当前的GNSS信息。
  13. 如权利要求11或12所述的方法，其特征在于，所述方法还包括：
    根据所述终端设备当前的GNSS信息，确定所对应的目标GAD；
    根据所述目标GAD和所述映射关系，确定所述终端设备所处的所述目标TA。
  14. 如权利要求11至13中任一项所述的方法，其特征在于，所述方法还包括：
    根据第一目标TA，以及禁止接入域信息，确定是否允许所述终端设备在所述第一目标TA接入PLMN，其中，所述目标TA为所述PLMN对应的所述第一目标TA。
  15. 如权利要求14所述的方法，其特征在于，所述根据第一目标TA，以及禁止接入域信息，确定是否允许所述终端设备在所述第一目标TA接入PLMN，包括：
    响应于所述第一目标TA包含在所述PLMN的禁止接入域中，确定禁止所述终端设备在所述第一目标TA接入所述PLMN，其中，所述禁止接入域信息用于指示所述PLMN的禁止接入域；或
    响应于所述第一目标TA未包含在所述PLMN的禁止接入域中，确定允许所述终端设备在所述第一目标TA接入所述PLMN，其中，所述禁止接入域信息用于指示所述PLMN的禁止接入域。
  16. 如权利要求11至15中任一项所述的方法，其特征在于，所述方法还包括：
    根据第二目标TA，以及服务域限制信息，确定是否允许所述终端设备在所述第二目标TA与RPLMN进行通信，其中，所述目标TA为所述RPLMN对应的所述第二目标TA。
  17. 如权利要求16所述的方法，其特征在于，所述根据所述第二目标TA，以及服务域限制信息，确定是否允许所述终端设备在所述第二目标TA与RPLMN进行通信，包括：
    响应于所述第二目标TA包含在所述RPLMN的非允许区域中，确定禁止所述终端设备在所述第二目标TA与所述RPLMN进行通信，其中，所述服务域限制信息用于指示所述RPLMN的非允许区域；或
    响应于所述第二目标TA包含在所述RPLMN的非允许区域中，确定禁止所述终端设备在所述第二目标TA与任何eRPLMN进行通信，其中，所述服务域限制信息用于指示所述RPLMN的非允许区域；或
    响应于所述第二目标TA包含在所述RPLMN的允许区域中，确定允许所述终端设备在所述第二目标TA与所述RPLMN进行通信，其中，所述服务域限制信息用于指示所述RPLMN的允许区域。
  18. 如权利要求16所述的方法，其特征在于，所述方法还包括：
    在所述第二目标TA包含在所述RPLMN的允许区域的情况下，根据所述第三目标TA，以及服务域限制信息，确定是否允许所述终端设备在所述第三目标TA与eRPLMN进行通信，其中，所述目标TA为所述eRPLMN对应的所述第三目标TA。
  19. 如权利要求18所述的方法，其特征在于，所述根据所述第三目标TA，以及服务域限制信息，确定是否允许所述终端设备在所述第三目标TA与eRPLMN进行通信，包括：
    响应于所述第三目标TA包含在所述eRPLMN的允许区域中，确定允许所述终端设备在所述第三目标TA与所述eRPLMN进行通信，其中，所述服务域限制信息用于指示所述eRPLMN的允许区域；或
    响应于所述第三目标TA包含在所述eRPLMN的非允许区域中，确定禁止所述终端设备在所述第三目标TA与所述eRPLMN进行通信，其中，所述服务域限制信息用于指示所述eRPLMN的非允许区 域。
  20. 一种通信装置，其特征在于，所述装置包括：
    收发模块，被配置为获取GAD与TA的映射关系；
    处理模块，被配置为根据所述映射关系，以及所述终端设备当前的GNSS信息，确定所述终端设备所处的目标TA。
  21. 一种通信装置，其特征在于，所述装置包括：
    处理模块，被配置为获取GAD与TA的映射关系；
    收发模块，被配置为向终端设备发送GAD与TA的映射关系，其中，所述映射关系用于所述终端设备确定所处的目标TA。
  22. 一种通信装置，其特征在于，所述装置包括：
    处理模块，被配置为确定终端设备所处的目标TA，其中，所述目标TA从所述终端设备接入网络所使用的接入网设备处获取，或者所述目标TA根据地理区域描述GAD与跟踪区TA的映射关系，以及终端设备当前的GNSS信息确定。
  23. 一种通信装置，其特征在于，所述装置包括处理器和存储器，所述存储器中存储有计算机程序，所述处理器执行所述存储器中存储的计算机程序，以使所述装置执行如权利要求1至9中任一项所述的方法，或所述处理器执行所述存储器中存储的计算机程序，以使所述装置执行如权利要求10至19中任一项所述的方法。
  24. 一种通信装置，其特征在于，包括：处理器和接口电路；
    所述接口电路，用于接收代码指令并传输至所述处理器；
    所述处理器，用于运行所述代码指令以执行如权利要求1至9中任一项所述的方法，或用于运行所述代码指令以执行如权利要求10至19中任一项所述的方法。
  25. 一种计算机可读存储介质，用于存储有指令，当所述指令被执行时，使如权利要求1至9中任一项所述的方法被实现，或当所述指令被执行时，使如权利要求10至19中任一项所述的方法被实现。
PCT/CN2022/126524 2022-10-20 2022-10-20 移动性限制实现方法和装置 WO2024082233A1 (zh)

Priority Applications (2)

Application Number Priority Date Filing Date Title
PCT/CN2022/126524 WO2024082233A1 (zh) 2022-10-20 2022-10-20 移动性限制实现方法和装置
CN202280004349.5A CN115997416A (zh) 2022-10-20 2022-10-20 移动性限制实现方法和装置

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/CN2022/126524 WO2024082233A1 (zh) 2022-10-20 2022-10-20 移动性限制实现方法和装置

Publications (1)

Publication Number Publication Date
WO2024082233A1 true WO2024082233A1 (zh) 2024-04-25

Family

ID=85993909

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2022/126524 WO2024082233A1 (zh) 2022-10-20 2022-10-20 移动性限制实现方法和装置

Country Status (2)

Country Link
CN (1) CN115997416A (zh)
WO (1) WO2024082233A1 (zh)

Citations (7)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20150245256A1 (en) * 2014-02-21 2015-08-27 Apple Inc. Mitigating no-service delays for LTE capable wireless devices without LTE access permission
CN111586582A (zh) * 2019-02-15 2020-08-25 华为技术有限公司 确定跟踪区域的方法、终端设备和核心网设备
CN111713128A (zh) * 2019-06-17 2020-09-25 Oppo广东移动通信有限公司 用于确定、发送策略的方法及设备
CN112806095A (zh) * 2018-09-27 2021-05-14 中兴通讯股份有限公司 基于地理位置的跟踪区域管理
CN114616768A (zh) * 2019-11-07 2022-06-10 高通股份有限公司 用于支持5g卫星无线电接入技术的系统和方法
CN114979936A (zh) * 2021-02-18 2022-08-30 大唐移动通信设备有限公司 Plmn选择方法、装置、终端及amf
US20220303887A1 (en) * 2019-10-03 2022-09-22 Nokia Technologies Oy Plmn selection based on the geo-localisation of a user equipment

Patent Citations (7)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20150245256A1 (en) * 2014-02-21 2015-08-27 Apple Inc. Mitigating no-service delays for LTE capable wireless devices without LTE access permission
CN112806095A (zh) * 2018-09-27 2021-05-14 中兴通讯股份有限公司 基于地理位置的跟踪区域管理
CN111586582A (zh) * 2019-02-15 2020-08-25 华为技术有限公司 确定跟踪区域的方法、终端设备和核心网设备
CN111713128A (zh) * 2019-06-17 2020-09-25 Oppo广东移动通信有限公司 用于确定、发送策略的方法及设备
US20220303887A1 (en) * 2019-10-03 2022-09-22 Nokia Technologies Oy Plmn selection based on the geo-localisation of a user equipment
CN114616768A (zh) * 2019-11-07 2022-06-10 高通股份有限公司 用于支持5g卫星无线电接入技术的系统和方法
CN114979936A (zh) * 2021-02-18 2022-08-30 大唐移动通信设备有限公司 Plmn选择方法、装置、终端及amf

Also Published As

Publication number Publication date
CN115997416A (zh) 2023-04-21

Similar Documents

Publication Publication Date Title
WO2024065842A1 (zh) 路径添加方法和装置
WO2024026890A1 (zh) 一种定位方法/装置/设备及存储介质
WO2024077455A1 (zh) 一种非陆地网络的接入方法及装置
WO2024092523A1 (zh) 侧行链路定位消息的发送方法、接收方法及其装置
WO2024082233A1 (zh) 移动性限制实现方法和装置
WO2024092578A1 (zh) 一种服务区域限制信息的创建方法及其装置
WO2024050778A1 (zh) 一种人工智能服务策略的更新方法及装置
WO2024065229A1 (zh) 侧行链路sl定位方法和装置
WO2024164346A1 (zh) 一种网络标识的传输方法及其装置
WO2024145902A1 (zh) 密钥获取方法、装置、设备及芯片系统
WO2024065098A1 (zh) 一种迁移的方法及装置
WO2024148489A1 (zh) 一种个人物联网网络pin元素注册的方法及通信装置
WO2024016191A1 (zh) 一种限制信息确定方法/装置/设备及存储介质
WO2023184191A1 (zh) 一种扩展现实多媒体xrm业务的处理方法及其装置
WO2024130561A1 (zh) 一种用户位置信息的可信确定方法及其装置
EP4443979A1 (en) Cell determination method and apparatus
WO2024138338A1 (zh) 一种服务调用方法/装置/设备及存储介质
WO2024092818A1 (zh) 同步源选择方法和装置
WO2024138581A1 (zh) 一种网络切片的授权方法、装置、设备及存储介质
WO2024092820A1 (zh) 一种托管网络确定方法、装置、设备及存储介质
WO2024197472A1 (zh) 一种算力登记与注销方法、装置及存储介质
WO2023225826A1 (zh) 定位系统信息的获取方法和装置
WO2023225878A1 (zh) 一种ai网络功能的重新认证授权方法/装置/设备及存储介质
WO2024000198A1 (zh) 连接控制方法、装置、设备及存储介质
WO2024182954A1 (zh) 感知节点发现方法及其装置

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 22962420

Country of ref document: EP

Kind code of ref document: A1