A method, device and computer storage medium for activating and deactivating a service

Abstract

The present invention discloses a method, device and computer storage medium for activating and deactivating services. The method comprises: during the process of initiating registration with a network entity, a terminal sends indication information to the network entity, wherein the indication information is used to indicate to the network entity services that need to be activated and / or services that need to be deactivated.

Description

Technical Field

[0001] The present invention relates to the field of mobile communication technology, and in particular to a method, device and computer storage medium for activating and deactivating a service. Background Art

[0002] After the terminal registers to the network for the first time, it will establish some service information with the core network element, such as protocol data unit (PDU) session information. When the terminal enters the idle state, it will also save this service information; when the terminal registers to the network again, it will confirm with the core network element whether the locally saved service information is valid and activate all services. However, not all services need to be activated. In some scenarios, the terminal only needs to activate some services. The current service activation method causes a waste of resources. Summary of the invention

[0003] In order to solve the above technical problems, the embodiments of the present invention provide a method, device and computer storage medium for activating and deactivating a service.

[0004] The method for activating and deactivating a service provided by an embodiment of the present invention includes:

[0005] During the process of initiating registration with a network entity, the terminal sends indication information to the network entity, where the indication information is used to indicate to the network entity services that need to be activated and / or services that need to be deactivated.

[0006] In the embodiment of the present invention, the terminal sends indication information to the network entity during the process of initiating registration with the network entity, including:

[0007] The terminal sends indication information carrying an activation service list and / or a deactivation service list to the network entity during the process of initiating registration with the network entity;

[0008] The activated service list includes one or more service information that needs to be activated, and the deactivated service list includes one or more service information that needs to be deactivated.

[0009] In the embodiment of the present invention, the service information at least includes: identification information of the service.

[0010] In an embodiment of the present invention, the service information includes at least: identification information of the public land mobile network entity (PLMN, Public Land Mobile Network) to which the service belongs or identification information of the network slice.

[0011] In the embodiment of the present invention, the terminal sends the indication information to the network entity, including:

[0012] The terminal sends a registration request message to the network entity, where the registration request message carries the indication information.

[0013] In the embodiment of the present invention, the terminal sends the indication information to the network entity, including:

[0014] The terminal sends a registration completion message to the network entity, where the registration completion message carries the indication information.

[0015] In the embodiment of the present invention, the terminal sends indication information to the network entity during the process of initiating registration with the network entity, including:

[0016] The terminal sends indication information to the network entity during the process of initiating attachment to the network entity.

[0017] In the embodiment of the present invention, the terminal sends indication information to the network entity during the process of initiating registration with the network entity, including:

[0018] The terminal sends indication information to the network entity during the process of initiating location area update to the network entity.

[0019] In the embodiment of the present invention, the terminal sends indication information to the network entity during the process of initiating registration with the network entity, including:

[0020] The terminal sends indication information to the network entity during the process of initiating tracking area update to the network entity.

[0021] In the embodiment of the present invention, the indication information is also used to trigger the network entity to release the context of the service that needs to be deactivated.

[0022] In the embodiment of the present invention, when the network entity sends a change, the terminal sends indication information to the network entity, including:

[0023] The terminal sends indication information to the destination network entity, wherein the indication information is used to trigger the destination network entity to perform the following operations: sending the indication information to the source network entity; receiving the context of the service that needs to be activated sent by the source network entity.

[0024] In the embodiment of the present invention, the indication information is used to trigger the source network entity to perform the following operations: based on the indication information, determine the service to be activated, and send the context of the service to be activated to the destination network entity;

[0025] The indication information is used to trigger the source network entity to perform the following operations: based on the indication information, determine the service that needs to be deactivated, and delete the context of the service that needs to be deactivated.

[0026] In the embodiment of the present invention, the service that needs to be activated or the service that needs to be deactivated includes one or more of the following services:

[0027] PDU session, Packet Data Network (PDN) connection, Quality of Service (QoS) flow, bearer, data flow.

[0028] In the embodiment of the present invention, the network entity is a core network element.

[0029] The service activation and deactivation device provided by the embodiment of the present invention includes:

[0030] A registration unit configured to initiate a registration process with a network entity;

