Location-based service management

Abstract

Various example embodiments of the present disclosure relate to location-based service management. In one aspect, a first network device receives first coarse location information of a terminal device during a service attempt procedure for the terminal device. Then, based on an event that the terminal device is not located within an area in which the terminal device is allowed to be served, the first network device initiates a detach procedure for the terminal device, wherein the determination of the event is based on the first coarse location information.

Description

Technical Field

[0001] The various example embodiments described in this disclosure relate to the field of communications, and particularly, but not limited to, terminal devices, network devices, methods, apparatuses, and computer-readable storage media for location-based service management. Background Technology

[0002] A communication network can be viewed as a facility that enables communication between two or more communication devices. Mobile or wireless communication networks are an example of communication networks. Communication devices may be provided with services by application servers.

[0003] Such communication networks operate according to standards such as those issued by 3GPP (3rd Generation Partnership Project) or ETSI (European Telecommunications Standards Institute). Examples of standards include the so-called 5G (fifth generation) standard provided by 3GPP. Summary of the Invention

[0004] The various exemplary embodiments described herein provide certain advantages, such as in the form of one or more improvements which are explicitly described herein or will be apparent to those skilled in the art in light of this disclosure. Therefore, at least some of these exemplary embodiments are intended to provide (or otherwise facilitate) at least some of these foregoing advantages and improvements.

[0005] Typically, the example embodiments of this disclosure provide solutions(s) related to location-based service management, such as for meeting compliance requirements regarding national borders.

[0006] Some exemplary embodiments of this disclosure will be described with reference to certain aspects. These aspects are not intended to indicate key or essential features of the various exemplary embodiments of this disclosure, nor are they intended to be used to limit its scope. In view of this disclosure, other features, aspects, and elements will be apparent to those skilled in the art. For example, it should be understood that additional aspects may be provided by combination of any two or more aspects described below.

[0007] In a first aspect, a first network device is provided. The first network device includes at least one processor and at least one memory storing instructions, which, when executed by the at least one processor, cause the first network device to at least: receive first coarse location information of the terminal device from the terminal device during a service attempt process for the terminal device; and initiate a separation process for the terminal device based on an event that the terminal device is not located in an area where the terminal device is permitted to be served, wherein the determination of the event is based on the first coarse location information.

[0008] In a second aspect, a second network device is provided. The second network device includes at least one processor and at least one memory storing instructions, which, when executed by the at least one processor, cause the second network device to at least: receive first coarse location information of a terminal device from a first network device; determine, based on the first coarse location information, whether the terminal device is located within an area where the terminal device is permitted to be served; and, based on the determination that the terminal device is not located within the area, send a cancellation location message to the first network device for detaching the terminal device.

[0009] In a third aspect, a third network device is provided. The third network device includes at least one processor and at least one memory storing instructions, which, when executed by the at least one processor, cause the third network device to at least: receive from a first network device a request for cell information associated with a terminal device, wherein the cell information is determined based on first coarse location information received from the terminal device; and send the cell information to the first network device to indicate the coverage area of ​​the cell in which the terminal device is located.

[0010] In a fourth aspect, a fourth network device is provided. The fourth network device includes at least one processor and at least one memory storing instructions, which, when executed by the at least one processor, cause the fourth network device to at least: receive first coarse location information of a terminal device from a first network device; and, based on the first coarse location information, send a response to the first network device including at least one of country / region information or international / region information, wherein the at least one of the country / region information or international / region information is used to determine the area where the terminal device is permitted to be served.

[0011] In a fifth aspect, a terminal device is provided. The terminal device includes at least one processor and at least one memory storing instructions, which, when executed by the at least one processor, cause the terminal device to at least: send first coarse location information of the terminal device to a first network device; and receive, from the first network device, a portion or all of a portion or all of a second coarse location information of an area where the terminal device is permitted to be served, the second coarse location information being used to attach or detach the terminal device.

[0012] In a sixth aspect, a method is provided. The method includes: receiving first coarse location information of the terminal device from the terminal device at a first network device during a service attempt process for the terminal device; and initiating a separation process for the terminal device based on an event that the terminal device is not located in an area where the terminal device is permitted to be served, wherein the determination of the event is based on the first coarse location information.

[0013] In a seventh aspect, a method is provided. The method includes: receiving first coarse location information of a terminal device from a first network device at a second network device; determining, based on the first coarse location information, whether the terminal device is located within an area where the terminal device is permitted to be served; and sending a cancel location message to the first network device based on the determination that the terminal device is not located within the area, for the purpose of separating the terminal device.

[0014] In an eighth aspect, a method is provided. The method includes: receiving, at a third network device, a request from a first network device for cell information associated with a terminal device, wherein the cell information is determined based on first coarse location information received from the terminal device; and sending the cell information to the first network device to indicate the coverage area of ​​the cell in which the terminal device is located.

[0015] In a ninth aspect, a method is provided. The method includes: receiving first coarse location information of a terminal device from a first network device at a fourth network device; and sending a response to the first network device based on the first coarse location information, including at least one of country area information or international area information, wherein the at least one of country area information or international area information is used to determine the area where the terminal device is permitted to be served.

[0016] In a tenth aspect, a method is provided. The method includes: sending first coarse location information of the terminal device to a first network device from a terminal device; and receiving, from the first network device, part or all of a second coarse location information of an area where the terminal device is permitted to be served, wherein part or all of the second coarse location information is used to attach or detach the terminal device.

[0017] In an eleventh aspect, an apparatus is provided. The apparatus includes: means for receiving first coarse location information of the terminal device from the terminal device at a first network device during a service attempt process for the terminal device; and means for initiating a separation process for the terminal device based on an event that the terminal device is not located in an area where the terminal device is permitted to be served, wherein the determination of the event is based on the first coarse location information.

[0018] In a twelfth aspect, an apparatus is provided. The apparatus includes: components for receiving first coarse location information of a terminal device from a first network device at a second network device; components for determining, based on the first coarse location information, whether the terminal device is located within an area where the terminal device is permitted to be served; and components for sending a cancel location message to the first network device to separate the terminal device based on the determination that the terminal device is not located within the area.

[0019] In a thirteenth aspect, an apparatus is provided. The apparatus includes: components for receiving, at a third network device, a request from a first network device for cell information associated with a terminal device, wherein the cell information is determined based on first coarse location information received from the terminal device; and components for sending the cell information to the first network device to indicate the coverage area of ​​the cell in which the terminal device is located.

[0020] In a fourteenth aspect, an apparatus is provided. The apparatus includes: components for receiving first coarse location information of a terminal device from a first network device at a fourth network device; and components for sending a response to the first network device based on the first coarse location information, including at least one of country area information or international area information, wherein the at least one of the country area information or international area information is used to determine the area where the terminal device is permitted to be served.

[0021] In a fifteenth aspect, an apparatus is provided. The apparatus includes: components for transmitting first coarse location information of a terminal device to a first network device at a terminal device; and components for receiving, from the first network device, a portion or all of a second coarse location information of an area where the terminal device is permitted to be served, wherein the portion or all of the second coarse location information is used to attach or detach the terminal device.

[0022] In a sixteenth aspect, a non-transitory computer-readable medium is provided, comprising program instructions for causing an apparatus to perform at least the method according to any one of the sixth, seventh, eighth, ninth, and tenth aspects described above.

[0023] In a seventeenth aspect, a first network device is provided. The first network device includes: a receiving circuit system configured to receive first coarse location information of a terminal device from the terminal device during a service attempt process for the terminal device; and an initiating circuit system configured to initiate a separation process for the terminal device based on an event that the terminal device is not located within an area where the terminal device is permitted to be served, wherein the determination of the event is based on the first coarse location information.

