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

Abstract

A method for indicating a tracking area in which a terminal device (120) is located and a network device (110, 1500, 1600, 1700, 1800, 1900, 2000) includes a first network device receiving a tracking area identifier (TAI) of a first tracking area (TA) in which the terminal device (120) is located from a second network device (S310), and sending an indication to the terminal device (120) that the terminal device (120) is in the first TA (S320), thereby enabling the terminal device to clarify the TA in which it is located and ensuring a normal communication process.

Description

Technical Field

[0001] This application relates to the field of communications, and more specifically, to a method for indicating a tracking area where a terminal device is located and a network device.

Background Art

[0002] In satellite networks such as low-Earth orbit (LEO), satellites move relative to the ground, and the beams emitted from the satellites also move 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 cover only one TA at first, then go through the process of covering at least a partial area of two TAs simultaneously and then covering only another TA. In the update mode of the soft tracking area code (Soft TAC), when a satellite covers at least two TAs simultaneously, it broadcasts the TACs corresponding to these TAs simultaneously, so the terminal device will receive at least two TACs simultaneously. In this case, the terminal device cannot know the TA where it is located, which affects the normal communication process.

Summary of the Invention

Problems to be Solved by the Invention

[0003] Embodiments of this application provide a method for indicating a tracking area where a terminal device is located and a network device, which can clarify the TA where the terminal device is located and reduce the adverse impact on the communication process.

Means for Solving the Problems

[0004] Embodiments of this application provide a method for indicating a tracking area where a terminal device is located, which is applied to a first network device, and the method includes: The first network device receives a tracking area identifier (TAI) of a first tracking area (TA) where the terminal device is located from a second network device, and sends an instruction indicating that the terminal device is in the first TA to the terminal device.

[0005] Embodiments of the present application further provide a NAS request processing method applied to a first network device. The method includes: 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, and the first network device accepts the NAS request.

[0006] Embodiments of the present application further provide a method for determining a tracking area where a terminal device is located, which is applied to a second network device. The method includes: In response to a NAS request received from the terminal device, the second network device determines a first TA where the terminal device is located from among tracking areas (TAs) corresponding to at least two tracking area identifiers (TAIs) of the terminal device.

[0007] Embodiments of the present application further provide a method for instructing a tracking area where a terminal device is located, which is applied to a second network device. The method includes: The second network device receives a NAS request from the terminal device, and sends the NAS request and at least two TAIs of the terminal device to the first network device.

[0008] Embodiments of the present application further provide a network device, which includes: a first receiving module configured to receive a TAI of a first TA where the terminal device is located from a second network device, and a first sending module configured to send an instruction indicating that the terminal device is in the first TA to the terminal device.

[0009] Embodiments of the present application further provide a network device, and the network device includes a second receiving module configured to receive a NAS request of a terminal device and at least two TAI of the terminal device from a second network device, and a first processing module configured to accept the NAS request.

[0010] Embodiments of the present application further provide a network device, and the network device includes a determination module configured to determine a first TA where the terminal device is located from among TAs corresponding to at least two TAI of the terminal device in response to a NAS request received from the terminal device.

[0011] Embodiments of the present application further provide a network device, and the network device includes a fourth receiving module configured to receive a NAS request from a terminal device, and a third transmitting module configured to transmit the NAS request and at least two TAI of the terminal device to a first network device.

[0012] Embodiments of the present application further provide a network device including a processor, a memory, and a transceiver. The memory is configured to store a computer program, and the processor calls and executes the computer program stored in the memory to control the transceiver to execute the method according to any one of the above items.

[0013] Embodiments of the present application further provide a chip including a processor that calls and executes a computer program from a memory to cause a device on which the chip is mounted to execute the method according to any one of the above items.

[0014] The embodiments of the present application further provide a computer-readable storage medium storing a computer program, where the computer program causes a computer to execute the method according to any one of the above.

[0015] The embodiments of the present application further provide a computer program product including computer program instructions, where the computer program instructions cause a computer to execute the method according to any one of the above.

[0016] The embodiments of the present application further provide a computer program, where the computer program causes a computer to execute the method according to any one of the above.

[0017] In the embodiments of the present application, the network device instructs the UE of the TA where the UE is located, so that the terminal device can clarify the TA where it is located and perform a normal communication process.

Brief Description of the Drawings

[0018]

Figure 1

Figure 2

Figure 3

Figure 4

Figure 5

Figure 6

Figure 7

Figure 8

Figure 9

Figure 10

Figure 11

Figure 12

Figure 13

Figure 14

Figure 15

Figure 16

Figure 17

Figure 18

Figure 19

Figure 20

Figure 21

Figure 22

DETAILED DESCRIPTION OF THE INVENTION

[0019] Hereinafter, with reference to the drawings of the embodiments of the present application, the technical solutions of the embodiments of the present application will be described.

[0020] In addition, terms such as "first", "second", etc. in the description of the embodiments of the present application, the claims, and the above drawings are not necessarily used to explain a specific order or sequence, but are used to distinguish similar objects. The "first" and "second" objects described simultaneously may be the same or different.

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

[0022] Generally, conventional communication systems have a limited number of connections and are easy to implement. However, with the development of communication technologies, mobile communication systems not only support conventional communications but also support, for example, device-to-device (D2D) communication, machine-to-machine (M2M) communication, machine type communication (MTC), vehicle-to-vehicle (V2V) communication, etc. The embodiments of the present application can also be applied to these communication systems.

[0023] Optionally, the communication system in the embodiments of the present application may be applied to a carrier aggregation (CA) scenario, a dual connectivity (DC) scenario, or a standalone (SA) network distribution scenario.

[0024] The embodiments of the present application do not limit the applicable spectrum. For example, the embodiments of the present application may be applied to licensed spectrum or unlicensed spectrum.

