Location management method and apparatus

Abstract

Provided in the embodiments of the present application are a location management method and apparatus. The method comprises: a first core network device acquiring a terminal identity of a first terminal device, and determining, on the basis of the terminal identity, to execute location management on the first terminal device; determining an area identity set for executing the location management; and sending the area identity set to the first terminal device. In the solution, after acquiring a terminal identity of a first terminal device, a first core network device sends to the first terminal device an area identity set for executing location management only when the first core network device determines to execute location management on the first terminal device, and thus a core network can execute location management on a terminal device on the basis of requirements instead of blindly executing location management on all terminals, such that network overheads can be reduced, and the efficiency of location management can be improved.

Description

Location management method and device

[0001] CROSS-REFERENCE TO RELATED APPLICATIONS

[0002] This application claims priority to the Chinese patent application filed with the State Intellectual Property Office of China on July 31, 2023, with application number 202310952525.4 and application name “A Location Management Method and Device”, the entire contents of which are incorporated by reference into this application. Technical Field

[0003] The present application relates to the field of communication technology, and in particular to a location management method and device. Background Art

[0004] Currently, mobile networks can use tracking areas (TAs) to manage the location of terminal devices. Mobile networks are divided into multiple TAs, and multiple geographically close cells can be assigned to the same TA. Different TAs are distinguished by different tracking area identities (TAIs). After a terminal device registers with the network, the network device responsible for mobility management will determine a registration area (RA) for the terminal device based on the radio access network devices it is connected to and the TAs within its management scope. The RA can include one or more TAs and can be expressed as a TAI list. The TAI list is sent to the terminal device, which then stores the TAI list. If the TAI detected by the terminal device in a cell broadcast message is included in the TAI list, it indicates that the terminal device has moved within the registration area and does not need to update its location to the network. If the TAI detected by the terminal device in the cell broadcast message is not in the TAI list, it indicates that the terminal device has moved out of the registration area. The terminal device can initiate a tracking area update process or a mobility registration update process to notify the network device responsible for mobility management that it has left the registration area, allowing the network device responsible for mobility management to configure a new registration area for the terminal device.

[0005] In IoT technologies, such as passive IoT (P-IoT) or ambient IoT (A-IoT), terminal devices can be active, passive, or semi-passive. Passive or semi-passive terminal devices lack the ability to actively communicate and require network stimulation to communicate. Therefore, not all IoT terminals support the aforementioned location management methods.

[0006] How to manage the location of terminal devices in the Internet of Things is an urgent problem that needs to be solved.

[0007] Summary of the Invention

[0008] The embodiments of the present application provide a location management method and apparatus for performing location management on terminal devices in the Internet of Things, which can reduce network overhead and improve location management efficiency.

[0009] In a first aspect, a location management method is provided, which can be applied to a first core network device or a chip in the first core network device. Taking the application of the method to the first core network device as an example, the method includes: the first core network device obtains a terminal identifier of a first terminal device, and determines to perform location management on the first terminal device based on the terminal identifier; determines a set of area identifiers for performing location management; and sends the set of area identifiers to the first terminal device.

[0010] In the above scheme, after receiving the terminal identification of the first terminal device, the first core network device needs to determine whether to perform location management on the first terminal device. When it is determined to perform location management on the first terminal device, it sends information for performing location management (such as an area identification set) to the first terminal device. This can enable the core network to perform location management on terminal devices according to demand, rather than blindly performing location management on all terminals. It can reduce network overhead (such as context maintenance costs) and improve location management efficiency.

[0011] In one possible design, the first core network device can obtain the contract data of the first terminal device from the second core network device based on the terminal identifier, the contract data includes at least one of the first information, the second information or the capability information of the terminal device, the first information indicates that the first terminal device needs to be location managed, the second information indicates that the first service requester needs location management, the first service requester is the service requester that manages the first terminal device, and the capability information of the first terminal device indicates that the first terminal device supports location management; determine to execute location management on the first terminal device based on the contract data.

[0012] In this way, the first core network device can determine to perform location management on the first terminal device based on the contract data.

[0013] In one possible design, a first core network device may receive a first message, the first message including a terminal identifier of the first terminal device and capability information of the first terminal device, wherein the capability information of the first terminal device indicates that the first terminal device supports location management. Accordingly, the first core network device may obtain the contract data of the first terminal device from the second core network device based on the terminal identifier, wherein the contract data includes first information and / or second information, wherein the first information indicates that location management needs to be performed on the first terminal device, and the second information indicates that location management needs to be performed on the first service requester, which is the service requester that manages the first terminal device. The first service requester determines to perform location management on the first terminal device based on the contract data and the capability information of the first terminal device.

[0014] In this way, the first core network device can determine to perform location management on the first terminal device based on the subscription data and the capability information reported by the first terminal device.

[0015] In one possible design, the first core network device can receive a first message, which includes a terminal identifier of the first terminal device and capability information of the first terminal device, and the capability information of the first terminal device indicates that the first terminal device supports location management; and determines to perform location management on the first terminal device based on the terminal identifier and the capability information of the first terminal device.

[0016] In this way, the first core network device can determine to perform location management on the first terminal device based on the subscription data and the capability information reported by the first terminal device.

[0017] In one possible design, the first message may be a first registration request message; the first core network device may send a first registration acceptance message to the first terminal device, the first registration acceptance message indicating that the first terminal device is successfully registered, and the first registration acceptance message includes an area identifier set, and the area indicated by the area identifier set is the registration area allocated by the first core network device to the first terminal device.

[0018] In this way, it is possible to determine whether to perform location management on the first terminal device during the registration process of the first terminal device, and to send a set of area identifiers for location management to the first terminal device without sending additional separate messages, thereby saving system resources.

[0019] In one possible design, before the first core network device determines to perform location management on the first terminal device based on the terminal identifier, it can also obtain the local configuration information of the first core network device; wherein the local configuration information of the first core network device includes at least one item of a terminal device list, a service requester list, and the capability information of the first terminal device, the terminal device list indicates the terminal devices for which location management needs to be performed, the terminal device list includes the terminal identifier of the first terminal device, the service requester list indicates the service requester that needs location management, the service requester list includes the identifier of the first service requester, the first service requester is the service requester that manages the first terminal device, and the capability information of the first terminal device indicates that the first terminal device supports location management. Accordingly, the first core network device can determine to perform location management on the first terminal device based on the terminal identifier and the local configuration information of the first core network device.

[0020] In this way, the first core network device can determine to perform location management on the first terminal device according to the local configuration.

[0021] In one possible design, before the first core network device determines to perform location management on the first terminal device based on the terminal identifier, it may also receive a second message from the first service requester, where the second message includes first information and / or second information, the first information indicating that location management needs to be performed on the first terminal device, and the second information indicating that the first service requester requests location management, where the first service requester is the service requester that manages the first terminal device. Accordingly, the first core network device may determine to perform location management on the first terminal device based on the terminal identifier, the first information, and / or the second information.

[0022] In this way, the first core network device can perform location management on the first terminal device according to the instructions of the first service requester.

[0023] In one possible design, second location information may also be obtained, where the second location information indicates an area where location management is performed. The first core network device may receive a terminal identifier of the first terminal device from the first access network device. The first core network device may also determine the first location information based on the location information of the first access network device, where the first location information indicates an area where the first terminal device is located; and determine that the first terminal device is located in an area where location management is performed based on the first location information and the second location information.

[0024] It is understood that the second location information may be sent by the first service requester, or sent by other core network devices (such as the second core network device), or pre-configured in the first core network device. The embodiment of the present application does not limit the source of the second location information. It is understood that when the first service requester sends the second location information to the first core network device, the second location information may be carried in the second message described above, or in other messages. The embodiment of the present application does not limit this.

[0025] In this way, it can be achieved that location management is performed on the first terminal device only when the first terminal device is located in an area where location management is performed.

[0026] In one possible design, the first core network device may further obtain a preset route of the first terminal device. Accordingly, the first core network device may determine a set of region identifiers for performing location management based on the area covering part or all of the preset route, where the set of region identifiers includes region identifiers of the area covering part or all of the preset route.

[0027] It is understandable that the preset line may be sent by the first service requester, or sent by other core network devices (such as the second core network device), or pre-configured in the first core network device. The embodiment of the present application does not limit the source of the preset line. It is understandable that when the first service requester sends the preset line to the first core network device, the preset line may be carried in the second message described above, or in other messages. The embodiment of the present application does not limit this. In a specific example, the second location information includes the preset line or the second location information is the preset line.

[0028] In the Internet of Things scenario, the service requester usually requires the terminal device to move along a preset route. Therefore, the first core network device determines the area identifier set for performing location management based on the preset route (or the area corresponding to the preset route). This can realize location management of the terminal device on the preset route (or the area corresponding to the preset route), improve the efficiency of location management, and save power consumption.

[0029] In one possible design, the first core network device can also receive the terminal identification of the first terminal device from the second access network device; determine the area where the first terminal device is located based on the location information of the second access network device; if the area where the first terminal device is located does not belong to the area of ​​the preset route, it is determined that the first terminal device has deviated from the preset route; and send third information to the first service requester, the third information indicating that the location of the first terminal device is abnormal, and the first service requester is the service requester who manages the first terminal device.

[0030] In this way, when the first terminal device deviates from the preset route, the first core network device can notify the first service requester, so that the first service requester can promptly discover the route error of the first terminal device and reduce the transportation cost caused by the route error.

[0031] In one possible design, the first time information can also be obtained, and the first time information indicates the time period for performing location management; the first core network device can determine to perform location management on the first terminal device based on the terminal identifier when the current time is within the time period indicated by the first time information.

[0032] It is understood that the first time information may be sent by the first service requester, or sent by other core network devices (such as the second core network device), or pre-configured in the first core network device. The embodiment of the present application does not limit the source of the first time information. It is understood that when the first service requester sends the first time information to the first core network device, the first time information may be carried in the second message described above, or in other messages. The embodiment of the present application does not limit this.

[0033] In this way, location management can be performed on the first terminal device only during the time period when location management is required, which can improve the effectiveness of location management and save power consumption.

[0034] In one possible design, the first core network device can also obtain the location information and second time information of the target location, where the second time information indicates the time when the first terminal device arrives at the target location; determine whether the first terminal device arrives at the target location within the time indicated by the second time information; if the first terminal device does not arrive at the target location within the time indicated by the second time information, send fourth information to the first service requester, and the fourth information indicates that the location of the first terminal device is abnormal. The first service requester is the service requester who manages the first terminal device.

[0035] It is understandable that the location information and the second time information of the target location may be sent by the first service requester, or sent by other core network devices (such as the second core network device), or pre-configured in the first core network device. The embodiment of the present application does not limit the source of the location information and the second time information of the target location. It is understandable that when the first service requester sends the location information and the second time information of the target location to the first core network device, the location information and the second time information of the target location may be carried in the second message described above, or may be carried in other messages. The embodiment of the present application does not limit this.

[0036] The following are several implementation methods for determining whether the first terminal device arrives at the target location within the time indicated by the second time information:

[0037] Method 1: Within the time indicated by the second time information, a paging message is sent to one or more access network devices, where the paging message indicates that paging is to be performed on the first terminal device, and the paging message includes the terminal identifier of the first terminal device; the terminal identifier of the first terminal device is received from a third access network device, and it is determined that the first terminal device is located in an area corresponding to the location information of the third access network device; based on the location information of the third access network device and the location information of the target location, it is determined whether the first terminal device has arrived at the target location within the time indicated by the second time information.

[0038] Method 2: Within the time indicated by the second time information, a paging message is sent to one or more access network devices corresponding to the target location, where the paging message indicates that paging is to be performed on the first terminal device, and the paging message includes the terminal identification of the first terminal device; based on whether the terminal identification of the first terminal device is received from any one of the one or more access network devices corresponding to the target location, it is determined whether the first terminal device has arrived at the target location within the time indicated by the second time information.

[0039] Method 3: The set of area identifiers does not include an area identifier for an area covering the target location. The terminal identifier of the first terminal device is received from a third access network device; the area where the first terminal device is located is determined to be an area covering the target location based on the location information of the third access network device; and the first terminal device is determined, based on the current time and the second time information, to have arrived at the target location within the time indicated by the second time information.

[0040] It can be understood that the above methods are only examples and are not limited thereto.

[0041] In this way, the first service requester can promptly learn that the first terminal device has not arrived at the designated location at the designated time and / or discover that the first terminal device has taken an incorrect route, thereby reducing transportation costs caused by the error.

[0042] In one possible design, the first core network device can also obtain third time information, which indicates a preset duration; determine that the first terminal device has been in the same location for more than a preset duration; and send fifth information to the first service requester, which indicates that the location of the first terminal device is abnormal, and the first service requester is the service requester who manages the first terminal device.

[0043] It is understood that the third time information may be sent by the first service requester, or sent by other core network devices (such as the second core network device), or pre-configured in the first core network device. The embodiment of the present application does not limit the source of the third time information. It is understood that when the first service requester sends the third time information to the first core network device, the third time information may be carried in the second message described above, or in other messages. The embodiment of the present application does not limit this.

[0044] The following are several implementation methods for determining that the first terminal device has been in the same location for more than a preset period of time:

[0045] Method 1: Send a paging message to one or more access network devices, where the paging message is used to perform paging on the first terminal device. The paging message includes the terminal identification of the first terminal device. If the duration of receiving the terminal identification of the first terminal device from the same access network device for multiple consecutive times exceeds a preset duration, it is determined that the first terminal device has been in the same location for more than the preset duration.

[0046] Method 2: Periodically send paging information to one or more access network devices according to a preset duration. The paging information is used to perform paging on the first terminal device. The paging information includes the terminal identification of the first terminal device. If the terminal identification of the first terminal device is received multiple times from the same access network device, it is determined that the first terminal device has been in the same location for more than the preset duration.

[0047] Method 3: The area identifier set includes the area identifier of the area covering part of the preset route; if the terminal identifier of the first terminal device is not received from any access network device outside the area represented by the area identifier set for more than a preset time, it is determined that the first terminal device is in the same location for more than the preset time.

[0048] It can be understood that the above methods are only examples and are not limited thereto.

[0049] In this way, the first service requester can promptly discover that the first terminal device has been at the same location for more than a preset time, so that the first service requester can promptly check whether the first terminal device has fallen during movement or whether the transportation vehicle for transporting the first terminal device is faulty.

[0050] In one possible design, the second message is a service subscription request message, which instructs the first core network device to provide location management services for the first terminal device or the terminal device managed by the first service requester.

[0051] In this way, location management can be taken as a service, and the first terminal device or the terminal device managed by the first service requester can be subscribed to the location management service on demand, thereby improving the effectiveness of location management.

[0052] In one possible design, the first core network device may further send billing information corresponding to location management to the third core network device;

[0053] The billing information includes at least one of the following:

[0054] Event type information, indicating the event corresponding to location management;

[0055] The number of regional identifiers for which location management is performed;

[0056] the duration of performing location management;

[0057] The number of times location management was performed;

[0058] The number of terminal devices for which location management is performed.

[0059] In this way, when location management is used as a service, the first core network device can send billing information corresponding to the location management to the third core network device, so that the third core network device can count the fees and realize paid use of location management.

[0060] In one possible design, the first core network device can also receive a third message from the first service requester, and the third message indicates to stop performing location management on the first terminal device; based on the third message, the sixth information and / or seventh information is sent to the first terminal device, the sixth information indicates that the first terminal device removes the area identification set, and the seventh information indicates that the first terminal device does not need to update the location of the first terminal device to the network.

[0061] In this way, the first core network device can stop performing location management on the first terminal device in a timely manner according to the needs of the service requester, thereby saving system resources.

[0062] In one possible design, the first core network device can also receive a second registration request message from the second terminal device, where the second registration request message includes a terminal identifier of the second terminal device; determine not to perform location management on the second terminal device based on the terminal identifier of the second terminal device; and send a second registration acceptance message to the second terminal device, where the second registration acceptance message indicates that the second terminal device has been successfully registered, and the area identifier in the second registration acceptance message is empty or is a default area identifier.

[0063] In this way, location management can be avoided for the second terminal device by not configuring an area identifier for the second terminal device or by configuring a default area identifier for the second terminal device, which can further reduce network overhead (such as context maintenance cost) and improve location management efficiency.

[0064] According to a second aspect, a location management method is provided, which can be applied to a first core network device or a chip in the first core network device. Taking the application of the method to the first core network device as an example, the method includes: the first core network device receives a second registration request message from a second terminal device, and the second registration request message includes a terminal identifier of the second terminal device; determines not to perform location management on the second terminal device based on the terminal identifier of the second terminal device; and sends a second registration acceptance message to the second terminal device, the second registration acceptance message indicates that the second terminal device has been successfully registered, and the area identifier in the second registration acceptance message is empty or is a default area identifier.

[0065] In this way, location management can be avoided for the second terminal device by not configuring an area identifier for the second terminal device or by configuring a default area identifier for the second terminal device. The core network can perform location management on the terminal device according to demand instead of blindly performing location management on all terminals. This can reduce network overhead (such as context maintenance costs) and improve location management efficiency.

[0066] On the third aspect, a location management method is provided, which can be applied to a first service requester or a chip in the first service requester. Taking the application of the method to a first core network device as an example, the method includes: determining a second message, the second message includes first information and / or second information, the first information indicates that the first terminal device needs to be location managed, the second information indicates that the first service requester requests location management, and the first service requester is the service requester that manages the first terminal device; sending the second message to the first core network device.

[0067] In one possible design, the second message further includes one or more of the following:

[0068] second location information, the second location information indicating an area where location management is performed;

[0069] a preset route of the first terminal device;

[0070] first time information, the first time information indicating a time period for performing location management;

[0071] Location information of the target location and second time information, where the second time information indicates the time when the first terminal device arrives at the target location;

[0072] The third time information indicates a preset duration.

[0073] In one possible design, the first service requester may further receive third information, fourth information, or fifth information from the first core network device, where the third information, fourth information, or fifth information indicates that the location of the first terminal device is abnormal; or

[0074] In one possible design, the second message is a service subscription request message, which instructs the first core network device to provide location management services for the first terminal device or the terminal device managed by the first service requester.

[0075] In one possible design, the first service request direction sends a third message to the first core network device, and the third message instructs to stop performing location management on the first terminal device.

