A communication method and a communication device

Abstract

The application provides a communication method and a communication device. The method comprises the following steps: receiving first information from a UE, wherein the first information is sent by the UE based on a shutdown procedure; determining a location management network element which subscribes to a location event reported by the UE based on the first information; and sending cancelation of reporting the location event information to the location management network element, wherein the cancelation of reporting the location event information indicates that the UE cancels reporting the location event. Through the method of the application, the core network can be synchronized with the UE state in time, the shutdown time delay of the UE is reduced, and thus the user experience is improved.

Description

Technical Field

[0001] This application relates to the field of wireless communication technology, and more specifically, to a communication method and a communication device. Background Technology

[0002] Before a UE performs a power-off operation, it sends a cancel location reporting event to the core network. The UE then powers off after receiving a response from the core network, thus saving network resources. However, in practical applications, due to various reasons (such as poor network conditions), the core network may fail to receive the cancel location reporting event from the UE, or the UE may fail to receive a response from the core network. This results in the core network being unable to synchronize the UE's state, increasing the UE's power-off latency and reducing the user experience.

[0003] Therefore, there is an urgent need for a solution that enables the core network to synchronize the UE status in a timely manner while reducing the UE shutdown latency. Summary of the Invention

[0004] This application provides a communication method and apparatus that enables the core network to synchronize the UE status in a timely manner while reducing the UE's shutdown latency, thereby improving the user experience.

[0005] Firstly, a method is provided that can be performed by an apparatus (e.g., a communication apparatus). The apparatus can be a device (such as a network device), or it can be a component of a device (e.g., a chip (such as a modem chip, also known as a baseband chip, or a system-on-a-chip (SoC) chip containing a modem core, or a system-in-package (SIP) chip), a chip system, or a circuit), which is not limited in this application. The following description primarily uses an access and mobility management network element as an example.

[0006] The method includes: receiving first information from a terminal device, the first information being sent by the terminal device based on a power-off procedure; determining a location management network element that subscribes to location events reported by the terminal device based on the first information; and sending a cancellation information message to the location management network element, the cancellation information message instructing the terminal device to cancel reporting location events.

[0007] Based on the above scheme, the access and mobility management network element determines the location management network element that the terminal device reports the location event based on the first information. Furthermore, it sends a cancellation information to the location management network element. After sending the first information, the terminal device can enter the power-off state. In this way, the state of the terminal device is synchronized with the core network, while reducing the power-off latency of the terminal device.

[0008] In conjunction with the first aspect, in some implementations of the first aspect, the method further includes: determining the location management network element that subscribes to the location events reported by the terminal device based on the first information and the subscription relationship between the terminal device and the location management network element, wherein the subscription relationship includes the subscription relationship between the terminal device and the location management network element.

[0009] Based on the above scheme, the access and mobility management network element determines the location management network element for the terminal device to report location events based on the first information and the subscription relationship, and sends a cancellation information for reporting location events to the location management network element, thereby reducing the shutdown latency of the terminal device.

[0010] In conjunction with the first aspect, in some implementations of the first aspect, before the access and mobility management network element determines the location management network element that subscribes to the location events reported by the terminal device based on the first information and the subscription relationship between the terminal device and the location management network element, the method further includes: sending a first subscription to the location management network element, the first subscription being used to subscribe to the location events reported by the terminal device subscribed by the location management network element; and receiving a first subscription notification, the first subscription notification including the location events reported by the terminal device subscribed by the location management network element.

[0011] In conjunction with the first aspect, in some implementations of the first aspect, the method further includes: accessing and recording the subscription relationship between the terminal device and the location management network element.

[0012] Based on the above scheme, the access and mobility management network element subscribes to the location management network element for the location events reported by the terminal device. In this way, the access and mobility management network element can obtain the subscription relationship between the terminal device and the location management network element.

[0013] In conjunction with the first aspect, in some implementations of the first aspect, the first information is the registration information; or, the first information is the first cancellation of the reported location event information.

[0014] Based on the above scheme, the terminal device can send the first information to the access and mobility management network element before entering the power-off state, or the terminal device can save the first cancellation of location reporting event information and then enter the power-off state. After the terminal device is powered on, it can send the first information to the access and mobility management network element. In this way, the terminal device's status is synchronized with the core network, while reducing the power-off latency of the terminal device.

[0015] In conjunction with the first aspect, in some implementations of the first aspect, canceling the reporting of location event information includes a first identifier, which is used by the location management network element to determine the reason why the terminal device cancels the reporting of location events.

[0016] Based on the above scheme, the location management network element can determine the reason why the UE initiates the cancellation of location reporting based on the first identifier. This makes the communication process more flexible and efficient. For example, if the location management network element determines that the reason for the terminal device to cancel the location reporting is that it is powered off, the location management network element allows the terminal device to cancel the location reporting.

[0017] In conjunction with the first aspect, in some implementations of the first aspect, Namf_Communication_N1MessageNotify includes canceling the reporting of location event information; in other words, the method for canceling the sending of location event information can reuse protocol TS24.571.

[0018] Secondly, a method is provided that can be performed by an apparatus (e.g., a communication apparatus). This apparatus can be a device (such as a network device), or it can be a component of a device (e.g., a chip (such as a modem chip, also known as a baseband chip, or a SoC chip or SIP chip containing a modem core) or a chip system or circuit), and this application does not limit this. The following description primarily uses an access and mobility management network element as an example.

[0019] The method includes: receiving first information and second information from a terminal device, wherein the first information is sent by the terminal device based on a power-off procedure, and the second information includes a location management network element for reporting location events by the terminal device; and sending a cancellation information for reporting location events to the location management network element based on the first information and the second information, wherein the cancellation information for reporting location events instructs the terminal device to cancel reporting location events.

[0020] Based on the above scheme, the access and mobility management network element can determine the location management network element that has a subscription relationship with the terminal device based on the second information. Then, the access and mobility management network element sends the cancellation of location reporting event information to the location management network element based on the first and second information. After sending the first and second information, the terminal device can enter the power-off state. In this way, the state of the terminal device is synchronized with the core network, while reducing the power-off latency of the terminal device.

[0021] In conjunction with the second aspect, in some implementations of the second aspect, the first information is any one of the following: registration information or first cancellation of location reporting event information.

[0022] In conjunction with the second aspect, in some implementations of the second aspect, the method further includes: canceling the reporting of location event information includes a first identifier, which is used by the location management network element to determine the reason why the terminal device cancels the reporting of location events.

[0023] Thirdly, a method is provided that can be performed by a device (e.g., a communication device). This device can be an apparatus (such as a terminal device), or it can be a component of an apparatus (e.g., a chip (such as a modem chip, also known as a baseband chip, or a system-on-a-chip (SoC) chip containing a modem core, or a system-in-package (SIP) chip), a chip system, or a circuit), which is not limited in this application. The following description primarily uses a terminal device as an example.

[0024] The method includes: sending a cancellation of location event reporting information and a first identifier to a location management network element, wherein the cancellation of location event reporting information instructs the terminal device to cancel the reporting of location events, and the first identifier is used by the location management network element to determine the reason for the terminal device to cancel the reporting of location events; after sending the cancellation of location event reporting information and the first identifier, the terminal device enters a power-off state (or, in response to the completion of sending the cancellation of location event reporting information and the first identifier, the terminal device enters a power-off state).

[0025] Based on the above scheme, when the terminal device sends the information to cancel reporting the location event to the location management network element, it also sends the first identifier. The location management network element can then determine the reason for the terminal device to cancel reporting the location event based on the first identifier. This allows the core network to synchronize the UE status in a timely manner while reducing the UE shutdown latency. For example, if the location management network element determines that the reason for the terminal device to cancel reporting the location event is shutdown based on the reason value, the location management network element allows the terminal device to cancel reporting the location event.

[0026] In conjunction with the first aspect, in some implementations of the first aspect, before the terminal device enters the power-off state, the method further includes: receiving a cancellation of location event reporting response information, wherein the cancellation of location event reporting response information indicates that the terminal device is allowed to cancel reporting location events.

[0027] Based on the above scheme, after receiving the cancellation of location event reporting response information, the terminal device enters the power-off state. The cancellation of location event reporting response information indicates that the terminal device is allowed to cancel reporting location events.

[0028] In conjunction with the first aspect, in some implementations of the first aspect, before the terminal device enters the power-off state, the method further includes: the terminal device entering the power-off state after a first duration; the start time of the first duration is located after the terminal device sends the cancellation of location reporting event information and the first identifier.

[0029] Based on the above scheme, a first duration is set, after which the terminal device can enter the shutdown state. This reduces the shutdown latency of the terminal device. The shutdown of the terminal device after the first duration indicates that the terminal device failed to synchronize its state with the core network. Furthermore, after the terminal device is powered on, it can cancel the reporting of location events to the location management network element.

[0030] Fourthly, a method is provided that can be performed by a device (e.g., a communication device). The device can be a machine (such as a terminal device), or it can be a component of a machine (e.g., a chip (such as a modem chip, also known as a baseband chip, or a SoC chip or SIP chip containing a modem core) or a chip system or circuit), and this application does not limit this. The following description primarily uses a terminal device as an example.

[0031] The method includes: determining to cancel reporting location event information; instructing the terminal device to cancel reporting location event information; after determining to cancel reporting location event information, the terminal device enters a power-off state; and after the terminal device enters a power-on state, it sends the cancellation of reporting location event information to the location management network element.

[0032] As one possible implementation, the terminal device determines whether to cancel reporting location event information based on stored data. Optionally, the cancellation information is stored in non-volatile memory (NV) or a universal subscriber identity module (USIM).

[0033] Based on the above scheme, after storing the information to cancel reporting location events, the terminal device enters the power-off state. After the terminal device is powered on, it sends the information to cancel reporting location events to the location management network element. In this way, the status of the terminal device is synchronized with the core network, while reducing the power-off latency of the terminal device.

[0034] In conjunction with the fourth aspect, in some implementations of the fourth aspect, the method further includes: receiving a cancellation of location event reporting response information, wherein the cancellation of location event reporting response information indicates whether the location management network element allows the terminal device to cancel reporting the location event.

[0035] Fifthly, a method is provided that can be performed by an apparatus (e.g., a communication apparatus). The apparatus can be a device (such as a network device), or it can be a component of a device (e.g., a chip (such as a modem chip, also known as a baseband chip, or a SoC chip or SIP chip containing a modem core) or a chip system or circuit), and this application does not limit this. The following description primarily uses a location management network element as an example.

