Method for managing user location information and communication device

Abstract

The present disclosure provides a user location information management method and a communication device, and relates to the technical field of space-air-ground communication. The user location information management method comprises the following steps: a mobility management entity stores user location information from a user equipment as first user location information, wherein the first user location information comprises a first identifier; the mobility management entity stores user location information of the user equipment reported by a radio access network to which the user equipment is connected as second user location information, wherein the second user location information comprises a second identifier; and the mobility management entity determines the second user location information according to the second identifier, and uses the second user location information to perform a network process, wherein the network process comprises location verification. The embodiment of the present disclosure can enable the mobility management entity to use accurate user location information to complete location verification of the user equipment.

Description

Technical Field

[0001] This disclosure relates to the field of air-space-ground communication technology, and more specifically, to a method and communication device for managing user location information in narrowband Internet of Things (IoT) satellite scenarios. Background Technology

[0002] For NB-IoT (Narrow Band Internet of Things) satellite access scenarios, relevant communication standards stipulate that in some deployments, the location of the UE (User Equipment) cannot be provided through the LPP (Location Position Protocol). In such cases, the UE's location information is provided through the NAS (Non-Access Stratum). The MME (Mobility Management Entity) requests coarse location information from the UE. The UE provides coarse location information through the SMC (Security Mode Control) procedure. Subsequently, the MME can provide the coarse location information provided by the UE to the E-SMLC (Enhanced Serving Mobile Location Center) to execute the EPC-NI-LR (Evolved Packet Core - Network - Initiated Location Request) procedure for location verification.

[0003] However, the coarse location information provided by the UE may not meet the location verification requirements. Therefore, a solution to this dilemma is needed.

[0004] It should be noted that the information disclosed in the background section above is only used to enhance the understanding of the background of this disclosure, and therefore may include information that does not constitute prior art known to those skilled in the art. Summary of the Invention

[0005] The purpose of this disclosure is to provide a method and communication device for managing user location information in NB-IoT satellite access scenarios, so that the MME can accurately use precise UE user location information to verify the location of user equipment.

[0006] According to a first aspect of the present disclosure, a method for managing user location information is provided, comprising: a mobility management entity storing user location information from a user equipment as first user location information, the first user location information including a first identifier; the mobility management entity storing user location information of the user equipment reported by a wireless access network connected to the user equipment as second user location information, the second user location information including a second identifier; the mobility management entity determining the second user location information based on the second identifier, and performing a network process using the second user location information, the network process including location verification.

[0007] According to a second aspect of the present disclosure, a method for managing user location information is provided, comprising: a user equipment sending user location information including a first identifier to a mobility management entity.

[0008] According to a third aspect of the present disclosure, a method for managing user location information is provided, comprising: a radio access network sending user location information including a second identifier to a mobility management entity.

[0009] According to a fourth aspect of this disclosure, a communication device is provided, comprising: a memory; and a processor coupled to the memory, the processor being configured to perform the method as described in any of the preceding methods based on instructions stored in the memory.

[0010] According to a fifth aspect of this disclosure, a computer-readable storage medium is provided having a program stored thereon that, when executed by a processor, implements a method for managing user location information as described in any of the preceding claims.

[0011] According to a fifth aspect of this disclosure, a computer program product is provided, comprising a computer program that, when executed by a processor, implements the steps of any of the methods described above.

[0012] This embodiment of the disclosure stores user location information from the UE as first user location information including a first identifier and user location information from the RAN as second user location information including a second identifier in the MME. Subsequently, the second user location information is located based on the second identifier, and the MME uses the second user location information to execute network processes. This enables the MME to use accurate UE user location information to perform services such as UE location verification. This solves the problem that the MME may receive multiple UE user location information under the new communication standard of narrowband IoT, which may lead to information confusion, and improves communication efficiency and accuracy.

[0013] It should be understood that the above general description and the following detailed description are exemplary and explanatory only, and are not intended to limit this disclosure. Attached Figure Description

[0014] The accompanying drawings, which are incorporated in and form part of this specification, illustrate embodiments consistent with this disclosure and, together with the description, serve to explain the principles of this disclosure. It is obvious that the drawings described below are merely some embodiments of this disclosure, and those skilled in the art can obtain other drawings based on these drawings without any inventive effort.

[0015] Figure 1 This is a flowchart of a method for managing user location information in an exemplary embodiment of this disclosure.

[0016] Figure 2 This is a sub-flowchart of step S1 in one embodiment of this disclosure.

[0017] Figure 3 This is a sub-flowchart of step S2 in one embodiment of this disclosure.

[0018] Figure 4 This is a schematic diagram illustrating the addition of a first identifier and a second identifier by the network side in an exemplary embodiment of this disclosure.

[0019] Figure 5 This is a flowchart of an embodiment of the present disclosure of the MME sending a location report.

[0020] Figure 6 This is a flowchart of a method for managing user location information in an exemplary embodiment of this disclosure.

[0021] Figure 7 This is a flowchart of a method for managing user location information in an exemplary embodiment of this disclosure.

[0022] Figure 8 This is a sub-flowchart of step S71 in an exemplary embodiment.

[0023] Figure 9 This is a schematic diagram illustrating the addition of a first identifier and a second identifier by the UE side and the access side in an exemplary embodiment.

