Network transfer method, terminal and network-side device

Abstract

The application discloses a network transfer method, a terminal and a network side device, and belongs to the technical field of communication. The method comprises the following steps: a terminal acquires a service currently executed by the terminal; the terminal releases the service currently executed by the terminal in the case that there is no target service in the service currently executed by the terminal; and the terminal executes network transfer of the terminal after releasing the service currently executed by the terminal. Through the application, the problem that the terminal cannot be transferred to a network in the case that the terminal currently exists a non-important service is solved.

Description

Technical Field

[0001] This application belongs to the field of communication technology, specifically relating to a network transfer method, terminal, and network-side equipment. Background Technology

[0002] In the existing technology, if the user equipment (UE) currently has some continuous unimportant services, such as services with low service priority, the UE will continue to camp on the current network, making it impossible to transfer the UE's services to the target network as the network hopes, resulting in the inability to adjust network operation in a timely manner and the waste of communication resources. Summary of the Invention

[0003] This application provides a network transfer method, terminal, and network-side device, which can solve the problem in the prior art where the terminal continues to reside on the current network and cannot achieve network transfer when there are unimportant services currently available on the terminal.

[0004] In a first aspect, a network transfer method is provided, comprising: a terminal acquiring a service currently being executed by the terminal; if no target service exists among the services currently being executed by the terminal, the terminal releasing the service currently being executed by the terminal; and after releasing the service currently being executed by the terminal, the terminal performing a network transfer to the terminal.

[0005] Secondly, a network transfer device is provided, comprising: an acquisition module for acquiring a service currently being executed by a terminal; a release module for releasing the service currently being executed by the terminal if no target service exists among the services currently being executed by the terminal; and an execution module for performing a network transfer to the terminal after releasing the service currently being executed by the terminal.

[0006] Thirdly, a network transfer method is provided, comprising: a network-side device generating and extending roaming (EXT-SOR) corresponding to first information; the network-side device sending the first information to a terminal; wherein the first information indicates that the service with target information is the target service.

[0007] Fourthly, a network transfer device is provided, comprising: a generation module for generating first information corresponding to EXT-SOR; and a second sending module for sending the first information to a terminal; wherein the first information indicates that a service having target information is the target service.

[0008] Fifthly, a terminal is provided, the terminal including a processor, a memory, and a program or instructions stored in the memory and executable on the processor, wherein the program or instructions, when executed by the processor, implement the steps of the method described in the first aspect.

[0009] In a sixth aspect, a network-side device is provided, the network-side device including a processor, a memory, and a program or instructions stored in the memory and executable on the processor, wherein the program or instructions, when executed by the processor, implement the steps of the method described in the third aspect.

[0010] In a seventh aspect, a readable storage medium is provided, on which a program or instructions are stored, which, when executed by a processor, implement the steps of the method described in the first aspect, or implement the steps of the method described in the third aspect.

[0011] Eighthly, a chip is provided, the chip including a processor and a communication interface coupled to the processor, the processor being configured to run network-side device programs or instructions to implement the method as described in the first aspect, or to implement the method as described in the third aspect.

[0012] In this embodiment, the terminal can release the currently executed service and perform network transfer if the target service is not present in the currently executed service. If the target service is a high-priority service, the terminal can release the currently executed service and perform network transfer if no high-priority service is present in the currently executed service. In addition, the target service can also be one or more services specified by the terminal. That is, if none of these specified one or more services are present in the currently executed service, the terminal can also release the currently executed service and perform network transfer. This solves the problem in the prior art where the terminal continues to reside on the current network and cannot perform network transfer when there is an unimportant service present in the terminal. Attached Figure Description

[0013] Figure 1 This diagram illustrates a block diagram of a wireless communication system to which embodiments of this application may be applied;

[0014] Figure 2 This is a flowchart of the network transfer method in an embodiment of this application. Figure 1 ;

[0015] Figure 3 This is a registration flowchart of the network-side device in this application determining whether the EXT-SOR information resides in the VPLMN;

[0016] Figure 4This is a registration flowchart of the network-side device in this application determining whether the EXT-SOR information resides in the HPLMN;

[0017] Figure 5 This is a flowchart of the network transfer method in an embodiment of this application. Figure 2 ;

[0018] Figure 6 This is a flowchart illustrating the process by which the network-side device in this application needs to update the information corresponding to EXT-SOR.

[0019] Figure 7 This is a schematic diagram of the network transfer device structure according to an embodiment of this application. Figure 1 ;

[0020] Figure 8 This is a schematic diagram of the network transfer device structure according to an embodiment of this application. Figure 2 ;

[0021] Figure 9 This is a schematic diagram of the structure of a communication device according to an embodiment of this application;

[0022] Figure 10 A schematic diagram of the hardware structure of a terminal to implement an embodiment of this application;

[0023] Figure 11 This is a schematic diagram of the network-side device according to an embodiment of this application. Detailed Implementation

[0024] The technical solutions of the embodiments of this application will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some embodiments of this application, not all embodiments. Based on the embodiments of this application, all other embodiments obtained by those skilled in the art without creative effort are within the scope of protection of this application.

[0025] The terms "first," "second," etc., used in the specification and claims of this application are used to distinguish similar objects and not to describe a specific order or sequence. It should be understood that such use of data can be interchanged where appropriate so that embodiments of this application can be implemented in orders other than those illustrated or described herein, and the objects distinguished by "first" and "second" are generally of the same class, not limited in number; for example, a first object can be one or more. Furthermore, in the specification and claims, "and / or" indicates at least one of the connected objects, and the character " / " generally indicates that the preceding and following objects are in an "or" relationship.

[0026] It is worth noting that the technologies described in this application are not limited to Long Term Evolution (LTE) / LTE-Advanced (LTE-A) systems, but can also be used in other wireless communication systems, such as Code Division Multiple Access (CDMA), Time Division Multiple Access (TDMA), Frequency Division Multiple Access (FDMA), Orthogonal Frequency Division Multiple Access (OFDMA), Single-carrier Frequency-Division Multiple Access (SC-FDMA), and other systems. The terms "system" and "network" in this application are often used interchangeably, and the described technologies can be used with the systems and radio technologies mentioned above, as well as with other systems and radio technologies. However, the following description describes New Radio (NR) systems for illustrative purposes, and the term NR is used in most of the following description, although these technologies can also be applied to applications other than NR systems, such as 6th generation (6G) radio systems. th Generation 6G communication system.

[0027] Figure 1This diagram illustrates a block diagram of a wireless communication system applicable to embodiments of this application. The wireless communication system includes a terminal 11 and a network-side device 12. The terminal 11 can also be referred to as a terminal device or user equipment (UE). Terminal 11 can be a mobile phone, tablet computer, laptop computer, personal digital assistant (PDA), handheld computer, netbook, ultra-mobile personal computer (UMPC), mobile internet device (MID), wearable device, vehicle-mounted device (VUE), pedestrian terminal (PUE), etc. Wearable devices include wristbands, headphones, glasses, etc. It should be noted that this application does not limit the specific type of terminal 11. Network-side device 12 can be a base station or a core network. The base station can be referred to as a node B, evolved node B, access point, base transceiver station (BTS), radio base station, radio transceiver, basic service set (BSS), extended service set (ESS), B node, evolved B node (eNB), home B node, home evolved B node, WLAN access point, WiFi node, transmitting and receiving point (TRP), or any other suitable term in the field, as long as the same technical effect is achieved. The base station is not limited to specific technical terms. It should be noted that in this application embodiment, only the base station in the NR system is used as an example, but the specific type of base station is not limited.

[0028] The network transfer method provided in this application will be described in detail below with reference to the accompanying drawings, through specific embodiments and application scenarios.

[0029] This application provides a network transfer method. Figure 2 This is a flowchart of the network transfer method in an embodiment of this application. Figure 1 ,like Figure 2 As shown, the steps of this method include:

[0030] Step S202: The terminal obtains the service currently being executed by the terminal;

[0031] Step S204: If the target service does not exist in the services currently being executed by the terminal, the terminal releases the service currently being executed by the terminal.

[0032] Step S206: After releasing the service currently being executed by the terminal, the terminal performs a network transfer to the terminal.

[0033] Through steps S202 to S206 in the embodiments of this application, the terminal can release the currently executed service and transfer the network if the target service does not exist in the currently executed service. If the target service is a high-priority service, the terminal can release the currently executed service and transfer the network if the high-priority service does not exist in the currently executed service. In addition, the target service can also be one or more services specified by the terminal. That is, if the terminal does not have these one or more specified services in the currently executed service, the terminal can also release the currently executed service and transfer the network. This solves the problem in the prior art that when the terminal has an unimportant service, the terminal will continue to reside in the current network and cannot transfer the network.

[0034] In the specific application scenario of this application embodiment, the target service in this application embodiment is preferably a service with a service priority higher than a preset priority.

[0035] Optionally, in this application embodiment, the method by which the terminal determines whether the target service exists in the currently executed service may include the following two methods:

[0036] Method 1) Determine based on the first information corresponding to the EXT-SOR sent by the network-side device. The specific steps are as follows:

[0037] Step S11: The terminal receives the first information corresponding to the Extended Roaming Control (EXT-SOR) sent by the network-side device;

[0038] Step S12: The terminal determines whether the target service exists in the currently executed service based on the first information; wherein, the first information is used to indicate that the service with target information is the target service.

[0039] Method 2) The terminal independently determines whether the target business exists in the currently executed business.

[0040] In other words, in this embodiment of the application, the method by which the terminal determines whether the target service exists in the currently executed service can be determined by the terminal itself, or by information sent by the network-side device.

[0041] For the above method 1), in the optional implementation of the embodiments of this application, the target information in the first information includes at least one of the following: the type of target service, the name of the target service, the number of the target service, the target single network slice selection assistance information (S-NSSAI), the target data network name (DNN), the target 5G quality of service identifier (5QI), the request type of the target PDU session, the target Internet Protocol (IP) address, and the target packet filter.

[0042] In other words, services on Protocol Data Unit (PDU) sessions belonging to the target S-NSSAI are high-priority services; services connected to the target data network (DNN / APN) are high-priority services; services belonging to the target 5QI are high-priority services; certain PDU session request type information; services in PDU sessions established using the target PDUSESSION request type are high-priority services, such as "initialemergency request," "existing emergency PDU session," and "MA PDU request." The IP address of the PDUSESSION; PDU sessions with certain target IP addresses are high-priority services; services whose target communication IP address belongs to a certain address range are high-priority services; services on PDU sessions / QOSFLOW containing the target packet filter are high-priority services.

