Slice information configuration method and device

Abstract

The present application relates to a method and device for configuring slice information. The specific implementation method is: a terminal device receives configuration update information, and the configuration update information includes first slice information; the terminal device configures slice information associated with a first session according to the first slice information. In an embodiment of the present application, the terminal device updates its own slice information associated with the first session according to the slice information in the configuration update information, which can ensure the normal processing of the session and improve the stability of the communication system.

Description

Technical Field

[0001] The present application relates to the field of communications, and more specifically, to a slice information configuration method and device. Background Art

[0002] The 3rd Generation Partnership Project (3GPP) introduced a new feature of network slicing in the 5G system. This feature is also a representative function of the 5G system. By dividing different network slices in the same network environment, different network resources, such as bandwidth, rate, and service quality, can be allocated separately. This allows different business needs to occupy network resources more reasonably. Summary of the invention

[0003] The embodiments of the present application provide a method and device for configuring slice information.

[0004] The present application provides a method for configuring slice information, including:

[0005] The terminal device receives configuration update information, where the configuration update information includes first slice information;

[0006] The terminal device configures slice information associated with the first session based on the first slice information.

[0007] The present application provides a terminal device, including:

[0008] A first receiving unit, configured to receive configuration update information, where the configuration update information includes first slice information;

[0009] A processing unit is used to configure slice information associated with the first session according to the first slice information.

[0010] The embodiment of the present application provides a terminal device, including a processor and a memory. The memory is used to store a computer program, and the processor is used to call and run the computer program stored in the memory, so that the terminal device executes the slice information configuration method in the embodiment of the present application.

[0011] The embodiment of the present application provides a network device, including a processor and a memory. The memory is used to store a computer program, and the processor is used to call and run the computer program stored in the memory, so that the network device executes the slice information configuration method in the embodiment of the present application.

[0012] An embodiment of the present application provides a chip for implementing the above-mentioned slice information configuration method.

[0013] Specifically, the chip includes: a processor, which is used to call and run a computer program from a memory, so that a device equipped with the chip executes the slice information configuration method in the embodiment of the present application.

[0014] An embodiment of the present application provides a computer-readable storage medium for storing a computer program. When the computer program is executed by a device, the device executes the slice information configuration method in the embodiment of the present application.

[0015] An embodiment of the present application provides a computer program product, including computer program instructions, which enable a computer to execute the slice information configuration method in the embodiment of the present application.

[0016] The embodiment of the present application provides a computer program, which, when executed on a computer, enables the computer to execute the slice information configuration method in the embodiment of the present application. BRIEF DESCRIPTION OF THE DRAWINGS

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

[0018] Figure 2 It is a schematic flowchart of a slice information configuration method according to an embodiment of the present application.

[0019] Figure 3 It is a schematic flowchart of a slice information configuration method according to another embodiment of the present application.

[0020] Figure 4 It is a schematic block diagram of a terminal device according to an embodiment of the present application.

[0021] Figure 5 It is a schematic block diagram of a terminal device according to another embodiment of the present application.

[0022] Figure 6 is a schematic diagram of a configuration update process according to an embodiment of the present disclosure.

[0023] Figure 7 It is a schematic block diagram of a communication device according to an embodiment of the present application.

[0024] Figure 8 is a schematic block diagram of a chip according to an embodiment of the present application.

[0025] Fig. 9 It is a schematic block diagram of a communication system according to an embodiment of the present application. DETAILED DESCRIPTION

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

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

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

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

[0030] In one embodiment, the communication system in the embodiment of the present application can be applied to an unlicensed spectrum, wherein the unlicensed spectrum can also be considered as a shared spectrum; or, the communication system in the embodiment of the present application can also be applied to an authorized spectrum, wherein the authorized spectrum can also be considered as an unshared spectrum.

[0031] The embodiments of the present application describe various embodiments in conjunction with network devices and terminal devices, wherein the terminal device may also be referred to as user equipment (UE), access terminal, user unit, user station, mobile station, mobile station, remote station, remote terminal, mobile device, user terminal, terminal, wireless communication device, user agent or user device, etc.

[0032] The terminal device can be a station (STAION, ST) in a WLAN, a cellular phone, a cordless phone, a Session Initiation Protocol (SIP) phone, a Wireless Local Loop (WLL) station, a Personal Digital Assistant (PDA) device, a handheld device with wireless communication function, a computing device or other processing device connected to a wireless modem, a vehicle-mounted device, a wearable device, a terminal device in a next-generation communication system such as an NR network, or a terminal device in a future evolved Public Land Mobile Network (PLMN) network, etc.

[0033] In the embodiments of the present application, the terminal device can be deployed on land, including indoors or outdoors, handheld, wearable or vehicle-mounted; it can also be deployed on the water surface (such as ships, etc.); it can also be deployed in the air (for example, on airplanes, balloons and satellites, etc.).

[0034] In the embodiment of the present application, the terminal device can be a mobile phone, a tablet computer, a computer with wireless transceiver function, a virtual reality (VR) terminal device, an augmented reality (AR) terminal device, a wireless terminal device in industrial control, a wireless terminal device in self driving, a wireless terminal device in remote medical, a wireless terminal device in a smart grid, a wireless terminal device in transportation safety, a wireless terminal device in a smart city, or a wireless terminal device in a smart home, etc.

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