[0036] The method includes: receiving cancellation of location event reporting information and a first identifier; the cancellation of location event reporting information instructs the terminal device to cancel the location event reporting; and determining the reason for the terminal device to cancel the location event reporting based on the first identifier.

[0037] In conjunction with the fifth aspect, in some implementations of the fifth aspect, the reporting of location event information and the first identifier from the terminal device are cancelled; or, the reporting of location event information and the first identifier from the access and mobility management network element are cancelled.

[0038] In conjunction with the fifth aspect, in some implementations of the fifth aspect, the method further includes: in the case that the location event information is cancelled and the first identifier comes from the terminal device, sending a cancellation location event response message to the terminal device, wherein the cancellation location event response message indicates that the terminal device is allowed to cancel the location event.

[0039] The beneficial effects of the fifth aspect and its possible implementation can be found in the descriptions of any of the aforementioned aspects, and will not be elaborated upon here.

[0040] A sixth aspect provides a communication apparatus for performing the method provided in any one of the first to fifth aspects. Specifically, the apparatus may include units and / or modules for performing the method provided in any of the above-described implementations of the first to fifth aspects, such as processing units and / or communication units.

[0041] In one implementation, the device is a communication device (such as a terminal device or a network device). When the device is a communication device, the communication unit can be a transceiver or an input / output interface; the processing unit can be at least one processor. Optionally, the transceiver can be a transceiver circuit. Optionally, the input / output interface can be an input / output circuit.

[0042] In another implementation, the device is a chip, chip system, or circuit used in a communication device. When the device is a chip, chip system, or circuit used in a communication device, the communication unit can be an input / output interface, interface circuit, output circuit, input circuit, pin, or related circuit on the chip, chip system, or circuit; the processing unit can be at least one processor, processing circuit, or logic circuit.

[0043] A seventh aspect provides a communication apparatus comprising: a memory for storing a program; and at least one processor for executing the computer program or instructions stored in the memory to perform the method provided by any of the above-described implementations of any of the first to fifth aspects.

[0044] In one implementation, the device is a communication device (such as a terminal device or a network device).

[0045] In another implementation, the device is a chip, chip system, or circuit used in a communication device.

[0046] Eighthly, this application provides a processor for performing the methods provided in the above aspects.

[0047] Unless otherwise specified, or if it does not contradict its actual function or internal logic in the relevant description, the transmission and acquisition / reception operations involved in the processor can be understood as processor output and input operations, or as transmission and reception operations performed by radio frequency circuits and antennas. This application does not limit them in this regard.

[0048] Ninth aspect, a computer-readable storage medium is provided for program code executed by a device, the program code including a method for performing any of the above-described implementations of any of the first to fifth aspects.

[0049] In a tenth aspect, a computer program product comprising instructions is provided, which, when executed by a processor on a computer, causes the computer to perform a method provided by any of the above-described implementations of any of the first to fifth aspects.

[0050] Eleventhly, a chip is provided, the chip including a processor and a communication interface, the processor reading instructions stored in a memory through the communication interface and executing the method provided by any of the above implementations of any of the first to fifth aspects.

[0051] Optionally, as one implementation, the chip further includes a memory storing computer programs or instructions, and a processor for executing the computer programs or instructions stored in the memory. When the computer programs or instructions are executed, the processor is used to execute the method provided by any of the above implementations of any of the first to fifth aspects.

[0052] In a twelfth aspect, a communication system is provided, comprising a first communication device and a second communication device. The first communication device is configured to execute the method provided in any implementation of the first or second aspect, and the second communication device is configured to execute the method provided in any implementation of the third to fifth aspects.

[0053] The beneficial effects of aspects six through twelfth and their possible implementations can be found in the descriptions of any of the foregoing aspects, and will not be repeated here. Attached Figure Description

[0054] Figure 1A schematic diagram of a communication network architecture applicable to an embodiment of this application is shown.

[0055] Figure 2 A schematic diagram of another network architecture applicable to embodiments of this application is shown.

[0056] Figure 3 This is a schematic diagram of the communication method 300 provided in an embodiment of this application.

[0057] Figure 4 This is a schematic diagram of the communication method 400 provided in an embodiment of this application.

[0058] Figure 5 This is a schematic diagram of the communication method 500 provided in the embodiments of this application.

[0059] Figure 6 This is a schematic diagram of the communication method 600 provided in an embodiment of this application.

[0060] Figure 7 This is a schematic diagram of method 700 provided in an embodiment of this application.

[0061] Figure 8 This is a schematic block diagram of a communication device 800 provided in an embodiment of this application.

[0062] Figure 9 This is a schematic diagram of another communication device 900 provided in an embodiment of this application.

[0063] Figure 10 This is a schematic block diagram of the chip system 1000 provided in the embodiments of this application. Detailed Implementation

[0064] The technical solutions in this application will now be described with reference to the accompanying drawings.

[0065] Before introducing the scheme of this application, the following points should be noted.

[0066] (1) In this application, "instruction" can include direct instruction, indirect instruction, explicit instruction, implicit instruction, etc. When describing an instruction information as indicating A, it can be understood that the instruction information carries A, carries the identifier of A, carries B which is associated with A, carries the identifier of B which is associated with A, etc. In other words, if the receiving side of an instruction information can determine A based on the instruction information, it can be described as the instruction information indicating A, and the specific method of determination is not limited. When it is understood that the instruction information carries A, "instruction" can be replaced with "includes". In this case, a statement such as "send / receive instruction information, the instruction information indicates A" can be replaced with "send / receive A".

[0067] In this application, the information indicated by the instruction information is called the information to be instructed. In specific implementations, there are many ways to indicate the information to be instructed, such as, but not limited to, directly indicating the information to be instructed, such as the information to be instructed itself or its index. It can also indirectly indicate the information to be instructed by indicating other information, where there is a relationship between the other information and the information to be instructed. It can also indicate only a part of the information to be instructed, while the other parts are known or pre-agreed upon. For example, the instruction of specific information can be achieved by using a pre-agreed (e.g., protocol-defined) arrangement of various pieces of information, thereby reducing instruction overhead to some extent. Furthermore, the information to be instructed can be sent as a whole or divided into multiple sub-information pieces, and the sending period and / or timing of these sub-information pieces can be the same or different.

[0068] (2) In this application, the expression " / " is used to indicate that the objects before and after are in an "or" relationship; for example, A / B can mean: A or B. The expression "and / or" is used to indicate that the objects before and after are in a relationship of either "and" or "or"; for example, A and / or B can mean the following: A exists alone, B exists alone, A and B exist simultaneously, where A and B can be single or multiple. "At least one of the following" or similar expressions are used to indicate any combination of the listed items; for example, at least one of A, B and / or C can mean the following: A exists alone, B exists alone, C exists alone, A and B exist simultaneously, B and C exist simultaneously, A and C exist simultaneously, A, B and C exist simultaneously, where A, B, and C can be single or multiple.

[0069] (3) In this application, "send" and "receive" indicate the direction of signal transmission. For example, "send information to XX" can be understood as the destination of the information being XX, which may include direct transmission via the air interface or indirect transmission by other units or modules via the air interface. "Receive information from YY" can be understood as the source of the information being YY, which may include direct reception from YY via the air interface or indirect reception from YY by other units or modules via the air interface. "Send" can also be understood as the "output" of the chip interface, and "receive" can also be understood as the "input" of the chip interface. In other words, sending and receiving can occur between devices, such as between network devices and terminal devices, or within a device, such as between components, modules, chips, software modules, or hardware modules within the device via a bus, wiring, or interface.

[0070] (4) In the various embodiments of this application, unless otherwise specified or in case of logical conflict, the terms and / or descriptions of different embodiments are consistent and can be referenced by each other. The technical features of different embodiments can be combined to form new embodiments according to their inherent logical relationship.

[0071] (5) In this application, "first," "second," and "#1," "#2," and "#A" are merely for descriptive convenience and are used to distinguish objects, and are not intended to limit the scope of the embodiments of this application. They are not used to describe the order or sequence of features. It should be understood that such described objects can be interchanged where appropriate in order to describe solutions other than those in the embodiments of this application.

[0072] (6) In this application, “predefined” may mean a standard protocol predefined, or it may mean that the devices have agreed or negotiated in advance. Here, “protocol” may refer to standard protocols in the field of communications, such as fourth-generation (4G) network protocols, fifth-generation (5G) network protocols, new radio (NR) protocols, and related protocols applied in future communication networks. This application does not limit this.

[0073] (7) In this application, the words “exemplary,” “for example,” etc., are used to indicate examples, illustrations, or descriptions. Any embodiment or design described as an “example” in this application should not be construed as being more preferred or advantageous than other embodiments or designs. Rather, the term “example” is used to present concepts in a specific manner.

[0074] (8) In this application, “of”, “corresponding, relevant”, “corresponding”, and “related” can sometimes be used interchangeably. It should be noted that when the distinction is not emphasized, they have the same meaning.

[0075] (9) In this application, “when…”, “if” and “if” all refer to the device making a corresponding processing under certain objective circumstances, and are not limited to a time, nor do they require the device to make a judgment when it is implemented, nor do they mean that there are other limitations.

[0076] (10) In this application, various types of information are involved (e.g., deregistration information, or initial registration information, etc.). It should be understood that their names do not limit the content of this application. For example, "deregistration information" can also be called "deregistration message", and "initial registration information" can also be called "initial registration message". No limitation is imposed.

[0077] Next, we will introduce the communication system to which this application applies.

[0078] The technical solutions provided in this application can be applied to various communication systems, such as 5th generation (5G) or new radio (NR) systems, long term evolution (LTE) systems, LTE frequency division duplex (FDD) systems, and LTE time division duplex (TDD) systems. The technical solutions provided in this application can also be applied to future communication systems, such as 6th generation mobile communication systems. Furthermore, the technical solutions provided in this application can also be applied to device-to-device (D2D) communication, vehicle-to-everything (V2X) communication, machine-to-machine (M2M) communication, machine-type communication (MTC), and Internet of Things (IoT) communication systems or other communication systems.

[0079] Next, the network architecture applicable to this application will be introduced.

[0080] Figure 1 A schematic diagram of a communication network architecture applicable to embodiments of this application is shown. This network architecture may specifically include the following devices or network elements.