[0025] Embodiments of the present application will describe each embodiment by combining network devices and terminal devices. Here, the terminal device may also be referred to as a user equipment (UE), an access terminal, a user unit, a user station, a mobile station, a mobile station, a remote station, a remote terminal, a mobile device, a user terminal, a terminal, a wireless communication device, a user agent, or a user device, etc. The terminal device may be a station (ST: STAION) in a WLAN, or 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 mobile device with a wireless communication function, a computing device, or other processing devices connected to a wireless modem, an in-vehicle device, a wearable device, and a terminal device in an NR network or a terminal device in a next-generation communication system such as a future-evolved public land mobile network (PLMN).

[0026] Rather than being restrictive, as an example, in the embodiments of the present application, the terminal device may be a wearable device. A wearable device can also be called a wearable smart device, and is a general term for wearable devices developed by applying wearable technology to intelligently design items worn daily, such as glasses, gloves, watches, clothing, shoes, etc. A wearable device is a portable device that is either directly worn on the body or integrated into the user's clothing or accessories. A wearable device is not only a hardware device, but also realizes powerful functions through software support, data interaction, cloud interaction, etc. Broadly speaking, wearable smart devices include smartwatches, smart glasses, etc. that have complete functions, large sizes, and can implement all or part of their functions without relying on smartphones, and various smart bracelets, smart jewelry, etc. that focus only on specific types of application functions and need to be used in cooperation with other devices such as smartphones to monitor physical signs.

[0027] The network device may be a device that communicates with the mobile device, and the network device may be an access point (AP) in a WLAN, a base transceiver station (BTS) in GSM or CDMA, or a base station (NB) in WCDMA, or an evolved base station (eNB or eNodeB) in LTE, or a relay station or access point, or an in-vehicle device, a wearable device, and a network device (gNB) in an NR network or a network device in a future evolved PLMN network, etc.

[0028] In the embodiments of the present application, the network device can provide services to a cell, and the terminal device communicates with the network device via the transmission resources (such as frequency domain resources or frequency spectrum resources) used by the cell. The cell may be a cell corresponding to a network device (such as a base station), or the cell may belong to a base station corresponding to a macro base station or a small cell. Here, the small cell may include a metro cell, a micro cell, a pico cell, a femto cell, etc. These small cells have the characteristics of a small coverage range and low transmission power, and are suitable for providing high-speed data transmission services.

[0029] FIG. 1 exemplarily shows one network device 110 and two terminal devices 120. Optionally, the wireless communication system 100 may include a plurality of network devices 110, and the coverage range of each network device 110 may include other numbers of terminal devices 120, but the embodiments of the present application are not limited thereto. The embodiments of the present application may be applied to one terminal device 120 and one network device 110, or may be applied to one terminal device 120 and another terminal device 120.

[0030] Optionally, the communication system 100 may also include other network entities such as a Mobility Management Entity (MME) and an Access and Mobility Management Function (AMF), but the embodiments of the present application are not limited thereto.

[0031] Note that the terms "system" and "network" in this specification are always used interchangeably herein. The term "and / or" in this specification only describes the associated relationship and indicates that three relationships may exist. For example, A and / or B can indicate three cases: when A exists independently, when both A and B exist, and when B exists independently. Also, the symbol " / " in this specification usually indicates that the relationship between the associated objects is an "or" relationship.

[0032] Note that the "instruction" in the embodiments of this application may be a direct instruction, an indirect instruction, or may be shown as having relevance. For example, A instructing B can mean that A directly instructs B, for example, indicating that B can be obtained by A, or that A indirectly instructs B, for example, A instructs C and B can be obtained through C, or it can also mean that A and B have relevance.

[0033] In the description of the embodiments of this application, the term "corresponding" can represent having a direct or indirect corresponding relationship between the two, can also represent having relevance between the two, and furthermore, can be the relationship of instructing and being instructed, or the relationship of constituting and being constituted.

[0034] To facilitate the understanding of the technical solutions in the embodiments of this application, the related technologies in the embodiments of this application are described below. The following related technologies can be combined with the technical solutions of the embodiments of this application as optional solutions, and all are included in the protection scope of the embodiments of this application.

[0035] Figure 2 exemplarily shows the update mode of Soft TAC in the satellite beam movement scenario. As shown in Figure 2, TA1 and TA2 are areas with fixed geographical positions. During satellite movement, the process goes through covering TA1, then covering a partial area of both TA1 and TA2 simultaneously, and then covering only TA2. In the Soft TAC mode, when the satellite covers TA1 and TA2 simultaneously, in order to broadcast two TACs (including TAC1 and TAC2) simultaneously, the UE receives the two TACs simultaneously. As a result, the UE cannot determine the TA where it is located. For example, when TA1 is within the UE's registration area (RA: Registration Area) and TA2 is not within the UE's registration area, when the UE moves from TA1 to TA2, the UE continues to receive the two TACs, so the UE cannot determine whether it is in TA1 or TA2. Even after the UE registered in TA1 moves to TA2, subsequent non-access stratum (NAS: Non-Access-Stratum) processes such as service request or protocol data unit (PDU: Protocol Data Unit) session establishment are initiated. Furthermore, when the ULI transmitted from the base station to the core network carries two tracking area identifiers (TAI: Tracking area Identity) (each TAI corresponds to one TAC, and the TAI includes the indication of the corresponding TAC and the country of location), the current core network has no corresponding mechanism to handle such a situation.

[0036] The embodiments of the present application provide a method for indicating the tracking area where the terminal device is located. Figure 3 is an exemplary flowchart of a method 300 for indicating the tracking area where the terminal device is located according to the embodiments of the present application. The method can optionally be applied to the system shown in Figure 1 or Figure 2, but is not limited thereto. The method can be applied to the first network device and includes at least a part of the following content.

[0037] In step S310, the first network device receives the Tracking Area Identity (TAI) of the first TA where the terminal device is located from the second network device.