[0043] Furthermore, regarding the above method 1), it should be noted that the terminal receives the first information transmitted by the network-side device through at least one of the following: a transparent container for SOR, or a transparent container for EXT-SOR. The transparent container for SOR or the transparent container for EXT-SOR includes at least one of the following: EXT-SOR information 1, EXT-SOR information 2, or EXT-SOR security information.

[0044] As shown in Table 1, the IE of a container with an IE of 73 is a pass-through container of SOR.

[0045] IEI Information Element Type / Reference Presence Format Length Extended protocoldiscriminator Extended protocol discriminator9.2 M V 1 Security header type Security header type 9.3 M V 1 / 2 Spare half octet Spare half octet 9.5 M V 1 / 2 Registration accept message identity Message type 9.7 M V 1 5GS registration result 5GS registration result9.11.3.6 M LV 2 77 5G-GUTI 5GS Mobile Identity 9.11.3.4 O TLV-E 14 4A Equivalent PLMNs PLMN list 9.11.3.45 O TLV 5-47 54 TAI list 5GS tracking area identitylist9.11.3.9 O TLV 9-114 15 Allowed NSSAI NSSAI 9.11.3.37 O TLV 4-74 11 Rejected NSSAI Rejected NSSAI9.11.3.46 O TLV 4-42 31 Configured NSSAI NSSAI 9.11.3.37 O TLV 4-146 21 5GS network feature support 5GS network feature support9.11.3.5 O TLV 3-5 50 PDU session status PDU session status 9.11.3.44 O TLV 4-34 26 PDU session reactivationresult PDU session reactivationresult9.11.3.42 O TLV 4-34 72 PDU session reactivationresult error cause PDU session reactivation result errorcause9.11.3.43 O TLV-E 5-515 79 LADN information LADN information 9.11.3.30 O TLV-E 12-1715 B- MICO indication MICO indication 9.11.3.31 O TV 1 9- Network slicing indicator Network slicing indication9.11.3.36 O TV 1 27 Service area list Service area list9.11.3.49 O TLV 6-114 5E T3512 value GPRS timer 39.11.2.5 O TLV 3 5D Non-3GPP de-registrationtimer value GPRS timer 29.11.2.4 O TLV 3 16 T3502 value GPRS timer 29.11.2.4 O TLV 3 34 Emergency number list Emergency number list9.11.3.23 O TLV 5-50 7A Extended emergencynumber list Extended emergency numberlist9.11.3.26 O TLV-E 7-65538 73 SOR transparentcontainer SOR transparent container9.11.3.51 O TLV-E 20-n 78 EAP message EAP message9.11.2.2 O TLV-E 7-1503 A- NSSAI inclusion mode NSSAI inclusion mode9.11.3.37A O TV 1 76 Operator-defined accesscategory definitions Operator-defined access categorydefinitions9.11.3.38 O TLV-E 3-n 51 Negotiated DRXparameters 5GS DRX parameters9.11.3.2A O TLV 3 D- Non-3GPP NW policies Non-3GPP NW providedpolicies9.11.3.36A O TV 1 60 EPS bearer contextstatus EPS bearer context status9.11.3.23A O TLV 4 6E Negotiated extended DRXparameters Extended DRX parameters9.11.3.26A O TLV 3 6C T3447 value GPRS timer 39.11.2.5 O TLV 3 6B T3448 value GPRS timer 39.11.2.4 O TLV 3 6A T3324 value GPRS timer 39.11.2.5 O TLV 3 67 UE radio capability ID UE radio capability ID9.11.3.68 O TLV 3-n 68 UE radio capability IDdeletion indication UE radio capability ID deletionindication9.11.3.69 O TV 1 39 Pending NSSAI NSSAI9.11.3.37 O TLV 4-146 74 Ciphering key data Ciphering key data9.11.3.18C O TLV-E 34-n 75 CAG information list CAG information list9.11.3.18A O TLV-E 3-n 1B Truncated 5G-S-TMSIconfiguration Truncated 5G-S-TMSIconfiguration9.11.3.70 O TLV 3 1C Negotiated WUSassistance information WUS assistance information9.11.3.71 O TLV 3-n 29 Negotiated NB-N1 modeDRX parameters NB-N1 mode DRX parameters9.11.3.73 O TLV 3

[0046] Table 1

[0047] It should be noted that the SOR transparent container is a type 6 information element with a minimum length of 20 octets, as shown in Tables 2 and 3. This includes information 1 of the EXT-SOR and information 2 of the EXT-SOR.

[0048]

[0049] Table 2

[0050]

[0051] Table 3

[0052] Tables 2 and 3 above indicate that the SOR (transparent container information element) carries protected EXT-SOR related information. EXT-SOR information 1 and information 2 are newly added portions of the EXT-SOR related information, such as information indicating high-priority services. SOR header-new, SOR-MAC-IAUSF-new, and CounterSOR-new are the parts that need modification. They need to be modified to indicate that the SOR transparent containerIE contains EXT-SOR information 1 (EXT-SOR related information protected by USIM, etc.) or EXT-SOR information 2 (EXT-SOR related information not protected by USIM, etc.), as well as related security information, as shown in Table 4.

[0053]

[0054] Table 4

[0055] Whether to carry EXT-SOR information (octet 4, bit 6):

[0056] 0 indicates that the SOR transparent container does not carry EXT-SOR information;

[0057] 1 indicates that the SOR transparent container carries EXT-SOR information;

[0058] Furthermore, the calculation of SOR-MAC-IAUSF-new also corresponds to the content of the SOR transparent container IE. That is, if the SOR transparent container IE carries EXT-SOR, then the calculation process of SOR-MAC-IAUSF-new also includes EXT-SOR; if the SOR transparent container IE does not carry EXT-SOR, then the calculation process of SOR-MAC-IAUSF-new does not include EXT-SOR.

[0059] CounterSOR-new also corresponds to the content of the SOR transparent container IE. That is, if the SOR transparent container IE carries EXT-SOR, then the calculation process of SOR-MAC-IAUSF-new also reflects the existence (or transmission) of EXT-SOR; if the SOR transparent container IE does not carry EXT-SOR, then the calculation process of SOR-MAC-IAUSF-new does not reflect the existence (or transmission) of EXT-SOR.

[0060] As shown in Table 5, IE also includes a pass-through container for EXT-SOR;

[0061] IEI Information Element Type / Reference Presence Format Length Extended protocoldiscriminator Extended protocol discriminator9.2 M V 1 Security header type Security header type9.3 M V 1 / 2 Spare half octet Spare half octet9.5 M V 1 / 2 Registration acceptmessage identity Message type9.7 M V 1 5GS registration result 5GS registration result9.11.3.6 M LV 2 77 5G-GUTI 5GS mobile identity9.11.3.4 O TLV-E 14 4A Equivalent PLMNs PLMN list9.11.3.45 O TLV 5-47 54 TAI list 5GS tracking area identitylist9.11.3.9 O TLV 9-114 15 Allowed NSSAI NSSAI9.11.3.37 O TLV 4-74 11 Rejected NSSAI Rejected NSSAI9.11.3.46 O TLV 4-42 31 Configured NSSAI NSSAI9.11.3.37 O TLV 4-146 21 5GS network featuresupport 5GS network feature support9.11.3.5 O TLV 3-5 50 PDU session status PDU session status9.11.3.44 O TLV 4-34 26 PDU session reactivationresult PDU session reactivationresult9.11.3.42 O TLV 4-34 72 PDU session reactivationresult error cause PDU session reactivation resulterror cause9.11.3.43 O TLV-E 5-515 79 LADN information LADN information9.11.3.30 O TLV-E 12-1715 B- MICO indication MICO indication9.11.3.31 O TV 1 9- Network slicing indication Network slicing indication9.11.3.36 O TV 1 27 Service area list Service area list9.11.3.49 O TLV 6-114 5E T3512 value GPRS timer 39.11.2.5 O TLV 3 5D Non-3GPP de-registrationtimer value GPRS timer 29.11.2.4 O TLV 3 16 T3502 value GPRS timer 29.11.2.4 O TLV 3 34 Emergency number list Emergency number list9.11.3.23 O TLV 5-50 7A Extended emergency numberlist Extended emergency numberlist9.11.3.26 O TLV-E 7-65538 73 SOR transparent container SOR transparent container9.11.3.51 O TLV-E 20-n 78 EAP message EAP message9.11.2.2 O TLV-E 7-1503 A- NSSAI inclusion mode NSSAI inclusion mode9.11.3.37A O TV 1 76 Operator-defined accesscategory definitions Operator-defined access categorydefinitions9.11.3.38 O TLV-E 3-n 51 Negotiated DRX parameters 5GS DRX parameters9.11.3.2A O TLV 3 D- Non-3GPP NW policies Non-3GPP NW providedpolicies9.11.3.36A O TV 1 60 EPS bearer context status EPS bearer context status9.11.3.23A O TLV 4 6E Negotiated extended DRXparameters Extended DRX parameters9.11.3.26A O TLV 3 6C T3447 value GPRS timer 39.11.2.5 O TLV 3 6B T3448 value GPRS timer 39.11.2.4 O TLV 3 6A T3324 value GPRS timer 39.11.2.5 O TLV 3 67 UE radio capability ID UE radio capability ID9.11.3.68 O TLV 3-n 68 UE radio capability IDdeletion indication UE radio capability ID deletionindication9.11.3.69 O TV 1 39 Pending NSSAI NSSAI9.11.3.37 O TLV 4-146 74 Ciphering key data Ciphering key data9.11.3.18C O TLV-E 34-n 75 CAG information list CAG information list9.11.3.18A O TLV-E 3-n 1B Truncated 5G-S-TMSIconfiguration Truncated 5G-S-TMSIconfiguration9.11.3.70 O TLV 3 1C Negotiated WUS assistanceinformation WUS assistance information9.11.3.71 O TLV 3-n 29 Negotiated NB-N1 mode DRXparameters NB-N1 mode DRX parameters9.11.3.73 O TLV 3 EXT-SOR transparentcontainer