[0081] 1. User Equipment (UE)

[0082] UE can be referred to as terminal equipment, access terminal, user unit, user station, mobile station, mobile station, remote station, remote terminal, mobile device, user terminal, terminal, wireless communication equipment, user agent, or user equipment.

[0083] Terminal devices can be devices that provide voice / data to users, such as handheld devices with wireless connectivity, in-vehicle devices, etc. Currently, examples of terminals include: mobile phones, tablets, laptops, PDAs, mobile internet devices (MIDs), wearable devices, virtual reality (VR) devices, augmented reality (AR) devices, wireless terminals in industrial control, wireless terminals in self-driving vehicles, wireless terminals in remote medical surgery, wireless terminals in smart grids, wireless terminals in transportation safety, wireless terminals in smart cities, wireless terminals in smart homes, cellular phones, cordless phones, session initiation protocol (SIP) phones, wireless local loop (WLL) stations, personal digital assistants (PDAs), handheld devices with wireless communication capabilities, computing devices or other processing devices connected to a wireless modem, wearable devices, terminal devices in 5G networks, or future public land mobile communication networks. Terminal devices in a network (PLMN), etc., are not limited to this in the embodiments of this application.

[0084] By way of example and not limitation, in this embodiment, the terminal device can also be a wearable device. Wearable devices, also known as wearable smart devices, are a general term for devices that utilize wearable technology to intelligently design and develop everyday wearables, such as glasses, gloves, watches, clothing, and shoes. Wearable devices are portable devices that are worn directly on the body or integrated into the user's clothing or accessories. Wearable devices are not merely hardware devices, but also achieve powerful functions through software support, data interaction, and cloud interaction. Broadly speaking, wearable smart devices include those that are feature-rich, large in size, and can achieve complete or partial functions without relying on a smartphone, such as smartwatches or smart glasses, as well as those that focus on a specific type of application function and require the use of other devices such as smartphones, such as various smart bracelets and smart jewelry for vital sign monitoring.

[0085] Furthermore, in this embodiment, the terminal device can also be a terminal device in an IoT system. IoT is an important component of the future development of information technology. Its main technical feature is to connect objects to the network through communication technology, thereby realizing an intelligent network of human-machine interconnection and object-to-object interconnection.

[0086] It should be noted that terminal devices and access network devices can communicate with each other using some air interface technology (such as NR or LTE). Terminal devices can also communicate with each other using some air interface technology (such as NR or LTE).

[0087] In this embodiment, the device for implementing the functions of the terminal device can be the terminal device itself, or it can be a device that supports the terminal device in implementing the functions, such as a chip system or a chip. This device can be installed in the terminal device. In this embodiment, the chip system can be composed of chips, or it can include chips and other discrete devices.

[0088] The embodiments of this application do not limit the specific technology or device form used by the UE.

[0089] 2. Radio access network (RAN): Used to provide network access functionality for authorized user equipment in a specific area, and can use transmission tunnels of different quality according to the user equipment level, service requirements, etc.

[0090] The RAN manages radio resources, provides access services to user equipment, and facilitates the forwarding of control signals and user equipment data between the user equipment and the core network.

[0091] The access network equipment includes, but is not limited to: next-generation node base stations (gNBs) in 5G systems, evolved node Bs (eNBs) in LTE systems, radio network controllers (RNCs), node Bs (NBs), base station controllers (BSCs), base transceiver stations (BTSs), home-evolved node Bs (or home node Bs (HNBs)), base band units (BBUs), transmitting and receiving points (TRPs), transmitting points (TPs), small cell equipment (picos), mobile switching centers, or network equipment in future networks. It is understood that this application does not limit the specific type of access network equipment. In systems employing different wireless access technologies, the names of devices with access network equipment functions may differ.

[0092] Optionally, in some deployments of the access device, the access device may include a central unit (CU) and a distributed unit (DU), etc. In other deployments of the access device, the CU may be divided into a CU-control plane (CP) and a CU-user plane (UP), etc. In still other deployments of the access device, the access device may also be an open radio access network (ORAN) architecture, etc. This application does not limit the specific deployment method of the access device.

[0093] 3. Access and Mobility Management (AMF) network element: mainly used for mobility management and access management, such as mobility restrictions, initial registration of terminal devices, mobility registration updates, deregistration, and registration management.

[0094] 4. Authentication server function (AUSF) network element: mainly used for user authentication, etc.

[0095] 5. Unified Data Management (UDM) network element: used for unified data management, 5G user data management, processing user identification, access authentication, registration, or mobility management, etc.

[0096] For example, UDM can perform security authentication during the mobility registration process of terminal devices, interact with AMF to exchange subscription data, and update the context of terminal devices.

[0097] 6. Session Management Function (SMF) network element: mainly used for session management, allocation and management of Internet Protocol (IP) addresses for terminal devices, selection and management of user plane functions, policy control and charging function interface endpoints, and downlink data notification, etc.

[0098] 7. Policy control function (PCF) network element: A unified policy framework used to guide network behavior, providing policy rule information to network elements (such as AMF, SMF, etc.) or terminal devices.

[0099] For example, the PCF can provide access and mobility policy control services to the AMF, including providing the AMF with mobility-related policy rules and updating the mobility-related policy rules.

[0100] 8. Application function (AF) network element: used for data routing affected by applications, accessing network open function network elements, and interacting with the policy framework for policy control, etc.

[0101] 9. Network Repository Function (NRF) Network Element: Used to store network function entities and their description information, as well as support functions such as service discovery and network element entity discovery.

[0102] 10. Network Exposure Function (NEF) element: Used to securely expose services and capabilities provided by 3GPP network functions to the outside world.

[0103] Figure 2 A schematic diagram of another network architecture applicable to embodiments of this application is shown.

[0104] like Figure 2As shown, the network architecture may include, but is not limited to, the following: (R)AN devices, access and mobility management function network elements, network open function network elements, application function network elements, location management function (LMF) network elements, unified data management network elements, gateway mobile location center (GMLC) network elements, location retrieval function (LRF) network elements, UEs, etc.

[0105] like Figure 2 As shown, the location management network element is mainly used to manage all resources used for UE positioning, calculate the final positioning result and accuracy, connect with the AMF through the NL1 interface to transmit various UE positioning signaling, negotiate positioning capabilities with the UE through the long-term evolution presentation protocol (LPP), send auxiliary data and request positioning, and exchange RAN positioning information with the RAN through the new radiopositioning protocol a (NRPPa).

[0106] It should be understood that the network architecture described above in the embodiments of this application is merely an example of a network architecture described from the perspective of a traditional point-to-point architecture and a service-oriented architecture. The network architecture applicable to the embodiments of this application is not limited to this, and any network architecture that can realize the functions of the above-mentioned network elements is applicable to the embodiments of this application.

[0107] It should be noted that the names of the various network elements and interfaces in this application are merely examples and do not limit the scope of protection of this application. This application does not exclude the possibility that the network elements may be given other names in the future, or that the functions of various network elements may be combined. With the evolution of technology, any device or network element that can implement the functions of the above-mentioned network elements is within the scope of protection of this application. This application does not exclude the possibility that other names may be used in future protocols to replace the above-mentioned network elements to achieve their same or similar functions. For example, in a 5G communication system, the access and mobility management network element may be AMF, the session management network element may be SMF, and the location management network element may be LMF. In future communication systems, these network elements may also evolve into other functional combinations, and therefore may have other names. For example, the access and mobility management network element may evolve into an access management network element for managing access, and a mobility management network element for managing mobility. This application does not limit these. Secondly, the above-mentioned network elements may also be referred to as entities, devices, apparatuses, functions, or modules, etc., and this application does not particularly limit these terms.

[0108] Before a UE performs a power-off operation, it sends a cancel location reporting event to the core network. The UE then powers off after receiving a response from the core network, thus saving network resources. However, in practical applications, due to various reasons (e.g., poor network environment), the core network may fail to receive the cancel location reporting event from the UE, or the UE may fail to receive a response from the core network. This results in the core network being unable to synchronize the UE's state, increasing the UE power-off latency and reducing the user experience. Therefore, this application proposes a method to address these issues.

[0109] Figure 3 This is a schematic diagram of the communication method 300 provided in an embodiment of this application.

[0110] S301, UE initiates shutdown.

[0111] Specifically, before entering the power-off state, the UE needs to initiate a cancellation of location reporting event. Based on this, this application mainly involves the following schemes: Scheme A, Scheme B and Scheme C.

[0112] Option A includes S302 and S303.

[0113] S302, the UE sends the first information, and the AMF receives the first information accordingly.

[0114] The first piece of information is either the registration information or the information about canceling the reporting of location events.

[0115] Optionally, S302 further includes: the UE sending a cause value (i.e., a first identifier), the cause value being used to characterize the state of the UE.

[0116] The embodiments of this application do not limit the specific method of sending the cause value. For example, the cause value may be carried in the first information; or the UE may send the cause value using separate signaling. For ease of description, the following description will use the method of including the cause value in the information (e.g., cancel reporting location event information, or deregister information, etc.), but it should be understood that this application is not limited to this.

[0117] In the embodiments of this application, the cause value is used to characterize the state of the UE. For ease of description, in the following text: cause value #1 is switch off, indicating that the UE is in or about to be in a power-off state; cause value #2 is restart, indicating that the UE restarts after being powered off; cause value #3 is initial registration, indicating that the UE initiates initial registration with the AMF.

[0118] S303, AMF sends a cancellation of location reporting event information, and correspondingly, LMF receives the cancellation of location reporting event information.

[0119] Specifically, the AMF determines to send a cancellation location event reporting information to the LMF based on the first information, wherein the cancellation location event reporting information instructs the UE to cancel reporting the location event to the LMF.

[0120] Optionally, the cancellation of location event reporting includes a reason value, which characterizes the UE's state. Further, the LMF can determine the reason why the UE cancels location event reporting based on the reason value.

[0121] In Scheme A, the AMF sends the UE cancel location reporting event information to the LMF. In this way, the UE status is synchronized with the core network, while the UE shutdown latency is reduced.

[0122] Option B includes S304.

[0123] S304, the UE sends a cancellation location reporting event message, and the LMF receives the cancellation location reporting event message accordingly.

