A method and terminal device for obtaining slice information

Abstract

Embodiments of the present application relate to a method for obtaining slice information and a terminal device, wherein the method comprises: in response to receiving allowed network slice selection assistance information (NSSAI) or updating allowed NSSAI by a non-access layer of the terminal device, the non-access layer of the terminal device sending expected-to-use slice information to an access layer of the terminal device; and the access layer of the terminal device receiving and storing the expected-to-use slice information, so as to use the expected-to-use slice information when performing cell selection or cell reselection; wherein the expected-to-use slice information is the allowed NSSAI or a subset of the allowed NSSAI. Embodiments of the present application can make the access layer of the terminal device always store expected-to-use slice information, so that cell selection or cell reselection can be performed according to the expected-to-use slice information.

Description

Technical Field

[0001] This application relates to the field of communications, and more specifically, to a method and terminal device for acquiring slice information. Background Technology

[0002] In the R15 / R16 standards of 5G technology, when a User Equipment (UE) selects a cell for access, it is unaware of which Single-Network Slice Selection Assistance Information (S-NSSAI) the cell supports. The UE requests the required S-NSSAI by including a requested NSSAI (which can contain multiple S-NSSAIs) in its registration request message. If the cell supports access with the S-NSSAI, the Access and Mobility Management Function (AMF) includes the S-NSSAI in the allowed NSSAI carried in the registration acceptance message, indicating that the UE is allowed to use the services of that slice. If the cell or Radio Access Network (RAN) node where the UE resides does not support access with the S-NSSAI, the AMF includes the rejected S-NSSAI in the rejected NSSAI carried in the registration acceptance message, indicating that the UE cannot use the services of that slice.

[0003] In existing technologies, the UE's Non-Access Stratum (NAS) only provides slice information to the Access Stratum (AS) layer when requesting the establishment of a Radio Resource Control (RRC) connection. The AS then uses this slice information for cell selection. However, in some scenarios, such as when the UE undergoes cell reselection or cell selection, the UE's NAS layer may not trigger an RRC connection request. Consequently, the AS layer cannot obtain the slice information that the UE intends to use, making it unable to select a cell based on the intended slice information. Summary of the Invention

[0004] This application provides a method and terminal device for obtaining slice information, which enables the UE's AS layer to always store the slice information to be used, thereby enabling cell selection or cell reselection based on the slice information to be used.

[0005] This application provides a method for obtaining slice information, applied to a terminal device, the method comprising:

[0006] In response to the terminal device’s non-access stratum receiving or updating the allowed network slice selection assistance information (NSSAI), the terminal device’s non-access stratum sends the slice information to be used to the terminal device’s access stratum.

[0007] The access layer of the terminal device receives and stores the intended slice information for use during cell selection or cell reselection; wherein the intended slice information is the allowed NSSAI or a subset of the allowed NSSAI.

[0008] This application also provides a terminal device, including: a transmitting module at the non-access layer and a receiving and storage module at the access layer; wherein,

[0009] The sending module is used to send the slice information to be used to the receiving and storing module in response to the non-access stratum receiving allowed NSSAI or updating allowed NSSAI of the terminal device.

[0010] A receiving and storage module is configured to receive and store the intended slice information for use during cell selection or cell reselection; wherein the intended slice information is the allowed NSSAI or a subset of the allowed NSSAI.

[0011] This application also provides a terminal device, including: a processor and a memory, the memory being used to store a computer program, and the processor being used to call and run the computer program stored in the memory to perform the method described in any of the above embodiments.

[0012] This application also provides a chip, including: a processor, configured to call and run a computer program from a memory, causing a device on which the chip is installed to perform the method described in any of the above embodiments.

[0013] Embodiments of this application also provide a computer-readable storage medium for storing a computer program that causes a computer to perform the methods described in any of the preceding claims.

[0014] This application also provides a computer program product, including computer program instructions that cause a computer to perform the methods described in any of the foregoing embodiments.

[0015] This application also provides a computer program that causes a computer to perform the methods described in any of the foregoing embodiments.

[0016] In this embodiment, after receiving a new allowed NSSAI or updating the allowed NSSAI, the NAS layer sends the expected slice information to the AS layer. The AS layer stores the expected slice information and uses it for subsequent cell selection or cell reselection. This ensures that the AS layer always needs the expected slice information, and thus can always perform cell selection or cell reselection based on this slice information. Attached Figure Description