[0024] Figure 10 This is a block diagram of a user location information management device according to an exemplary embodiment of the present disclosure.

[0025] Figure 11 This is a block diagram of a communication device according to an exemplary embodiment of the present disclosure. Detailed Implementation

[0026] Example embodiments will now be described more fully with reference to the accompanying drawings. However, example embodiments can be implemented in many forms and should not be construed as limited to the examples set forth herein; rather, these embodiments are provided to make this disclosure more comprehensive and complete, and to fully convey the concept of the example embodiments to those skilled in the art. The described features, structures, or characteristics can be combined in any suitable manner in one or more embodiments. In the following description, numerous specific details are provided to give a full understanding of embodiments of this disclosure. However, those skilled in the art will recognize that the technical solutions of this disclosure can be practiced with one or more of the specific details omitted, or other methods, components, apparatus, steps, etc., can be employed. In other instances, well-known technical solutions are not shown or described in detail to avoid obscuring various aspects of this disclosure.

[0027] Furthermore, the accompanying drawings are merely illustrative of this disclosure, and the same reference numerals in the drawings denote the same or similar parts, thus repeated descriptions of them will be omitted. Some block diagrams shown in the drawings are functional entities and do not necessarily correspond to physically or logically independent entities. These functional entities may be implemented in software, in one or more hardware modules or integrated circuits, or in different network and / or processor devices and / or microcontroller devices.

[0028] The exemplary embodiments of this disclosure will now be described in detail with reference to the accompanying drawings.

[0029] Figure 1 This is a flowchart of a method for managing user location information in an exemplary embodiment of this disclosure.

[0030] refer to Figure 1 The method 100 applied to narrowband IoT satellite scenarios can be executed by the MME and may include:

[0031] Step S1: The mobility management entity stores the user location information from the user equipment as first user location information, the first user location information including a first identifier;

[0032] Step S2, the mobility management entity stores the user location information of the user equipment reported by the radio access network to which the user equipment is connected as second user location information, the second user location information including a second identifier;

[0033] Step S3: The mobility management entity determines the second user location information based on the second identifier, and performs a network procedure using the second user location information, the network procedure including location verification.

[0034] This embodiment of the disclosure stores user location information from the UE as first user location information including a first identifier and user location information from the RAN as second user location information including a second identifier in the MME. Subsequently, the second user location information is located based on the second identifier, and the MME uses the second user location information to execute network processes. This enables the MME to use accurate UE user location information to perform services such as UE location verification. This solves the problem that the MME may receive multiple UE user location information under the new communication standard of narrowband IoT, which may lead to information confusion, and improves communication efficiency and accuracy.

[0035] In this embodiment of the disclosure, the first user location information includes user location information sent by the UE in the initial UE message or the first set of UL NAS transmission messages.

[0036] The initial UE message is the first message sent by the UE to the MME through the base station after establishing an RRC connection with the base station. It initiates the signaling interaction process between the UE and the core network. When establishing a connection with the network, the UE informs the network of its basic information and access request, allowing the network to identify the UE and perform subsequent processing, such as resource allocation and security authentication. The initial UE message includes user location information such as TAI, UE identification information, selected PLMN information, NAS layer signaling (such as Attach Request messages), security-related parameters, and UE capability information.

[0037] Following the initial UE message, when the UE needs to send further NAS signaling to the core network, it will transmit it through the first set of UL NAS transmission messages. For example, in the attach procedure, the UE may first send an AttachRequest in the initial UE message, and subsequently send related authentication responses and other messages through the first set of UL NAS transmission messages.

[0038] The first set of UL NAS transmission messages is used to transmit non-access stratum (NAS) signaling messages between the UE and the core network, enabling the transmission of various control functions between the UE and the core network, such as session management and mobility management messages. The first set of UL NAS transmission messages mainly includes user location information such as TAI and various NAS signaling messages. The specific content depends on the UE's operation and network requirements, such as authentication messages, encryption mode command responses, and location update requests.

[0039] The user location information such as TAI in the initial UE message is used to help the network initially determine the UE's location in order to perform subsequent resource allocation and paging area settings. The user location information such as TAI in the first set of UL NAS transmission messages is continuously updated to the network during the interaction between the UE and the core network, ensuring that the network always knows the tracking area where the UE is located, so as to perform accurate mobility management and paging operations.

[0040] User Location Information (ULI) is used to identify the location of a user equipment (UE), and may include Tracking Area Identity (TAI) and Cell ID. In a communication network, TAI is used to track the UE's location over a larger area, while the Cell ID more precisely identifies the specific cell where the UE is located. The combination of the two can more accurately determine the UE's location information, enabling the network to perform operations such as paging and location updates.

[0041] In an exemplary embodiment, the ULI sent by the UE in the initial UE message or the first set of UL NAS transmission messages includes TAI and CGI (Cell Global Identity). The CGI consists of the Mobile Country Code (MCC), Mobile Network Code (MNC), and Cell Identifier (CI). In a mobile communication network, it helps the network accurately identify the specific cell where the user is located in order to perform operations such as signal transmission and handover, and ensure the accuracy and stability of communication.

[0042] After obtaining the ULI reported by the UE, the MME will store it for later use.