[0062] Table 5

[0063] The EXT-SOR pass-through container is used by the IE to carry EXT-SOR related information, such as EXT-SOR information 1 or 2, and can also carry EXT-SOR security information, such as MAC address, counter, etc. See Table 6 for details.

[0064]

[0065] Table 6

[0066] The EXT-SOR header indicates the characteristics of the EXT-SOR, such as whether it is EXT-SOR information sent from the network to the UE or EXT-SOR information sent from the UE to the network; and the valid scope of the EXT-SOR information, such as whether there are time restrictions or PLMN restrictions, etc.

[0067] EXT-SOR-MAC-1 represents the checksum generated after performing the integrity protection algorithm on EXT-SOR information 1 or 2;

[0068] CountereEXT-SOR represents the count value required to perform the integrity protection algorithm on EXT-SOR information 1 or 2.

[0069] In an optional embodiment of this application, based on the above method 1), the method of receiving the first information corresponding to the extended roaming control EXT-SOR sent by the network-side device in step S11 may further include:

[0070] Step S11-1: The terminal sends a notification message to the network-side device; wherein, the notification message is used to notify the network-side device that the terminal supports EXT-SOR capability;

[0071] Step S11-2: The terminal receives the first information corresponding to EXT-SOR sent by the network-side device.

[0072] Regarding the method of the terminal sending a notification message to the network-side device involved in step S11-1 above, for the network-side device, taking the registration request message to notify the terminal of EXT-SOR capability as an example in a specific application scenario, the process includes:

[0073] Step S21: The network-side device checks whether the registration request message sent by the terminal indicates "UE supports EXT-SOR capability". If it does, proceed to step S23; otherwise, proceed to step 22.

[0074] Step S22: The network-side device determines that the terminal does not support the EXT-SOR function;

[0075] Step S23: The network-side device determines that the terminal supports the EXT-SOR function. The VPLMN AMF needs to obtain the EXT-SOR-related information of the UE from the HPLMN;

[0076] Step S24: AMF determines whether it already has the latest EXT-SOR related information; if it does, proceed to step S25; if not, proceed to step S26.

[0077] In step S25, under certain special scenarios, such as initial registration or emergency registration, the Home Public Land Mobile Network (HPLMN) Unified Data Management (UDM) may request the Access and Mobility Management Function (AMF) to re-acquire EXT-SOR related information from the HPLMN UDM. Therefore, the Visited Public Land Mobile Network (VPLMN) AMF determines whether the current scenario falls under this category. If so, step S26 is executed. Otherwise, the information is not re-acquired.

[0078] Step S26: The VPLMN AMF requests information related to EXT-SOR from the HPLMN UDM.

[0079] In another optional embodiment of this application, for the network-side device, in a specific application scenario, it is also possible to determine whether the terminal supports EXT-SOR capability through subscription information. The specific process is as follows:

[0080] Step S31: After receiving the registration request message, the VPLMN AMF determines whether the UE supports EXT-SOR capability based on the UE's subscription information.

[0081] If the UE's subscription information is not in the VPLMN AMF, the subscription information of the UE is obtained from the HPLLMN UDM first; if the UE does not support the EXT-SOR function, the EXT-SOR related behavior is stopped; otherwise, step S32 is executed.

[0082] In step S32, the AMF decides how to obtain information related to EXT-SOR;

[0083] It should be noted that the specific process of step S32 is equivalent to steps S23 to S26 above.

[0084] It should be noted that the notification message uses the 5GMM (5G System Mobility Management) capability to indicate to the network-side device that the terminal supports EXT-SOR capability; in specific application scenarios, this 5GMM capability is shown as IE with IEI of 10 in Table 7:

[0085] IEI Information Element Type / Reference Presence Format Length Extended protocol discriminator Extended Protocoldiscriminator9.2 M V 1 Security header type Security header type9.3 M V 1 / 2 Spare half octet Spare half octet9.5 M V 1 / 2 Registration request messageidentity Message type9.7 M V 1 5GS registration type 5GS registration type9.11.3.7 M V 1 / 2 ngKSI NAS key setidentifier9.11.3.32 M V 1 / 2 5GS mobile identity 5GS mobile identity9.11.3.4 M LV-E 6-n C- Non-current native NAS key setidentifier NAS key setidentifier9.11.3.32 O TV 1 10 5GMM capability 5GMM capability9.11.3.1 O TLV 3-15 2E UE security capability UE securitycapability9.11.3.54 O TLV 4-10 2F Requested NSSAI NSSAI9.11.3.37 O TLV 4-74 52 Last visited registered TAI 5GS tracking areaidentity9.11.3.8 O TV 7 17 S1 UE network capability S1 UE networkcapability9.11.3.48 O TLV 4-15 40 Uplink data status Uplink data status9.11.3.57 O TLV 4-34 50 PDU session status PDU session status9.11.3.44 O TLV 4-34 B- MICO indication MICO indication9.11.3.31 O TV 1 2B UE status UE status9.11.3.56 O TLV 3 77 Additional GUTI 5GS mobile identity9.11.3.4 O TLV-E 14 25 Allowed PDU session status Allowed PDU sessionstatus9.11.3.13 O TLV 4-34 18 UE's usage setting UE's usage setting9.11.3.55 O TLV 3 51 Requested DRX parameters 5GS DRX parameters9.11.3.2A O TLV 3 70 EPS NAS message container EPS NAS messagecontainer9.11.3.24 O TLV-E 4-n 74 LADN indication LADN indication9.11.3.29 O TLV-E 3-811 8- Payload container type Payload containertype9.11.3.40 O TV 1 7B Payload container Payload container9.11.3.39 O TLV-E 4-65538 9- Network slicing indication Network slicingindication9.11.3.36 O TV 1 53 5GS update type 5GS update type9.11.3.9A O TLV 3 41 Mobile station classmark 2 Mobile station classmark29.11.3.31C O TLV 5 42 Supported codecs Supported codec list9.11.3.51A O TLV 5-n 71 NAS message container NAS message container9.11.3.33 O TLV-E 4-n 60 EPS bearer context status EPS bearer contextstatus9.11.3.23A O TLV 4 6E Requested extended DRXparameters Extended DRXparameters9.11.3.26A O TLV 3 6A T3324 value GPRS timer 39.11.2.5 O TLV 3 67 UE radio capability ID UE radio capabilityID9.11.3.68 O TLV 3-n 35 Requested mapped NSSAI Mapped NSSAI9.11.3.31B O TLV 3-42 48 Additional informationrequested Additional informationrequested9.11.3.12A O TLV 3 1A Requested WUS assistanceinformation WUS assistanceinformation9.11.3.71 O TLV 3-n XX N5GC indication N5GC indication9.11.3.72 O T 1 30 Requested NB-N1 mode DRXparameters NB-N1 mode DRXparameters9.11.3.73 O TLV 3

[0086] Table 7

[0087] Furthermore, the purpose of the 5GMM capability information element is to provide the network with information about UEs related to 5GCN or interoperable with EPS. This content may affect how the network processes UE operations.

[0088] The encoding of 5GMM capability information elements is shown in Table 8. Among them, 5GMM capability is a type 4 information element with a minimum length of 3 octets and a maximum length of 15 octets.

[0089]

[0090] Table 8

[0091] The EXT-SOR capability (octet 5, bit 5) is 0 when it indicates that the EXT-SOR capability is not supported, and 1 when it indicates that the EXT-SOR capability is supported.

[0092] Optionally, the notification message in the embodiments of this application includes at least one of the following: registration request message, uplink non-transport layer transmission message, and protocol data unit session message.

[0093] Optionally, in this embodiment of the application, the method of determining whether the target business exists in the currently executed business based on the first information in step 12 of the above method 1) includes one of the following:

[0094] (1) The terminal determines whether the target service exists in the service it is currently executing based on the first information;

[0095] (2) The terminal determines whether the target service exists in the currently executed service based on the first information, and / or the contract information stored by the terminal, and / or the target service agreed upon by the terminal and the network side equipment, and / or the target service customized by the terminal.

[0096] In other words, the terminal can determine whether the target service exists in the service it is executing based solely on the first piece of information, or it can further combine other methods to determine it, such as the target service agreed upon by the terminal and the network-side equipment.

[0097] In optional embodiments of this application, the method of releasing the currently executed service by the terminal in step S204 of this application may further include:

[0098] Step S204-11: The terminal immediately releases the currently executed service according to the instruction of the first information; or,

[0099] Step S204-12: Release the currently executed service of the terminal after a preset time period according to the indication of the first information.

[0100] Step S204-12 may further include: the terminal starts a timer according to the instruction of the first information, and releases the service currently being executed by the terminal when the timer expires.

[0101] Through the above steps S204-11 and S204-12, the terminal can immediately release the service currently being executed by the terminal, or it can release it after a certain period of time by using a timer.

[0102] In optional embodiments of this application, the method steps may further include:

[0103] Step S208: Before the timer expires, the terminal receives the second information corresponding to EXT-SOR sent by the network-side device, wherein the second information is the updated information of the first information;

[0104] Step S210: The terminal stops running the timer and overwrites the first information with the second information, and determines whether the target service exists in the service currently being executed by the terminal based on the second information; or, the terminal discards the second information and releases the service currently being executed by the terminal based on the first information if the timer times out.

[0105] As can be seen from steps S208 and S210 above, the network-side device can continuously send information corresponding to the EXT-SOR to the terminal. Whether the terminal needs to use the later received information to overwrite the earlier information after receiving multiple EXT-SOR-corresponding messages is determined by the terminal itself. This is because the target services indicated by the later received EXT-SOR-corresponding messages may not be entirely the same.

[0106] The method mentioned in method 2) above, which involves the terminal independently determining whether the target service exists in the currently executed service, can further include: the terminal independently determining whether the target service exists in the currently executed service based on the subscription information stored by the terminal, and / or the target service agreed upon by the terminal and the network-side equipment, and / or the target service customized by the terminal.

[0107] Based on the above method 2), the method for the terminal to release the currently executed service can further include: the terminal determines to immediately release the currently executed service; or, the terminal determines to release the currently executed service after a custom preset time period.

[0108] Based on the above method 2), the method of releasing the currently executed service of the terminal after a preset time period can further include: the terminal determines to start a timer, and releases the currently executed service of the terminal when the timer expires.