[0017] Figure 1 This is a schematic diagram illustrating an application scenario of an embodiment of this application.

[0018] Figure 2 This is a flowchart illustrating the implementation process of a UE selecting a cell based on the slice information to be used in related technologies.

[0019] Figure 3 This is a schematic flowchart of a method 300 for obtaining slice information according to an embodiment of this application.

[0020] Figure 4 This is a flowchart of the implementation according to Embodiment 1 of this application.

[0021] Figure 5 This is a flowchart of the implementation according to Embodiment 2 of this application.

[0022] Figure 6 This is a flowchart of the implementation according to Embodiment 3 of this application.

[0023] Figure 7 This is a schematic diagram of the structure of a terminal device 700 according to an embodiment of this application.

[0024] Figure 8 This is a schematic diagram of the structure of a terminal device 800 according to an embodiment of this application.

[0025] Figure 9 This is a schematic structural diagram of a communication device 900 according to an embodiment of this application;

[0026] Figure 10 This is a schematic structural diagram of a chip 1000 according to an embodiment of this application. Detailed Implementation

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

[0028] It should be noted that the terms "first," "second," etc., in the specification, claims, and accompanying drawings of the embodiments of this application are used to distinguish similar objects and are not necessarily used to describe a specific order or sequence. The objects described by "first" and "second" may be the same or different.

[0029] The technical solutions of this application embodiment 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, evolution system of NR system, LTE-based access to unlicensed spectrum (LTE-U) system, NR-based access to unlicensed spectrum (NR-U) system, Universal Mobile Telecommunication System (UMTS), Wireless Local Area Networks (WLAN), Wireless Fidelity (WiFi), 5th Generation (5G) system, or other communication systems, etc.

[0030] Traditional communication systems typically 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 communication but also, for example, device-to-device (D2D) communication, machine-to-machine (M2M) communication, machine-type communication (MTC) communication, and vehicle-to-vehicle (V2V) communication. The embodiments of this application can also be applied to these communication systems.

[0031] Optionally, the communication system in this application embodiment can be applied to a carrier aggregation (CA) scenario, a dual connectivity (DC) scenario, or a standalone (SA) network deployment scenario.

[0032] The embodiments of this application do not limit the spectrum to which the application is applied. For example, the embodiments of this application can be applied to licensed spectrum or unlicensed spectrum.

[0033] This application describes 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. The terminal device may be a station (STAION, ST) in a WLAN, a cellular phone, cordless phone, Session Initiation Protocol (SIP) phone, Wireless Local Loop (WLL) station, Personal Digital Assistant (PDA) device, handheld device with wireless communication capabilities, computing device or other processing device connected to a wireless modem, vehicle-mounted device, wearable device, and next-generation communication system, such as terminal device in an NR network or terminal device in a future evolved Public Land Mobile Network (PLMN) network, etc.

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

[0035] Network devices can be devices used to communicate with mobile devices. Network devices can be access points (APs) in WLANs, base stations (BTSs) in GSM or CDMA, base stations (NodeBs, NBs) in WCDMA, evolved base stations (eNBs or eNodeBs) in LTE, relay stations or access points, or in-vehicle devices, wearable devices, and network devices (gNBs) in NR networks, or network devices in future evolved PLMN networks, etc.

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

[0037] Figure 1 An exemplary embodiment shows one network device 110 and two terminal devices 120. Optionally, the wireless communication system 100 may include multiple network devices 110, and the coverage area of ​​each network device 110 may include other numbers of terminal devices 120. This application embodiment does not limit this. This application embodiment can be applied to one terminal device 120 and one network device 110, or it can be applied to one terminal device 120 and another terminal device 120.

[0038] Optionally, the wireless communication system 100 may also include other network entities such as a Mobility Management Entity (MME) and an Access and Mobility Management Function (AMF), which are not limited in this application embodiment.

[0039] It should be understood that the terms "system" and "network" are often used interchangeably in this document. The term "and / or" in this document merely describes the relationship between related objects, indicating that three relationships can exist. For example, A and / or B can represent: A alone, A and B simultaneously, or B alone. Furthermore, the character " / " in this document generally indicates that the preceding and following related objects have an "or" relationship.