[0043] At the SA2#161 meeting, it was approved that for NB-IoT satellite access scenarios, if the UE location cannot be provided through LPP (Location Position Protocol) in some deployments, it is necessary to increase the possibility of providing UE location information through NAS. The Attach and TAU procedures of TS 23.401 were updated with descriptions of MME requesting UE coarse location information and UE providing coarse location information through SMC procedures. After that, MME can provide UE coarse location information to E-SMLC to perform EPC-NI-LR procedure for location verification.

[0044] In an exemplary embodiment, the MME can obtain the coarse location information reported by the UE through the NAS SMC procedure. This coarse location information differs from the ULI (User Location Information) and is represented using only a small amount of code. The network side translates and interprets the code in this coarse location information to obtain the user location information used for location verification. However, the coarse location information reported by the UE may not have sufficient accuracy to meet the location verification requirements.

[0045] To overcome the problem that the coarse location information sent by the UE cannot meet the accuracy requirements of location verification, a strategy is proposed in which the MME sends location report control information to the RAN (Radio Access Network) after receiving the coarse location information provided by the UE, so as to request the Radio Access Network to provide the user location information of the user equipment through the location report.

[0046] In an exemplary embodiment, after receiving coarse location information from the UE, the MME can provide the UE's coarse location information to the E-SMLC to perform location verification via the EPC-NI-LR procedure. Specifically, the MME selects an E-SMLC and sends a location request message to it. The location request includes the requested location information type, the requested QoS, the serving cell identity, the UE's coarse location information (in the case of NB-IoT satellite access), and the UE's LPP support capability. The E-SMLC determines whether the obtained location estimate meets the accuracy requested by the MME based on parameters received from the MME (e.g., cell identifier or coarse location information) and responds by sending a location response message to the MME.

[0047] If the coarse location information can meet the location information requested by the MME and the location accuracy requirements within the QoS, the E-SMLC can immediately send a location response message; at the same time, in the case of NB-IoT satellite access, if coarse location information is provided in the location request message, the E-SMLC should immediately send a location response message.

[0048] If the coarse location information does not meet the location information requested by the MME and the location accuracy requirements within the QoS, and the E-SMLC fails to obtain a location estimate, the location response message will contain the cause of the failure.

[0049] Furthermore, when the MME decides to verify the location (country or international region) of a UE that has registered or registered NB-IoT, LTE-M, or WB-EUTRAN satellite access via the LCS service, if the coarse location information provided by the UE is determined to meet the accuracy requirements based on the location response message, the remaining steps are skipped.

[0050] If the location response message determines that the coarse location information provided by the UE does not meet the accuracy requirements, the MME sends a Location Reporting Control message to the Radio Access Network (RAN) indicating that the coarse location information does not meet the accuracy requirements and requests the RAN to trigger the process of reporting the UE's accurate location report.

[0051] In an exemplary embodiment, the location report control information may include previously obtained coarse location information of the UE, identification information of the UE, etc., to request the RAN to locate the precise location information of the UE based on the coarse location information of the UE in the location report control information and generate a corresponding location report.

[0052] The RAN can translate, calculate, and interpret the coarse location information of the UE to obtain the UE's precise User Location Information (ULI), and then send this precise ULI to the MME via location reporting. In an exemplary embodiment, the precise ULI may include the latest UE's TAI and CGI. Since the precise ULI reported by the RAN is obtained based on the coarse location information reported by the UE at its latest location, the ULI reported by the RAN is also called the updated ULI.

[0053] In an exemplary embodiment, the TAI provided by the RAN may include all broadcast TAIs corresponding to the UE. Further, if the RAN can determine the TAI the UE is currently in, it carries that TAI in the location report. In an exemplary embodiment, the RAN may also carry one or more TACs (Tracking Area Codes) of the PLMN (Public Land Mobile Network) selected by the UE in the location report, but this does not guarantee that the UE will always be located in one of these TACs.

[0054] The Public Land Mobile Network (PLMN) is used to uniquely identify a mobile network globally. It consists of the Mobile Country Code (MCC) and the Mobile Network Code (MNC). Different coding combinations can clearly distinguish mobile network operators in different countries and regions. The Tracking Area Code (TAC) is used to identify a geographical area in mobility management. In LTE and 5G networks, multiple cells can form a Tracking Area (TA), and the TAC is the code used to identify this TA. The Tracking Area Identifier (TAI) for LTE consists of the PLMN and the TAC, i.e., TAI = PLMN + TAC.

[0055] In an exemplary embodiment, the cell (ECGI) and TAI reported by the RAN refer to the fixed cell and fixed TA where the UE is located.

[0056] Since the ULI reported by the UE and the ULI reported by the RAN through the location report have the same format, both including TAI and CGI / ECGI, when the MME receives the initial ULI reported by the UE and the updated ULI reported by the RAN one after the other, it may confuse the ULI that needs to be used when performing network procedures such as location verification and user billing.

[0057] Therefore, in this embodiment of the present disclosure, the MME stores the user location information reported by the UE as first location information and the user location information reported by the RAN as second location information, and distinguishes them by a first identifier and a second identifier. In subsequent network processes, the MME can accurately identify the precise user location information reported by the RAN by the second identifier, thereby improving communication efficiency and accuracy.

[0058] In an exemplary embodiment, the network side, i.e., the MME, may add a first identifier and a second identifier to the received information.