[0038] In step S320, the first network device sends an instruction indicating that the terminal device is in the first TA to the terminal device.

[0039] The above step S320 may include the following.

[0040] If the first TA is an area that allows the start of the terminal device's service and it is determined that the first TA is not within the RA configured by the core network for the terminal device, the first network device sends a configuration update command to the terminal device, and the configuration update command carries an instruction indicating that the terminal device is in the first TA.

[0041] Or, if it is determined that the first TA is a restricted area, the first network device sends a rejection message to the terminal device, and the rejection message carries an instruction indicating that the terminal device is in the first TA.

[0042] Through the above process, the network device instructs the UE of the TA where the UE is located, so that the terminal device can clarify the TA where it is located and perform a normal communication process.

[0043] Here, the above first network device may be a core network device such as an Access and Mobility Management Function (AMF), and the above second network device may be a base station.

[0044] Taking the case where the first network device is an AMF and the second network device is a base station as an example, in the above method, the interaction process between the AMF and the base station may include the following.

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

[0046] 2. If the first TA is an area that allows the start of services of the terminal device and the first TA is not within the RA configured by the core network for the terminal device, the AMF adds the first TA to the RA, feedbacks a configuration update command to the terminal device, and the configuration update command carries an indication indicating that the terminal device is in the first TA.

[0047] 3. If the first TA is a restricted area, the AMF feedbacks a rejection message to the terminal device, and the rejection message carries an indication indicating that the terminal device is in the first TA.

[0048] In the following, taking the case where the first network device is the AMF and the second network device is the base station as an example, specific embodiments will be given to describe the above method in detail.

[0049] Embodiment 1: In this embodiment, after the UE is registered and 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 can know the TA where the UE is located when starting the NAS process through the mapping relationship between the information and the geographical location of the TA (in this embodiment and the following embodiments, the TA where the UE is located is called the first TA). For example, when the terminal device moves from TA1 to TA2, the first TA where it is currently located is TA2, and the base station sends the ULI to the AMF, and the ULI carries the TAI of the first TA (that is, TA2).

[0050] FIG. 4 is a flowchart of the realization of Embodiment 1 of the present application, including the following steps.

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

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

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

[0054] 4. The AMF determines whether TA2 is an area (Allowed Area) that allows the service start of the terminal device, and whether TA2 is within the RA configured by the core network for the terminal device. In this embodiment, assuming that TA2 is an area that allows the service start of the UE and TA2 is not within the UE's RA, TA2 can be added to the UE's RA, and the subsequent NAS process can be continuously executed.

[0055] 5. The AMF sends a configuration update command to the UE. The configuration update command includes an updated TAI list (TAI List), the TAI list includes TA2, and the configuration update command carries an indication indicating that the UE is at TA2. For example, providing a dedicated field in the configuration update command and setting the value of the field to TA2 indicates that the UE is currently at TA2. Optionally, if TA2 has corresponding new slice information, the new slice information is included in the configuration update command and sent to the UE.

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

[0057] 7. Since the AMF providing new slice information does not affect 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 immediately perform the registration process.

[0058] Example 2: Similar to the background of Example 1, the base station has the ability to determine the first TA where the UE is located. The difference from Example 1 is that in this example, the first TA where the UE is located is a restricted area.

[0059] Figure 5 is a flowchart of the implementation of Example 2 of the present application, including the following steps.

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

[0061] 2. Based on the location information of the UE, the base station determines the first TA where the UE is currently located, for example, TA2. Then, if the base station has the ability to determine whether TA2 is a restricted area, it proceeds to steps 3a and 3b; if the base station does not have the ability to determine whether TA2 is a restricted area, it proceeds to steps 4, 5a, and 5b.

[0062] 3a. The base station determines, based on the mobility restriction list previously sent from the core network, that TA2 is a restricted area, and the restricted area includes a non-allowed area or a forbidden area.

[0063] 3b. The base station sends a rejection message to the UE, and the rejection message carries an indication showing that the UE is in TA2. For example, a dedicated field is provided in the rejection message, and setting the value of the field to TA2 indicates that the UE is currently in TA2.

[0064] 4. When 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 (i.e., TA2).

[0065] 5a. When the AMF determines that TA2 is a restricted area, it rejects the NAS process. The restricted area includes a non-allowed area or a forbidden area.

[0066] 5b. The AMF sends a rejection message to the UE, and the rejection message carries an indication indicating that the UE is in TA2. For example, by providing a dedicated field in the rejection message and setting the value of the field to TA2, it indicates that the UE is currently in TA2.

[0067] Corresponding to the above-mentioned Example 1 and Example 2, the present application provides a method for determining the tracking area where the terminal device is located. FIG. 6 is an exemplary flowchart of a method 600 for determining the tracking area where the terminal device is located according to an embodiment of the present application. The method can optionally be applied to the system shown in FIG. 1 or FIG. 2, but is not limited thereto. The method can be applied to a second network device and includes at least a part of the following content.

[0068] In step S610, in response to a NAS request received from the terminal device, the second network device determines a first TA where the terminal device is located from among the tracking areas (TAs) corresponding to at least two tracking area identifiers (TAIs) of the terminal device.

[0069] Furthermore, the second network device can send the TAI of the first TA to the first network device.

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

[0071] Optionally, the above-mentioned second network device can be a base station, and the first network device can be an AMF.

[0072] When the base station has the ability to determine whether the first TA is a restricted area, it further includes the following.

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

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

[0075] Optionally, determining the first TA where the above terminal device is located may include the second network device determining the location where the terminal device is located and determining the first TA where the terminal device is located based on the location.

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

[0077] The embodiments of the present application provide a method for processing NAS requests. FIG. 7 is an exemplary flowchart of a NAS request processing method 700 according to an embodiment of the present application. The method may optionally be applied to the system shown in FIG. 1 or FIG. 2, but is not limited thereto. The method may be applied to the AMF and includes at least a part of the following content.

