Methods and apparatus for controlling access attempts caused by location tracking

Abstract

A method and apparatus for providing access control for a mobile-initiated location request (MIRP) in a 5G network, particularly but not limited to. The access attempt message triggered by a MIRP or other 5GMM process can be assigned an access class based on whether the MIRP process is in progress or not. The message assigned the access class can be an LTE location protocol message. Possible access classes can include, for example, the MT_acc class for an inactive process and the MO_sig class for an inactive process. Access control checks can be performed unless the mobile device switches from idle mode to connected mode.

Description

Technical Field

[0001] The exemplary, non-limiting embodiments generally relate to communications, and more specifically to access control for mobile-initiated location requests.

[0002] A brief description of current progress

[0003] It is known that the user equipment requests access control for the mobile termination location request. Attached Figure Description

[0004] The foregoing aspects and other features are explained in the following description in conjunction with the accompanying drawings, in which:

[0005] Figure 1 This is a block diagram of a possible, non-limiting, exemplary system in which exemplary embodiments can be practiced;

[0006] Figure 2 This is a diagram illustrating the features as described herein;

[0007] Figure 3 This is a diagram illustrating the features as described herein;

[0008] Figure 4 This is a flowchart illustrating the steps described herein;

[0009] Figure 5 This is a flowchart illustrating the steps described herein; and

[0010] Figure 6 This is a flowchart illustrating the steps described herein. Detailed Implementation

[0011] The following abbreviations, which can be found in the instruction manual and / or accompanying drawings, are defined as follows:

[0012] 3GPP Third Generation Partner Program

[0013] 5G (Fifth Generation)

[0014] 5GC 5G Core Network

[0015] 5GMM 5G Mobility Management

[0016] 5GS 5G system

[0017] AMF Access and Mobility Management Functions

[0018] CU Central Unit

[0019] DL downlink

[0020] DU Distributed Unit

[0021] eNB (or eNodeB) Evolved Node B (e.g., LTE base station)

[0022] EN-DC E-UTRA-NR Dual Connection

[0023] The en-gNB or En-gNB provides NR user plane and control plane protocol termination to the UE and acts as a secondary node in the EN-DC.

[0024] E-UTRA, or Evolved Universal Terrestrial Radio Access, also known as LTE radio access technology.

[0025] gNB (or gNodeB) is a base station used for 5G / NR (i.e., a node that provides NR user plane and control plane protocol termination toward the UE and connects to the 5GC via the NG interface).

[0026] I / F interface

[0027] LPP LTE positioning protocol

[0028] LR location request

[0029] LTE Long Term Evolution

[0030] MAC Media Access Control

[0031] MME (Mobility Management Entity)

[0032] MMTEL Multimedia Telephony

[0033] MO: Mobile Initiation

[0034] MO-LR (Move-Initiating / Originated) Location Request

[0035] MO-SMSoNAS is a mobile-initiated short message service based on the non-access stratum.

[0036] MT movement terminated

[0037] MT-LR Terminating / Terminated Location Request

[0038] NAS Non-Access Layer

[0039] ng or NG, next generation

[0040] ng-eNB or NG-eNB, the next generation of eNB

[0041] NR New Radio

[0042] N / W or NW network

[0043] PDCP (Packet Data Convergence Protocol)

[0044] PHY physical layer

[0045] RAN (Radio Access Network)

[0046] RRH Remote Radio Head

[0047] RRC Radio Resource Control

[0048] RU radio unit

[0049] Rx receiver

[0050] SDAP Service Data Adaptation Protocol

[0051] SGW Service Gateway

[0052] SMF Session Management Function

[0053] SMS Short Message Service

[0054] SMSoIP is a short message service based on the Internet Protocol.

[0055] TS Technical Specifications

[0056] Tx Transmitter

[0057] UE (User Equipment) (e.g., wireless equipment, typically mobile equipment)

[0058] UL uplink

[0059] UPF User Plane Functions

[0060] Turning Figure 1 The figure illustrates a block diagram of one possible, non-limiting example in which examples can be practiced. It shows a user equipment (UE) 110, a radio access network (RAN) node 170, and (multiple) network elements 190. Figure 1In the example, User Equipment (UE) 110 wirelessly communicates with Wireless Network 100. The UE is a wireless device that can access Wireless Network 100. UE 110 includes one or more processors 120, one or more memories 125, and one or more transceivers 130 interconnected via one or more buses 127. Each of the one or more transceivers 130 includes a receiver Rx 132 and a transmitter Tx 133. The one or more buses 127 may be address, data, or control buses and may include any interconnection mechanism, such as a series of lines on a motherboard or integrated circuit, fiber optic cable, or other optical communication device. The one or more transceivers 130 are connected to one or more antennas 128. The one or more memories 125 include computer program code 123. UE 110 includes a module 140, which includes one or both of portions 140-1 and / or 140-2, and module 140 may be implemented in various ways. Module 140 may be implemented in hardware as module 140-1, such as as part of one or more processors 120. Module 140-1 can also be implemented as an integrated circuit or via other hardware such as a programmable gate array. In another example, module 140 can be implemented as module 140-2, which is implemented as computer program code 123 and executed by one or more processors 120. For example, one or more memories 125 and computer program code 123 can be configured, together with one or more processors 120, to cause user equipment 110 to perform one or more of the operations described herein. UE 110 communicates with RAN node 170 via radio link 111.