[0076] In a fourth aspect, a location management method is provided, which can be applied to a second terminal device or a chip in the second terminal device. Taking the application of the method to the second terminal device as an example, the method includes: sending a second registration request message to the first core network device, the second registration request message including the terminal identifier of the second terminal device; receiving a second registration acceptance message from the first core network device, the second registration acceptance message indicating that the second terminal device is successfully registered, and the area identifier in the second registration acceptance message is empty or is a default area identifier; based on the locally stored area identifier being empty or being the default area identifier, determining that there is no need to monitor the area identifier in the cell broadcast message or there is no need to execute the mobility registration update process.

[0077] In a fifth aspect, a communication device is provided, which includes a module or unit or technical means for executing the method described in the first aspect or any possible design of the first aspect.

[0078] Exemplarily, the device may include:

[0079] A transceiver module, configured to obtain a terminal identification of a first terminal device;

[0080] A processing module, configured to determine, based on the terminal identifier, that location management is to be performed on the first terminal device; and to determine a set of area identifiers for performing location management;

[0081] The transceiver module is further configured to send the area identifier set to the first terminal device.

[0082] In a sixth aspect, a communication device is provided, which includes a module, unit or technical means for executing the method described in the second aspect or any possible design of the second aspect.

[0083] Exemplarily, the device may include:

[0084] a transceiver module, configured to receive a second registration request message from a second terminal device, where the second registration request message includes a terminal identifier of the second terminal device;

[0085] A processing module, configured to determine not to perform location management on the second terminal device according to the terminal identification of the second terminal device;

[0086] The transceiver module is further configured to send a second registration acceptance message to the second terminal device, where the second registration acceptance message indicates that the second terminal device has successfully registered, and the area identifier in the second registration acceptance message is empty or a default area identifier.

[0087] In a seventh aspect, a communication device is provided, which includes a module, unit or technical means for executing the method described in the third aspect or any possible design of the third aspect.

[0088] Exemplarily, the device may include:

[0089] a processing module, configured to determine a second message, where the second message includes first information and / or second information, the first information indicating that location management needs to be performed on the first terminal device, and the second information indicating that the first service requester requests location management, where the first service requester is a service requester that manages the first terminal device;

[0090] The transceiver module is used to send a second message to the first core network device.

[0091] In an eighth aspect, a communication device is provided, which includes a module, unit or technical means for executing the method described in any possible design method of the fourth aspect or the fourth+ aspect.

[0092] Exemplarily, the device may include:

[0093] a transceiver module, configured to send a second registration request message to the first core network device, the second registration request message including a terminal identifier of the second terminal device; and receive a second registration acceptance message from the first core network device, the second registration acceptance message indicating that the second terminal device has been successfully registered, and the area identifier in the second registration acceptance message being empty or a default area identifier;

[0094] The processing module is used to determine that there is no need to monitor the area identifier in the cell broadcast message or to execute the mobility registration update process according to the locally stored area identifier being empty or being a default area identifier.

[0095] In the ninth aspect, a communication device is provided, which includes a processor, and the processor is configured to execute the method described in the first aspect or any possible design of the first aspect or the second aspect or any possible design of the second aspect or the third aspect or any possible design of the third aspect or the fourth aspect or any possible design of the fourth aspect.

[0096] In the tenth aspect, a computer-readable storage medium is provided, which includes instructions. When the instructions are executed by a processor, the method described in the first aspect or any possible design of the first aspect or the second aspect or any possible design of the second aspect or the third aspect or any possible design of the third aspect or the fourth aspect or any possible design of the fourth aspect is implemented.

[0097] In the eleventh aspect, a computer program product is provided, which includes instructions, which, when executed by a processor, enable the method described in the first aspect or any possible design of the first aspect or the second aspect or any possible design of the second aspect or the third aspect or any possible design of the third aspect or the fourth aspect or any possible design of the fourth aspect to be implemented.

[0098] In the twelfth aspect, an embodiment of the present application provides a communication system, which includes a first core network device for implementing the function of the first aspect and a first service requester for implementing the function of the third aspect; or, the communication system includes a first core network device for implementing the function of the second aspect and a second terminal device for implementing the function of the fourth aspect.

[0099] The beneficial effects of each design in the above-mentioned second aspect to the twelfth aspect can refer to the description of the beneficial effects of the corresponding designs in the first aspect to the second aspect. BRIEF DESCRIPTION OF THE DRAWINGS

[0100] FIG1 is an architecture diagram of a communication system provided in an embodiment of the present application;

[0101] FIG2 is a schematic diagram of the registration process of a terminal device;

[0102] Figures 3A and 3B are schematic diagrams of the business architecture of the passive Internet of Things;

[0103] FIG4 is a flow chart of a location management method provided in an embodiment of the present application;

[0104] FIG5A is a schematic diagram of the coverage of a first access network device;

[0105] FIG5B is a schematic diagram of a preset route;

[0106] FIG5C is a schematic diagram of the actual movement trajectory of the first terminal device;

[0107] FIG6 is a flow chart of a location management method provided in an embodiment of the present application;

[0108] FIG7 is a flowchart of another location management method provided in an embodiment of the present application;

[0109] FIG8 is a flowchart of another location management method provided in an embodiment of the present application;

[0110] FIG9 is a flowchart of another location management method provided in an embodiment of the present application;

[0111] FIG10 is a schematic structural diagram of a communication device provided in an embodiment of the present application;

[0112] FIG11 is a schematic structural diagram of another communication device provided in an embodiment of the present application;

[0113] FIG12 is a schematic structural diagram of another communication device provided in an embodiment of the present application. DETAILED DESCRIPTION

[0114] In order to make the purpose, technical solutions and advantages of the embodiments of the present application clearer, the embodiments of the present application will be further described in detail below with reference to the accompanying drawings.

[0115] The network architecture and business scenarios described in this application are intended to more clearly illustrate the technical solutions of the embodiments of this application, and do not constitute a limitation on the technical solutions provided by the embodiments of this application. Ordinary technicians in this field will know that with the evolution of network architecture and the emergence of new business scenarios, the technical solutions provided by the embodiments of this application are also applicable to similar technical problems.

[0116] In the embodiments of the present application, "multiple" may refer to two or more. In view of this, in the embodiments of the present application, "multiple" may also be understood as "at least two". "At least one" may be understood as one or more, for example, one, two or more. For example, "including at least one" means including one, two or more. For example, including at least one of A, B and C, then included may be A, B, C, A and B, A and C, B and C, or A, B and C. "And / or" describes the association relationship of associated objects. Specifically, there may be three relationships. For example, A and / or B may represent: A exists alone, A and B exist at the same time, and B exists alone. In addition, the character " / ", unless otherwise specified, generally indicates that the previous and subsequent associated objects are in an "or" relationship.

[0117] In addition, the terms "system" and "network" in the embodiments of the present application may be used interchangeably, and "according to" and "based on" may be used interchangeably.

[0118] In the embodiments of this application, ordinal numbers such as "first," "second," and "third" are generally used to distinguish different objects and are not used to define the order, sequence, priority, or importance of multiple objects. For example, in the embodiments of this application, "first information" and "second information" are used to distinguish two pieces of information and do not define the priority or importance of the two pieces of information.

[0119] The embodiments of the present application will be presented around a system including multiple devices, components, modules, etc. It should be understood that the system may include other devices, components, modules, etc. not mentioned, or may only include some of the devices, components, or modules, etc. mentioned in the embodiments.

[0120] The following first introduces a communication system to which the embodiments of the present application are applicable.

[0121] The embodiments of the present application are applicable to communication systems of various standards, such as: long term evolution (LTE) communication systems, 5G communication systems, 6G communication systems and future communication systems, vehicle to everything (V2X), long term evolution-vehicle network (LTE-vehicle, LTE-V), vehicle to vehicle (V2V), vehicle network, machine type communications (MTC), IoT, long term evolution-machine to machine (LTE-machine to machine, LTE-M), machine to machine (M2M), Internet of Things, etc.

[0122] Figure 1 is an architectural diagram of a communication system provided in an embodiment of the present application, illustrating a fifth-generation (5G) network architecture based on a service-oriented architecture. The 5G network architecture shown in Figure 1 may include terminal devices, access network (AN) devices, and core network (CN) devices. Terminal devices access the data network (DN) through the access network devices and core network devices. The components of the communication system are described below.

[0123] Terminal devices include devices that provide voice and / or data connectivity to users. For example, a terminal device is a device with wireless transceiver capabilities that can be deployed on land, including indoors or outdoors, handheld, wearable, or vehicle-mounted; it can also be deployed on the water (such as ships, etc.); it can also be deployed in the air (such as airplanes, balloons, and satellites, etc.). The terminal device can be a tag, a mobile phone, a tablet computer, a computer with wireless transceiver capabilities, a virtual reality (VR) terminal, an augmented reality (AR) terminal, a wireless terminal in industrial control, a vehicle-mounted terminal, a wireless terminal in self-driving, a wireless terminal in remote medical care, a wireless terminal in a smart grid, a wireless terminal in transportation safety, a wireless terminal in a smart city, a wireless terminal in a smart home, a wearable terminal, etc. The embodiments of the present application do not limit the application scenarios.

[0124] Terminal equipment may sometimes also be referred to as terminal, user equipment (UE), access terminal, vehicle-mounted terminal, industrial control terminal, UE unit, UE station, mobile station, mobile station, remote station, remote terminal, mobile device, UE terminal, wireless communication equipment, UE agent or UE device, etc. The terminal may also be fixed or mobile. It will be understood that all or part of the functions of the terminal in this application may also be implemented by software functions running on hardware, or by virtualization functions instantiated on a platform (such as a cloud platform). The terminal device in this application may be a terminal for 5G or a terminal for 6G, and this application does not limit this.

[0125] In passive IoT scenarios, terminal devices can also serve as tags, and terminal devices are sometimes also called tags.

[0126] Access network equipment is a device that provides wireless communication capabilities for terminal devices. Examples of access network equipment include, but are not limited to, the next-generation base station (g NodeB, gNB) in 5G, evolved NodeB (eNB), radio network controller (RNC), NodeB (NB), base station controller (BSC), base transceiver station (BTS), home base station (e.g., home evolved NodeB, or home nodeB, HNB), baseband unit (BBU), transmitting and receiving point (TRP), transmitting point (TP), mobile switching center, etc.

[0127] In some deployments, a gNB may include a centralized unit (CU) and a distributed unit (DU). The gNB may also include an active antenna unit (AAU). The CU may implement some gNB functions, while the DU may implement other gNB functions. For example, the CU is responsible for processing non-real-time protocols and services, implementing the functions of the radio resource control (RRC) and packet data convergence protocol (PDCP) layers. The DU is responsible for processing physical layer protocols and real-time services, implementing the functions of the radio link control (RLC), media access control (MAC), and physical (PHY) layers. The AAU implements some physical layer processing functions, RF processing, and active antenna-related functions. RRC layer information is generated by the CU and ultimately encapsulated by the DU's PHY layer into PHY layer information, or is converted from PHY layer information. Therefore, in this architecture, higher-layer signaling, such as RRC layer signaling, can also be considered to be sent by the DU, or by a combination of the DU and the AAU. It can be understood that the access network device may include one or more of a CU node, a DU node, and an AAU node. In addition, the CU can be divided into an access network device in the access network, and the CU can be divided into an access network device in the CN. The access network device can be a radio access network (RAN) device or a wired access network (FAN) device. Among them, the RAN device can be a RAN device for 5G, a RAN device for 6G, or other names, and this application does not limit this.

[0128] Access network equipment and terminal devices can be fixed or mobile. They can be deployed on land, including indoors or outdoors, handheld or vehicle-mounted; on water; or in the air on aircraft, balloons, and satellites. The embodiments of this application do not limit the application scenarios of access network equipment and terminal devices.

[0129] The core network equipment includes some or all of the following network elements: unified data management (UDM) network element, unified data repository (UDR) network element, network exposure function (NEF) network element (not shown in the figure), policy control function (PCF) network element, access and mobility management function (AMF) network element, session management function (SMF) network element, user plane function (UPF) network element, Internet of Things management function (IoTMF) network element, etc.

[0130] The mobility management network element is a control plane network element provided by the operator network, responsible for access control and mobility management of terminal devices accessing the operator network, such as mobile state management, allocation of user temporary identity, authentication and authorization of users, etc. In 5G, the mobility management network element can be an AMF network element. In future communications such as the 6th generation (6G), the mobility management network element can still be an AMF network element or have other names, which are not limited in this application.

[0131] The data management network element is a control plane network element provided by the operator, which is responsible for storing the subscriber permanent identifier (SUPI), credentials, security context, contract data, service configuration information, etc. of the subscribers in the operator's network. The contract data may include the contract data of the terminal device (or user), and may also include the contract data of the service requester (such as the service requester who manages the terminal device, specifically, for example, a server, application function, third party, enterprise or user). In 5G, the data management network element may be a UDM network element. In future communications such as 6G, the data management network element may still be a UDM network element, or have other names, which are not limited in this application.

[0132] The session management network element is a control plane network element provided by the operator network, responsible for managing the protocol data unit (PDU) session of the terminal device. In 5G, the session management network element can be an SMF network element. In future communications such as 6G, the session management network element can still be an SMF network element or have other names, which are not limited in this application.

[0133] The user plane network element is a gateway provided by the operator and is the gateway for communication between the operator network and the DN. In 5G, the user plane network element can be a UPF network element. In future communications such as 6G, the user plane network element can still be a UPF network element or have other names, which are not limited in this application.

[0134] The unified database network element is a control plane network element provided by the operator, which includes the access function of executing contract data, policy data, application data, and other types of data. In 5G, the unified database network element can be a UDR network element. In future communications such as 6G, the unified database network element can still be a UDR network element or have other names, which are not limited in this application.

[0135] A network open element is a control plane element provided by an operator. It opens the operator's network interface to third parties in a secure manner. In 5G, a network open element may be a NEF element. In future communications such as 6G, the network open element may still be a NEF element or have other names, which are not limited in this application.

[0136] The policy control network element (PCNE) is a control plane function provided by the operator, used to provide PDU session policies to the session management network element. Policies may include charging-related policies, QoS-related policies, and authorization-related policies. In 5G, the policy control network element may be a PCF network element. In future communications such as 6G, the policy control network element may still be a PCF network element or have other names, which are not limited in this application.

[0137] The location management function (LMF) network element can be used to determine the location of the UE, obtain downlink location measurement or location estimation from the UE, etc. For example, in 5G, the location management function network element can be an LMF network element. In future communication systems, such as 6G, the location management function network element can still be an LMF network element or have other names, which are not limited in this application.

[0138] The Internet of Things functional network element is a control plane network element or a network element with a user plane data transmission function. This function can be connected to the access network device, which is equivalent to the access network device having an interface with the function; or the function can communicate with the access network device through a mobile management device (such as AMF). This function can be used to perform functions such as management of Internet of Things terminals (or called ambient energy acquisition Internet of Things terminals Ambient IoT), Internet of Things terminal data processing, and Internet of Things terminal data routing. It can parse messages or instructions from the service requester (or application function), determine the reader (such as access network equipment or terminal equipment with reader function) to execute instructions or operations based on the message or instruction, instruct the reader to execute the Internet of Things terminal operation or instruct the reader to execute the random access process of the Internet of Things terminal; receive data from the Internet of Things terminal through the reader, optionally perform data processing of the Internet of Things terminal, and send the data of the Internet of Things terminal to the service requester. It can be understood that in the specific implementation, the function can also have other names, which is not limited in this application. This function can be an independent network element, or it can be combined with other network elements in the core network.

[0139] The 5G network architecture shown in Figure 1 also includes application function (AF) network elements. AF network elements are used to convey the requirements of the application side to the network side, such as QoS requirements or user status event subscriptions. The application function network element can be a third-party functional entity or an application server deployed by the operator. In 5G, the application function network element can be an AF network element. In future communications such as 6G, the application function network element can still be an AF network element or have other names, which are not limited in this application.

[0140] In some embodiments, the 5G network architecture shown in Figure 1 may include a service requester (or an operation requester or a third party), and the specific implementation form may be a server or an application function (such as AF), etc. In the embodiment of the present application, the service requester may be understood as an operation requester. The service requester or the operation requester may be understood as a device that sends an operation instruction, such as a service requester or an operation requester may be a server (server) or an A-IoT server or an AF network element or other device that sends an operation instruction. The operation requester may correspond to a certain type of user, and such user may include an enterprise, a tenant, a third party or a company, without restriction. Among them, the service requester corresponding to a certain type of user may be understood as the service requester belonging to such user and being managed by such user.

[0141] The data network is a network outside the operator network. The operator network can access multiple DNs, and various services can be deployed on the DNs to provide data and / or voice services to terminal devices.

[0142] In Figure 1, Npcf, Nudr, Nudm, Naf, Namf, and Nsmf are the service-oriented interfaces provided by the PCF, UDR, UDM, AF, AMF, and SMF, respectively, and are used to invoke corresponding service-oriented operations. The N1 interface is the interface between the AMF and the terminal device and can be used to transmit non-access-stratum (NAS) signaling (such as QoS rules from the AMF) to the terminal device. The N2 interface is the interface between the AMF and the RAN and can be used to transmit radio bearer control information from the core network to the RAN. The N3 interface is the interface between the RAN and the UPF and is primarily used to transmit uplink and downlink user plane data between the RAN and the UPF. The N4 interface is the interface between the SMF and the UPF and can be used to transmit information between the control plane and the user plane, including the issuance of forwarding rules, QoS control rules, traffic statistics rules, etc. for the user plane, as well as the reporting of user plane information. The N6 interface is the interface between the UPF and the DN and is used to transmit uplink and downlink user data flows between the UPF and the DN.

[0143] In order to enable the core network to efficiently paging specific terminals within a small range, during the UE registration process, the AMF can send the Registration Area (RA) to the UE in the Registration Accept message. The registration area can be a Tracking Area Identifier (TAI) list. When the UE moves within the registration area, it does not need to update its location to the network. When the UE moves from the registration area to a location outside the registration area (for example, when the UE monitors that the TAI broadcast by the base station does not belong to any TAI in the TAI list), the UE needs to initiate a mobility registration update process, that is, the UE sends a Registration Request message, where the Registration Type included in the Registration Request message is Mobility Registration Update. The AMF will resend a new registration area (that is, a new TAI list) to the UE based on some configurations or policies. Through this process, even if the terminal is in idle state (that is, the terminal has no connection with the core network), it can notify the core network when it moves out of the registration area, so that the core network can perform mobility management on the terminal. Its advantage is that the core network can always manage the mobility of the terminal at the registration area granularity. When downlink data needs to be sent to the terminal, the core network can prioritize paging the UE from the current registration area to improve efficiency.

[0144] See Figure 2, which shows an example of a registration process for a terminal device. The specific steps are as follows:

[0145] S201. The UE sends a registration request message to the RAN, which carries the registration type and UE identification information;

[0146] S202: RAN selects a suitable AMF.

[0147] S203. RAN sends a registration request message to AMF.

[0148] Optionally, in 204, AMF selects an appropriate network device responsible for mobility management (authentication server function, AUSF) to perform security processes such as authentication; UE, AMF, AUSF, and UDM interact to complete security processes such as authentication.

[0149] Optionally, 205: After the UE and the network successfully authenticate each other, the AMF interacts with the UDM to obtain the UE's subscription data.

[0150] S206. The AMF sends an N2 message to the RAN. The N2 message includes a non-access stratum (NAS) message that the RAN needs to forward to the UE. The NAS message includes a registration accept message sent by the AMF to the UE. The registration accept message includes the registration area (RA), such as the TAI list.

[0151] S207. RAN forwards the NAS message sent by AMF to UE (the NAS message includes a registration accept message).

[0152] During the registration process for each terminal device, the AMF sends a registration acceptance message to the RAN containing the TAI list. In other words, all successfully registered terminal devices will be configured with the TAI list, meaning that location management will be performed on them.

[0153] In the passive IoT (P-IoT) or ambient energy harvesting IoT (A-IoT) technology, IoT terminals are included, such as active terminal devices, passive terminal devices, semi-passive terminal devices, and semi-active terminal devices. The IoT terminals can be in the form of tags, sensors, etc., and this application does not limit the form of terminal devices. Access network equipment (such as base stations) can be used as readers (or readers), application function network elements can be used as servers, and core network equipment can execute processes related to IoT services (such as IoT terminal management), such as access management, security authentication, command transmission, business data transmission, and other functions.

[0154] It is understood that the embodiments of this application do not limit the device form or name of the IoT terminal. For ease of description, the embodiments of this application use the IoT terminal in the form of a tag as an example. In the embodiments of this application, unless otherwise specified, the passive IoT can be interchanged with the ambient energy harvesting IoT, the ambient energy enabling IoT, the IoT, etc.

[0155] 3A and 3B are schematic diagrams of the service architecture of the passive Internet of Things. In FIG3A , an enhanced access management device (such as an AMF network element) is used to execute processes related to the Internet of Things service.

[0156] Figure 3B shows new functions such as tag management function (TMF), IoT management function (IMF), IoT terminal management function, ambient IoT terminal management function (AITMF), ambient IoT function (AIoTF), ambient energy enabled IoT terminal management function, ambient energy enabled IoT management function and other network elements to execute IoT business-related processes. This function can be connected to the access network device, which is equivalent to the access network device having an interface with the function; or the function can communicate with the access network device through a mobile management device (such as AMF). This function can be used to perform IoT terminal (or ambient energy acquired IoT terminal Ambient IoT) management, IoT terminal data processing, IoT terminal data routing and other functions. It can parse the message or instruction from the service requester (or application function), determine the reader (such as access network equipment or terminal equipment with reader function) that executes the instruction or operation according to the message or instruction, instruct the reader to perform the IoT terminal operation or instruct the reader to perform the random access process of the IoT terminal; receive data from the IoT terminal through the reader, optionally perform data processing of the IoT terminal, and send the IoT terminal data to the service requester. It can be understood that in the specific implementation, this function can also have other names, which are not limited in this application. This function can be an independent network element, or it can be combined with other network elements in the core network. For example, the TMF network element can be combined with the AMF network element. In one possible implementation, when this function is combined with other network elements in the core network, the interaction between this function and other network elements is an internal operation of the network element or can be omitted.

[0157] When a server performs an operation on a tag, it may send an operation instruction to the core network. The operation instruction may include, but is not limited to, obtaining tag information, performing an inventory operation (also known as an inventory operation), a read operation, a write operation, an invalidation operation, and exchanging information with the tag. The instruction may include regional location information, tag identification information, and so on. The base station sends an access instruction to the tag. When the tag successfully performs random access, the base station sends an instruction to the tag (the base station may forward the instruction sent by the core network to the tag). The tag obtains or sends the corresponding information based on the instruction. For example, when the instruction is an inventory instruction or an inventory operation, the tag sends the tag identification information; when the instruction is a read instruction or a read operation, the tag sends the data information stored in the tag storage area; when the instruction is a write instruction or a write operation, the tag stores the data information to be written to the tag included in the instruction in the tag storage area. The base station sends (or forwards) the information sent by the tag to the core network; and the core network sends this information to the server.

[0158] However, terminal devices in passive IoT (referred to as IoT terminals) are typically low-power and low-complexity. Passive or semi-passive terminals require network stimulation to initiate communication and cannot proactively initiate communication. Furthermore, after a power outage, purely passive terminals cannot record status information (such as registration status or registration area) and are not connected. Therefore, the mobility management mechanism shown in Figure 2 is not applicable to IoT terminals.

[0159] In view of this, for passive Internet of Things scenarios (or environmental energy acquisition Internet of Things scenarios), how to design location management (or mobility management) that is more suitable for passive Internet of Things (or environmental energy acquisition Internet of Things) is the problem to be solved by this application.

[0160] It can be understood that the embodiment of the present application takes the passive Internet of Things scenario as an example, but is not actually limited to application in this scenario. It can be applied to scenarios such as environmental energy acquisition Internet of Things, environmental energy enabled Internet of Things, Internet of Things, etc., or as long as the scenario requires mobility management (or location management), this application is applicable.

[0161] 4 is a flow chart of a location management method provided in an embodiment of the present application, the method comprising:

[0162] S401. A first core network device obtains a terminal identifier of a first terminal device;

[0163] Exemplarily, the first terminal device sends the terminal identification of the first terminal device, and the first core network device receives the terminal identification of the first terminal device.

[0164] Among them, the first core network device can be a core network device responsible for terminal device location management, for example, it can be the AMF shown in Figure 3A, or the new function shown in Figure 3B (such as TMF, AITMF, AIoTF), or other core network devices responsible for terminal device location management (such as LMF, NEF, PCF, SMF, etc.), which is not limited in this application.

[0165] The first terminal device can send the terminal identification of the first terminal device to the first core network device through the access network device (specifically, for example, the first access network device). For example, the first terminal device sends the terminal identification of the first terminal device to the first access network device. After the first access network device receives the terminal identification of the first terminal device, it sends the terminal identification of the first terminal device to the first core network device.

[0166] In some embodiments, the identification information of the first terminal device sent by the first terminal device to the first core network device through the first access network device can be carried in a non-access stratum (NAS) message. In other words, the first access network device directly forwards the NAS message to the first core network device. Exemplarily, the first terminal device carries the non-access stratum message in an access network (AN) message and sends it to the first access network device. The first access network device extracts the NAS message from the AN message, encapsulates the NAS message through a next generation application protocol (NGAP) message (or N2 message) and sends it to the AMF.

[0167] In other embodiments, the terminal identifier of the first terminal device sent by the first terminal device to the first access network device and the terminal identifier of the first terminal device sent by the first access network device to the first core network device can be carried in different messages. For example, when the first core network device is an AMF, the terminal identifier of the first terminal device sent by the first terminal device to the first access network device is carried in an air interface message, and the terminal identifier of the first terminal device sent by the first access network device to the first core network device is carried in an N2 message. In other words, after receiving the air interface message, the first access network device does not directly forward it to the first core network device, but processes it into an N2 message before sending it to the first core network device.

[0168] In some embodiments, the first terminal device may send an encrypted terminal identifier of the first terminal device, and accordingly, the first core network device receives the encrypted terminal identifier of the first terminal device, and the first core network device obtains the terminal identifier of the first terminal device based on the encrypted terminal identifier of the first terminal device. For example, after the first core network device receives the encrypted terminal identifier of the first terminal device, it sends the encrypted terminal identifier of the first terminal device to the UDM or UDR, and the UDM or UDR decrypts the encrypted terminal identifier of the first terminal device and sends it to the first core network device, and the first core network device receives the terminal identifier of the first terminal device from the UDM or UDR.

[0169] In an embodiment of the present application, the first terminal device may be a terminal identifier that reports the first terminal device to the first core network device during an initial registration process, a mobility registration update process, a wake-up process, or a service request process. The terminal identifier of the first terminal device may be carried in a message (such as a first message). It is understood that the type of the first message may be different in different processes. Taking the mobility registration update process as an example, after successful random access, the first terminal device may send a first registration request message to the first core network device through the first access network device (i.e., the first message is a first registration request message), and the first registration request message includes the terminal identifier of the first terminal device. It should be understood that the first access network device may forward the first registration request message received from the first terminal device to the first core network device; or the message received by the first access network device from the first terminal device and the message sent by the first access network device to the first core network device may be different. For example, the first access network device may receive the first registration request message from the first terminal device through an AN message, and encapsulate the first registration request message into an N2 message (i.e., the N2 message contains the first registration request message) before sending it to the first core network device.

[0170] S402. The first core network device determines to perform location management on the first terminal device according to the terminal identifier of the first terminal device;

[0171] In the embodiments of the present application, location management is only an example of a name and can be replaced by other names in actual applications. For example, it can also be called mobility management, positioning management, positioning service, location tracking service or other names. This application does not impose any restrictions.

[0172] Specifically, the first core network device determines whether to perform location management on the first terminal device according to the terminal identification of the first terminal device, and executes S403 to S404 when it is determined to perform location management on the first terminal device.

[0173] In one possible design, the first core network device may determine to perform location management on the first terminal device based on one or more of the following:

[0174] 1. The first terminal device needs to be location managed.

[0175] The need for location management to be performed on the first terminal device means that the first core network device needs to perform location management on the first terminal device. For ease of description, in this document, the need for location management to be performed on the first terminal device can also be replaced by the description that the first terminal device needs location management, or that location management needs to be performed on the first terminal device, etc.

[0176] Specifically, the first core network device can determine that the first terminal device needs to be location managed based on the first information and / or the second information, the first information indicates that the first terminal device needs to be location managed, and the second information indicates that the first service requester needs location management. In one possible implementation, the first terminal device belongs to the first service requester, or the first terminal device is a terminal device managed by the first service requester, or the first service requester manages the first terminal device. In another possible implementation, the first service requester is the service requester of the first terminal device, or the first service requester is the service requester that manages the first terminal device. The specific form of the first service requester can refer to the above description of the service requester, for example, the first service requester is the functional entity corresponding to the Internet of Things service (such as TMF or AITMF), or is the server of the enterprise that manages the first terminal device (the specific form is, for example, AF).

[0177] In one possible implementation, when the first terminal device belongs to a terminal device group created by the first service requester, the first terminal device belongs to the first service requester, or the first terminal device is a terminal device managed by the first service requester, or the first service requester manages the first terminal device. For example, when the first service requester creates a terminal device group by dynamic creation or configuration, and the terminal device group includes the first terminal device, the first terminal device belongs to the first service requester, or the first terminal device is a terminal device managed by the first service requester, or the first service requester manages the first terminal device.

[0178] In another possible implementation, when the contract data of the first terminal device includes information representing the first service requester, such as one or more of the identifier of the first service requester, the slice information corresponding to the first service requester, the data network name corresponding to the first service requester, and the service identifier corresponding to the first service requester, the first terminal device belongs to the first service requester, or the first terminal device is a terminal device managed by the first service requester, or the first service requester manages the first terminal device.

[0179] In another possible implementation, when the contract data or service configuration information (such as service profile) corresponding to the first service requester includes information characterizing the first terminal device, such as the terminal identifier of the first terminal device (such as SUPI, SUCI, GPSI, IP address, MAC address, etc.), the group identifier corresponding to the first terminal device, etc., the first terminal device belongs to the first service requester, or the first terminal device is a terminal device managed by the first service requester, or the first service requester manages the first terminal device.

[0180] The first service requester requires location management, which may mean that the first core network device needs to perform location management on the terminal device managed by the first service requester, or the first service requester requests that location management be performed on the terminal device managed by the first service requester. For ease of description, the term "require location management" in this document may also be replaced by "request to perform location management" or "subscribe to location management," etc.

[0181] In one possible design, the first information is indication information and / or the second information is indication information.

[0182] Exemplarily, the first information indicates that location management needs to be performed or that the terminal device needs to be location managed. The first core network device can determine that location management needs to be performed on the first terminal device based on the terminal identifier of the first terminal device and the first information. Alternatively, the first information indicates that location management needs to be performed on the first terminal device. In one possible implementation, when the subscription data of the first terminal device includes the first information, the first information can indicate that location management needs to be performed on the first terminal device.

[0183] Exemplarily, the second information indicates that location management is required, or the second information indicates that the first service requester requires location management, or the second information indicates that location management needs to be performed on the terminal device managed by the first service requester. The first terminal device is one of at least one terminal device managed by the first service requester. In one possible implementation, when the contract data or service configuration information (such as a service profile) corresponding to the first service requester includes the second information, the second information may indicate that the first service requester requires location management, or that location management needs to be performed on the terminal device managed by the first service requester.

[0184] In another possible design, the first information is the terminal identification of the first terminal device in the terminal device list (or called the terminal device identification list) and / or the second information is the identification of the first service requester in the service requester list (or called the service requester identification list). The terminal device list indicates one or more terminal devices that need to be location managed, for example, the terminal device list includes the terminal identifications of one or more terminal devices that need to be location managed, and the terminal identification of the first terminal device in the terminal device list indicates that the first terminal device needs to be location managed. The service requester list indicates the identifications of one or more service requesters that need location management, for example, the service requester list includes the identifications of one or more service requesters that need location management, and the service requester list includes the identification of the first service requester, indicating that the first service requester needs location management (or the terminal device managed by the first service requester needs to be location managed). In one possible implementation, the terminal device list may include the terminal identifications of one or more terminal devices; the service requester list may include the identifications of one or more service requesters.

[0185] In another possible design, the first information is a terminal device list (or a terminal device identification list) and / or the second information is a service requester list (or a service requester identification list). The terminal device list indicates one or more terminal devices that need to be location managed, for example, the terminal device list includes one or more terminal identifications of terminal devices that need to be location managed; when the terminal device list includes the terminal identification of the first terminal device, it can indicate that the first terminal device needs to be location managed. The service requester list indicates one or more identifications of service requesters that need location management, for example, the service requester list includes one or more identifications of service requesters that need location management, when the service requester list includes the identification of the first service requester, it can indicate that the first service requester needs location management (or that the terminal device managed by the first service requester needs to be location managed).

[0186] It is understandable that before the first terminal device determines that the first terminal device needs to be location managed based on the first information and / or the second information, it needs to first obtain the first information and / or the second information. The first information and / or the second information may be sent by the first service requester, or sent by other core network devices (such as the second core network device), or pre-configured in the first core network device. The embodiment of the present application does not limit the source of the first information and / or the second information.

[0187] In a specific implementation manner, the first core network device obtains the first information and / or the second information from the subscription data or service configuration information of the first terminal device.

[0188] Take contract data as an example:

[0189] Exemplarily, the contract data is contract data at the terminal device granularity, that is, the contract data includes contract data of the first terminal device, and the contract data of the first terminal device includes first information, which is an indication information indicating that location management needs to be performed or the terminal device needs to be location managed or the first terminal device needs to be location managed. The first core network device can determine that location management needs to be performed on the first terminal device based on the first information.

[0190] Exemplarily, the contract data is contract data at the granularity of the service requester, that is, the contract data includes the contract data of the first service requester. The contract data of the first service requester includes second information, where the second information is indication information indicating that location management is required, or indicating that the first service requester requires location management; or the contract data of the first service requester includes a terminal identifier or a terminal device list of a terminal device, where the terminal identifier or terminal device list includes a terminal identifier of a terminal device managed by the first service requester for which location management is required, and the second information is identification information of the terminal device or the terminal device list.

[0191] It can be understood that since the first terminal device is a terminal device managed by the first service requester, the first terminal device is subject to the contract data of the first service requester. Therefore, in some embodiments, the contract data of the first service requester can be used as the contract data of the first terminal device.

[0192] Exemplarily, the contract data includes both contract data at the terminal device granularity and contract data at the service requester granularity. For example, the contract data includes contract data of a first terminal device and contract data of a first service requester. The contract data of the first terminal device includes first information, which is indication information indicating that location management needs to be performed on the first terminal device. The contract data of the first service requester includes second information, which is indication information indicating that location management needs to be performed on the first service requester. The first core network device determines to perform location management on the first terminal device (or determines that location management needs to be performed on the first terminal device) based on the first information and the second information.

[0193] Exemplarily, the contract data includes a terminal device list, and the terminal device list may include terminal identifications of one or more terminal devices. The terminal device list may represent one or more terminal devices for which location management needs to be performed. For example, the terminal device list includes terminal identifications of one or more terminal devices for which location management needs to be performed, the first information is the terminal device list or the first information is the terminal identification of the first terminal device in the terminal list, the first core network device may obtain the terminal identification of the first terminal device by querying or obtaining the terminal device list, or the first core network device may determine that the terminal identification of the first terminal device is included in the terminal list by querying or obtaining the terminal device list, and thus may determine that the first terminal device needs to be location managed.

[0194] Exemplarily, the contract data includes a service requester list, the service requester list includes one or more identifiers of service requesters that require location management, the second information is the service requester list or the second information is the identifier of the first service requester in the service requester list, the first core network device can obtain the identifier of the first service requester by querying or obtaining the service requester list, or the first core network device learns through querying or obtaining that the identifier of the first service requester is included in the service requester list, thereby determining that the first service requester requires location management. Specifically, the first core network device determines that the first terminal device managed by the first service requester needs to be location managed.

[0195] Exemplarily, the contract data includes a terminal device list and a service requester list. The first information is the terminal identifier of the first terminal device in the terminal device list, and the second information is the identifier of the first service requester in the service requester list. The first core network device can determine that the first terminal device needs to be location managed and the first service requester needs location management by querying the terminal device list and the service requester list.

[0196] Exemplarily, the contract data includes a terminal device list and a service requester list, the terminal device list indicates the terminal devices managed by the first service requester, for example, the terminal device list includes the terminal identification of one or more terminal devices managed by the first service requester, and the service requester list indicates the service requester that requires location management, for example, the service requester list includes the identification of one or more service requesters that require location management. The first information is a terminal device list (for example, the terminal identification of one or more terminal devices), and the terminal device list includes the terminal identification of the first terminal device. The second information is a service requester list (for example, the identification of one or more service requesters), and the service requester list includes the identification of the first service requester. The first core network device determines that the first service requester needs to perform location management based on the second information. The first core network device determines that the terminal devices managed by the first service requester include the first terminal device based on the first information. The first core network device determines to perform location management on the first terminal device (or determines that the first terminal device needs to be subjected to location management) based on the first information and the second information.

