Method and network device for indicating tracking area where terminal device is located

Abstract

A method for indicating the tracking area where a terminal device (120) is located and a network device (110, 1500, 1600, 1700, 1800, 1900, 2000), wherein the method comprises: a first network device receives a tracking area identifier TAI of a first tracking area where a terminal device (120) is located from a second network device (S310); and sends an indication that the terminal device (120) is in the first tracking area to the terminal device (120) (S320). The terminal device (120) can clearly know the tracking area where it is located, thereby ensuring a normal communication process.

Description

[0001] This application is a divisional application of the PCT international patent application PCT / CN2021 / 098501 with an application date of June 5, 2021, which has entered the Chinese national phase and has the Chinese patent application number 202180093780.7 and the invention name “Method and network device for indicating the tracking area where a terminal device is located”. Technical Field

[0002] The present application relates to the field of communications, and more specifically, to a method and a network device for indicating a tracking area where a terminal device is located. Background Art

[0003] In a satellite network, such as a low-Earth Orbit (LEO) satellite, the satellite is moving relative to the ground, and the beam emitted by the satellite is also moving relative to the ground. When the geographical location of the Tracking Area (TA) is fixed, as the satellite moves relative to the ground, the satellite will go through a process from covering only one TA, to covering parts of at least two TAs at the same time, and then to covering only another TA. In the update mode of the Soft Tracking Area Code (Soft TAC), when the satellite covers at least two TAs at the same time, it will simultaneously broadcast the TACs corresponding to these TAs, causing the terminal device to receive at least two TACs at the same time; in this case, the terminal device cannot know the TA it is in, affecting the normal communication process. Summary of the invention

[0004] The embodiments of the present application provide a method and a network device for indicating the tracking area where a terminal device is located, so that the terminal device can clearly know the TA where it is located and reduce the adverse impact on the communication process.

[0005] The embodiment of the present application provides a method for indicating a tracking area where a terminal device is located, which is applied to a first network device and includes:

[0006] The first network device receives a tracking area identifier TAI of a first tracking area TA where the terminal device is located from the second network device;

[0007] An indication that the terminal device is in a first TA is sent to the terminal device.

[0008] The embodiment of the present application further provides a method for processing a NAS request, which is applied to a first network device and includes:

[0009] The first network device receives a NAS request of the terminal device and at least two TAIs of the terminal device from the second network device;

[0010] The first network device accepts the NAS request.

[0011] The embodiment of the present application further provides a method for determining a tracking area where a terminal device is located, which is applied to a second network device and includes:

[0012] In response to receiving a NAS request from the terminal device, the second network device determines a first TA where the terminal device is located from TAs corresponding to at least two TAIs of the terminal device.

[0013] The embodiment of the present application further provides a method for indicating a tracking area where a terminal device is located, which is applied to a second network device and includes:

[0014] The second network device receives a NAS request from the terminal device;

[0015] The NAS request and at least two TAIs of the terminal device are sent to the first network device.

[0016] The present application also provides a network device, including:

[0017] A first receiving module, configured to receive a TAI of a first TA where a terminal device is located from a second network device;

[0018] The first sending module is used to send an indication that the terminal device is in a first TA to the terminal device.

[0019] The present application also provides a network device, including:

[0020] A second receiving module, configured to receive a NAS request of a terminal device and at least two TAIs of the terminal device from a second network device;

[0021] The first processing module is used to accept the NAS request.

[0022] The present application also provides a network device, including:

[0023] The determination module is used to determine, in response to receiving a NAS request from a terminal device, a first TA where the terminal device is located from TAs corresponding to at least two TAIs of the terminal device.

[0024] The present application also provides a network device, including:

[0025] A fourth receiving module, configured to receive a NAS request from a terminal device;

[0026] The third sending module is used to send the NAS request and at least two TAIs of the terminal device to the first network device.

[0027] An embodiment of the present application further proposes a network device, comprising: a processor, a memory and a transceiver, wherein the memory is used to store a computer program, and the processor is used to call and run the computer program stored in the memory, and control the transceiver to execute any of the methods described above.

[0028] An embodiment of the present application further proposes a chip, comprising: a processor, configured to call and run a computer program from a memory, so that a device equipped with the chip executes any of the methods described above.

[0029] The embodiment of the present application further provides a computer-readable storage medium for storing a computer program, wherein the computer program enables a computer to execute any of the methods described above.

[0030] An embodiment of the present application further provides a computer program product, comprising computer program instructions, which enable a computer to execute any of the methods described above.

[0031] The embodiment of the present application also provides a computer program, which enables a computer to execute any of the methods described above.

[0032] In the embodiment of the present application, the network device indicates to the UE the TA in which it is located, so that the terminal device can clearly know the TA in which it is located, thereby carrying out the normal communication process. BRIEF DESCRIPTION OF THE DRAWINGS

[0033] Figure 1 It is a schematic diagram of an application scenario of an embodiment of the present application.

[0034] Figure 2 The figure is a schematic diagram of the update mode of Soft TAC in a satellite beam moving scenario.

[0035] Figure 3 It is a schematic flowchart of a method 300 for indicating a tracking area where a terminal device is located according to an embodiment of the present application.

[0036] Figure 4 This is an implementation flow chart of the first embodiment of the present application.

[0037] Figure 5 This is the implementation flow chart of the second embodiment of the present application.

[0038] Figure 6 It is a schematic flowchart of a method 600 for determining a tracking area where a terminal device is located according to an embodiment of the present application.

[0039] Figure 7 It is a schematic flow chart of a NAS request processing method 700 according to an embodiment of the present application.

[0040] Figure 8 This is the implementation flow chart of Example 3 of the present application.

[0041] Fig. 9 This is the implementation flow chart of the fourth embodiment of the present application.

[0042] Fig.10 This is the implementation flow chart of the fifth embodiment of the present application.

[0043] Fig.11 This is the implementation flow chart of Example 6 of the present application.

[0044] Fig.12 This is the implementation flow chart of Example 7 of the present application.

[0045] Fig.13 This is the implementation flow chart of Example 8 of the present application.

[0046] Fig.14 It is a schematic flowchart of a method 1400 for indicating a tracking area where a terminal device is located according to an embodiment of the present application.

[0047] Fig.15 It is a schematic diagram of the structure of a network device 1500 according to an embodiment of the present application.

[0048] Fig.16 It is a schematic diagram of the structure of a network device 1600 according to an embodiment of the present application.

[0049] Fig.17 It is a schematic diagram of the structure of a network device 1700 according to an embodiment of the present application.

[0050] Fig.18 It is a schematic diagram of the structure of a network device 1800 according to an embodiment of the present application.

[0051] Fig.19 It is a schematic diagram of the structure of a network device 1900 according to an embodiment of the present application.

[0052] Fig. 20 It is a schematic diagram of the structure of a network device 2000 according to an embodiment of the present application.

[0053] Fig.21 It is a schematic structural diagram of a communication device 2100 according to an embodiment of the present application.

[0054] Fig. 22 is a schematic structural diagram of a chip 2200 according to an embodiment of the present application. DETAILED DESCRIPTION