[0078] In step S710, 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.

[0079] In step S720, the first network device accepts the NAS request.

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

[0081] In this case, since the base station does not have the ability to determine the exact location of the terminal device, all TAI (at least two TAI) of the terminal device are sent to the AMF, and the AMF determines the first TA where the terminal is located.

[0082] The base station can send an N2 message to the AMF, and the N2 message carries at least two TAI of the NAS request of the terminal device. For example, step S710 above includes the first network device receiving an N2 message from the second network device, and the N2 message carries the NAS request and the ULI, and the ULI carries two TAI of the terminal device.

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

[0084] Among the TAI received by the AMF, at least one TA corresponding to the TAI is an area that allows the UE to start services, that is, there are the following two cases.

[0085] Case 1: All TAs corresponding to all TAI received by the AMF are areas that allow the UE to start services. In this case, regardless of which TA the UE is currently in, since all of these TAs are areas that allow the UE to start services, the AMF accepts the NAS request and continues to execute the NAS process.

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

[0087] As described above, in any of the above cases, after receiving the NAS request and at least two TAIs, the AMF first accepts the NAS request, that is, executes step S720 above.

[0088] If all the TAs corresponding to the TAI received by the AMF are areas that allow the terminal device to start 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 the configuration update command sent to the UE carries an indication indicating that the UE is in the first TA.

[0089] If not all the TAs corresponding to the TAI received by the AMF are areas that allow the terminal device to start services, the AMF can determine the first TA where the UE is located. Next, if it is determined that the first TA is an area that allows the terminal device to start services and the first TA is not within the RA configured by the core network for the terminal device, a configuration update is performed on the terminal device. If it is determined that the first TA is a restricted area, the AMF releases the corresponding connection.

[0090] Therefore, after step S720 above, If all the TAs corresponding to the at least two TAIs above are areas that allow the terminal device to start services, the first network device may further include sending a configuration update command to the terminal device.

[0091] Or, after the above step S720, The first network device determines a first TA where the terminal device is located from among the TAs corresponding to the at least two TAI; If the first TA is an area that permits service start of the terminal device and it is determined that the first TA is not within the RA configured by the core network for the terminal device, the first network device may further include sending a configuration update command to the terminal device, where the configuration update command carries an indication indicating that the terminal device is in the first TA.

[0092] This method is applicable when all of the TAs corresponding to the at least two TAI received by the AMF are areas that permit service start of the terminal device, and is also applicable when not all of the TAs corresponding to the at least two TAI are areas that permit service start of the terminal device.

[0093] Or, after the above step S720, The first network device determines a first TA where the terminal device is located from among the TAs corresponding to the at least two TAI; If the first TA is a restricted area, the first network device may further include sending an N2 resource release request to a second network device or sending a connection release request to the terminal device, where the N2 resource release request or the connection release request carries an indication indicating that the terminal device is in the first TA. 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.

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

[0095] In some embodiments, in the above process, the first network device determining the first TA where the terminal device is located is The first network device executes a location service (LCS) process to determine the location of the terminal device, and determines a first TA where the terminal device is located based on the location, including.

[0096] Hereinafter, taking the case where the first network device is an AMF and the second network device is a base station as an example, specific embodiments will be given to describe the above method in detail. In the following embodiments, it is assumed that the UE receives a broadcast message of two TACs including TA1 and TA2.

[0097] Embodiment 3: In this embodiment, the UE starts a NAS request in a connected state such as a PDU session establishment request. Since the base station does not have the ability to determine the exact location of the terminal device, within the ULI of the N2 message, the base station sends both two TAI (for example, TA1, TA2) to the AMF. In this embodiment, it is assumed that the TAs corresponding to the two TAI are both areas that allow the service start of the UE. For example, when the terminal device moves from TA1 to TA2, the first TA where it is currently located is TA2.

[0098] FIG. 8 is a flowchart of the implementation of Embodiment 3 of the present application, including the following steps.

[0099] 1. The UE starts a NAS request message such as a PDU session establishment request in a connected state.

[0100] 2-3. The base station does not have the ability to know the exact location of the UE. The base station sends an N2 message to the AMF. The N2 message carries the ULI, and the ULI carries the NAS request and two TAI of the UE, namely TA1 and TA2.

[0101] 4. The AMF receives the N2 message, accepts the NAS request, and continues to execute the NAS process. Then, the AMF determines whether the two TAs are areas that allow the UE to start services. In this embodiment, since it is assumed that both of the two TAs are areas that allow the UE to start services, in this step, the determination result is that both of the two TAs are areas that allow the UE to start services.

[0102] 5. The AMF sends a configuration update command to the UE. The configuration update command includes the updated TAI List, and the TAI List includes TA2. Optionally, if TA2 has new slice information corresponding thereto, the new slice information is included in the configuration update command and sent to the UE.

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

[0104] 7. Since the AMF providing new slice information does not affect 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 immediately perform the registration process.

[0105] Embodiment 4: This embodiment is the same as the assumption conditions of Embodiment 3.

[0106] FIG. 9 is a flowchart of the implementation of Embodiment 4 of the present application, including the following steps.

[0107] 1. The UE starts a NAS request message such as a PDU session establishment request in the connected state.

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

[0109] 4. The AMF receives the N2 message, accepts the NAS request, continues to execute the NAS process, and determines whether the two TAs are areas that allow the UE to start services. In this embodiment, since it is assumed that both of the two TAs are areas that allow the UE to start services, in this step, the determination result is that both of the two TAs are areas that allow the UE to start services.

[0110] 5. The AMF starts the LCS process to obtain the accurate location information of the UE, and based on the location of the UE, determines the area where the UE is currently located, for example, TA2.