[0197] It can be understood that when the contract data includes the first information and / or the second information, the first core network device needs to obtain the contract data. In some embodiments, the first core network device can obtain the contract data from other core network devices such as the second core network device, wherein the second core network device can be a network device that stores the contract data of the contracted user in the operator network, such as UDM or UDR, etc., which is not limited in this application. Optionally, after the first core network device obtains the contract data from the second core network device, it can store part or all of the contract data locally, and then the first core network device can also directly read the contract data locally.

[0198] In one implementation, the first core network device obtains the first information and / or the second information from locally configured (or stored) information. In a specific implementation, the first core network device is configured with the first information and / or the second information. In another specific implementation, the first core network device locally stores context information (e.g., UE context), and the context information includes the first information and / or the second information.

[0199] It can be understood that in the embodiments of the present application, local configuration can be replaced with local storage, configuration or pre-configured description.

[0200] Exemplarily, the first core network device is locally configured (or stored) with a terminal device list, and the terminal device list may include terminal identifications of one or more terminal devices. The terminal device list may represent one or more terminal devices that need to be location managed. For example, the terminal device list includes the terminal identifications of one or more terminal devices that need to be location managed, the first information is the terminal device list or the first information is the terminal identification of the first terminal device in the terminal list, the first core network device may obtain the terminal identification of the first terminal device by querying the terminal device list, or the first core network device may obtain the terminal identification of the first terminal device by querying the terminal device list, or the first core network device may obtain the terminal identification of the first terminal device by querying the terminal device list.

[0201] The terminal device list is queried or obtained to determine whether the terminal identifier of the first terminal device is included in the terminal list, thereby determining that location management needs to be performed on the first terminal device.

[0202] Exemplarily, the first core network device is locally configured (or stored) with a service requester list, the service requester list includes one or more identifiers of service requesters that require location management, the second information is the service requester list or the second information is the identifier of the first service requester in the service requester list, the first core network device can obtain the identifier of the first service requester by querying or obtaining the service requester list, or the first core network device learns through querying or obtaining that the identifier of the first service requester is included in the service requester list, and then determines that the first service requester requires location management. Specifically, the first core network device determines that the first terminal device managed by the first service requester needs to be location managed.

[0203] Exemplarily, the first core network device is locally configured (or stored) with a terminal device list and a service requester list, the first information is the terminal identifier of the first terminal device in the terminal device list, and the second information is the identifier of the first service requester in the service requester list. The first core network device can determine that the first terminal device needs to be location managed and the first service requester needs location management by querying the terminal device list and the service requester list.

[0204] Exemplarily, the first core network device is locally configured (or stored) with a terminal device list and a service requester list, the terminal device list indicates the terminal devices managed by the first service requester, for example, the terminal device list includes the terminal identifiers of one or more terminal devices managed by the first service requester, and the service requester list indicates the service requesters that require location management, for example, the service requester list includes the identifiers of one or more service requesters that require location management. The first information is a terminal device list (for example, the terminal identifiers of one or more terminal devices), and the terminal device list includes the terminal identifier of the first terminal device. The second information is a service requester list (for example, the identifiers of one or more service requesters), and the service requester list includes the identifier of the first service requester. The first core network device determines that the first service requester needs to perform location management based on the second information. The first core network device determines that the terminal devices managed by the first service requester include the first terminal device based on the first information. The first core network device determines to perform location management on the first terminal device (or determines that the first terminal device needs to be subjected to location management) based on the first information and the second information.

[0205] In specific implementation, the locally configured (or stored) information can be configured (or stored) locally in advance by technical personnel, configured in the first core network device through network management, or configured (or stored) locally after the first core network device receives it from other devices (such as UDM or UDR or AF, etc.). This application does not impose any restrictions.

[0206] In one implementation, the first core network device obtains the first information and / or the second information from the first service requester (eg, AF), or the first core network device receives the first information and / or the second information from the first service requester.

[0207] In some embodiments, the first service requester may directly send the first information and / or the second information to the first core network. For example, the first service requester sends a second message to the first core network, and the second message includes the first information and / or the second information.

[0208] For example, the location management described in this document can be used as a service, such as a location management service (it can be understood that the location management service is only an example of a name, and there can actually be other names, such as mobility management service, etc., which are not limited in this application). The first service requester can send a service subscription request message (or called a subscription request message or a service request message, etc.) to the first core network. The service subscription request message is used to subscribe to the location management service (or to request the location management service). The service subscription request message (for example, the second message can be a service subscription request message) may include first information and / or second information; the first information indicates that the first terminal device needs to be location managed, or indicates that the first terminal device is subscribed to the location management service. The first information is specifically, for example, an indication information, or a terminal identifier of the first terminal device; the second information indicates that the first service requester needs location management, or indicates that the first service requester is subscribed to the location management service. The second information is specifically, for example, an indication information, or an identifier of the service requester.

[0209] In other embodiments, the first service requester may send the first information and / or the second information to the first core network device through other devices.

[0210] For example, the first service requester sends the first information and / or the second information to the second core network device (such as a network element such as NEF, UDM or UDR), and the second core network device updates the contract data (such as the contract data of the first terminal device and / or the contract data of the first service requester) based on the first information and / or the second information sent by the first service requester, and the second core network device sends the updated contract data to the first core network device, so that the first core network device can obtain the first information and / or the second information. In one possible implementation, the first service requester sends the first information and / or the second information to the second core network device through other core network devices. For example, the first service requester (such as AF) can send the first information and / or the second information to the UDR (or UDM) through the NEF. Optionally, before the second core network device sends the updated contract data to the first core network device, the first core network device also subscribes to notifications of contract data changes from the second core network device, so that the second core network device sends the updated contract data to the first core network device when the contract data is updated. For example, the first core network device sends a contract data subscription request message to the second core network device, and the second core network device sends the updated contract data to the first core network device when the contract data is updated according to the contract data subscription request message.

[0211] It can be understood that when the first information or the second information is located in different devices, it can be the same or different information forms. For example, when the second core network device updates the contract data based on the first information and / or second information sent by the first service requester, it can directly save the first information and / or the second information to the contract data, or it can convert the first information and / or the second information into another form and save it to the contract data. This application does not impose any restrictions.

[0212] In some other embodiments, the first core network device may determine the first information and / or the second information based on the information sent by the first service requester. For example, the information sent by the first service requester is different from the first information and / or the second information, but the information sent by the first service requester may indicate that the first terminal device needs to be location managed and / or the first service requester needs location management. For example, the first service requester sends a service subscription request message, which does not contain either the first information or the second information, but the message itself indicates a subscription to a location management service. The first core network device may determine the first information and / or the second information based on the service subscription request message.

[0213] The above introduces the manner in which the first core network obtains the first information and / or the second information. It should be noted that the manner in which the first core network device obtains the first information may be the same as or different from the manner in which the second information is obtained. Exemplarily, the first core network device may obtain the first information through contract data, and obtain the second information through a message from the first service requester. In addition, when the manner in which the first core network device obtains the first information is the same as the manner in which the second information is obtained, the first information and the second information may be carried in the same message or in different messages, respectively, and this is not limited in the embodiments of the present application.

[0214] In one possible implementation, the terminal identifier of the first terminal device may have a variety of different forms. Exemplarily, the terminal identifier sent by the first terminal device in the above step S401 (i.e., the terminal identifier received by the first core network from the first terminal device) may be the same as or different from the terminal identifier used by the first core network device to determine the execution of location management for the first terminal device. For example, the terminal identifier sent by the first terminal device may be an encrypted terminal identifier, and the first core network device obtains an unencrypted (for example, decrypted) terminal identifier based on the encrypted terminal identifier. The first core network device determines to execute location management for the first terminal device based on the unencrypted terminal identifier.

[0215] 2. The first terminal device supports location management.

[0216] It can be understood that the first terminal device supports location management, which means that the first terminal device supports the first core network device to perform location management on it.

[0217] Exemplarily, the first terminal device supports location management, which can be understood as the first terminal device supports initiating an access process (such as a tracking area update process (TAU) or a mobility registration update process) based on the acquired area identifier set. Specifically, when the area identifier included in the broadcast message monitored by the first terminal device does not belong to any area identifier in the area identifier set acquired by the first terminal device, the first terminal device initiates a tracking area update process or a mobility registration update process. In one possible implementation, the area identifier set includes one or more area identifiers.

[0218] In one implementation, the first core network device determines that the first terminal device supports location management based on capability information of the first terminal device, and the capability information of the first terminal device indicates that the first terminal device supports location management.

[0219] It is understandable that before the first core network device determines that the first terminal device supports location management based on the capability information of the first terminal device, it needs to first obtain the capability information of the first terminal device. The capability information of the first terminal device may be sent by the first terminal device, or sent by the first service requester, or sent by other core network devices (such as the second core network device), or pre-configured in the first core network device. The embodiment of the present application does not limit the source of the capability information of the first terminal device.

[0220] In some embodiments, the first terminal device may report the capability information of the first terminal device. For example, the first terminal device sends the capability information of the first terminal device to the first core network device; or, the first terminal device sends the capability information of the first terminal device to the first access network device, and the first access network device sends the capability information of the first terminal device to the first core network device. The first terminal device may send the capability information of the first terminal device together with the terminal identification of the first terminal device, or the first terminal device may send the terminal identification of the first terminal device and the capability information of the first terminal device separately at different times, which is not limited in this application. The first core network device receives the capability information from the first terminal device.

[0221] For example, the first terminal device sends a NAS message (such as a first registration request message) to the first core network device through the first access network device, and the NAS message (such as the first registration request message) carries the terminal identification of the first terminal device and the capability information of the first terminal device.

[0222] For another example, the first terminal device sends an RRC message to the first access network device, and the RRC message includes the capability information of the first terminal device; the first access network device sends an NGAP message to the first core network device, and the NGAP message includes the capability information of the first terminal device.

[0223] In some other embodiments, the terminal identification of the first terminal device may indicate the capability of the first terminal device, for example, the capability information of the first terminal device may be included in the terminal identification of the first terminal. Exemplarily, some fields of the terminal identification of the first terminal device may indicate the capability of the first terminal device. The field may be one or more of a string, a number, or a bit. For example, some fields of the terminal identification may indicate whether the terminal device supports location management, and the field has different values ​​when the terminal device supports and does not support location management; or, for example, when the first terminal device supports location management, the terminal identification of the first terminal device may include a field indicating support for location management, and when the first terminal device does not support location management, the terminal identification of the first terminal device does not include a field indicating support for location management. The first core network device may know that the first terminal device supports location management based on the terminal identification (for example, the terminal identification of the first terminal device).

[0224] In other embodiments, the contract data (e.g., the contract data of the first terminal device and / or the contract data of the first service requester) includes capability information of the first terminal device, and the first core network device can determine the capability information of the first terminal device from the contract data. The manner in which the first core network device obtains the contract data can be referred to the relevant description above and will not be repeated here.

[0225] In some other embodiments, the first core network device locally configures (or stores) the capability information of the first terminal device, and the first core network device reads the capability information of the first terminal device locally. Optionally, the capability information of the first terminal device may be configured (or stored) locally in advance by a technician, or configured through a network management system, or sent to the first core network device by other devices (such as the first terminal device, UDM, UDR, or AF, etc.), and then the first core network device configures (or stores) it locally. This application does not impose any restrictions.

[0226] In another implementation, the first core network device determines that the first terminal device is of the first type based on the type information of the first terminal device, and the type information of the first terminal device indicates that the first terminal device is of the first type.

[0227] Different types of terminal devices have different capabilities, and the capability information of the first terminal device (i.e., whether it supports location management) can be determined through the type information of the first terminal device. For example, the type information of the terminal device may include active terminal devices, passive terminal devices, semi-passive terminal devices, etc., wherein passive terminal devices or semi-passive terminal devices do not have the ability to actively communicate, and the passive terminal cannot record status information after power failure. Therefore, passive terminal devices and semi-passive terminal devices do not support location management in terms of capabilities, while active terminal devices have the ability to actively communicate, can record status information after power failure, and support location management in terms of capabilities. Therefore, the first type may be an active terminal device. Of course, this is only an example, and the type information of the actual terminal device is not limited to this, and the first type is not limited to active terminal devices.

[0228] Before the first core network device determines that the first terminal device is of the first type based on the type information of the first terminal device, the first core network device needs to first obtain the type information of the first terminal device. The specific implementation method for the first core network device to obtain the type information of the first terminal device can refer to the specific implementation method for the first core network device to obtain the capability information of the first terminal device.

[0229] 3. The first terminal device is located in an area where location management is performed.

[0230] The first terminal device is located in an area where location management is performed, which can also be described as the first terminal device is located in an area where location management needs to be performed, or the first terminal device is located in an area where location management needs to be performed, or the first terminal device is located in an area where location management needs to be performed on the terminal device, and so on.

[0231] In one possible implementation, a first core network device obtains first location information. The first core network device determines, based on the first location information, that the first terminal device is located in an area requiring location management. The first location information indicates the area where the first terminal device is located, or the first location information is an area identifier of the area where the first terminal device is located.

[0232] In some embodiments, the first core network device may determine the first location information based on the access network device (such as the first access network device) where the first terminal device is located. For example, the first core network device obtains the location information of at least one access network device (including the first core network device). The first terminal device sends the terminal identifier of the first terminal device to the first core network device through the first access network device (such as a first registration request message, the first registration request message includes the terminal identifier of the first terminal device), and the first core network device receives the terminal identifier of the first terminal device sent by the first terminal device through the first access network device. The first core network device determines the first location information based on the location information of the first access network device (such as a cell identifier, a tracking area identifier corresponding to the first access network device, a first access network device identifier, etc.). Exemplarily, after the first core network device receives the terminal identifier of the first terminal device from the first access network device, it determines that the first terminal device is located in the location corresponding to the first access network device, and determines the location information of the first access network device as the first location information.

[0233] In a specific implementation, the first location information may be one or more of an access network device identifier (e.g., a gNB identifier, a Global RAN node ID, etc.), a cell identifier, a geographic location identifier (e.g., coordinate values, longitude and latitude, etc.), a TAI, a closed access group (CAG) identifier, a reader (or reader) identifier, a user equipment identifier (e.g., a generic public subscription identifier (GPSI), a subscription concealed identifier (SUCI), or a subscriber permanent ID (SUPI), etc.). In one possible implementation, the user equipment identifier may be an identifier of a terminal device serving as a reader (e.g., GPSI, SUCI, or SUPI, etc.).

[0234] In one implementation, a first core network device obtains first location information and second location information. The first core network device determines, based on the first location information and the second location information, that the first terminal device is located in an area requiring location management, where the first location information indicates the area where the first terminal device is located, and the second location information indicates the area requiring location management.

[0235] It can be understood that before the first terminal device determines that the first terminal device is located in the area where location management is performed based on the first location information and the second location information, it needs to first obtain the first location information and the second location information. Among them, the method for obtaining the first location information can refer to the above. The second location information may be sent by the first service requester, or by other core network devices (such as sent by the second core network device), or pre-configured in the first core network device. The embodiment of the present application does not limit the source of the second location information.

[0236] In some embodiments, the second location information includes at least one of the following, or the second location information is determined based on at least one of the following: location information locally configured by the first core network device, or location information specified in the protocol, or location information in the contract data, or location information provided by the first service requester. This application does not impose any restrictions.

[0237] Among them, the location information locally configured by the first core network device may include the location information of the area where location management is performed and / or the location information of the area where location management is not performed. The location information specified in the protocol may include the location information of the area where location management is performed and / or the location information of the area where location management is not performed. The location information provided by the first service requester may include the location information of the area where location management is performed and / or the location information of the area where location management is not performed. The location information in the contract data may include the location information of the area where location management is performed and / or the location information of the area where location management is not performed. Optionally, the location information provided by the first service requester may also include the location information of the area where the operation instruction is executed. Optionally, the location information in the contract data may also include the location information of the area where the operation instruction is executed.

[0238] In one example, a first service requester sends a service request message to a first core network device. The service request message carries instructions and location information (i.e., the location information provided by the first service requester). The types of instructions include, but are not limited to, one or more of inventory, read, write, deactivate, and locate. The location information indicates the area where the instructions need to be executed. The location information locally configured by the first core network device or the location information in the subscription data (i.e., the second location information) includes a first type of area and a second type of area. The first type of area can represent an area where location management does not need to be performed (e.g., a non-public network area or an indoor area), and the second type of area can represent an area where location management needs to be performed (e.g., a public network area or an outdoor area). When the area indicated by the location information provided by the first service requester (e.g., an identifier of an area located on the first public network) (i.e., the area where the instructions are executed) is the second type of area and the first terminal device is in the area where the instructions are executed, location management needs to be performed on the first terminal device. When the area indicated by the location information provided by the first service requester (i.e., the area where the instructions are executed) is the first type of area and the first terminal device is in the area where the instructions are executed, location management does not need to be performed on the first terminal device.

[0239] Exemplarily, the area where location management is performed may be one or more of one or more public land mobile network (PLMN) areas, one or more specific PLMN areas, one or more non-public network (NPN) areas, one or more specific NPN areas, one or more geographic location areas (e.g., specified coordinates, longitude and latitude), areas corresponding to one or more tracking areas, areas corresponding to one or more cells, areas corresponding to one or more closed access groups (CAGs), areas corresponding to one or more readers / writers, areas corresponding to one or more access network devices, areas corresponding to one or more user devices, and the like. In one possible implementation, the area corresponding to one or more cells may be understood as the area covered by one or more cells; the area corresponding to one or more closed groups may be understood as the area corresponding to the access network devices that broadcast the one or more closed groups; the area corresponding to one or more readers / writers may be understood as the area covered by one or more readers / writers; the area corresponding to one or more access network devices may be understood as the area covered by one or more access network devices; the user device may be understood as a user device that can function as a reader (or reader / writer); and the area corresponding to one or more user devices may be understood as the area covered by one or more user devices.

[0240] Correspondingly, the second location information can be one or more of a PLMN identifier, a geographic location identifier (such as coordinate values, longitude and latitude, etc.), a TAI, a cell identifier (such as a cell ID), a CAG identifier, a reader identifier, an access network device identifier (such as a RAN identifier, a gNodeB identifier, etc.), a user equipment identifier (such as GPSI, SUCI, SUPI, etc.), etc.

[0241] As an example, a non-public network (NPN), also known as a campus network, local area network, or private network, is typically a small campus network with limited mobility for terminal devices. Therefore, location management can be omitted to reduce network overhead. A PLMN, also known as a public network, has a larger range, so location management can be performed for terminal devices within the public network. It should be understood that the above examples are only examples and are not limited to these.