[0055] The technical solutions in the embodiments of the present application will be described below in conjunction with the drawings in the embodiments of the present application.

[0056] It should be noted that the terms "first", "second", etc. in the description and claims of the embodiments of the present application and the above drawings are used to distinguish similar objects, and are not necessarily used to describe a specific order or sequence. The objects described by the "first" and "second" described at the same time may be the same or different.

[0057] The technical solutions of the embodiments of the present application can be applied to various communication systems, such as: Global System of Mobile communication (GSM) system, Code Division Multiple Access (CDMA) system, Wideband Code Division Multiple Access (WCDMA) system, General Packet Radio Service (GPRS), Long Term Evolution (LTE) system, Advanced Long Term Evolution (LTE-A) system, New Radio (NR) system, NR system evolution system, LTE on unlicensed spectrum (LTE-U) system, NR on unlicensed spectrum (NR-based access to unlicensed spectrum, NR-U) system, Universal Mobile Telecommunication System (UMTS), Wireless Local Area Networks (WLAN), Wireless Fidelity (WiFi), 5th-Generation (5G) system or other communication systems.

[0058] Generally speaking, traditional communication systems support a limited number of connections and are easy to implement. However, with the development of communication technology, mobile communication systems will not only support traditional communications, but will also support, for example, device to device (Device to Device, D2D) communication, machine to machine (Machine to Machine, M2M) communication, machine type communication (Machine Type Communication, MTC), and vehicle to vehicle (Vehicle to Vehicle, V2V) communication, etc. The embodiments of the present application can also be applied to these communication systems.

[0059] Optionally, the communication system in the embodiment of the present application can be applied to a carrier aggregation (CA) scenario, a dual connectivity (DC) scenario, or a standalone (SA) networking scenario.

[0060] The embodiments of the present application do not limit the spectrum to which they are applied. For example, the embodiments of the present application can be applied to licensed spectrum or unlicensed spectrum.

[0061] The embodiments of the present application describe various embodiments in combination with network devices and terminal devices, wherein: the terminal device may also be referred to as user equipment (UE), access terminal, user unit, user station, mobile station, mobile station, remote station, remote terminal, mobile device, user terminal, terminal, wireless communication device, user agent or user device, etc. The terminal device may be a station (STAION, ST) in a WLAN, a cellular phone, a cordless phone, a Session Initiation Protocol (SIP) phone, a Wireless Local Loop (WLL) station, a Personal Digital Assistant (PDA) device, a handheld device with wireless communication function, a computing device or other processing device connected to a wireless modem, a vehicle-mounted device, a wearable device, and a next-generation communication system, for example, a terminal device in an NR network or a terminal device in a future evolved Public Land Mobile Network (PLMN) network, etc.

[0062] As an example but not limitation, in the embodiments of the present application, the terminal device may also be a wearable device. Wearable devices may also be referred to as wearable smart devices, which are a general term for wearable devices that are intelligently designed and developed using wearable technology for daily wear, such as glasses, gloves, watches, clothing, and shoes. A wearable device is a portable device that is worn directly on the body or integrated into the user's clothes or accessories. Wearable devices are not only hardware devices, but also powerful functions achieved through software support, data interaction, and cloud interaction. Broadly speaking, wearable smart devices include full-featured, large-sized, and fully or partially independent of smartphones, such as smart watches or smart glasses, as well as devices that only focus on a certain type of application function and need to be used in conjunction with other devices such as smartphones, such as various types of smart bracelets and smart jewelry for vital sign monitoring.

[0063] The network device can be a device used to communicate with a mobile device. The network device can be an access point (AP) in WLAN, a base station (Base Transceiver Station, BTS) in GSM or CDMA, a base station (NodeB, NB) in WCDMA, an evolved base station (Evolutional Node B, eNB or eNodeB) in LTE, or a relay station or access point, or a vehicle-mounted device, a wearable device, a network device (gNB) in an NR network, or a network device in a future evolved PLMN network, etc.

[0064] In an embodiment of the present application, a network device provides services for a cell, and a terminal device communicates with the network device through transmission resources (e.g., frequency domain resources, or spectrum resources) used by the cell. The cell may be a cell corresponding to a network device (e.g., a base station). The cell may belong to a macro base station or a base station corresponding to a small cell. The small cells here may include: a metro cell, a micro cell, a picocell, a femtocell, etc. These small cells have the characteristics of small coverage and low transmission power, and are suitable for providing high-speed data transmission services.

[0065] Figure 1 An exemplary network device 110 and two terminal devices 120 are shown. Optionally, the wireless communication system 100 may include multiple network devices 110, and each network device 110 may include other number of terminal devices 120 within its coverage area, which is not limited in the present embodiment. The present embodiment may be applied to one terminal device 120 and one network device 110, or to one terminal device 120 and another terminal device 120.

[0066] Optionally, the wireless communication system 100 may also include other network entities such as a mobility management entity (Mobility Management Entity, MME), an access and mobility management function (Access and Mobility Management Function, AMF), etc., which is not limited in the embodiments of the present application.

[0067] It should be understood that the terms "system" and "network" are often used interchangeably in this article. The term "and / or" in this article is only a description of the association relationship of associated objects, indicating that three relationships can exist. For example, A and / or B can represent: A exists alone, A and B exist at the same time, and B exists alone. In addition, the character " / " in this article generally indicates that the associated objects before and after are in an "or" relationship.

[0068] It should be understood that the "indication" mentioned in the embodiments of the present application can be a direct indication, an indirect indication, or an indication of an association relationship. For example, A indicates B, which can mean that A directly indicates B, for example, B can be obtained through A; it can also mean that A indirectly indicates B, for example, A indicates C, and B can be obtained through C; it can also mean that there is an association relationship between A and B.

[0069] In the description of the embodiments of the present application, the term "corresponding" may indicate a direct or indirect correspondence between two items, or an association relationship between the two items, or a relationship between indication and being indicated, configuration and being configured, and the like.

[0070] To facilitate understanding of the technical solutions of the embodiments of the present application, the relevant technologies of the embodiments of the present application are described below. The following related technologies can be arbitrarily combined with the technical solutions of the embodiments of the present application as optional solutions, and they all belong to the protection scope of the embodiments of the present application.

[0071] Figure 2 The following is an exemplary diagram showing a Soft TAC update mode in a satellite beam moving scenario. Figure 2As shown, TA1 and TA2 are areas with fixed geographical locations. During the movement of the satellite, it starts from covering TA1, then covers part of TA1 and TA2 at the same time, and then covers only TA2. In the Soft TAC mode, when the satellite covers TA1 and TA2 at the same time, it will broadcast two TACs (including TAC 1 and TAC 2) at the same time. Therefore, the UE will receive two TACs at the same time, causing the UE to be unable to determine the TA it is in. For example, when TA1 is in the UE's registration area (RA) and TA2 is not in the UE's registration area, when the UE moves from TA1 to TA2, since the UE has been receiving two TACs, the UE cannot determine whether it is currently in TA1 or TA2. After the UE registered in TA1 moves to TA2, it will still initiate subsequent non-access stratum (NAS) processes such as service request (ServiceRequest) or protocol data unit (PDU) session establishment. In addition, if the ULI sent by the base station to the core network carries two tracking area identities (TAIs) (each TAI corresponds to a TAC, and the TAI includes the corresponding TAC and an indication of the country in which it is located), the core network currently has no corresponding mechanism to handle this situation.