[0024] In an eighteenth aspect, a second network device is provided. The second network device includes: a receiving circuit system configured to receive first coarse location information of a terminal device from a first network device; a determining circuit system configured to determine, based on the first coarse location information, whether the terminal device is located within an area where the terminal device is permitted to be served; and a transmitting circuit system configured to send a cancel location message to the first network device to separate the terminal device based on the determination that the terminal device is not located within the area.

[0025] In a nineteenth aspect, a third network device is provided. The third network device includes: a receiving circuit system configured to receive from a first network device a request for cell information associated with a terminal device, wherein the cell information is determined based on first coarse location information received from the terminal device; and a transmitting circuit system configured to transmit the cell information to the first network device to indicate the coverage area of ​​the cell in which the terminal device is located.

[0026] In a twentieth aspect, a fourth network device is provided. The fourth network device includes: a receiving circuit system configured to receive first coarse location information of a terminal device from a first network device; and a transmitting circuit system configured to send a response to the first network device based on the first coarse location information, including at least one of country area information or international area information, wherein the at least one of the country area information or international area information is used to determine the area where the terminal device is permitted to be served.

[0027] In a twenty-first aspect, a terminal device is provided. The terminal device includes: a transmitting circuit system configured to transmit first coarse location information of the terminal device to a first network device; and a receiving circuit system configured to receive, from the first network device, a portion or all of a second coarse location information of an area where the terminal device is permitted to be served, wherein the second coarse location information is used to attach or detach the terminal device.

[0028] In a twenty-second aspect, a computer program including instructions is provided, which, when executed by a device, cause the device to perform at least the method according to any one of the sixth, seventh, eighth, ninth, and tenth aspects described above.

[0029] Various other aspects and additional examples are also described in the following detailed description and the appended claims.

[0030] The subject matter of the independent claims is provided according to several aspects. Several other aspects are defined in the dependent claims. Any examples that do not fall within the scope of the claims are to be interpreted as examples helpful in understanding this disclosure.

[0031] As previously stated, it should be understood that the summary portion is not intended to identify key or essential features of the embodiments of this disclosure, nor is it intended to limit its scope. Other features, aspects, and elements of this disclosure will become clear in light of the following. Attached Figure Description

[0032] Some exemplary embodiments will now be described by way of illustration and non-limiting example only, with reference to the accompanying drawings, in which:

[0033] Figure 1The illustrations show example communication networks in which some exemplary embodiments of this disclosure may be implemented;

[0034] Figure 2 The illustration shows a scenario in which location-based service management according to some example embodiments of the present disclosure can be applied;

[0035] Figures 3A-3E Each illustrates a signaling diagram, which encapsulates a process for location-based service management according to some example embodiments of this disclosure;

[0036] Figure 4 The illustration shows a flowchart of a method implemented at a network device according to some example embodiments of the present disclosure;

[0037] Figure 5 The illustration shows a flowchart of a method implemented at another network device according to some example embodiments of the present disclosure;

[0038] Figure 6 The illustration shows a flowchart of a method implemented at another network device according to some example embodiments of the present disclosure;

[0039] Figure 7 The illustration shows a flowchart of a method implemented at another network device according to some example embodiments of the present disclosure;

[0040] Figure 8 The illustration shows a flowchart of a method implemented at a terminal device according to some example embodiments of the present disclosure;

[0041] Figure 9 A simplified block diagram of a device suitable for implementing exemplary embodiments of the present disclosure is illustrated; and

[0042] Figure 10 A block diagram of an example computer-readable medium according to some example embodiments of the present disclosure is illustrated.

[0043] Throughout the accompanying drawings, the same or similar reference numerals denote the same or similar elements. Detailed Implementation

[0044] Various exemplary embodiments of this disclosure will now be described further. It should be understood that these exemplary embodiments are described for illustrative purposes only and are intended to assist those skilled in the art in understanding and implementing the various exemplary embodiments of this disclosure, without implying any specific limitation on their scope. The exemplary embodiments described herein can also be implemented in various ways other than those described below.

[0045] The terminology used herein is generally used only for the purpose of describing certain exemplary embodiments and is not intended to be limiting. In the following description and claims, unless otherwise defined, all technical and scientific terms used herein have the same meaning as commonly understood by one of ordinary skill in the art to which this disclosure pertains.

[0046] In this disclosure, references to "an embodiment," "an embodiment," "an example embodiment," "some example embodiments," "certain example embodiments," "various example embodiments," etc., indicate that the described embodiments may include (multiple) specific features, structures, or characteristics, but not every embodiment or example embodiment necessarily includes (multiple) specific features, structures, or characteristics. Furthermore, such phrases do not necessarily refer to the same embodiment or example embodiment. Additionally, when (multiple) specific features, structures, or characteristics are described in conjunction with embodiments or example embodiments, it is considered that combining such features, structures, or characteristics in conjunction with other embodiments or example embodiments described herein is within the knowledge of those skilled in the art, regardless of whether such combinations are explicitly described.

[0047] It should be understood that although the terms "first" and "second," etc., may be used herein to describe various elements, these elements should not be limited by these terms. These terms are used only to distinguish one element from another. For example, without departing from the scope of the various example embodiments, a first element may be referred to as a second element, and similarly, a second element may be referred to as a first element.

[0048] The terminology used herein is for the purpose of describing particular embodiments only and is not intended to limit the exemplary embodiments. As used herein, the singular forms “a,” “an,” and “the” are also intended to include the plural forms unless the context otherwise requires. It should also be understood that the terms “comprises,” “comprising,” “has,” “having,” “includes,” and / or “including,” when used herein, specify the presence of the stated features, elements, and / or components, but do not exclude the presence or addition of one or more other features, elements, components, and / or combinations thereof.

[0049] As used herein, “at least one of the following: ” and “at least one of ” and similar expressions (where the list of two or more elements is connected by “and” or “or”) mean at least any one of these elements, or at least any two or more of these elements, or at least all of these elements. As used herein, the expression “and / or” includes any and all combinations of the listed terms, including at least one of these elements, or at least two or more of these elements, or at least all of these elements. As used herein, the term “or” means a non-exclusive “or” unless otherwise specified (e.g., using “otherwise” or “or in alternatives”).

[0050] As used herein, unless explicitly stated otherwise, performing a feature, step, or function in response to A does not indicate that the feature, step, or function is performed immediately after A occurs, because one or more intermediate features, steps, or functions may be included between the occurrence of the feature, step, or function and A (at least in part). Similarly, performing a feature, step, or function based on A does not indicate that the feature, step, or function is performed solely based on A, because the feature, step, or function may be based at least in part on one or more other features, steps, or functions in addition to A.

[0051] As used herein, the term "circuit system" may refer to one or more of the following example embodiments: (a) Hardware circuit implementation only (such as implementation in analog and / or digital circuit systems only), and (b) A combination of hardware circuitry and software, such as (if applicable): (i) A combination of (multiple) analog and / or digital hardware circuits and software / firmware, and (ii) Any portion of the hardware processor(s) having software (including (multiple) digital signal processors), software, and (multiple) memories, which work together to enable a device (such as a mobile phone or server) to perform various functions, and (c) (multiple) hardware circuits and / or (multiple) processors, such as (multiple) microprocessors or a portion thereof, which require software (e.g., firmware) to operate, but may be absent when operation does not require the software.

[0052] This definition of circuit system applies to all uses of the term herein, including in any claim. As another example, as used herein, the term circuit system also covers only hardware circuitry or a processor (or processors), or a portion of hardware circuitry or a processor and its accompanying software and / or firmware. The term circuit system also covers (e.g., and if applicable to a particular claim element) baseband integrated circuits or processor integrated circuits for mobile devices, or similar integrated circuits in servers, cellular network devices, or other computing or networking devices.