[0031] The indication unit is configured to send indication information to the network entity during the process of initiating registration with the network entity, wherein the indication information is used to indicate to the network entity the services that need to be activated and / or the services that need to be deactivated.

[0032] In the embodiment of the present invention, the indication unit is specifically configured to: in the process of initiating registration with the network entity, send indication information carrying the activation service list and / or deactivation service list to the network entity;

[0033] The activated service list includes one or more service information that needs to be activated, and the deactivated service list includes one or more service information that needs to be deactivated.

[0034] In the embodiment of the present invention, the service information at least includes: identification information of the service.

[0035] In an embodiment of the present invention, the service information includes at least: identification information of the PLMN to which the service belongs or identification information of the network slice.

[0036] In the embodiment of the present invention, the indication unit is specifically configured to: send a registration request message to the network entity, wherein the registration request message carries the indication information.

[0037] In the embodiment of the present invention, the indication unit is specifically configured to: send a registration completion message to the network entity, wherein the registration completion message carries the indication information.

[0038] In the embodiment of the present invention, the instructing unit is specifically configured to: send instruction information to the network entity during the process of initiating attachment to the network entity.

[0039] In the embodiment of the present invention, the indication unit is specifically configured to: send indication information to the network entity during the process of initiating location area update to the network entity.

[0040] In the embodiment of the present invention, the indication unit is specifically configured to: send indication information to the network entity during the process of initiating a tracking area update to the network entity.

[0041] In the embodiment of the present invention, the indication information is also used to trigger the network entity to release the context of the service that needs to be deactivated.

[0042] In an embodiment of the present invention, when a network entity sends a change, the indication unit is specifically configured to: send indication information to a destination network entity, wherein the indication information is used to trigger the destination network entity to perform the following operations: send the indication information to a source network entity; receive the context of a service that needs to be activated sent by the source network entity.

[0043] In the embodiment of the present invention, the indication information is used to trigger the source network entity to perform the following operations: based on the indication information, determine the service to be activated, and send the context of the service to be activated to the destination network entity;

[0044] The indication information is used to trigger the source network entity to perform the following operations: based on the indication information, determine the service that needs to be deactivated, and delete the context of the service that needs to be deactivated.

[0045] In the embodiment of the present invention, the service that needs to be activated or the service that needs to be deactivated includes one or more of the following services:

[0046] PDU session, PDN connection, QoS flow, bearer, data flow.

[0047] In the embodiment of the present invention, the network entity is a core network element.

[0048] The computer storage medium provided by the embodiment of the present invention stores computer executable instructions thereon, and the computer executable instructions, when executed by a processor, can implement the above-mentioned service activation and deactivation method.

[0049] In the technical solution of the embodiment of the present invention, during the process of initiating registration with a network entity, the terminal sends indication information to the network entity, and the indication information is used to indicate to the network entity the services that need to be activated and / or the services that need to be deactivated. By adopting the technical solution of the embodiment of the present invention, when the terminal registers with the network again, only the services that need to be activated can be activated, and the services that need to be deactivated can be released, thereby effectively saving resources and improving service efficiency. BRIEF DESCRIPTION OF THE DRAWINGS

[0050] The drawings described herein are used to provide a further understanding of the present invention and constitute a part of this application. The exemplary embodiments of the present invention and their descriptions are used to explain the present invention and do not constitute an improper limitation of the present invention. In the drawings:

[0051] Figure 1 This is a system architecture diagram of a 5G network according to an embodiment of the present invention;

[0052] Figure 2 A system architecture diagram of a 4G network according to an embodiment of the present invention;

[0053] Figure 3 Schematic diagram of the process of service activation and deactivation method according to an embodiment of the present invention Figure 1 ;

[0054] Figure 4 Schematic diagram of the process of service activation and deactivation method according to an embodiment of the present invention Figure 2 ;

[0055] Figure 5 A schematic diagram of the structure of a device for activating and deactivating services according to an embodiment of the present invention;

[0056] Figure 6 The figure is a schematic diagram of the structure of a terminal according to an embodiment of the present invention. DETAILED DESCRIPTION