[0072] The present application embodiment provides a method for indicating the tracking area where a terminal device is located. Figure 3 is a schematic flow chart of a method 300 for indicating a tracking area where a terminal device is located according to an embodiment of the present application. The method can optionally be applied to Figure 1 or Figure 2 The system shown in the figure is not limited thereto. The method can be applied to a first network device, and includes at least part of the following contents.

[0073] S310: The first network device receives the TAI of the first TA where the terminal device is located from the second network device;

[0074] S320: Send an indication that the terminal device is in the first TA to the terminal device.

[0075] The above step S320 may include:

[0076] When it is determined that the first TA is an area that allows the terminal device to initiate services and the first TA is not in the RA configured by the core network for the terminal device, the first network device sends a configuration update instruction to the terminal device and carries an indication that the terminal device is in the first TA in the configuration update instruction.

[0077] Alternatively, when it is determined that the first TA is a restricted area, the first network device sends a rejection message to the terminal device, and carries an indication of the first TA of the terminal device in the rejection message.

[0078] Through the above process, the network device indicates to the UE the TA in which it is located, so that the terminal device can clearly know the TA in which it is located, thereby carrying out the normal communication process.

[0079] Among them, the above-mentioned first network device can be a core network device, such as an access and mobility management function (AMF); the above-mentioned second network device can be a base station.

[0080] Taking the first network device as AMF and the second network device as a base station as an example, in the above method, the interaction process between the AMF and the base station may include:

[0081] 1. The base station receives the NAS request from the terminal device, determines the first TA where the terminal device is located, and sends the TAI of the first TA to the AMF.

[0082] 2. If the first TA is an area where the terminal device is allowed to initiate services, and the first TA is not in the RA configured for the terminal device in the core network, the AMF adds the first TA to the RA and feeds back a configuration update instruction to the terminal device, which carries an indication that the terminal device is in the first TA.

[0083] 3. If the first TA is a restricted area, the AMF feeds back a rejection message to the terminal device, which carries an indication that the terminal device is in the first TA.

[0084] The following takes the first network device as AMF and the second network device as a base station as an example to introduce the above method in detail with a specific embodiment.

[0085] Embodiment 1:

[0086] In this embodiment, after the UE is registered, a secure connection is established. The base station can know the accurate location of the UE through UE location measurement or information such as the Global Navigation Satellite System (GNSS), and know the TA where the UE is located when initiating the NAS process through the mapping relationship with the TA's geographical location (in this embodiment and the following embodiments, the TA where the UE is located is referred to as the first TA). For example, when the terminal device moves from TA1 to TA2, the current first TA is TA2; the base station sends a ULI to the AMF, and carries the TAI of the first TA (i.e., TA2) in the ULI.

[0087] Figure 4This is a flowchart of the implementation of the first embodiment of the present application, including the following steps:

[0088] 1. The UE sends a NAS message such as a Service request or a PDU session establishment request to the base station.

[0089] 2. The base station determines the first TA where the UE is currently located based on the UE location information.

[0090] 3. The base station sends an N2 message to the AMF. The N2 message carries the ULI, and the ULI carries the TAI of the first TA where the UE is currently located (such as TA2).

[0091] 4. AMF determines whether TA2 is an area (Allowed Area) where the terminal device is allowed to initiate services, and whether TA2 is in the RA configured by the core network for the terminal device. In this embodiment, assuming that TA2 is an area where the UE is allowed to initiate services and TA2 is not in the RA of the UE, TA2 can be added to the RA of the UE and the subsequent NAS process can be continued.

[0092] 5. AMF sends a configuration update instruction to the UE, which includes an updated TAI list (TAI List), which contains TA2; and the configuration update instruction carries an indication that the UE is in TA2. For example, a dedicated field is set in the configuration update instruction, and the value of the field is set to TA2, which indicates that the UE is currently in TA2. Optionally, if TA2 has corresponding new slice information, the new slice information is included in the configuration update instruction and sent to the UE.

[0093] 6. After receiving the configuration update instruction, the UE needs to respond and send a configuration update completion message to the AMF.

[0094] 7. Since the AMF provides a new slice information without affecting the existing slice connection, the AMF does not need to release the NAS signaling connection after receiving the response, and the UE does not need to perform the registration process immediately.

[0095] Embodiment 2:

[0096] The background is the same as that of the first embodiment, and the base station is capable of determining the first TA where the UE is located. The difference from the first embodiment is that in this embodiment, it is assumed that the first TA where the UE is located is a restricted area.

[0097] Figure 5 This is a flowchart of the implementation of the second embodiment of the present application, including the following steps:

[0098] 1. The UE sends a NAS message such as a service request or a PDU session establishment request to the base station.

[0099] 2. The base station determines the first TA, such as TA2, where the UE is currently located based on the UE location information. Afterwards, if the base station is capable of determining whether TA2 is a restricted area, steps 3a and 3b are continued; if the base station is not capable of determining whether TA2 is a restricted area, steps 4, 5a and 5b are continued.

[0100] 3a. The base station determines that TA2 is a restricted area, including a non-allowed area or a forbidden area, through the mobility restriction list previously sent by the core network.

[0101] 3b. The base station sends a rejection message to the UE, and the rejection message carries an indication that the UE is in TA2. For example, a dedicated field is set in the rejection message, and the value of the field is set to TA2, indicating that the UE is currently in TA2.

[0102] 4. If the base station cannot determine whether TA2 is a restricted area, it sends an N2 message to the AMF. The N2 message carries the ULI, and the ULI carries the TAI of the first TA where the UE is currently located (ie, TA2).

[0103] 5a. If AMF determines that TA2 is a restricted area, including a non-allowed area or a forbidden area, the NAS process is rejected.

[0104] 5b. AMF sends a rejection message to the UE, and the rejection message carries an indication that the UE is in TA2. For example, a dedicated field is set in the rejection message, and the value of the field is set to TA2, indicating that the UE is currently in TA2.

[0105] Corresponding to the above-mentioned embodiment 1 and embodiment 2, the present application proposes a method for determining the tracking area where the terminal device is located. Figure 6 is a schematic flow chart of a method 600 for determining a tracking area where a terminal device is located according to an embodiment of the present application. The method may optionally be applied to Figure 1 or Figure 2 The system shown in the figure is not limited thereto. The method can be applied to the second network device, including at least part of the following contents. Including:

[0106] S610: In response to receiving a NAS request from a terminal device, the second network device determines a first TA where the terminal device is located from TAs corresponding to at least two TAIs of the terminal device.

[0107] Further, the second network device may send the TAI of the first TA to the first network device.

[0108] For example, the second network device sends an N2 message to the first network device, the N2 message carries a ULI, and the ULI carries the TAI of the first TA.

[0109] Optionally, the second network device may be a base station, and the first network device may be an AMF.

[0110] If the base station is capable of determining whether the first TA is a restricted area, the method may further include:

[0111] When it is determined that the first TA is a restricted area, the second network device (i.e., the base station) sends a rejection message to the terminal device, and carries an indication that the terminal device is in the first TA in the rejection message. For example, a dedicated field is set in the rejection message, and the value of the field is set to the TAI of the first TA, which is used to indicate that the UE is currently in the first TA.

[0112] Optionally, the restricted area includes a non-allowed area or a forbidden area.

[0113] Optionally, the determining the first TA where the terminal device is located may include:

[0114] The second network device determines the location of the terminal device;

[0115] The first TA where the terminal device is located is determined according to the position.

[0116] The above NAS request may include a Service request or a PDU session establishment request, etc.

[0117] This application embodiment proposes a NAS request processing method. Figure 7 is a schematic flow chart of a NAS request processing method 700 according to an embodiment of the present application, which method can optionally be applied to Figure 1 or Figure 2 The system shown is, but not limited to, the method can be applied to AMF, including at least part of the following.

[0118] S710: The first network device receives a NAS request of a terminal device and at least two TAIs of the terminal device from a second network device;

[0119] S720: The first network device accepts the NAS request.

[0120] Optionally, the first network device includes an AMF, and the second network device includes a base station.

[0121] In this case, the base station is unable to determine the exact location of the terminal device, so all TAIs (at least two TAIs) of the terminal device are sent to the AMF, and the AMF determines the first TA where the terminal is located.

[0122] The base station may send an N2 message to the AMF, and carry at least two TAIs requested by the terminal device NAS in the N2 message. For example, the above step S710 includes: the first network device receives an N2 message from the second network device, the N2 message carries the NAS request and the ULI, and the ULI carries two TAIs of the terminal device.

[0123] Before the above step S710, the base station receives a NAS request from the UE. For example, the base station receives a NAS request sent by a UE in a connected state, such as a PDU session establishment request; or the base station receives a NAS request sent by a UE in an idle state, such as a service request.

[0124] Among the TAIs received by the AMF, at least one TA corresponding to the TAI is an area where the UE is allowed to initiate services, that is, there are the following two situations:

[0125] Case 1: All TAs corresponding to the TAIs received by AMF are areas where the UE is allowed to initiate services. In this case, no matter which TA the UE is currently in, the TA is an area where the UE is allowed to initiate services, so AMF accepts the NAS request and continues to execute the NAS process.

[0126] Case 2: Among the TAs corresponding to the TAI received by AMF, some are areas where the UE is allowed to initiate services, and the other part is a restricted area. In this case, the TA where the UE is currently located may be an area where the UE is allowed to initiate services, or it may be a restricted area. In either case, AMF first assumes that the TA where the UE is currently located is an area where the UE is allowed to initiate services, and accepts the NAS request and continues to execute the NAS process; after determining the first TA where the UE is currently located, if the first TA is a restricted area, AMF releases the corresponding connection.

[0127] It can be seen from the above that no matter which of the above situations is the case, after AMF receives the NAS request and at least two TAIs, it first accepts the NAS request, that is, executes the above step S720.

[0128] If the TAs corresponding to the TAIs received by the AMF are all areas where the terminal device is allowed to initiate services, the AMF can complete the configuration update of the UE. Furthermore, the AMF can also determine the first TA where the UE is located, and carry an indication that the UE is in the first TA in the configuration update instruction sent to the UE.

[0129] If the TAs corresponding to the TAIs received by the AMF are not all areas where the terminal device is allowed to initiate services, the AMF can determine the first TA where the UE is located. Then, if it is determined that the first TA is an area where the terminal device is allowed to initiate services and the first TA is not in the RA configured by the core network for the terminal device, the configuration of the terminal device is updated; if it is determined that the first TA is a restricted area, the AMF releases the corresponding connection.

[0130] Therefore, after the above step S720, the following steps may also be included:

[0131] In the case that the TAs corresponding to the at least two TAIs are areas where the terminal device is allowed to initiate services, the first network device sends a configuration update instruction to the terminal device.

[0132] Alternatively, after the above step S720, the following may also be included:

[0133] The first network device determines a first TA where the terminal device is located from the TAs corresponding to the at least two TAIs;

[0134] When the first TA is an area where the terminal device is allowed to initiate services and the first TA is not in the RA configured by the core network for the terminal device, the first network device sends a configuration update instruction to the terminal device and carries an indication that the terminal device is in the first TA in the configuration update instruction.

[0135] This method is applicable to the situation where the TAs corresponding to at least two TAIs received by AMF are both areas where terminal devices are allowed to initiate services, and it is also applicable to the situation where the TAs corresponding to at least two TAIs are not both areas where terminal devices are allowed to initiate services.

[0136] Alternatively, after the above step S720, the following may also be included:

[0137] The first network device determines a first TA where the terminal device is located from the TAs corresponding to the at least two TAIs;

[0138] In the case where the first TA is a restricted area, the first network device sends an N2 resource release request to the second network device or a connection release request to the terminal device, and carries an indication that the terminal device is in the first TA in the N2 resource release request or the connection release request. For example, the AMF sends an N2 resource release request to the base station, and the AMF sends a connection release request to the UE.

[0139] Optionally, the restricted area includes a non-allowed area or a forbidden area.

[0140] In some implementations, in the above process, the first network device determines the first TA where the terminal device is located, including:

[0141] The first network device executes a location service (LCS) process to determine the location of the terminal device;

[0142] The first TA where the terminal device is located is determined according to the position.

[0143] The following takes the first network device as an AMF and the second network device as a base station as an example to introduce the above method in detail with a specific embodiment. In the following embodiment, it is assumed that the UE receives a broadcast message containing two TACs, including TA1 and TA2.

[0144] Embodiment three:

[0145] In this embodiment, the UE initiates a NAS request in the connected state, such as a PDU session establishment request. The base station is unable to determine the exact location of the UE, so in the ULI of the N2 message, the base station sends both TAIs (e.g., TA1 and TA2) to the AMF. In this embodiment, it is assumed that the TAs corresponding to the two TAIs are areas where the UE is allowed to initiate services. For example, when the terminal device moves from TA1 to TA2, the current first TA is TA2.

[0146] Figure 8 This is a flowchart of the implementation of the third embodiment of the present application, including the following steps:

[0147] 1. The UE initiates a NAS request message in the connected state, such as a PDU session establishment request.

[0148] 2-3. The base station is unable to know the exact location of the UE. The base station sends an N2 message to the AMF. The N2 message carries the ULI. The ULI carries the NAS request and the two TAIs of the UE, namely TA1 and TA2.

[0149] 4. AMF receives the N2 message, accepts the NAS request, and continues the NAS process. In addition, AMF determines whether the two TAs are areas where the UE is allowed to initiate services. Since it is assumed in this embodiment that both TAs are areas where the UE is allowed to initiate services, in this step, the result of the judgment is that both TAs are areas where the UE is allowed to initiate services.

[0150] 5. AMF sends a configuration update instruction to the UE, which includes an updated TAI List, which contains TA2. Optionally, if TA2 has corresponding new slice information, the new slice information is included in the configuration update instruction and sent to the UE.