[0053] As used herein, the term "communication network" refers to a network that conforms to any suitable communication standard, such as Long Term Evolution (LTE), LTE-A Advanced (LTE-A), Wideband Code Division Multiplexing (WCDMA), High-Speed ​​Packet Access (HSPA), Narrowband Internet of Things (NB-IoT), etc. Furthermore, communication between terminal devices and network devices in a communication network can be performed according to any suitable generation of communication protocols, including but not limited to first-generation (1G), second-generation (2G), 2.5G, 2.75G, third-generation (3G), fourth-generation (4G), 4.5G, fifth-generation (5G), sixth-generation (6G) communication protocols, and / or any other protocols currently known or to be developed in the future. Various exemplary embodiments of this disclosure can be applied to various communication systems. Given the rapid development of communication, future types of communication technologies and systems will naturally exist, and this disclosure can be embodied using these future types of communication technologies and systems. This should not be construed as limiting the scope of this disclosure to the aforementioned communication technologies and systems.

[0054] As used herein, the term "network device" or "network element" refers to a node in a communication network through which terminal devices access the network and receive services. A communication network may include a core network (CN). A communication network may include a radio access network (RAN). Network devices in the RAN may refer to base stations (BS) or access points (APs), such as Node B (NodeB or NB), evolved Node B (eNodeB or eNB), New Radio (NR), Next Generation Node B (e.g., gNB), Remote Radio Unit (RRU), Radio Header (RH), Remote Radio Header (RRH), relays, low-power nodes (such as femtoseconds, picoseconds), etc., depending on the terminology and technology applied.

[0055] The term "terminal device" refers to any terminal device that can be configured to perform wireless communication. By way of example embodiments, a terminal device may also be referred to as a communication device, user equipment (UE), subscriber station (SS), portable subscriber station, mobile station (MS), or access terminal (AT). Terminal devices may include, but are not limited to, mobile phones, cellular phones, smartphones, VoIP phones, wireless local loop phones, tablets, wearable terminal devices, personal digital assistants (PDAs), portable computers, desktop computers, image capture terminal devices (such as digital cameras), gaming terminal devices, music storage and playback devices, in-vehicle wireless terminal devices, wireless endpoints, mobile stations, laptop embedded devices (LEEs), laptop mounted devices (LMEs), USB dongles, smart devices, wireless customer premises equipment (CPEs), Internet of Things (IoT) devices, watches or other wearable devices, head-mounted displays (HMDs), vehicles, drones, medical devices and applications (e.g., remote surgery), industrial devices and applications (e.g., robots and / or other wireless devices operating in industrial and / or automated processing chain environments), consumer electronics devices, devices operating on commercial and / or industrial wireless networks, etc. As used herein, the terms “terminal equipment,” “communication equipment,” “terminal,” “user equipment,” and “UE” are used interchangeably.

[0056] In the field of communications, continuous development is underway to provide enhanced (e.g., efficient and reliable) solutions for utilizing wireless communication networks. Each new generation presents the technical challenges of handling the different situations and processes used to connect and serve devices connected to wireless networks. To meet the demands of increased wireless data services since the deployment of fourth-generation (4G) communication systems, efforts are ongoing to develop improved fifth-generation (5G) or pre-6G communication systems. These new communication systems can support a wide range of service applications for terminal devices.

[0057] Figure 1 The illustration shows a schematic diagram of an example communication environment 100 in which some example embodiments of this disclosure can be implemented. For example... Figure 1 As shown, the communication environment 100 may involve terminal equipment 110, core network (CN) 120, and network entity 130.

[0058] like Figure 1As shown, terminal device 110 is illustrated as a mobile phone. It should be noted that terminal device 110 can be any other suitable type of terminal device. For example, CN 120 can provide user authentication, access authorization, tracking, IP connectivity, and other access, routing, or mobility functions. CN 120 may include a Mobility Management Entity (MME) 121, a Home Subscriber Server (HSS) 122, an Evolved Serving Mobility Location Center (E-SMLC) 123, a Serving Gateway (S-GW), or a Packet Data Network (PDN) Gateway (P-GW). In some example embodiments, the control plane entity may manage non-access stratum (NAS) functions, such as mobility, authentication, and bearer management (e.g., data bearer, signal bearer, etc.) for terminal device 110 served by network entity 130 associated with CN 120.

[0059] Network entity 130 described herein may include or be referred to as a network node, base station, network element, radio access network (RAN), base transceiver station, access point, NodeB, eNodeB (eNB), next-generation NodeB (gNB), or other suitable terms. Network entity 130 and terminal device 110 may communicate via communication link 110 (which may be wireless or wired). For example, network entity 130 and terminal device 110 may perform wireless communication (e.g., receive signaling, send signaling) via a Uu interface.

[0060] In a non-terrestrial network (NTN) scenario, network entity 130 can be implemented as a satellite. The satellite-based network entity 130 can communicate directly with terminal device 110 using the NR / LTE Uu interface. The satellite can be a transparent satellite or a regenerated satellite. For an NTN with a transparent satellite, the base station on Earth can communicate with the terminal device via the satellite. For example, communication links between the satellite and the terminal device, between the satellite and the base station on Earth, and between the base station on Earth and the core network 120 can be used in NTN transparent mode. For an NTN with a regenerated satellite, the base station can be airborne and communicate directly with the terminal device. For example, communication links between the satellite and the terminal device, and between the satellite (all or part of the eNB / gNB airborne) and the core network 120 can be used in NTN regenerated mode.

[0061] It should be understood that these devices are for illustrative purposes only and do not imply any specific limitations. The communication environment 100 may include any suitable number or type of devices(s) configured to implement the exemplary embodiments of this disclosure.

[0062] Communications in Environment 100 may follow any suitable communication standards or protocols that exist or will be developed in the future, such as Universal Mobile Telecommunications System (UMTS), Long Term Evolution (LTE), LTE-Advanced (LTE-A), 5G New Radio (NR), Wi-Fi, and WiMAX standards, and employ any suitable communication technologies, including, for example, Multiple-Input Multiple-Output (MIMO), Orthogonal Frequency Division Multiplexing (OFDM), Time Division Multiplexing (TDM), Frequency Division Multiplexing (FDM), Code Division Multiplexing (CDM), Bluetooth, ZigBee, and Machine-Type Communication (MTC), Enhanced Mobile Broadband (eMBB), Massive Machine-Type Communication (mMTC), Ultra-Reliable Low-Latency Communication (URLLC), Carrier Aggregation (CA), Dual Connectivity (DC), and New Radio Unlicensed (NR-U) technologies.

[0063] Figure 2 The illustration shows a scenario in which location-based service management, according to some example embodiments of the present disclosure, can be applied. For example... Figure 2 As shown, the coverage of satellite 130 can span two countries, one of which cannot be served due to regulatory restrictions, such as a prohibited country, while the other country can be served by satellite 130, such as a permitted country. Terminal equipment (UE) 110 can be located in the regulatory area where service is not permitted.

[0064] Regarding basic regulatory compliance, determining which jurisdiction UE 110 is located in can be challenging (if not impossible) when the NTN cell coverage overlaps with two regulatory regions (e.g., across borders) and the UE's location is unknown. In the worst case, if the jurisdiction where UE 110 is located is unclear, the network may be unable to provide service to avoid violating regulations. Furthermore, in cases where the coverage area spans various regulatory regions, the UE's location needs to be verified for each UE within that region.

[0065] As mentioned above, NTN cell coverage can span multiple regulatory areas, some of which may have restrictions prohibiting service provision. Without UE location information, the network may be unable to determine whether UE 110 is permitted to be served. Furthermore, Narrowband Internet of Things (NB-IoT) does not support the LTE Location Protocol (LPP) stack and therefore cannot provide its location to the network via Location Services (LCS). However, NB-IoT devices can estimate their location based on the Global Navigation Satellite System (GNSS) and can send their approximate location to the RAN.