[0057] In order to enable a more detailed understanding of the features and technical contents of the embodiments of the present invention, the implementation of the embodiments of the present invention is described in detail below in conjunction with the accompanying drawings. The attached drawings are for reference only and are not intended to limit the embodiments of the present invention.

[0058] Figure 1 : is a system architecture diagram of a 5G network according to an embodiment of the present invention, such as Figure 1 As shown in the figure, the devices involved in the 5G network system include:

[0059] Terminal (UE, User Equipment), Radio Access Network (RAN, Radio Access Network), User Plane Function (UPF, User Plane Function), Data Network (DN, Data Network), Core Access and Mobility Management Function (AMF, Core Access and Mobility Management Function), Session Management Function (SMF, Session Management Function), Policy Control Function (PCF, Policy Control function), Application Function (AF, Application Function), Authentication Server Function (AUSF, Authentication Server Function), Unified Data Management (UDM, Unified Data Management).

[0060] Figure 2 is a system architecture diagram of a 4G network according to an embodiment of the present invention, such as Figure 2 As shown in the figure, the devices involved in the 4G network system include:

[0061] Terminal (UE, User Equipment), Evolved Universal Terrestrial Radio Access Network (E-UTRAN, Evolved Universal Terrestrial Radio Access Network), Mobility Management Function (MME, Mobility Management Entity) network element, Serving GPRS Support Node (SGSN, Serving GPRS Support Node), Home Subscriber Server (HSS, Home Subscriber Server), Serving Gateway (Serving Gateway), Packet Data Gateway (PDN Gateway, Packet Data Network Gateway), Policy and Charging Rules Function (PCRF, Policy and Charging Rules Function).

[0062] Above Figure 1 , Figure 2 The example is only an example of a network architecture to implement the embodiment of the present invention. The embodiment of the present invention is not limited to the above Figure 1 , Figure 2 The network structure described.

[0063] Figure 3 Schematic diagram of the process of service activation and deactivation method according to an embodiment of the present invention Figure 1 ,like Figure 3 As shown, the service activation and deactivation method includes the following steps:

[0064] Step 301: During the process of initiating registration with a network entity, the terminal sends indication information to the network entity, where the indication information is used to indicate to the network entity services that need to be activated and / or services that need to be deactivated.

[0065] In one implementation, the indication information carries an activated service list.

[0066] In one implementation, the indication information carries a deactivated service list.

[0067] The activated service list includes one or more service information that needs to be activated, and the deactivated service list includes one or more service information that needs to be deactivated.

[0068] Based on this, the terminal sends indication information carrying an activated service list and / or a deactivated service list to the network entity during the process of initiating registration with the network entity.

[0069] In the above solution, the service information at least includes: identification information of the service.

[0070] In one embodiment, the service information also includes: identification information of the PLMN to which the service belongs or identification information of the network slice.

[0071] In the embodiment of the present invention, during the process of initiating registration with a network entity, the terminal sends indication information to the network entity, which can be implemented in any of the following ways:

[0072] Mode 1: The terminal sends a registration request message to the network entity, and the registration request message carries the indication information.

[0073] Mode 2: The terminal sends a registration completion message to the network entity, and the registration completion message carries the indication information.

[0074] In actual applications, the registration process initiated by the terminal to the network entity includes but is not limited to the following situations:

[0075] Case 1: the terminal sends indication information to the network entity during the process of initiating attachment to the network entity.

[0076] Case 2: the terminal sends indication information to the network entity during the process of initiating location area update to the network entity.

[0077] Case 3: the terminal sends indication information to the network entity during the process of initiating tracking area update to the network entity.

[0078] In the embodiment of the present invention, the indication information is also used to trigger the network entity to release the context of the service that needs to be deactivated.

[0079] In an embodiment of the present invention, when a network entity sends a change, a terminal sends indication information to a destination network entity, wherein the indication information is used to trigger the destination network entity to perform the following operations: sending the indication information to a source network entity; and receiving the context of a service that needs to be activated sent by the source network entity.

[0080] In the above scheme, the indication information is used to trigger the source network entity to perform the following operations: based on the indication information, determine the service to be activated, and send the context of the service to be activated to the destination network entity;

[0081] The indication information is used to trigger the source network entity to perform the following operations: based on the indication information, determine the service that needs to be deactivated, and delete the context of the service that needs to be deactivated.