[0109] In optional embodiments of this application, the method steps may further include:

[0110] Step S212: If the target service exists in the currently executed service, determine whether the target service has ended.

[0111] Step S214: If the target service has ended, determine that the target service does not exist in the currently executed services.

[0112] As can be seen from the above steps S212 and S214, if the target service exists in the currently executed service, it will only be determined that the target service does not exist in the currently executed service after the target service has ended. For example, if the target service is a high-priority service, the presence of a high-priority service in the currently executed service indicates that the terminal has a relatively important service to execute and cannot perform network transfer. Only after the currently executed high-priority service ends will it be considered that the relatively important service has ended and the currently executed service is not an important service, and then network transfer can be performed.

[0113] Based on the above method 1), the method steps of this application embodiment may further include:

[0114] Step S216: The terminal determines whether the visited Public Land Mobile Network (VPLMN) in the network-side equipment has changed;

[0115] In step S218, if the VPLMN changes, the terminal deletes the first information or determines whether the target service exists in the currently executed service based on the first information.

[0116] As can be seen from the above steps S216 and S218, if the VPLMN changes, the terminal can delete the first information or continue to determine whether the target service exists in the currently executed service based on the first information. The specific method to be used can be determined according to the actual situation.

[0117] Based on the above method 1), after receiving the first information sent by the network-side device, the method of this application embodiment may further include:

[0118] Step S220: Perform security checks on the first information; wherein, the security checks include integrity checks and / or decryption checks;

[0119] Step S222: If the first information security test passes, determine whether the VPLMN in the network-side device has been changed;

[0120] Step S224: If the VPLMN in the network-side device has not been changed, send feedback information to the network-side device, wherein the feedback information is used to indicate that the terminal has received the first information.

[0121] The method of sending feedback information to the network-side device involved in step S224 may further include:

[0122] Step S224-11: Protect the feedback information; wherein, the protection includes integrity protection and / or encryption protection;

[0123] Step S224-12: Send the protected feedback information to the network-side device via a registration end message or an uplink non-access stratum transmission message.

[0124] Through steps S220 to S224, the terminal needs to perform security checks on the received first information because the first information sent by the network-side device may be of low security, potentially leading to erroneous network transfer operations based on such information. Similarly, the terminal also needs to protect the feedback information sent to the network-side device to ensure its security.

[0125] It should be noted that the key used for this protection is generated during the authentication process between the UE and the network and can be confirmed during the security process; the protection can use the KDF algorithm, for example, by generating a checksum through the KDF algorithm.

[0126] In a specific application scenario of this application embodiment, the feedback information indicates that the terminal has received the first information via SOR header-new or EXT-SOR header-new; wherein, SOR header-new is shown in Table 9;

[0127]

[0128] Table 9

[0129] The SOR header-new contains information that instructs the UE to report to the network that it has successfully received the EXT-SOR, as shown in Table 10.

[0130]

[0131] Table 10

[0132] When the EXT-SOR data type is 0, it indicates that the EXT-SOR transparent container carries extended control for roaming information. When the EXT-SOR data type is 1, it indicates that the EXT-SOR transparent container carries confirmation of successful reception of extended control for roaming information.

[0133] In addition, SOR-MAC-IUE-new: performs an integrity-protected checksum on the SOR header-new information.

[0134] Among them, EXT-SOR header-new is shown in Table 11;

[0135]

[0136] Table 11

[0137] The EXT-SOR header-new contains information that instructs the UE to report to the network that it has successfully received the EXT-SOR, as shown in Table 12.

[0138]

[0139] Table 12

[0140] When the EXT-SOR data type is 0, it indicates that the EXT-SOR transparent container carries extended control for roaming information. When the EXT-SOR data type is 1, it indicates that the EXT-SOR transparent container carries confirmation of successful reception of extended control for roaming information.

[0141] In addition, EXT-SOR-MAC-IUE-new: a checksum after integrity protection is performed on the EXT-SOR header-new information; EXT-SOR transparent container IEI: the cell identification identifier corresponding to the new EXT-SOR transparent container;

[0142] In an optional embodiment of this application, after receiving the first information, the method steps in this application embodiment may further include:

[0143] Step S226: The terminal saves the first information to the user service identification module USIM or the mobile device ME.

[0144] In another optional embodiment of this application, the method steps of this application embodiment may further include:

[0145] In step S228, the terminal interacts with the user to exchange first information via the AT interface.

[0146] In specific application scenarios, the way the terminal interacts with the user to exchange first information via the AT interface can be:

[0147] (1) The terminal can interact with the user through the AT interface to exchange EXT-SOR related information; that is, the user can query the UE for EXT-SOR related information through the AT interface; and the user can also set whether the UE actively reports changes to EXT-SOR related information through the AT interface.

[0148] (2) The terminal can show the EXT-SOR information received by the UE to the user through the AT interface, and can also show the EXT-SOR information stored in the UE to the user through the AT interface;

[0149] (3) The UE can proactively display information to the user, for example, when it receives EXT-SOR related information from the network-side device, it can display the information to the user, or when the user queries, it can provide feedback on EXT-SOR related information to the user; the EXT-SOR related information may also include information such as the target PLMN that the network-side device wants the UE to transfer to.

[0150] The following example illustrates the entire registration process in this application embodiment, taking the registration process where the network-side device determines whether the EXT-SOR information resides in the VPLMN as an example. Figure 3 As shown, the registration process includes the following steps:

[0151] In step S301, the UE can check its EXT-SOR capability. If it supports the EXT-SOR capability, it will carry an indication in the REG REQ message that the UE supports the EXT-SOR capability; if it does not support the EXT-SOR capability, it will not carry this indication.

[0152] It should be noted that the UE may also choose not to check its EXT-SOR capability. That is, the indication that "UE supports EXT-SOR capability" is not sent to the network-side device in the air interface message, but is determined by the network-side device based on the subscription information stored by the network-side device. In this case, the UE and the HPLMN UDM need to store the subscription information of the UE and the network-side device, such as the UE's EXT-SOR capability, and / or whether the UE requests the network-side device to return EXT-SOR related information in certain scenarios, such as during the registration process.

[0153] Step S302: The UE sends a registration request message to the network-side device;

[0154] Step S303: The network-side device and the UE complete mutual authentication and key negotiation;

[0155] After receiving the UE's registration request message, the network-side device triggers the authentication and key negotiation process. This authentication includes the network-side device's assessment of the terminal's legitimacy and the terminal's assessment of the network-side device's legitimacy; this authentication can be performed using the 5G-AKA or EAP-AKA algorithm.

[0156] During the authentication process, the network-side device and the terminal can negotiate a key KEY1, which will be used in the subsequent EXT-SOR transmission and inspection; this key KEY1 is stored in both the HPLMN and the UE.

[0157] If, during the authentication process, the UE or network-side device finds that it cannot verify the trustworthiness of the other party's identity, it will stop the subsequent EXT-SOR process and end the registration process.

[0158] If, during the authentication process, the UE and the network-side device mutually confirm the reliability of each other's identities, negotiate a key, and determine that the key will be used subsequently, then proceed to step 104.

[0159] In step S304, the VPLMN AMF determines whether it is necessary to obtain EXT-SOR related information for the UE from the HPLMMN UDM.

[0160] In addition, the judgment process may also include:

[0161] VPLMN AMF can assist in making judgments based on the operator's configuration;

[0162] If it is necessary to obtain EXT-SOR related information for the UE from the HPLMN UDM, then execute 105;

[0163] If it is not necessary to obtain the EXT-SOR related information of the UE from the HPLMN UDM, then proceed with the existing registration process;

[0164] In step S305, the VPLMN AMF requests EXT-SOR related information for the UE from the HPLMN UDM, such as subscription information; or, the VPLMN AMF provides relevant information to the HPLMN UDM, including: UE ID (identity identifier of the terminal), indication of requesting EXT-SOR related information, UE's current location information, such as geographical location, PLMN ID (identifier of home public terrestrial mobile network), TA, CELL, etc.

[0165] The Nudm_SDM_Get interface can be used to request EXT-SOR related information for the UE from the HPLMN UDM;

[0166] Step S306: HPLM NUMBER UDM prepares information related to EXT-SOR;

[0167] Among them, HPLMN UDM prepares information related to EXT-SOR;

[0168] (1) After judgment, the HPLMN UDM decides to perform the EXT-SOR function on the UE; the judgment can be based on the UE's subscription information, or on the HPLMN's configuration information, current load, etc.

[0169] HPLMN UDM can determine whether to provide the UE's EXT-SOR related information independently or to obtain it through the network-side device function EXT-SOR-AF. This determination can be based on HPLMN policies, such as whether HPLMN has a policy for invoking EXT-SOR-AF; or it can be based on the current configuration, such as whether HPLMN has EXT-SOR-AF configured.

[0170] If the HPLMN UDM obtains the EXT-SOR-AF information, proceed to step S307; if the HPLMN UDM determines the EXT-SOR-related information for the UE itself, proceed to step S310.

[0171] (2) If the HPLMN UDM decides not to perform the EXT-SOR function for the UE temporarily, for example, if the HPLMN cannot calculate the EXT-SOR related information on its own or obtain the EXT-SOR related information from the EXT-SOR-AF, then it will notify the UE in some way, instructing the HPLMN not to require the UE to perform the EXT-SOR function. This method may include: 1) not returning the EXT-SOR related information to the UE, 2) or returning the information indicating "the HPLMN does not require the UE to perform the EXT-SOR function"; when the HPLMN UDM wants to notify the UE to update the EXT-SOR related information after registration, it can be handled through the EXT-SOR update process.

[0172] Step S307: HPLMN UDM requests EXT-SOR related information from EXT-SOR-AF;

[0173] When the HPLMN UDM requests EXT-SOR related information from the EXT-SOR-AF, it can provide: UE ID, an indication of requesting EXT-SOR related information, and carry the UE's current location information, such as geographical location, VPLMN ID, TA, CELL, etc.

[0174] Step S308, EXT-SOR-AF prepares EXT-SOR related information for HPLM NUMBER UDM;