[0242] Optionally, the second location information is a preset route (it will be understood that the preset route is only an example of a name, and can also be called a preset line, line information, route information, expected trajectory, trajectory information, etc., without limitation), and the preset route is the route that the first terminal device expects, requires or instructs the first service requester to move.

[0243] In one possible implementation, the preset route may include one or more area identifiers, and the area indicated by the one or more area identifiers corresponds to the movement route of the first terminal device. The one or more area identifiers may specifically include: one or more of: one or more PLMN identifiers, one or more TAIs, one or more cell identifiers (e.g., cell IDs), one or more CAG identifiers, one or more reader identifiers, one or more access network device identifiers (e.g., RAN identifiers, gNodeB identifiers, etc.), one or more user equipment identifiers (e.g., GPSI, SUCI, SUPI, etc.), etc.

[0244] In another possible implementation, the preset route may include one or more geographic location information (e.g., coordinate values ​​or longitude and latitude). The core network device (e.g., the first core network device or other core network device) may determine one or more area identifiers based on the one or more geographic location information in the preset route, for example, by converting the one or more geographic location information into one or more area identifiers (e.g., converting the coordinate values ​​into a TAI).

[0245] In the Internet of Things scenario, the service requester usually requires the terminal device to move along a preset route. Therefore, the first core network device determines to perform location management on the first terminal device based on the preset route (or the area corresponding to the preset route). This can achieve location management of the terminal device only on the preset route (or the area corresponding to the preset route), which can save power consumption.

[0246] 4. The current time is within the time period for executing location management.

[0247] The time period for executing location management may also be described as a time period during which location management needs to be executed, or a time period during which location management is required.

[0248] In one possible implementation, the first time information indicates a time period for performing location management. The first time information may be sent by the first service requester, or sent by another core network device (such as a second core network device), or preconfigured on the first core network device. This embodiment of the application does not limit the source of the first time information.

[0249] It can be understood that when the first service request direction sends the first time information to the first core network device, the first time information can be carried in the second message described above (such as the service subscription request message) or in other messages, and the embodiment of this application does not limit this.

[0250] When the current time is within the time period indicated by the first time information, the first core network device can determine to perform location management on the first terminal device according to the terminal identifier. Optionally, the first time information can include one or more of a start time, a duration, and an end time.

[0251] For example, the subscription data sent by the second core network device includes first time information, and the first time information indicates a time period for performing location management. When the current time is within the time period indicated by the first time information, the first core network device can determine to perform location management on the first terminal device based on the terminal identifier.

[0252] In the embodiments of the present application, the above-mentioned methods can be implemented separately or in combination with each other. The following lists several possible specific implementation methods:

[0253] Example 1: The first core network device receives a terminal identifier from a first terminal device (such as receiving a first registration request message, which carries the terminal identifier of the first terminal device); the first core network device obtains the contract data of the first terminal device from the second core network device based on the terminal identifier of the first terminal device, and the contract data includes at least one of the first information, the second information or the capability information of the terminal device; the first core network device determines to perform location management on the first terminal device based on the contract data.

[0254] Example 2: The first core network device receives the terminal identification and capability information from the first terminal device (such as receiving a first registration request message, which carries the terminal identification and capability information of the first terminal device); the first core network device obtains the contract data of the first terminal device from the second core network device based on the terminal identification of the first terminal device, and the contract data includes the first information and / or the second information; the first core network device determines to perform location management on the first terminal device based on the contract data and the capability information of the first terminal device.

[0255] Example 3: A first core network device receives a terminal identifier and capability information of a first terminal device from a first terminal device (e.g., receives a first registration request message, which carries the terminal identifier and capability information of the first terminal device); the first core network device determines to perform location management on the first terminal device based on the capability information of the first terminal device (e.g., the capability information indicates that the first terminal device supports location management). Alternatively, the first core network device receives a terminal identifier from the first terminal device, which includes the capability information of the first terminal device, and the first core network device determines to perform location management on the first terminal device based on the capability information of the first terminal device.

[0256] Example 4: The first core network device receives a terminal identifier from the first terminal device (such as receiving a first registration request message, which carries the terminal identifier of the first terminal device); the first core network device obtains locally configured (or stored) information, and the locally configured (or stored) information includes one or more items of a terminal device list, a service requester list, and capability information of the first terminal device; the first core network device determines to perform location management on the first terminal device based on one or more items of the terminal device list, the service requester list, and capability information of the first terminal device.

[0257] Example 5: The first core network device receives a terminal identifier from a first terminal device (such as receiving a first registration request message, which carries the terminal identifier of the first terminal device); the first core network device receives first information and / or second information from a first service requester (such as receiving a service subscription request message, which includes the first information and / or second information), and the first core network device determines to perform location management on the first terminal device based on the first information and / or the second information.

[0258] Of course, the above combinations are only examples and are not limited to these.

[0259] S403. The first core network device determines a set of area identifiers for performing location management.

[0260] The region identifier set may represent one or more regions. For example, the region identifier set may include one or more region identifiers, where a region identifier indicates a region, and different region identifiers indicate different regions. Accordingly, the region identifier set indicates one or more regions.

[0261] The area identifier set used for executing location management may be understood as the area identifier set used when executing location management, that is, the area identifier set is used for executing location management.

[0262] In one possible implementation, the area identifier set is used to perform location management, and the first terminal device may initiate a tracking area update process or a mobility registration update process based on the area identifier set, so that the network obtains the current location information of the first terminal device.

[0263] Exemplarily, the first terminal device initiates a tracking area update process or a mobility registration update process based on the area identifier set. The specific implementation method may be that after the first terminal device leaves the area represented by the area identifier set, the first terminal device initiates the mobility registration update process or the tracking area update process. For example, when the area identifier included in the broadcast message monitored by the first terminal device does not belong to any area identifier in the area identifier set acquired by the first terminal device (indicating that the first terminal device is leaving the area represented by the area identifier set), the first terminal device initiates the tracking area update process or the mobility registration update process.

[0264] Since the first terminal device can initiate an access process to the network after leaving the area represented by the area identifier set based on the area identifier set, so that the network knows the current location of the first terminal device, the area identifier set can be used to perform location management.

[0265] It can be understood that the area identifier set used to perform location management does not mean that location management is performed only in the area corresponding to the area identifier set.

[0266] In one possible implementation, the first core network device may determine a set of area identifiers based on the area where the first terminal device is located. For example, in S401, the first core network device receives the terminal identifier of the first terminal device from the first access network device, and then determines that the first terminal device is located within the coverage range of the first access network device, and then determines a set of area identifiers based on the area (which may be one or more areas) corresponding to the first access network device. Exemplarily, the area corresponding to the first access network device may be one or more tracking areas (for example, one or more tracking areas supported by the first access network device), and the first core network device may combine the one or more tracking area identifiers corresponding to the first access network device into a set of area identifiers (for example, a TAI list). Alternatively, the first core network device may combine the one or more tracking area identifiers corresponding to the first access network device and the tracking area identifiers corresponding to other areas adjacent to the first access network device into a set of area identifiers (for example, a TAI list).

[0267] For example, referring to Figure 5A , which illustrates an example of the coverage of a first access network device (e.g., a base station), the coverage of the first access network device (e.g., a base station) includes two tracking areas, namely, TA1 and TA2 (with area identifiers TAI1 and TAI2, respectively). The area identifier set can be {TAI1} or {TAI2} or {TAI1, TAI2}. It should be understood that Figure 5A only illustrates some examples of TAs and does not represent the actual size or shape of the TAs.

[0268] In another possible implementation, the first core network device can obtain a preset route and determine a set of area identifiers for performing location management based on the area covering part or all of the preset route, where the area identifier set includes the area identifiers of the area covering part or all of the preset route.

[0269] The preset route may be sent by the first service requester, or sent by other core network devices (such as the second core network device), or pre-configured in the first core network device. The embodiment of the present application does not limit the source of the preset route. It is understood that when the first service requester sends the preset route to the first core network device, the preset route may be carried in the second message (such as the service subscription request message) described above, or may be carried in other messages. The embodiment of the present application does not limit this.

[0270] The information in the preset route may be the same as the information in the area identifier set. Exemplarily, the preset route may include one or more area identifiers, and the area indicated by the one or more area identifiers corresponds to the mobile route of the first terminal device. The first core network device uses the preset route as the area identifier set, that is, the area identifier in the preset route is the area identifier in the area identifier set. Among them, the area identifier specifically includes, but is not limited to, PLMN identifier, TAI, cell identifier (such as cell ID), CAG identifier, reader identifier, access network device identifier (such as RAN identifier, gNodeB identifier, etc.), user equipment identifier (such as GPSI, SUCI, SUPI, etc.), etc.

[0271] The information in the preset route may be different from the information in the area identifier set. For example, the preset route includes one or more geographic location information (e.g., coordinate values ​​or longitude and latitude), and the first core network device determines the area identifier set based on the preset route. For example, the first core network device may convert the one or more geographic location information in the preset route into one or more area identifiers (e.g., converting the coordinate values ​​into TAIs), and the converted area identifiers are the area identifiers in the area identifier set.

[0272] In specific implementation, the first core network device can send the area identifier corresponding to the area covering all routes in the preset route to the first terminal device (that is, the first core network device determines the area identifier set used to perform location management based on the area covering all routes in the preset route); or, the first core network device can send the area identifier corresponding to the area of ​​some routes in the preset route to the first terminal device (for example, the first core network device divides the preset route into multiple sections, and sends the area identifier multiple times, each time sending the area identifier corresponding to one section of the route).

[0273] For example, see Figure 5B , which shows an example of a preset route. The preset route includes location A (starting point), location B, location C, and location D (end point), where location A is located in TA1, location B and location C are both located in TA2, and location D is located in TA3. The area identifiers of TA1, TA2, and TA3 are TAI1, TAI2, and TAI3, respectively. The area identifier set can be {TA1, TA2, TA3}, or {TA1, TA2}, or {TA1}, etc. It will be understood that Figure 5B only illustrates some examples of TAs and does not represent the actual size or shape of the TAs.

[0274] S404. The first core network device sends a set of area identifiers to the first terminal device. Correspondingly, the first terminal device receives the set of area identifiers.

[0275] Exemplarily, after authenticating and / or authorizing the first terminal device, the first core network device may send a first registration acceptance message to the first terminal device, where the first registration acceptance message includes the area identifier set. Similarly, the first core network device may send the first registration acceptance message to the first terminal device via the first access network device.

[0276] Optionally, after receiving the area identifier set, the first terminal device can save the area identifier set and initiate a tracking area update process or a mobility registration update process based on the area identifier set. Exemplarily, during the movement, the first terminal device listens to the cell broadcast message, and after receiving the cell broadcast message, obtains the area identifier in the cell broadcast message, and compares the area identifier with the area identifier in the area identifier set. If none of the area identifiers in the area identifier set is the same as the area identifier in the cell broadcast message, or if any area identifier included in the broadcast message is not the same as the area identifier in the area identifier set, it means that the first terminal device has moved out of the area corresponding to the area identifier set. The first terminal device can initiate a tracking area update process or a mobility registration update process to the network, so that the network (or core network) obtains the current location information of the first terminal device. For example, the first core network device is notified that the first terminal device has moved out of the area corresponding to the area identifier set, so that the first core network device determines a new area identifier set for the first terminal device.

[0277] Take the mobility registration update process as an example: the first terminal device sends a third registration request message to the first core network device through the second access network device (for example, the first terminal device initiates random access to the new access network device (such as the second access network device), and after the random access is successful, the third registration request message is sent to the first core network device through the second access network device). The third registration request message carries the terminal identifier of the first terminal device. The subsequent method executed by the first core network device can refer to the method executed by the first core network device after receiving the first registration request message above, and will not be repeated here.

[0278] In the above scheme, after receiving the terminal identification of the first terminal device, the first core network device needs to determine whether to perform location management on the first terminal device. When it is determined to perform location management on the first terminal device, it sends information for performing location management (such as an area identification set) to the first terminal device. This can enable the core network to perform location management on terminal devices as needed (for example, performing location management on terminals that meet at least one of the conditions of supporting location management, requiring location management, and being located in an area requiring location management), rather than blindly performing location management on all terminals. This can reduce network overhead (such as context maintenance costs) and improve location management efficiency.

[0279] In one possible design, when the first core network device determines a set of area identifiers for performing location management based on an area covering part or all of a preset route, if the first terminal device moves out of the area corresponding to the set of area identifiers, the first terminal device will report the terminal identifier of the first terminal device to the first core network device through an access network device (such as a second access network device). After the first core network device receives the terminal identifier of the first terminal device from the second access network device, it can determine the area where the first terminal device is located based on the location information of the second access network device. If the first terminal device deviates from the preset route (for example, the area where the first terminal device is located does not belong to the area of ​​the preset route), it can report the abnormal location of the first terminal device to the first service requester, for example, by sending third information to the first service requester, the third information indicating that the location of the first terminal device is abnormal. Optionally, the third information specifically indicates that the first terminal device has deviated from the preset route. When the location of the first terminal device is normal, the first core network device may not report the third information, or may report the location information of the first terminal device and / or information indicating that the location is normal. For example, when the area where the first terminal device is located belongs to the preset route, the first core network device sends eighth information to the first service requester, the eighth information indicating that the location of the first terminal device is normal (or has not deviated from the preset route).

[0280] For example, see Figure 5C, which is an example of the actual moving trajectory of the first terminal device. The preset route is A→B→C→D, the corresponding TA is TA1→TA2→TA3, and the area identifier set received by the first terminal device is, for example, {TAI1, TAI2, TAI3}. The actual trajectory of the first terminal device is TA1→TA2→TA4. When the first terminal device is in TA1, the TA identifier heard by the first terminal device in the cell broadcast message is TAI1, which is one of {TAI1, TAI2, TAI3}, so it will not be reported; when the first terminal device is in TA2, the TA identifier heard by the first terminal device in the cell broadcast message is TAI2, which is one of {TAI1, TAI2, TAI3}, so it will not be reported; after the first terminal device enters TA4, the TA identifier heard by the first terminal device in the cell broadcast message is TAI4, which is not any of {TAI1, TAI2, TAI3}, and reports the location update to the first core network device (for example, sending a third registration request message, the message carries the terminal identifier of the first terminal device), and the first core network device can determine the area where the first terminal device is located through the location information of the second access network device, and then determine that the first terminal device has deviated from the preset route.

[0281] Through the above design, when the first terminal device deviates from the preset route, the network (such as the core network) can notify the first service requester, so that the first service requester can promptly discover the route error of the first terminal device and reduce the transportation cost caused by the route error. For example, in a logistics scenario, the first terminal device is a transportation tool, or the first terminal device is attached to an item and transported by the transportation tool. During the transportation process, the first service requester (such as an application function, a third party, an enterprise, etc.) hopes that the network can manage the location of the item. Through the above design method, when an abnormality occurs in the transportation path, the first service requester can promptly discover the abnormality of the transportation path, avoiding the discovery of the abnormality after the item arrives at the wrong destination.

[0282] In one possible design, the first core network device determines whether the first terminal device arrives at the target location within the time indicated by the second time information. When the first terminal device does not arrive at the target location within the time indicated by the second time information, the first core network device may send fourth information to the first service requester, and the fourth information indicates that the location of the first terminal device is abnormal. Optionally, the fourth information specifically indicates that the first terminal device has not arrived at the target location within the specified time (such as the time indicated by the second time information). When the location of the first terminal device is normal, the first core network device may not report it, or report that the location of the first terminal device is normal. For example, when the first terminal device arrives at the target location within the specified time, the first core network device sends ninth information to the first service requester, and the ninth information indicates that the location of the first terminal device is normal (or the first terminal device arrives at the target location within the specified time).

[0283] Among them, the location information and / or the second time information of the target location may be sent by the first service requester, or sent by other core network devices (such as the second core network device), or pre-configured in the first core network device. The embodiment of the present application does not limit the source of the location information and / or the second time information of the target location. It can be understood that when the first service requester sends the location information and the second time information of the target location to the first core network device, the location information and the second time information of the target location can be carried in the second message (such as the service subscription request message) described above, or can be carried in other messages. The embodiment of the present application does not limit this.

[0284] The second time information indicates the time when the first terminal device arrives at the target location (for example, the time expected, required, or indicated by the first service requester for the first terminal device to arrive at the target location). The second time information may be different from the first time information, or the second time information may be included in the first time information (for example, the first time information includes a start time and an end time, and the second time information is the end time), which is not limited in this application.

[0285] Several specific implementations of the first core network device determining that the first terminal device has not arrived at the target location within the time indicated by the second time information are listed below:

[0286] Example 1: The first core network device can send paging information (or paging message) to one or more access network devices (for example, all access network devices connected to the first core network device) within the time indicated by the second time information. The paging information indicates that paging is performed on the first terminal device, and the paging information includes the terminal identifier of the first terminal device; if an access network device pages the first terminal device, the access network device will report the terminal identifier of the first terminal device to the first core network device. For example, the first core network device receives the terminal identifier of the first terminal device from the third access network device (indicating that the third access network device pages the first terminal device), the first core network device can determine that the first terminal device is located in the area corresponding to the location information of the third access network device, and then the first core network device can determine whether the first terminal device is located at the target location based on the location information of the third access network device and the location information of the target location; if the first terminal device is located at the target location, the first core network device can determine that the first terminal device arrived at the target location within the time indicated by the second time information, otherwise it can be determined that the first terminal device did not arrive at the target location within the time indicated by the second time information.

[0287] Example 2: The first core network device may send a paging message to one or more access network devices corresponding to the target location within the time indicated by the second time information. The paging message indicates that paging is to be performed on the first terminal device, and the paging message includes the terminal identifier of the first terminal device. The first core network device determines whether the first terminal device has arrived at the target location within the time indicated by the second time information based on whether the terminal identifier of the first terminal device is received from any of the one or more access network devices corresponding to the target location. For example, if the first core network device does not receive the terminal identifier of the first terminal device from any of the access network devices corresponding to the target location within the time indicated by the second time information, it is determined that the first terminal device has not arrived at the target location within the time indicated by the second time information.

[0288] In some embodiments, performing paging on the first terminal device may be performing an inventory operation or an inventory operation on the first terminal device.