[0111] 6. The AMF sends a configuration update command to the UE. The configuration update command includes the updated TAI List, the TAI List includes TA2, and further includes an indication indicating that the UE is in TA2. For example, setting the value of a dedicated field in the configuration update command to TA2 indicates that the UE is currently in TA2. Optionally, if TA2 has new slice information corresponding thereto, the new slice information is included in the configuration update command and sent to the UE.

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

[0113] 8. Since the AMF providing new slice information does not affect 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 immediately perform the registration process.

[0114] Embodiment 5: In this embodiment, the UE starts a NAS request such as a Service request in the idle state. Since the base station does not have the ability to determine the exact location of the terminal device, within the ULI of the N2 message, the base station sends both two TAls (for example, TA1 and TA2) to the AMF. In this embodiment, it is assumed that both two TAs are areas that allow the service start of the UE. For example, when the terminal device moves from TA1 to TA2, the first TA where it is currently located is TA2.

[0115] FIG. 10 is a flowchart for implementing Embodiment 5 of the present application, and includes the following steps.

[0116] 1. The UE starts a NAS request message such as a Service request in the idle state.

[0117] 2-3. The base station does not have the ability to know the exact location of the UE. The base station sends an N2 message to the AMF. The N2 message carries the ULI, and the ULI carries the NAS request and two TAls of the UE, namely TA1 and TA2.

[0118] 4. The AMF receives the N2 message, accepts the NAS request, continues to execute the NAS process, and the UE enters the connected state. Then, the AMF determines whether both two TAs are areas that allow the service start of the UE. In this embodiment, since it is assumed that both two TAs are areas that allow the service start of the UE, in this step, the determination result is that both two TAs are areas that allow the service start of the UE.

[0119] 5. The AMF sends a configuration update command to the UE. The configuration update command includes an updated TAI List, and the TAI List includes TA2. Optionally, if the new slice information corresponding to TA2 is available, the new slice information is included in the configuration update command and sent to the UE.

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

[0121] 7. Since the provision of new slice information by the AMF does not affect 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 immediately perform the registration process.

[0122] Example 6: This example is the same as the assumption conditions of Example 5.

[0123] FIG. 11 is a flowchart of the implementation of Example 6 of the present application, including the following steps.

[0124] 1. The UE starts a NAS request message such as a Service request in the idle state.

[0125] 2-3. The base station does not have the ability to know the exact location of the UE. The base station sends an N2 message to the AMF. The N2 message carries the ULI, and the ULI carries the NAS request and two TAI of the UE, namely, TA1 and TA2.

[0126] 4. The AMF receives the N2 message, accepts the NAS request, continues to execute the NAS process, and enables the UE to enter the connected state. Then, the AMF determines whether the two TAs are areas that allow the UE to start services. In this example, since it is assumed that both of the two TAs are areas that allow the UE to start services, in this step, the determination result is that both of the two TAs are areas that allow the UE to start services.

[0127] 5. The AMF starts the LCS process to obtain the exact location information of the UE, and based on the location of the UE, determines the area where the UE is currently located, for example, TA2.

[0128] 6. The AMF sends a configuration update command to the UE. The configuration update command includes the updated TAI List, which contains TA2, and further includes an indication indicating that the UE is in TA2. For example, providing a dedicated field in the configuration update command and setting the value of this field to TA2 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 command and sent to the UE.

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

[0130] 8. Since the AMF providing new slice information does not affect 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.

[0131] In the above Examples 3 to 6, the processing method where all the TAs corresponding to the TAI in the broadcast message received by the UE are all areas that allow the UE to start services has been described. Here, two cases where the UE is in the connected state and the idle state are included. In this case, the AMF performs a configuration update for the UE, and the configuration update command can carry an indication indicating that the UE is in the first TA. In the following, the processing method in the case where some of the TAs corresponding to the TAI in the broadcast message received by the UE are areas that allow the UE to start services will be described.

[0132] Example 7: In this example, the UE starts a NAS request in the connected state, such as a PDU session establishment request. Since the base station does not have the ability to determine the exact location of the UE, in the ULI of the N2 message, the base station sends both TAI to the AMF. In this example, it is assumed that TA1 is an area that allows the UE to start services and TA2 is a restricted area. For example, when the terminal device moves from TA1 to TA2, the first TA where it is currently located is TA2.

[0133] Figure 12 is a flowchart for implementing Example 7 of the present application, and includes the following steps.

[0134] 1. The UE starts a NAS request message such as a PDU session establishment request in the connected state.

[0135] 2-3. The base station does not have the ability to know the exact location of the UE. The base station sends an N2 message to the AMF. The N2 message carries the ULI, and the ULI carries the NAS request and two TAI of the UE, namely, TA1 and TA2.

[0136] 4. The AMF receives the N2 message, accepts the NAS request, and continues to execute the NAS process. Then, the AMF determines whether the two TAs are areas that allow the start of services for the UE. In this embodiment, it is assumed that TA2 is a restricted area. Therefore, in this step, the determination result is that TA1 is an area that allows the start of services for the UE, and TA2 is a restricted area.

[0137] 5. The AMF starts an LCS process to obtain the exact location information of the UE, and based on the location of the UE, determines the area where the UE is currently located, for example, TA2.

[0138] 6. Since TA2 is a restricted area, the core network starts a release process for the NAS request corresponding to the UE.

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

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

[0141] Example 8: In this example, the UE initiates NAS requests such as a Service request in the idle state. Since the base station does not have the ability to determine the exact location of the UE, within the ULI of the N2 message, the base station sends both of the two TAI (for example, TA1 and TA2) to the AMF. In this example, assume that TA1 is the area that allows the service start of the UE, and TA2 is the restricted area. For example, when the terminal device moves from TA1 to TA2, the first TA where it is currently located is TA2.

[0142] Figure 13 is a flowchart of the implementation of Example 8 of this application, including the following steps.

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

[0144] 2 - 3. The base station does not have the ability to know the exact location of the UE. The base station sends an N2 message to the AMF. The N2 message carries the ULI, and the ULI carries the NAS request and the two TAI of the UE, namely, TA1 and TA2.