[0066] Using positioning-based GNSS estimation, coarse location information can be obtained in the field. coarseLocationInfThe field is indicated in o. This field can be encoded as an ellipsoidal point information element (IE). The first / leftmost bit of the first octet contains the most significant bit. degreesLatitude and degreesLongitude The least significant bit is set to 0 to meet accuracy requirements corresponding to a granularity of approximately 2 km. How many LSBs are set to 0 to meet the accuracy requirements depends on the UE implementation. Following a network request and after access stratum (AS) security is established in connected mode, low-complexity user equipment (BL UE) with reduced bandwidth and UEs within enhanced coverage can report their coarse UE location information (e.g., the most significant bit of GNSS coordinates to ensure accuracy on the order of 2 km) to the eNB, if available.

[0067] Since NB-IoT UEs do not use AS security, exposing the user's coarse location via the air interface is insecure for privacy reasons. Therefore, improved UE management is needed when AS security is disabled and the UE does not support the LTE positioning protocol. Furthermore, it is desirable to determine when to decouple the UE from the network if it is accessing from an unauthorized region / country.

[0068] In view of the foregoing, according to some example embodiments of this disclosure, multiple solutions for location-based service management are provided, particularly (but not limited to), to meet compliance requirements of respecting national borders while serving a UE. In these multiple solutions, the UE reports its coarse location information and can be attached to permitted areas or detached from permitted areas. In this way, for example, the UE does not access the NTN from a non-permitted area, thereby meeting compliance requirements. Example embodiments of this disclosure will be further described below with reference to the accompanying drawings.

[0069] Further details of some exemplary embodiments of this disclosure will be referred to Figures 3A-3E To describe. Figures 3A-3E Signaling diagrams are shown, illustrating some example procedures for location-based service management according to some example embodiments of this disclosure. Procedures 300-304 will be referenced for discussion purposes only. Figure 1 To describe. Processes 300-304 may involve Figure 1 The diagrams include terminal device 110, MME 121 (corresponding to the first network device), HSS 122 (corresponding to the second network device), RAN 130 (corresponding to the third network device), and E-SMLC 123 (corresponding to the fourth network device). It should be understood that any graphic elements, numerical values, and descriptive text in these diagrams are for illustrative purposes only and do not imply any specific limitations.

[0070] If the UE attempts to access a service from the network, such as during an attachment procedure, service request procedure, or tracking area update procedure, it is necessary to determine whether terminal device 110 meets compliance requirements. In this case, terminal device 110 may be controlled to send its coarse location information to determine whether it is permitted to be served. Further details are described below.

[0071] In process 300, MME 121 receives (310) coarse location information of terminal device 110 from terminal device 110 during a service attempt for the terminal device (e.g., during an attachment process, a service request process, or a tracking area update process). More specifically, for example, if terminal device 110 moves from an allowed location to a prohibited location in idle mode and connected mode. Here, an allowed location may refer to an allowed area or allowed geographic location or allowed country, and a prohibited location may refer to a prohibited area or prohibited geographic location or prohibited country. An allowed area or allowed geographic location or allowed country is an area or geographic location or country where terminal device 110 is allowed to be served. A prohibited area or prohibited geographic location or prohibited country is an area or geographic location or country where terminal device 110 is not allowed to be served, or an area or geographic location or country other than an allowed area or allowed geographic location or allowed country.

[0072] In the example embodiment, the coarse location information of terminal device 110 may be sent along with a security mode completion message during the attachment process for terminal device 110. The security mode completion message is a Non-Access Stratum (NAS) security mode completion message sent from terminal device 110 to MME 121, as described in step 5a of the attachment process in 3GPP TS 23.401. Furthermore, the security mode completion message may refer to section 7.2.4.4 of 3GPP TS 33.401. The location included in the coarse location information described herein may refer to GNSS coordinates rather than a 3GPP-based area, such as a cell area or tracking area.

[0073] Next, based on an event that terminal device 110 is not located within the area where the terminal device is permitted to be served (also known as the permitted area), MME 121 initiates (320) a separation process for terminal device 110. The determination of this event is based at least on coarse location information of terminal device 110.

[0074] In some example embodiments, for example, in such Figure 3BIn process 301 shown, MME 121 can determine (3201) whether terminal device 110 is located within an allowed area based on the approximate location information of the region and the approximate location information of terminal device 110. For example, the approximate location information of the region may include coordinates for a list of ellipsoidal points for the region. The approximate location information of terminal device 110 may include coordinates for the ellipsoidal points where terminal device 110 is located. If the coordinates of terminal device 110 do not belong to the list of ellipsoidal points for the allowed area, then MME 121 can determine that terminal device 110 is not located within an allowed area, and vice versa.

[0075] In the example embodiment, the approximate location information of the region can be considered as the local configuration of the MME 121. Based on its local configuration (e.g., a list of allowed country locations containing ellipsoidal points, or a list of prohibited country locations containing ellipsoidal points), the MME 121 can determine whether the terminal device 110 is accessing from a prohibited region, or a prohibited geographic location, or a prohibited country.

[0076] If terminal device 110 is not in an allowed area, or if terminal device 110 is in a prohibited area, MME 121 may initiate (3202) a disconnection procedure for terminal device 110. If terminal device 110 is in an allowed area, or if terminal device 110 is not in a prohibited area, MME 121 may continue a service attempt procedure for terminal device 110, such as an attachment procedure, a mobility procedure, or a service request procedure for terminal device 110.

[0077] In other words, if terminal device 110 is not located in a prohibited area, prohibited geographical location, or prohibited country, MME 121 can continue the service attempt process, such as the attachment process. It should be understood that, to avoid obscuring the various exemplary embodiments of this disclosure, further details regarding the attachment process can be found in section 5.3.2.1 of 3GPP TS 23.401, and these details will not be repeated herein. If terminal device 110 is located in a prohibited area, prohibited geographical location, or prohibited country, MME 121 can initiate (3202) a disengagement process for terminal device 110. In this way, deregistration is based on local configuration.

[0078] Furthermore, in the example embodiment, MME 121 may send (330) a portion or all of the coarse location information of the permitted areas to the terminal device. This coarse location information can be used to attach or detach the terminal device. In other words, for example, when detaching the terminal device 110, MME 121 may send a complete or partial list of prohibited coarse location information to the terminal device 110. This complete or partial list of prohibited coarse location information will help the terminal device 110 avoid attempting a service attempt process (e.g., an attachment process) until it is in a permitted location.

[0079] In some example embodiments, MME 121 can reuse the configuration of the RAN's coarse location and cell ID to avoid large configurations of GNSS data. MME 121 receives the coarse location and sends it to RAN 130 for mapping cell ID information. If the cell ID indicates a service-restricted cell, terminal device 110 is deregistered.

[0080] In such Figure 3C In the illustrated process 302, MME 121 can acquire cell information associated with terminal device 110. The cell information is determined based on coarse location information of an allowed area. The allowed area can be determined based on service restriction information received from HSS 122. The coarse location information of the allowed area can be configured within MME 121 based on the cell information.

[0081] Specifically, MME 121 can send (3203) a request for cell information to RAN 130 via a new message (i.e., a request message configured for a request for cell information) or an additional information element (IE) in a location request message. More specifically, after MME 121 receives the coarse location information of terminal device 110 via a secure mode completion message, MME 121 can request RAN 130 to provide information about the cell to which terminal device 110 is mapped (i.e., mapped cell information, such as mapped cell ID information) based on the coarse location information from terminal device 110. The cell can be used to indicate the coverage area of ​​the cell to which terminal device 110 is located. Furthermore, the cell can be provided by a non-terrestrial network. Here, RAN 130 can support local configuration for coarse location and mapped cells.