[0151] 6. After receiving the configuration update instruction, the UE needs to respond and send a configuration update completion message to the AMF.

[0152] 7. Since the AMF provides a new slice information without affecting the existing slice connection, the AMF does not need to release the NAS signaling connection after receiving the response, and the UE does not need to perform the registration process immediately.

[0153] Embodiment 4:

[0154] The assumptions of this embodiment are the same as those of the third embodiment.

[0155] Fig. 9 This is a flowchart of the implementation of the fourth embodiment of the present application, including the following steps:

[0156] 1. The UE initiates a NAS request message in the connected state, such as a PDU session establishment request.

[0157] 2-3. The base station is unable to know the exact location of the UE. The base station sends an N2 message to the AMF. The N2 message carries the ULI. The ULI carries the NAS request and the two TAIs of the UE, namely TA1 and TA2.

[0158] 4. AMF receives the N2 message, accepts the NAS request, and continues the NAS process; and AMF determines whether the two TAs are areas where the UE is allowed to initiate services. Since this embodiment assumes that both TAs are areas where the UE is allowed to initiate services, in this step, the result of the judgment is that both TAs are areas where the UE is allowed to initiate services.

[0159] 5. AMF initiates the LCS process to obtain the accurate location information of the UE, and determines the area where the UE is located at this time, such as TA2, based on the UE's location.

[0160] 6. AMF sends a configuration update instruction to the UE, which includes an updated TAI List, which includes TA2 and an indication that the UE is in TA2. For example, a dedicated field is set in the configuration update instruction, and the value of the field is set to TA2, indicating that the UE is currently in TA2. Optionally, if TA2 has corresponding new slice information, the new slice information is included in the configuration update instruction and sent to the UE.

[0161] 7. After receiving the configuration update instruction, the UE needs to respond and send a configuration update completion message to the AMF.

[0162] 8. Since the AMF provides a new slice information without affecting the existing slice connection, the AMF does not need to release the NAS signaling connection after receiving the response, and the UE does not need to perform the registration process immediately.

[0163] Embodiment five:

[0164] In this embodiment, the UE initiates a NAS request, such as a Service request, in the idle state. The base station is unable to determine the exact location of the UE, so in the ULI of the N2 message, the base station sends both TAIs (e.g., TA1 and TA2) to the AMF. In this embodiment, it is assumed that both TAs are areas where the UE is allowed to initiate services. For example, when the terminal device moves from TA1 to TA2, the current first TA is TA2.

[0165] Fig.10 This is a flowchart of the implementation of the fifth embodiment of the present application, comprising the following steps:

[0166] 1. The UE initiates a NAS request message, such as a Service Request, in the idle state.

[0167] 2-3. The base station is unable to know the exact location of the UE. The base station sends an N2 message to the AMF. The N2 message carries the ULI. The ULI carries the NAS request and the two TAIs of the UE, namely TA1 and TA2.

[0168] 4. AMF receives the N2 message, accepts the NAS request, and continues the NAS process to put the UE into the connected state. In addition, AMF determines whether the two TAs are areas where the UE is allowed to initiate services. Since it is assumed in this embodiment that both TAs are areas where the UE is allowed to initiate services, in this step, the result of the judgment is that both TAs are areas where the UE is allowed to initiate services.

[0169] 5. AMF sends a configuration update instruction to the UE, which includes an updated TAI List, which contains TA2. Optionally, if TA2 has corresponding new slice information, the new slice information is included in the configuration update instruction and sent to the UE.

[0170] 6. After receiving the configuration update instruction, the UE needs to respond and send a configuration update completion message to the AMF.

[0171] 7. Since the AMF provides a new slice information without affecting the existing slice connection, the AMF does not need to release the NAS signaling connection after receiving the response, and the UE does not need to perform the registration process immediately.

[0172] Embodiment six:

[0173] The assumptions of this embodiment are the same as those of the fifth embodiment.

[0174] Fig.11 This is a flowchart of the implementation of the sixth embodiment of the present application, comprising the following steps:

[0175] 1. The UE initiates a NAS request message, such as a Service Request, in the idle state.

[0176] 2-3. The base station is unable to know the exact location of the UE. The base station sends an N2 message to the AMF. The N2 message carries the ULI. The ULI carries the NAS request and the two TAIs of the UE, namely TA1 and TA2.

[0177] 4. AMF receives the N2 message, accepts the NAS request, and continues the NAS process to put the UE into the connected state. In addition, AMF determines whether the two TAs are areas where the UE is allowed to initiate services. Since it is assumed in this embodiment that both TAs are areas where the UE is allowed to initiate services, in this step, the result of the judgment is that both TAs are areas where the UE is allowed to initiate services.

[0178] 5. AMF initiates the LCS process to obtain the accurate location information of the UE, and determines the area where the UE is located at this time, such as TA2, based on the UE's location.

[0179] 6. AMF sends a configuration update instruction to the UE, which includes an updated TAI List, which includes TA2 and an indication that the UE is in TA2. For example, a dedicated field is set in the configuration update instruction, and the value of the field is set to TA2, indicating that the UE is currently in TA2. Optionally, if TA2 has corresponding new slice information, the new slice information is included in the configuration update instruction and sent to the UE.

[0180] 7. After receiving the configuration update instruction, the UE needs to respond and send a configuration update completion message to the AMF.

[0181] 8. Since the AMF provides a new slice information without affecting the existing slice connection, the AMF does not need to release the NAS signaling connection after receiving the response, and the UE does not need to perform the registration process immediately.

[0182] The above embodiments 3 to 6 introduce the processing method when the TAs corresponding to all TAIs in the broadcast message received by the UE are all areas where the UE is allowed to initiate services, including the two cases where the UE is in a connected state and an idle state. In this case, the AMF performs a configuration update on the UE and may carry an indication that the UE is in the first TA in the configuration update instruction. The following describes the processing method when the TAs corresponding to some TAIs in the broadcast message received by the UE are areas where the UE is allowed to initiate services.

[0183] Embodiment seven:

[0184] In this embodiment, the UE initiates a NAS request in the connected state, such as a PDU session establishment request. The base station is unable to determine the exact location of the UE, so in the ULI of the N2 message, the base station sends both TAIs to the AMF. In this embodiment, it is assumed that TA1 is an area where the UE is allowed to initiate services and TA2 is a restricted area. For example, when the terminal device moves from TA1 to TA2, the current first TA is TA2.

[0185] Fig.12 This is a flowchart of the implementation of Embodiment 7 of the present application, comprising the following steps:

[0186] 1. The UE initiates a NAS request message in the connected state, such as a PDU session establishment request.

[0187] 2-3. The base station is unable to know the exact location of the UE. The base station sends an N2 message to the AMF. The N2 message carries the ULI. The ULI carries the NAS request and the two TAIs of the UE, namely TA1 and TA2.

[0188] 4. AMF receives the N2 message, accepts the NAS request, and continues the NAS process. In addition, AMF determines whether the two TAs are areas where the UE is allowed to initiate services. Since TA2 is assumed to be a restricted area in this embodiment, in this step, the result of the judgment is that TA1 is an area where the UE is allowed to initiate services, and TA2 is a restricted area.