[0036] In an embodiment of the present application, the network device may be a device for communicating with a mobile device. The network device may be an access point (AP) in WLAN, a base station (Base Transceiver Station, BTS) in GSM or CDMA, a base station (NodeB, NB) in WCDMA, an evolved base station (EvolutionalNode B, eNB or eNodeB) in LTE, or a relay station or access point, or a vehicle-mounted device, a wearable device, and a network device (gNB) in an NR network, or a network device in a future evolved PLMN network, or a network device in an NTN network, etc.

[0037] As an example but not limitation, in an embodiment of the present application, the network device may have a mobile characteristic, for example, the network device may be a mobile device. Optionally, the network device may be a satellite or a balloon station. For example, the satellite may be a low earth orbit (LEO) satellite, a medium earth orbit (MEO) satellite, a geostationary earth orbit (GEO) satellite, a high elliptical orbit (HEO) satellite, etc. Optionally, the network device may also be a base station set up in a location such as land or water.

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

[0039] Figure 1 A communication system 100 is exemplarily shown. The communication system includes a network device 110 and two terminal devices 120. In one embodiment, the communication system 100 may include multiple network devices 110, and each network device 110 may include other number of terminal devices 120 within its coverage area, which is not limited in the present embodiment.

[0040] In one implementation, the communication system 100 may also include other network entities such as a mobility management entity (MME), an access and mobility management function (AMF), etc., which is not limited in the embodiments of the present application.

[0041] Among them, the network equipment may include access network equipment and core network equipment. That is, the wireless communication system also includes multiple core networks for communicating with the access network equipment. The access network equipment may be an evolutionary base station (evolutional node B, referred to as eNB or e-NodeB) macro base station, micro base station (also called "small base station"), micro-micro base station, access point (AP), transmission point (TP) or new generation base station (new generation Node B, gNodeB) in a long-term evolution (LTE) system, a next-generation (mobile communication system) (next radio, NR) system or an authorized auxiliary access long-term evolution (LAA-LTE) system.

[0042] It should be understood that the device with communication function in the network / system in the embodiment of the present application can be referred to as a communication device. Figure 1 Taking the communication system shown as an example, the communication equipment may include network equipment and terminal equipment with communication functions. The network equipment and terminal equipment may be specific equipment in the embodiments of the present application and will not be repeated here. The communication equipment may also include other equipment in the communication system, such as network controllers, mobile management entities and other network entities, which are not limited to the embodiments of the present application.

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

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

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

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

[0047] After the introduction of network slicing, each data session (session) under the 5G system, such as a PDU (Protocol Data Unit) session, needs to have an associated single network slice selection assistance information (S-NSSAI). The network side can confirm and select the route of the data session based on the S-NSSAI associated with (or corresponding to) the data session, and allocate matching network resources.

[0048] The slices that can be used by the user equipment (UE) are usually based on the contracted slices under its home network, such as the HPLMN (Home Public Land Mobile Network). When the UE roams into a visited network, such as a VPLMN (Visited PLMN), if the S-NSSAI used by the UE under the original HPLMN is a common configuration value for all PLMNs, it can still be used directly under the VPLMN; if the S-NSSAI is not a common configuration value but a private configuration value of the HPLMN, then the VPLMN needs to configure the S-NSSAI under this VPLMN for the UE, use the S-NSSAI of the UE's original HPLMN as the mapping slice (mapping S-NSSAI) of the S-NSSAI under this VPLMN, and associate it with the S-NSSAI under this VPLMN. If the UE is roaming between different VPLMNs, different VPLMNs will allocate S-NSSAI under their own networks and associate the S-NSSAI of the same HPLMN as the mapping S-NSSAI. This mapping relationship is shown in Table 1 below:

[0049] Table 1 S-NSSAI configuration relationship between HPLMN and VPLMN

[0050]

[0051]

[0052] In a scenario: If the UE establishes a data session under VPLMN1 to initiate a service process, but the service is not released and roaming occurs while the data session is still activated, for example, the UE moves to VPLMN2. If the slice information corresponding to the data session at this time is S-NSSAIa+mapped S-NSSAI2, that is, the S-NSSAI2 under the corresponding HPLMN is not the standard value, the UE needs to request the S-NSSAI2 under the HPLMN corresponding to this data session in the mobile update registration request. VPLMN2 will allocate the slice S-NSSAIb+mapped S-NSSAI2 of this network to the UE in the mobile registration response. After receiving it, the UE needs to locally update the slice information associated with the data session and replace the previous S-NSSAIa+mapped S-NSSAI2 with the new S-NSSAIb+mapped S-NSSAI2.

[0053] Similarly: if the UE moves from HPLMN to VPLMN1, the UE must locally replace the slice information S-NSSAI2 associated with the data session with S-NSSAIa+mapped S-NSSAI2; if the UE moves from VPLMN1 to HPLMN, the UE must locally replace the slice information S-NSSAIa+mapped S-NSSAI2 associated with the data session with S-NSSAI2.

[0054] However, the related art only considers the situation that the UE can be immediately allocated the available slice information of the network in the mobile registration response after roaming into the visited network, and there are still certain limitations in practical applications. In view of this, an embodiment of the present application provides a slice information configuration method, and a terminal device can configure the slice information associated with the data session according to the received configuration update information.

[0055] Figure 2 FIG. 2 is a schematic flow chart of a slice information configuration method 200 according to an embodiment of the present application. The method may optionally be applied to Figure 1 The system shown in the figure is not limited thereto. The method includes at least part of the following contents.

[0056] S210. The terminal device receives configuration update information, where the configuration update information includes first slice information;