[0082] In response to the request, RAN 130 may send (3204) mapped cell information in a new message (i.e., the message configured for the request) or in an uplink (UL) non-access stratum (NAS) message using a location report control message or user location information (ULI). On the other side of the communication, MME 121 may receive (3204) cell information from RAN 130 via at least one of the following: a response message to the request message, a location report control message, or a UL NAS message.

[0083] Then, MME 121 can determine (3205) whether the coverage area of ​​the cell indicated by the cell information belongs to an allowed area. For example, based on service restriction information received from HSS 122, as described in step 11 of the attachment process in 3GPP TS 23.401, MME 121 can determine whether the mapped cell belongs to an allowed area for terminal device 110.

[0084] If the coverage area of ​​the mapped cell is not within the permitted area, that is, if terminal device 110 is located in the prohibited area, then MME 121 can determine (3206) that terminal device 110 is not located within the permitted area. In this case, MME 121 can initiate (3207) a separation process for terminal device 110.

[0085] It should be understood that process 302 can also be described using prohibited areas. For example, a list of prohibited coarse location information can be locally configured within MME 121 based on mapped cell information reported by RAN 130. A portion of the list can indicate adjacent coordinates that terminal device 110 is not allowed to be served. For brevity, other details can be found in the description above.

[0086] Similarly, MME 121 may send part or all of the approximate location information of the permitted area to the terminal device (330), which causes the terminal device 110 not to attempt a service attempt process (e.g., attachment process) when it is not located in the permitted area.

[0087] In some example embodiments, in such Figure 3D In process 303 shown, MME 121 can send (3208) coarse location information of terminal device 110 to HSS 122. For example, when terminal device 110 sends its Rough position At any time after the Security Mode Completion (SMC) in step 5a, the MME 121 may, in the update location request in step 8 of the attachment procedure in 3GPP TS 23.401, [the location may be specified]. Rough position Information is transparently transmitted to HSS 121.

[0088] In this scenario, HSS 122 gains a new capability to determine whether the approximate location of terminal device 110 is within an permitted country. Specifically, HSS 122 can receive (3208) the approximate location information of terminal device 110 from MME 121. Then, based on the approximate location information of terminal device 110, HSS 122 can determine (3209) whether terminal device 110 is within an permitted area. Based on the determination that terminal device 110 is not within an permitted area, HSS 122 can send (3210) a location cancellation message to MME 121 to separate the terminal device. In other words, for example, if the approximate location of terminal device 110 is not within a permitted country, HSS 122 can use the location cancellation message to respond or flag associated services.

[0089] On the other side of the communication, MME 121 receives (3210) a location cancellation message. After receiving the location cancellation message, MME 121 can initiate (3211) a detachment process for terminal device 110. Additionally, HSS 122 can send service restriction information to MME 121. Part or all of the service restriction information is used to attach or detach terminal device 110. For example, HSS 122 can send service-restricted cell ID information to MME 121. If HSS 122 has already responded using a list of service-restricted cell IDs, MME 121 will send (330) that list to terminal device 110. Using the list of service-restricted cell IDs, terminal device 110 will not attempt to attach or request service when served by any cell in that list.

[0090] In some example embodiments, MME 121 can send to E-SMLC 123 Rough position The information is used to verify the location, and E-SMLC 123 will return the country or international area information.

[0091] In such Figure 3E In the illustrated process 304, MME 121 may send (3212) coarse location information of terminal device 110 to E-SMLC 123. For example, this could be done at any time after MME 121 receives a location from terminal device 110. Rough position When the information is received, MME 121 can send the coarse location information to E-SMLC 123, for example, in step 2 as described in Clause 9.1.17 of 3GPP TS23.271. On the E-SMLC 123 side, based on the coarse location information of terminal device 110, E-SMLC 123 can return country / region information and / or international / region information.

[0092] On the other side of the communication, MME 121 can receive a response (3213) from E-SMLC 123. The response includes at least one of country area information or international area information. At least one of the country area information or international area information is used to determine the permitted area, for example, permitted country or permitted international area.

[0093] Based on the E-SMLC response, MME 121 may decide whether to keep terminal device 110 attached or disconnect it from the network. If terminal device 110 is not located in an authorized area indicated by national area information or international area information or both, MME 121 may initiate (3214) a disconnection process for terminal device 110.

[0094] In addition, E-SMLC 123 can also provide a list of adjacent coordinates at which terminal device 110 is not permitted to be served, i.e., sending coarse location information of permitted areas to MME 121. Part or all of the coarse location information of permitted areas is used to attach or detach terminal device 110. MME 121 can send (330) this list to terminal device 110 in a detachment request. This will help terminal device 110 not retry registration before leaving these coordinates.

[0095] Using the above solution, MME 121 can utilize new service restriction data included in the user's subscription. When deregistration is triggered due to regulatory requirements, a new deregistration message or optional IE can be configured to include a list of allowed / restricted areas containing GNSS coordinates. Terminal device 110 can be provided with policies regarding (multiple) restricted areas (e.g., restricted areas represented by GNSS locations or approximate locations). This will help terminal device 110 avoid retries of (multiple) service requests or (multiple) registration requests when deregistered from the network after entering a restricted area.

[0096] Figure 4 A flowchart of an example method 400 implemented at a first network device according to some example embodiments of the present disclosure is shown. For discussion purposes, method 400 will be referred to... Figure 1 Described from the perspective of MME 121.

[0097] At box 410, during a service attempt process for the terminal device, MME 121 receives first coarse location information of the terminal device from the terminal device. At box 420, based on an event that the terminal device is not located within an area where the terminal device is permitted to be served, MME 121 initiates a separation process for the terminal device, wherein the determination of the event is based on the first coarse location information.

[0098] In some example embodiments, MME 121 initiates a separation process for the terminal device by: determining whether the terminal device is located within the region based on second and first coarse location information of the region; and initiating a separation process for the terminal device based on the determination that the terminal device is not located within the region.

[0099] In some example embodiments, the region is determined based on service restriction information received from the second network device, and the MME 121 determines that the terminal device is not located in the region by: obtaining cell information associated with the terminal device, wherein the cell information is determined based on first coarse location information; determining whether the coverage area of ​​the cell indicated by the cell information belongs to the region; and determining that the terminal device is not located in the region based on the determination that the coverage area of ​​the cell does not belong to the region.

[0100] In some example embodiments, MME 121 obtains cell information by sending a request for cell information to a third network device via an additional information element in a request message or a location request message configured for the request for cell information; and receives cell information from the third network device via at least one of the following: a response message to the request message, a location report control message, or an uplink (UL) non-access stratum (NAS) message.

[0101] In some example embodiments, the second coarse location information of the area is configured within the first network device based on cell information.

[0102] In some example implementations, the cell is provided by a non-terrestrial network.

[0103] In some example embodiments, MME 121 initiates a separation process for the terminal device by: sending first coarse location information to a second network device; receiving a cancel location message from the second network device based on determining that the terminal device is not located in the area; and initiating a separation process for the terminal device based on receiving the cancel location message.

[0104] In some example embodiments, MME 121 initiates a separation process for a terminal device by: sending first coarse location information to a fourth network device; receiving a response from the fourth network device including at least one of country area information or international area information; and initiating a separation process for the terminal device based on the response.

[0105] In some example embodiments, MME 121 also continues the service attempt process for the terminal device based on determining that the terminal device is located in the area.

[0106] In some example embodiments, the MME 121 also sends part or all of the second coarse location information of the region to the terminal device.

[0107] In some example embodiments, the second coarse location information includes coordinates for a list of ellipsoidal points for the region.