[0061] In this example, RAN node 170 is a base station that provides access to wireless network 100 by wireless devices (such as UE 110). RAN node 170 can be, for example, a base station for 5G, also known as New Radio (NR). In 5G, RAN node 170 can be an NG-RAN node, which is defined as a gNB or ng-eNB. A gNB is a node that provides NR user plane and control plane protocol termination to the UE and is connected to the 5GC (e.g., multiple network elements 190) via an NG interface. An ng-eNB is a node that provides E-UTRA user plane and control plane protocol termination to the UE and is connected to the 5GC via an NG interface. An NG-RAN node can include multiple gNBs, which can also include a central unit (CU) (gNB-CU) 196 and multiple distributed units (DUs) (gNB-DU), where DU 195 is shown. Note that a DU can include or be coupled to and control a radio unit (RU). The gNB-CU is a logical node that hosts the RRC, SDAP, and PDCP protocols of the gNB, or controls the RRC and PDCP protocols of the en-gNB that control the operation of one or more gNB-DUs. The gNB-CU terminates the F1 interface connected to the gNB-DU. The F1 interface is shown as reference numeral 198, although reference numeral 198 also shows links between remote elements of RAN node 170 and centralized elements of RAN node 170, such as the link between gNB-CU 196 and gNB-DU 195. The gNB-DU is a logical node that hosts the RLC, MAC, and PHY layers of the gNB or en-gNB, and its operation is partially controlled by the gNB-CU. One gNB-CU supports one or more cells. One cell is supported by only one gNB-DU. The gNB-DU terminates the F1 interface 198 connected to the gNB-CU. Note that DU195 is considered to include transceiver 160, for example, as part of an RU; however, some examples in this regard could allow transceiver 160 to be part of a separate RU, for example, under the control of and connected to DU 195. RAN node 170 could also be an eNB (evolved NodeB) base station for LTE (Long Term Evolution), or any other suitable base station or node.

[0062] RAN node 170 includes one or more processors 152, one or more memories 155, one or more network interfaces (N / WI / F) 161 interconnected via one or more buses 157, and one or more transceivers 160. Each of the one or more transceivers 160 includes a receiver Rx 162 and a transmitter Tx 163. The one or more transceivers 160 are connected to one or more antennas 158. The one or more memories 155 include computer program code 153. CU 196 may include one or more processors 152, memories 155, and network interfaces 161. Note that DU 195 may also include its own memory / multiple memories and processors, and / or other hardware, but these are not shown.

[0063] RAN node 170 includes module 150, which includes one or both of portions 150-1 and / or 150-2. Module 150 can be implemented in various ways. Module 150 can be implemented in hardware as module 150-1, such as as part of one or more processors 152. Module 150-1 can also be implemented as an integrated circuit or via other hardware such as a programmable gate array. In another example, module 150 can be implemented as module 150-2, which is implemented as computer program code 153 and executed by one or more processors 152. For example, one or more memories 155 and computer program code 153 are configured, together with one or more processors 152, to cause RAN node 170 to perform one or more of the operations described herein. Note that the functionality of module 150 can be distributed, such as being distributed between DU 195 and CU 196, or implemented solely in DU 195.

[0064] One or more network interfaces 161 communicate over a network, such as via links 176 and 131. Two or more gNBs 170 may communicate using, for example, link 176. Link 176 may be wired, wireless, or both, and may implement, for example, an Xn interface for 5G, an X2 interface for LTE, or other suitable interfaces for other standards.

[0065] One or more buses 157 may be address, data, or control buses and may include any interconnection mechanism, such as a series of lines on a motherboard or integrated circuit, optical fiber or other optical communication equipment, wireless channels, etc. For example, one or more transceivers 160 may be implemented as a Remote Radio Header (RRH) 195 for LTE or a Distributed Unit (DU) 195 for a gNB implementation of 5G, wherein other elements of the RAN node 170 may be physically located in a different location from the RRH / DU, and one or more buses 157 may be partially implemented as, for example, fiber optic cables or other suitable network connections for connecting other elements of the RAN node 170 (e.g., Central Unit (CU), gNB-CU) to the RRH / DU 195. Reference numeral 198 also indicates these suitable network links(s).

[0066] Note that the description in this document indicates that a "cell" performs a function; however, it should be clear that the equipment forming the cell can perform this function. A cell constitutes part of a base station. That is, each base station can have multiple cells. For example, a single carrier frequency and associated bandwidth can have three cells, each covering one-third of a 360-degree area, thus the coverage area of ​​a single base station is approximately elliptical or circular. Furthermore, each cell can correspond to a single carrier, and a base station can use multiple carriers. So if each carrier has three 120-degree cells and there are two carriers, the base station has a total of six cells.

[0067] Wireless network 100 may include one or more network elements 190, which may include core network functions and provide connectivity to other networks (e.g., the Internet) such as telephone networks and / or data communication networks via one or more links 181. Such core network functions for 5G may include access and mobility management functions (multiple AMFs) and / or user plane functions (multiple UPFs) and / or session management functions (multiple SMFs). Such core network functions for LTE may include MME (Mobility Management Entity) / SGW (Serving Gateway) functions. These are merely exemplary functions that may be supported by the network elements 190, and it should be noted that both 5G and LTE functions may be supported. RAN node 170 is coupled to network element 190 via link 131. Link 131 may be implemented as, for example, an NG interface for 5G, or an S1 interface for LTE, or other suitable interfaces for other standards. Network element 190 includes one or more processors 175, one or more memories 171, and one or more network interfaces (N / WI / F) 180 interconnected via one or more buses 185. The one or more memories 171 include computer program code 173. The one or more memories 171 and the computer program code 173 are configured, together with the one or more processors 175, to cause network element 190 to perform one or more operations.

