User position information management method and communication equipment

Abstract

The invention provides a user position information management method and communication equipment, and relates to the technical field of space-air-ground communication. The user position information management method comprises the following steps: a mobility management entity stores user position information from user equipment as first user position information, wherein the first user position information comprises a first identifier; the mobility management entity stores the user position information of the user equipment reported by a wireless access network connected with the user equipment as second user position information, wherein the second user position 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 execute a network process, the network process comprising location verification. According to the embodiment of the invention, the mobility management entity can use the accurate user position information to complete the position verification of the user equipment.

Description

Background Art

[0002] For the NB-IoT (Narrow Band Internet of Things) satellite access scenario, relevant communication standards stipulate that in some deployments, the UE (User Equipment) location cannot be provided through the LPP (Location Position Protocol). Therefore, the UE user location information is provided through the NAS (Non-Access Stratum). The MME (Mobility Management Entity) requests the UE's rough location information, and the UE provides the rough location information through the SMC (Security Mode Control) procedure. Subsequently, the MME can provide the rough 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) process for location verification.

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

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

[0005] The purpose of the present disclosure is to provide a management method and communication device for user location information applicable to the NB-IoT satellite access scenario, so that the MME can accurately use the precise UE user location information for location verification of the user equipment.

[0006] According to a first aspect of the embodiments of the present disclosure, a method for managing user location information is provided, including: a mobility management entity stores user location information from a user equipment as first user location information, where the first user location information includes 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, where the second user location information includes a second identifier; the mobility management entity determines the second user location information according to the second identifier, and uses the second user location information to execute a network process, where the network process includes location verification.

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

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

[0009] According to a fourth aspect of the present disclosure, a communication device is provided, including: a memory; and a processor coupled to the memory, where the processor is configured to execute the method as described in any one of the above based on instructions stored in the memory.

[0010] According to a fifth aspect of the present disclosure, a computer-readable storage medium is provided, on which a program is stored, and when the program is executed by a processor, the method for managing user location information as described in any one of the above is implemented.

[0011] According to a fifth aspect of the present disclosure, a computer program product is provided, including a computer program, and when the computer program is executed by a processor, the steps of the method as described in any one of the above are implemented.

[0012] In the embodiments of the present disclosure, in the MME, user location information from the UE is stored as first user location information including a first identifier, user location information from the RAN is stored as second user location information including a second identifier, and in subsequent steps, the second user location information is located according to the second identifier, enabling the MME to use the second user location information to execute network processes. This allows the MME to use accurate UE user location information for services such as UE location verification, solving the problem that the MME may receive multiple UE user location information under the new communication standard of narrowband Internet of Things, which may lead to information confusion, and improving communication efficiency and accuracy.

[0013] It should be understood that the above general description and the following detailed description are only exemplary and explanatory, and cannot limit the present disclosure. BRIEF DESCRIPTION OF THE DRAWINGS

[0014] The accompanying drawings herein are incorporated into and constitute a part of this specification, showing embodiments consistent with the present disclosure, and are used together with the specification to explain the principles of the present disclosure. Obviously, the accompanying drawings in the following description are only some embodiments of the present disclosure, and those of ordinary skill in the art can obtain other drawings based on these drawings without creative efforts.

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

[0016] Figure 2 is a sub - flowchart of step S1 in an embodiment of the present disclosure.

[0017] Figure 3 is a sub - flowchart of step S2 in an embodiment of the present disclosure.

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

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

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

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

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

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

[0024] Figure 10 is a block diagram of a device for managing user location information in an exemplary embodiment of the present disclosure.

[0025] Figure 11 is a block diagram of a communication device in an exemplary embodiment of the present disclosure. Detailed Embodiments

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

[0027] In addition, the accompanying drawings are only schematic illustrations of the present disclosure, and the same reference numerals in the drawings denote the same or similar parts, and thus repeated descriptions thereof will be omitted. Some of the 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 form, or in one or more hardware modules or integrated circuits, or in different networks and / or processor devices and / or microcontroller devices.

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

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