[0108] Figure 5 A flowchart of an example method 500 implemented at a second network device according to some example embodiments of the present disclosure is shown. For discussion purposes, method 500 will refer to Figure 1 Described from the perspective of HSS 122.

[0109] At box 510, HSS 122 receives first coarse location information of the terminal device from the first network device. At box 520, HSS 122 determines, based on the first coarse location information, whether the terminal device is located within an area where the terminal device is permitted to be served. At box 530, based on the determination that the terminal device is not located within the area, HSS 122 sends a cancel location message to the first network device to detach the terminal device.

[0110] In some example embodiments, HSS 122 also sends service restriction information to the first network device, some or all of which is used to attach or detach terminal devices.

[0111] In some example embodiments, service limitation information includes coordinates for a list of ellipsoidal points for the region.

[0112] Figure 6 A flowchart of an example method 600 implemented at a third network device according to some example embodiments of the present disclosure is shown. For discussion purposes, method 600 will be referred to... Figure 1 Described from the perspective of RAN 130.

[0113] At block 610, HSS 122 receives from the first network device a request for cell information associated with the terminal device, wherein the cell information is determined based on first coarse location information received from the terminal device. At block 620, HSS 122 sends the cell information to the first network device to indicate the coverage area of ​​the cell in which the terminal device is located.

[0114] In some example implementations, the cell is provided by a non-terrestrial network.

[0115] Figure 7 A flowchart of an example method 700 implemented at a fourth network device according to some example embodiments of the present disclosure is shown. Reference will be made to this flowchart for discussion purposes. Figure 1 Method 700 is described from the perspective of E-SMLC 123.

[0116] At block 710, E-SMLC 123 receives first coarse location information of the terminal device from the first network device. At block 720, based on the first coarse location information, E-SMLC 123 sends a response to the first network device including at least one of country area information or international area information, wherein at least one of the country area information or international area information is used to determine the area where the terminal device is allowed to be served.

[0117] In some example embodiments, the E-SMLC 123 also sends a second coarse location information of the area to the first network device, part or all of which of the second coarse location information is used to attach or detach terminal devices.

[0118] In some example embodiments, the second coarse location information includes coordinates for a list of ellipsoidal points for the region.

[0119] Figure 8 A flowchart of an example method 800 implemented at a terminal device according to some example embodiments of the present disclosure is shown. For discussion purposes, method 800 will refer to Figure 1 Described from the perspective of terminal device 110.

[0120] At block 810, terminal device 110 sends first coarse location information of the terminal device to the first network device. At block 820, terminal device 110 receives part or all of second coarse location information of the area where the terminal device is allowed to be served from the first network device, and part or all of the second coarse location information is used to attach or detach the terminal device.

[0121] In some example embodiments, the second coarse location information includes coordinates for a list of ellipsoidal points for the region.

[0122] In some example embodiments, the apparatus configured to perform method 400 (e.g., MME 121) may include components for performing the corresponding steps of method 400. The components may be implemented in any suitable form. For example, the components may be implemented in a circuit system or a software module.

[0123] In some example embodiments, the apparatus includes: means for receiving first coarse location information of the terminal device from the terminal device at a first network device during a service attempt process for the terminal device; and means for initiating a separation process for the terminal device based on an event that the terminal device is not located in an area where the terminal device is allowed to be served, wherein the determination of the event is based on the first coarse location information.

[0124] In some example embodiments, the components for initiating a separation process for a terminal device include: components for determining whether the terminal device is located within the area based on second coarse location information and first coarse location information of the area; and components for initiating a separation process for the terminal device based on determining that the terminal device is not located within the area.

[0125] In some example embodiments, the region is determined based on service restriction information received from a second network device, and the components for determining that the terminal device is not located within the region include: components for obtaining cell information associated with the terminal device, wherein the cell information is determined based on first coarse location information; components for determining whether the coverage area of ​​the cell indicated by the cell information belongs to the region; and components for determining that the terminal device is not located within the region based on the determination that the coverage area of ​​the cell does not belong to the region.

[0126] In some example embodiments, the components for obtaining cell information include: components for sending a request for cell information to a third network device via additional information elements in a request message or a location request message configured for a request for cell information; and components for receiving cell information from the third network device via at least one of the following: a response message to the request message, a location report control message, or an uplink (UL) non-access stratum (NAS) message.

[0127] In some example embodiments, the second coarse location information of the area is configured within the first network device based on cell information.

[0128] In some example implementations, the cell is provided by a non-terrestrial network.

[0129] In some example embodiments, the components for initiating a separation process for a terminal device include: components for sending first coarse location information to a second network device; components for receiving a cancel location message sent from the second network device based on determining that the terminal device is not located in the area; and components for initiating a separation process for the terminal device based on receiving the cancel location message.

[0130] In some example embodiments, the components for initiating a separation process for a terminal device include: components for sending first coarse location information to a fourth network device; components for receiving a response from the fourth network device including at least one of country area information or international area information; and components for initiating a separation process for the terminal device based on the response.

[0131] In some example embodiments, the apparatus further includes a component for continuing the service attempt process for the terminal device based on determining that the terminal device is located within the area.

[0132] In some example embodiments, the apparatus further includes a component for transmitting a portion or all of a second coarse location information of the area to a terminal device.

[0133] In some example embodiments, the second coarse location information includes coordinates for a list of ellipsoidal points for the region.

[0134] In some example embodiments, the apparatus further includes components for performing other steps in some example embodiments of method 400. In some example embodiments, the components include at least one processor and at least one memory including computer program code, the at least one memory and the computer program code being configured, together with the at least one processor, to cause execution of the apparatus.

[0135] In some example embodiments, the apparatus configured to perform method 500 (e.g., HSS 122) may include components for performing corresponding steps of method 500. These components may be implemented in any suitable form. For example, the components may be implemented in a circuit system or a software module.

[0136] In some example embodiments, the apparatus includes: components for receiving first coarse location information of a terminal device from a first network device; components for determining, based on the first coarse location information, whether the terminal device is located within an area where the terminal device is permitted to be served; and components for sending a cancel location message to the first network device to separate the terminal device based on the determination that the terminal device is not located within the area.

[0137] In some example embodiments, the apparatus further includes a component for sending service restriction information to a first network device, wherein part or all of the service restriction information is used to attach or detach the terminal device.

[0138] In some example embodiments, service limitation information includes coordinates for a list of ellipsoidal points for the region.

[0139] In some example embodiments, the apparatus further includes components for performing other steps in some example embodiments of method 500. In some example embodiments, the components include at least one processor and at least one memory including computer program code, the at least one memory and the computer program code being configured, together with the at least one processor, to cause execution of the apparatus.

[0140] In some example embodiments, the apparatus configured to perform method 600 (e.g., RAN 130) may include components for performing corresponding steps of method 600. The components may be implemented in any suitable form. For example, the components may be implemented in a circuit system or a software module.

[0141] In some example embodiments, the apparatus includes: components for receiving from a first network device a request for cell information associated with a terminal device, wherein the cell information is determined based on first coarse location information received from the terminal device; and components for sending the cell information to the first network device to indicate the coverage area of ​​the cell in which the terminal device is located.

[0142] In some example implementations, the cell is provided by a non-terrestrial network.

[0143] In some example embodiments, the apparatus further includes components for performing additional steps in some example embodiments of method 600. In some example embodiments, the components include at least one processor and at least one memory including computer program code, the at least one memory and the computer program code being configured, together with the at least one processor, to cause execution of the apparatus.

[0144] In some example embodiments, the apparatus configured to perform method 700 (e.g., E-SMLC 123) may include components for performing the corresponding steps of method 700. The components may be implemented in any suitable form. For example, the components may be implemented in a circuit system or a software module.