[0082] In the above solution of the embodiment of the present invention, the service that needs to be activated or the service that needs to be deactivated includes one or more of the following services:

[0083] PDU session, PDN connection, QoS flow, bearer, data flow.

[0084] In the above solution of the embodiment of the present invention, the network entity is a core network element.

[0085] The technical solution of the embodiment of the present invention is further described in detail below in conjunction with the 5G network architecture.

[0086] Figure 4 Schematic diagram of the process of service activation and deactivation method according to an embodiment of the present invention Figure 2 ,like Figure 4 As shown, the service activation and deactivation method includes the following steps:

[0087] Step 401: UE sends a registration request message to RAN.

[0088] Here, the registration request message is "Registration Request".

[0089] Here, the registration request message may carry service information that needs to be activated and / or service information that needs to be deactivated.

[0090] Step 402: RAN performs an AMF selection operation.

[0091] Here, RAN selects a new AMF, which is also called the target AMF.

[0092] Step 403: RAN sends a registration request message to the new AMF.

[0093] Here, the registration request message is "Registration Request".

[0094] Step 404: The new AMF sends a UE context request message to the old AMF.

[0095] Here, the UE context request message is "Namf_Communication_UE Context Transfer". The UE context request message carries service information that needs to be activated and / or service information that needs to be deactivated.

[0096] Here, the old AMF is also referred to as the source AMF.

[0097] Step 405: The old AMF sends a UE context response message to the new AMF.

[0098] Here, the UE context response message is "Namf_Communication_UE Context Transferresponse". The old AMF carries the context of the service to be activated in the UE context response message and sends it to the new AMF.

[0099] In one implementation, the old AMF deletes the context of the service that needs to be deactivated.

[0100] Step 406: The new AMF sends an identity request message to the UE.

[0101] Here, the identity request message is "Identity Request".

[0102] Step 407: The UE sends an identity response message to the new AMF.

[0103] Here, the identity response message is "Identity Response".

[0104] Step 408: The new AMF performs the AUSF selection operation.

[0105] Step 409: The new AMF performs authentication / security operations with each network element and the UE.

[0106] Step 410: The new AMF sends a registration completion notification message to the old AMF.

[0107] Here, the registration completion notification message is "Namf_Communication_Registration CompleteNotify".

[0108] Step 411: The new AMF sends an identity request message to the UE, and receives an identity response message sent by the UE.

[0109] Here, the identity request message is "Identity Request"; the identity response message is "IdentityResponse".

[0110] Step 412: The new AMF sends an ME identity confirmation message to the Equipment Identity Register (EIR) and receives a response message sent by the EIR.

[0111] Here, the identity confirmation message is "N5g-eir ME Identity Check_Get"

[0112] Step 413: The new AMF performs a UDM selection operation.

[0113] Steps 414a-414b: The new AMF performs registration / subscription retrieval with each network element.

[0114] Step 414c: UDM sends a UE context management deregistration notification message to the old AMF.

[0115] Here, the UE context management deregistration notification message is "Nudm_UE Context Management_Deregistration Notify".

[0116] Step 415: The new AMF performs a PCF selection operation.

[0117] Step 416: The new AMF and PCF execute execution policy control acquisition.

[0118] Here, the policy control acquisition message is "Npcf_AM Policy Control_Get".

[0119] Step 417: The new AMF sends a notification message to the SMF.

[0120] Here, the notification message is "Namf_Event Exposure_Notify (UE reach ablity state with PDU status)".

[0121] Step 418: The new AMF sends an N2 request message to the N3IWF.

[0122] Step 419: N3IWF sends an N2 response message to the new AMF.

[0123] Step 420: The old AMF and PCF execute policy control deletion.

[0124] Step 421: The new AMF sends a registration accept message to the UE.

[0125] Here, the registration acceptance message is "Registration Accept".

[0126] Step 422: The UE sends a registration completion message to the new AMF.

[0127] Here, the registration completion message is "Registration Complete".

[0128] Here, the registration completion message may carry service information that needs to be activated and / or service information that needs to be deactivated.