[0059] Figure 2 This is a sub-flowchart of step S1 in one embodiment of this disclosure.

[0060] refer to Figure 2 In an exemplary embodiment, step S1 may include:

[0061] Step S11: The mobility management entity adds the first identifier to the user location information sent by the user equipment through the initial UE message;

[0062] Step S12, the mobility management entity adds the first identifier to the user location information sent by the user equipment through the first set of UL NAS transmission messages.

[0063] The first identifier added to the ULI (User Location Information) sent by the UE through the initial UE message and the first identifier added to the ULI sent by the UE through the first set of UL NAS transmission messages can be the same. For example, the first identifier can be added and stored after receiving the ULI sent by the UE through the initial UE message.

[0064] After receiving the ULI sent by the UE through the first set of UL NAS transmission messages, a first identifier is added to the ULI, replacing the previously stored ULI corresponding to the UE that includes the first identifier.

[0065] When adding the first identifier to a ULI, you can add the first identifier to the entire ULI, add the first identifier to TAI or CGI, or add the first identifier to both TAI and CGI.

[0066] There are multiple formats and implementation methods for the first identifier. The simplest implementation method is a serial number, and the simplest way to add it is to add the serial number to the filename or header of the file storing the first user location information. This disclosure does not impose any special restrictions on this.

[0067] Figure 3 This is a sub-flowchart of step S2 in one embodiment of this disclosure.

[0068] refer to Figure 3 In an exemplary embodiment, step S2 may include:

[0069] Step S21: The mobility management entity adds a second identifier to the user location information in the location report sent by the radio access network.

[0070] After receiving a location report from the RAN, the MME extracts the ULI from the location report, adds a second identifier to the ULI, and stores the ULI as the second user location information.

[0071] The second identifier can correspond to the first identifier for easy identification.

[0072] Figure 4 This is a schematic diagram illustrating the addition of a first identifier and a second identifier by the network side in an exemplary embodiment of this disclosure.

[0073] refer to Figure 4 The process of adding the first and second identifiers on the network side can include:

[0074] Event 41 occurs when the UE sends an attach request message to the eNodeB (base station), carrying the UE's TAI and CGI information. The base station is part of the RAN. Event 41 corresponds to the initial UE message.

[0075] Event 42: The eNodeB forwards an attach request message to the MME.

[0076] Event 43: When the MME receives a ULI (including TAI and CGI) reported by the UE, it adds a first identifier to the ULI and stores it.

[0077] Event 44 involves UE authentication and NAS security settings to activate integrity protection and NAS encryption processes, involving interactions between multiple network elements including MME, RAN / eNodeB, MME, SGSN, serving gateway, PDN gateway, PCRF, and HSS (this interaction process is not detailed here as it does not involve the core invention points). For satellite access on NB-IoT, if the UE indicates support for reporting its coarse location information, the MME can request the UE to send its coarse location information in a Secure Mode Command message, and then the UE reports its coarse location information to the MME in a Secure Mode Complete (SMC) message. To perform UE location verification, the MME provides the coarse location information reported by the UE to the E-SMLC. When the E-SMLC determines that the coarse location information does not meet the accuracy requirements for location verification, it notifies the MME through a location response message.

[0078] Event 45: The MME sends a location reporting control message to the RAN, which includes the coarse location information of the UE obtained previously, and requests the RAN to make a more accurate location report for the UE based on the coarse location information.

[0079] Event 46: The RAN determines the UE's location based on the received location report control information and the UE's coarse location information, triggering a more precise location information report (feedback) through the RAN. The UE's current TAI (Tracking Area Identifier) ​​information is provided to the MME as part of the UE location report. If the current TAI of the UE can be determined, the TAI is also reported to the MME.

[0080] In event 47, the RAN sends a location report to the MME, informing it of the updated UE location information. The RAN can provide all broadcast TAIs as part of the ULI to the MME. If the TAI where the UE is located can be determined, the RAN will also report that TAI. The cell and TAI reported by the RAN refer to the fixed cell and fixed TA where the UE is located. As part of the user location information, the RAN can also report one or more TACs of the selected PLMN, but it is not guaranteed that the UE will always be located in one of these TACs.

[0081] In Event 48, the MME adds a second identifier to the ULI in the received location report from the RAN and stores it as the second user location information. For the two UE location information received by the MME, the network process, such as location verification and user billing, is executed by judging the identifier information or its own configuration and using the judged ULI as the user location information.

[0082] Then, continue the Attach process as described in TS 23.401 5.3.2.1.

[0083] In an exemplary embodiment, communication obstacles (such as faults or congestion) may exist between the RAN and MME, and the process by which the RAN determines the latest ULI of the UE may also encounter problems, resulting in the RAN not receiving the location report control message or being unable to send the location report control message. To prevent the MME from waiting for the location report to time out and causing uncontrollable network failures, a timer is set after the MME sends the location report control information to improve network stability. This timer can also be called a protection timer.

[0084] Figure 5 This is a flowchart of an embodiment of the present disclosure of the MME sending a location report.

[0085] refer to Figure 5 The process of MME sending location reports may include:

[0086] Step S51: After the mobility management entity sends location report control information to the radio access network, it starts a timer for a preset duration.

[0087] Step S52: Before the timer reaches a preset duration, the mobility management entity waits to receive a location report from the radio access network.