[0124] Specifically, the "Cancel Location Event Reporting" option instructs the UE to cancel reporting location events to the LMF. The cancellation information includes a reason value #1, which characterizes the UE's state. Furthermore, based on reason value #1, the LMF can determine that the reason the UE cancels reporting location events is that it is powered off.

[0125] In Scheme B, the LMF can determine that the reason for the UE canceling the location event reporting is power off based on the reason value #1 in the cancellation location event reporting information. In other words, if the LMF determines that the reason for the UE canceling the location event reporting is power off, the LMF will not reject the UE's request to cancel the location event reporting, thereby reducing the UE's power-off latency.

[0126] Option C includes S305-S307.

[0127] S305, the UE sends registration information, and the AMF receives the registration information accordingly.

[0128] S306, the UE was powered off and then powered on again.

[0129] S307, the UE sends a cancellation location reporting event message, and the LMF receives the cancellation location reporting event message accordingly.

[0130] Among them, the cancellation of location event information instructs the UE to initiate a cancellation of location event reporting to the LMF.

[0131] Optionally, the cancellation of location event reporting includes a reason value, which characterizes the UE's state. Further, the LMF can determine the reason why the UE cancels location event reporting based on the reason value.

[0132] In Scheme C, after the UE sends the registration information to the AMF, it can directly enter the power-off state. After the UE restarts and enters the power-on state, it sends the cancellation of location reporting event information to the LMF. This method reduces the UE's power-off latency.

[0133] The following combination Figures 4 to 7 Describe options A, B, and C in detail.

[0134] The first possible scenario, Scheme A, includes: if the AMF records the subscription relationship between the UE and the LMF, the AMF can obtain the subscription relationship between the UE and the LMF based on the stored data. In this case, the AMF sends the cancellation of location reporting event information to the LMF based on the first information.

[0135] This includes implementation method one and implementation method two, which will be combined in detail. Figure 4 Describe it.

[0136] Figure 4 This is a schematic diagram of the communication method 400 provided in an embodiment of this application.

[0137] It should be understood that the numbering of each step in Method 400 is for ease of description, and the numbering of each step does not limit the execution order of the steps.

[0138] S401, AMF sends subscription information #1, and correspondingly, LMF receives subscription information #1.

[0139] Among them, subscription information #1 (for example, it could be Nlmf_Location_DetermineLocation Request) is used to subscribe to the LMF for the UE's reported location events.

[0140] Specifically, after the AMF sends subscription information #1 to the LMF to subscribe to the UE's reported location events, the AMF records the relevant information of the UE's reported location events (e.g., denoted as information #A) for subsequent operations.

[0141] Message #A includes the LMF's ID, allowing the AMF to establish communication with the LMF via this ID. Message #A also includes the UE's ID that reported the location event to the LMF, enabling the AMF to determine the UE's subscription relationship with the LMF. In other words, the AMF records (or stores) the UE's subscription relationship with the LMF.

[0142] It should be understood that the above description of information #A is only an example. This application does not limit the specific content of information #A, as long as the AMF can obtain the subscription relationship between the UE and the LMF based on information #A. For example, information #A may also include referenceNumberExt, h-gmlc-callBackUri, etc.

[0143] In this embodiment of the application, the subscription relationship between LMF and UE refers to the UE reporting its own location information to LMF after the LMF subscribes to the location reporting event to the UE.

[0144] The embodiments of this application do not limit the specific implementation of the location event reporting method of the LMF-subscribed UE. As one possible implementation method, it includes S402-S403.

[0145] S402, LMF sends subscription information #2, and correspondingly, UE receives subscription information #2.

[0146] Among them, subscription information #2 (for example, it could be LCS Periodic-Triggered invoke) is used by the LMF to subscribe to the UE for reporting location events.

[0147] S403, the UE sends subscription response information #2, and correspondingly, the LMF receives subscription response information #2.

[0148] Among them, subscription response information #2 (for example, it could be LCS Periodic-Triggered return result) is used by the LMF to determine that the subscription to the UE for reporting location events was successful.

[0149] S404, LMF sends subscription response information #1, and AMF receives subscription response information #1 accordingly.

[0150] The subscription response information #1 (for example, it could be Nlmf_Location_DetermineLocationResponse) is used by the AMF to determine that the UE's reported location event was successfully subscribed to by the LMF.

[0151] In steps S401-S404, the AMF records the subscription relationship between the UE and the LMF. This application does not limit the specific implementation of the AMF recording the subscription relationship between the UE and the LMF. For example, the AMF records the subscription relationship between the UE and the LMF after step S401; or, the AMF records the subscription relationship between the UE and the LMF after step S404.

[0152] It should be understood that S401-S404 are merely illustrative examples, and the embodiments of this application do not exclude other ways for the AMF to obtain the subscription relationship between the UE and the LMF.

[0153] Implementation method 1: If the first information is the registration information, then method 400 also includes S405-S412.

[0154] S405, UE initiates shutdown.

[0155] S406, the UE sends out registration information (an example of the first information), and the AMF receives the registration information accordingly.

[0156] The deregistration information (e.g., a Deregistration Request) instructs the UE to initiate a deregistration process with the AMF.

[0157] Optionally, the registration information includes reason value #1, which indicates that the UE is about to enter a power-off state.

[0158] For example, the deregistration information may also include one or more of the following: the UE's temporary identifier and the UE's expected unavailability period duration.

[0159] ●The UE's temporary identifier (e.g., a globally unique temporary identity, GUTI) is used by the AMF to determine the UE's identity.

[0160] ● UE’s expected unavailability duration is used by the AMF to determine the expected duration for which the UE will be unable to communicate normally.

[0161] S407, AMF executes the deregistration process.

[0162] For example, the AMF performing the deregistration process may include operations such as deleting the UE's context and deleting the PDU session.

[0163] The specific details of the AMF's deregistration process can be found in the description in protocol TS23.502, and will not be described in detail here.

[0164] S408, the UE enters the power-off state after receiving confirmation information from the base station.

[0165] Specifically, after the UE sends the deregistration information, the base station sends an acknowledgment information to the UE. Based on the acknowledgment information, the UE can determine that the AMF has successfully received the deregistration information. Then, after receiving the acknowledgment information from the base station, the UE enters the power-off state.

[0166] S409, the AMF determines to send the cancellation of location reporting event information to the LMF based on the deregistration information and the subscription relationship between the UE and the LMF.

[0167] Specifically, the AMF queries the subscription relationship between the UE and the LMF. The process of the AMF obtaining the subscription relationship between the UE and the LMF is, for example, S401-S404. Further, based on the deregistration information and the subscription relationship between the UE and the LMF, the AMF determines to send a cancel location reporting event to the LMF, that is, the AMF continues to execute S410.

[0168] As one possible implementation, if the AMF does not find the subscription relationship between the UE and the LMF, then the AMF will not execute S410.

[0169] S410, AMF sends a cancellation of location reporting event information, and correspondingly, LMF receives the cancellation of location reporting event information.

[0170] The option to cancel reporting location event information (e.g., Namf_Communication_N1MessageNotify) instructs the UE to cancel reporting location events to the LMF.

[0171] Optionally, the cancellation of location event reporting information includes the reason value #1. Further, the LMF can determine from the reason value #1 that the UE cancels the location event reporting because it is powered off.

[0172] For example, canceling the reporting of location event information also includes one or more of the following: referenceNumberExt, h-gmlc-callBackUri. For details on canceling the reporting of location event information, please refer to the description in protocol TS24.571, which will not be described in detail here.

[0173] As one possible implementation, the AMF can send M cancellation location event reports to the LMF, where M is an integer greater than or equal to 2. In other words, the AMF can retransmit the cancellation location event reports. This improves the success rate of sending cancellation location event reports.

[0174] S411, LMF executes to cancel UE location reporting event.

[0175] The specific operations performed by the LMF to cancel the UE's location event reporting include, for example, determining whether to allow the UE to cancel the location event reporting, determining to notify other network elements in the core network that the UE has canceled the location event reporting, and deleting the information that the LMF subscribed to the UE for the location event reporting. The specific content can be found in the description in protocol TS23.273, and will not be described in detail here.

[0176] Optionally, if the LMF determines that the reason for the UE canceling the location event reporting is power off based on the reason value #1 in the cancellation location event reporting information, then the LMF allows the UE to cancel the location event reporting based on the reason value #1. In other words, if the LMF determines that the reason for the UE canceling the location event reporting is power off, the LMF will not reject the UE's request to cancel the location event reporting.

[0177] S412, LMF notifies other network elements in the core network that the UE cancels reporting location events.

[0178] The specific implementation of LMF notification to other network elements can be found in the description in protocol TS23.273, and will not be described in detail here.

[0179] In this way, after receiving the confirmation information from the base station, the UE can enter the power-off state. The AMF sends the cancellation of location reporting event information to the LMF. After receiving the cancellation of location reporting event information, the LMF does not need to reply to the UE with a response information. In this way, the UE status is synchronized with the core network, while reducing the UE power-off latency.

[0180] Implementation method 2: If the first information is to cancel the reporting of location event information, then method 400 also includes S413-S424.

[0181] S413, UE initiates shutdown.

[0182] S414, the UE sends registration information, and the AMF receives the registration information accordingly.

[0183] The details regarding the removal of registration information can be found in the relevant description in S406, and will not be repeated here.

[0184] S415, AMF executes the deregistration process.

[0185] For example, the AMF performing the deregistration process may include operations such as deleting the UE's context and deleting the PDU session.

[0186] The specific details of the AMF's deregistration process can be found in the description in protocol TS23.502, and will not be described in detail here.

[0187] S416, UE records cancellation of location event reporting information.

[0188] Specifically, the UE records (or stores) the cancellation of location reporting event information (e.g., LcsCancelLocation).

[0189] For example, the UE records additional information (e.g., additional information), such as routing information received by the LCS in the downlink air interface message, which is used to indicate the ID of the LMF that has a subscription relationship with the UE.

[0190] This application does not limit the specific method by which the UE records the cancellation of reporting location event information.

[0191] For example, the UE can cancel the recording of location event information in an external storage device (such as USIM).

[0192] For example, the UE records the cancellation of location event reporting information in the NV way, that is, the cancellation of location event reporting information is stored on the mobile phone.

[0193] S417, the UE receives confirmation information from the base station.

[0194] Specifically, after sending the deregistration information, the UE receives an acknowledgment information from the base station. Based on the acknowledgment information, the UE can determine that the AMF has successfully received the deregistration information.