[0030] Referring to Figure 1 , the method 100 applied to the narrowband Internet of Things satellite scenario can be executed by the MME and may include: Step S1, the mobility management entity stores the user location information from the user equipment as first user location information, and the first user location information includes a first identifier; 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, and the second user location information includes a second identifier; Step S3, the mobility management entity determines the second user location information according to the second identifier, and uses the second user location information to execute a network process, and the network process includes location verification.

[0031] In the embodiments of the present disclosure, in the MME, the user location information from the UE is stored as the first user location information including the first identifier, and the user location information from the RAN is stored as the second user location information including the second identifier. Subsequently, when the second user location information is located according to the second identifier, the MME uses the second user location information to execute network processes, enabling the MME to use accurate UE user location information for services such as UE location verification, and solving the problem that the MME may receive multiple UE user location information under the new communication standard regulations of narrowband Internet of Things, which may lead to information confusion, and improving communication efficiency and accuracy.

[0032] In the embodiments of the present disclosure, the first user location information includes the user location information sent by the UE in the initial UE message or the first set of UL NAS transport messages.

[0033] The initial UE message is the first message sent by the UE to the MME through the base station after completing the RRC connection establishment with the base station, which initiates the signaling interaction process between the UE and the core network. When the UE establishes a connection with the network, the UE notifies the network of its basic information and access request, enabling the network side to identify the UE and perform subsequent processing, such as resource allocation and security authentication. The UE will include user location information such as TAI, UE identification information, selected PLMN information, NAS layer signaling (such as Attach Request message, etc.), security-related parameters, UE capability information, etc. in the initial UE message.

[0034] After the initial UE message, when the UE has further NAS signaling to send to the core network, it will be transmitted through the first set of UL NAS transport messages. For example, in the attachment process, the UE may first send an Attach Request in the initial UE message and may subsequently send relevant authentication response messages through the first set of UL NAS transport messages.

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

[0036] User location information such as TAI in the initial UE message is used to help the network initially determine the location of the UE, so as to perform subsequent resource allocation and paging area setting, etc.; the user location information such as TAI in the first group of UL NAS transport messages is to continuously update the user location information of the UE 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 and other operations.

[0037] Among them, the User Location Information (ULI) is used to identify the location information of the user equipment, and may include TAI (Tracking Area Identity) and cell ID. In a communication network, TAI is used to track the location of the UE in a larger range, 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 location information of the UE user, so that the network can perform operations such as paging and location update.

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

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

[0040] At the SA2#161 meeting, for the case of NB-IoT satellite access, if the UE location cannot be provided through the LPP (Location Position Protocol) in some deployments, it is necessary to increase the possibility of providing the UE location information through the NAS, and descriptions of the MME requesting the UE rough location information and the UE providing the rough location information through the SMC procedure are added to the Attach and TAU procedures in TS 23.401. After that, the MME can provide the UE rough location information to the E-SMLC to execute the EPC-NI-LR process for location verification.

[0041] In an exemplary embodiment, the MME may obtain the rough location information reported by the UE through the NAS SMC procedure. This rough location information is different from the ULI and is represented by only a small amount of code. The network side translates and interprets the code in the rough location information to obtain the user location information for location verification. However, the rough location information reported by the UE may not meet the accuracy requirements for location verification.

[0042] To overcome the problem that the rough location information sent by the UE cannot meet the accuracy requirements for location verification, a strategy is proposed that after receiving the rough location information provided by the UE, the MME sends location report control information to the RAN (Radio Access Network) to request the radio access network to provide the user location information of the user equipment through a location report.

[0043] In an exemplary embodiment, after receiving the rough location information provided by the UE, the MME may provide the rough location information of the UE to the E-SMLC to perform the EPC-NI-LR process for location verification. The specific process is, for example: the MME selects the E-SMLC and sends a location request message to the selected E-SMLC; among them, the location request includes the type of location information requested, the requested QoS, the serving cell identity, the rough location information of the UE (in the case of NB-IoT satellite access), and the UE's ability to support LPP. The E-SMLC determines whether the obtained location estimate meets the accuracy requested by the MME based on the parameters received from the MME (such as cell identity or rough location information), and responds by sending a location response message to the MME.

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

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