[0145] 4. The AMF receives the N2 message, accepts the NAS request, continues to execute the NAS process, and the UE enters the connected state. Then, the AMF determines whether the two TAs are areas that allow the service start of the UE. In this example, since it is assumed that TA2 is the restricted area, in this step, the determination result is that TA1 is the area that allows the service start of the UE, and TA2 is the restricted area.

[0146] 5. The AMF starts the LCS process to obtain the exact location information of the UE, and based on the location of the UE, determines the area where the UE is currently located, for example, TA2.

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

[0148] In the above embodiments 7 and 8, the processing method in which the TA corresponding to some of the TAI in the broadcast message received by the UE is an area that allows the service start of the UE has been described. Here, two cases where the UE is in the connected state and the idle state are included. In this case, when the AMF receives the N2 message, first, it accepts the NAS request, makes the UE enter the connected state, then starts the LCS process, determines 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 the release request carries an indication indicating that the UE is in the first TA.

[0149] Note that in the above embodiments, only NAS requests such as Service Request and PDU session establishment request are taken as examples, but the method provided by this application is not limited to these two processes. Also, in this application, the case where TA1 and TA2 are included in the broadcast message received by the UE is taken as an example to show the case where the UE receives the TA. However, in this application, the number of TAs received by the UE is not limited, that is, the TAs broadcast by the base station may not be limited to one or two.

[0150] Corresponding to the above embodiments 3 - 8, this application provides a method for determining the tracking area where the terminal device is located. FIG. 14 is an exemplary flowchart of an indication method 1400 for the tracking area where the terminal device is located according to an embodiment of this application. The method can optionally be applied to the system shown in FIG. 1 or FIG. 2, but is not limited thereto. The method can be applied to the second network device and includes at least some of the following content.

[0151] In step S1410, the second network device receives a NAS request from the terminal device.

[0152] In step S1420, the NAS request and at least two TAI of the terminal device are transmitted to the first network device.

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

[0154] In some embodiments, the above method further includes the second network device receiving an N2 resource release request from the first network device, the N2 resource release request carrying an indication indicating that the terminal device is in the first TA, and the first TA corresponding to one of the at least two TAI; and sending a session release request to the terminal device, the session release request carrying an indication indicating that the terminal device is in the first TA.

[0155] Optionally, the transmitting the NAS request and at least two TAI of the terminal device to the first network device includes the second network device sending an N2 message to the first network device, the N2 message carrying the NAS request and the ULI, and the ULI carrying the at least two TAI.

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

[0157] The embodiments of the present application further provide a network device. FIG. 15 is a schematic diagram showing the configuration of a network device 1500 according to an embodiment of the present application. a first receiving module 1510 configured to receive the TAI of the first TA where the terminal device is located from the second network device; A first transmission module 1520 configured to send an instruction indicating that the terminal device is in the first TA to the terminal device.

[0158] Optionally, the first transmission module 1510 described above When it is determined that the first TA is an area that permits the start of the service of the terminal device and the first TA is not within the registration area (RA) constituted by the core network for the terminal device, it is configured to send a configuration update command to the terminal device, and the configuration update command carries an instruction indicating that the terminal device is in the first TA.

[0159] Optionally, the first transmission module 1510 described above When it is determined that the first TA is a restricted area, it is configured to send a rejection message to the terminal device, and the rejection message is configured to carry an instruction indicating that the terminal device is in the first TA.

[0160] Optionally, the restricted area described above includes a non-permitted area or a prohibited area.

[0161] Optionally, the first reception module 1520 described above is configured to receive an N2 message from a second network device, the N2 message carries user location information (ULI), and the ULI carries the TAI of the first TA.

[0162] Optionally, the network device described above includes an access mobility management function (AMF), and the second network device includes a base station.

[0163] Note that the above and other operations and / or functions of the modules in the network device according to the embodiments of the present application respectively implement the processes corresponding to the first network device in method 300 of FIG. 3, and for the sake of brevity, they will not be repeatedly described here.

[0164] An embodiment of the present application further provides a network device. FIG. 16 is a schematic diagram showing the configuration of a network device 1600 according to an embodiment of the present application. A second receiving module 1610 configured to receive a NAS request of a terminal device and at least two TAI of the terminal device from a second network device; A first processing module 1620 configured to accept the NAS request.

[0165] Optionally, the first processing module 1620 is further configured to send a configuration update command to the terminal device when all TAs corresponding to at least two TAI are areas that allow the service start of the terminal device.

[0166] Optionally, the first processing module 1620 further determines a first TA where the terminal device is located from among the TAs corresponding to at least two TAI, and when the first TA is an area that allows the service start of the terminal device and the first TA is determined not to be within the RA configured by the core network for the terminal device, the first processing module 1620 is configured to send a configuration update command to the terminal device, and the configuration update command carries an indication indicating that the terminal device is in the first TA.

[0167] Optionally, the first processing module 1620 further determines a first TA where the terminal device is located from among the TAs corresponding to at least two TAI, and when the first TA is a restricted area, the first processing module 1620 is configured to send an N2 resource release request or a connection release request, and the N2 resource release request or the connection release request carries an indication indicating that the terminal device is in the first TA.

[0168] Optionally, the restricted area includes a non-permitted area or a prohibited area.

[0169] Optionally, the first processing module 1620 executes a positioning service (LCS) process to determine the position of the terminal device, and based on the position, determines the first TA where the terminal device is located.

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

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

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

[0173] Note that the above and other operations and / or functions of the modules in the network device according to the embodiments of the present application respectively implement the corresponding processes of the first network device in the method 700 of FIG. 7, and for the sake of brevity, they will not be repeatedly described here.