[0195] S417 can also be executed before S416, without restriction.

[0196] S418, UE enters power-off state.

[0197] S419, the UE restarts.

[0198] S420, the UE sends the first request, and the AMF receives the first request accordingly.

[0199] Specifically, the first request includes a registration request and a cancellation of location event reporting information (an example of the first information), wherein the registration request is used to request the UE to register with the AMF, and the cancellation of location event reporting information is the cancellation of location event reporting information recorded by the UE in S416.

[0200] This application does not limit the method of sending registration requests and cancel location event reporting information. For example, the cancellation location event reporting information can be carried in the registration request through an extended field.

[0201] Optionally, the first request includes reason value #3, which indicates that the UE has re-entered the power-on state after a reboot.

[0202] As one possible implementation, the registration request is an initial registration request, which is briefly described below.

[0203] For example, an initial registration request may include one or more of the following: the UE's identifier, the registration type, and security parameters.

[0204] ● The UE's identifier is used by the AMF to determine the UE's identity. The UE's identifier may be, for example, a subscription concealed identifier (SUCI), a globally unique temporary identity (GUTI), or a permanent equipment identifier (PEI) corresponding to the UE.

[0205] ● Registration type, used by the AMF to determine the type of registration process initiated by the UE. Registration types may include, for example, initial registration, mobility registration update, etc.

[0206] ● Security parameters are used to ensure the security of the registration process and subsequent communication processes.

[0207] S421, AMF executes the registration process.

[0208] Specifically, the AMF registers the UE to the AMF based on the registration request. As an optional implementation, if the registration request is an initial registration request, the AMF will execute the initial registration process. The specific details of the AMF executing the initial registration process can be found in the description in protocol TS23.502, and will not be described in detail here.

[0209] S422, the AMF determines to send the cancellation of location event reporting information to the LMF based on the cancellation of location event reporting information and the subscription relationship between the UE and the LMF.

[0210] The subscription relationship between the UE and the LMF is obtained by the AMF during the S401-S404 process.

[0211] S422 can also be executed before S421, without restriction.

[0212] S423, AMF sends a cancellation of location reporting event information, and correspondingly, LMF receives the cancellation of location reporting event information.

[0213] The option to cancel reporting location event information (e.g., Namf_Communication_N1MessageNotify) instructs the UE to cancel reporting location events.

[0214] Optionally, the cancellation of location event reporting information includes reason value #2. Further, the LMF can determine the reason why the UE cancels location event reporting based on reason value #2: the UE has restarted and re-entered the power-on state.

[0215] As one possible implementation, the AMF can send M cancellation location event reports to the LMF, where M is an integer greater than or equal to 2. In other words, the AMF can retransmit the cancellation location event reports. This improves the success rate of sending cancellation location event reports.

[0216] S424, LMF executes to cancel UE location reporting event.

[0217] The specific operations performed by the LMF to cancel the UE's location event reporting include, for example, determining whether to allow the UE to cancel the location event reporting, determining to notify other network elements in the core network that the UE has canceled the location event reporting, and deleting the information that the LMF subscribed to the UE for the location event reporting. The specific content can be found in the description in protocol TS23.273, and will not be described in detail here.

[0218] Optionally, the LMF can determine that the reason for the UE canceling the location event reporting is a restart based on the reason value #2 in the cancellation location event reporting information, thereby reducing the possibility that the LMF will reject the UE's cancellation of the location event reporting.

[0219] S425, LMF notifies other network elements in the core network that the UE cancels reporting location events.

[0220] The specific implementation of LMF notification to other network elements can be found in the description in protocol TS23.273, and will not be described in detail here.

[0221] In summary, after receiving confirmation information from the base station, the UE can enter the power-off state. After powering on again, the AMF sends a cancellation information for location event reporting to the LMF. In this way, the UE state is synchronized with the LMF while reducing the latency of UE power-off. Furthermore, the LMF can resubscribe to location event reporting to the UE after powering on.

[0222] The second possible scenario, Scheme A, includes: the UE sending first information and second information, wherein the second information indicates the LMF that has a subscription relationship with the UE, and further, the AMF sends cancellation of location event reporting information to the LMF based on the first information and the second information.

[0223] This includes implementation methods three and four, which will be combined in detail. Figure 5 Describe it.

[0224] Figure 5 This is a schematic diagram of the communication method 500 provided in the embodiments of this application.

[0225] It should be understood that the numbering of each step in Method 500 is for ease of description, and the numbering of each step does not limit the execution order of the steps.

[0226] S501, LMF subscribes to and reports location events to the UE.

[0227] S501 can be referred to in S402-S403, and will not be repeated here.

[0228] Implementation method 3: If the first information is to cancel the reporting of location event information, then method 500 also includes S502-S509.

[0229] S502, UE initiates shutdown.

[0230] S503, the UE sends registration information (an example of the first information) and second information, and the AMF receives the registration information and the second information accordingly.

[0231] The deregistration information (e.g., a Deregistration Request) instructs the UE to initiate a deregistration process with the AMF. The content of the deregistration information can be found in the description in S406, and will not be repeated here.

[0232] The second information (e.g., LcsCancelLocation) includes additional information (e.g., additional information) and cancellation of location event reporting information (e.g., LCS-MSCancelDeferredLocation). The second information instructs the UE to cancel reporting location events to the LMF with which it has a subscription relationship.

[0233] Specifically, the additional information may be, for example, routing information received by the LCS in the downlink air interface message, which is used to indicate the ID of the LMF that has a subscription relationship with the UE.

[0234] It should be understood that the above-described method of sending the second information is only an example. This application does not exclude other methods of sending the second information. For example, the UE may use separate signaling to send the second information, or the second information may be carried in the deregistration information and sent together. This is not limited.

[0235] S504, AMF executes the deregistration process.

[0236] For example, the AMF performing the deregistration process may include operations such as deleting the UE's context and deleting the PDU session.

[0237] The specific details of the AMF's deregistration process can be found in the description in protocol TS23.502, and will not be described in detail here.

[0238] S505: After receiving confirmation information from the base station, the UE enters the power-off state.

[0239] Specifically, after the UE sends the deregistration information, the base station sends an acknowledgment information to the UE. Based on the acknowledgment information, the UE can determine that the AMF has successfully received the deregistration information. Then, after receiving the acknowledgment information from the base station, the UE enters the power-off state.

[0240] S506, the AMF determines to send the cancellation of location reporting event information to the LMF based on the deregistration information and the second information.

[0241] S507, the AMF sends a cancellation of location reporting event information, and the LMF receives the cancellation of location reporting event information accordingly.

[0242] The option to cancel reporting location event information (e.g., Namf_Communication_N1MessageNotify) instructs the UE to cancel reporting location events.

[0243] Optionally, the cancellation of location event reporting information includes reason value #1. Further, if the LMF can determine from reason value #1 that the reason for the UE canceling location event reporting is power off, then the LMF allows the UE to cancel location event reporting based on reason value #1. In other words, if the LMF determines that the reason for the UE canceling location event reporting is power off, the LMF will not reject the UE's request to cancel location event reporting.

[0244] As one possible implementation, the AMF can send M cancellation location event reports to the LMF, where M is an integer greater than or equal to 2. In other words, the AMF can retransmit the cancellation location event reports. This improves the success rate of sending cancellation location event reports.

[0245] S508, LMF executes to cancel UE location reporting event.

[0246] The content of S508 can be found in the description in S411, and will not be repeated here.

[0247] S509, LMF notifies other network elements in the core network that the UE cancels the reporting of location events.

[0248] The specific implementation of LMF notification to other network elements can be found in the description in protocol TS23.273, and will not be described in detail here.

[0249] In summary, after receiving confirmation information from the base station, the UE can enter the power-off state. The AMF can determine to send the cancellation of location reporting event information to the LMF based on the deregistration information and the second information sent by the UE. After receiving the cancellation of location reporting event information, the LMF does not need to reply to the UE with response information. In this way, the UE status is synchronized with the core network while reducing the UE power-off latency.

[0250] Implementation method four: Method 500 also includes S510-S521.

[0251] S510, UE initiates shutdown.

[0252] The contents of S511-S516 can be found in the descriptions in S414-S419, and will not be repeated here.

[0253] S517, the UE sends a second request, and the AMF receives the second request accordingly.

[0254] Specifically, the second request includes a registration request and second information. The content of the registration request can be referred to the description in S420, and the content of the second information can be referred to the description in S503. They will not be repeated here.

[0255] S518, AMF executes the registration process.

[0256] The content of S518 can be found in the description in S421, and will not be repeated here.

[0257] S519, the AMF determines to send the cancellation of location reporting event information to the LMF based on the second request.

[0258] S520, AMF sends a cancellation of location reporting event information, and correspondingly, LMF receives the cancellation of location reporting event information.

[0259] The option to cancel reporting location event information (e.g., Namf_Communication_N1MessageNotify) instructs the UE to cancel reporting location events.

[0260] Optionally, the cancellation of location event reporting information includes reason value #2. Further, the LMF can determine the reason why the UE cancels location event reporting based on reason value #2: the UE has restarted and re-entered the power-on state.

[0261] As one possible implementation, the AMF can send M cancellation location event reports to the LMF, where M is an integer greater than or equal to 2. In other words, the AMF can retransmit the cancellation location event reports. This improves the success rate of sending cancellation location event reports.

[0262] S521, LMF executes to cancel UE location reporting event.

[0263] The content of S521 can be found in the description in S424, and will not be repeated here.

[0264] S522, LMF notifies other network elements in the core network that the UE cancels reporting location events.

[0265] The specific implementation of LMF notification to other network elements can be found in the description in protocol TS23.273, and will not be described in detail here.

[0266] In summary, after receiving confirmation information from the base station, the UE can enter the power-off state. After powering on again, the AMF sends a cancellation information for location event reporting to the LMF. In this way, the UE's state is synchronized with the LMF while reducing the UE's power-off latency. Furthermore, the LMF can resubscribe to location event reporting to the UE after powering on.

[0267] In one possible implementation, scheme B includes: the UE sending a cancellation location event reporting message to the LMF, the cancellation location event reporting message including the reason value #1.

[0268] This includes implementation method five, specifically combined with... Figure 6 Describe it.

[0269] Figure 6 This is a schematic diagram of the communication method 600 provided in an embodiment of this application.