[0057] S220. The terminal device configures slice information associated with the first session according to the first slice information.

[0058] For example, in a roaming scenario, the terminal device may enter a visited network from a home network, or enter another visited network from one visited network, etc. The same data session may correspond to different network slice information in different networks. The terminal device may initiate a first session in a home network or a visited network, and enter another new network while the first session is activated. The first session may be any data session. In one embodiment, the first session is a protocol data unit (PDU) session activated in the terminal device.

[0059] The network side may perform slice authentication on the new network entered by the terminal device. If the authentication is successful, the slice information associated with the first session activated on the terminal device may be updated on the network side. The first session may also be referred to as a data session. In order to make the slice information associated with the first session activated on the terminal device consistent with that on the network side, the network side may send configuration update information including the first slice information to the terminal device. After receiving the configuration update information, the terminal device may replace the slice information associated with the first session with the received first slice information.

[0060] In an embodiment of the present application, the terminal device updates the slice information associated with its own first session according to the slice information in the configuration update information, which is beneficial to improving the stability of the communication system.

[0061] In one implementation, the first session may be a session initiated by the terminal device in the first network. While the first session remains activated, the terminal device undergoes a network change, for example, the terminal device roams into a second network.

[0062] In one implementation, the first network is a home network, and the second network is a visited network.

[0063] In one implementation, both the first network and the second network are access networks, that is, the first network is a first access network, and the second network is a second access network.

[0064] In an embodiment of the present application, the home network may be a network registered with a SIM (Subscriber Identity Module) card in a terminal device such as a UE. Usually, after the SIM card is registered, the home network of the UE using the SIM card may be fixed. For example, the home network slice information of the UE may include one HPLMN S-NSSAI, or may include multiple HPLMN S-NSSAIs. Different types of sessions may be associated with the same HPLMN S-NSSAI, or may be associated with different HPLMN S-NSSAIs. For the first session of the UE, its home network slice information may be an S-NSSAI in the NSSAI of the HPLMN of the UE. The access network may be called a roaming network, and the access network is different from the home network. For example, the access network and the home network may be networks of different operators.

[0065] In an embodiment of the present application, the first session initiated by the terminal device in the home network is associated with the home network slice information. If the network that the terminal device roams into from the home network is a visited network, the first slice information received by the terminal device in the configuration update process includes the local slice information and the mapped slice information of the visited network. Among them, the mapped slice information of the visited network may include the home network slice information. Exemplarily, the configuration update process may mainly include the visited network sending configuration update information, the terminal device updating the slice information associated with its own session and returning configuration update completion information to the network.

[0066] The first session initiated by the terminal device in the first access network associates the local slice information and the mapped slice information of the first access network. The mapped slice information of the first access network may include the home network slice information. If the terminal device roams from the first access network to the second access network, the first slice information received by the terminal device in the configuration update process includes the local slice information and the mapped slice information of the second access network. The mapped slice information of the second access network may include the home network slice information.

[0067] In one embodiment, the first slice information is the available slice information of the network that the terminal device roams into, such as the above-mentioned second network, that is, the slice information that the second network allocates to the first session of the terminal device and can be used for the first session. For example, the available slice information includes available NSSAI. If the second network is a visited network, the available NSSAI of the second network may include the S-NSSAI of the second network local to the first session and the S-NSSAI in the mapped home network.

[0068] In one embodiment, the home network slice information is S-NSSAI in the home network, and the home network is a local public land mobile network (HPLMN). In other words, the home network slice information is HPLMN S-NSSAI.

[0069] In one implementation, the terminal device updates slice information associated with the first session according to the first slice information, including:

[0070] For each first session activated in the terminal device, if the belonging network slice information in the first slice information matches the belonging network slice information associated with the first session, the terminal device updates the slice information associated with the first session to the first slice information.

[0071] Among them, the belonging network slice information in the first slice information matches the belonging network slice information associated with the first session, which can be understood as the belonging network slice information of the two being consistent, or satisfying a specific mapping relationship.

[0072] For example, the UE roams from the first network into the second network, the first session activated in the UE is a PDU dialogue, and the first slice information allocated by the second network for the first session received by the UE through the configuration update information is an available NSSAI. For each of the PDU session(s)active in the UE,if the allowed NSSAI contains an HPLMN S-NSSAI (eg mapped S-NSSAI, if available)matching to the HPLMN S-NSSAI of the PDU session,the UEshall locally update the S-NSSAI associated with the PDU session to the corresponding S-NSSAI received in the allowed NSSAI.

[0073] For example, if the first network is a visited network VPLMN1, the S-NSSAI associated with the activated PDU session in VPLMN1 may include the local S-NSSAI of VPLMN1 and the mapped HPLMN S-NSSAI. If the second network is a visited network VPLMN2, the available NSSAI associated with the activated PDU session received by the UE through the configuration update information includes the local S-NSSAI of VPLMN2 and the mapped HPLMN S-NSSAI. For another example, if the first network is a home network HPLMN, the S-NSSAI associated with the activated PDU session in the HPLMN may include the HPLMN S-NSSAI. If the second network is a visited network VPLMN, the available NSSAI associated with the activated PDU session received by the UE through the configuration update information includes the local S-NSSAI of the VPLMN and the mapped HPLMN S-NSSAI.

[0074] In one implementation, the terminal device updates the slice information associated with the first session to the first slice information, including:

[0075] When the local slice information of the first slice information is inconsistent with the local slice information associated with the first session, the slice information associated with the first session is updated to the first slice information.

[0076] In an embodiment of the present application, after receiving the configuration update information, the terminal device can compare whether the local slice information of the first slice information in the configuration update information is consistent with the local slice information associated with one or more locally activated PDU sessions. For example, the terminal device roams from the first network into the second network. Before receiving the configuration update information, the slice information associated with one or more PDU sessions includes the local slice information of the first network and the slice information of the home network of the terminal device. After receiving the configuration update information, the first slice information in the configuration update information includes the local slice information of the second network and the slice information of the home network of the terminal device. The local slice information of the second network in the first slice information can be compared with the local slice information of the first network in the slice information associated with the first session. If the two are not exactly the same, the local slice information of the first slice information is inconsistent with the local slice information associated with the first session.

[0077] In one implementation, the terminal device updates the slice information associated with the first session to the first slice information, including:

[0078] When the first slice information is inconsistent with the slice information associated with the first session, the slice information associated with the first session is updated to the first slice information.

[0079] In an embodiment of the present application, after receiving the configuration update information, the terminal device can compare whether the first slice information in the configuration update information is consistent with the slice information associated with one or more locally activated PDU sessions. If the first slice information is not exactly the same as the slice information associated with the first session, the first slice information is inconsistent with the slice information associated with the first session. In this case, the slice information associated with the first session can be updated to the first slice information in the configuration update information.

[0080] In an implementation, when the local slice information of the first slice information is inconsistent with the local slice information associated with the first session, or when the first slice information is inconsistent with the slice information associated with the first session, updating the slice information associated with the first session to the first slice information includes:

[0081] For each first session activated in the terminal device, if the home network slice information in the first slice information matches the home network slice information associated with the first session, and the local slice information of the first slice information is inconsistent with the local slice information associated with the first session, the terminal device will update the slice information associated with the first session to the first slice information.

[0082] In one implementation, updating the slice information associated with the first session to the first slice information includes at least one of the following:

[0083] Replacing the slice information associated with the first session with the first slice information;

[0084] The local slice information in the slice information associated with the first session is replaced with the local slice information in the first slice information.

[0085] For example, for each PDU session activated in the UE, if the HPLMN S-NSSAI contained in the available (allowed) NSSAI matches the HPLMN S-NSSAI associated with the PDU session, and the available NSSAI (e.g., S-NSSAIb+mapped S-NSSAI2) is inconsistent with the slice information associated with the PDU session (e.g., S-NSSAIa+mapped S-NSSAI2), the UE locally updates the slice information S-NSSAI associated with the PDU session (e.g., S-NSSAIa+mapped S-NSSAI2) to the corresponding S-NSSAI (e.g., S-NSSAIb+mapped S-NSSAI2) received in the available NSSAI.

[0086] For another example, for each PDU session activated in the UE, if the HPLMNS-NSSAI contained in the available (allowed) NSSAI matches the HPLMN S-NSSAI associated with the PDU session, and the local slice information S-NSSAI (e.g., S-NSSAIb) in the available NSSAI (e.g., S-NSSAIb+mappedS-NSSAI2) is inconsistent with the local slice information S-NSSAI (e.g., S-NSSAIa) in the slice information associated with the PDU session (e.g., S-NSSAIa+mapped S-NSSAI2), the UE locally updates the local slice information (e.g., S-NSSAIa) in the slice information associated with the PDU session to the local slice information (e.g., S-NSSAIb) received in the available NSSAI.

[0087] In one embodiment, Figure 3 As shown, the slice information configuration method 300 may include at least one step of the method 200, and the method 300 may further include:

[0088] S310: The terminal device establishes the first session under the first network, and the slice information associated with the first session is the slice information of the first network;

[0089] S320: When the terminal device roams into the second network and the first session is not released in the activated state, the terminal device sends a mobile update registration request, where the mobile update registration request includes the home network slice information in the slice information associated with the first session;

[0090] S330. The terminal device receives a mobile update registration response, and sets the belonging network slice information as pending slice information according to the mobile update registration response.

[0091] Specifically, after receiving the mobile update registration request, the second network will allocate the available slice information under the current network.

[0092] If the home network slice information associated with the first session requested by the UE cannot be directly confirmed to be available in the second network, the mobile update registration response returned by the second network to the UE will include an instruction to set the home network slice information to pending slice information, and the terminal device can set the slice information associated with the first session to pending slice information according to the mobile update registration response.

[0093] In this case, since the second network cannot directly confirm whether the home network slice information associated with the first session is available, the terminal device cannot configure the slice information associated with the first session according to the mobile update registration response.

[0094] In one embodiment, Figure 3 As shown, the slice information configuration method 300 also includes:

[0095] S340, the terminal device authenticates the home network slice information with the second network. For example, the terminal device sends slice authentication related information to the second network to confirm whether the home network slice information is available in the second network.

[0096] After the mobile update registration is completed, the second network will perform the authentication process of the pending slice information with the UE. And according to the authentication result, it will confirm whether the previously configured pending slice information is available or unavailable.

[0097] In the embodiment of the present application, when the pending slice is confirmed to be available after authentication, after the second network slice authentication is completed, configuration update information is sent to the terminal device to configure the available slice information to the terminal device. The terminal device can perform the following steps after receiving the configuration update information: Figure 2 The method shown thereby implements the configuration of slice information associated with the first session.