[0289] It can be understood that in the embodiment of the present application, the same terminal device can have multiple terminal identifiers in different forms. In different processes or different messages, the terminal identifiers of the same terminal device can be the same or different, and the embodiment of the present application does not limit this. For example, in some messages or processes, the terminal identifier can be SUCI, 5G-GUTI or TMSI, and in other messages or processes, the terminal identifier can be SUPI or GPSI, etc. Exemplarily, the first terminal identifier used in the paging process (such as the terminal identifier in the paging information) can be different from the terminal identifier of the first terminal device used in location management (such as the terminal identifier in S401). For example, the terminal identifier in S401 can be a permanent identifier (such as SUCI, which is an identifier that is encrypted after the permanent identifier is encrypted), or it can be a temporary identifier, depending on whether the first terminal device has a temporary identifier previously allocated by the AMF (if a temporary identifier is stored, the first terminal device reports the temporary identifier, and if the temporary identifier is not stored, the first terminal device reports the permanent identifier); and the terminal identifier in the paging information is usually a temporary identifier of the terminal device.

[0290] Example 3, the area identifier set determined in step S403 may not include the area identifier of the area covering the target location. For example, if the target location is the end point shown in Figure 5C, the area identifier set may be {TA1, TA2}. After the first core network device receives the terminal identifier of the first terminal device from the third access network device, it can determine that the area where the first terminal device is located is the area covering the target location (such as TA4) based on the location information of the third access network device, and then determine whether the first terminal device arrives at the target location within the time indicated by the second time information based on the current time and the second time information. For example, if the current time is within the time indicated by the second time information, it is determined that the first terminal device arrives at the target location within the time indicated by the second time information; if the current time has exceeded the time indicated by the second time information, it is determined that the first terminal device has not arrived at the target location within the time indicated by the second time information.

[0291] Of course, the above two are just examples and are not limited to them.

[0292] Through the above design, the first service requester can promptly learn that the first terminal device has not arrived at the designated location at the designated time and / or discover that the first terminal device has taken an incorrect route, thereby reducing transportation costs caused by the error.

[0293] In one possible design, when the first core network device determines that the first terminal device is in the same location or the same area for more than a period of time, it can report the abnormality to the first service requester, for example, by sending the fifth information to the first service requester, and the fifth information indicates that the location of the first terminal device is abnormal.

[0294] In one implementation, the third time information indicates the duration. The duration may be the maximum duration (or a preset duration) that the first terminal device is located in the same area. The third time information may be different from the first time information, or the third time information may be included in the first time information, which is not limited in this application.

[0295] Similarly, the third time information may be sent by the first service requester, or sent by other core network devices (such as the second core network device), or pre-configured in the first core network device. The embodiment of the present application does not limit the source of the third time information. It can be understood that when the first service requester sends the third time information to the first core network device, the third time information can be carried in the second message described above (such as the service subscription request message) or in other messages. The embodiment of the present application does not limit it.

[0296] The following lists several specific ways in which the first core network device determines that the first terminal device has been in the same location for more than a preset time:

[0297] Example 1: The first core network device may send a paging message through one or more access network devices (for example, all access network devices to which the first core network device is connected). The paging message is used to perform paging on the first terminal device, and the paging message includes the terminal identifier of the first terminal device. If the duration (or time difference) of the first core network device receiving the terminal identifier of the first terminal device from the same access network device multiple times (or multiple times in succession) exceeds the preset duration, it is determined that the first terminal device has been in the same location (that is, the area where the access network device is located) for more than the preset duration. For example, the time when the first core network device receives the terminal identifier of the first terminal device from access network device A is time node A; the time when the first core network device receives the terminal identifier of the first terminal device from access network device A again is time node B; when the time difference between time node B and time node A exceeds (or is equal to) the preset duration, it can be considered that the first terminal has been in the same location for more than the preset duration. For another example, the time when the first core network device receives the terminal identification of the first terminal device from the access network device A is time node A; when the first core network device still receives the terminal identification of the first terminal device from the access network device A at time node B, it can be considered that the first terminal is in the same location for more than the preset time length, wherein the time difference between time node B and time node A exceeds (or is equal to) the preset time length.

[0298] Example 2: The first core network device periodically sends paging information to one or more access network devices according to a preset duration. The paging information is used to perform paging on the first terminal device, and the paging information includes the terminal identifier of the first terminal device. If the terminal identifier of the first terminal device is received multiple times from the same access network device or the number of times the terminal identifier of the first terminal device is received from the same access network device exceeds (or is equal to) a set number of times or a set threshold, it is determined that the first terminal device has been in the same location for more than a preset duration. For example, the first core network device can periodically send paging information to one or more access network devices according to a preset duration (for example, with the preset duration as a single cycle). If the first core network device receives the terminal identifier of the first terminal device from the same access network device multiple times, it means that the first terminal device has been in the area corresponding to the access network device for more than a preset duration.

[0299] Example 3, the area identifier set determined in S403 includes the area identifier of the area covering part of the preset route; if the first core network device does not receive the terminal identifier of the first terminal device from any access network device for more than a preset time period, or if the first core network device does not receive the terminal identifier of the first terminal device from any access network device outside the area represented by the area identifier set for more than a preset time period, it can be determined that the first terminal device has been in the same position for more than the preset time period (that is, the first terminal device has been on this part of the route and has not entered the next section of the route).

[0300] Of course, the above two are just examples and are not limited to them.

[0301] Through the above design, the first service requester can promptly discover that the first terminal device has been at the same location for more than a preset time, so that the first service requester can promptly check whether the first terminal device has fallen during movement or whether the transportation vehicle for transporting the first terminal device is faulty.

[0302] It can be understood that when the first core network device obtains any multiple items of the above-mentioned first information, second information, second location information, preset route, location information of the target location, first time information, second time information, third time information, etc. (for example, by receiving a message), the any multiple items of information can be carried in different messages respectively or in the same message, and the embodiments of the present application do not impose any restrictions.

[0303] In one possible design, the first core network device may determine to perform location management on the first terminal device based on static configuration information. For example, one or more of the first information, second information, second location information, etc. mentioned above are configured in the subscription data and such information does not change (or does not change for a period of time). The first core network device determines to perform location management on the first terminal device based on such information.

[0304] In another possible design, a network device (such as the first service requester) may dynamically instruct the first core network device to perform location management on the first terminal device.

[0305] In a possible example, the first core network device (such as AMF) can subscribe to notifications of contract data updates from the second core network device (such as UDM or UDR), and the first service requester (such as AF) can update the contract data of the first terminal device in the second core network device, so that the parameters related to location management in the contract data (such as first information, second information, second location information, first time information, second time information, etc.) change. After the contract data of the first terminal device is changed, the second core network device sends the changed contract data of the first terminal device to the first core network device, so that the first core network device determines to perform location management on the first terminal device based on the changed contract data of the first terminal device.

[0306] For example, the first terminal device does not initially need location management, and its contract data does not include the first information and / or the second information. AF sends a parameter provisioning message (such as external parameter provisioning) to UDM through NEF (of course, the name of the message can also be other in actual application, and this application does not limit it). The parameter provisioning message includes indication information indicating that the first terminal device needs to be location managed or the first service requester needs location management (such as the identifier of the first terminal device or the identifier of AF). After receiving the parameter provisioning message, UDM adds relevant parameters to the contract data of the first terminal device, such as the first information and / or the second information, and UDM sends the changed contract data (including the first information and / or the second information) to AMF, and then AMF can determine to perform location management on the first terminal device based on the changed contract data.

[0307] For example, the first terminal device is located in area A, and the contract data does not include the area that requires location management. AF sends a parameter provision message to UDM through NEF (of course, the name of the message can also be other in actual applications, and this application does not limit it). The parameter provision message includes the location information of area A, indicating that area A requires location management (or the terminal device in area A needs to be location managed). After receiving the parameter provision message, UDM adds the location information of area A to the contract data of the first terminal device, and UDM sends the changed contract data (including the location information of area A) to AMF. Then AMF can determine to perform location management on the first terminal device in area A based on the changed contract data.

[0308] Optionally, the parameter provision message may include a terminal identifier of the first terminal device, indicating that the subscription data of the first terminal device is updated. Further, optionally, the parameter provision message may include terminal identifiers of multiple terminal devices, indicating that the subscription data of multiple terminal devices is updated.

[0309] It can be understood that the above is only an example, and the actual update content and update method of the contract data are not limited to this.

[0310] In another possible example, the first service requester may subscribe to location service management from the first core network device, for example, by sending a service subscription request message to the first core network device, wherein the service subscription request message includes one or more of the second location information (such as a preset route), the first time information, etc. After receiving the service subscription request message, the first core network device determines to perform location management on the first terminal device based on the content of the service subscription request message. Optionally, the service subscription request may also include indication information indicating location management; the service subscription request may also include a terminal identifier of the first terminal device, indicating that the subscription is for the first terminal device, or indicating that location management needs to be performed on the first terminal device (equivalent to the first information above); the service subscription request message may also include an identifier of the first service requester, indicating that the subscription is for the first service requester, or indicating that the first service requester (or the terminal device managed by the first service requester) needs location management (equivalent to the second information above).

[0311] In some embodiments, the first service requester may instruct the first core network device to stop performing location management on the first terminal device.

[0312] Exemplarily, the first service requester (such as AF) may send a third message (such as a service desubscription request message) to the first core network device, where the third message indicates to stop performing location management on the first terminal device; after receiving the third message, the first core network device may send the sixth information and / or the seventh information to the first terminal device according to the third message, where the sixth information indicates that the first terminal device removes the area identification set, and the seventh information indicates that the first terminal device does not need to update the location of the first terminal device to the network (for example, there is no need to perform a tracking area update process or a mobility registration update process). After receiving the sixth information and / or the seventh information, the first terminal device removes the area identification set.

[0313] Optionally, the seventh information can be a default area identifier or an area identifier used to indicate a global location (for example, all areas served by the first core network device, or the entire network area (for example, a public network area or a non-public network area), etc.), and the first terminal device also saves the area identifier.

[0314] Subsequently, the first terminal device can determine that it does not need to be location managed based on the locally unsaved area identifier or the locally saved area identifier as the default area identifier or the area identifier used to indicate the global location, that is, it does not need to notify the network of the location of the first terminal device, for example, it does not listen to the area identifier in the cell broadcast message, or does not compare the area identifier in the cell broadcast message with the area identifier stored in itself, etc.

[0315] Exemplarily, the first service requester (such as AF) can update the contract data in the second core network device (for example, AF sends an indication message to UDM or UDR, instructing UDM or UDR to delete the first information and / or second information in the contract data, etc.), and instruct the first core network device through the updated contract data to stop performing location management on the first terminal device.

[0316] Of course, the above are only examples and are not limited to these.

[0317] In this way, the first core network device can stop performing location management on the first terminal device in a timely manner according to the needs of the service requester, thereby saving system resources.

[0318] Referring to FIG6 , an embodiment of the present application further provides a location management method, the method comprising:

[0319] S601: A first core network device sends billing information corresponding to location management, and a third core network device receives the billing information.

[0320] The third core network device is a device responsible for charging in the network, such as a charging function (CHF) network element.

[0321] Exemplarily, the billing information includes but is not limited to one or more of the following:

[0322] 1) Event type information, indicating the event corresponding to location management;

[0323] 2) The number of regional identifiers used to perform location management;

[0324] 3) the duration of performing location management;

[0325] 4) Number of times location management is performed;

[0326] 5) The number of terminal devices for which location management is performed.

[0327] It is understood that the above-mentioned billing information can be billing information corresponding to one or more terminal devices, or billing information corresponding to one or more service requesters, and this application does not impose any restrictions. The billing information can correspond to one or more location management, or to location management within a period of time (such as one month or one year, etc.), and this application does not impose any restrictions.

[0328] S602. The third core network device determines the fee corresponding to the location management according to the billing information.

[0329] After receiving the billing information, the third core network device can count the fees and generate a bill based on the fee statistics results.

[0330] In an embodiment of the present application, when location management is used as a service, the first core network device can send billing information corresponding to the location management to the third core network device, so that the third core network device can calculate the fees and realize paid use of location management.

[0331] It can be understood that the above is an example of performing location management on a terminal device (specifically, the first terminal device). In actual applications, location management may not be performed on the terminal device.

[0332] 7 is a flowchart of another location management method provided in an embodiment of the present application, the method comprising:

[0333] S701. The first core network device obtains the terminal identification of the second terminal device.

[0334] Exemplarily, the second terminal device sends the terminal identification of the second terminal device, and the first core network device receives the terminal identification of the second terminal device.

[0335] The specific implementation of this step can refer to the specific implementation of the first terminal device sending the terminal identification of the first terminal device to the first core network device in S401 above. For example, the second terminal device sends a second registration request message to the first core network device through the access network device, and the second registration request message includes the terminal identification of the second terminal device.

[0336] S702. The first core network device determines not to perform location management on the second terminal device based on the terminal identifier of the second terminal device.

[0337] The specific implementation of this step can refer to the determination by the first core network device in S402 above regarding whether to perform location management on the first terminal device, with the difference being the determination result. For example, in one possible design, the first core network device may determine not to perform location management on the second terminal device based on one or more of the following: 1. The second terminal device does not require location management; 2. The second terminal device does not support location management; 3. The second terminal device is not located in an area where location management is performed; or 4. The current time is not within a time period where location management is performed.

[0338] S703. The first core network device does not send the area identifier set to the first terminal device (not shown in FIG7 ), or the first core network device sends a default area identifier to the first terminal device.

[0339] Exemplarily, after authenticating and / or authorizing the second terminal device, the first core network device sends a second registration accept message to the second terminal device, where the second registration accept message indicates that the second terminal device has successfully registered, and the region identifier in the second registration accept message is empty, a default region identifier, or a region identifier used to indicate a global location. It will be understood that the region identifier in the second registration accept message being empty means that the second registration accept message does not include the region identifier.

[0340] Since the area identifier in the second registration acceptance message is empty or the default area identifier, the second terminal device does not need to perform location management, that is, it does not need to update its own location to the network. For example, the second terminal device does not listen to the area identifier in the cell broadcast message, or does not compare the area identifier in the cell broadcast message with the area identifier saved by itself.

[0341] It is understandable that the same terminal device may have different location management requirements at different times. For example, the first terminal device and the second terminal device mentioned above are the same terminal device, and the method flow shown in Figure 4 and the method flow shown in Figure 7 are executed at different times.

[0342] It is understood that the above embodiments can be implemented separately or in combination with each other. In order to better understand the above technical solution, two examples of combined implementation are listed below:

[0343] Example 1. See Figure 8, which is a flowchart of another location management method provided in an embodiment of the present application. In this example, the first core network device takes AMF or TMF (denoted as AMF / TMF) as an example, the second core network device takes UDM or UDR (denoted as UDM / UDR) as an example, the first service requester takes AF as an example, and the first terminal device takes a tag as an example.

[0344] S800: Label initialization process.