[0068] Wireless network 100 can achieve network virtualization, which is a process of combining hardware and software network resources and network functions into a single software-based managed entity, a virtual network. Network virtualization involves platform virtualization, which is often used in conjunction with resource virtualization. Network virtualization is divided into external network virtualization and internal network virtualization. External network virtualization combines many networks or network components into virtual units, while internal network virtualization provides network-like functionality to software containers on a single system. Note that the virtualized entities created by network virtualization are still implemented to some extent using hardware such as processors 152 or 175 and memories 155 and 171, and these virtualized entities also produce technical effects.

[0069] Computer-readable storage devices 125, 155, and 171 can be of any type suitable for the local technical environment and can be implemented using any suitable data storage technology, such as semiconductor-based memory devices, flash memory, magnetic storage devices and systems, optical storage devices and systems, fixed storage, and removable storage. Computer-readable storage devices 125, 155, and 171 can be components for performing storage functions. Processors 120, 152, and 175 can be of any type suitable for the local technical environment and, by way of non-limiting example, can include one or more of general-purpose computers, special-purpose computers, microprocessors, digital signal processors (DSPs), and processors based on multi-core processor architectures. Processors 120, 152, and 175 can be means for performing functions, such as controlling UE 110, RAN node 170, and other functions as described herein.

[0070] Typically, various embodiments of user equipment 110 may include, but are not limited to, cellular phones with wireless communication capabilities (such as smartphones, tablets, personal digital assistants (PDAs)), portable computers with wireless communication capabilities, image capture devices with wireless communication capabilities (such as digital cameras), gaming devices with wireless communication capabilities, music storage and playback devices with wireless communication capabilities, internet devices that allow wireless internet access and browsing, tablets with wireless communication capabilities, and portable units or terminals combining such functions.

[0071] The features described in this article generally relate to access control for Mobile Initiated Location Request (MO-LR).

[0072] Location requests (LR) can be sent from the network or application server to the user equipment (UE). These location requests are considered to be mobile-terminated / terminating location requests (MT-LR). Location requests can also be sent by the UE to, for example, the network or application server. These location requests are considered to be mobile-initiated location requests (MO-LR).

[0073] Location requests can be sent using the LTE Location Protocol (LPP). LPP messages can be sent point-to-point between a location server (i.e., a network node) and the target device (i.e., the UE) to locate the target device. LPP can be used in conjunction with LTE location requests, 5G location requests, or other / future types of location requests.

[0074] For previous 3GPP mobile networks, MT-LR and MO-LR were defined. For 5G networks, access control for MT-LR is already specified in the current version TS 24.501; however, TS 24.501 contains a note stating that access control for MO-LR is not specified because MO-LR is not supported. For 5G networks, it was previously assumed that any / all LPP messages were MT-LR, meaning that services are initiated from the network side, not by the UE.

[0075] 3GPP TS 24.501 contains the latest version of the unified access control framework in 5G systems (5GS). As can be seen from the following note in Clause 4.5.1 of 3GPP TS 24.501, mobile-initiated location requests are not considered in the NAS protocol:

[0076] "Note 2: In this version of the protocol, initiating a mobile-initiated location request by sending a UL NAS TRANSPORT message (see Sub-clause 5.4.5.2.1) is not supported, and therefore no access control is specified for this situation. All LPP messages transmitted in a ULNAS TRANSPORT message are sent in response to a mobile termination or network-initiated location request, and the corresponding access attempt is treated as an MT access."

[0077] For Rel-16 of TS 23.273, MO-LR has been specified, but the access control procedure for MO-LR has not yet been defined. Refer to [link / reference] now. Figure 2 This illustrates an example of the 5G core network mobile-initiated location request (5GC-MO-LR) process. Figure 2 In this process, the initiation of step 2 or arrangement 1 (if executed) should be through access control. Figure 2 During the 5GC-MO-LR process, the 5G Mobility Management (5GMM) connection management process for Non-Access Stratum (NAS) signaling recovery should not be subject to access control checks, even if it is necessary to assign an access class for the access attempt.

[0078] Because location requests can take a considerably long time (i.e., up to 10 seconds) compared to other services, the UE may enter idle mode during this process. Therefore, MT-LR LPP messages are typically assigned access class "0" (MT_acc) to prevent LPP messages from being blocked. Conversely, for other services, there is no mechanism to exempt MO messages from being blocked, as it is assumed that the UE will rarely be idle during MO processes.

[0079] Access control for MO-LR presents different challenges than access control for MT-LR. In example embodiments, the unified access control framework found in 3GPP TS 24.501 can be modified according to this disclosure.

[0080] Now for reference Figure 3 , Figure 3 An example simplified protocol stack in the UE is shown. In the example embodiment, in the UE NAS layer 304, the 5GMM connection management procedure initiated to transmit LPP messages during the ongoing 5GC-MO-LR process may not be classified as MT_acc.