[0046] Furthermore, when the MME decides to verify the registration or register the location (country or international region) of the UE accessing NB-IoT, LTE-M, or WB-EUTRAN satellites through the LCS service, if it is determined according to the location response message that the rough location information provided by the UE meets the accuracy requirements, the remaining steps are skipped.

[0047] If it is determined according to the location response message that the rough location information provided by the UE does not meet the accuracy requirement, the MME sends location reporting control information (Location Reporting Control) to the radio access network (RAN), indicating that the rough location information at this time does not meet the accuracy requirement, and requests to trigger the process of the RAN reporting the accurate location report of the UE.

[0048] In an exemplary embodiment, the location reporting control information may include information such as the previously obtained rough location information of the UE and the identification information of the UE, so as to request the RAN to locate the accurate location information of the UE according to the rough location information of the UE in the location reporting control information and generate a corresponding location report.

[0049] The RAN can translate, calculate, and interpret the rough location information of the UE to obtain the accurate user location information (ULI) of the UE, and send the accurate user location information to the MME through a location report. In an exemplary embodiment, the accurate user location information may include the latest TAI and CGI of the UE. Since the accurate user location information reported by the RAN, that is, the ULI, is obtained according to the rough location information reported by the UE at the latest location, the ULI reported by the RAN is also called the updated ULI.

[0050] 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 where the UE is currently located, the TAI is carried 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 it cannot be guaranteed that the UE is always located in one of these TACs.

[0051] Among them, the PLMN (Public Land Mobile Network) is used to globally uniquely identify a mobile network and is composed of an MCC (Mobile Country Code) and an MNC (Mobile Network Code). Through different coding combinations, different mobile network operators in different countries and regions can be clearly distinguished. The TAC (Tracking Area Code) 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 TAI is the LTE tracking area identifier and is composed of the PLMN and the TAC, that is, TAI = PLMN + TAC.

[0052] 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.

[0053] 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 successively receives the initial ULI reported by the UE and the updated ULI reported by the RAN, it may be confused about which ULI to use when performing subsequent network processes, such as location verification and user billing.

[0054] Therefore, in the embodiments of the present disclosure, the MME is configured to store the user location information reported by the UE as the first location information, store the user location information reported by the RAN as the second location information, and distinguish them by the first identifier and the second identifier. Thus, in subsequent network processes, the MME can accurately identify the precise user location information reported by the RAN through the second identifier, improving communication efficiency and accuracy.

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

[0056] Figure 2 It is a sub - flow chart of step S1 in an embodiment of the present disclosure.

[0057] Reference Figure 2 , in an exemplary embodiment, step S1 may include: 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; Step S12, the mobility management entity adds the first identifier to the user location information sent by the user equipment through the first group of UL NAS transport messages.

[0058] Among them, the first identifier added to the ULI (user location information, the same below) sent by the UE through the initial UE message and the first identifier added to the ULI sent by the UE through the first group of UL NAS transport messages may be the same. For example, after receiving the ULI sent by the UE through the initial UE message, the first identifier may be added and stored.

[0059] After receiving the ULI sent by the UE through the first group of UL NAS transport messages, the first identifier is added to the ULI, replacing the ULI including the first identifier corresponding to the UE stored previously.

[0060] In the process of adding the first identifier to the ULI, the first identifier may be added to the entire ULI, or to the TAI or CGI therein, or to both the TAI and CGI therein.

[0061] There can be multiple formats and implementation methods for the first identifier. The simplest implementation method is a serial number, and the simplest addition method is to add the serial number in the file name or file header storing the first user location information. The present disclosure does not impose special restrictions on this.

[0062] Figure 3 It is a sub - flowchart of step S2 in an embodiment of the present disclosure.

[0063] Reference Figure 3 , in an exemplary embodiment, step S2 may include: 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.