[0189] 5. AMF initiates the LCS process to obtain the accurate location information of the UE, and determines the area where the UE is located at this time, such as TA2, based on the UE's location.

[0190] 6. Because TA2 is a restricted area, the core network initiates the release process of the UE corresponding to the NAS request.

[0191] 7. AMF adds an indication that the UE is currently in TA2 in the N2 resource release request message sent to the base station. For example, a dedicated field is set in the N2 resource release request message, and the value of the field is set to TA2, indicating that the UE is currently in TA2.

[0192] 8. The base station adds an indication that the UE is currently in TA2 to the session release request sent to the UE.

[0193] Embodiment eight:

[0194] In this embodiment, the UE initiates a NAS request, such as a Service request, in the idle state. The base station is unable to determine the exact location of the UE, so in the ULI of the N2 message, the base station sends both TAIs (e.g., TA1 and TA2) to the AMF. In this embodiment, it is assumed that TA1 is an area where the UE is allowed to initiate services, and TA2 is a restricted area. For example, when the terminal device moves from TA1 to TA2, the current first TA is TA2.

[0195] Fig.13 This is a flowchart of the implementation of the eighth embodiment of the present application, comprising the following steps:

[0196] 1. The UE initiates a NAS request message, such as a Service Request, in the idle state.

[0197] 2-3. The base station is unable to know the exact location of the UE. The base station sends an N2 message to the AMF. The N2 message carries the ULI. The ULI carries the NAS request and the two TAIs of the UE, namely TA1 and TA2.

[0198] 4. AMF receives the N2 message, accepts the NAS request, and continues the NAS process to put the UE into the connected state. In addition, AMF determines whether the two TAs are areas where the UE is allowed to initiate services. Since TA2 is assumed to be a restricted area in this embodiment, in this step, the result of the judgment is that TA1 is an area where the UE is allowed to initiate services, and TA2 is a restricted area.

[0199] 5. AMF initiates the LCS process to obtain the accurate location information of the UE, and determines the area where the UE is located at this time, such as TA2, based on the UE's location.

[0200] 6. Because TA2 is a restricted area, the core network releases the corresponding connection, sends a connection release request to the UE, and carries an indication that the terminal device is in the first TA in the connection release request. For example, a dedicated field is set in the connection release request, and the value of the field is set to TA2, which indicates that the UE is currently in TA2.

[0201] The above embodiments 7 and 8 introduce the processing method of the TA corresponding to some TAIs in the broadcast message received by the UE as the area where the UE is allowed to initiate services, including the two cases where the UE is in the connected state and the idle state. In this case, when the AMF receives the N2 message, it first accepts the NAS request and puts the UE into the connected state; then initiates the LCS process to determine the TA where the UE is located. If the TA where the UE is located is a restricted area, the AMF releases the corresponding connection and carries an indication that the UE is in the first TA in the release request.

[0202] It should be noted that the above embodiments only use NAS requests such as Service Request and PDU session establishment request as use cases, but the method proposed in this application is not limited to these two processes. In addition, this application takes the broadcast message received by the UE as an example, including TA1 and TA2, to indicate the situation where the UE receives TAI, but this application does not limit the number of TAIs received by the UE, that is, the TAI broadcast by the base station may not be limited to one or two.

[0203] Corresponding to the above-mentioned embodiments 3 to 8, the present application proposes a method for determining the tracking area where the terminal device is located. Fig.14 is a schematic flow chart of a method 1400 for indicating a tracking area where a terminal device is located according to an embodiment of the present application. The method can optionally be applied to Figure 1 or Figure 2 The system shown in the figure is not limited thereto. The method can be applied to the second network device, including at least part of the following contents. Including:

[0204] S1410: The second network device receives a NAS request from the terminal device;

[0205] S1420: Send the NAS request and at least two TAIs of the terminal device to the first network device.

[0206] Optionally, the second network device includes a base station, and the first network device includes an AMF.

[0207] In some embodiments, the above method further comprises:

[0208] The second network device receives an N2 resource release request from the first network device, where the N2 resource release request carries an indication that the terminal device is in a first TA; the first TA corresponds to one of the at least two TAIs;

[0209] A session release request is sent to the terminal device, and the session release request carries an indication that the terminal device is in the first TA.

[0210] Optionally, the sending of the NAS request and at least two TAIs of the terminal device to the first network device includes:

[0211] The second network device sends an N2 message to the first network device. The N2 message carries a NAS request and a ULI. The ULI carries the at least two TAIs.

[0212] Optionally, the NAS request includes a service request or a PDU session establishment request.

[0213] The embodiment of the present application also provides a network device, Fig.151 is a schematic diagram of the structure of a network device 1500 according to an embodiment of the present application, including:

[0214] The first receiving module 1510 is used to receive the TAI of the first TA where the terminal device is located from the second network device;

[0215] The first sending module 1520 is used to send an indication that the terminal device is in the first TA to the terminal device.

[0216] Optionally, the first sending module 1520 is used to:

[0217] When it is determined that the first TA is an area where the terminal device is allowed to initiate services and the first TA is not in the registration area RA configured by the core network for the terminal device, a configuration update instruction is sent to the terminal device, and the configuration update instruction carries an indication that the terminal device is in the first TA.

[0218] Optionally, the first sending module 1520 is used to:

[0219] In the case where it is determined that the first TA is a restricted area, a rejection message is sent to the terminal device, and the rejection message carries an indication that the terminal device is in the first TA.

[0220] Optionally, the above-mentioned restricted area includes a not allowed area or a prohibited area.

[0221] Optionally, the first receiving module 1510 is used to receive an N2 message from the second network device, where the N2 message carries user location information ULI, and the ULI carries the TAI of the first TA.

[0222] Optionally, the above-mentioned network device includes an access and mobility management function AMF, and the second network device includes a base station.

[0223] It should be understood that the above and other operations and / or functions of the modules in the network device according to the embodiment of the present application are respectively to implement Figure 3 The corresponding process of the first network device in the method 300 is not repeated here for the sake of brevity.

[0224] The embodiment of the present application also provides a network device, Fig.16 1 is a schematic diagram of the structure of a network device 1600 according to an embodiment of the present application, including:

[0225] The second receiving module 1610 is configured to receive a NAS request of a terminal device and at least two TAIs of the terminal device from a second network device;

[0226] The first processing module 1620 is used to accept a NAS request.

[0227] Optionally, the first processing module 1620 is further configured to send a configuration update instruction to the terminal device when the TAs corresponding to at least two TAIs are areas where the terminal device is allowed to initiate services.

[0228] Optionally, the first processing module 1620 is also used to determine the first TA where the terminal device is located from the TAs corresponding to the at least two TAIs; when the first TA is an area where the terminal device is allowed to initiate services and the first TA is not in the RA configured by the core network for the terminal device, send a configuration update instruction to the terminal device and carry an indication that the terminal device is in the first TA in the configuration update instruction.

[0229] Optionally, the above-mentioned first processing module 1620 is also used to determine the first TA where the terminal device is located from the TAs corresponding to the at least two TAIs; when the first TA is a restricted area, send an N2 resource release request or a connection release request, and carry an indication that the terminal device is in the first TA in the N2 resource release request or the connection release request.