[0088] Step S53: When the timer reaches the preset duration, the mobility management entity fails to receive the location report.

[0089] Figure 5 The embodiment shown can promptly stop waiting for a location report when the timer expires, resend the location report control information, or report an error to avoid the system falling into an uncontrollable state.

[0090] In addition to the MME adding the first and second identifiers, the UE and RAN can also add the first and second identifiers. In this case, the MME does not need to add identifiers and can directly store the received ULI. When used later, the second identifier is used to select the ULI from the RAN.

[0091] In an exemplary embodiment, if the user location information from the user equipment includes a first identifier, the mobility management entity stores the user location information from the user equipment including the first identifier as first user location information.

[0092] If the user location information from the radio access network includes a second identifier, the mobility management entity stores the user location information from the radio access network including the second identifier as the second user location information.

[0093] Figure 6 This is a flowchart of a method for managing user location information in an exemplary embodiment of this disclosure.

[0094] refer to Figure 6 In an exemplary embodiment, the method 600 applied to a narrowband IoT satellite scenario can be executed by a UE, including: step S61, whereby the user equipment sends user location information including a first identifier to a mobility management entity.

[0095] Specifically, the user equipment may add the first identifier to the user location information in the initial UE message; and the user equipment may add the first identifier to the user location information in the first set of UL NAS transmission messages.

[0096] In an exemplary embodiment, the first user location information includes the UE's TAI and CGI, and the UE may add a first identifier to the TAI and / or CGI. Alternatively, the UE may add the first identifier to the complete ULI containing the TAI and CGI.

[0097] Correspondingly, the mobility management entity stores the user location information from the user equipment, including the first identifier, as the first user location information.

[0098] The method for adding the first identifier to the UE can be the same as the method for adding the first identifier to the MME, such as adding a serial number to the header of the ULI file. Those skilled in the art can set it according to their actual needs.

[0099] Figure 7 This is a flowchart of a method for managing user location information in an exemplary embodiment of this disclosure.

[0100] refer to Figure 7 The method 700, applied to narrowband IoT satellite scenarios, can be executed by the radio access network (RAN) and includes:

[0101] In step S71, the radio access network sends user location information, including the second identifier, to the mobility management entity.

[0102] In method 700, the ULI sent by the RAN itself carries a second identifier. In this case, when the MME receives the ULI reported by the RAN through the location report, it can directly store the user location information from the radio access network, including the second identifier, as the second user location information.

[0103] Figure 8 This is a sub-flowchart of step S71 in an exemplary embodiment.

[0104] refer to Figure 8 In an exemplary embodiment, step S71 may include:

[0105] Step S711, the radio access network receives location report control information from the mobility management entity, the location report information including the identification information of the user equipment;

[0106] Step S712: The wireless access network obtains the user location information of the user equipment based on the location report control information;

[0107] In step S713, the radio access network sends a location report to the mobility management entity, the location report including the user location information of the user equipment and the second identifier.

[0108] In an exemplary embodiment, the location control report includes coarse location information of the user equipment. The radio access network determines the user location information of the user equipment based on the coarse location information and adds a second identifier to the user location information of the user equipment.

[0109] In addition to carrying the coarse location information reported by the UE in the location control report, the MME can also carry other information, such as the accuracy requirements for the updated ULI reported by the RAN. The information carried in the location control report can be adjusted according to actual needs.

[0110] The RAN can add a second identifier to the reported ULI in the same way as it adds a second identifier to the MME or adds a first identifier to the UE. For example, it can add a serial number to the header of the ULI file. Those skilled in the art can set it according to their actual needs.

[0111] Figure 9 This is a schematic diagram illustrating the addition of a first identifier and a second identifier by the UE side and the access side in an exemplary embodiment.

[0112] refer to Figure 9 The process of adding the first identifier and the second identifier by the UE side and the access side may include:

[0113] Event 91. The UE sends an attach request to the eNodeB base station, carrying the UE's TAI and CGI information in the request message. The UE adds a first identifier to the TAI and CGI, indicating that it is the initial ULI.

[0114] Event 92. The eNodeB forwards the attach request to the MME.

[0115] Event 93. UE authentication and NAS security settings to activate integrity protection and NAS encryption involve the interaction of multiple network elements, including MME, RAN / eNodeB, MME, SGSN, serving gateway, PDN gateway, PCRF, and HSS (this interaction process does not involve the core invention points and will not be elaborated here). For satellite access on NB-IoT, if the UE indicates support for reporting its coarse location information, the MME can request the UE to send its coarse location information in a Secure Mode Command message, and then the UE reports its coarse location information to the MME in a Secure Mode Complete (SMC) message. To perform UE location verification, the MME provides the reported coarse location information to the E-SMLC.

[0116] Event 94. The MME will send Location Reporting Control information (such as, but not limited to, Location Reporting Control information) to the RAN. This information includes previously obtained coarse UE location information, requesting the RAN to provide a more accurate location report for the UE based on the coarse UE location information, including the UE's TAI and CGI / ECGI information. To avoid timeouts while waiting for the RAN to report updated UE location information, a protection timer is set.

[0117] Event 95. The RAN determines the UE's location based on the received location report control information and the UE's coarse location information, triggering a more precise location information report (feedback) through the RAN. The current TAI (Tracking Area Identifier) ​​information is provided to the MME as part of the UE's location report. If the current TAI of the UE can be determined, the TAI is also reported to the MME.