[0064] After receiving the 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.

[0065] The method of the second identifier can correspond to the first identifier for easy identification.

[0066] Figure 4 It is a schematic diagram of adding the first identifier and the second identifier by the network side in an exemplary embodiment of the present disclosure.

[0067] Reference Figure 4 , the process of the network side adding the first identifier and the second identifier may include: Event 41, the UE sends an attachment request message to the eNodeB (base station), and the attachment request message carries the TAI and CGI information of the UE. Among them, the base station is a part of the RAN. Event 41 corresponds to the initial UE message.

[0068] Event 42, the eNodeB forwards the attachment request message to the MME.

[0069] Event 43, when the MME receives the ULI reported by the UE including the TAI and CGI, it adds the first identifier to the ULI and stores it.

[0070] Event 44: UE authentication and NAS security settings to activate the integrity protection and NAS encryption processes, involving the interaction of multiple network elements such as MME, RAN / eNodeB, MME, SGSN, serving gateway, PDN gateway, PCRF, HSS, etc. (since this interaction process does not involve the core invention points, it 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 the security mode command message, and then the UE reports its coarse location information to the MME in the security 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.

[0071] Event 45: The MME sends location report control information to the RAN. This location report control information includes the previously obtained coarse location information of the UE and requests the RAN to perform a more accurate location report for the UE based on this coarse location information.

[0072] Event 46: The RAN locates the UE's position based on the received location report control information and the UE's coarse location information, triggering the reporting (feedback) of more accurate location information through the RAN. The current TAI (Tracking Area Identity) information of the UE is provided to the MME as part of the UE location report. If the current TAI where the UE is located can be determined, it is also reported to the MME.

[0073] Event 47: The RAN sends a location report to notify the MME of the updated UE location information. The RAN can provide all broadcast TAIs to the MME as part of the ULI. If the TAI where the UE is located can be determined, the RAN also reports this TAI. The cell and TAI reported by the RAN refer to the fixed cell and fixed TAI 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 cannot be guaranteed that the UE is always located in one of these TACs.

[0074] Event 48: The MME adds a second identifier to the ULI in the location report received from the RAN and stores it as the second user location information. For the two UE location information received by the MME, by judging the identification information or its own configuration, the judged ULI is used as the user location information to execute network processes such as location verification and user charging.

[0075] After that, continue with the Attach process as described in TS 23.401 5.3.2.1.

[0076] In an exemplary embodiment, due to possible communication obstacles (such as faults or congestion) between the RAN and the MME, and problems may also occur in the process of the RAN determining the latest ULI of the UE, resulting in the RAN not receiving the location report control message, or the RAN 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 referred to as a protection timer.

[0077] Figure 5 It is a flowchart of the MME sending a location report in an embodiment of the present disclosure.

[0078] Refer to Figure 5 , the process of the MME sending a location report may include: Step S51, after the mobility management entity sends location report control information to the radio access network, start a timer, and the timer corresponds to a preset duration; Step S52, before the running duration of the timer reaches the preset duration, the mobility management entity waits to receive a location report from the radio access network; Step S53, when the running duration of the timer reaches the preset duration, the mobility management entity fails to receive the location report.

[0079] Figure 5 The illustrated embodiment can stop waiting for the location report in time when the timer times out, resend the location report control information, or report an error to avoid the system falling into an uncontrollable state.

[0080] In addition to the MME adding the first identifier and the second identifier, the UE and the RAN can also add the first identifier and the second identifier. In this case, the MME can directly store the received ULI without adding an identifier, and select the ULI from the RAN through the second identifier when used later.

[0081] 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 the first user location information.

[0082] 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.

[0083] Figure 6 It is a flowchart of a method for managing user location information in an exemplary embodiment of the present disclosure.

[0084] Refer to Figure 6, in an exemplary embodiment, the method 600 applied to the narrowband Internet of Things satellite scenario may be executed by a UE, including: Step S61, the user equipment sends user location information including a first identifier to the mobility management entity.

[0085] Wherein, the user equipment may add the first identifier to the user location information in the initial UE message; and, the user equipment adds the first identifier to the user location information in the first set of UL NAS transport messages.

[0086] In an exemplary embodiment, the first user location information includes the TAI and CGI of the UE, and the UE may add the first identifier to the TAI and / or CGI. Alternatively, the UE may add the first identifier to the complete ULI including the TAI and CGI.

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

[0088] The way for the UE to add the first identifier may be the same as the way for the MME to add the first identifier. For example, add a serial number to the header of the ULI, etc., and those skilled in the art can set it according to actual needs.

[0089] Figure 7 is a flowchart of the method for managing user location information in an exemplary embodiment of the present disclosure.

[0090] Refer to Figure 7 , the method 700 applied to the narrowband Internet of Things satellite scenario may be executed by the radio access network RAN, including: Step S71, the radio access network sends user location information including a second identifier to the mobility management entity.

[0091] In the method 700, the ULI sent by the RAN itself carries the second identifier. At this time, 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.

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

[0093] Refer to Figure 8 , in an exemplary embodiment, step S71 may include: Step S711, the radio access network receives location report control information from the mobility management entity, and the location report information includes the identifier information of the user equipment; Step S712, the radio access network obtains the user location information of the user equipment according to the location report control information; Step S713, the radio access network sends a location report to the mobility management entity, where the location report includes the user location information of the user equipment and the second identifier.

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

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

[0096] The manner in which the RAN adds the second identifier to the reported ULI can be the same as the manner in which the MME adds the second identifier or the manner in which the UE adds the first identifier. For example, a serial number is added to the file header of the ULI. Those skilled in the art can set it according to actual needs.

[0097] Figure 9 It is a schematic diagram of adding the first identifier and the second identifier by the UE side and the access side in an exemplary embodiment.

[0098] Reference Figure 9 , the process of adding the first identifier and the second identifier by the UE side and the access side may include: Event 91. The UE sends an attachment request to the eNodeB base station, and the request message carries the TAI and CGI information of the UE. The UE adds a first identifier to the TAI and CGI, indicating that it is the initial ULI.

[0099] Event 92. The eNodeB forwards the attachment request to the MME.

[0100] Event 93. UE authentication and NAS security settings to activate integrity protection and NAS encryption involve the interaction of multiple network elements such as the MME, RAN / eNodeB, MME, SGSN, serving gateway, PDN gateway, PCRF, HSS, etc. (Since this interaction process does not involve the core inventive point, it will not be elaborated here). For satellite access on NB-IoT, if the UE indicates that it supports reporting its rough location information, the MME can request the UE to send its rough location information in the security mode command message, and then the UE reports its rough location information to the MME in the security mode complete (SMC) message. To perform UE location verification, the MME provides the reported rough location information to the E-SMLC.

[0101] 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 the previously obtained rough location information of the UE, and requests the RAN to perform a more accurate location report for this UE based on the rough location information of the UE, including information such as the TAI and CGI / ECGI of the UE. To avoid waiting for the RAN to report and update the UE location information to timeout, a protection timer is set.

[0102] Event 95. The RAN locates the UE location based on the received location reporting control information and the rough location information of the UE, and triggers the reporting (feedback) of more accurate location information through the RAN. The current TAI (Tracking Area Identity) information is provided to the MME as part of the UE location report. If the current TAI where the UE is located can be determined, the RAN also reports this TAI to the MME.

[0103] Event 96. The RAN sends a location report message to notify the MME of the updated location information of the UE. The RAN provides all broadcast TAIs to the MME as part of the ULI. If the TAI where the UE is located can be determined, the RAN also reports this TAI. The cell and TAI reported by the RAN refer to the fixed cell and fixed TAI 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 cannot be guaranteed that the UE is always 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.

[0104] After that, continue with the Attach process as described in TS 23.401 5.3.2.1.

[0105] In the embodiment of the present 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 group of UL NAS (Uplink Non - Access Stratum) transmission messages, the UE adds the first identifier to the initial TAI and CGI, and calls it the initial ULI. Then, the MME obtains the rough location information of the UE through the NAS SMC process, the MME provides this rough location information to the RAN side, and the RAN adds the second identifier to the new ULI during the location report, and calls it the updated ULI.

[0106] The process of adding the first identifier and the second identifier by the network side can be as follows: After receiving the initial UE message or the first set of UL NAS transport messages, the MME adds the first identifier to the TAI and CGI therein to obtain the initial ULI. Then, the MME obtains the rough location information of the UE through the NAS SMC process. The MME provides the rough location information of the UE to the RAN side in the location report control information to obtain a new ULI from the location report provided by the RAN. The MME adds the second identifier to the new ULI to obtain the updated ULI.

[0107] For the two ULIs of the UE stored by the MME, by judging the second identifier or its own configuration, the MME uses the ULI with the second identifier as the user location information to execute network processes such as location verification and user charging.

[0108] To avoid the MME waiting for the updated ULI to time out when the RAN sends a location report to the MME, a protection timer is set for this process to resend the location report control information in a timely manner or to determine in a timely manner that the acquisition of the second user location information fails and start subsequent processes.

[0109] In summary, in the embodiments of the present disclosure, for the NB-IoT satellite access scenario, the network side receives multiple ULIs of UEs, resulting in confusion. By adding the first identifier and the second identifier to the user location information of the UE on the UE side or the network side for differentiation, the MME can use the updated user location information in subsequent network processes, avoiding the problem that the network and the access network cannot distinguish between the initial ULI and the updated ULI. In addition, when waiting for the RAN to return the updated ULI, a protection timer is set to avoid timeout, realizing the supplement of the location verification process for NB-IoT satellite access UEs and further improving the space-air-ground integrated system.

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

[0111] Figure 10 It is a block diagram of a management device for user location information in an exemplary embodiment of the present disclosure.

[0112] Reference Figure 10 As shown in, the management device 1000 for user location information provided in the MME may include: The first identifier module 101 is configured such that the mobility management entity stores the user location information from the user equipment as the first user location information, and the first user location information includes the first identifier; The second identifier module 102 is configured such 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 the second user location information, and the second user location information includes the second identifier; The location search and positioning module 103 is configured such that the mobility management entity determines the second user location information according to the second identifier, and uses the second user location information to execute a network process, where the network process includes location verification.

[0113] Since the functions of the apparatus 1000 have been described in detail in their corresponding method embodiments, they will not be elaborated herein.

[0114] It should be noted that although several modules or units of a device for action execution are mentioned in the above detailed description, such a division is not mandatory. In fact, according to the embodiments of the present disclosure, the features and functions of two or more of the above-described modules or units 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.

[0115] In an exemplary embodiment of the present disclosure, a communication device capable of implementing the above method is also provided.

[0116] Those skilled in the art to which the present invention pertains can understand that various aspects of the present invention can be implemented as a system, a method, or a program product. Therefore, various aspects of the present invention can be specifically implemented in the following forms, namely: a complete hardware implementation, a complete software implementation (including firmware, microcode, etc.), or an implementation combining hardware and software aspects, which can be collectively referred to herein as "circuitry", "module", or "system".

[0117] Reference is now made to Figure 11 describe the communication device 1100 according to this embodiment of the present invention. Figure 11 The illustrated communication device 1100 is merely an example and should not impose any limitation on the functions and scope of use of the embodiments of the present invention.

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

[0119] Among them, the storage unit stores program code, and the program code can be executed by the processing unit 1110, so that the processing unit 1110 executes the steps according to various exemplary embodiments of the present invention described in the above "Exemplary Method" section of this specification. For example, the processing unit 1110 can execute the method as shown in the embodiments of the present disclosure.

[0120] The storage unit 1120 may include a readable medium in the form of a volatile storage unit, such as a random access storage unit (RAM) 11201 and / or a cache storage unit 11202, and may further include a read-only storage unit (ROM) 11203.

[0121] The storage unit 1120 may also include a program / utilities 11204 having a set (at least one) of program modules 11205. Such program modules 11205 include, but are not limited to: an 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.

[0122] The bus 1130 may represent one or more of several types of bus structures, including a memory bus or memory controller, a peripheral bus, an accelerated graphics port, a processing unit, or a local bus using any of a variety of bus structures.

[0123] The communication device 1100 may also communicate with one or more external devices 1200 (such as a keyboard, a pointing device, a Bluetooth device, etc.), may also communicate with one or more devices that enable a user to interact with the communication device 1100, and / or may communicate with any device that enables the communication device 1100 to communicate with one or more other computing devices (such as a router, a modem, etc.). Such communication may be through an input / output (I / O) interface 1150. Further, the communication device 1100 may also communicate with one or more networks (such as a local area network (LAN), a wide area network (WAN), and / or a public network, such as the Internet) through a network adapter 1160. As shown in the figure, the network adapter 1160 communicates with other modules of the communication device 1100 through the bus 1130. It should be understood that although not shown in the figure, other hardware and / or software modules may 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, etc.

[0124] Through the description of the above embodiments, those skilled in the art can easily understand that the example embodiments described herein can be implemented by software, or can be implemented by a combination of software and necessary hardware. Therefore, the technical solutions according to the embodiments of the present disclosure can be embodied in the form of a software product, which can be stored in a non-volatile storage medium (which can be a CD-ROM, a USB flash drive, a mobile hard disk, etc.) or on a network, including several instructions to enable a computing device (which can be a personal computer, a server, a terminal device, or a network device, etc.) to execute the method according to the embodiments of the present disclosure.

[0125] In an exemplary embodiment of the present disclosure, there is also provided a computer-readable storage medium, on which a program product capable of implementing the above methods of this specification is stored. In some possible implementation manners, various aspects of the present invention can also be implemented in the form of a program product, which includes program code. When the program product runs on a terminal device, the program code is used to cause the terminal device to execute the steps according to various exemplary embodiments of the present invention described in the above "Exemplary Method" section of this specification.

[0126] The program product for implementing the above method according to an embodiment of the present invention may be a portable compact disc read-only memory (CD-ROM) and includes program code, and can 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, a readable storage medium may be any tangible medium that contains or stores a program, and this program can be used by or in combination with an instruction execution system, apparatus, or device.

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

[0128] The computer-readable signal medium may include a data signal propagated in a baseband or as part of a carrier wave, which carries the readable program code. Such a propagated data signal may take various forms, including but not limited to an electromagnetic signal, an optical signal, or any suitable combination of the above. The readable signal medium may also be any readable medium other than the readable storage medium, and this readable medium can send, propagate, or transmit a program for use by or in combination with an instruction execution system, apparatus, or device.

[0129] The program code contained on the readable medium can be transmitted by any appropriate medium, including but not limited to wireless, wired, optical cable, RF, etc., or any suitable combination of the above.

[0130] The program code for performing the operations of the present invention can be written in any combination of one or more programming languages, including object-oriented programming languages such as Java, C++, etc., and also including conventional procedural programming languages such as the "C" language or similar programming languages. The program code can be executed entirely on the user's computing device, partially on the user's device, executed as a stand-alone 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 the case of a remote computing device, the remote computing device can be connected to the user's computing device through 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., by connecting through the Internet using an Internet service provider).

[0131] In addition, the above-mentioned drawings are only schematic illustrations of the processes included in the method according to the exemplary embodiments of the present invention, rather than for limiting purposes. It is easy to understand that the processes shown in the above-mentioned drawings do not indicate or limit the chronological order of these processes. Additionally, it is also easy to understand that these processes can be executed, for example, synchronously or asynchronously in multiple modules.

[0132] Those skilled in the art will readily conceive of other embodiments of the present disclosure after considering the specification and practicing the invention disclosed herein. This application is intended to cover any variations, uses, or adaptations of the present disclosure that follow the general principles of the present disclosure and include known common general knowledge or conventional technical means in the technical field not disclosed in the present disclosure. The specification and embodiments are only regarded as exemplary, and the true scope and concept of the present disclosure are pointed out by the claims.

Claims

1. A method for managing user location information, characterized in that, Applied to the narrowband Internet of Things satellite scenario, including: The mobility management entity stores the user location information from the user equipment as the first user location information, and the first user location information includes 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 the second user location information, and the second user location information includes a second identifier; The mobility management entity determines the second user location information according to the second identifier, and uses the second user location information to execute a network process, and the network process includes location verification.

2. The management method of user location information according to claim 1, characterized in that The mobility management entity storing the user location information from the user equipment as the first user location information includes: The mobility management entity adds the first identifier to the user location information sent by the user equipment through 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 group of UL NAS transport messages.

3. The management method of user location information according to claim 1, wherein The mobility management entity storing the user location information of the user equipment reported by the radio access network to which the user equipment is connected as the second user location information includes: 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 management method of user location information according to claim 1, characterized in that, The mobility management entity storing the user location information from the user equipment as the first user location information includes: 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 management method of user location information according to claim 1, characterized in that, The mobility management entity storing the user location information of the user equipment reported by the radio access network to which the user equipment is connected as the second user location information includes: 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 management method of user location information according to claim 1, characterized in that, The mobility management entity storing the user location information of the user equipment reported by the radio access network to which the user equipment is connected as the second user location information includes: The mobility management entity obtains the rough location information of the user equipment; 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 a location report, where the location report control information is used to indicate that the rough location information does not meet the accuracy requirement of location verification.

7. The management method of user location information according to claim 6, characterized in that, The location report control information includes the identification information of the user equipment and the first user location information.

8. The management method of user location information according to claim 6, wherein The mobility management entity sending the location report control information to the radio access network includes: After the mobility management entity sends the location report control information to the radio access network, it starts a timer, and the timer corresponds to a preset duration; Before the running duration of the timer reaches the preset duration, the mobility management entity waits to receive the location report from the radio access network; When the running duration of the timer reaches the preset duration, the mobility management entity receives a failure of the location report.

9. The management method of user location information according to claim 1, characterized in that, Both the first user location information and the second user location information include the tracking area identity and the cell global identification code of the user equipment.

10. A method for managing user location information, characterized in that, Applied to the narrowband Internet of Things satellite scenario, it includes: The user equipment sends user location information including a first identifier to the mobility management entity.

11. The method for managing user location information according to claim 10, wherein, The user equipment sending user location information including a first identifier to the mobility management entity includes: The user equipment adds the first identifier to the user location information in the initial UE message. The user equipment adds the first identifier to the user location information in the first group of UL NAS transport messages.

12. The management method of user location information according to claim 10, characterized in that, The user equipment sending user location information including a first identifier to the mobility management entity includes: The first user location information includes the tracking area identity and the cell global identification code of the user equipment, and the user equipment adds the first identifier to the tracking area identity and / or the cell global identification code.

13. A method for managing user location information, characterized in that, Applied to the narrowband Internet of Things satellite scenario, it includes: The radio access network sends user location information including a second identifier to the mobility management entity.

14. The management method of user location information according to claim 13, wherein The radio access network sending user location information including a second identifier to the mobility management entity includes: The radio access network receives location report control information from the mobility management entity, and the location report information includes the identifier information of the user equipment and the rough location information of the user equipment. The radio access network obtains the user location information of the user equipment according to 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, and the location report includes the user location information of the user equipment and the second identifier.

15. The method for managing user location information according to claim 14, wherein The radio access network obtaining the user location information of the user equipment according to the location report control information includes: The radio access network identifies the rough location information to determine the user location information of the user equipment.

16. A communication device, characterized in that, It includes: A memory; And A processor coupled to the memory, the processor being configured to execute the method according to any one of claims 1-15 based on instructions stored in the memory.

17. A computer-readable storage medium, on which a program is stored, and when the program is executed by a processor, it implements the method according to any one of claims 1-15.

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

Images