[0270] It should be understood that the numbering of each step in Method 600 is for ease of description, and the numbering of each step does not limit the execution order of the steps.

[0271] S601, LMF subscribes to and reports location events to UE.

[0272] S601 can be referred to in S402-S403, and will not be repeated here.

[0273] S602, UE initiates shutdown.

[0274] When the UE is in a CM-IDLE state, method 600 includes S603.

[0275] S603, the UE sends request information #1, and the AMF receives request information #1 accordingly.

[0276] Among them, request information #1 (for example, it could be a service request) is used by the UE to request the establishment of a signaling connection with the AMF.

[0277] If the AMF and UE successfully establish a connection, then method 600 also includes S604-S611.

[0278] S604, AMF sends request response information #1, and correspondingly, UE receives request response information #1.

[0279] Among them, request response information #1 indicates that the AMF and UE have successfully established a connection.

[0280] S605, the UE sends a cancellation location reporting event message, and the LMF receives the cancellation location reporting event message accordingly.

[0281] The cancellation of location event reporting information (e.g., LCS-MSCancelDeferredLocation) includes a reason value #1. The cancellation of location event reporting information instructs the UE to cancel reporting location events. Furthermore, if the LMF can determine from the reason value #1 that the reason for the UE to cancel reporting location events is that the device is powered off, then the LMF will allow the UE to cancel reporting location events based on the reason value #1. In other words, if the LMF determines that the reason for the UE to cancel reporting location events is that the device is powered off, the LMF will not reject the UE's request to cancel reporting location events.

[0282] S606, LMF executes to cancel UE location reporting event.

[0283] The content of S606 can be found in the description in S411, and will not be repeated here.

[0284] S607, LMF notifies other network elements in the core network that the UE cancels reporting location events.

[0285] The specific implementation of LMF notification to other network elements can be found in the description in protocol TS23.273, and will not be described in detail here.

[0286] S608, the LMF sends a cancellation location reporting event response message, and the UE receives the cancellation location reporting event response message accordingly.

[0287] Among them, the Cancel Location Event Reporting Response Information Instruction LMF allows the UE to cancel reporting location events.

[0288] If the Cancel Location Event Reporting Response Instruction (LMF) allows the UE to cancel reporting location events, the UE can execute S609.

[0289] As one possible implementation, if the LMF does not allow the UE to cancel the location reporting event response, S605 can be executed repeatedly until the LMF allows the UE to cancel the location reporting event; or, the UE can directly execute S609 and enter the power-off state, and then re-initiate the cancellation of the location reporting event after the UE is powered on.

[0290] S608 is an optional step. Specifically, in one possible scenario, the UE confirms that the LMF has received the cancellation location event information based on the cancellation location event response information, and S608 is executed; in another possible scenario, after executing S605, the UE may assume that the LMF has received the cancellation location event information. For example, since the cancellation location event information includes the cause value #1, the UE may assume that the LMF allows the UE to cancel the location event after sending the cancellation location event information, and the UE may continue to execute S609 after executing S605.

[0291] As a possible implementation, when S608 is executed, method 600 further includes: setting duration #1 (i.e., the first duration), the start time of duration #1 is after the UE sends the cancellation of location reporting event information (i.e., S605), after duration #1 the UE can confirm that the LMF failed to receive the cancellation of location reporting event information sent by the UE, then the UE executes step S609, further, after the UE is powered on, re-initiating the cancellation of location reporting event.

[0292] In this application embodiment, the duration #1 is not limited. Optionally, the duration #1 can be predefined, configured, or indicated.

[0293] In one possible scenario, if the UE executes S609 after duration #1 and confirms that the LMF failed to receive the cancellation location reporting event information sent by the UE, the UE may receive a cancellation location reporting event response from the LMF. In this case, the UE can ignore the cancellation location reporting event response and continue executing S609. After the UE restarts, it can then re-initiate the cancellation location reporting event to the LMF. In other words, the priority of deregistration information is higher than the priority of the cancellation location reporting event response information.

[0294] S609, the UE sends registration information, and the AMF receives the registration information accordingly.

[0295] The details regarding the removal of registration information can be found in the relevant description in S406, and will not be repeated here.

[0296] S610, AMF executes the deregistration process.

[0297] For example, the AMF performing the deregistration process may include operations such as deleting the UE's context and deleting the PDU session.

[0298] The specific details of the AMF's deregistration process can be found in the description in protocol TS23.502, and will not be described in detail here.

[0299] S611, after receiving confirmation information from the base station, the UE enters the power-off state.

[0300] Specifically, after the UE sends the deregistration information, the base station sends an acknowledgment information to the UE. Based on the acknowledgment information, the UE can determine that the AMF has successfully received the deregistration information. Then, after receiving the acknowledgment information from the base station, the UE enters the power-off state.