[0175] Among them, the EXT-SOR-AF prepared for the HPLM NUMBER UDM can be in plaintext or a protected data packet 1. This protected data packet 1 can only be parsed by certain network-side devices that can trust it, such as USIM or a certain encryption / decryption program stored in ME.

[0176] Step S309, EXT-SOR-AF sends the EXT-SOR related information to HPLM NUMBER UDM;

[0177] In step S310, the HPLMN UDM decides to protect the information related to EXT-SOR;

[0178] One purpose of this protection is to prevent the VPLMN from tampering with it; once the VPLMN is tampered with, the UE can identify the tampering when deprotecting.

[0179] This decision can be made after evaluation, for example, the PLMN where the current UE is located is a VPLMN, or an untrusted network-side device or area; the EXT-SOR related information can be plaintext EXT-SOR related information or protected EXT-SOR related information, such as data packet 1;

[0180] Step S311, HPLMN UDM sends the EXT-SOR related information to the functional unit responsible for protecting the data, such as AUSF;

[0181] Step S312: The Authorization Server Function (AUSF) protects the received EXT-SOR;

[0182] The protection algorithm will use the key negotiated in step S303;

[0183] Step S313: AUSF sends the protected EXT-SOR related information to HPLM NUMBER UDM;

[0184] Step S314: HPLM NUMBER UDM sends the protected EXT-SOR related information to VPLMN AMF;

[0185] In step S315, the VPLMN AMF forwards the information related to the protected EXT-SOR to the UE;

[0186] Among them, VPLMN AMF puts the information related to the protected EXT-SOR into the registration success message, namely the REGISTRATION ACCEPT message;

[0187] Step S316: The UE processes the information related to the protected EXT-SOR;

[0188] After receiving the REGISTRATION ACCEPT message, the UE processes the information related to the protected EXT-SOR.

[0189] Step S317, UE feedback REGISTRATION COMPLETE;

[0190] If the UE checks and finds that the VPLMN has not tampered with or discarded the protected EXT-SOR related information, the UE will send feedback to the HPLMMN that it has received the EXT-SOR related information. This feedback information can be included in the REGISTRATION COMPLETE.

[0191] Step S318, the VPLMN AMF determines whether the message sent by the UE contains the information corresponding to the EXT-SOR confirmation that it has been received;

[0192] If the VPLMN AMF finds an EXT-SOR confirmation message in the REGISTRATION COMPLETE message after receiving it, it decides to forward the confirmation message to the HPLMN UDM.

[0193] In step S319, the VPLMN AMF forwards the confirmation information to the HPLMN UDM;

[0194] Step S320: HPLM NUMBER UDM checks the confirmation information of EXT-SOR;

[0195] Step S321, HPLM NUMBER UDM forwards this confirmation message to EXT-SOR-AF;

[0196] If EXT-SOR-AF requests the UE to confirm receipt of EXT-SOR related information, then HPLMN UDM forwards this confirmation information to EXT-SOR-AF.

[0197] Step S322, EXT-SOR-AF checks this EXT-SOR confirmation information;

[0198] If successful, the process ends; if it fails, EXT-SOR-AF can resend the EXT-SOR related information; after the resend requirement is reached, the VPLMN can be considered unreliable, and the UE is required to leave the current VPLMN, for example, by registering with DE-REGISTRATION in the current VPLMN.

[0199] It should be noted that the network-side device can also reside on the HPLMN to determine the EXT-SOR information. When the UE is residing on the HPLMN, since the HPLMN is trusted, it can use a protected approach when instructing the UE on EXT-SOR related information, i.e., obtaining the EXT-SOR related information in the same way as when the UE is residing on the VPLMN; the process is the same as the registration process for CAMP (residing) on ​​the VPLMN. Alternatively, it can use an unprotected approach, where the HPLMN UDM sends the EXT-SOR related information to the HPLMN AMF in plaintext. The HPLMN AMF then sends this information to the UE in an air interface NAS message. The HPLMN AMF will decide whether to provide security protection for this NAS message, such as encryption and integrity protection, based on existing protocol requirements. Figure 4 As shown, the registration process includes:

[0200] Step S401: When the UE is residing in the HPLMN, it initiates registration and completes authentication and security.

[0201] Step S402, AMF determines whether to request EXT-SOR related information from UDM;

[0202] It should be noted that steps S403 to S407 are the same as steps S305 to S309;

[0203] In step S408, the UDM determines that the UE is currently in the HPLMN and decides not to protect the EXT-SOR related information.

[0204] Step S409, UDM sends information related to the unprotected EXT-SOR to HPLMAN AMF;

[0205] In step S410, the HPLMN AMF puts the information related to the unprotected EXT-SOR into the registration success message and sends it to the UE;

[0206] Based on its current location within the HPLMN, the UE determines that it can accept information related to unprotected EXT-SOR.

[0207] The processing of EXT-SOR related information is the same as in steps S504~S512; if it is necessary to provide feedback to HPLM NUMBER UDM that EXT-SOR related information has been received, the plaintext of the feedback information can be placed in the registration end message and sent to the network.

[0208] In a specific application scenario of this application embodiment, based on the above steps S301 to S322, the process of the UE processing the information corresponding to the EXT-SOR sent by the network may further include:

[0209] Step S501: The UE receives a NAS message from the network;

[0210] Step S502: The UE checks whether the NAS message contains EXT-SOR related information. If the UE finds that the network does not provide EXT-SOR related parameters, it will not perform the EXT-SOR function. At this time, the UE may assume that the network does not want the UE to perform this function, or it may assume that the VPLMN is involved. If the EXT-SOR related information is included, proceed to step S503.

[0211] Step S503: The UE performs a security check on the EXT-SOR related information to determine whether the VPLMN has tampered with the EXT-SOR.

[0212] If the security check is successful, proceed to step S503-11; otherwise, proceed to step S513.

[0213] Step S503-11: The UE checks whether the PLMN in which the UE is currently located meets the conditions of the PLMN.

[0214] If the current PLMN is a qualified PLMN, for example, not HPLMM, but EHPLMN, or UserControlled PLMN Selector with Access Technology, go to S503-13 and check the conditions of the network selection mode.

[0215] If the current PLMN is not a compliant PLMN, for example, it is an HPLMM, EHPLMN, or UserControlled PLMN Selector with Access Technology, proceed to step S503-12.

[0216] Step S503-12, the UE saves the received EXT-SOR related information;

[0217] If the current PLMN changes, i.e., it moves from an ineligible PLMN to another ineligible PLMN, the EXT-SOR related information may remain valid or may be considered invalid.

[0218] If the current PLMN changes, i.e., it moves from a non-compliant PLMN to a compliant PLMN, the EXT-SOR related information can remain valid or be deleted.

[0219] Step S503-13: The UE checks whether its current network selection mode is automatic network selection mode. If it is in automatic network selection mode, proceed to step S504; if it is in manual network selection mode, save the received EXT-SOR related information and do not execute it for the time being.

[0220] If the UE enters the automatic network selection mode from the manual network selection mode, it needs to enter step S503-11 again;

[0221] It can further check whether the VPLMN in the current automatic network selection mode is the same VPLMN that received the currently saved EXT-SOR; and based on the check result, further determine the UE's subsequent action 1. The UE's subsequent action 1 may include:

[0222] 1) If the current VPLMN is the VPLMN that receives the currently saved EXT-SOR, then the currently saved EXT-SOR is considered to remain valid;

[0223] 2) If the current VPLMN is no longer the VPLMN that receives the currently saved EXT-SOR, then the currently saved EXT-SOR is considered to remain valid;

[0224] 3) If the current VPLMN is no longer the VPLMN that receives the currently saved EXT-SOR, then the currently saved EXT-SOR is considered invalid.

[0225] Step S504: The UE checks whether the EXT-SOR needs to be sent to the USIM or a special program for parsing. If so, proceed to step S505; otherwise, write the relevant information after the EXT-SOR is deprotected into the ME, and then proceed to step S506.

[0226] The conditions for entering S504 include: the UE being in VPLMN, the UE being in automatic network selection mode, and EXT-SOR security checks. The order is not restricted, as long as these conditions are met simultaneously.

[0227] In step S505, dedicated programs such as USIM parse the EXT-SOR related information, send the parsed EXT-SOR related information to the UE, and then execute step S506.

[0228] Step S506: The UE uses this parameter to check whether there is a high-priority service currently being executed; if so, proceed to step S507; otherwise, proceed to step S507.

[0229] In addition, the UE can also use its own defined criteria to check whether there are high-priority services. For example, if the UE considers a certain service being executed to be a high-priority service, that service may not be within the scope of high-priority services recognized by the network.

[0230] The standard defined by the UE can be user-defined or predefined by the UE. If it is user-defined, the user can query, set, modify, and delete the EXT-SOR related parameters stored in the UE. The UE can also actively report changes to this parameter to the user. The user's operation on the EXT-SOR related parameters in the UE can be through the AT command interface, the API interface, or other message interfaces.

[0231] Step S507: The UE saves the EXT-SOR related information. If the UE already has EXT-SOR related information saved, the existing EXT-SOR related information is overwritten. When saving the EXT-SOR related information, the UE can save the corresponding current VPLMN information, such as the VPLMN ID, indicating that the EXT-SOR related information was received under this VPLMN.

[0232] In step S508, the UE can wait until the high priority on going service ends before continuing to apply the EXT-SOR related information saved by the UE, regardless of whether the PLMN where the UE is located has changed.

[0233] If a UE detects a PLMN change during the execution of a high-priority service, it can assume that the EXT-SOR-related information received under the previous PLMN remains valid; or it can assume that the information becomes invalid.

[0234] Step S509: Does the UE currently have any services that are not high-priority and are being executed? If so, proceed to S510; otherwise, the UE releases the connection, enters IDLE state, and proceeds to step S512.

[0235] In step S510, the UE calculates the time required to stop the current service and determines the duration of timer TIMER1. This duration can be set to a default value, or it can be determined by the UE based on its implementation, or it can be negotiated with the network, or the network can provide indication information in the air interface message, and the UE can further determine the duration of timer TIMER1 based on the indication information; or it can be limited to a maximum value, and the duration cannot be greater than this maximum value.

[0236] If the current timer is not running, start timer TIMER1;

[0237] If a change occurs to the current service PLMN during the operation of the timer, then: the currently stored EXT-SOR related information can be considered invalid; or the currently stored EXT-SOR related information can be considered still valid, and then a judgment can be made according to the principles in step S503-11.