[0081] In an example embodiment, a new event can be identified in UE NAS layer 304, where 5GMM receives a request from higher layer 302 to send a Mobile Initiated Location Request (MIRP), unless the request triggers a service request procedure to transition the UE from 5GMM-IDLE mode to 5GMM-CONNECTED mode. In other words, if the request triggers the UE to transition from idle mode to connected mode, the new event has not yet occurred. Examples of this new event may include: a NAS transmission procedure initiated by the UE for transmitting the MIRP; a 5GMM connection management procedure triggered by a NAS transmission procedure initiated by the UE for transmitting the MIRP; and NAS signaling connection recovery during an ongoing 5GC-MO-LR procedure.

[0082] In the example embodiment, in UE NAS layer 304, a new event can be classified as MO_sig during access class assignment.

[0083] In an example embodiment, the higher layer 302 in the UE can indicate to the UE NAS layer 304 when the 5GC-MO-LR procedure begins and stops. Based on these start and stop indications, while the 5GC-MO-LR procedure is in progress, when a service request procedure or registration procedure for NAS signaling connection restoration purposes or following a fallback indication from a lower layer is initiated in 5GMM-IDLE mode, the UE NAS layer 304 may be able to skip access control checks. In the case of indicating an ongoing 5GC-MO-LR procedure, the access attempt can be mapped to MO_sig.

[0084] In the example embodiment, additional steps can be added to the access control procedure for LR. During this additional step, it can be determined whether the LPP message is part of an ongoing MO-LR procedure. Based on this determination, an access class can be assigned. In contrast to MT-LR LPP messages, MO-LR LPP messages can be assigned a class other than "0" (MT_acc).

[0085] In an example implementation, when the 5G core network mobile-initiated location request (5GC-MO-LR) process starts and stops, it may be necessary to notify the non-access stratum (NAS) layer 304.

[0086] The access control procedure for MO-LR can be similar to that for MO-SMSoNAS (Mobile Initiated Short Message Service over Non-Access Stratum). In an example embodiment, the difference between the two procedures lies in the fact that the 5G Mobility Management (5GMM) connection management procedure initiated for transmitting LPP messages can be checked to determine whether the LPP message was sent within an ongoing 5GC-MO-LR procedure. If the LPP message was sent within an ongoing 5GC-MO-LR procedure, the assigned access class can be "3" (MO_sig), or it can be assigned a new access class for MO-LR. If the LPP message was not sent within an ongoing 5GC-MO-LR procedure, the assigned access class can be "0" (MT_acc), which is never prohibited. Conversely, for SMSONAS, the 5GMM connection management procedure initiated for transmitting SMS messages outside of an MO-SMSoNAS procedure (i.e., an MT-SMSoNAS procedure) can be classified as access class "3" instead of "0". Therefore, for example, if the UE is idle during the MT-SMSoNAS procedure, access control can be applied (i.e., access attempts to send SMS messages during an ongoing MT-SMSoNAS procedure can be prohibited). For location services, since obtaining the UE's location can take a long time (i.e., possibly more than 10 seconds), the 5GMM connection management procedure initiated to transmit LPP messages can be classified as MT_acc.

[0087] In an example embodiment, the access control procedure for LR may include the following steps. (See reference...) Figure 3 The example protocol stack of the UE can receive a request at NAS layer 304 from a higher layer 302 to send a Mobility Initiation Location Request (MOLR). This request can be considered a start indication for a 5GC-MO-LR procedure, or it can be sent to NAS layer 304 along with the start indication. The NAS layer can identify an access attempt that needs to be initiated due to a request from a higher layer. The access attempt can be a 5GMM connection management procedure or a UE-initiated NAS transport procedure. NAS layer 304 can determine the access category and establishment reason of the access attempt. NAS layer 304 can provide the access category and establishment reason to a lower layer 306 and can request the lower layer 306 to perform an access control check at least based on the access category.

[0088] If, while the 5GC-MO-LR process is in progress (i.e., after receiving the start indication and before receiving the stop indication), a service request or registration process for NAS signaling connection recovery purposes or in accordance with a fallback indication from lower layer 306 is initiated in 5GMM-IDLE mode, NAS layer 304 can determine the access category and establishment reason of the service request or registration process and can provide that establishment reason to lower layer 306. NAS layer 304 can receive a stop indication for the 5GC-MO-LR process from higher layer 302.

[0089] In the example embodiment, neither a new access class nor a new RRC establishment reason is required, and the associated access attempt can be mapped to MO_sig. In another example embodiment, a new access class (e.g., mobile-initiated location request) can be defined for access attempts that need to be initiated due to a request from a higher layer 302. With access identity "0", the new access class can be mapped to a new RRC establishment reason (e.g., mobile-initiated location request).