[0230] Optionally, the above-mentioned restricted area includes a not allowed area or a prohibited area.

[0231] Optionally, the first processing module 1620 is used to execute a location service LCS process to determine the location of the terminal device; and determine the first TA where the terminal device is located according to the location.

[0232] Optionally, the second receiving module 1610 is configured to receive an N2 message from a second network device, where the N2 message carries a NAS request and a ULI, and the ULI carries at least two TAIs.

[0233] Optionally, the above-mentioned network device includes AMF, and the second network device includes a base station.

[0234] The above NAS request includes a service request or a PDU session establishment request.

[0235] It should be understood that the above and other operations and / or functions of the modules in the network device according to the embodiment of the present application are respectively to implement Figure 7 The corresponding process of the first network device in method 700 is not repeated here for the sake of brevity.

[0236] The embodiment of the present application also provides a network device, Fig.17 1700 is a schematic diagram of the structure of a network device according to an embodiment of the present application, including:

[0237] The determination module 1720, in response to receiving a NAS request from the terminal device, determines a first TA where the terminal device is located from TAs corresponding to at least two TAIs of the terminal device.

[0238] The embodiment of the present application also provides a network device, Fig.18 is a schematic diagram of the structure of a network device 1800 according to an embodiment of the present application, including: a determination module 1720;

[0239] The system also includes a second sending module 1830, configured to send the TAI of the first TA to the first network device.

[0240] Optionally, the second sending module 1830 is used to send an N2 message to the first network device, where the N2 message carries a ULI, and the ULI carries the TAI of the first TA.

[0241] It also includes: a second processing module 1840, which is used to send a rejection message to the terminal device when it is determined that the first TA is a restricted area, and carry an indication that the terminal device is in the first TA in the rejection message.

[0242] Optionally, the above-mentioned restricted area includes a not allowed area or a prohibited area.

[0243] Optionally, the above-mentioned determination module 1720 is used to determine the location of the terminal device; and determine the first TA where the terminal device is located according to the location.

[0244] Optionally, the NAS request includes a service request or a PDU session establishment request.

[0245] Optionally, the above network device includes a base station.

[0246] Optionally, the first network device includes AMF.

[0247] It should be understood that the above and other operations and / or functions of the modules in the network device according to the embodiment of the present application are respectively to implement Figure 6 The corresponding process of the second network device in method 600 is not repeated here for the sake of brevity.

[0248] The embodiment of the present application also provides a network device, Fig.19 19 is a schematic diagram of the structure of a network device 1900 according to an embodiment of the present application, including:

[0249] The fourth receiving module 1910 is used to receive a NAS request from a terminal device;

[0250] The third sending module 1920 is used to send the NAS request and at least two TAIs of the terminal device to the first network device.

[0251] The embodiment of the present application also provides a network device, Fig. 20 1 is a schematic diagram of the structure of a network device 2000 according to an embodiment of the present application, including: a fourth receiving module 1910, a third sending module 1920; and further including:

[0252] The fifth receiving module 2030 is configured to receive an N2 resource release request from the first network device, wherein the N2 resource release request carries an indication that the terminal device is in a first TA; wherein the first TA corresponds to one TAI of the at least two TAIs;

[0253] The fourth sending module 2040 is used to send a session release request to the terminal device, and carry an indication that the terminal device is in the first TA in the session release request.

[0254] Optionally, the third sending module 1920 is used to send an N2 message to the first network device, where the N2 message carries a NAS request and a ULI, and the ULI carries at least two TAIs.

[0255] Optionally, the NAS request includes a service request or a PDU session establishment request.

[0256] Optionally, the above-mentioned network device includes a base station, and the first network device includes an AMF.

[0257] It should be understood that the above and other operations and / or functions of the modules in the network device according to the embodiment of the present application are respectively to implement Fig.14 The corresponding process of the second network device in method 1400 is not repeated here for the sake of brevity.

[0258] It should be noted that the functions described in the various modules (submodules, units or components, etc.) in the network device of the embodiment of the present application can be implemented by different modules (submodules, units or components, etc.) or by the same module (submodules, units or components, etc.). For example, the first receiving module and the second receiving module can be different modules or the same module, and both can implement their corresponding functions in the embodiment of the present application. In addition, the sending module and the receiving module in the embodiment of the present application can be implemented by the transceiver of the device, and some or all of the remaining modules can be implemented by the processor of the device.

[0259] Fig.21 It is a schematic structural diagram of a communication device 2100 according to an embodiment of the present application. Fig.21 The communication device 2100 shown includes a processor 2110, and the processor 2110 can call and run a computer program from a memory to implement the method in the embodiment of the present application.

[0260] Alternatively, if Fig.21 As shown, the communication device 2100 may further include a memory 2120. The processor 2110 may call and run a computer program from the memory 2120 to implement the method in the embodiment of the present application.

[0261] The memory 2120 may be a separate device independent of the processor 2110 , or may be integrated into the processor 2110 .

[0262] Alternatively, if Fig.21 As shown, the communication device 2100 may further include a transceiver 2130, and the processor 2110 may control the transceiver 2130 to communicate with other devices, specifically, may send information or data to other devices, or receive information or data sent by other devices.

[0263] The transceiver 2130 may include a transmitter and a receiver. The transceiver 2130 may further include an antenna, and the number of antennas may be one or more.

[0264] Optionally, the communication device 2100 may be a terminal device of an embodiment of the present application, and the communication device 2100 may implement the corresponding processes implemented by the terminal device in each method of the embodiment of the present application, which will not be described again for the sake of brevity.

[0265] Optionally, the communication device 2100 may be a network device of an embodiment of the present application, and the communication device 2100 may implement the corresponding processes implemented by the network device in each method of the embodiment of the present application, which will not be described in detail here for the sake of brevity.

[0266] Fig. 22 is a schematic structural diagram of a chip 2200 according to an embodiment of the present application. Fig. 22 The chip 2200 shown includes a processor 2210, which can call and run a computer program from a memory to implement the method in the embodiment of the present application.

[0267] Alternatively, if Fig. 22 As shown, the chip 2200 may further include a memory 2220. The processor 2210 may call and run a computer program from the memory 2220 to implement the method in the embodiment of the present application.

[0268] The memory 2220 may be a separate device independent of the processor 2210 , or may be integrated into the processor 2210 .

[0269] Optionally, the chip 2200 may further include an input interface 2230. The processor 2210 may control the input interface 2230 to communicate with other devices or chips, and specifically, may obtain information or data sent by other devices or chips.

[0270] Optionally, the chip 2200 may further include an output interface 2240. The processor 2210 may control the output interface 2240 to communicate with other devices or chips, and specifically, may output information or data to other devices or chips.

[0271] Optionally, the chip can be applied to the terminal device in the embodiments of the present application, and the chip can implement the corresponding processes implemented by the terminal device in the various methods of the embodiments of the present application. For the sake of brevity, they will not be repeated here.

[0272] Optionally, the chip can be applied to the network device in the embodiments of the present application, and the chip can implement the corresponding processes implemented by the network device in each method of the embodiments of the present application. For the sake of brevity, they will not be repeated here.