[0238] Step S511: After the timer expires, the UE checks and meets all the above conditions, releases the current service, releases the NAS signaling connection, enters the IDLE state, and executes step S512; if not, it continues this step.

[0239] The phrase "meeting all the above conditions" means that: the EXT-SOR has successfully passed the security check; the current PLMN is a VPLMN with User Controlled PLMN Selector and Access Technology; there are no high-priority services; automatic network selection mode is in place; and the timer duration meets the requirements.

[0240] The release of the current service in step S511 includes the following scenarios:

[0241] Scenario 1: If there are high-priority services among the services currently being executed by the terminal, it is necessary to determine whether the high-priority services have ended. For example, if the priority service is downgraded or the high-priority service is stopped, the services of the current terminal can be released after "all the above conditions are met".

[0242] Scenario 2: If the current terminal only has low-priority services, then the services of the current terminal will be released after "all the above conditions are met".

[0243] Scenario 3: If the terminal currently only has low-priority services, and the terminal stops the low-priority service during the timer operation period of "meeting all the above conditions", then the service can also be released.

[0244] Scenario 4: If the current terminal only has low-priority services, and if the terminal enters a non-PLMN during the execution of low-priority services, the terminal stops the timer and proceeds to step S503.

[0245] In step S512, the UE selects a network; the network selection method can be: sorting the network or selecting a target network specified by the network.

[0246] Step S513: If the security detection fails, it is determined that the current VPLMN network has tampered with the EXT-SOR related information, or that the credibility of the current VPLMN has decreased. The UE sets the current VPLMN network to the lowest priority.

[0247] The UE can immediately release the connection and search for other networks; if no other network is available, it can then register and reside on the current network.

[0248] After the UE discovers that the VPLMN has tampered with the EXT-SOR related information, it can either report the event to the user or not.

[0249] The above Figure 2 The description of this application is from the terminal side; the following description will focus on the network transfer method in this application from the network side. Figure 5 This is a flowchart of the network transfer method in an embodiment of this application. Figure 2 ,like Figure 5 As shown, the steps of this method include:

[0250] Step S602: The network-side device generates the first information corresponding to the EXT-SOR;

[0251] Step S604: The network-side device sends first information to the terminal; wherein, the first information indicates that the service with target information is the target service.

[0252] It should be noted that the target information in the embodiments of this application may include at least one of the following: the type of target service, the name of the target service, the number of the target service, the target network slice selection assistance information S-NSSAI, the target data network name DNN, the target 5QI, the request type of the target protocol data unit (PDU) session, the target network interconnection protocol IP address, and the target packet filter.

[0253] In an optional embodiment of this application, the method by which the network-side device generates the first information in step S502 may further include: the home public land mobile network unified data management HPLMN UDM network element in the network-side device generating the first information.

[0254] In an optional embodiment of this application, the sending of the first information from the network-side device to the terminal in step S604 may further include:

[0255] Step S604-11: The HPLMN UDM network element in the network-side device sends the first information to the AMF network element in the network-side device;

[0256] Step S604-12: The AMF network element in the network-side device transmits the first information to the terminal.

[0257] Optionally, the AMF network element in the network-side device transmits the first information to the terminal through at least one of the following: a transparent transmission container for the SOR and a transparent transmission container for the EXT-SOR. The transparent transmission container for the EXT-SOR includes at least one of the following: EXT-SOR information 1, EXT-SOR information 2, and EXT-SOR security information.

[0258] Optionally, before the HPLMN UDM network element in the network-side device sends the first information to the AMF network element in the network-side device, the method further includes: the HPLMN UDM network element in the network-side device protecting the first information by sending it to the authentication server function AUSF network element in the network-side device.

[0259] In an optional embodiment of this application, after the network-side device sends the first information to the terminal, the method further includes: the network-side device sending second information corresponding to EXT-SOR to the terminal.

[0260] Regarding the method by which network-side devices need to update information corresponding to EXT-SOR, in the specific application scenarios of this application embodiment, such as... Figure 6 As shown, the update process includes:

[0261] Step S701: The UE completes registration in the VPLMN;

[0262] Step S702, HPLMN determines that the information related to EXT-SOR needs to be updated;

[0263] Step S703: HPLMN prepares EXT-SOR related information; if HPLMN UDM is obtained through EXT-SOR-AF, proceed to step S703.

[0264] Step S704: HPLM NUMBER UDM requests EXT-SOR information from SOR-AF;

[0265] Step S705, SOR-AF determines EXT-SOR information;

[0266] Step S706, SOR-AF feeds back EXT-SOR information;

[0267] Step S707, HPLM NUMBER UDM protects the EXT-SOR information;

[0268] Step S708, HPLM NUMBER UDM sends EXT-SOR information to AUSF;

[0269] Step S709, AUSF protects the EXT-SOR information;

[0270] Step S710: AUSF sends the protected EXT-SOR information to HPLM NUMBER UDM;

[0271] It can be seen that the above steps S704~S710 are the same as... Figure 3 Steps S307 to S313 are the same;

[0272] Step S711, HPLM NUMBER UDM sends the protected and updated EXT-SOR related information to VPLMN AMF;

[0273] In step S712, the VPLMN AMF transmits the received updated EXT-SOR information after protection to the UE via a NAS message. This can be done, for example, via an MM message or a DL NAS TRANSPORT (Downlink Non-Access Stratum) message. The VPLMN AMF cannot modify the updated EXT-SOR information after protection.

[0274] In step S713, after receiving the updated EXT-SOR information after protection, the UE first performs a security check on the information, such as an integrity check.

[0275] Step S714: If it is necessary to send feedback to the network that the UE has successfully received the updated EXT-SOR related information, the feedback information can be protected and then sent to the network in an uplink non-access stratum (NAS) message, such as UL NAS TRANSPORT (uplink non-access stratum transmission) message.

[0276] Step S715, VPLMN AFM determines whether EXT-SOR information has been received;

[0277] Step S716: HPLM NAVF sends a confirmation message to HPLM NAVUDM.

[0278] Step S717, HPLM NUMBER UDM checks the confirmation message;

[0279] In step S718, the HPLMN UDM forwards the confirmation message to the SOR-AF.

[0280] It should be noted that S715~S718 in this process are related to... Figure 3 Steps S318 to S321 are the same.

[0281] In addition, the network can also decide whether to update EXT-SOR related information residing in the HPLMN. That is, after the UE resides and registers in the HPLMN, and the HPLMN is trusted, when the HPLMN instructs the UE on EXT-SOR related information, it can do so in a protected manner, i.e., updating the EXT-SOR related information in the same way as when the UE resides in the VPLMN; the process is the same as the registration process when residing in the VPLMN. Alternatively, it can notify the UE by transmitting unprotected EXT-SOR related information. Upon receiving this, the UE saves the EXT-SOR related information. This parameter will be used when the UE resides in a qualified VPLMN.

[0282] It should be noted that the network transfer method provided in this application embodiment can be executed by a network transfer device, or by a control module within the network transfer device for executing the network transfer method. This application embodiment uses the execution of the network transfer method by a network transfer device as an example to illustrate the network transfer device provided in this application embodiment.

[0283] This application provides a network transfer device. Figure 7 This is a schematic diagram of the network transfer device structure according to an embodiment of this application. Figure 1 ,like Figure 7 As shown, the device includes:

[0284] Module 72 is used to obtain the service currently being executed by the terminal;

[0285] Release module 74 is used to release the currently executed service of the terminal if the target service does not exist in the currently executed service of the terminal;

[0286] The execution module 76 is used to perform a network transfer to the terminal after releasing the currently executing service of the terminal.

[0287] Optionally, the apparatus in this application embodiment may further include:

[0288] The first receiving module is used to receive the first information corresponding to the Extended Roaming Control (EXT-SOR) sent by the network-side device;

[0289] The first determining module is used to determine whether a target service exists in the currently executed service based on the first information; wherein the first information is used to indicate that the service with target information is the target service.

[0290] The first receiving module may further include: a first sending unit, used to send a notification message to the network-side device; wherein the notification message is used to notify the network-side device that the terminal supports EXT-SOR capability; and a receiving unit, used to receive first information corresponding to EXT-SOR sent by the network-side device.

[0291] Optionally, the notification message includes at least one of the following: a registration request message, an uplink non-transport layer transmission message, or a protocol data unit session message.

[0292] Optionally, the first determining module in this application embodiment includes one of the following: a first determining unit, used to determine whether the target service exists in the service currently being executed by the terminal based on the first information, and / or the subscription information saved by the terminal, and / or the target service agreed upon by the terminal and the network-side device, and / or the target service customized by the terminal.

[0293] Optionally, the release module 74 in this embodiment may further include: a first release unit, configured to immediately release the service currently being executed by the terminal according to the instruction of the first information; or, a second release unit, configured to release the service currently being executed by the terminal after a preset time period according to the instruction of the first information.

[0294] Optionally, the second release unit is also configured to start a timer according to the indication of the first information, and release the service currently being executed by the terminal if the timer expires.

[0295] Optionally, the apparatus in this application embodiment may further include: a second determining module, used to autonomously determine whether the target service exists in the currently executed service.

[0296] The second determining module is further used by the terminal to independently determine whether the target service exists in the currently executed service based on the subscription information stored by the terminal, and / or the target service agreed upon by the terminal and the network-side equipment, and / or the target service customized by the terminal.

[0297] Optionally, the release module in this application embodiment may further include: a third release unit, used to determine to immediately release the service currently being executed by the terminal; or, a fourth release unit, used to determine to release the service currently being executed by the terminal after a custom preset time period.

[0298] The fourth release unit is also used to determine the start timer and release the currently executed service of the terminal if the timer expires.

[0299] Optionally, the apparatus in this application embodiment may further include: a second receiving module, configured to receive second information corresponding to EXT-SOR sent by a network-side device before the timer expires, wherein the second information is information updated from the first information; a first processing module, configured to stop the timer from running and overwrite the first information with the second information, and determine whether the target service exists in the service currently being executed by the terminal based on the second information; or, discard the second information and release the service currently being executed by the terminal based on the first information if the timer expires.