[0090] In an example embodiment, when a UE needs to access 5GS, the UE can first perform an access control check to determine whether access is allowed for the access attempt. When 5GS (in Figure 3 When a request to send a Mobile Initiated Location Request (MILR) or LPP message is received from a higher layer 302 during the 5GC-MO-LR process (found in NAS layer 304), an access control check may be performed unless the request triggers a service request procedure to transition the UE from 5GMM-IDLE mode to 5GMM-CONNECTED mode. If the received request triggers a service request procedure to transition the UE from 5GMM-IDLE mode to 5GMM-CONNECTED mode, the access control check does not need to be performed by the UE.

[0091] In the example embodiment, access class "0" (MT_acc) may be appropriate in the absence of an ongoing 5GC-MO-LR process.

[0092] In example embodiments, access class "3" (MO_sig) may be appropriate when a UE initiates a 5GMM-specific procedure in NAS 304 or in the case of a mobile-initiated location request. Examples of these scenarios include: a) a UE-initiated NAS transmission procedure for transmitting a mobile-initiated location request; b) a 5GMM connection management procedure triggered by a) above; and c) NAS signaling connection recovery during an ongoing 5GC-MO-LR procedure.

[0093] In an example embodiment, if the event triggering the access attempt is a request to send a Mobility Initiation Location (MOI) request from a higher layer 302, the NAS layer 304 (including the 5GMM) may initiate a NAS transport procedure to send the MOI request in a UL NAS TRANSPORT message. However, in an alternative example embodiment, if the event triggering the access attempt is a request to send a MOI request from a higher layer 302, the NAS layer 304 (including the 5GMM) may not initiate a NAS transport procedure to send the request in a UL NAS TRANSPORT message, possibly due to a prohibition on the relevant access class. However, in the latter case, upon receiving an indication from a lower layer 306 that the prohibition for the access class associated with the access attempt has been mitigated, the NAS layer 304 (including the 5GMM) may initiate a NAS transport procedure to send the request in a UL NAS TRANSPORT message (if still necessary).

[0094] In the example embodiment, when the 5GC-MO-LR procedure is in progress, no SMS (Short Message Service), no SMSoIP (Short Message Service over Internet Protocol), no MMTEL (Multimedia Telephone) video call, and no MMTEL voice call are in progress on the NAS. Any service request or registration procedure initiated in 5GMM-IDLE mode for NAS signaling connection restoration purposes or in accordance with the fallback instruction from lower layer 306 can be mapped to access class "3" (=MO_sig) or a new access class for mobile-initiated location requests.

[0095] Figure 4 Possible steps of an example embodiment are illustrated. According to one aspect, an example method 400 may be provided, comprising: receiving a request for sending a mobile initiation location request, 402; and performing an access control check on the received request, 404.

[0096] Figure 5Possible steps of an example embodiment are illustrated. According to one aspect, an example method 500 may be provided, comprising: receiving an indication that a 5G core mobile-initiated location request process has commenced, wherein no indication that the 5G core mobile-initiated location request process has ceased has been received, 502; and assigning an access class to a service request process or service registration process without performing access control checks, 504. The service request process or registration process may be one of the following: a process initiated in idle mode for the purpose of restoring a non-access stratum signaling connection, or a process following a fallback instruction from a lower layer of the protocol stack of the user equipment. Step 504, assigning an access class to the service request process or service registration process without performing access control checks, may be performed only if no non-access stratum based SMS is in progress, no SMSoIP is in progress, no MMTEL video call is in progress, and no MMTEL voice call is in progress.

[0097] Figure 6 Possible steps of an example embodiment are illustrated. According to one aspect, an example method 600 may be provided, comprising: receiving at least one indication of the status of a 5G core mobile-initiated location request process, 602; initiating a 5G mobility management connection management process for transmitting LTE location protocol messages, 604; determining, based on at least one indication of the status of the 5G core mobile-initiated location request process, whether the 5G core mobile-initiated location request process is in progress, 606; and classifying the 5G mobility management connection management process based on the determination, 608. The at least one indication 602 of the status of the 5G core mobile-initiated location request process may include one of the following: an indication that the 5G core mobile-initiated location request process has started, or an indication that the 5G core mobile-initiated location request process has stopped. Classifying the 5G mobility management connection management process based on the determination 608 may include classifying the 5G mobility management connection management process using one of the following: an access class determined based on whether the 5G core mobile-initiated location request process is in progress, or an access class determined based on whether the 5G core mobile-initiated location request process is not in progress, for a mobile-terminated access request.

[0098] According to one aspect, an example method may be provided, comprising: receiving at a user equipment a request for sending a mobile-initiated location request; and performing an access control check at the user equipment in response to the received request.

[0099] The example method may also include identifying the access attempt to be initiated based at least in part on a request used to send a mobile-initiated location request; and determining the access class for the identified access attempt, wherein the execution of access control checks may include performing access control checks at least in part based on the determined access class.

[0100] Requests to initiate a location can be sent from a higher layer within the user equipment.

[0101] Example methods may also include determining that the access category of the access attempt is "mobile-initiated signaling", where the access attempt is initiated due to a request to send a mobile-initiated location request.

[0102] According to one example embodiment, an apparatus may be provided, comprising: at least one processor; and at least one non-transitory memory including computer program code, the at least one non-transitory memory and the computer program code being configured, together with the at least one processor, to cause the apparatus to: receive a request for sending a mobile initiation location request; and perform an access control check on the received request.

[0103] The apparatus may also be caused to: identify an access attempt to be initiated based at least in part on a request for sending a mobile initiation location request; and determine the access class of the identified access attempt, wherein performing access control checks may include performing access control checks at least in part based on the determined access class.

[0104] A request to send a location initiation request can be sent from a higher layer in the device.

[0105] The device can also be triggered to determine that the access category of the access attempt is "mobility-initiated signaling", wherein the access attempt can be initiated by a request to send a mobile-initiated location request.