[0145] In some example embodiments, the apparatus includes: components for receiving first coarse location information of a terminal device from a first network device; and components for sending a response to the first network device based on the first coarse location information, including at least one of country area information or international area information, wherein at least one of the country area information or international area information is used to determine the area where the terminal device is permitted to be served.

[0146] In some example embodiments, the apparatus further includes a component for transmitting a second coarse location information of a region to a first network device, wherein a portion or all of the second coarse location information is used to attach or detach the terminal device.

[0147] In some example embodiments, the second coarse location information includes coordinates for a list of ellipsoidal points for the region.

[0148] In some example embodiments, the apparatus further includes components for performing additional steps in some example embodiments of method 700. In some example embodiments, the components include at least one processor and at least one memory including computer program code, the at least one memory and the computer program code being configured, together with the at least one processor, to cause execution of the apparatus.

[0149] In some example embodiments, the apparatus configured to perform method 800 (e.g., terminal device 110) may include components for performing corresponding steps of method 800. The components may be implemented in any suitable form. For example, the components may be implemented in a circuit system or a software module.

[0150] In some example embodiments, the apparatus includes: components for transmitting first coarse location information of a terminal device to a first network device; and components for receiving a portion or all of a second coarse location information of an area where the terminal device is permitted to be served from the first network device, wherein the portion or all of the second coarse location information is used to attach or detach the terminal device.

[0151] In some example embodiments, the second coarse location information includes coordinates for a list of ellipsoidal points for the region.

[0152] In some example embodiments, the apparatus also includes components for performing other steps in some example embodiments of method 800. In some embodiments, the components include at least one processor and at least one memory including computer program code, the at least one memory and the computer program code being configured, together with the at least one processor, to cause execution of the apparatus.

[0153] Figure 9 This is a simplified block diagram of a device 900 suitable for implementing an example embodiment of the present disclosure. Device 900 can be provided to implement a communication device, such as... Figure 1 The terminal device 110, MME 121, HSS 122, E-SMLC 123, or RAN 130 are shown. As shown, device 900 includes one or more processors 910, one or more memories 920 coupled to processor 910, and one or more communication modules 940 coupled to processor 910.

[0154] The communication module 940 is used for bidirectional communication. The communication module 940 has at least one antenna to facilitate communication. The communication interface can represent any interface required for communication with other network elements.

[0155] Processor 910 can be of any type suitable for a local technology network, and by way of non-limiting and illustrative example, can include one or more of the following: general-purpose computer, special-purpose computer, microprocessor, digital signal processor (DSP), and processor based on a multi-core processor architecture. Device 900 can have multiple processors, such as application-specific integrated circuit chips that are time-dependent on a clock synchronized with the main processor.

[0156] Memory 920 may include one or more non-volatile memories and one or more volatile memories. Examples of non-volatile memories include, but are not limited to: read-only memory (ROM) 924, electrically programmable read-only memory (EPROM), flash memory, hard disk, compact disc (CD), digital video disc (DVD), and other magnetic storage devices and / or optical storage devices. Examples of volatile memories include, but are not limited to: random access memory (RAM) 922 and other volatile memories that will not persist during power outages.

[0157] Computer program 930 includes computer-executable instructions that are executed by the associated processor 910. Program 930 may be stored in ROM 924. Processor 910 may perform any appropriate actions and processes by loading program 930 into RAM 922.

[0158] The exemplary embodiments of this disclosure can be implemented by program 930, such that device 900 can execute the reference Figures 2 to 8 Any process discussed in this disclosure. Exemplary embodiments of this disclosure may also be implemented by hardware or by a combination of software and hardware.

[0159] In some example embodiments, program 930 may be tangibly contained in a computer-readable medium, which may be included in device 900 (such as memory 920) or other storage devices accessible by device 900. Device 900 may load program 930 from the computer-readable medium into RAM 922 for execution. The computer-readable medium may include any type of tangible non-volatile storage device, such as ROM, EPROM, flash memory, hard disk, CD, DVD, etc. Figure 10 An example of a computer-readable medium 1000 in the form of a CD or DVD is shown. The computer-readable medium has a program 930 stored thereon.

[0160] Generally, the various embodiments of this disclosure can be implemented using hardware or dedicated circuitry, software, logic, or any combination thereof. Some aspects can be implemented using hardware, while others can be implemented using firmware or software that can be executed by a controller, microprocessor, or other computing device. Although various aspects of the exemplary embodiments of this disclosure are illustrated and described as block diagrams, flowcharts, or using some other graphical representation, it should be understood that, as non-limiting and illustrative examples, the blocks, apparatuses, systems, techniques, or methods described herein can be implemented using hardware, software, firmware, dedicated circuitry or logic, general-purpose hardware or controllers or other computing devices, or some combination thereof.

[0161] This disclosure also provides at least one computer program product tangibly stored on a non-transitory computer-readable storage medium. The computer program product includes computer-executable instructions that are executed in a device on a target real or virtual processor, such as instructions included in a program module to perform the functions described above. Figures 2 to 8 The described method. Typically, a program module includes routines, programs, libraries, objects, classes, components, data structures, etc., that perform a specific task or implement a specific abstract data type. In various example embodiments, the functionality of a program module can be combined or split among program modules as needed. The machine-executable instructions for a program module can be executed on a local or distributed device. In a distributed device, a program module can reside on both local and remote storage media.

[0162] Program code used to perform the methods of this disclosure may be written in any combination of one or more programming languages. This program code may be provided to a processor or controller of a general-purpose computer, special-purpose computer, or other programmable data processing apparatus, such that, when executed by the processor or controller, the program code causes the functions / operations specified in the flowcharts and / or block diagrams to be implemented. The program code may be executed entirely on a machine, partially on a machine, as a stand-alone software package, partially on a machine and partially on a remote machine, or entirely on a remote machine or server.

[0163] In the context of this disclosure, computer program code or related data may be carried by any suitable carrier wave to enable a device, apparatus, or processor to perform the various processes and operations described above. Examples of carrier waves include signals, computer-readable media, etc.

[0164] Computer-readable media can be computer-readable signal media or computer-readable storage media. Computer-readable media can include, but is not limited to, electronic, magnetic, optical, electromagnetic, infrared, or semiconductor systems, devices, or equipment, or any suitable combination of the foregoing. More specific examples of computer-readable storage media will include electrical connections having one or more wires, portable computer floppy disks, hard disks, random access memory (RAM), read-only memory (ROM), erasable programmable read-only memory (EPROM or flash memory), optical fiber, portable optical disc read-only memory (CD-ROM), optical storage devices, magnetic storage devices, or any suitable combination of the foregoing. As used herein, the term "non-transient" is a limitation on the medium itself (e.g., tangible, not signaling), not a limitation on the persistence of data storage (e.g., RAM and ROM).

[0165] Furthermore, although the operations are depicted in a specific order, this should not be construed as requiring such operations to be performed in the specific order shown or in a sequential order, or as requiring all illustrated operations to be performed to obtain the desired result. In some cases, multitasking and parallel processing can be advantageous. Similarly, while several specific implementation details are included in the foregoing discussion, these should not be construed as limiting the scope of this disclosure, but rather as descriptions of features that may be specific to particular example embodiments. Certain features described in the context of a single embodiment may also be implemented in combination in a single example embodiment. Conversely, various features described in the context of a single example embodiment may also be implemented individually or in any suitable sub-combination in multiple example embodiments.

[0166] Although this disclosure has been described in language specific to structural features and / or methodological actions, it should be understood that the various exemplary embodiments of this disclosure are not limited to the specific features or actions described above. Rather, the specific features and actions described above are disclosed as exemplary forms for implementing various exemplary embodiments of this disclosure.

Claims