[0300] Optionally, the apparatus in this application embodiment may further include: a third determining module, configured to determine whether the target service has ended if the target service exists in the currently executed service; and a fourth determining module, configured to determine that the target service does not exist in the currently executed service if the target service has ended.

[0301] Optionally, the apparatus in this application embodiment may further include: a fifth determining module, configured to determine whether the visited public land mobile network (VPLMN) in the network-side device has changed; and a second processing module, configured to delete the first information or determine whether the target service exists in the currently executed service based on the first information if the VPLMN has changed.

[0302] Optionally, the apparatus in this application embodiment may further include: a detection module, configured to perform security detection on the first information after receiving the first information sent by the network-side device; wherein the security detection includes integrity checking and / or decryption detection; a sixth determination module, configured to determine whether the VPLMN in the network-side device has changed if the security detection of the first information passes; and a first sending module, configured to send feedback information to the network-side device if the VPLMN in the network-side device has not changed, wherein the feedback information is used to indicate that the terminal has received the first information.

[0303] The first sending module may further include: a protection unit for protecting the feedback information; wherein the protection includes integrity protection and / or encryption protection; and a second sending unit for sending the protected feedback information to the network-side device via a registration end message or an uplink non-access stratum transmission message.

[0304] Optionally, the apparatus in this application embodiment may further include: a storage module, configured to save the first information to the user service identification module (USIM) or the mobile device (ME) after receiving the first information.

[0305] Optionally, the apparatus in this application embodiment may further include: an interaction module, used to interact with the user for first information via an AT interface.

[0306] Optionally, the target information in this application embodiment includes at least one of the following: the type of target service, the name of the target service, the number of the target service, the target S-NSSAI, the target DNN, the target 5QI, the request type of the target PDU session, the target IP address, and the target packet filter.

[0307] Optionally, in this embodiment of the application, the first receiving module receives the first information sent by the network-side device through at least one of the following carriers: a transparent container of SOR, a transparent container of EXT-SOR.

[0308] Optionally, the pass-through container of EXT-SOR includes at least one of the following: EXT-SOR information 1, EXT-SOR information 2, and EXT-SOR security information.

[0309] Optionally, the notification message may use the 5GMM capability to instruct the network-side device that the terminal supports the EXT-SOR capability.

[0310] Optionally, the feedback information may indicate that the terminal has received the first information via SOR header-new or EXT-SOR header-new.

[0311] Optionally, the target service is a service whose priority is higher than the preset priority.

[0312] The above description is from the terminal side; the following description will focus on the network side. Embodiments of this application also provide a network transfer device. Figure 8 This is a schematic diagram of the network transfer device structure according to an embodiment of this application. Figure 2 ,like Figure 8 As shown, the device includes:

[0313] Generation module 82 is used to generate the first information corresponding to EXT-SOR;

[0314] The second sending module 84 is used to send first information to the terminal; wherein the first information indicates that the service with target information is the target service.

[0315] Optionally, the target information includes at least one of the following:

[0316] The target service type, target service name, target service number, target network slice selection auxiliary information (S-NSSAI), target data network name (DNN), target 5QI, target protocol data unit (PDU) session request type, target network interconnection protocol IP address, and target packet filter.

[0317] Optionally, module 82 in the present application embodiment may further include: an HPLMN UDM network element for generating first information.

[0318] Optionally, the second sending module 84 in the present application embodiment may further include: an HPLMN UDM network element for sending first information to an AMF network element; and an AMF network element for transmitting the first information to the terminal.

[0319] Optionally, the AMF network element transmits the first information to the terminal through at least one of the following: the transparent container of the SOR, or the transparent container of the EXT-SOR.

[0320] Optionally, the pass-through container of EXT-SOR includes at least one of the following: EXT-SOR information 1, EXT-SOR information 2, and EXT-SOR security information.

[0321] Optionally, the apparatus in this application embodiment may further include: an HPLMN UDM network element, used to protect the first information to the AMF network element before the HPLMN UDM network element sends the first information to the AMF network element.

[0322] Optionally, the apparatus in this application embodiment may further include: a second sending module, further configured to send second information corresponding to EXT-SOR to the terminal after the network-side device sends the first information to the terminal; and / or a third receiving module, configured to receive the protected feedback information sent by the terminal and deprotect the feedback; wherein the feedback information is used to indicate that the terminal has received the first information.

[0323] Through the embodiments of this application, a terminal can release the currently executed service and transfer the network when the target service is not present in the currently executed service. If the target service is a high-priority service, the terminal can release the currently executed service and transfer the network when there is no high-priority service present in the currently executed service. In addition, the target service can also be one or more services specified by the terminal. That is, if the terminal is not currently executing one or more of these specified services, the terminal can also release the currently executed service and transfer the network. This solves the problem in the prior art where the terminal will continue to reside on the current network and cannot transfer the network when there is an unimportant service present in the terminal.

[0324] The network transfer device in this application embodiment can be a device, or a component, integrated circuit, or chip in a terminal. The device can be a mobile terminal or a non-mobile terminal. For example, a mobile terminal can include, but is not limited to, the types of terminals 11 listed above, while a non-mobile terminal can be a server, network attached storage (NAS), personal computer (PC), television (TV), ATM, or self-service machine, etc. This application embodiment does not impose specific limitations.

[0325] The network transfer device in this application embodiment can be a device with an operating system. This operating system can be Android, iOS, or other possible operating systems; this application embodiment does not specifically limit the specific operating system used.

[0326] The network transfer device provided in this application embodiment can achieve Figure 2 or Figure 5 The various processes implemented in the method embodiments achieve the same technical effect, and will not be described again here to avoid repetition.

[0327] Optional, such as Figure 9 As shown, this application embodiment also provides a communication device 900, including a processor 901, a memory 902, and a program or instructions stored in the memory 902 and executable on the processor 901. For example, when the communication device 900 is a terminal, the program or instructions executed by the processor 901 implement the various processes of the above-described network transfer method embodiment and achieve the same technical effect. When the communication device 900 is a network-side device, the program or instructions executed by the processor 901 implement the various processes of the above-described network transfer method embodiment and achieve the same technical effect; to avoid repetition, further details are omitted here.

[0328] Figure 10 A schematic diagram of the hardware structure of a terminal to implement an embodiment of this application.

[0329] The terminal 100 includes, but is not limited to, components such as: radio frequency unit 101, network module 102, audio output unit 103, input unit 104, sensor 105, display unit 106, user input unit 107, interface unit 108, memory 109, and processor 110.

[0330] Those skilled in the art will understand that the terminal 100 may also include a power supply (such as a battery) for supplying power to various components. The power supply may be logically connected to the processor 110 through a power management system, thereby enabling functions such as managing charging, discharging, and power consumption through the power management system. Figure 10 The terminal structure shown does not constitute a limitation on the terminal; the terminal may include more than [other components]. Figure 10 The number of components may be increased or decreased, or certain components may be combined, or different component arrangements may be made, which will not be elaborated here.

[0331] It should be understood that, in this embodiment, the input unit 104 may include a graphics processing unit (GPU) 1041 and a microphone 1042. The GPU 1041 processes image data of still images or videos obtained by an image capture device (such as a camera) in video capture mode or image capture mode. The display unit 106 may include a display panel 1061, which may be configured in the form of a liquid crystal display, an organic light-emitting diode, or the like. The user input unit 107 includes a touch panel 1071 and other input devices 1072. The touch panel 1071 is also called a touch screen. The touch panel 1071 may include a touch detection device and a touch controller. Other input devices 1072 may include, but are not limited to, a physical keyboard, function keys (such as volume control buttons, power buttons, etc.), a trackball, a mouse, and a joystick, which will not be described in detail here.

[0332] In this embodiment, the radio frequency unit 101 receives downlink data from the network-side device and processes it for the processor 110; additionally, it sends uplink data to the network-side device. Typically, the radio frequency unit 101 includes, but is not limited to, an antenna, at least one amplifier, a transceiver, a coupler, a low-noise amplifier, a duplexer, etc.

[0333] The memory 109 can be used to store software programs or instructions and various data. The memory 109 may primarily include a program or instruction storage area and a data storage area. The program or instruction storage area may store the operating system, application programs or instructions required for at least one function (such as sound playback, image playback, etc.). Furthermore, the memory 109 may include high-speed random access memory and non-volatile memory, wherein the non-volatile memory may 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. For example, at least one disk storage device, flash memory device, or other non-volatile solid-state storage device.

[0334] Processor 110 may include one or more processing units; optionally, processor 110 may integrate an application processor and a modem processor, wherein the application processor mainly handles the operating system, user interface, and applications or instructions, and the modem processor mainly handles wireless communication, such as a baseband processor. It is understood that the aforementioned modem processor may also not be integrated into processor 110.

[0335] Specifically, embodiments of this application also provide a network-side device. For example... Figure 11 As shown, the network device 1100 includes an antenna 111, a radio frequency (RF) device 112, and a baseband device 113. The antenna 111 is connected to the RF device 112. In the uplink direction, the RF device 112 receives information through the antenna 111 and transmits the received information to the baseband device 113 for processing. In the downlink direction, the baseband device 113 processes the information to be transmitted and sends it to the RF device 112. The RF device 112 processes the received information and transmits it through the antenna 111.

[0336] The aforementioned frequency band processing device can be located in the baseband device 113. The method executed by the network-side device in the above embodiments can be implemented in the baseband device 113, which includes a processor 114 and a memory 115.

[0337] Baseband device 113 may include, for example, at least one baseband board on which multiple chips are disposed, such as Figure 11 As shown, one of the chips, for example, is a processor 114, which is connected to a memory 115 to call the program in the memory 115 and execute the network device operations shown in the above method embodiment.

[0338] The baseband device 113 may also include a network interface 116 for exchanging information with the radio frequency device 112, such as a common public radio interface (CPRI).

[0339] Specifically, the network-side device in this embodiment of the invention further includes: instructions or programs stored in memory 115 and executable on processor 114, wherein processor 114 calls the instructions or programs in memory 115 to execute. Figure 8 The methods executed by each module shown achieve the same technical effect, and to avoid repetition, they will not be described in detail here.

[0340] This application also provides a readable storage medium storing a program or instructions. When the program or instructions are executed by a processor, they implement the various processes of the above-described network transfer method embodiments and achieve the same technical effects. To avoid repetition, they will not be described again here.