[0106] According to one example embodiment, an apparatus may be provided, comprising: a component for receiving a request for sending a mobile initiation location request; and a component for performing an access control check on the received request.

[0107] The apparatus may further include components for identifying an access attempt to be initiated based at least in part on a request for sending a mobile initiation location request; and components for determining the access class of the identified access attempt, wherein the components for performing access control checks may include modules for performing access control checks based at least in part on the determined access class.

[0108] A request to send a location initiation request can be sent from a higher layer in the device.

[0109] The apparatus may also include components for determining that the access category of the access attempt is "mobility-initiated signaling", wherein the access attempt is initiated due to a request to send a mobile-initiated location request.

[0110] According to another example embodiment, a machine-readable non-transitory program storage device may be provided, which tangibly contains a machine-executable instruction program for performing operations including: receiving a request at a user equipment for sending a mobile initiation location request; and performing an access control check on the received request at the user equipment.

[0111] The operation may further include: identifying the access attempt to be initiated based at least in part on a request to send a mobile-initiated location request; and determining the access class of the identified access attempt, wherein the execution of access control checks may include performing access control checks based at least in part on the determined access class.

[0112] A request to initiate a location can be sent from a higher layer within the user equipment.

[0113] The operation may also include determining that the access category of the access attempt is "mobile-initiated signaling", wherein the access attempt may be initiated by a request to send a mobile-initiated location request.

[0114] According to one aspect, an example method may be provided, which includes: receiving a start indication at a user device when a mobile-initiated location request process has started and receiving a stop indication when the mobile-initiated location request process has stopped.

[0115] Start and stop instructions can come from a higher level in the user equipment.

[0116] Example methods may also include: determining that a move-initiated location request process is in progress if a start instruction has been received but a stop instruction has not yet been received.

[0117] Example methods may also include: assigning an access class to a service request process or registration process without performing access control checks, wherein the service request process or registration process can be one of the following: a process initiated in idle mode for non-access stratum signaling connection restoration purposes, or a process following a fallback instruction from a lower layer of the user equipment's protocol stack, and wherein: a mobile-initiated location request process may be in progress, no non-access stratum based SMS may be in progress, no SMSoIP may be in progress, no MMTEL video call may be in progress, and no MMTEL voice call may be in progress.

[0118] Example methods may also include determining the reason for establishing a service request process or registration process.

[0119] Assigning an access class to a service request process or registration process can include assigning an access class to a mobile-initiated location request.

[0120] According to one example embodiment, an apparatus may be provided, comprising: at least one processor; and at least one non-transitory memory including computer program code, the at least one non-transitory memory and the computer program code being configured together with the at least one processor to cause the apparatus to: receive a start indication when a mobile initiation location request process has begun and receive a stop indication when the mobile initiation location request process has stopped.

[0121] Start and stop instructions can come from a higher level in the device.

[0122] The device can also be configured to determine that a move-initiated location request process is in progress when a start instruction has been received but a stop instruction has not yet been received.

[0123] The device can also be configured to: assign an access class to a service request process or registration process and not perform access control checks, wherein the service request process or registration process can be one of the following: a process initiated in idle mode for the purpose of restoring a non-access stratum signaling connection, or a process following a fallback instruction from a lower layer of the protocol stack of the user equipment, and wherein: a mobile-initiated location request process is in progress, no short message service on a non-access stratum is in progress, no short message service on Internet Protocol is in progress, no multimedia telephony video call is in progress, and no multimedia telephony voice call is in progress.

[0124] The device can also be configured to determine the reason for establishing a service request process or registration process.

[0125] Assigning an access class to a service request process or registration process can include assigning an access class to a mobile-initiated location request.

[0126] According to one example embodiment, an apparatus may be provided, comprising: a component for receiving a start indication when a mobile initiation location request process has commenced and for receiving a stop indication when the mobile initiation location request process has ceased.

[0127] Start and stop instructions can come from a higher level in the device.

[0128] The device may also include a component for determining that a move initiation location request process is in progress when a start instruction has been received but a stop instruction has not yet been received.

[0129] The apparatus may further include: a component for assigning an access class to a service request process or registration process without performing access control checks, wherein the service request process or registration process may be one of the following: a process initiated in idle mode for the purpose of restoring a non-access stratum signaling connection, or a process following a fallback instruction from a lower layer of the protocol stack of the apparatus, and wherein: a mobile-initiated location request process is in progress, no short message service on a non-access stratum is in progress, no short message service on Internet Protocol is in progress, no multimedia telephony video call is in progress, and no multimedia telephony voice call is in progress.

[0130] The apparatus may also include components for determining the reason for initiating a service request process or registration process. A module for assigning an access class to a service request process or registration process may include a module for assigning an access class to a mobile-initiated location request.

[0131] According to another example embodiment, a machine-readable non-transitory program storage device may be provided, which tangibly contains a machine-executable instruction program for performing operations including: receiving a start indication when a move-initiated location request process has started, and receiving a stop indication when the move-initiated location request process has stopped.

[0132] Start and stop instructions can come from a higher level in the user equipment.

[0133] The operation may also include: determining that a move-initiated location request process is in progress when a start instruction has been received but a stop instruction has not yet been received.