[0098] In one example, the UE roams from the HPLMN to the VPLMN1. First, the UE establishes a first session under the HPLMN, and the slice information associated with the first session is the HPLMN slice information, such as the HPLMN S-NSSAI2. When the UE roams into the VPLMN1 and the first session is not released in the activated state, the UE sends a mobile update registration request to the VPLMN1, and the mobile update registration request includes the home network slice information in the slice information associated with the first session, that is, the HPLMN S-NSSAI2. The UE receives a mobile update registration response from the VPLMN1, and the mobile update registration response is used to set the HPLMN S-NSSAI2 as pending slice information. The network requests the UE to obtain the necessary slice authentication related information, and the UE sends the slice authentication related information of the VPLMN1, so that the VPLMN1 can confirm whether the HPLMN S-NSSAI2 is available. If available, the VPLMN1 can configure the first session in the UE to associate the first slice information, such as S-NSSAIa+mapped (mapped) S-NSSAI2.

[0099] In another example, the UE roams from VPLMN1 to VPLMN2. First, the UE establishes a first session under VPLMN1, and the slice information associated with the first session is S-NSSAIa+mapped S-NSSAI2. Among them, S-NSSAIa is the local slice information of the first network, and mapped S-NSSAI2 is the mapped slice information, that is, the mapped home network slice information. When the UE roams into VPLMN2 and the first session is not released in the activated state, the UE sends a mobile update registration request to VPLMN2, and the mobile update registration request includes the home network slice information in the slice information associated with the first session, that is, HPLMNS-NSSAI2. The UE receives a mobile update registration response from VPLMN2, and the mobile update registration response is used to set the HPLMN S-NSSAI2 as pending slice information. The UE sends slice authentication related information of VPLMN2, so that VPLMN2 can confirm whether the HPLMN S-NSSAI2 is available. If available, VPLMN2 can configure the first session in the UE to associate the first slice information, such as S-NSSAIb+mapped S-NSSAI2, where S-NSSAIb is the local slice information of the second network, and mappedS-NSSAI2 is the mapped slice information, i.e., the mapped home network slice information.

[0100] In one embodiment, the configuration update information is sent by the second network upon confirming that the home network slice information is available.

[0101] In one embodiment, S110 terminal device receives configuration update information including: S350, the terminal device receives configuration update information sent by the second network when confirming that the belonging network slice information is available.

[0102] For example, the second network, such as VPLMN2, sends configuration update information to the UE when confirming that the first slice information, such as S-NSSAI2 in S-NSSAIb+mapped S-NSSAI2, is available. The configuration update information may include S-NSSAIb+mapped S-NSSAI2.

[0103] In one embodiment, Figure 3 As shown, the method 300 also includes:

[0104] S360. The terminal device deletes the belonging network slice information from the pending slice information according to the configuration update information, and sets the first slice information as the available slice information.

[0105] For example, after receiving the configuration update command, the UE can delete S-NSSAI2 from the pending slice information and set S-NSSAIb+mapped S-NSSAI2 as the available slice information.

[0106] After S360, S370 (see S220 in the above method embodiment) may be executed to update the slice information associated with the first session to the first slice information. For example, the slice information associated with the first session is replaced with the first slice information in the configuration update information, such as S-NSSAIb+mapped S-NSSAI2. For another example, the local slice information in the slice information associated with the first session is replaced with the local slice information in the first slice information in the configuration update command, such as S-NSSAIb.

[0107] In one embodiment, the configuration update information is carried in a configuration update command (Configuration Update Command). For example, the configuration update command can be used to allow the AMF to update the UE configuration to access parameters related to mobility management by providing new parameter information in the command.

[0108] Based on the same technical concept, an embodiment of the present application also provides a terminal device. Figure 4 4 is a schematic block diagram of a terminal device 400 according to an embodiment of the present application. The terminal device 400 may include:

[0109] A first receiving unit 410 is configured to receive configuration update information, where the configuration update information includes first slice information;

[0110] The processing unit 420 is used to configure the slice information associated with the first session according to the first slice information.

[0111] In one embodiment, the processing unit 420 is used to update the slice information associated with the first session to the first slice information for each first session activated in the terminal device if the belonging network slice information in the first slice information matches the belonging network slice information associated with the first session.

[0112] In one implementation, the processing unit 420 is configured to update the slice information associated with the first session to the first slice information when the local slice information of the first slice information is inconsistent with the local slice information associated with the first session.

[0113] In one implementation, the processing unit 420 is configured to update the slice information associated with the first session to the first slice information, including at least one of the following:

[0114] Replacing the slice information associated with the first session with the first slice information;

[0115] The local slice information in the slice information associated with the first session is replaced with the local slice information in the first slice information.

[0116] In one embodiment, the home network slice information is single network slice selection auxiliary information S-NSSAI in the home network, and the home network is a local public land mobile network HPLMN.

[0117] In one embodiment, the first session is a protocol data unit PDU session activated in the terminal device; the first slice information is the available slice information of the network into which the terminal device roams, and the available slice information is the available S-NSSAI.

[0118] In one embodiment, Figure 5 As shown, the terminal device 500 may include:

[0119] The session establishing unit 510 is used for the terminal device to establish the first session under the first network, and the slice information associated with the first session is the slice information of the first network;

[0120] A first sending unit 520 is configured to send a mobile update registration request when the terminal device roams into the second network and the first session is not released in an activated state, wherein the mobile update registration request includes the home network slice information in the slice information associated with the first session;