[0040] It should be understood that the term "instruction" mentioned in the embodiments of this application can be a direct instruction, an indirect instruction, or an indication of a relationship. For example, A instructing B can mean that A directly instructs B, such as B being able to obtain information through A; it can also mean that A indirectly instructs B, such as A instructing C, so B can obtain information through C; or it can mean that there is a relationship between A and B.

[0041] In the description of the embodiments of this application, the term "correspondence" may indicate that there is a direct or indirect correspondence between two things, or that there is an association between two things, or that there is a relationship of instruction and being instructed, configuration and being configured, etc.

[0042] To facilitate understanding of the technical solutions of the embodiments of this application, the relevant technologies of the embodiments of this application are described below. The following relevant technologies are optional solutions and can be combined with the technical solutions of the embodiments of this application in any way, and they all fall within the protection scope of the embodiments of this application.

[0043] In the R15 / R16 standards of 5G technology, the UE is unaware of which S-NSSAIs the cell supports when selecting a cell for access. The UE requests the required S-NSSAI by including a requested NSSAI (which may contain multiple S-NSSAIs) in the registration request message. If the cell supports access with the S-NSSAI, the AMF includes the S-NSSAI in the allowed NSSAI section of the registration acceptance message to indicate that the UE is allowed to use the services of that slice. If the cell or RAN node where the UE resides does not support access with the S-NSSAI, the AMF includes the rejected S-NSSAI in the rejected NSSAI section of the registration acceptance message to indicate that the UE cannot use the services of that slice.

[0044] Furthermore, in the R17 standard, the 3rd Generation Partnership Project (3GPP) began to consider supporting different S-NSSAI for cells in different frequency bands, supporting different slice services in different cells, and broadcasting the supported slice information in broadcast messages. When the NAS layer in the UE requests to establish an RRC connection with the AS layer, it notifies the AS layer of the intended slice information, so that the AS layer can select a cell based on the intended slice information. Figure 2 This is a flowchart illustrating the implementation process of a UE selecting a cell based on the slice information to be used in related technologies, including the following steps:

[0045] Step 0: The RAN broadcasts the supported slice information in a broadcast message.

[0046] Step 1: The NAS layer in the UE requests the AS layer to establish an RRC connection, providing the expected slice information, the reason value for establishing the RRC connection, and the NAS-Protocol Data Unit (PDU). The NAS-PDU refers to the registration request message, which carries parameters such as the 5G Globally Unique Temporary UE Identity (5G-GUTI) and the registration type.

[0047] The AS layer selects a suitable cell for access based on the slice information to be used provided by the NAS layer and the slice information supported in the broadcast message.

[0048] Step 2: The UE sends an RRC setup request message to the RAN, which carries the (S-TMSI) and the RRC setup reason value.

[0049] Step 3: The RAN accepts the RRC setup request and sends an RRC setup message to the UE;

[0050] Step 4: The UE sends an RRC setup complete message to the RAN, which carries the NAS-PDU from step 1 and the slice information to be used.

[0051] Step 5: The RAN selects the AMF and sends an N2 message - Uplink Non-Access Stratum Transport (UL NAS TRANSPORT) message to the AMF, which carries the aforementioned NAS-PDU.

[0052] Step 6: The AMF accepts the registration and returns a registration acceptance message to the UE, which carries the new 5G-GUTI.

[0053] In existing technologies, the UE's NAS layer only provides the AS layer with the slice information it intends to use when requesting to establish an RRC connection. The AS then uses this slice information for cell selection. However, in some scenarios, such as when the UE undergoes cell reselection or cell selection, the UE's NAS layer may not trigger an RRC connection request. As a result, the AS layer cannot obtain the slice information that the UE intends to use, and therefore cannot select a cell based on the intended slice. Consequently, the UE cannot camp on the optimal cell.

[0054] This application provides a method for obtaining slice information, which can be applied to terminal devices. Figure 3 This is a schematic flowchart of a method 300 for obtaining slice information according to an embodiment of this application. This method can optionally be applied to... Figure 1 The system shown is not limited to this. The method includes at least a portion of the following.