[0134] The operation may also include: assigning an access class to a service request process or registration process without performing access control checks, wherein the service request process or registration process may be one of the following: a process initiated in idle mode for the purpose of restoring a non-access stratum signaling connection, or a process following a fallback instruction from a lower layer of the user equipment's protocol stack, and wherein: a mobile-initiated location request process is in progress, no short message service on a non-access stratum is in progress, no short message service on Internet Protocol is in progress, no multimedia telephony video call is in progress, and no multimedia telephony voice call is in progress.

[0135] This operation may also include determining the reason for establishing a service request process or registration process.

[0136] Assigning an access class to a service request process or registration process can include assigning an access class to a mobile-initiated location request.

[0137] According to one aspect, an example method may be provided, the example method comprising: receiving at a user equipment at at least one indication of the status of a 5G core mobile-initiated location request process, wherein each of the at least one indication includes one of: an indication that the 5G core mobile-initiated location request process has started, or an indication that the 5G core mobile-initiated location request process has stopped; initiating at the user equipment a 5G mobility management connection management process for transmitting LTE location protocol messages; determining at the user equipment, based on at least one indication of the status of the 5G core mobile-initiated location request process, whether the 5G core mobile-initiated location request process is in progress; and classifying at the user equipment, based on the determination, the 5G mobility management connection management process to: an access category for a mobile-initiated location request determined based on whether the 5G core mobile-initiated location request process is in progress, or an access category for a mobile-terminated access request determined based on whether the 5G core mobile-initiated location request process is not in progress.

[0138] Example methods may also include: receiving a request to send one of the following: a Long Term Evolution Location Protocol (LTE) message or a Mobile Initiated Location Request (MIRP) message within the 5G Core Mobile Initiated Location Request process, and one of the following: performing access control checks for the 5G Mobility Management Connection Management process if the received request does not trigger the user equipment to transition from idle mode to connected mode, or not performing access control checks for the 5G Mobility Management Connection Management process if the received request triggers the user equipment to transition from idle mode to connected mode.

[0139] The access class used for a location request initiated by a mobile device may include MO_sig, and the access class used for an access request terminated by a mobile device may include MT_acc.

[0140] According to one example embodiment, an apparatus may be provided, comprising: at least one processor; and at least one non-transitory memory including computer program code, the at least one non-transitory memory and the computer program code being configured, together with the at least one processor, to cause the apparatus to: receive at least one indication of the state of a 5G core mobile-initiated location request process, wherein each of the at least one indication includes one of the following: an indication that the 5G core mobile-initiated location request process has started, or an indication that the 5G core mobile-initiated location request process has stopped; initiate a 5G mobility management connection management process for transmitting LTE location protocol messages; determine, based on at least one indication of the state of the 5G core mobile-initiated location request process, whether the 5G core mobile-initiated location request process is in progress; and classify the 5G mobility management connection management process based on the determination: an access class for a mobile-initiated location request determined based on whether the 5G core mobile-initiated location request process is in progress, or an access class for a mobile-terminated access request determined based on whether the 5G core mobile-initiated location request process is not in progress.

[0141] The device can also be caused to: receive and send a request for one of the following: a Long Term Evolution Location Protocol (LTE) message or a Mobile Initiated Location Request (MIRP) message within a 5G Core Mobile Initiated Location Request (MIRP) procedure, and one of the following: perform an access control check for a 5G Mobility Management Connection Management (MIM) procedure, wherein the received request does not trigger a transition of the user equipment (UE) from idle mode to connected mode, or not perform an access control check for a 5G Mobility Management (MIM) connection management (MIM) procedure, wherein the received request triggers a transition of the UE from idle mode to connected mode.

[0142] The access class used for a location request initiated by a mobile device may include MO_sig, and the access class used for an access request terminated by a mobile device may include MT_acc.

[0143] According to an example embodiment, an apparatus may be provided, comprising: components for receiving at least one indication of the state of a 5G core mobile-initiated location request process, wherein each of the at least one indication includes one of the following: an indication that the 5G core mobile-initiated location request process has started, or an indication that the 5G core mobile-initiated location request process has stopped; components for initiating a 5G mobility management connection management process for transmitting LTE location protocol messages; components for determining whether the 5G core mobile-initiated location request process is in progress based on at least one indication of the state of the 5G core mobile-initiated location request process; and components for classifying the 5G mobility management connection management process based on the determination: an access class for mobile-initiated location request determined based on whether the 5G core mobile-initiated location request process is in progress, or an access class for mobile termination access request determined based on whether the 5G core mobile-initiated location request process is not in progress.

[0144] The apparatus may also include components for receiving a request to send one of the following: a Long Term Evolution Location Protocol message or a Mobile Initiated Location Request (MIRP) message within a 5G Core Mobile Initiated Location Request (MIRP) process, and one of the following: components for performing access control checks for the 5G Mobility Management Connection Management (MIM) process if the received request does not trigger the User Equipment (UE) to transition from idle mode to connected mode, or components for not performing access control checks for the 5G Mobility Management (MIM) Connection Management (MIM) process if the received request triggers the UE to transition from idle mode to connected mode.

[0145] The access class used for a location request initiated by a mobile device may include MO_sig, and the access class used for an access request terminated by a mobile device may include MT_acc.