[0129] In the above scheme, after the new AMF receives the registration request of the terminal, it will obtain the context of the activated service from the old AMF. In one embodiment, the deactivated service is also notified to the old AMF. After the old AMF receives the notification from the new AMF, it deletes the context of the service that is not in the activated service list or in the deactivated service list.

[0130] Figure 5 FIG. 1 is a schematic diagram of the structure of the device for activating and deactivating a service according to an embodiment of the present invention. Figure 5 As shown, the device comprises:

[0131] A registration unit 501, configured to initiate a registration process with a network entity;

[0132] The indication unit 502 is configured to send indication information to the network entity during the process of initiating registration with the network entity, wherein the indication information is used to indicate to the network entity the services that need to be activated and / or the services that need to be deactivated.

[0133] In one implementation, the indication unit 502 is specifically configured to: in the process of initiating registration with the network entity, send indication information carrying the activation service list and / or the deactivation service list to the network entity;

[0134] The activated service list includes one or more service information that needs to be activated, and the deactivated service list includes one or more service information that needs to be deactivated.

[0135] In one implementation, the service information at least includes: identification information of the service.

[0136] In one embodiment, the service information includes at least: identification information of the PLMN to which the service belongs or identification information of the network slice.

[0137] In one implementation, the indication unit 502 is specifically configured to: send a registration request message to the network entity, wherein the registration request message carries the indication information.

[0138] In one implementation, the indication unit 502 is specifically configured to: send a registration completion message to the network entity, wherein the registration completion message carries the indication information.

[0139] In one implementation, the instructing unit 502 is specifically configured to: send instruction information to the network entity during the process of initiating attachment to the network entity.

[0140] In one implementation, the indication unit 502 is specifically configured to: send indication information to the network entity during the process of initiating a location area update to the network entity.

[0141] In one implementation, the indication unit 502 is specifically configured to: send indication information to the network entity during the process of initiating a tracking area update to the network entity.

[0142] In one implementation, the indication information is further used to trigger the network entity to release the context of the service that needs to be deactivated.

[0143] In one embodiment, when the network entity sends a change, the indication unit 502 is specifically configured to: send indication information to the destination network entity, wherein the indication information is used to trigger the destination network entity to perform the following operations: send the indication information to the source network entity; receive the context of the service that needs to be activated sent by the source network entity.

[0144] In one embodiment, the indication information is used to trigger the source network entity to perform the following operations: based on the indication information, determine the service to be activated, and send the context of the service to be activated to the destination network entity;

[0145] The indication information is used to trigger the source network entity to perform the following operations: based on the indication information, determine the service that needs to be deactivated, and delete the context of the service that needs to be deactivated.

[0146] In one embodiment, the service that needs to be activated or the service that needs to be deactivated includes one or more of the following services:

[0147] PDU session, PDN connection, QoS flow, bearer, data flow.

[0148] In one implementation, the network entity is a core network element.

[0149] Those skilled in the art should understand that Figure 5 The implementation functions of each unit in the service activation and deactivation device shown can be understood by referring to the relevant description of the aforementioned service activation and deactivation method. Figure 5 The functions of the various units in the service activation and deactivation device shown may be implemented by a program running on a processor, or may be implemented by a specific logic circuit.

[0150] If the above-mentioned service activation and deactivation device of the embodiment of the present invention is implemented in the form of a software function module and sold or used as an independent product, it can also be stored in a computer-readable storage medium. Based on this understanding, the technical solution of the embodiment of the present invention can be essentially or partly reflected in the form of a software product that contributes to the prior art. The computer software product is stored in a storage medium, including a number of instructions for a computer device (which can be a personal computer, a server, or a network device, etc.) to execute all or part of the methods described in each embodiment of the present invention. The aforementioned storage medium includes: various media that can store program codes, such as a U disk, a mobile hard disk, a read-only memory (ROM, Read Only Memory), a magnetic disk or an optical disk. In this way, the embodiment of the present invention is not limited to any specific combination of hardware and software.

[0151] Correspondingly, an embodiment of the present invention further provides a computer storage medium, in which computer executable instructions are stored. When the computer executable instructions are executed by a processor, the above-mentioned service activation and deactivation method of the embodiment of the present invention is implemented.