[0055] S310: In response to the terminal device’s non-access stratum (NAS) receiving allowed network slice selection assistance information (NSSAI) or updating allowed NSSAI, the terminal device’s non-access stratum sends the slice information to be used to the terminal device’s access stratum (AS).

[0056] S320: The access layer of the terminal device receives and stores the intended slice information for use during cell selection or cell reselection; wherein the intended slice information is an allowed NSSAI or a subset of allowed NSSAI.

[0057] Subsequently, the access layer of the terminal device can select a suitable cell for access based on the expected slice information and the slice information supported in the broadcast message.

[0058] In the above process, after receiving the allowed NSSAI or updating the allowed NSSAI, the NAS layer sends the expected slice information to the AS layer. The AS layer stores the expected slice information and uses it for subsequent cell selection or cell reselection. This process ensures that the AS layer always stores the expected slice information, so it can always perform cell selection or cell reselection based on this information, thereby guaranteeing that the UE can camp on the optimal cell.

[0059] Optionally, in the above process, the slice information to be used that the NAS layer sends to the AS can be: the allowed NSSAI received by the terminal device or a subset of the allowed NSSAI received by the terminal device.

[0060] Alternatively, the slice information to be used that the NAS layer sends to the AS can be: the allowed NSSAI updated by the end device or a subset of the allowed NSSAI updated by the end device.

[0061] In some implementations, the NAS layer of the terminal device receiving the allowed NSSAI includes: the NAS layer of the terminal device receiving a registration acceptance message carrying the allowed NSSAI.

[0062] Example 1:

[0063] Figure 4 According to the implementation flowchart of Embodiment 1 of this application, in Embodiment 1, the terminal device receives a registration acceptance message sent by the network device, which carries the allowed NSSAI. Figure 4 The example shown uses AMF as an example of a network device. Figure 4 As shown, it includes the following steps:

[0064] Step 401: The UE sends a registration request message to the AMF. The registration request message carries the requested NSSAI, which in turn carries the S-NSSAI information that the UE wishes to access.

[0065] In step 402, the AMF returns a registration acceptance message to the UE, which carries allowed NSSAIs and rejected NSSAIs. The allowed NSSAIs represent the permitted NSSAIs, while the rejected NSSAIs carry the rejected S-NSSAIs and a rejection reason value.

[0066] In step 403, the UE's NAS layer provides the expected slice information to the AS layer. This expected slice information can be the allowed NSSAI or a subset of the allowed NSSAI. The UE's AS layer stores the expected slice information and uses it later when cell selection or cell reselection is required.

[0067] During subsequent cell selection or cell reselection, the UE's AS layer can select a suitable cell for access based on the expected slice information and the slice information supported in the received broadcast message; for details, please refer to... Figure 2 The access step in step 1 and the subsequent steps.

[0068] In this embodiment, the NAS layer of the UE can determine the slice information to be used after initiating registration, and provide the slice information to the AS layer for use by the AS layer when cell selection or cell reselection is required in the future; thereby ensuring that the AS layer always stores the slice information to be used, and that the AS can always select a suitable cell based on the slice information to be used.

[0069] In some implementations, the NAS layer of the terminal device receiving the allowed NSSAI includes: the NAS layer of the terminal device receiving a configuration update command message, the configuration update command message carrying the allowed NSSAI.

[0070] Example 2:

[0071] Figure 5 According to the implementation flowchart of Embodiment 2 of this application, in Embodiment 2, the terminal device receives a configuration update command message sent by the network device, which carries the allowed NSSAI. Figure 5 The example shown uses AMF as an example of a network device. Figure 5 As shown, it includes the following steps:

[0072] Step 501: The UE has already registered in the network, but when the allowed NSSAI of the UE changes, the AMF sends a UE configuration update command message to the UE, which carries the new allowed NSSAI.

[0073] Step 502, the UE's NAS layer stores the new allowed NSSAI.

[0074] Step 503: The UE returns a UE configuration update complete message to the AMF.

[0075] In step 504, the UE's NAS layer provides the expected slice information to the AS layer. This expected slice information can be the allowed NSSAI or a subset of the allowed NSSAI. The UE's AS layer stores the expected slice information and uses it later when cell selection or cell reselection is required.

[0076] In the above process, there is no order restriction between steps 503 and 504. Either step can be executed first, or they can be executed simultaneously.