[0341] The processor mentioned above is the processor in the terminal described in the above embodiments. The readable storage medium includes computer-readable storage media, such as computer read-only memory (ROM), random access memory (RAM), magnetic disk, or optical disk.

[0342] This application embodiment also provides a chip, which includes a processor and a communication interface. The communication interface and the processor are coupled. The processor is used to run network-side device programs or instructions to implement the various processes of the above-described network transfer method embodiments and achieve the same technical effect. To avoid repetition, it will not be described again here.

[0343] It should be understood that the chip mentioned in the embodiments of this application may also be referred to as a system-on-a-chip, system chip, chip system, or system-on-a-chip, etc.

[0344] It should be noted that, in this document, the terms "comprising," "including," or any other variations thereof are intended to cover non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements includes not only those elements but also other elements not expressly listed, or elements inherent to such a process, method, article, or apparatus. Without further limitations, an element defined by the phrase "comprising one..." does not exclude the presence of other identical elements in the process, method, article, or apparatus that includes that element. Furthermore, it should be noted that the scope of the methods and apparatuses in the embodiments of this application is not limited to performing functions in the order shown or discussed, but may also include performing functions substantially simultaneously or in the reverse order, depending on the functions involved. For example, the described methods may be performed in a different order than described, and various steps may be added, omitted, or combined. Additionally, features described with reference to certain examples may be combined in other examples.

[0345] Through the above description of the embodiments, those skilled in the art can clearly understand that the methods of the above embodiments can be implemented by means of software plus necessary general-purpose hardware platforms. Of course, they can also be implemented by hardware, but in many cases the former is a better implementation method. Based on this understanding, the technical solution of this application, in essence, or the part that contributes to the prior art, can be embodied in the form of a software product. This computer software product is stored in a storage medium (such as ROM / RAM, magnetic disk, optical disk) and includes several instructions to cause a terminal (which may be a mobile phone, computer, server, air conditioner, or network device, etc.) to execute the methods described in the various embodiments of this application.

[0346] The embodiments of this application have been described above with reference to the accompanying drawings. However, this application is not limited to the specific embodiments described above. The specific embodiments described above are merely illustrative and not restrictive. Those skilled in the art can make many other forms under the guidance of this application without departing from the spirit and scope of the claims, and all of these forms are within the protection scope of this application.

Claims

1. A method for transferring networks, characterized in that, include: The terminal obtains the service currently being executed by the terminal; If the target service does not exist in the service currently being executed by the terminal, the terminal shall release the service currently being executed by the terminal. After releasing the service currently being executed by the terminal, the terminal performs a network transfer to the terminal. The terminal determines whether the target service exists in the currently executed service, including: The terminal receives the first information corresponding to the Extended Roaming Control (EXT-SOR) sent by the network-side device; The terminal determines whether the target service exists in the currently executed service based on the first information; wherein, the first information is used to indicate that the service with target information is the target service; The target information includes at least one of the following: target single network slice selection auxiliary information S-NSSAI, target data network name DNN; After receiving the first information sent by the network-side device, the method further includes: The terminal performs a security check on the first information; wherein the security check includes an integrity check and / or a decryption check; If the first information security detection passes, the terminal determines whether the Visited Public Land Mobile Network (VPLMN) in the network-side device has changed. If the VPLMN in the network-side device remains unchanged, the terminal sends feedback information to the network-side device, wherein the feedback information is used to indicate that the terminal has received the first information.

2. The method according to claim 1, characterized in that, The first information corresponding to the Extended Roaming Control (EXT-SOR) sent by the receiving network-side device includes: The terminal sends a notification message to the network-side device; wherein the notification message is used to notify the network-side device that the terminal supports EXT-SOR capability; The terminal receives the first information corresponding to EXT-SOR sent by the network-side device.

3. The method according to claim 2, characterized in that, The notification message includes at least one of the following: registration request message, uplink non-transport layer transmission message, and protocol data unit session message.

4. The method according to claim 1, characterized in that, Based on the first information, determining whether the target business exists in the currently executed business includes one of the following: The terminal determines whether the target service exists in the service it is currently executing based on the first information; The terminal determines whether the target service exists in the currently executed service based on the first information, and / or the subscription information stored by the terminal, and / or the target service agreed upon by the terminal and the network-side device, and / or the target service customized by the terminal.

5. The method according to claim 1, characterized in that, The terminal releases the service it is currently executing, including: The terminal immediately releases the currently executed service according to the instruction of the first information; or, The terminal releases the currently executed service after a preset time period according to the instruction of the first information.

6. The method according to claim 5, characterized in that, The terminal releasing the currently executed service after a preset time period according to the indication of the first information includes: The terminal starts a timer according to the instruction of the first information, and releases the service currently being executed by the terminal if the timer expires.

7. The method according to claim 6, characterized in that, The method further includes: Before the timer expires, the terminal receives second information corresponding to EXT-SOR sent by the network-side device, wherein the second information is the updated information of the first information; The terminal stops running the timer and overwrites the first information with the second information, and determines whether the target service exists in the service currently being executed by the terminal based on the second information; or, the terminal discards the second information and releases the service currently being executed by the terminal based on the first information if the timer times out.

8. The method according to claim 1, characterized in that, The method further includes: If the target service exists in the currently executed service, the terminal determines whether the target service has ended. If the target service ends, the terminal determines that the target service does not exist in the currently executed service.

9. The method according to claim 6, characterized in that, The method further includes: The terminal determines whether the VPLMN in the network-side device has changed; In the event of a change in the VPLMN, the terminal determines that the first information is invalid and stops the timer, or determines whether the target service exists in the currently executed service based on the first information.

10. The method according to claim 1, characterized in that, Sending feedback information to the network-side device, including: The terminal protects the feedback information; wherein the protection includes integrity protection and / or encryption protection. The terminal sends the protected feedback information to the network-side device via a registration end message or an uplink non-access layer transmission message.

11. The method according to claim 1, characterized in that, After receiving the first information, the method further includes: The terminal saves the first information to the user service identification module USIM or the mobile device ME.

12. The method according to claim 11, characterized in that, The method further includes: The terminal interacts with the user to exchange the first information via the AT interface.

13. The method according to claim 1, characterized in that, The terminal receives first information transmitted by the network-side device through at least one of the following: a transparent container of SOR, or a transparent container of EXT-SOR.

14. The method according to claim 13, characterized in that, The EXT-SOR pass-through container includes at least one of the following: EXT-SOR information 1, EXT-SOR information 2, and EXT-SOR security information; the EXT-SOR security information includes: the value of the counter required to generate the protected first information, and / or the checksum for generating the protected first information, and / or the encrypted ciphertext information for generating the protected first information.

15. The method according to claim 2, characterized in that, The notification message indicates to the network-side device, via the 5G system mobility management (5GMM) capability, that the terminal supports the EXT-SOR capability.

16. The method according to claim 1, characterized in that, The feedback information indicates that the terminal has received the first information via SOR header-new or EXT-SOR header-new.

17. The method according to claim 1, characterized in that, The target service is a service whose priority is higher than the preset priority.

18. A method for transferring networks, characterized in that, include: The network-side device generates the first information corresponding to the EXT-SOR; The network-side device sends the first information to the terminal, so that if the target service does not exist in the service currently being executed by the terminal, the terminal releases the service currently being executed by the terminal, and after releasing the service currently being executed by the terminal, performs a network transfer to the terminal; wherein, the first information indicates that the service with target information is the target service; After the network-side device sends the first information to the terminal, the method further includes: The network-side device receives feedback information sent by the terminal after the first information security detection passes, indicating that the VPLMN in the network-side device has not been changed; wherein, the feedback information is used to indicate that the terminal has received the first information; The security detection includes integrity checks and / or decryption checks.

19. The method according to claim 18, characterized in that, The network-side device is also used for: The terminal sends a notification message; wherein the notification message is used to notify the network-side device that the terminal supports EXT-SOR capability.

20. The method according to claim 18, characterized in that, The first information generated by the network-side device includes: The first information is generated by the home public land mobile network unified data management HPLMN UDM network element in the network-side device.

21. The method according to claim 20, characterized in that, The network-side device sends the first information to the terminal, including: The HPLMN UDM network element in the network-side device sends the first information to the Access and Mobility Management Function (AMF) network element in the network-side device. The AMF network element in the network-side device transmits the first information to the terminal.

22. The method according to claim 21, characterized in that, The AMF network element in the network-side device transmits the first information to the terminal through at least one of the following: a SOR pass-through container, or an EXT-SOR pass-through container.

23. The method according to claim 22, characterized in that, The EXT-SOR pass-through container includes at least one of the following: EXT-SOR information 1, EXT-SOR information 2, and EXT-SOR security information; the EXT-SOR security information includes: the value of the counter required to generate the protected first information, and / or the checksum for generating the protected first information, and / or the encrypted ciphertext information for generating the protected first information.

24. The method according to claim 20, characterized in that, Before the HPLMN UDM network element in the network-side device sends the first information to the AMF network element in the network-side device, the method further includes: The HPLMN UDM network element in the network-side device protects the first information by sending it to the AUSF network element, which functions as the authentication server in the network-side device.

25. The method according to claim 20, characterized in that, After the network-side device sends the first information to the terminal, the method further includes: The network-side device sends the second information corresponding to EXT-SOR to the terminal.

26. The method according to claim 18, characterized in that, The feedback information is the protected feedback information, and the method further includes: the network-side device deprotecting the feedback.

27. The method according to claim 18, characterized in that, The target information includes at least one of the following: target single network slice selection auxiliary information S-NSSAI, target data network name DNN.

28. A terminal, characterized in that, It includes a processor, a memory, and a program or instructions stored in the memory and executable on the processor, wherein the program or instructions, when executed by the processor, implement the steps of the network transfer method as described in any one of claims 1 to 17.

29. A network-side device, characterized in that, It includes a processor, a memory, and a program or instructions stored in the memory and executable on the processor, wherein the program or instructions, when executed by the processor, implement the steps of the network transfer method as described in any one of claims 18 to 27.

30. A readable storage medium, characterized in that, The readable storage medium stores a program or instructions that, when executed by a processor, implement the network transfer method as described in any one of claims 1 to 17, or implement the steps of the network transfer method as described in any one of claims 18 to 27.

Images