[0152] Figure 6 FIG. 1 is a schematic diagram of the structure of a terminal according to an embodiment of the present invention. Figure 6 As shown, the terminal 60 may include one or more (only one is shown in the figure) processors 602 (the processor 602 may include but is not limited to a processing device such as a microprocessor (MCU, MicroController Unit) or a programmable logic device (FPGA, Field Programmable Gate Array)), a memory 604 for storing data, and a transmission device 606 for communication functions. It can be understood by those skilled in the art that Figure 6 The structure shown is for illustration only and does not limit the structure of the above electronic device. Figure 6 More or fewer components as shown, or with Figure 6 Different configurations shown.

[0153] The memory 604 can be used to store software programs and modules of application software, such as program instructions / modules corresponding to the service activation and deactivation method in the embodiment of the present invention. The processor 602 executes various functional applications and data processing by running the software programs and modules stored in the memory 604, that is, implementing the above method. The memory 604 may include a high-speed random access memory, and may also include a non-volatile memory, such as one or more magnetic storage devices, flash memory, or other non-volatile solid-state memory. In some examples, the memory 604 may further include a memory remotely arranged relative to the processor 602, and these remote memories may be connected to the terminal 60 via a network. Examples of the above network include, but are not limited to, the Internet, an intranet, a local area network, a mobile communication network, and combinations thereof.

[0154] The transmission device 606 is used to receive or send data via a network. The specific example of the above network may include a wireless network provided by the communication provider of the terminal 60. In one example, the transmission device 606 includes a network adapter (NIC, Network Interface Controller), which can be connected to other network devices through a base station so as to communicate with the Internet. In one example, the transmission device 606 can be a radio frequency (RF, Radio Frequency) module, which is used to communicate with the Internet wirelessly.

[0155] The technical solutions described in the embodiments of the present invention can be combined arbitrarily without conflict.

[0156] In the several embodiments provided by the present invention, it should be understood that the disclosed methods and intelligent devices can be implemented in other ways. The device embodiments described above are only schematic. For example, the division of the units is only a logical function division. There may be other division methods in actual implementation, such as: multiple units or components can be combined, or can be integrated into another system, or some features can be ignored or not executed. In addition, the coupling, direct coupling, or communication connection between the components shown or discussed can be through some interfaces, and the indirect coupling or communication connection of the devices or units can be electrical, mechanical or other forms.

[0157] The units described above as separate components may or may not be physically separated, and the components displayed as units may or may not be physical units, that is, they may be located in one place or distributed on multiple network units; some or all of the units may be selected according to actual needs to achieve the purpose of the present embodiment.

[0158] In addition, all functional units in the embodiments of the present invention may be integrated into a second processing unit, or each unit may be a separate unit, or two or more units may be integrated into one unit; the above-mentioned integrated units may be implemented in the form of hardware or in the form of hardware plus software functional units.

[0159] The above description is only a specific implementation mode of the present invention, but the protection scope of the present invention is not limited thereto. Any technician familiar with the technical field can easily think of changes or substitutions within the technical scope disclosed by the present invention, which should be covered by the protection scope of the present invention.

Claims

1. A method for activating and deactivating a service, the method comprising: The terminal sends indication information to the network entity during the process of initiating registration with the network entity, where the indication information is used to indicate to the network entity the services that need to be activated and / or the services that need to be deactivated; Wherein, when a network entity is changed, the terminal sends indication information to the network entity, including: The terminal sends indication information to the destination network entity, wherein the indication information is further used to trigger the destination network entity to perform the following operations: sending the indication information to the source network entity; receiving the context of the service to be activated sent by the source network entity; The network entity is the access and mobility management function AMF.

2. The method according to claim 1, wherein: The terminal sends indication information to the network entity during the process of initiating registration with the network entity, including: During the process of initiating registration with a network entity, the terminal sends indication information carrying an activated service list and / or a deactivated service list to the network entity.

3. The method according to claim 2, wherein: The activated service list includes one or more service information that needs to be activated, and the deactivated service list includes one or more service information that needs to be deactivated.

4. The method according to claim 3, wherein: The service information includes at least: identification information of the public land mobile network entity PLMN to which the service belongs or identification information of the network slice.

5. The method according to claim 1, wherein: The terminal sends indication information to the network entity, including: The terminal sends a registration request message to the network entity, where the registration request message carries the indication information.