[0118] Event 96. The RAN sends a Location Report message to the MME, notifying it of the updated UE location information. The RAN provides all broadcast TAIs as part of the ULI to the MME. If the TAI where the UE is located can be determined, the RAN will also report that TAI. The cell and TAI reported by the RAN refer to the fixed cell and fixed TA where the UE is located. As part of the user location information, the RAN also reports one or more TACs of the selected PLMN, but it is not guaranteed that the UE will always be located in one of these TACs. A second identifier is added to the updated UE location information to indicate that it is an updated ULI.

[0119] Then, continue the Attach process as described in TS 23.401 5.3.2.1.

[0120] In this embodiment of the disclosure, the process of adding the first identifier and the second identifier by the UE side and the access side can be as follows: In the initial UE message or the first set of UL NAS (Uplink Non-Access Stratum) transmission messages, the UE adds a first identifier to the initial TAI and CGI, which is called the initial ULI. Then, the MME obtains the UE coarse location information through the NAS SMC procedure, and the MME provides this coarse location information to the RAN side. The RAN adds a second identifier to the new ULI when reporting the location, which is called the updated ULI.

[0121] The process of adding the first and second identifiers on the network side can be as follows: After receiving the initial UE message or the first set of UL NAS transmission messages, the MME adds the first identifier to the TAI and CGI, which is the initial ULI. Then, the MME obtains the UE's coarse location information through the NAS SMC procedure. The MME provides the UE's coarse location information to the RAN side in the location report control information to obtain the new ULI from the location report provided by the RAN. The MME adds the second identifier to the new ULI, which is the updated ULI.

[0122] For the ULIs of two stored UEs, the MME determines the second identifier or its own configuration, and uses the ULI with the second identifier as the user location information to perform network processes such as location verification and user billing.

[0123] To prevent the MME from waiting for the ULI update to time out when the RAN sends a location report to the MME, a protection timer is set for this process to promptly resend the location report control information or promptly determine if the acquisition of the second user's location information has failed and start the subsequent process.

[0124] In summary, this embodiment addresses the NB-IoT satellite access scenario where the network receives multiple ULIs from different UEs, leading to confusion. By adding a first identifier and a second identifier to the UE's user location information on either the UE side or the network side, differentiation is achieved. This allows the MME to use updated user location information in subsequent network processes, avoiding the problem of the network and access network being unable to distinguish between the initial ULI and the updated ULI. Furthermore, a protection timer is set to prevent timeout while waiting for the RAN to return the updated ULI, supplementing the NB-IoT satellite access UE location verification process and further improving the integrated air-space-ground system.

[0125] Corresponding to the above method embodiments, this disclosure also provides a user location information management device, which can be used to execute the above method embodiments.

[0126] Figure 10 This is a block diagram of a user location information management device according to an exemplary embodiment of the present disclosure.

[0127] refer to Figure 10 The user location information management device 1000 set in the MME may include:

[0128] The first identification module 101 is configured to allow the mobility management entity to store user location information from the user equipment as first user location information, wherein the first user location information includes a first identifier;

[0129] The second identification module 102 is configured to store the user location information of the user equipment reported by the wireless access network to which the user equipment is connected as second user location information, and the second user location information includes a second identifier;

[0130] The location module 103 is configured to allow the mobility management entity to determine the location information of the second user based on the second identifier and to execute a network process using the second user location information, the network process including location verification.

[0131] Since the functions of the device 1000 have been described in detail in their corresponding method embodiments, they will not be repeated here.

[0132] It should be noted that although several modules or units for the device used to perform actions have been mentioned in the detailed description above, this division is not mandatory. In fact, according to embodiments of this disclosure, the features and functions of two or more modules or units described above can be embodied in one module or unit. Conversely, the features and functions of one module or unit described above can be further divided and embodied by multiple modules or units.

[0133] In an exemplary embodiment of this disclosure, a communication device capable of implementing the above-described method is also provided.

[0134] Those skilled in the art will understand that various aspects of the present invention can be implemented as systems, methods, or program products. Therefore, various aspects of the present invention can be specifically implemented in the following forms: entirely in hardware, entirely in software (including firmware, microcode, etc.), or in a combination of hardware and software, collectively referred to herein as “circuit,” “module,” or “system.”

[0135] The following reference Figure 11 To describe a communication device 1100 according to this embodiment of the present invention. Figure 11 The communication device 1100 shown is merely an example and should not impose any limitations on the functionality and scope of use of the embodiments of the present invention.

[0136] like Figure 11As shown, the components of the communication device 1100 may include, but are not limited to: at least one processing unit 1110, at least one storage unit 1120, and a bus 1130 connecting different system components (including storage unit 1120 and processing unit 1110).

[0137] The storage unit stores program code that can be executed by the processing unit 1110, causing the processing unit 1110 to perform the steps described in the "Exemplary Methods" section of this specification according to various exemplary embodiments of the present invention. For example, the processing unit 1110 can perform the method shown in the embodiments of this disclosure.

[0138] Storage unit 1120 may include readable media in the form of volatile storage units, such as random access memory (RAM) 11201 and / or cache memory 11202, and may further include read-only memory (ROM) 11203.