[0174] The embodiments of the present application further provide a network device. FIG. 17 is a schematic diagram showing the configuration of a network device 1700 according to the embodiments of the present application. It includes a determination module 1720 configured to determine a first TA where the terminal device is located from among the TAs corresponding to at least two TAI of the terminal device in response to a NAS request received from the terminal device.

[0175] The embodiments of the present application further provide a network device. FIG. 18 is a schematic diagram showing the configuration of a network device 1800 according to the embodiments of the present application, including a determination module 1720. It further includes a second transmission module 1830 configured to transmit the first network device to the TAI of the first TA.

[0176] Optionally, the second transmission module 1830 is configured to transmit an N2 message to the first network device, the N2 message carrying a ULI, and the ULI carrying the TAI of the first TA.

[0177] When the first TA is determined to be a restricted area, the network device 1800 further includes a second processing module 1840 configured to send a rejection message to the terminal device, and the rejection message carries an indication indicating that the terminal device is in the first TA.

[0178] Optionally, the restricted area includes a non-permitted area or a prohibited area.

[0179] Optionally, the determination module 1720 is configured to determine the location where the terminal device is located and, based on the location, determine the first TA where the terminal device is located.

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

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

[0182] Optionally, the first network device includes an AMF.

[0183] Note that the above and other operations and / or functions of the modules in the network device according to the embodiments of the present application respectively implement the corresponding processes of the second network device in the method 600 of FIG. 6, and for the sake of brevity, they will not be repeatedly described here.

[0184] The embodiments of the present application further provide a network device. FIG. 19 is a schematic diagram showing the configuration of a network device 1900 according to the embodiments of the present application. A fourth receiving module 1910 configured to receive a NAS request from a terminal device. A third transmitting module 1920 configured to transmit the NAS request and at least two TAI of the terminal device to a first network device.

[0185] The embodiments of the present application further provide a network device. FIG. 20 is a schematic diagram showing the configuration of a network device 2000 according to an embodiment of the present application, which includes a fourth receiving module 1910 and a third transmitting module 1920. A fifth receiving module 2030 configured to receive an N2 resource release request from a first network device, where the N2 resource release request carries an indication indicating that the terminal device is in a first TA, and the first TA corresponds to one of the at least two TAI above, the fifth receiving module 2030. A fourth transmitting module 2040 configured to transmit a session release request to a terminal device, where the session release request carries an indication indicating that the terminal device is in a first TA, the fourth transmitting module 2040. The network device further includes the fourth transmitting module 2040.

[0186] Optionally, the above third transmitting module 1920 is configured to transmit an N2 message to a first network device, where the N2 message carries a NAS request and a ULI, and the ULI carries at least two TAI.

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

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

[0189] It should be noted that the above and other operations and / or functions of the modules in the network device according to the embodiments of the present application respectively implement the corresponding processes of the second network device in the method 1400 in FIG. 14. For the sake of brevity, they will not be repeatedly described here.

[0190] Note that the functions described for each module (sub-module, unit, or component, etc.) of the network device in the embodiments of the present application may be implemented by different modules (sub-modules, units, or components, etc.), or may be implemented by the same module (sub-module, unit, or component, etc.). For example, the first receiving module and the second receiving module may be different modules, or may be the same module, and both can implement the corresponding functions in the embodiments of the present application. Alternatively, the transmitting module and the receiving module in the embodiments of the present application may be implemented by a transceiver of the device, or a part or all of each of the remaining modules may be implemented by a processor of the device.

[0191] FIG. 21 is a schematic diagram showing the configuration of a communication device 2100 according to an embodiment of the present application. The communication device 2100 shown in FIG. 21 includes a processor 2110, and the processor 2110 can implement the method in the embodiments of the present application by calling and executing a computer program from a memory.

[0192] Optionally, as shown in FIG. 21, the communication device 2100 may further include a memory 2120. Here, the processor 2110 can implement the method in the embodiments of the present application by calling and executing a computer program from the memory 2120.

[0193] Here, the memory 2120 can be a separate device independent of the processor 2110, or can be integrated into the processor 2110.

[0194] Optionally, as shown in FIG. 21, the terminal device 2100 may further include a transceiver 2130, and the processor 2110 can control the transceiver 2130 to communicate with other devices. Specifically, it can transmit information or data to other devices, or receive information or data transmitted by other devices.

[0195] Here, the transceiver 2130 may include a transmitter and a receiver. The transceiver 2130 may further include one or more antennas.

[0196] Optionally, the communication device 2100 may be a terminal device in the embodiments of the present application, or the communication device 2100 can execute the corresponding process realized by the terminal device in each method of the embodiments of the present application, and for the sake of brevity, it will not be repeatedly described here.

[0197] Optionally, the communication device 2100 may be a network device in the embodiments of the present application, or the communication device 2100 can realize the corresponding process realized by the network device in each method in the embodiments of the present application, and for the sake of brevity, it will not be repeatedly described here.

[0198] FIG. 22 is a schematic diagram showing the configuration of the chip 2200 according to the embodiment of the present application. The chip 2200 shown in FIG. 22 includes a processor 2210, and the processor 2210 can realize the method in the embodiment of the present application by calling and executing a computer program from a memory.

[0199] Optionally, as shown in FIG. 22, the chip 2200 may further include a memory 2220. Here, the processor 2210 can realize the method in the embodiment of the present application by calling and executing a computer program from the memory 2220.

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

[0201] Optionally, the chip 2200 may further include an input interface 2230. Here, the processor 2210 can control the input interface 2230 to communicate with other devices or chips. Specifically, the processor 2210 can obtain information or data transmitted by other devices or chips.

[0202] Optionally, the chip 2200 may further include an output interface 2240. Here, the processor 2210 can control the output interface 2240 to communicate with other devices or chips. Specifically, the processor 2210 can output information or data to other devices or chips.

[0203] Optionally, the chip may be applicable to the terminal device in the embodiments of the present application, and the chip can execute the corresponding process realized by the terminal device in each method of the embodiments of the present application. For the sake of brevity, it will not be repeatedly described here.