[0301] In the above, a cause value (i.e., cause value #1 in S605) is added to the cancellation location reporting event information sent by the UE to the LMF. In this way, the LMF can determine that the reason for the UE to cancel the location reporting event is power off, and thus the LMF allows the UE to cancel the location reporting event, thereby reducing the UE's power off latency.

[0302] In one possible implementation, scheme C includes: after the UE powers on, it sends a cancellation location reporting event message to the LMF.

[0303] This includes implementation method six, specifically combined with... Figure 7 Describe it.

[0304] Figure 7 This is a schematic diagram of method 700 provided in an embodiment of this application.

[0305] It should be understood that the numbering of each step in Method 700 is for ease of description, and the numbering of each step does not limit the execution order of the steps.

[0306] S701, LMF subscribes to and reports location events to the UE.

[0307] S701 can be referred to in S402-S403, and will not be repeated here.

[0308] S702, UE initiates shutdown.

[0309] S703, UE failed to transmit uplink air interface.

[0310] Specifically, in some possible situations (such as poor channel conditions, base station failure, or congestion), the UE may fail to send uplink data to the base station. In other words, in such cases, the UE may fail to send registration information.

[0311] S704, the UE sends registration information, and the AMF receives the registration information accordingly.

[0312] The details regarding the removal of registration information can be found in the relevant description in S406, and will not be repeated here.

[0313] S705, UE records cancellation of location event reporting information.

[0314] Specifically, the UE records the cancellation of location reporting event information (e.g., LcsCancelLocation).

[0315] For example, the UE records additional information (e.g., additional information), such as routing information received by the LCS in the downlink air interface message, which is used to indicate the ID of the LMF that has a subscription relationship with the UE.

[0316] This application does not limit the specific method by which the UE records the cancellation of reporting location event information.

[0317] For example, the UE can cancel the recording of location event information in an external storage device (such as USIM).

[0318] For example, the UE records the cancellation of location event reporting information in the NV way, that is, the cancellation of location event reporting information is stored on the mobile phone.

[0319] S706, UE enters power-off state.

[0320] Specifically, after the UE records the cancellation of reporting location event information, the UE enters the power-off state.

[0321] In one possible scenario, if the AMF successfully receives the deregistration information in S704, the AMF can then execute the deregistration process based on the deregistration information.

[0322] Another possible scenario is that in S704, if the AMF fails to successfully receive the deregistration information, the AMF will execute S707.

[0323] S707: In the event that the implicit deregistration timer times out, AMF executes the deregistration process.

[0324] Specifically, the AMF can determine that the UE has entered the power-off state based on the implicit deregistration timer (e.g., the implicit deregistration timer), and then the AMF will execute the deregistration process.

[0325] For details regarding the AMF's execution of the deregistration process based on the implicit deregistration timer, please refer to the description in protocol TS24.501; it will not be described in detail here.

[0326] For example, the AMF performing the deregistration process may include operations such as deleting the UE's context and deleting the PDU session.

[0327] The specific details of the AMF's deregistration process can be found in the description in protocol TS23.502, and will not be described in detail here.

[0328] S708: After the UE is powered on, it determines to initiate a cancel location reporting event to the LMF based on the cancel location reporting event information.

[0329] Specifically, after the UE is powered on, based on the recorded cancellation of location reporting event information (i.e., the cancellation of location reporting event information recorded by the UE in S705), it is determined that the UE did not initiate a cancellation of location reporting event before powering off. Therefore, the UE determines to initiate a cancellation of location reporting event to the LMF.

[0330] S709, the UE sends a registration request, and the AMF receives the registration request accordingly.

[0331] The details of the registration request can be found in S420, and will not be repeated here.

[0332] S710, the UE sends a cancellation location reporting event message, and the LMF receives the cancellation location reporting event message accordingly.

[0333] Among them, the option to cancel reporting location event information instructs the UE to cancel reporting location events.

[0334] Optionally, the cancellation of location event reporting information includes reason value #2. Further, the LMF can determine the reason why the UE cancels location event reporting based on reason value #2: the UE is in the power-on state after being restarted.

[0335] S711, LMF executes to cancel UE location reporting event.

[0336] The content of S711 can be found in the description in S411, and will not be repeated here.

[0337] S712, LMF notifies other network elements in the core network that the UE cancels reporting location events.

[0338] The specific implementation of LMF notification to other network elements can be found in the description in protocol TS23.273, and will not be described in detail here.

[0339] S713, LMF sends a cancellation location reporting event response message, and correspondingly, UE receives the cancellation location reporting event response message.

[0340] Specifically, after receiving the information about canceling the location event reporting, the LMF returns a cancellation response information to the UE. The cancellation response information is used to indicate whether the LMF allows the UE to cancel the location event reporting.

[0341] In the above process, after the UE sends the registration information to the AMF, the UE records the cancellation of location event reporting and enters the power-off state. After powering on again, the UE initiates the cancellation of location event reporting to the LMF. In this way, the UE's state is synchronized with the LMF while reducing the latency of UE power-off. Furthermore, the LMF can resubscribe to location event reporting from the UE after powering on.

[0342] In some possible cases, the above implementation methods can be used in combination, without limitation.

[0343] For example, the combination of Implementation Method 1 and Implementation Method 6 is a possible implementation method. If the deregistration information in S406 fails to be sent successfully, the UE can continue to execute S705-S713.

[0344] For another example, the combination of implementation method three and implementation method six is ​​a possible implementation method. If the deregistration information and the second information in S503 fail to be sent successfully, the UE can continue to execute S705-S713.

[0345] For example, implementation methods five and six can be used in combination. For instance, in S603, if request information #1 fails to be sent successfully, the UE can continue to execute S704-S713; in S604, if the UE fails to receive request response information #1 successfully, the UE can continue to execute S704-S713; in S605, if the cancellation of location event reporting information fails to be sent successfully, the UE can continue to execute S704-S713; in S608, if the cancellation of location event reporting response information indicates that the LMF does not allow the UE to cancel the location event reporting, the UE can continue to execute S704-S713; and after duration #1, the UE can continue to execute S704-S713. Other scenarios will not be listed one by one.

[0346] Here is a simple example.

[0347] One possible scenario: In S604, if the UE fails to successfully receive the request response information #1, the UE can continue to execute S704-S713.

[0348] In other words, in S604, if the UE fails to receive the request response information #1, the UE sends the registration information to the AMF and then enters the power-off state. After the UE is powered on again, it can initiate the cancellation of location reporting event again.

[0349] As one possible implementation, the method also includes: setting a duration #2, after which the UE can confirm that the connection between the AMF and the UE has failed to be established, and then the UE executes S704. The start time of duration #2 is located after the UE sends request information #1 (i.e., S603). This method reduces the UE's shutdown latency.

[0350] In this application embodiment, the duration #2 is not limited. Optionally, the duration #2 can be predefined, configured, or indicated.

[0351] In one possible scenario, when the UE confirms the failure to establish a connection with the AMF after duration #2 and executes S704, the UE receives request response information #1 from the AMF. In this case, the UE can ignore request response information #1, continue executing S704, and then re-initiate a cancellation location reporting event to the LMF after the UE restarts. In other words, the priority of deregistering information is higher than the priority of request response information #1.

[0352] Figure 8 This is a schematic block diagram of a communication device 800 provided in an embodiment of this application. The communication device includes a transceiver unit 810. The transceiver unit 810 can be used to implement corresponding communication functions. The transceiver unit 810 can also be referred to as a communication interface or a communication unit. Optionally, the device 800 further includes a processing unit 820. The processing unit 820 can be used to implement processing operations.

[0353] Optionally, the device 800 may further include a storage unit for storing instructions and / or data, and the processing unit 820 may read the instructions and / or data from the storage unit to enable the device to implement the aforementioned method embodiments.

[0354] Optionally, the transceiver unit 810 includes a sending unit and / or a receiving unit, wherein the sending unit is used to perform the sending operation in the above embodiments, and the receiving unit is used to perform the receiving operation in the above embodiments.

[0355] It should be noted that the communication device 800 may include a transmitting unit but not a receiving unit; or, the communication device 800 may include a receiving unit but not a transmitting unit. Specifically, it depends on whether the above-described scheme performed by the communication device 800 includes both transmitting and receiving actions. For example, the communication device 800 is used to perform the above-described... Figures 3 to 7 The actions performed by each node (e.g., UE, AMF, LMF) in the illustrated embodiments can be found in the above description. Figures 3 to 7 The relevant descriptions in the illustrated embodiments will not be repeated here.

[0356] For example, communication device 800 is used to execute the following scheme.

[0357] In one possible design, the device 800 is a network device, or it can be a component of a network device (such as a chip, chip system, or circuit). The transceiver unit and the processing unit can be used to implement the relevant operations of the network device, for example, the network device is an access and mobility management network element.

[0358] In one possible implementation, the transceiver unit 810 is used to receive first information from the terminal device, which is sent by the terminal device based on the power-off process; the processing unit 820 is used to determine the location management network element that subscribes to the location event reporting of the terminal device based on the first information; the transceiver unit 810 is also used to send a cancellation information to the location management network element, which instructs the terminal device to cancel the reporting of location events.

[0359] Optionally, the processing unit 820 is further configured to determine the location management network element that subscribes to the location events reported by the terminal device based on the first information and the subscription relationship between the terminal device and the location management network element, wherein the subscription relationship includes the subscription relationship between the terminal device and the location management network element.

[0360] Optionally, before the access and mobility management network element determines the location management network element that subscribes to the location events reported by the terminal device based on the first information and the subscription relationship between the terminal device and the location management network element, the transceiver unit 810 is further configured to send a first subscription to the location management network element, the first subscription being used to subscribe to the location events reported by the terminal device subscribed by the location management network element; the transceiver unit 810 is further configured to receive a first subscription notification, the first subscription notification including the location events reported by the terminal device subscribed by the location management network element.

[0361] Optionally, the processing unit 820 is also used to record the subscription relationship between the terminal device and the location management network element.

[0362] Optionally, the first information is the registration information; or, the first information is the first cancellation of the reported location event information.

[0363] Optionally, the cancellation of location event reporting information includes a first identifier, which is used by the location management network element to determine the reason why the terminal device cancels the location event reporting.

[0364] In a second possible design, the device 800 is a network device, or it can be a component of a network device (such as a chip, chip system, or circuit). The transceiver unit and the processing unit can be used to implement the relevant operations of the network device, for example, the network device is an access and mobility management network element.

[0365] In one possible implementation, the transceiver unit 810 is configured to receive first information and second information from the terminal device, wherein the first information is sent by the terminal device based on the power-off process, and the second information includes the location management network element for reporting location events by the terminal device; the transceiver unit 810 is further configured to send cancellation of reporting location events information to the location management network element based on the first information and the second information, wherein the cancellation of reporting location events information instructs the terminal device to initiate cancellation of reporting location events.

[0366] Optionally, the first information is any one of the following: registration information or the first cancellation of location reporting event information.

[0367] Optionally, the cancellation of location event reporting information includes a first identifier, which is used by the location management network element to determine the reason why the terminal device cancels the location event reporting.

[0368] In a third possible design, the device 800 can be a terminal device, or a component of a terminal device (such as a chip, chip system, or circuit). The transceiver unit and processing unit can be used to implement the relevant operations of the terminal device.

[0369] In one possible implementation, the transceiver unit 810 is used to send a cancellation of location event reporting information and a first identifier to the location management network element. The cancellation of location event reporting information instructs the terminal device to cancel the reporting of location events, and the first identifier is used by the location management network element to determine the reason for the terminal device to cancel the reporting of location events. After sending the cancellation of location event reporting information and the first identifier, the terminal device enters a power-off state.

[0370] Optionally, before the terminal device enters the power-off state, the transceiver unit 810 is also configured to receive a cancellation of location event reporting response information, which indicates that the terminal device is allowed to cancel reporting the location event.

[0371] Optionally, the terminal device enters a power-off state after a first duration; the first duration begins at the transceiver unit 810 after sending the cancellation of the reported location event information and the first identifier.

[0372] A fourth possible design is that the device 800 is a terminal device, or it can be a component of a terminal device (such as a chip, chip system, or circuit). The transceiver unit and processing unit can be used to implement the relevant operations of the terminal device.

[0373] In one possible implementation, the processing unit 820 is used to determine whether to cancel the reporting of location event information, and to instruct the terminal device to cancel the reporting of location events. After determining whether to cancel the reporting of location event information, the terminal device enters a power-off state. After the terminal device enters a power-on state, the transceiver unit 810 is also used to send the cancellation of reporting of location events information to the location management network element.

[0374] Optionally, the terminal device determines whether to cancel reporting location event information based on stored data, wherein the cancel location event information is stored in NV or USIM.

[0375] Optionally, the transceiver unit 810 is also configured to receive a cancellation of location event reporting response information, which indicates whether the location management network element allows the terminal device to cancel the location event reporting.

[0376] In a fifth possible design, the device 800 is a network device, or it can be a component of a network device (such as a chip, chip system, or circuit). The transceiver unit and the processing unit can be used to implement the relevant operations of the network device, such as a location management network element.

[0377] In one possible implementation, the transceiver unit 810 is used to receive the cancellation of location reporting event information and the first identifier, wherein the cancellation of location reporting event information instructs the terminal device to initiate the cancellation of location reporting event; and the processing unit 820 is used to determine the reason for the terminal device to initiate the cancellation of location reporting event based on the first identifier.

[0378] Optionally, the reporting of location event information and the first identifier from the terminal device can be cancelled; or, the reporting of location event information and the first identifier from the access and mobility management network element can be cancelled.

[0379] Optionally, if the cancellation of location event reporting information and the first identifier originate from the terminal device, the transceiver unit 810 is further configured to send a cancellation of location event reporting response information to the terminal device, the cancellation of location event reporting response information indicating that the terminal device is allowed to cancel the reporting of location events.

[0380] It is understood that the division of units in the above-described device is merely a logical functional division. Each function can correspond to a functional unit, or two or more functions can be integrated into one functional unit. In actual implementation, all or some units can be integrated into a single physical entity, or they can be distributed across different physical entities. Furthermore, the aforementioned functional units can be implemented in hardware, software, or a combination of both. Whether a function is executed in hardware or software depends on the specific application and design constraints of the technical solution. Those skilled in the art can use different methods to implement the described functions for each specific application, but such implementation should not be considered beyond the scope of this application.

[0381] In one example, the functional unit in any of the above devices may be one or more integrated circuits configured to implement the above methods, such as: one or more application-specific integrated circuits (ASICs), or one or more central processing units (CPUs), one or more microcontroller units (MCUs), one or more digital signal processors (DSPs), or one or more field-programmable gate arrays (FPGAs), or a combination of at least two of these integrated circuit forms.

[0382] In one example, the storage unit may include random access memory, flash memory, read-only memory, programmable read-only memory, or electrically erasable programmable memory and / or registers, etc.

[0383] Figure 9 This is a schematic diagram of another communication device 900 provided in an embodiment of this application. The device 900 includes a processor 910, which is coupled to a memory 920. The memory 920 is used to store computer programs or instructions and / or data. The processor 910 is used to execute the computer programs or instructions stored in the memory 920, or to read the data stored in the memory 920, in order to execute the methods in the above method embodiments.

[0384] Optionally, there may be one or more processors 910.

[0385] Optionally, the memory 920 may be one or more.

[0386] Optionally, the memory 920 is integrated with the processor 910, or the memory 920 is built into the processor 910, or the memory 920 is set separately from the processor 910.

[0387] Optionally, such as Figure 9 As shown, the device 900 also includes a transceiver 930 for receiving and / or transmitting signals. For example, a processor 910 is used to control the transceiver 930 to receive and / or transmit signals.

[0388] For example, processor 910 is used to execute computer programs or instructions stored in memory 920 to implement the relevant operations of terminal devices or network devices in the various method embodiments described above.

[0389] Optionally, the transceiver 930 includes a transmitter (or a transmitter module, a transmitting circuit, etc.) and / or a receiver (or a receiver module, a receiving circuit, etc.), wherein the transmitter is used to perform the transmitting operation in the above embodiments, and the receiver is used to perform the receiving operation in the above embodiments.

[0390] It should be noted that the communication device 900 may include a transmitter but not a receiver; or, the communication device 900 may include a receiver but not a transmitter. Specifically, it depends on whether the above-described scheme performed by the communication device 900 includes both transmitting and receiving actions. For example, the communication device 900 is used to perform the above-described... Figures 3 to 7 The actions performed by each node (e.g., UE, AMF, LMF) in the illustrated embodiments can be found in the above description. Figures 3 to 7 The relevant descriptions in the illustrated embodiments will not be repeated here.

[0391] It should be understood that the processor mentioned in the embodiments of this application can be a central processing unit (CPU), or other general-purpose processors, digital signal processors (DSPs), application-specific integrated circuits (ASICs), field-programmable gate arrays (FPGAs), or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, etc. A general-purpose processor can be a microprocessor or any conventional processor.

[0392] It should also be understood that the memory mentioned in the embodiments of this application can be volatile memory and / or non-volatile memory. Non-volatile memory can be read-only memory (ROM), programmable read-only memory (PROM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), or flash memory. Volatile memory can be random access memory (RAM). For example, RAM can be used as an external cache. By way of example and not limitation, RAM includes the following forms: static random access memory (SRAM), dynamic random access memory (DRAM), synchronous dynamic random access memory (SDRAM), double data rate synchronous dynamic random access memory (DDR SDRAM), enhanced synchronous dynamic random access memory (ESDRAM), synchronous linked dynamic random access memory (SLDRAM), and direct rambus RAM (DR RAM).

[0393] It should be noted that when the processor is a general-purpose processor, DSP, ASIC, FPGA, or other programmable logic device, discrete gate or transistor logic device, or discrete hardware component, the memory (storage module) can be integrated into the processor.

[0394] It should also be noted that the memory described herein is intended to include, but is not limited to, these and any other suitable types of memory.

[0395] Figure 10 This is a schematic block diagram of a chip system 1000 provided in an embodiment of this application. The chip system 1000 (or may also be referred to as a processing system) includes logic circuitry 1010 and an input / output interface 1020.

[0396] The logic circuit 1010 can be a processing circuit in the chip system 1000. The logic circuit 1010 can be coupled to a memory unit, calling instructions from the memory unit, enabling the chip system 1000 to implement the methods and functions of the embodiments of this application. The input / output interface 1020 can be an input / output circuit in the chip system 1000, outputting processed information from the chip system 1000, or inputting data or signaling information to be processed into the chip system 1000 for processing.

[0397] As one approach, the chip system 1000 is used to implement the operations performed by the communication device (such as a terminal device or a network device) in the various method embodiments described above.

[0398] For example, logic circuit 1010 is used to implement processing-related operations performed by a communication device (such as a terminal device or a network device) in the above method embodiments; input / output interface 1020 is used to implement sending and / or receiving-related operations performed by a communication device (such as a terminal device or a network device) in the above method embodiments.

[0399] This application also provides a computer-readable storage medium storing computer instructions for implementing the methods executed by a communication device (such as a terminal device or a network device) in the above-described method embodiments.

[0400] For example, when the computer program is executed by a computer, it enables the computer to implement the methods described in the embodiments of the above methods, which are executed by a communication device (such as a terminal device or a network device).

[0401] This application also provides a computer program product comprising instructions which, when executed by a computer, implement the methods described above as being performed by a communication device (such as a terminal device or a network device).

[0402] This application also provides a communication system, which includes the terminal devices and / or network devices described in the above embodiments.

[0403] The explanations and beneficial effects of the relevant contents in any of the devices provided above can be found in the corresponding method embodiments provided above, and will not be repeated here.

[0404] In the several embodiments provided in this application, it should be understood that the disclosed apparatus and methods can be implemented in other ways. For example, the apparatus embodiments described above are merely illustrative; for instance, the division of units is only a logical functional division, and in actual implementation, there may be other division methods. For example, multiple units or components may be combined or integrated into another system, or some features may be ignored or not executed. Furthermore, the mutual coupling or direct coupling or communication connection shown or discussed may be through some interfaces, and the indirect coupling or communication connection of apparatus or units may be electrical, mechanical, or other forms.

[0405] In the above embodiments, implementation can be achieved entirely or partially through software, hardware, firmware, or any combination thereof. When implemented using software, it can be implemented entirely or partially in the form of a computer program product. The computer program product includes one or more computer instructions. When the computer program instructions are loaded and executed on a computer, all or part of the processes or functions described in the embodiments of this application are generated. The computer can be a general-purpose computer, a special-purpose computer, a computer network, or other programmable device. For example, the computer can be a personal computer, a server, or a network device, etc. The computer instructions can be stored in a computer-readable storage medium or transmitted from one computer-readable storage medium to another. 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 (e.g., coaxial cable, fiber optic, digital subscriber line (DSL)) or wireless (e.g., infrared, wireless, microwave, etc.) means. The computer-readable storage medium can be any available medium that a computer can access or a data storage device such as a server or data center that integrates one or more available media. The available media can be magnetic media (e.g., floppy disks, hard disks, magnetic tapes), optical media (e.g., DVDs), or semiconductor media (e.g., solid-state disks, SSDs). For example, the aforementioned available media include, but are not limited to, USB flash drives, portable hard drives, read-only memory (ROM), random access memory (RAM), magnetic disks, or optical disks, and other media capable of storing program code.

[0406] The above description is merely a specific embodiment of this application, but the scope of protection of this application is not limited thereto. Any variations or substitutions that can be easily conceived by those skilled in the art within the scope of the technology disclosed in this application should be included within the scope of protection of this application. Therefore, the scope of protection of this application should be determined by the scope of the claims.

Claims

1. A communication method, characterized in that, The method includes: Receive first information from the terminal device, the first information being sent by the terminal device based on the power-off process; Based on the first information, a location management network element that subscribes to the location events reported by the terminal device is determined; Send a cancellation location event reporting message to the location management network element, the cancellation location event reporting message instructing the terminal device to cancel reporting location events.

2. The method according to claim 1, characterized in that, The step of determining the location management network element that subscribes to the location events reported by the terminal device based on the first information includes: Based on the first information and the subscription relationship between the terminal device and the location management network element, the location management network element that subscribes to the location events reported by the terminal device is determined, and the subscription relationship includes the subscription relationship between the terminal device and the location management network element.

3. The method according to claim 2, characterized in that, Before determining the location management network element that subscribes to the location events reported by the terminal device based on the first information and the subscription relationship between the terminal device and the location management network element, the method further includes: Send a first subscription to the location management network element, wherein the first subscription is used to subscribe to the location reporting events of the terminal device subscribed by the location management network element; Receive a first subscription notification, the first subscription notification including the location reporting events of the terminal device subscribed by the location management network element.

4. The method according to claim 2 or 3, characterized in that, The method further includes: Record the subscription relationship between the terminal device and the location management network element.

5. A communication method, characterized in that, The method includes: Receive first information and second information from the terminal device, wherein the first information is sent by the terminal device based on the power-off process, and the second information includes the location management network element of the terminal device reporting location events; Based on the first information and the second information, a cancellation information for reporting location events is sent to the location management network element, and the cancellation information for reporting location events instructs the terminal device to cancel reporting location events.

6. The method according to any one of claims 1 to 5, characterized in that, include: The first piece of information is any one of the following: registration information or first cancellation of location reporting event information.

7. The method according to any one of claims 1 to 6, characterized in that, include: The information about canceling the location event reporting includes a first identifier, which is used by the location management network element to determine the reason why the terminal device cancels the location event reporting.

8. A communication method, characterized in that, The method includes: The location management network element sends a cancellation information for reporting location events and a first identifier. The cancellation information for reporting location events instructs the terminal device to cancel reporting location events. The first identifier is used by the location management network element to determine the reason why the terminal device cancels reporting location events. After sending the cancel location reporting event information and the first identifier, the terminal device enters a power-off state.

9. The method according to claim 8, characterized in that, Before the terminal device enters the power-off state, the method further includes: The terminal device receives a cancellation response message for location event reporting from the location management network element, wherein the cancellation response message indicates that the terminal device is allowed to cancel reporting the location event.

10. The method according to claim 8, characterized in that, The method further includes: After a first duration, the terminal device enters a power-off state, with the first duration starting after the sending of the cancel location reporting event information and the first identifier.

11. A communication method, characterized in that, The method includes: The system determines to cancel reporting location event information, wherein the cancellation of location event reporting information instructs the terminal device to cancel reporting location events; After confirming the cancellation of the location reporting event information, the terminal device enters a power-off state; After the terminal device enters the power-on state, it sends the information about canceling the location reporting event to the location management network element.

12. The method according to claim 11, characterized in that, The method further includes: The system receives a cancellation response message for location event reporting, which indicates whether the location management network element allows the terminal device to cancel reporting location events.

13. A communication method, characterized in that, The method includes: Receive a cancellation location event reporting information and a first identifier, wherein the cancellation location event reporting information instructs the terminal device to cancel reporting the location event; The reason for the terminal device canceling the location event reporting is determined based on the first identifier.

14. The method according to claim 13, characterized in that, include: The cancellation of location event reporting information and the first identifier are from the terminal device; or, the cancellation of location event reporting information and the first identifier are from the access and mobility management network element.

15. The method according to claim 14, characterized in that, The cancellation of location event reporting information and the first identifier are from the terminal device, and the method further includes: Send a cancellation location event reporting response message to the terminal device, the cancellation location event reporting response message indicating that the terminal device is allowed to cancel reporting location events.

16. A communication device, characterized in that, include: A processor for executing a computer program or instructions stored in a memory to cause the communication device to perform the method as described in any one of claims 1 to 15.

17. A computer program product, characterized in that, The computer program product includes programs or instructions for performing the method as described in any one of claims 1 to 15.

18. A chip system, characterized in that, include: A processor for retrieving and running a computer program or instructions from memory, causing a communication device on which the chip system is installed to perform the method of any one of claims 1 to 15.

19. A computer-readable storage medium, characterized in that, include: The computer-readable storage medium stores a computer program that, when run on a computer, causes the computer to perform the method as described in any one of claims 1 to 15.

Images