6. The method according to claim 1, wherein: The terminal sends indication information to the network entity, including: The terminal sends a registration completion message to the network entity, where the registration completion message carries the indication information.

7. The method according to claim 1, wherein: The terminal sends indication information to the network entity during the process of initiating registration with the network entity, including: The terminal sends indication information to the network entity during the process of initiating attachment to the network entity.

8. The method according to claim 1, wherein: The terminal sends indication information to the network entity during the process of initiating registration with the network entity, including: The terminal sends indication information to the network entity during the process of initiating location area update to the network entity.

9. The method according to claim 1, wherein: The terminal sends indication information to the network entity during the process of initiating registration with the network entity, including: The terminal sends indication information to the network entity during the process of initiating tracking area update to the network entity.

10. The method according to claim 1, wherein: The indication information is also used to trigger the network entity to release the context of the service that needs to be deactivated.

11. The method according to claim 1, wherein: The indication information is used to trigger the source network entity to perform the following operations: based on the indication information, determine the service to be activated, and send the context of the service to be activated to the destination network entity; The indication information is used to trigger the source network entity to perform the following operations: based on the indication information, determine the service that needs to be deactivated, and delete the context of the service that needs to be deactivated.

12. The method according to claim 1, wherein: The services that need to be activated or deactivated include one or more of the following services: Protocol Data Unit PDU session, Packet Data Network PDN connection, Quality of Service QoS flow, bearer, data flow.

13. The method according to any one of claims 1 to 12, wherein: The network entity is a core network element.

14. A device for activating and deactivating a service, the device comprising: A registration unit configured to initiate a registration process with a network entity; an indication unit, configured to send indication information to the network entity during a registration process with the network entity, wherein the indication information is used to indicate to the network entity a service that needs to be activated and / or a service that needs to be deactivated; Wherein, in the case where a network entity changes, the indication unit is specifically configured to: send indication information to a destination network entity, wherein the indication information is further used to trigger the destination network entity to perform the following operations: send the indication information to a source network entity; receive a context of a service to be activated sent by the source network entity; The network entity is the access and mobility management function AMF.

15. The device according to claim 14, wherein: The indication unit is specifically configured to: in the process of initiating registration with the network entity, send indication information carrying the activation service list and / or the deactivation service list to the network entity.

16. The device according to claim 15, wherein: The activated service list includes one or more service information that needs to be activated, and the deactivated service list includes one or more service information that needs to be deactivated.

17. The device according to claim 16, wherein: The service information includes at least: identification information of the PLMN to which the service belongs or identification information of the network entity slice.

18. The device according to claim 14, wherein: The indication unit is specifically configured to: send a registration request message to the network entity, wherein the registration request message carries the indication information.

19. The device according to claim 14, wherein: The indication unit is specifically configured to: send a registration completion message to the network entity, wherein the registration completion message carries the indication information.

20. The device according to claim 14, wherein: The indication unit is specifically configured to: send indication information to the network entity during the process of initiating attachment to the network entity.

21. The device according to claim 14, wherein: The indication unit is specifically configured to: send indication information to the network entity during the process of initiating location area update to the network entity.

22. The device according to claim 14, wherein: The indication unit is specifically configured to: send indication information to the network entity during the process of initiating tracking area update to the network entity.

23. The device according to claim 14, wherein: The indication information is also used to trigger the network entity to release the context of the service that needs to be deactivated.

24. The device according to claim 14, wherein: The indication information is used to trigger the source network entity to perform the following operations: based on the indication information, determine the service to be activated, and send the context of the service to be activated to the destination network entity; The indication information is used to trigger the source network entity to perform the following operations: based on the indication information, determine the service that needs to be deactivated, and delete the context of the service that needs to be deactivated.

25. The device according to claim 14, wherein: The services that need to be activated or deactivated include one or more of the following services: PDU session, PDN connection, QoS flow, bearer, data flow.

26. The device according to any one of claims 14 to 25, wherein: The network entity is a core network element.

27. A computer storage medium having computer executable instructions stored thereon, wherein the computer executable instructions, when executed by a processor, implement the method steps described in any one of claims 1-13.

Images