[0139] Storage unit 1120 may also include a program / utility 11204 having a set (at least one) program module 11205, such program module 11205 including but not limited to: operating system, one or more application programs, other program modules and program data, each or some combination of these examples may include an implementation of a network environment.

[0140] Bus 1130 can represent one or more of several types of bus structures, including a memory cell bus or memory cell controller, a peripheral bus, a graphics acceleration port, a processing unit, or a local bus using any of the various bus structures.

[0141] The communication device 1100 can also communicate with one or more external devices 1200 (e.g., keyboards, pointing devices, Bluetooth devices, etc.), one or more devices that enable a user to interact with the communication device 1100, and / or any device that enables the communication device 1100 to communicate with one or more other computing devices (e.g., routers, modems, etc.). This communication can be performed via input / output (I / O) interface 1150. Furthermore, the communication device 1100 can also communicate with one or more networks (e.g., local area networks (LANs), wide area networks (WANs), and / or public networks, such as the Internet) via network adapter 1160. As shown, network adapter 1160 communicates with other modules of the communication device 1100 via bus 1130. It should be understood that, although not shown in the figures, other hardware and / or software modules can be used in conjunction with the communication device 1100, including but not limited to: microcode, device drivers, redundant processing units, external disk drive arrays, RAID systems, tape drives, and data backup storage systems.

[0142] From the above description of the embodiments, those skilled in the art will readily understand that the exemplary embodiments described herein can be implemented by software or by combining software with necessary hardware. Therefore, the technical solutions according to the embodiments of this disclosure can be embodied in the form of a software product, which can be stored in a non-volatile storage medium (such as a CD-ROM, USB flash drive, external hard drive, etc.) or on a network, including several instructions to cause a computing device (such as a personal computer, server, terminal device, or network device, etc.) to execute the methods according to the embodiments of this disclosure.

[0143] In exemplary embodiments of this disclosure, a computer-readable storage medium is also provided, on which a program product capable of implementing the methods described above is stored. In some possible embodiments, various aspects of the invention may also be implemented as a program product comprising program code that, when the program product is run on a terminal device, causes the terminal device to perform the steps of the various exemplary embodiments of the invention described in the "Exemplary Methods" section of this specification.

[0144] The program product for implementing the above-described method according to embodiments of the present invention may employ a portable compact disc read-only memory (CD-ROM) and include program code, and may run on a terminal device, such as a personal computer. However, the program product of the present invention is not limited thereto. In this document, the readable storage medium may be any tangible medium containing or storing a program that may be used by or in conjunction with an instruction execution system, apparatus, or device.

[0145] The program product may employ any combination of one or more readable media. A readable medium may be a readable signal medium or a readable storage medium. A readable storage medium may be, for example, but not limited to, an electrical, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any combination thereof. More specific examples of readable storage media (a non-exhaustive list) include: an electrical connection having one or more wires, a portable disk, a hard disk, random access memory (RAM), read-only memory (ROM), erasable programmable read-only memory (EPROM or flash memory), optical fiber, portable compact disk read-only memory (CD-ROM), optical storage devices, magnetic storage devices, or any suitable combination thereof.

[0146] Computer-readable signal media may include data signals propagated in baseband or as part of a carrier wave, carrying readable program code. Such propagated data signals may take various forms, including but not limited to electromagnetic signals, optical signals, or any suitable combination thereof. A readable signal medium may also be any readable medium other than a readable storage medium, capable of sending, propagating, or transmitting programs for use by or in conjunction with an instruction execution system, apparatus, or device.

[0147] The program code contained on the readable medium may be transmitted using any suitable medium, including but not limited to wireless, wired, optical fiber, RF, etc., or any suitable combination thereof.

[0148] Program code for performing the operations of this invention can be written in any combination of one or more programming languages, including object-oriented programming languages ​​such as Java and C++, and conventional procedural programming languages ​​such as C or similar languages. The program code can execute entirely on the user's computing device, partially on the user's device, as a standalone software package, partially on the user's computing device and partially on a remote computing device, or entirely on a remote computing device or server. In cases involving remote computing devices, the remote computing device can be connected to the user's computing device via any type of network, including a local area network (LAN) or a wide area network (WAN), or it can be connected to an external computing device (e.g., via the Internet using an Internet service provider).

[0149] Furthermore, the above figures are merely illustrative of the processes included in the method according to exemplary embodiments of the present invention, and are not intended to be limiting. It is readily understood that the processes shown in the above figures do not indicate or limit the temporal order of these processes. Additionally, it is readily understood that these processes may be executed synchronously or asynchronously, for example, in multiple modules.

[0150] Other embodiments of this disclosure will readily occur to those skilled in the art upon consideration of the specification and practice of the invention disclosed herein. This application is intended to cover any variations, uses, or adaptations of this disclosure that follow the general principles of this disclosure and include common knowledge or customary techniques in the art not disclosed herein. The specification and examples are to be considered exemplary only, and the true scope and concept of this disclosure are indicated by the claims.

Claims