1. A first network device, comprising: At least one processor; as well as At least one memory, the at least one memory storing an indication, the indication, when executed by the at least one processor, such that the first network device at least: During the service attempt process for the terminal device, first coarse location information of the terminal device is received from the terminal device. as well as Based on an event that the terminal device is not located in an area where the terminal device is allowed to be served, a separation process is initiated for the terminal device, wherein the determination of the event is based on the first coarse location information.

2. The first network device of claim 1, wherein the first network device is configured to initiate the separation process for the terminal device by: Based on the second coarse location information and the first coarse location information of the region, determine whether the terminal device is located within the region; and Based on the determination that the terminal device is not located in the area, the separation process for the terminal device is initiated.

3. The first network device of claim 1, wherein the area is determined based on service restriction information received from the second network device, and the first network device is configured to determine that the terminal device is not located in the area by: Obtain cell information associated with the terminal device, wherein the cell information is determined based on the first coarse location information; Determine whether the coverage area of ​​the cell indicated by the cell information belongs to the area; as well as Based on the determination that the coverage area of ​​the cell does not belong to the area, it is determined that the terminal device is not located in the area.

4. The first network device according to claim 3, wherein the first network device is configured to acquire the cell information by: The request for the cell information is sent to a third network device via additional information elements in a request message or location request message configured to request the cell information; and The cell information is received from the third network device via at least one of the following: a response message to the request message, a location report control message, or an uplink (UL) non-access stratum (NAS) message.

5. The first network device according to claim 3 or 4, wherein the second coarse location information of the area is configured within the first network device based on the cell information.

6. The first network device according to any one of claims 3 to 5, wherein the cell is provided by a non-terrestrial network.

7. The first network device of claim 1, wherein the first network device is configured to initiate the separation process for the terminal device by: Send the first rough location information to the second network device; Receive from the second network device a location cancellation message sent based on the determination that the terminal device is not located within the area; and Based on receiving the location cancellation message, the separation process for the terminal device is initiated.

8. The first network device of claim 1, wherein the first network device is configured to initiate the separation process for the terminal device by: Send the first rough location information to the fourth network device; Receive a response from the fourth network device including at least one of national regional information or international regional information; and Based on the response, the separation process for the terminal device is initiated.

9. The first network device according to any one of claims 1 to 8, wherein the first network device is further configured to: Based on the determination that the terminal device is located in the area, the service attempt process for the terminal device continues.

10. The first network device according to any one of claims 1 to 8, wherein the first network device is further configured to: Send part or all of the second rough location information of the area to the terminal device.

11. The first network device of claim 10, wherein the second coarse location information includes coordinates of a list of ellipsoidal points for the region.

12. A second network device, comprising: At least one processor; as well as At least one memory storing instructions that, when executed by the at least one processor, cause the second network device to at least: Receive first rough location information of the terminal device from the first network device; Based on the first rough location information, determine whether the terminal device is located in the area where the terminal device is allowed to be served; as well as Based on the determination that the terminal device is not located in the area, a location cancellation message is sent to the first network device to separate the terminal device.

13. The second network device according to claim 12, wherein the second network device is further configured to: Send service restriction information to the first network device, wherein part or all of the service restriction information is used to attach or detach the terminal device.

14. The first network device according to claim 12 or 13, wherein the service restriction information includes the coordinates of a list of ellipsoidal points of the region.

15. A third network device, comprising: At least one processor; as well as At least one memory storing instructions that, when executed by the at least one processor, cause the third network device to at least: Receive a request from a first network device for cell information associated with a terminal device, wherein the cell information is determined based on first coarse location information received from the terminal device; and The cell information is sent to the first network device to indicate the coverage area of ​​the cell in which the terminal device is located.

16. The fourth network device according to claim 1, wherein the cell is provided by a non-terrestrial network.

17. A fourth network device, comprising: At least one processor; as well as At least one memory storing instructions that, when executed by the at least one processor, cause the fourth network device to at least: Receive first rough location information of the terminal device from the first network device; as well as Based on the first coarse location information, a response including at least one of country area information or international area information is sent to the first network device, wherein the country area information or the at least one of the international area information is used to determine the area where the terminal device is allowed to be served.

18. The fourth network device of claim 17, wherein the fourth network device is further configured to: Send a second coarse location information of the area to the first network device, wherein part or all of the second coarse location information is used to attach or detach the terminal device.

19. The fourth network device according to claim 17 or 18, wherein the second coarse location information includes coordinates of a list of ellipsoidal points for the region.

20. A terminal device, comprising: At least one processor; as well as At least one memory storing instructions that, when executed by the at least one processor, cause the terminal device to at least: Send the first approximate location information of the terminal device to the first network device; as well as The terminal device receives part or all of a second coarse location information of the area where it is permitted to be served from the first network device, and the part or all of the second coarse location information is used to attach or detach the terminal device.

21. The terminal device of claim 20, wherein the second coarse location information includes coordinates of a list of ellipsoidal points for the region.

22. A method comprising: During the service attempt process for the terminal device, the first coarse location information of the terminal device is received from the terminal device at the first network device. as well as Based on an event that the terminal device is not located in an area where the terminal device is allowed to be served, a separation process is initiated for the terminal device, wherein the determination of the event is based on the first coarse location information.

23. A method comprising: The second network device receives the first rough location information of the terminal device from the first network device. Based on the first rough location information, determine whether the terminal device is located in the area where the terminal device is allowed to be served; as well as Based on the determination that the terminal device is not located in the area, a location cancellation message is sent to the first network device to separate the terminal device.

24. A method comprising: At a third network device, a request for cell information associated with a terminal device is received from a first network device, wherein the cell information is determined based on first coarse location information received from the terminal device; and The cell information is sent to the first network device to indicate the coverage area of ​​the cell in which the terminal device is located.

25. A method comprising: At the fourth network device, the first approximate location information of the terminal device is received from the first network device. as well as Based on the first coarse location information, a response including at least one of country area information or international area information is sent to the first network device, wherein the country area information or the at least one of the international area information is used to determine the area where the terminal device is allowed to be served.

26. A method comprising: The terminal device sends its first approximate location information to the first network device. as well as The terminal device receives part or all of a second coarse location information of the area where it is permitted to be served from the first network device, and the part or all of the second coarse location information is used to attach or detach the terminal device.

27. An apparatus comprising: Components for receiving first coarse location information of the terminal device from the terminal device at a first network device during a service attempt process for the terminal device; as well as Components for initiating a separation process for the terminal device based on an event that the terminal device is not located in an area where the terminal device is permitted to be served, wherein the determination of the event is based on the first coarse location information.

28. An apparatus comprising: A component for receiving first rough location information of a terminal device from a first network device at a second network device; A component for determining whether the terminal device is located within an area where the terminal device is permitted to be served, based on the first coarse location information; as well as Used to send a cancel location message to the first network device based on determining that the terminal device is not located in the area, in order to separate components of the terminal device.

29. An apparatus comprising: A component for receiving, at a third network device, a request for cell information associated with a terminal device from a first network device, wherein the cell information is determined based on first coarse location information received from the terminal device; as well as A component for sending the cell information to the first network device to indicate the coverage area of ​​the cell in which the terminal device is located.

30. An apparatus comprising: A component for receiving first rough location information of a terminal device from a first network device at a fourth network device; as well as A component for sending a response to the first network device based on the first coarse location information, including at least one of country area information or international area information, wherein the country area information or the at least one of the international area information is used to determine the area where the terminal device is allowed to be served.

31. An apparatus comprising: A component for sending first coarse location information of the terminal device to the first network device from the terminal device; as well as A component for receiving part or all of a second coarse location information of the area where the terminal device is permitted to be served from the first network device, wherein the part or all of the second coarse location information is used to attach or detach the terminal device.

32. A non-transitory computer-readable medium comprising program instructions that, when executed by a device, cause the device to perform at least the method according to any one of claims 22 to 26.

Images