[0121] The second receiving unit 530 is used for the terminal device to receive a mobile update registration response, and to set the belonging network slice information as pending slice information according to the mobile update registration response.

[0122] In one embodiment, Figure 5 As shown, the terminal device 500 may also include:

[0123] The authentication unit 540 is used to authenticate the home network slice information with the second network. For example, the authentication unit sends slice authentication related information to the second network to confirm whether the home network slice information is available in the second network.

[0124] The terminal device 500 may include one or more units of the terminal device 400 , and specific functions may refer to the relevant description of the terminal device 400 .

[0125] In one embodiment, the configuration update information is sent by the second network upon confirming that the home network slice information is available.

[0126] In one embodiment, the processing unit is used to delete the belonging network slice information from the pending slice information according to the configuration update information, and set the first slice information as the available slice information.

[0127] In one embodiment, wherein:

[0128] The first network is a home network, and the second network is a visited network; or,

[0129] The first network is a first access network, and the second network is a second access network.

[0130] In one implementation, the configuration update information is carried in a configuration update command.

[0131] In the embodiments of the present application, the above-mentioned units may implement the functions of each unit in the form of software, hardware, or a combination of software and hardware. In the several embodiments provided in the present application, it should be understood that the disclosed devices and methods may be implemented in other ways. For example, the device embodiments described above are merely schematic. For example, the division of modules or units is only a logical function division. There may be other division methods in actual implementation, such as multiple units or components may be combined or integrated into another device, or some features may be ignored or not executed. Another point is that the mutual coupling or direct coupling or communication connection shown or discussed may be through some interfaces, indirect coupling or communication connection of devices or units, which may be electrical, mechanical or other forms.

[0132] The units described as separate components may or may not be physically separated, and the components shown as units may be one physical unit or multiple physical units, that is, they may be located in one place or distributed in multiple different places. Some or all of the units may be selected according to actual needs to achieve the purpose of the present embodiment.

[0133] In addition, each functional unit in each embodiment of the present application can be integrated into a processing unit, or each unit can exist physically separately, or two or more units can be integrated into one unit. The above-mentioned integrated unit can be implemented in the form of hardware or in the form of a software functional unit. For example, at least one of the first receiving unit 410, the second receiving unit 530, and the first sending unit 520 of the terminal device can be implemented by the transceiver of the terminal device. At least one of the processing unit 420, the session establishment unit 510, and the authentication unit 540 of the terminal device can be implemented by the processor of the terminal device, or by the processor and transceiver of the terminal device. Among them, the processor of the terminal device can call and run a computer program from the memory of the terminal device so that the terminal device implements the method in the embodiment of the present application. The processor can also control the transceiver of the terminal device to communicate with other devices, specifically, it can send information or data to other devices, or receive information or data sent by other devices.

[0134] The terminal devices 400 and 500 of the embodiments of the present application can implement the corresponding functions of the terminal devices in the embodiments of the aforementioned methods 200 and 300. The processes, functions, implementation methods and beneficial effects corresponding to the various modules (sub-modules, units or components, etc.) in the terminal devices 400 and 500 can be found in the corresponding descriptions in the above-mentioned method embodiments, which will not be repeated here. It should be noted that the functions described by the various modules (sub-modules, units or components, etc.) in the terminal devices 400 and 500 of the embodiments of the application can be implemented by different modules (sub-modules, units or components, etc.) or by the same module (sub-module, unit or component, etc.).

[0135] The related art provides a method for handling slice information in mobility when a data session exists. However, in another important scenario, namely, the configuration update process, it is also necessary to locally update the slice information associated with the data session. For example, the first network is VPLMN1, and the slice information associated with the data session initiated under the first network includes local slice information S-NSSAIa and mapped slice information mapped S-NSSAI2; the second network is VPLMN2, and the slice information (i.e., the first slice information) allocated to the data session under the second network includes local slice information S-NSSAIa and mapped slice information mapped S-NSSAI2. See Figure 6 , the configuration update process may include the following steps:

[0136] S601, UE establishes a data session under VPLMN1 to initiate a data service. The slice information associated with the data service (or data session) is the slice information S-NSSAIa+mapped S-NSSAI2 composed of the local slice information S-NSSAIa of VPLMN1 and the mapped slice information mapped S-NSSAI2. Among them, the mapped slice information mapped S-NSSAI2 of the UE can be the slice information of the UE's home network.

[0137] S602, the UE roams into VPLMN2, and the data service (or data session) in the UE is still in the activated state and has not been released. Therefore, the UE can request the HPLMN slice information S-NSSAI2 associated with the data session in the mobile update registration request sent to VPLMN2.

[0138] S603. There is no related configuration record of S-NSSAI2 under VPLMN2 before, and further negotiation and slice authentication are required. Therefore, VPLMN2 can instruct the UE to set S-NSSAI2 to pending slice information (Pending NSSAI) in the mobile update registration response sent to the UE. After receiving the mobile update registration response, the UE sets S-NSSAI2 to pending slice information.

[0139] S604, a slice authentication process is performed between the network side and the UE under VPLMN2, and the necessary slice authentication related information is requested from the UE, and S-NSSAI2 is further confirmed to be an available slice under VPLMN2, and the first slice information consisting of the local slice information S-NSSAIb and the mapped slice information mapped S-NSSAI2 of VPLMN2 is configured. For example, the first slice information may include a mapping relationship of S-NSSAIb+mapped S-NSSAI2.