[0146] According to another example embodiment, a machine-readable non-transitory program storage device can be provided, the non-transitory program storage device tangibly containing a machine-executable instruction program to perform operations including: receiving at least one indication of the status of a 5G core mobile-initiated location request process, wherein each of the at least one indication includes one of the following: an indication that the 5G core mobile-initiated location request process has started, or an indication that the 5G core mobile-initiated location request process has stopped; initiating a 5G mobility management connection management process at a user equipment for transmitting LTE location protocol messages; determining at the user equipment whether the 5G core mobile-initiated location request process is in progress based on at least one indication of the status of the 5G core mobile-initiated location request process; and classifying the 5G mobility management connection management process at the user equipment based on the determination: an access category for a mobile-initiated location request determined based on whether the 5G core mobile-initiated location request process is in progress, or an access category for a mobile-terminated access request determined based on whether the 5G core mobile-initiated location request process is not in progress.

[0147] The operation may also include: receiving a request to send one of the following: a Long Term Evolution Location Protocol message or a Mobile Initiated Location Request (MIRP) message within the 5G Core Mobile Initiated Location Request process, and one of the following: performing an access control check for the 5G Mobility Management Connection Management process if the received request does not trigger the user equipment to transition from idle mode to connected mode, or not performing an access control check for the 5G Mobility Management Connection Management process if the received request triggers the user equipment to transition from idle mode to connected mode.

[0148] The access class used for a location request initiated by a mobile device may include MO_sig, and the access class used for an access request terminated by a mobile device may include MT_acc.

[0149] It should be understood that the above description is illustrative only. Those skilled in the art can devise various alternatives and modifications. For example, the features recited in the various dependent claims can be combined with each other in any suitable combination. Furthermore, features from the different embodiments described above can be selectively combined to form new embodiments. Therefore, this specification is intended to cover all such alternatives, modifications, and variations falling within the scope of the appended claims.

Claims

1. A method of communication, comprising: At the Non-Access Stratum (NAS) layer of the user equipment, a request for sending a location initiation request is received from a higher layer of the user equipment. The access attempt to be initiated by the user equipment is identified at least in part based on the request; An access control check is performed in response to the access attempt; Performing the access control check includes determining that the access category used for the access attempt is mobile-initiated signaling, and The access control check mentioned therein is based on the determined access category.

2. A device for communication, comprising: At least one processor; and At least one non-transitory memory, including computer program code, wherein the at least one non-transitory memory and the computer program code are configured, together with the at least one processor, to cause the device to: At the Non-Access Stratum (NAS) layer of the user equipment, a request for sending a location-initiated motion request is received from a higher layer of the user equipment. The access attempt to be initiated by the user equipment is identified at least in part based on the request; Perform access control checks on the access request; Performing the access control check includes determining that the access category used for the access attempt is mobile-initiated signaling, and The access control check mentioned therein is based on the determined access category.

3. A method of communication, comprising: At the Non-Access Stratum (NAS) layer of the user equipment, a start indication is received from a higher layer of the user equipment when the mobile-initiated location request process has started, and a stop indication is received when the mobile-initiated location request process has stopped. as well as Assigning an access category to a service request process or registration process without performing access control checks, wherein the service request process or registration process includes: A process initiated in idle mode for the purpose of restoring non-access stratum signaling connections, and in: The process of initiating a location request by the mobile device is in progress. No short message service is currently in operation outside the access layer. No short message service over Internet Protocol (ISP) is currently in operation. No multimedia video calls are in progress, and No multimedia phone voice call is in progress.

4. The method according to claim 3, further comprising: If the start instruction has been received but the stop instruction has not yet been received, it is determined that the movement initiation location request process is in progress.

5. The method of claim 3, further comprising determining the reason for establishing the service request process or the registration process.

6. The method of claim 3, wherein assigning the access category to the service request process or the registration process includes assigning the access category to a mobile-initiated location request.

7. A device for communication, comprising: At least one processor; and At least one non-transitory memory, including computer program code, wherein the at least one non-transitory memory and the computer program code are configured, together with the at least one processor, to cause the device to: At the Non-Access Stratum (NAS) layer of the user equipment, a start indication is received from a higher layer of the user equipment when the mobile-initiated location request process has started, and a stop indication is received when the mobile-initiated location request process has stopped. as well as Assigning an access category to a service request process or registration process without performing access control checks, wherein the service request process or registration process includes: A process initiated in idle mode for the purpose of restoring non-access stratum signaling connections, and in: The process of initiating a location request by the mobile device is in progress. No short message service is currently in operation outside the access layer. No short message service over Internet Protocol (ISP) is currently in operation. No multimedia video calls are in progress, and No multimedia phone voice call is in progress.

8. The apparatus of claim 7, wherein the at least one non-transitory memory and the computer program code are configured, together with the at least one processor, to further cause the apparatus to: If the start instruction has been received but the stop instruction has not yet been received, it is determined that the movement initiation location request process is in progress.

9. The apparatus of claim 7, wherein the at least one non-transitory memory and the computer program code are configured, together with the at least one processor, to further enable the apparatus to determine the establishment reason for the service request process or the registration process.

10. The apparatus of claim 7, wherein assigning the access category for the service request process or the registration process includes assigning the access category for a mobile-initiated location request.

11. A machine-readable, non-transitory program storage device, tangibly containing a machine-executable instruction program for performing operations, the operations comprising the steps of the method according to any one of claims 1 and 3-6.

Images