[0077] During subsequent cell selection or cell reselection, the UE's AS layer can select a suitable cell for access based on the expected slice information and the slice information supported in the received broadcast message; for details, please refer to... Figure 2 The access step in step 1 and the subsequent steps.

[0078] In this embodiment, the NAS layer of the UE can register in the network, receive the latest allowed NSSAI in real time, and use the allowed NSSAI to generate the expected slice information. The expected slice information is then provided to the AS layer for use by the AS layer when cell selection or cell reselection is required. This ensures that the AS layer always stores the expected slice information, guaranteeing that the AS can always select a suitable cell based on the expected slice information.

[0079] In some implementations, the NAS layer of the terminal device updates the allowed NSSAIs by: the NAS layer of the terminal device receiving a configuration update command message carrying a rejected NSSAI; and the NAS layer of the terminal device using the rejected NSSAIs to update the allowed NSSAIs.

[0080] Example 3:

[0081] Figure 6 According to the implementation flowchart of Embodiment 3 of this application, in Embodiment 3, the terminal device receives a configuration update command message sent by the network device. This configuration update command message carries a rejected NSSAI, and updates the allowed NSSAI based on the rejected NSSAI. Figure 6 The example shown uses AMF as an example of a network device. Figure 6 As shown, it includes the following steps:

[0082] Step 601: The UE has already registered in the network, but when the rejected NSSAI corresponding to the UE changes, the AMF sends a UE configuration update command message to the UE, which carries the updated rejected NSSAI.

[0083] Step 602: The NAS layer of the UE updates the allowed NSSAI based on the rejected NSSAI. For example, if the original allowed NSSAI contains slice 1 and slice 2, and the received rejected NSSAI contains slice 1, then the allowed NSSAI is updated; slice 1 in the allowed NSSAI is deleted, and the updated allowed NSSAI contains only slice 2.

[0084] Step 603: The UE returns a UE configuration update complete message to the AMF.

[0085] In step 604, the UE's NAS layer provides the expected slice information to the AS layer. This expected slice information can be the updated allowed NSSAI or a subset of the updated allowed NSSAI. The UE's AS layer stores the expected slice information and uses it later when cell selection or cell reselection is required.

[0086] In the above process, there is no order restriction between steps 603 and 604. Either step can be executed first, or they can be executed simultaneously.

[0087] During subsequent cell selection or cell reselection, the UE's AS layer can select a suitable cell for access based on the expected slice information and the slice information supported in the received broadcast message; for details, please refer to... Figure 2 The access step in step 1 and the subsequent steps.

[0088] In this embodiment, after registering in the network, the NAS layer of the UE can receive the latest rejected NSSAI in real time, update the allowed NSSAI based on the rejected NSSAI, generate the expected slice information using the updated allowed NSSAI, and provide the expected slice information to the AS layer for use by the AS layer when cell selection or cell reselection is required in the future. This ensures that the AS layer always stores the expected slice information, guaranteeing that the AS can always select a suitable cell based on the expected slice information.

[0089] This application also proposes a terminal device. Figure 7 This is a schematic diagram of the structure of a terminal device 700 according to an embodiment of this application, including: a transmitting module 710 located in the non-access layer and a receiving and storage module 720 located in the access layer; wherein,

[0090] The sending module 710 is used to send the slice information to be used to the receiving and storing module in response to the non-access stratum receiving allowed NSSAI or updating allowed NSSAI of the terminal device.

[0091] The receiving and storage module 720 is configured to receive and store the intended slice information for use during cell selection or cell reselection; wherein the intended slice information is the allowed NSSAI or a subset of the allowed NSSAI.

[0092] Figure 8This is a schematic diagram of the structure of a terminal device 800 according to an embodiment of this application, as shown below. Figure 8 As shown, optionally, the terminal device further includes:

[0093] The selection module 830, located at the access layer, is used to select a suitable cell for access based on the slice information to be used and the slice information supported in the broadcast message.

[0094] Optionally, the aforementioned terminal equipment also includes:

[0095] The first receiving module 840, located in the non-access stratum, is used to receive a registration acceptance message that carries the allowed NSSAI.

[0096] Optionally, the aforementioned terminal equipment also includes:

[0097] The second receiving module 850, located in the non-access stratum, is used to receive a configuration update command message, which carries the allowed NSSAI.