[0140] S605. VPLMN2 configures the new available slice to the UE through a configuration update command (Configuration Update Command) process. That is, VPLMN2 sends a configuration update command to the UE, and the first slice information carried in the configuration update command includes local slice information S-NSSAIb and mapped slice information mapped S-NSSAI2. The configuration update command is used to configure the local slice information S-NSSAIb and the mapped slice information mapped S-NSSAI2 as available slice information, that is, the first slice information.

[0141] S606. After receiving the Configuration Update Command, the UE needs to remove S-NSSAI2 from the pending slice information, and set the slice information S-NSSAIb and mapped S-NSSAI2 allocated for the data session in the Configuration Update Command to available. In addition, configure the mapping relationship between S-NSSAIb and mapped S-NSSAI2.

[0142] S607. The UE obtains the new available slice information included in the configuration update command, where the new available slice information includes the slice information of the HPLMN, such as S-NSSAI2. When associating the available slice information with the corresponding slice of the activated data session, if the new available slice information is different from the slice information corresponding to the current data session. The UE needs to locally update the slice information associated with the data session according to the latest available slice information. For example, the UE performs local updates according to the latest available slice information, and configures the new slice information, namely S-NSSAIb and mapped S-NSSAI2, to the corresponding data session. After receiving the new available slice information in the configuration update process, the UE needs to locally update the slice information associated with the data session.

[0143] In one implementation, according to the relevant description in the above example, after receiving the configuration update command, the UE may perform the following operations according to the available NSSAI included in the configuration update command:

[0144] For each PDU Session activated in the UE, if the HPLMN S-NSSAI contained in the Available NSSAI (e.g. the mapped S-NSSAI if available) matches the HPLMN S-NSSAI associated with that PDU Session, the UE shall locally update the S-NSSAI associated with that PDU Session to the corresponding S-NSSAI received in the Allowed NSSAI.

[0145] In roaming and slice authentication scenarios, the slice information associated with the data session can be effectively updated to prevent the UE records from being inconsistent with the actual network configuration, leading to various possible subsequent anomalies.

[0146] In one embodiment, the protocol message or information element may not be modified or added, thereby avoiding the terminal or network element upgrade caused by the protocol upgrade, with a low investment cost, and only the processing logic of the UE when receiving the configuration update command needs to be modified.

[0147] The comparison between the embodiments of the present application and the related art can be seen in Table 2 below:

[0148] Table 2

[0149]

[0150]

[0151] In an embodiment of the present application, after receiving a configuration update command (Configuration Update Command), the terminal can obtain the slice information of the HPLMN included in the new available slice information in the configuration update command. When associating the new available slice information with the corresponding slice information of the activated data session, if the new available slice information is different from the slice information corresponding to the current data session, the UE needs to update the slice information associated with the data session locally according to the latest available slice information. This embodiment can be applied to various cross-network roaming scenarios to facilitate the stability of services such as data services.

[0152] Figure 7 7 is a schematic structural diagram of a communication device 700 according to an embodiment of the present application. The communication device 700 includes a processor 710, and the processor 710 can call and run a computer program from a memory to enable the communication device 700 to implement the method in the embodiment of the present application.

[0153] In one implementation, the communication device 700 may further include a memory 720. The processor 710 may call and run a computer program from the memory 720 to enable the communication device 700 to implement the method in the embodiment of the present application.

[0154] The memory 720 may be a separate device independent of the processor 710 , or may be integrated into the processor 710 .

[0155] In one implementation, the communication device 700 may further include a transceiver 730, and the processor 710 may control the transceiver 730 to communicate with other devices, specifically, may send information or data to other devices, or receive information or data sent by other devices.

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

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

[0158] In one implementation, the communication device 700 may be a terminal device of an embodiment of the present application, and the communication device 700 may implement the corresponding processes implemented by the terminal device in each method of the embodiment of the present application, which will not be described in detail here for the sake of brevity.

[0159] Figure 8 8 is a schematic structural diagram of a chip 800 according to an embodiment of the present application. The chip 800 includes a processor 810, and the processor 810 can call and run a computer program from a memory to implement the method in the embodiment of the present application.

[0160] In one implementation, the chip 800 may further include a memory 820. The processor 810 may call and run a computer program from the memory 820 to implement the method executed by the terminal device or the network device in the embodiment of the present application.

[0161] The memory 820 may be a separate device independent of the processor 810 , or may be integrated into the processor 810 .

[0162] In one implementation, the chip 800 may further include an input interface 830. The processor 810 may control the input interface 830 to communicate with other devices or chips, and specifically, may obtain information or data sent by other devices or chips.

[0163] In one implementation, the chip 800 may further include an output interface 840. The processor 810 may control the output interface 840 to communicate with other devices or chips, and specifically, may output information or data to other devices or chips.

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

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

[0166] The chips used in the network device and the terminal device may be the same chip or different chips.

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

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

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

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

[0171] Fig. 9 9 is a schematic block diagram of a communication system 900 according to an embodiment of the present application. The communication system 900 includes a terminal device 910 and a network device 920.

[0172] The terminal device 910 can be used to implement the corresponding functions implemented by the terminal device in the above method, and the network device 920 can be used to implement the corresponding functions implemented by the network device in the above method. For the sake of brevity, they will not be described in detail here.

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

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

[0175] Those skilled in the art can clearly understand that, for the convenience and brevity of description, the specific working processes of the systems, devices and units described above can refer to the corresponding processes in the aforementioned method embodiments and will not be repeated here.

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

Claims