[0345] Exemplarily, the tag is initialized, for example, by a label printer writing identification information and configuration information to the tag. The configuration information may include one or more of capability information (such as terminal type (active, passive, or semi-passive), information on support or non-support of location management, and a default area identifier (such as a default TAI). Optionally, the configuration information may be included in the terminal identifier. The default TAI indicates that the tag does not need to perform mobility management.

[0346] S801. AF sends a service request message to AMF / TMF through NEF. The service request message may include one or more of instructions, terminal identification, location information, AF identification, etc.

[0347] The instruction may include one or more of inventory, read, write, deactivate, locate, etc. The instruction indicates the operation that the AF requests to be performed.

[0348] The terminal identifier indicates the target terminal corresponding to the instruction, that is, the terminal identifier of the terminal on which the operation needs to be performed. The terminal identifier can be one or more (that is, the operation can be requested to be performed on one or more terminals at the same time). The terminal identifier includes the identifier of the tag.

[0349] The location information indicates the location range within which the instruction is to be executed, i.e., the operation is performed on terminals within the location range. In one possible implementation, the location information may be one or more of geographic location information (e.g., coordinate values, longitude and latitude), network identifier, TAI, cell identifier, CAG identifier, reader / writer identifier, access network device identifier, and user equipment identifier.

[0350] It can be understood that S801 is an optional step.

[0351] S802. AMF / TMF instructs the current reader / writer of the tag (such as reader / writer 1) to execute a random access process.

[0352] The reader / writer may be an access network device or a user device, etc., without limitation.

[0353] In one possible implementation, the AMF / TMF may send a random access initiation instruction and a mask to the interrogator. During the random access process, the interrogator may broadcast this mask to indicate the tags within its coverage range and the tag range for this random access. Tags within the coverage range determine whether to participate in the random access based on the broadcasted mask. For example, if a tag falls within the tag range indicated by the mask, it may participate in the random access process. If a tag does not fall within the tag range indicated by the mask, it does not participate in the random access process.

[0354] It can be understood that S802 is an optional step.

[0355] S803: The reader 1 interacts with the tag to complete the random access process.

[0356] In one possible implementation, in the random access process, the reader sends a select command, and the select command may include the mask information in step S802. After being stimulated, the tag listens to the mask information. When the tag's identifier belongs to the tag range indicated by the mask information, the tag can generate a random number. Subsequently, the reader can periodically broadcast query (Query) or query request (QueryRep) instructions, and each time the tag listens to a Query or QueryRep instruction, it can reduce the random number by one. When the random number is reduced to 0, the tag can send a 16-bit random number (called RN16) to the reader. If there is no conflict (that is, no other tag sends RN16 at the same time), the reader can correctly demodulate the random number RN16, and the reader sends the RN16 to the tag, indicating that the RN16 is successfully received. After the tag correctly receives the RN16 from the reader, step 4 is executed.

[0357] In another possible implementation, the reader broadcasts a system message (eg, system information broadcast), the tag determines to perform a random access procedure according to the system message, and interacts with the reader to complete the random access procedure.

[0358] S804. When random access is successful, the tag can send the tag identifier to AMF / TMF through the reader / writer, and AMF / TMF receives the tag identifier.

[0359] It can be understood that the way in which the AMF / TMF obtains the tag identification in step S804 can refer to the way in which the first core network device obtains the terminal identification of the first terminal device in step S401 above, and is not limited to receiving the tag identification through the reader.

[0360] In one possible implementation, the tag can send a NAS message (such as a registration request message) to the AMF / TMF through a reader / writer (such as an access network device), and the NAS message includes the tag's identifier.

[0361] Optionally, the NAS message may also carry capability information.

[0362] In one possible implementation, the capability information indicates that the tag is one of a passive device, a semi-passive device, and an active device; or, the capability information indicates that the tag supports or does not support location management; or, the capability information indicates that the tag supports location management (if the tag does not provide capability information, it means that the tag does not support location management).

[0363] It can be understood that when the tag is randomly accessed successfully, if steps 801 and 802 are executed, the reader (such as an access network device) will forward the instruction sent by the core network to the tag. The tag obtains or sends corresponding information according to the instruction. For example, when the instruction is an inventory instruction or an inventory operation is performed, the tag will send the tag identifier; when the instruction is a read instruction or a read operation is performed, the tag will send the data stored in the tag storage area; when the instruction is a write instruction or a write operation is performed, the tag will store the data to be written to the tag included in the instruction in the tag storage area. The reader sends (or forwards) the information sent by the tag to the core network; the core network sends the information to the AF.

[0364] S805. Optionally, a security authentication process is performed between the tag and the network.

[0365] Among them, the entities involved in the security process may include one or more of tags, AMF / TMF, AUSF, UDM, authentication, authorization and accounting (AAA) servers, etc.

[0366] S806. AMF / TMF determines whether to perform location management on the tag.

[0367] It is understood that the specific implementation of step S807 can refer to the above S402. For example, the AMF / TMF determines whether to perform location management on the tag based on any one or more of the following information:

[0368] A. Pre-configuration information of AMF / TMF, or tag and / or AF subscription data obtained from UDM / UDR.

[0369] In one possible implementation, the pre-configuration information may include a terminal identification list. When the terminal identification list includes the identification of the tag, the tag needs to be location managed; or, the pre-configuration information includes a service requester list. When a service request message is received from a service requester (i.e., AF) included in the service requester list, it is determined that location management needs to be performed on the terminal belonging to the service requester.

[0370] In another possible implementation, the UDM / UDR stores the tag's contract data, which includes indication information for indicating whether the tag needs to perform location management. Alternatively, the contract data includes indication information for indicating that the tag needs to perform location management (equivalent to the first information above). It is understood that if the contract data does not contain this indication information, it means that the tag does not need to perform location management.

[0371] In another possible implementation, the UDM / UDR stores the AF or the corresponding contract data or the service configuration information of the passive IoT service, and the contract data or service configuration information includes a list of terminals (terminal identification list) for which the AF needs to perform location management. Alternatively, the contract data or service configuration information includes indication information for indicating whether the AF needs location management. If so, the terminal belonging to the AF (such as the tag) needs to be location managed. Alternatively, the contract data or service configuration information includes indication information (such as the second information) for indicating that the AF needs to perform location management, and the terminal belonging to the AF (such as the tag) needs to be location managed.

[0372] B. Tag capability information.

[0373] For example, when the tag sends capability information in S804, and the capability information indicates that the tag is a first type of terminal (e.g., active), it is determined that location management is performed on the tag; if the capability information indicates that the tag is a second type of terminal (e.g., passive or semi-passive), it is determined that location management is not performed on the tag. Alternatively, when the capability information indicates that the tag supports location management, it is determined that location management is performed on the tag; when the capability information indicates that the tag does not support location management, it is determined that location management is not performed on the tag.

[0374] C. Location information sent by AF or location information in contract data.

[0375] In one possible implementation, when the area indicated by the location information is a first-category area (equivalent to the area indicated by the second location information above), AMF / TMF needs to perform location management; when the area indicated by the location information is a second-category area, AMF / TMF does not perform location management.

[0376] Among them, the first type of area indicates the area where location management is performed, such as the area corresponding to the public network (PLMN), or one or more of specific geographical location information (such as coordinate values, longitude and latitude, etc.), network identifier (such as public network identifier PLMN), TAI, cell identifier, closed group identifier, reader identifier, access network equipment identifier, user equipment identifier, etc.

[0377] The second type of area indicates an area where mobile management does not need to be performed, such as an area corresponding to a non-public network, or one or more of specific geographic location information (such as coordinate values, longitude and latitude, etc.), network identifier (such as a non-public network identifier SNPN ID or PLMN ID+NID), TAI, cell identifier, closed group identifier, reader / writer identifier, access network device identifier, user equipment identifier, etc.

[0378] S807. When the AMF / TMF determines to perform location management on the tag, information for performing location management may be included in the message sent to the tag (eg, a NAS message or a registration accept message).

[0379] It can be understood that the specific implementation of step S807 can refer to the above S404.

[0380] Exemplarily, AMF / TMF may send the area identifier of the registration area (such as TAI, the number of TAIs may be one or more) to the tag, and the specific form may be a set of area identifiers.

[0381] When the AMF / TMF determines not to perform location management on the tag, the AMF / TMF does not need to send information for performing location management, such as TAI, to the tag; alternatively, the AMF / TMF may send a default area identifier (such as a default TAI) to the terminal, indicating that the tag does not need to be location managed. For example, based on the default TAI, the tag does not need to monitor the TA broadcast by the base station (or reader) and does not need to perform the mobility registration update process (or tracking area update process).

[0382] It can be understood that before AMF / TMF sends the area identifier set, it needs to determine the area identifier set. The specific implementation can refer to S403 above and will not be repeated here.

[0383] S808. The AMF / TMF may feed back information of the tag on which the operation is performed, such as the tag identifier, to the AF.

[0384] S809: The reader / writer (eg, reader / writer 2) periodically broadcasts its corresponding area identifier (eg, TAI) according to the configuration information.

[0385] In one possible implementation, the reader broadcasts a select command that includes TA information, instructing the tag to compare the broadcast TAI with the tag's stored TAI. If the broadcast TAI differs from the tag's stored TAI, the tag must perform a random access procedure.

[0386] S810: When the tag stores a TAI (ie, the TAI is not empty) or the TAI stored in the tag is not the default TAI, and the TAI stored in the tag is different from the TAI in the broadcast message, the tag performs a random access procedure and executes step S811.

[0387] S811: The tag performs a random access process. Please refer to the description of step S803 for details.

[0388] S812: When the tag is successfully randomly accessed, the tag identifier is sent to the AMF / TMF via the new reader (eg, reader 2). For details, refer to the description of step S804.

[0389] Optionally, the tag may also send a previously stored TAI. In one example, the tag may carry information such as the tag identifier and TAI in the registration request message.

[0390] S813. The AMF / TMF determines a new TAI for the tag. Alternatively, the AMF / TMF determines not to perform location management on the tag based on the configuration information or subscription data.

[0391] It is understood that the AMF / TMF determines not to perform location management on the tag based on the configuration information or subscription data, and can refer to step S702 above. S814. The AMF / TMF sends an indication message to the tag, indicating a new TAI or removing the previously saved TAI or updating the TAI saved by the tag to the default TAI.

[0392] It can be understood that step S814 can refer to the detailed description of step S703 above.

[0393] Through the above solution, the AMF / TMF can determine whether to perform location management for the terminal based on pre-configured information, subscription data, or service configuration information. When a terminal needs to be located, information for performing location management (such as TAI) is written to the terminal, allowing the core network to perform location management only for some terminals. This can reduce the network's context maintenance costs for terminals, perform location management on demand, reduce signaling overhead, and improve communication efficiency.

[0394] Example 2. See Figure 9, which is a flowchart of another location management method provided in an embodiment of the present application. In this example, the first core network device takes AMF or TMF (denoted as AMF / TMF) as an example, the second core network device takes UDM or UDR (denoted as UDM / UDR) as an example, the first service requester takes AF as an example, and the terminal device takes a tag as an example.

[0395] S900: Tag initialization process.

[0396] For the specific implementation, please refer to S800 and will not be described in detail here.

[0397] S901. The AF instructs the core network to perform location management.

[0398] Here are two ways:

[0399] Method 1: AF updates the contract data to UDM through NEF, and instructs AMF / TMF to perform location management on the tag through the contract data.

[0400] Exemplary:

[0401] S901A-1, AMF / TMF can send a UDM subscription request message to subscribe to notifications of contract data updates from UDM, so that when the contract data corresponding to the tag and / or AF in the UDM / UDR is updated, the UDM / UDR can send a notification of contract data changes to AMF / TMF, which carries the changed contract data.

[0402] S901A-2. The AF may send a parameter provision message to the UDM / UDR through the NEF. The message carries indication information (equivalent to the second information mentioned above). The indication information indicates to perform location management on the terminal device (including the tag) belonging to the AF.

[0403] Optionally, the message may also include: one or more terminal identifiers (including the identifier of the tag), and / or location information. When the message includes one or more terminal identifiers, the indication information may simultaneously indicate that location management is to be performed on the one or more terminal devices (equivalent to the first information mentioned above). When the message includes location information (equivalent to the second location information mentioned above), it may indicate that location management is to be performed on the terminal devices located in the range corresponding to the location information. When the message includes a terminal identifier and location information, it may indicate that location management is to be performed on the one or more terminal devices in the range corresponding to the location information.

[0404] S901A-3. UDM / UDR updates the message tag and / or the contract data corresponding to AF according to the parameters, and sends a notification of the contract data change to AMF / TMF, which carries the changed contract data.

[0405] Mode 2: S901B and AF instruct to perform location management on the tag by issuing instructions or subscribing to a location management service (or called a location tracking service, or other names).

[0406] In one possible implementation, the AF sends a request message (such as an instruction message or a subscription location tracking service message or a subscription location management service request message, etc.) to the AMF / TMF through the NEF. Figure 9 takes the service subscription request message as an example.

[0407] The message may include a terminal identifier, instruction information (instructing execution of location management, equivalent to the first information above), location information (optionally, the location information may be a preset route), and an AF identifier. Optionally, the message may also include time information.

[0408] The terminal identifier indicates the terminal identifier of the terminal on which the operation needs to be executed. The location information indicates the location range where the instruction is to be executed.

[0409] In one possible implementation, the location information also indicates the location range for performing location management (equivalent to the second location information above), or the location information (such as a preset route) indicates a predetermined route trajectory for the tag movement (equivalent to the preset route above).

[0410] In one possible implementation, the location information may be one or more of geographic location information (such as coordinate values, longitude and latitude, etc.), network identifier, TAI, cell identifier, CAG identifier, reader identifier, access network device identifier, user equipment identifier, etc.

[0411] In one possible implementation, the location information may include a target location, indicating a location that the tag needs to reach.

[0412] In a possible implementation, the time information may include one or more of a start time, a duration, and an end time, indicating the execution of location management or a time period for location management (equivalent to the first time information mentioned above).

[0413] In a possible implementation, the time information further includes information indicating the time of arrival at the target location (equivalent to the second time information mentioned above).

[0414] S902. AMF / TMF instructs the current reader / writer of the tag (such as reader / writer 1) to execute a random access process.

[0415] For the specific implementation, please refer to S802 and will not be described in detail here.

[0416] S903: The reader interacts with the tag to complete the random access process.

[0417] For the specific implementation, please refer to S803 and will not be described in detail here.

[0418] S904: When random access is successful, the tag can send the tag identification to the AMF / TMF through the reader.

[0419] The specific implementation of step S904 may refer to S804 or S401 and will not be repeated here.

[0420] S905: For specific implementation, please refer to S805 and will not be described in detail here.

[0421] S906A. AMF / TMF determines to perform location management based on the information provided by AF.

[0422] The specific implementation of step S906A can refer to the above S402. For example:

[0423] In one possible implementation, when AF updates the contract data of the tag or the contract data corresponding to AF (or the service configuration information corresponding to the passive Internet of Things service) to UDM through NEF, UDM will send the updated contract data (or the service configuration information corresponding to the passive Internet of Things service) to AMF / TMF (such as step S901A-3), and then AMF / TM can determine to perform location management on the tag based on the updated contract data (or service configuration information) sent by UDM.

[0424] In another possible implementation, when AF subscribes to the location tracking service for the tag to AMF / TMF (such as step S901B, AF sends a service subscription request message to AMF / TMF), AMF / TMF can determine to perform location management on the tag based on the information carried in the service subscription request message sent by AF (such as the tag identifier, AF identifier, indication information or location information, etc.).

[0425] Optionally, when the information provided by AF also includes time information for indicating the time period for performing location management, AMF / TMF can determine whether the current time falls within the time range indicated by the time information, thereby determining whether to start or continue to perform location management on the tag.

[0426] Optionally, when the information provided by AF includes location information, AMF / TMF can determine whether the tag is located in the area indicated by the location information, thereby determining whether to perform location management on the tag (such as performing location management on the tag only when the tag is located in the area indicated by the location information).

[0427] Optionally, the AMF / TMF may also determine whether to perform location management on the tag based on the tag's capability information. For example, location management is performed on the tag only when the tag supports location management.

[0428] S906B, AMF / TMF determines TAI based on the location information.

[0429] The specific implementation of step S906B may refer to the above S403. In one possible implementation, the AMF / TMF determines the TAI that needs to be sent to the tag based on the location information provided by the AF.

[0430] S907. When the AMF / TMF determines to perform location management on the tag, it includes information for performing location management (such as TAI) in the message sent to the tag (such as a NAS message or a registration acceptance message).

[0431] The specific implementation of step S907 can refer to the above S404. For example:

[0432] When the AMF / TMF determines that location management is not to be performed on the tag, the AMF / TMF may not send information for performing location management to the tag; alternatively, the AMF / TMF may send a default TAI to the tag, indicating that the tag does not need to perform location management. Specifically, after receiving the default TAI, the tag may determine that it does not need to monitor the TAI broadcast by the reader based on the default TAI, and does not need to perform the mobility registration update process (or tracking area update process).

[0433] Optionally, S908, when the AF does not need to perform location management on the tag, the AF may also instruct the AMF / TMF to stop performing location management on the tag.

[0434] The specific implementation of step S908 can refer to the specific implementation of the first service requester instructing the first core network device to stop performing location management on the first terminal device in the above text. For example, the AF can send a service desubscription request message to the AMF / TMF to instruct the AMF / TMF to stop performing location management on the tag. Alternatively, the AF can update the tag or the contract data corresponding to the AF or update the service configuration information of the passive Internet of Things service to the UDM / UDR, and instruct the AMF / TMF through the updated contract data or service configuration information that there is no need to perform location management on the tag.

[0435] S909: The reader / writer periodically broadcasts the TAI according to the configuration information.

[0436] For specific implementation, please refer to S809 and will not be repeated here.

[0437] S910: When the tag stores a TAI (ie, the TAI is not empty) or the TAI stored in the tag is not the default TAI, and the TAI stored in the tag is different from the TAI in the broadcast message, the tag performs a random access procedure and executes step S911.

[0438] S911. The tag executes a random access procedure.

[0439] S912: When the tag is successfully randomly accessed, the tag sends its identification to the AMF / TMF via the new reader (eg, reader 2). For details, refer to the description of step S812.

[0440] S913: The AMF / TMF determines a new TAI for the tag. Alternatively, the AMF / TMF determines not to perform location management on the tag based on the configuration information or subscription data. For details, refer to the description of step S813.

[0441] S914: AMF / TMF sends an instruction message to the tag, indicating a new TAI, or instructing the tag to remove the TAI previously saved by the tag, or instructing the tag to update the saved TAI to the default TAI. For details, refer to the description of step S814.

[0442] Optionally, S915, AMF / TMF may send a notification message to AF through NEF. The notification message may include the tag identifier, the tag location information, and indication information indicating whether the tag location is normal or abnormal.

[0443] The location information of the tag may be one or more of geographic location information (such as coordinate values, longitude and latitude, etc.), network identification, TAI, cell identification, closed group identification, reader identification, access network device identification, user equipment identification, etc.

[0444] For example, when the information provided by the AF in step S901 includes a preset route, if the tag's location falls within the preset route, the AMF / TMF may send normal indication information to the AF, indicating that the current tag's movement trajectory or location is consistent with the preset route. If the tag's location does not fall within or deviates from the preset route, the AMF / TMF may send abnormal indication information to the AF, indicating that the current tag's movement trajectory or location does not conform to the preset route.

[0445] For example, if the information provided by the AF in S901 includes the target location and the time to arrive at the target location, the AMF / TMF can obtain the system time and the tag's location to determine whether the tag arrived at the target location on time. If the tag does not arrive at the target location on time, the AMF / TMF can send an abnormality indication to the AF, indicating that the tag did not move according to the established route.

[0446] For example, the AMF is also configured with a timer duration (equivalent to the third time information above). When a tag is located in the same location for a long time (e.g., exceeding the timer duration) (e.g., the tag is inventoried by the same reader), an abnormality indication message may be sent to the AF, indicating that the tag location is abnormal. Optionally, the timer duration may be provided by the AF.

[0447] In the above scheme, AF can dynamically instruct the core network to perform location management on the tag through the service interface message, so that the core network performs location management on the tag on demand according to the instruction of AF, instead of performing location management on all terminals at all locations in all time periods, which improves the flexibility of terminal location management and saves costs.

[0448] The following describes the communication device used to implement the above method in the embodiment of the present application with reference to the accompanying drawings. Therefore, the above contents can be used in subsequent embodiments, and repeated contents will not be repeated.

[0449] Figure 10 is a schematic block diagram of a communication device 1000 provided in an embodiment of the present application. The communication device 1000 can implement the functions or steps implemented by any device, network element, terminal or requester in any of the above method embodiments. The communication device may include a processing module 1010 and a transceiver module 1020. Optionally, the communication device 1000 may also include a storage module, which can be used to store instructions (codes or programs) and / or data. The processing module 1010 and the transceiver module 1020 can be coupled with the storage module. For example, the processing module 1010 can read the instructions (codes or programs) and / or data in the storage module to implement the corresponding method. The above-mentioned modules can be set independently or partially or fully integrated.

[0450] It should be understood that the processing module 1010 can be a processor or controller, for example, a general-purpose central processing unit (CPU), a general-purpose processor, a digital signal processing (DSP), an application-specific integrated circuit (ASIC), a field programmable gate array (FPGA) or other programmable logic device, a transistor logic device, a hardware component or any combination thereof. It can implement or execute the various exemplary logic blocks, modules and circuits described in conjunction with the disclosure of this application. The processor can also be a combination that implements computing functions, for example, including a combination of one or more microprocessors, a combination of a DSP and a microprocessor, and so on. The transceiver module 1020 is an interface circuit of the device for receiving signals from other devices. For example, when the device is implemented in the form of a chip, the transceiver module 1020 is an interface circuit of the chip for receiving signals from other chips or devices, or is an interface circuit of the chip for sending signals to other chips or devices.

[0451] As an example, when the communication device 1000 is a first core network device or a component used in a first core network device, the transceiver module 1020 is used to obtain the terminal identification of the first terminal device; the processing module 1010 is used to determine the location management to be performed on the first terminal device based on the terminal identification; determine the area identification set for performing location management; the transceiver module 1020 is also used to send the area identification set to the first terminal device.

[0452] Alternatively, when the communication device 1000 is a first core network device or a component used in a first core network device, the transceiver module 1020 is used to receive a second registration request message from a second terminal device, where the second registration request message includes a terminal identifier of the second terminal device; the processing module 1010 is used to determine not to perform location management on the second terminal device based on the terminal identifier of the second terminal device; the transceiver module 1020 is also used to send a second registration acceptance message to the second terminal device, where the second registration acceptance message indicates that the second terminal device has been successfully registered, and the area identifier in the second registration acceptance message is empty or is a default area identifier.

[0453] As an example, when the communication device 1000 is a first service requester or a component applied to the first service requester, the processing module 1010 is used to determine a second message, the second message includes first information and / or second information, the first information indicates that the first terminal device needs to be location managed, the second information indicates that the first service requester requests location management, and the first service requester is a service requester that manages the first terminal device; the transceiver module 1020 is used to send the second message to the first core network device.

[0454] As an example, when the communication device 1000 is a second terminal device or a component used in a second terminal device, the transceiver module 1020 is used to send a second registration request message to the first core network device, where the second registration request message includes the terminal identifier of the second terminal device; receive a second registration acceptance message from the first core network device, where the second registration acceptance message indicates that the second terminal device is successfully registered, and the area identifier in the second registration acceptance message is empty or is a default area identifier; the processing module 1010 is used to determine that there is no need to monitor the area identifier in the cell broadcast message or there is no need to execute the mobility registration update process based on the locally stored area identifier being empty or being the default area identifier.

[0455] It should be understood that the processing unit 1010 in the embodiment of the present application can be implemented by a processor or a processor-related circuit component, and the transceiver unit 1020 can be implemented by a transceiver or a transceiver-related circuit component or a communication interface.

[0456] It should be understood that all relevant contents of each step involved in the above method embodiment can be referred to the functional description of the corresponding functional module and will not be repeated here.

[0457] Based on the same concept, as shown in FIG11 , an embodiment of the present application provides a communication device 1100. The communication device 1100 includes a processor 1110. Optionally, the communication device 1100 may further include a memory 1120 for storing instructions executed by the processor 1110, or storing input data required by the processor 1110 to execute instructions, or storing data generated after the processor 1110 executes instructions. The processor 1110 can implement the method shown in the above method embodiment using the instructions stored in the memory 1120.

[0458] The memory 1120 may be a storage unit of a chip within the communication device 1100, such as a register, a cache, etc. The storage unit may also be a storage unit within the communication device 1100 that is located outside the chip, such as a read-only memory (ROM) or other types of static storage devices that can store static information and instructions, a random access memory (RAM), etc.

[0459] Optionally, the memory 1120 may be located within or outside the device. The processor 1110 is coupled to the memory 1120. Coupling in the embodiments of the present application refers to an indirect coupling or communication connection between devices, units, or modules, which may be electrical, mechanical, or other forms, and is used for information exchange between devices, units, or modules. The processor 1110 may operate in conjunction with the memory 1120.

[0460] The communication device 1100 may be a chip or a chip system. Optionally, in the embodiment of the present application, the chip system may be composed of a chip, or may include a chip and other discrete devices.

[0461] Based on the above embodiments, referring to FIG12 , an embodiment of the present application also provides another communication device 1200, including: an input / output interface 1210 and a logic circuit 1220; the input / output interface 1210 is used to receive code instructions and transmit them to the logic circuit 1220; the logic circuit 1220 is used to run code instructions to execute the method executed by any device or network element or terminal or requester in any of the above embodiments.

[0462] An embodiment of the present application also provides a computer-readable storage medium, including instructions, which, when executed on a computer, enables the computer to execute a method executed by any device, network element, terminal, or requester in any of the above embodiments.

[0463] An embodiment of the present application also provides a computer program product, including instructions, which, when executed on a computer, enables the computer to execute a method executed by any device, network element, terminal, or requester in any of the above embodiments.

[0464] Those skilled in the art will appreciate that the various illustrative logical blocks and steps described in conjunction with the embodiments disclosed herein can be implemented using electronic hardware, or a combination of computer software and electronic hardware. Whether these functions are implemented in hardware or software depends on the specific application and design constraints of the technical solution. Professionals and technicians may use different methods to implement the described functions for each specific application, but such implementation should not be considered beyond the scope of this application.

[0465] Those skilled in the art will clearly understand that, for the convenience and brevity of description, the specific working processes of the systems, devices and units described above can refer to the corresponding processes in the aforementioned method embodiments and will not be repeated here.

[0466] In the several embodiments provided in this application, it should be understood that the disclosed systems, devices and methods can be implemented in other ways. For example, the device embodiments described above are merely schematic. For example, the division of the units is merely a logical function division. In actual implementation, there may be other division methods, such as multiple units or components can be combined or integrated into another system, or some features can be ignored or not executed. Another point is that the mutual coupling or direct coupling or communication connection shown or discussed can be through some interfaces, indirect coupling or communication connection of devices or units, which can be electrical, mechanical or other forms.

[0467] The units described as separate components may or may not be physically separate, and the components shown as units may or may not be physical units, that is, they may be located in one place or distributed across multiple network units. Some or all of these units may be selected to achieve the purpose of this embodiment according to actual needs.

[0468] If the functions are implemented in the form of software functional units and sold or used as independent products, they can be stored in a computer-readable storage medium. Based on this understanding, the part that essentially contributes to the technical solution of the present application or the part of the technical solution can be embodied in the form of a software product, which is stored in a storage medium and includes several instructions for enabling a computer device (which can be a personal computer, server, or network device, etc.) to execute all or part of the steps of the method described in each embodiment of the present application. The aforementioned storage medium includes various media that can store program codes, such as USB flash drives, mobile hard drives, ROM, RAM, magnetic disks or optical disks.

[0469] Obviously, those skilled in the art may make various changes and modifications to the present application without departing from the scope of the present application. Thus, if these modifications and variations of the present application fall within the scope of the claims of the present application and their equivalents, the present application is intended to include these modifications and variations.

Claims

1. A location management method, characterized in that: Applied to a first core network device, the method includes: Acquire a terminal identification of a first terminal device, and determine to perform location management on the first terminal device according to the terminal identification; Determining a set of area identifiers for performing the location management; The area identifier set is sent to the first terminal device.

2. The method according to claim 1, characterized in that The determining, according to the terminal identifier, to perform location management on the first terminal device includes: Acquire subscription data of the first terminal device from the second core network device according to the terminal identifier, the subscription data including at least one of first information, second information, or capability information of the terminal device, the first information indicating that the first terminal device needs to be managed by the location management, the second information indicating that the first service requester needs the location management, the first service requester is a service requester that manages the first terminal device, and the capability information of the first terminal device indicates that the first terminal device supports the location management; Determine, based on the contract data, to perform location management on the first terminal device.

3. The method according to claim 1, characterized in that The obtaining of the terminal identification of the first terminal device includes: receiving a first message, wherein the first message includes a terminal identifier of the first terminal device and capability information of the first terminal device, wherein the capability information of the first terminal device indicates that the first terminal device supports the location management; The determining, according to the terminal identifier, to perform location management on the first terminal device includes: Acquire subscription data of the first terminal device from the second core network device according to the terminal identifier, the subscription data including first information and / or second information, the first information indicating that the first terminal device needs to be managed by the location, the second information indicating that the first service requester needs the location management, and the first service requester is a service requester that manages the first terminal device; Determine the location management to be performed on the first terminal device according to the subscription data and the capability information of the first terminal device.

4. The method according to claim 1, characterized in that The obtaining of the terminal identification of the first terminal device includes: receiving a first message, wherein the first message includes a terminal identifier of the first terminal device and capability information of the first terminal device, wherein the capability information of the first terminal device indicates that the first terminal device supports the location management; The determining, according to the terminal identifier, to perform location management on the first terminal device includes: Determine, based on the terminal identifier and capability information of the first terminal device, to perform location management on the first terminal device.

5. The method according to claim 3 or 4, characterized in that The first message is a first registration request message; The sending the area identifier set to the first terminal device includes: A first registration acceptance message is sent to the first terminal device, wherein the first registration acceptance message indicates that the first terminal device has been successfully registered, and the first registration acceptance message includes the area identifier set, wherein the area indicated by the area identifier set is the registration area allocated by the first core network device to the first terminal device.

6. The method according to claim 1, characterized in that Before determining to perform location management on the first terminal device according to the terminal identifier, the method further includes: Obtaining information of the local configuration of the first core network device; wherein the information of the local configuration of the first core network device includes at least one of a terminal device list, a service requester list and capability information of the first terminal device, the terminal device list indicates terminal devices for which the location management needs to be performed, the terminal device list includes the terminal identifier of the first terminal device, the service requester list indicates the service requester that needs the location management, the service requester list includes the identifier of the first service requester, the first service requester is the service requester that manages the first terminal device, and the capability information of the first terminal device indicates that the first terminal device supports the location management; The determining, according to the terminal identifier, to perform location management on the first terminal device includes: Determine the location management to be performed on the first terminal device according to the terminal identifier and the local configuration information of the first core network device.

7. The method according to claim 1, characterized in that Before determining to perform location management on the first terminal device according to the terminal identifier, the method further includes: receiving a second message from a first service requester, wherein the second message includes first information and / or second information, the first information indicating that the first terminal device needs to be position managed, the second information indicating that the first service requester requests the position management, and the first service requester is a service requester that manages the first terminal device; The determining, according to the terminal identifier, to perform location management on the first terminal device includes: Determine, according to the terminal identifier, the first information and / or the second information, to perform location management on the first terminal device.

8. The method according to any one of claims 1 to 7, characterized in that The method further comprises: acquiring second location information, where the second location information indicates an area where the location management is performed; The obtaining of the terminal identification of the first terminal device includes: Receiving a terminal identification of the first terminal device from a first access network device; The determining, according to the terminal identifier, to perform location management on the first terminal device further includes: Determine first location information according to the location information of the first access network device, where the first location information indicates an area where the first terminal device is located; It is determined that the first terminal device is located in an area where the location management is performed according to the first location information and the second location information.

9. The method according to any one of claims 1 to 8, characterized in that The method further comprises: Acquire a preset route of the first terminal device; The determining of a set of area identifiers for performing the location management comprises: A set of area identifiers for performing the location management is determined according to an area covering part or all of the preset route, wherein the set of area identifiers includes area identifiers of areas covering part or all of the preset route.

10. The method according to claim 9, characterized in that The method further comprises: Receiving a terminal identification of the first terminal device from a second access network device; Determine the area where the first terminal device is located according to the location information of the second access network device; If the area where the first terminal device is located does not belong to the area of ​​the preset route, determining that the first terminal device deviates from the preset route; Sending third information to the first service requester, wherein the third information indicates that the location of the first terminal device is abnormal, and the first service requester is a service requester that manages the first terminal device.

11. The method according to any one of claims 1 to 10, characterized in that The method further comprises: Acquire first time information, where the first time information indicates a time period for performing the location management; The determining, according to the terminal identifier, to perform location management on the first terminal device further includes: When the current time is within the time period indicated by the first time information, it is determined according to the terminal identifier to perform location management on the first terminal device.

12. The method according to any one of claims 1 to 11, characterized in that The method further comprises: Acquire location information and second time information of a target location, where the second time information indicates the time when the first terminal device arrives at the target location; determining whether the first terminal device arrives at the target location within the time indicated by the second time information; If the first terminal device does not reach the target location within the time indicated by the second time information, fourth information is sent to the first service requester, where the fourth information indicates that the location of the first terminal device is abnormal, and the first service requester is the service requester that manages the first terminal device.

13. The method according to claim 12, characterized in that The determining whether the first terminal device arrives at the target location within the time indicated by the second time information includes: sending a paging message to one or more access network devices within the time indicated by the second time information, the paging message indicating that paging is performed on the first terminal device, the paging message including a terminal identifier of the first terminal device; receiving the terminal identifier of the first terminal device from a third access network device, and determining that the first terminal device is located in an area corresponding to the location information of the third access network device; determining whether the first terminal device arrives at the target location within the time indicated by the second time information based on the location information of the third access network device and the location information of the target location; or, The determining whether the first terminal device arrives at the target location within the time indicated by the second time information includes: sending a paging message to one or more access network devices corresponding to the target location within the time indicated by the second time information, the paging message indicating that paging is performed on the first terminal device, the paging message including a terminal identifier of the first terminal device; determining whether the first terminal device arrives at the target location within the time indicated by the second time information based on whether the terminal identifier of the first terminal device is received from any one of the one or more access network devices corresponding to the target location; or, The area identifier set does not include the area identifier of the area covering the target location; the determining whether the first terminal device arrives at the target location within the time indicated by the second time information includes: receiving the terminal identifier of the first terminal device from a third access network device; determining, based on the location information of the third access network device, that the area where the first terminal device is located is the area covering the target location; and determining, based on the current time and the second time information, whether the first terminal device arrives at the target location within the time indicated by the second time information.

14. The method according to any one of claims 1 to 13, characterized in that The method further comprises: Acquire third time information, where the third time information indicates a preset duration; Determining that the first terminal device is in the same location for more than the preset time period; Fifth information is sent to the first service requester, where the fifth information indicates that the location of the first terminal device is abnormal, and the first service requester is a service requester that manages the first terminal device.

15. The method according to claim 14, characterized in that The determining that the first terminal device is in the same position for more than the preset time period includes: sending a paging message to one or more access network devices, the paging message is used to perform paging on the first terminal device, and the paging message includes a terminal identifier of the first terminal device; if the duration of receiving the terminal identifier of the first terminal device from the same access network device for multiple consecutive times exceeds the preset time period, then determining that the first terminal device is in the same position for more than the preset time period; or, The determining that the first terminal device is in the same location for more than the preset time period includes: periodically sending paging information to one or more access network devices according to the preset time period, the paging information is used to perform paging on the first terminal device, and the paging information includes a terminal identifier of the first terminal device; if the terminal identifier of the first terminal device is received multiple times from the same access network device, it is determined that the first terminal device is in the same location for more than the preset time period; or, The area identifier set includes area identifiers of areas covering part of the preset route; the determination that the first terminal device is in the same location for more than the preset time period includes: if the terminal identifier of the first terminal device is not received from any access network device outside the area represented by the area identifier set for more than the preset time period, then it is determined that the first terminal device is in the same location for more than the preset time period.

16. The method according to claim 7, characterized in that The second message is a service subscription request message, and the service subscription request message instructs the first core network device to provide a location management service for the first terminal device or a terminal device managed by the first service requester.

17. The method according to any one of claims 1 to 16, characterized in that: The method further comprises: Sending charging information corresponding to the location management to the third core network device; The billing information includes at least one of the following: Event type information, indicating the event corresponding to the location management; The number of area identifiers for performing the location management; the duration of performing the location management; the number of times the location management is performed; The number of terminal devices for which the location management is performed.

18. The method according to any one of claims 1 to 17, characterized in that: The method further comprises: receiving a third message from the first service requester, wherein the third message indicates to stop performing the location management on the first terminal device; According to the third message, sixth information and / or seventh information is sent to the first terminal device, the sixth information instructs the first terminal device to remove the area identifier set, and the seventh information indicates that the first terminal device does not need to update the location of the first terminal device to the network.

19. The method according to any one of claims 1 to 18, characterized in that: The method further comprises: receiving a second registration request message from a second terminal device, where the second registration request message includes a terminal identifier of the second terminal device; determining not to perform location management on the second terminal device according to the terminal identification of the second terminal device; A second registration acceptance message is sent to the second terminal device, where the second registration acceptance message indicates that the second terminal device is successfully registered, and the area identifier in the second registration acceptance message is empty or a default area identifier.

20. A location management method, characterized in that: Applicable to the first core network equipment, including: receiving a second registration request message from a second terminal device, where the second registration request message includes a terminal identifier of the second terminal device; determining not to perform location management on the second terminal device according to the terminal identification of the second terminal device; A second registration acceptance message is sent to the second terminal device, where the second registration acceptance message indicates that the second terminal device is successfully registered, and the area identifier in the second registration acceptance message is empty or a default area identifier.

21. A location management method, characterized in that: Applied to a first service requester, the method comprises: Determine a second message, where the second message includes first information and / or second information, where the first information indicates that the first terminal device needs to be managed by the location management, and the second information indicates that the first service requester requests the location management, where the first service requester is a service requester that manages the first terminal device; Send the second message to the first core network device.

22. The method according to claim 21, characterized in that The second message also includes one or more of the following: second location information, the second location information indicating an area where the location management is performed; a preset route of the first terminal device; first time information, the first time information indicating a time period for performing the location management; Location information of a target location and second time information, where the second time information indicates the time when the first terminal device arrives at the target location; The third time information indicates a preset duration.

23. The method of claim 22, wherein: The method further comprises: Receive third information, fourth information or fifth information from the first core network device, and the third information, fourth information or fifth information indicates that the location of the first terminal device is abnormal.

24. The method according to any one of claims 21 to 23, characterized in that The second message is a service subscription request message, and the service subscription request message instructs the first core network device to provide a location management service for the first terminal device or a terminal device managed by the first service requester.

25. The method according to any one of claims 21 to 24, characterized in that The method further comprises: A third message is sent to the first core network device, wherein the third message indicates to stop performing the location management on the first terminal device.

26. A location management method, characterized in that: Applied to a second terminal device, the method includes: Sending a second registration request message to the first core network device, where the second registration request message includes a terminal identifier of the second terminal device; receiving a second registration acceptance message from the first core network device, where the second registration acceptance message indicates that the second terminal device has been successfully registered, and where the area identifier in the second registration acceptance message is empty or a default area identifier; According to the locally stored area identifier being empty or being a default area identifier, it is determined that there is no need to monitor the area identifier in the cell broadcast message or there is no need to perform the mobility registration update procedure.

27. A communication device, characterized in that: Comprising a module for executing the method as claimed in any one of claims 1 to 19, or comprising a module for executing the method as claimed in claim 20, or comprising a module for executing the method as claimed in any one of claims 21 to 25, or comprising a module for executing the method as claimed in claim 26.

28. A communication device, characterized in that: The communication device comprises a processor configured to execute the method according to any one of claims 1 to 19, the method according to claim 20, the method according to any one of claims 21 to 25, or the method according to claim 26.

29. A computer-readable storage medium, characterized in that: The computer-readable storage medium comprises instructions, and when the instructions are executed by a processor, the method according to any one of claims 1 to 19, the method according to claim 20, the method according to any one of claims 21 to 25, or the method according to claim 26 is implemented.

30. A computer program product, characterized in that The computer program product comprises instructions, and when the instructions are executed by a processor, the method according to any one of claims 1 to 19, the method according to claim 20, the method according to any one of claims 21 to 25, or the method according to claim 26 is implemented.

Images