[0098] Optionally, the aforementioned terminal device further includes: a third receiving module 860 and an updating module 870 located in the non-access layer; wherein,

[0099] The third receiving module 860 is used to receive a configuration update command message, which carries a rejected NSSAI.

[0100] Update module 870 to update the allowed NSSAI by utilizing the rejected NSSAI.

[0101] Optionally, the slice information to be used is the allowed NSSAI received by the terminal device or the allowed NSSAI updated by the terminal device.

[0102] It should be understood that the above and other operations and / or functions of the modules in the terminal device according to the embodiments of this application are respectively for implementing Figure 3 The corresponding procedures for the terminal devices in Method 300 are omitted here for the sake of brevity.

[0103] It should be noted that the functions described in the various modules (sub-modules, units, or components, etc.) of the terminal devices 700 and 800 in the embodiments of this application can be implemented by different modules (sub-modules, units, or components, etc.) or by the same module (sub-module, unit, or component, etc.). For example, the first receiving module and the second receiving module can be different modules or the same module, both of which can realize their corresponding functions in the embodiments of this application. In addition, the sending module and receiving module in the embodiments of this application can be implemented by the transceiver of the device, and some or all of the other modules can be implemented by the processor of the device.

[0104] Figure 9 This is a schematic structural diagram of a communication device 900 according to an embodiment of this application. Figure 9 The communication device 900 shown includes a processor 910, which can call and run computer programs from memory to implement the methods in the embodiments of this application.

[0105] Optionally, such as Figure 9 As shown, the communication device 900 may further include a memory 920. The processor 910 can retrieve and run computer programs from the memory 920 to implement the methods described in this embodiment.

[0106] The memory 920 can be a separate device independent of the processor 910, or it can be integrated into the processor 910.

[0107] Optionally, such as Figure 9 As shown, the communication device 900 may also include a transceiver 930, which the processor 910 can control to communicate with other devices. Specifically, it can send information or data to other devices or receive information or data sent by other devices.

[0108] The transceiver 930 may include a transmitter and a receiver. The transceiver 930 may further include antennas, and the number of antennas may be one or more.

[0109] Optionally, the communication device 900 may be a terminal device in the embodiments of this application, and the communication device 900 may implement the corresponding processes implemented by the terminal device in the various methods of the embodiments of this application. For the sake of brevity, it will not be described in detail here.

[0110] Figure 10 This is a schematic structural diagram of a chip 1000 according to an embodiment of this application. Figure 10 The chip 1000 shown includes a processor 1010, which can call and run computer programs from memory to implement the methods in the embodiments of this application.

[0111] Optionally, such as Figure 10 As shown, chip 1000 may further include memory 1020. Processor 1010 can retrieve and run computer programs from memory 1020 to implement the methods described in this embodiment.

[0112] The memory 1020 can be a separate device independent of the processor 1010, or it can be integrated into the processor 1010.

[0113] Optionally, the chip 1000 may also include an input interface 1030. The processor 1010 can control the input interface 1030 to communicate with other devices or chips, specifically, to acquire information or data sent by other devices or chips.

[0114] Optionally, the chip 1000 may also include an output interface 1040. The processor 1010 can control the output interface 1040 to communicate with other devices or chips, specifically, to output information or data to other devices or chips.

[0115] Optionally, the chip can be applied to the terminal device in the embodiments of this application, and the chip can implement the corresponding processes implemented by the terminal device in the various methods of the embodiments of this application. For the sake of brevity, it will not be described in detail here.

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

[0117] The processors mentioned above can be general-purpose processors, digital signal processors (DSPs), field-programmable gate arrays (FPGAs), application-specific integrated circuits (ASICs), or other programmable logic devices, transistor logic devices, discrete hardware components, etc. Among them, the general-purpose processors mentioned above can be microprocessors or any conventional processor.

[0118] The aforementioned memory can be volatile memory or non-volatile memory, or a combination of both. Non-volatile memory can be read-only memory (ROM), programmable read-only memory (PROM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), or flash memory. Volatile memory can be random access memory (RAM).

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