1. A method for managing user location information, characterized in that, Applications include narrowband IoT satellite scenarios, including: The mobility management entity stores user location information from user equipment as first user location information, the first user location information including a first identifier; The mobility management entity stores the user location information of the user equipment reported by the radio access network to which the user equipment is connected as second user location information. The second user location information includes a second identifier, wherein the first identifier and the second identifier are used to distinguish the first user location information and the second user location information. The mobility management entity determines the second user location information based on the second identifier and performs network procedures using the second user location information, the network procedures including location verification; The mobility management entity stores the user location information of the user equipment reported by the radio access network to which the user equipment is connected as second user location information, including: The mobility management entity obtains coarse location information of the user equipment from the user equipment; The mobility management entity provides the coarse location information to the E-SMLC for location verification; When the location response message sent by the E-SMLC determines that the coarse location information does not meet the accuracy requirements, the mobility management entity sends location report control information to the radio access network to request the radio access network to provide the user location information of the user equipment through location reporting. The location report control information is used to indicate that the coarse location information does not meet the accuracy requirements of location verification.

2. The user location information management method as described in claim 1, characterized in that, The mobility management entity stores user location information from user equipment as first user location information, including: The mobility management entity adds the first identifier to the user location information sent by the user equipment via the initial UE message; The mobility management entity adds the first identifier to the user location information sent by the user equipment through the first set of UL NAS transmission messages.

3. The user location information management method as described in claim 1, characterized in that, The mobility management entity stores the user location information of the user equipment reported by the radio access network to which the user equipment is connected as second user location information, including: The mobility management entity adds the second identifier to the user location information in the location report sent by the radio access network.

4. The user location information management method as described in claim 1, characterized in that, The mobility management entity stores user location information from user equipment as first user location information, including: The user location information from the user equipment includes the first identifier, and the mobility management entity stores the user location information from the user equipment including the first identifier as the first user location information.

5. The user location information management method as described in claim 1, characterized in that, The mobility management entity stores the user location information of the user equipment reported by the radio access network to which the user equipment is connected as second user location information, including: The user location information from the radio access network includes the second identifier, and the mobility management entity stores the user location information from the radio access network including the second identifier as the second user location information.

6. The user location information management method as described in claim 1, characterized in that, The location reporting control information includes the identification information of the user equipment and the coarse location information.

7. The user location information management method as described in claim 1, characterized in that, The mobility management entity sends location report control information to the radio access network, including: After the mobility management entity sends location report control information to the radio access network, it starts a timer, which corresponds to a preset duration. Before the timer reaches the preset duration, the mobility management entity waits to receive the location report from the radio access network; When the timer reaches the preset duration, the mobility management entity receives the location report and fails.

8. The user location information management method as described in claim 1, characterized in that, Both the first user location information and the second user location information include the tracking area identifier and the cell global identification code of the user equipment.

9. A method for managing user location information, characterized in that, Applications include narrowband IoT satellite scenarios, including: The user equipment sends user location information, including a first identifier, to the mobility management entity; The mobility management entity stores user location information from the user equipment as first user location information, which includes a first identifier; the mobility management entity stores user location information reported by the radio access network to which the user equipment is connected as second user location information, which includes a second identifier; the first identifier and the second identifier are used to distinguish between the first user location information and the second user location information; the mobility management entity determines the second user location information based on the second identifier and uses the second user location information to execute network procedures, which include location verification.

10. The user location information management method as described in claim 9, characterized in that, The user equipment sends user location information, including a first identifier, to the mobility management entity, including: The user equipment adds the first identifier to the user location information in the initial UE message; In the first set of UL NAS transmission messages, the user equipment adds the first identifier to the user location information.

11. The user location information management method as described in claim 9, characterized in that, The user equipment sends user location information, including a first identifier, to the mobility management entity, including: The first user location information includes the tracking area identifier and the cell global identification code of the user equipment, and the user equipment adds the first identifier to the tracking area identifier and / or the cell global identification code.

12. A method for managing user location information, characterized in that, Applications include narrowband IoT satellite scenarios, including: The radio access network sends user location information, including a second identifier, to the mobility management entity; The mobility management entity stores user location information from the user equipment as first user location information, which includes a first identifier; the mobility management entity stores user location information reported by the radio access network to which the user equipment is connected as second user location information, which includes a second identifier; the first identifier and the second identifier are used to distinguish between the first user location information and the second user location information; the mobility management entity determines the second user location information based on the second identifier and uses the second user location information to execute network procedures, which include location verification.

13. The user location information management method as described in claim 12, characterized in that, The radio access network sends user location information, including a second identifier, to the mobility management entity, including: The radio access network receives location reporting control information from a mobility management entity, the location reporting control information including user equipment identification information and coarse location information of the user equipment; The wireless access network obtains the user location information of the user equipment based on the location report control information, and adds the second identifier to the user location information; The radio access network sends a location report to the mobility management entity, the location report including the user location information of the user equipment and the second identifier.

14. The user location information management method as described in claim 13, characterized in that, The wireless access network obtains the user location information of the user equipment based on the location report control information, including: The wireless access network identifies the coarse location information to determine the user location information of the user equipment.

15. A communication device, characterized in that, include: Memory; as well as A processor coupled to the memory, the processor being configured to perform the method as described in any one of claims 1-14 based on instructions stored in the memory.

16. A computer-readable storage medium having a program stored thereon that, when executed by a processor, implements the method as claimed in any one of claims 1-14.

17. A computer program product, comprising a computer program, characterized in that, When executed by a processor, the computer program implements the steps of the method according to any one of claims 1-14.

Images