[0273] It should be understood that the chip mentioned in the embodiments of the present application can also be called a system-level chip, a system chip, a chip system or a system-on-chip chip, etc.

[0274] The processor mentioned above may be a general-purpose processor, a digital signal processor (DSP), a field programmable gate array (FPGA), an application specific integrated circuit (ASIC) or other programmable logic devices, transistor logic devices, discrete hardware components, etc. Among them, the general-purpose processor mentioned above may be a microprocessor or any conventional processor, etc.

[0275] The memory mentioned above may be a volatile memory or a non-volatile memory, or may include both volatile and non-volatile memories. Among them, the non-volatile memory may be a read-only memory (ROM), a programmable ROM (PROM), an erasable programmable ROM (EPROM), an electrically erasable programmable ROM (EEPROM) or a flash memory. The volatile memory may be a random access memory (RAM).

[0276] It should be understood that the above-mentioned memory is exemplary but not restrictive. For example, the memory in the embodiments of the present application may also be static random access memory (static RAM, SRAM), dynamic random access memory (dynamic RAM, DRAM), synchronous dynamic random access memory (synchronous DRAM, SDRAM), double data rate synchronous dynamic random access memory (double data rate SDRAM, DDR SDRAM), enhanced synchronous dynamic random access memory (enhanced SDRAM, ESDRAM), synchronous link dynamic random access memory (synch link DRAM, SLDRAM) and direct memory bus random access memory (Direct Rambus RAM, DR RAM), etc. That is to say, the memory in the embodiments of the present application is intended to include but not limited to these and any other suitable types of memory.

[0277] In the above embodiments, it can be implemented in whole or in part by software, hardware, firmware or any combination thereof. When implemented using software, it can be implemented in whole or in part in the form of a computer program product. The computer program product includes one or more computer instructions. When the computer program instruction is loaded and executed on a computer, the process or function described in the embodiment of the present application is generated in whole or in part. The computer can be a general-purpose computer, a special-purpose computer, a computer network or other programmable devices. The computer instruction can be stored in a computer-readable storage medium, or transmitted from one computer-readable storage medium to another computer-readable storage medium, for example, the computer instruction can be transmitted from a website site, computer, server or data center by wired (e.g., coaxial cable, optical fiber, digital subscriber line (Digital Subscriber Line, DSL)) or wireless (e.g., infrared, wireless, microwave, etc.) mode to another website site, computer, server or data center. The computer-readable storage medium can be any available medium that a computer can access or a data storage device such as a server, a data center, etc. that contains one or more available media integrations. The available medium may be a magnetic medium (eg, a floppy disk, a hard disk, a magnetic tape), an optical medium (eg, a DVD), or a semiconductor medium (eg, a solid state disk (SSD)).

[0278] It should be understood that in the various embodiments of the present application, the size of the serial numbers of the above-mentioned processes does not mean the order of execution. The execution order of each process should be determined by its function and internal logic, and should not constitute any limitation on the implementation process of the embodiments of the present application.

[0279] Those skilled in the art can 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.

[0280] The above is only a specific implementation of the present application, but the protection scope of the present application is not limited thereto. Any person skilled in the art who is familiar with the present technical field can easily think of changes or substitutions within the technical scope disclosed in the present application, which should be included in the protection scope of the present application. Therefore, the protection scope of the present application should be based on the protection scope of the claims.

Claims

1. A method for processing a non-access layer NAS request, applied to a first network device, include: The first network device receives a non-access layer NAS request of a terminal device and at least two tracking area identifiers TAI of the terminal device from the second network device; The first network device accepts the NAS request; as well as The first network device determines the TAI corresponding to the tracking area TA where the terminal device is located from the at least two TAIs.

2. The method according to claim 1, It is characterized in that The first network device receives a NAS request of the terminal device and at least two TAIs of the terminal device from the second network device, including: The first network device receives an N2 message from the second network device, wherein the N2 message carries the NAS request and user location information ULI, and the ULI carries at least two TAIs of the terminal device.

3. The method according to claim 1, It is characterized in that One of the at least two TAIs is the TAI corresponding to the TA where the terminal device is located.

4. The method according to claim 1, It is characterized in that The TA corresponding to any one of the at least two TAIs is an area in which the terminal device is allowed to initiate a service; or, The TA corresponding to at least one TAI of the at least two TAIs is an area in which the terminal device is allowed to initiate services.

5. The method according to claim 4, It is characterized in that The TA where the terminal device is located is the area where the first network device allows the terminal device to initiate services.

6. The method according to any one of claims 1 to 5, It is characterized in that The first network device includes an access and mobility management function AMF, and the second network device includes a base station.

7. A method for indicating a tracking area where a terminal device is located, applied to a second network device, include: The second network device receives a non-access layer NAS request from the terminal device; The NAS request and at least two tracking area identifiers TAI of the terminal device are sent to the first network device, so that the first network device determines the TAI corresponding to the tracking area TA where the terminal device is located from the at least two TAIs.

8. The method according to claim 7, It is characterized in that The sending the NAS request and the at least two TAIs of the terminal device to the first network device includes: The second network device sends an N2 message to the first network device, wherein the N2 message carries the NAS request and user location information ULI, and the ULI carries at least two TAIs of the terminal device.

9. The method according to claim 7, It is characterized in that One of the at least two TAIs is the TAI corresponding to the TA where the terminal device is located.

10. The method according to claim 7, It is characterized in that The TA corresponding to any one of the at least two TAIs is an area in which the terminal device is allowed to initiate a service; or, The TA corresponding to at least one TAI of the at least two TAIs is an area in which the terminal device is allowed to initiate services.

11. The method according to claim 10, It is characterized in that The TA where the terminal device is located is the area where the first network device allows the terminal device to initiate services.

12. The method according to any one of claims 7 to 11, in, The second network device includes a base station, and the first network device includes an access and mobility management function AMF.

13. A network device, include: A first receiving module is used to receive a non-access layer NAS request of a terminal device and at least two tracking area identifiers TAI of the terminal device from a second network device; The first processing module is used to accept the non-access layer NAS request and determine the TAI corresponding to the tracking area TA where the terminal device is located from the at least two TAIs.

14. A network device, include: A second receiving module is used to receive a non-access layer NAS request from a terminal device; The first sending module is used to send the NAS request and at least two tracking area identifiers TAI of the terminal device to the first network device, so that the first network device determines the TAI corresponding to the tracking area TA where the terminal device is located from the at least two TAIs.

15. A network device, include: A processor, a memory and a transceiver, wherein the memory is used to store a computer program, and the processor is used to call and run the computer program stored in the memory, and control the transceiver to execute the method as claimed in any one of claims 1 to 6.

16. A network device, include: A processor, a memory and a transceiver, wherein the memory is used to store a computer program, and the processor is used to call and run the computer program stored in the memory, and control the transceiver to execute the method as claimed in any one of claims 7 to 12.

17. A computer-readable storage medium for storing a computer program, wherein the computer program causes a computer to execute the method according to any one of claims 1 to 6, or causes a computer to execute the method according to any one of claims 7 to 12.

Images