[0204] Optionally, the chip may be applicable to the network device in the embodiments of the present application, and the chip can execute the corresponding process realized by the terminal device in each method of the embodiments of the present application. For the sake of brevity, it will not be repeatedly described here.

[0205] Note that the chip mentioned in the embodiments of the present application may be called a system-level chip, a system-on-chip, a chip system, or a system-on-a-chip, etc.

[0206] The above-mentioned processor 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. Here, the above-mentioned general-purpose processor may be a microprocessor or any conventional processor.

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

[0208] Note that the above memory is exemplary but not limiting. For example, the memory in the embodiments of the present application may be a static random access memory (SRAM), a dynamic random access memory (DRAM), a synchronous dynamic random access memory (SDRAM), a double data rate synchronous dynamic random access memory (DDR SDRAM), an enhanced synchronous dynamic random access memory (ESDRAM), a synchronous link dynamic random access memory (SLDRAM), or a direct rambus random access memory (DR RAM), etc. That is, the memory in the embodiments of the present application is intended to include these and any other suitable types of memory, but is not limited thereto.

[0209] In the above embodiments, it can be realized in whole or in part by software, hardware, firmware, or any combination thereof. When realized using software, it can be realized 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 loads and executes the computer program instructions, the processes or functions described in the embodiments of the present application are generated in whole or in part. The computer can be a general-purpose computer, a dedicated computer, a computer network, or other programmable devices. The computer instructions may be stored in a computer-readable storage medium, or may be transmitted from one computer-readable storage medium to another computer-readable storage medium. For example, the computer instructions can be transmitted from one website, computer, server, or data center to another website, computer, server, or data center via wired (such as coaxial cable, optical fiber, digital subscriber line (DSL)) or wireless (such as infrared, wireless, microwave, etc.). The computer-readable storage medium can be any available medium accessible by the computer, or a data storage device such as a server or data center integrated by one or more available media. The available medium can be a magnetic medium (such as floppy disk, hard disk, magnetic tape, etc.), an optical medium (such as DVD, etc.), or a semiconductor medium (such as solid state hard disk (SSD), etc.).

[0210] In addition, in each embodiment of the present application, the magnitude of the numbers of the above processes does not mean the order of execution before and after, and the execution order of each process should be determined by its function and internal logic, and should not constitute any limitation to the implementation process of the embodiments of the present application.

[0211] A person skilled in the art can clearly understand that, for the sake of convenience and brevity of description, the specific operation processes of the above systems, devices and units can refer to the corresponding processes in the embodiments of the foregoing methods, and will not be repeatedly described herein.

[0212] The above content is only a specific embodiment of the present application, and the protection scope of the present application is not limited thereto. Any modifications or substitutions that can be easily conceived by a person skilled in the art within the technical scope disclosed in the present application should be included within the protection scope of the present application. Therefore, the protection scope of the present application shall be subject to the protection scope of the claims.

Claims

1. A non-access stratum (NAS) request processing method applied to a first network device, comprising: the first network device receives a NAS request of a terminal device and at least two tracking area identifiers (TAIs) of the terminal device from a second network device, wherein each TAI of the at least two TAIs corresponds to a tracking area code (TAC) related to a satellite; the first network device accepts the NAS request; the first network device determines, from the at least two TAIs, a TAI corresponding to a tracking area (TA) where the terminal device is located; and the first network device includes an access mobility management function (AMF), and the second network device includes a base station, the NAS request processing method.

2. The first network device receiving a NAS request of a terminal device and at least two TAIs of the terminal device from a second network device is: the first network device receiving an N2 message from the second network device, the N2 message carrying the NAS request and user location information (ULI), and the ULI carrying at least two TAIs of the terminal device; The NAS request processing method according to claim 1.

3. A network device, comprising: the network device is a first network device; a second receiving module configured to receive a non-access stratum (NAS) request of a terminal device and at least two tracking area identifiers (TAIs) of the terminal device from a second network device, wherein each TAI of the at least two TAIs corresponds to a tracking area code (TAC) related to a satellite; a first processing module configured to accept the NAS request and determine, from the at least two TAIs, a TAI corresponding to a tracking area (TA) where the terminal device is located; and the first network device includes an access mobility management function (AMF), and the second network device includes a base station, the network device.

4. The second receiving module is configured to receive an N2 message from the second network device, the N2 message carrying the NAS request and user location information (ULI), and the ULI carrying the at least two TAls. The network device according to claim 3.

5. The TA corresponding to any one of the at least two TAls is an area that permits service start of the terminal device, or The TA corresponding to at least one of the at least two TAls is an area that permits service start of the terminal device. The network device according to claim 3.

6. The TA where the terminal device is located is an area that permits service start of the terminal device. The network device according to claim 5.

7. A network device, wherein the network device is a second network device, a fourth receiving module configured to receive a non-access stratum (NAS) request from a terminal device, and a third transmitting module configured to transmit the NAS request and at least two tracking area identifiers (TAls) of the terminal device to a first network device, the first network device being configured to determine, from the at least two TAls, a TAI corresponding to a tracking area (TA) where the terminal device is located, each TAI of the at least two TAls corresponding to a tracking area code (TAC) related to a satellite, the third transmitting module. The first network device includes an access mobility management function (AMF), and the second network device includes a base station, the network device.

8. The third transmitting module is configured to transmit an N2 message to the first network device, the N2 message carrying the NAS request and user location information (ULI), and the ULI carrying the at least two TAls. The network device according to claim 7.

9. The TA corresponding to any one of the at least two TAls is an area that permits service start of the terminal device, or The TA corresponding to at least one of the at least two TAls is an area that permits service start of the terminal device. The network device according to claim 7.

10. The TA where the terminal device is located is an area that permits the start of the service of the terminal device. The network device according to claim 9.

Images