1. A slice information configuration method, comprising: The terminal device establishes a first session under the first network, and the slice information associated with the first session is the slice information of the first network; When the terminal device roams into the second network and the first session is not released in the activated state, the terminal device sends a mobility update registration request, where the mobility update registration request includes the home network slice information in the slice information associated with the first session; The terminal device receives a mobile update registration response, where the mobile update registration response includes an indication of setting the home network slice information in the slice information associated with the first session as pending slice information; According to the mobile update registration response, the home network slice information in the slice information associated with the first session is set as pending slice information; The terminal device receives configuration update information sent by the second network, where the configuration update information includes first slice information; The terminal device deletes the home network slice information in the slice information associated with the first session from the pending slice information according to the configuration update information, and sets the first slice information as available slice information; The terminal device configures slice information associated with the first session according to the first slice information.

2. The method according to claim 1, wherein: The terminal device configures slice information associated with the first session according to the first slice information, including: For each first session activated in the terminal device, if the belonging network slice information in the first slice information matches the belonging network slice information associated with the first session, the terminal device updates the slice information associated with the first session to the first slice information.

3. The method according to claim 2, wherein: The terminal device updates the slice information associated with the first session to the first slice information, including: When the local slice information of the first slice information is inconsistent with the local slice information associated with the first session, the slice information associated with the first session is updated to the first slice information.

4. The method according to claim 3, updating the slice information associated with the first session to the first slice information, comprising at least one of the following: replacing the slice information associated with the first session with the first slice information; The local slice information in the slice information associated with the first session is replaced with the local slice information in the first slice information.

5. The method according to any one of claims 2 to 4, wherein: The home network slice information is the single network slice selection auxiliary information S-NSSAI in the home network, and the home network is the local public land mobile network HPLMN.

6. The method according to any one of claims 1 to 4, wherein: The first session is a protocol data unit PDU session activated in the terminal device; the first slice information is the available slice information of the network into which the terminal device roams, and the available slice information includes available NSSAI.

7. The method according to claim 6, wherein: The method further comprises: The terminal device authenticates the home network slice information with the second network.

8. The method according to claim 7, wherein: The configuration update information is sent by the second network when it confirms that the home network slice information is available.

9. The method according to any one of claims 1 to 4, wherein: The first network is a home network, and the second network is a visited network; or, The first network is a first access network, and the second network is a second access network.

10. The method according to any one of claims 1 to 4, wherein the configuration update information is carried in a configuration update command.

11. A terminal device, comprising: A session establishing unit, configured for the terminal device to establish a first session under a first network, wherein the slice information associated with the first session is the slice information of the first network; A first sending unit, configured to send a mobile update registration request when the terminal device roams into a second network and the first session is not released in an activated state, wherein the mobile update registration request includes the home network slice information in the slice information associated with the first session; A second receiving unit is used to receive a mobile update registration response, where the mobile update registration response includes an indication of setting the home network slice information in the slice information associated with the first session as pending slice information; A processing unit, configured to set the home network slice information in the slice information associated with the first session as pending slice information according to the mobile update registration response; The second receiving unit is further used to receive configuration update information sent by the second network, where the configuration update information includes first slice information; The processing unit is further configured to delete, according to the configuration update information, the home network slice information in the slice information associated with the first session from the pending slice information, and set the first slice information as available slice information; Configure slice information associated with the first session according to the first slice information.

12. The terminal device according to claim 11, wherein: The processing unit is used to update the slice information associated with each first session activated in the terminal device to the first slice information if the belonging network slice information in the first slice information matches the belonging network slice information associated with the first session.

13. The terminal device according to claim 12, wherein: The processing unit is configured to update the slice information associated with the first session to the first slice information when the local slice information of the first slice information is inconsistent with the local slice information associated with the first session.

14. The terminal device according to claim 13, wherein the processing unit is configured to update the slice information associated with the first session to the first slice information, comprising at least one of the following: replacing the slice information associated with the first session with the first slice information; The local slice information in the slice information associated with the first session is replaced with the local slice information in the first slice information.

15. The terminal device according to any one of claims 12 to 14, wherein: The home network slice information is the single network slice selection auxiliary information S-NSSAI in the home network, and the home network is the local public land mobile network HPLMN.

16. The terminal device according to any one of claims 11 to 14, wherein: The first session is a protocol data unit PDU session activated in the terminal device; the first slice information is the available slice information of the network into which the terminal device roams, and the available slice information includes available NSSAI.

17. The terminal device according to claim 16, wherein: The terminal device further includes: An authentication unit is used to authenticate the home network slice information with the second network.

18. The terminal device according to claim 17, wherein: The configuration update information is sent by the second network when it confirms that the home network slice information is available.

19. The terminal device according to any one of claims 11 to 14, wherein: The first network is a home network, and the second network is a visited network; or, The first network is a first access network, and the second network is a second access network.

20. The terminal device according to any one of claims 11 to 14, wherein the configuration update information is carried in a configuration update command.

21. A terminal device, comprising: A processor and a memory, the memory being used to store a computer program, the processor being used to call and run the computer program stored in the memory, so that the terminal device executes the method as claimed in any one of claims 1 to 10.

22. A chip, comprising: A processor, configured to call and run a computer program from a memory, so that a device equipped with the chip executes a method as claimed in any one of claims 1 to 10.

23. A computer-readable storage medium for storing a computer program, which, when executed by a device, causes the device to perform the method according to any one of claims 1 to 10.

Images