[0120] In the above embodiments, implementation can be achieved, in whole or in part, through software, hardware, firmware, or any combination thereof. When implemented in software, it can be implemented, in whole or in part, as a computer program product. This computer program product includes one or more computer instructions. When these computer program instructions are loaded and executed on a computer, all or part of the processes or functions described in the embodiments of this application are generated. The computer can be a general-purpose computer, a special-purpose computer, a computer network, or other programmable device. The computer instructions can be stored in a computer-readable storage medium or transmitted from one computer-readable storage medium to another. For example, the computer instructions can be transmitted from one website, computer, server, or data center to another via wired (e.g., coaxial cable, fiber optic, Digital Subscriber Line (DSL)) or wireless (e.g., infrared, wireless, microwave, etc.) means. The computer-readable storage medium can be any available medium accessible to a computer or a data storage device such as a server or data center that integrates one or more available media. The available media can be magnetic media (e.g., floppy disks, hard disks, magnetic tapes), optical media (e.g., DVDs), or semiconductor media (e.g., solid-state drives (SSDs)).

[0121] It should be understood that in the various embodiments of this application, the order of the above-mentioned processes does not imply 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 this application.

[0122] Those skilled in the art will understand that, for the sake of convenience and brevity, the specific working processes of the systems, devices, and units described above can be referred to the corresponding processes in the foregoing method embodiments, and will not be repeated here.

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

Claims

1. A method for obtaining slice information, applied to a terminal device, the method comprising: In response to the terminal device's non-access stratum receiving a registration accept message or configuration update command message carrying allowed network slice selection assistance information (NSSAI), or in response to the terminal device's non-access stratum updating allowed NSSAI, the terminal device's non-access stratum sends intended slice information to the terminal device's access stratum, wherein the intended slice information is the allowed NSSAI received by the terminal device or a subset of the allowed NSSAI received by the terminal device; or, the intended slice information is the allowed NSSAI updated by the terminal device or a subset of the allowed NSSAI updated by the terminal device. The access layer of the terminal device receives and stores the intended slice information for use during cell reselection; and The access layer of the terminal device selects a suitable cell for access based on the expected slice information and the slice information supported in the broadcast message.

2. The method according to claim 1, wherein, The non-access stratum update allowed NSSAI of the terminal device includes: The non-access layer of the terminal device receives a configuration update command message, the configuration update command message carrying a rejected NSSAI; The non-access layer of the terminal device uses the rejected NSSAI to update the allowed NSSAI.

3. A terminal device, comprising: The system includes a transmitting module at the non-access layer, a first receiving module at the non-access layer, a second receiving module at the non-access layer, a receiving and storage module at the access layer, and a selection module at the access layer; wherein... The first receiving module at the non-access stratum is used to receive a registration acceptance message, which carries an allowed NSSAI. The second receiving module at the non-access stratum is used to receive a configuration update command message, the configuration update command message carrying the allowed NSSAI; The sending module is configured to send intended slice information to the receiving and storing module in response to the terminal device's non-access stratum receiving the registration acceptance message or the configuration update command message carrying allowed NSSAI, or in response to the terminal device's non-access stratum updating allowed NSSAI, wherein the intended slice information is the allowed NSSAI received by the terminal device or a subset of the allowed NSSAI received by the terminal device; or, the intended slice information is the allowed NSSAI updated by the terminal device or a subset of the allowed NSSAI updated by the terminal device. The receiving and storage module is used to receive and store the slice information to be used during cell reselection; The selection module at the access layer is used to select a suitable cell for access based on the expected slice information and the slice information supported in the broadcast message.

4. The terminal device according to claim 3, wherein, The terminal device further includes: a third receiving module and an update module located in the non-access layer; wherein... The third receiving module is used to receive a configuration update command message, the configuration update command message carrying a rejected NSSAI; The update module is used to update the allowed NSSAI using the rejected NSSAI.

5. A terminal device, comprising: A processor and a memory for storing a computer program, the processor for calling and running the computer program stored in the memory to perform the method as described in any one of claims 1 to 2.

6. A chip, comprising: A processor for retrieving and running a computer program from memory, causing a device on which the chip is mounted to perform the method as described in any one of claims 1 to 2.

7. A computer-readable storage medium for storing a computer program that causes a computer to perform the method as described in any one of claims 1 to 2.

8. A computer program product comprising computer program instructions that cause a computer to perform the method as described in any one of claims 1 to 2.

Images