Communication method, terminal and network side device

Abstract

The present application discloses a communication method, a terminal, and a network side device, and belongs to the field of communications. The communication method of an embodiment of the present application includes: a terminal sending a first message to a network side device to request that the terminal establish a connection with the network side device using a requested slice; and a terminal receiving a second message sent by the network side device, the second message carrying information for indicating whether the terminal supports use of the requested slice within a target tracking area (TA).

Description

[Technical Field]

[0001] (CROSS-REFERENCE TO RELATED APPLICATIONS) This application claims priority to Chinese Patent Application No. 202211003981.6, entitled "Communication Method, Terminal and Network Side Equipment," filed on August 19, 2022, the entire contents of which are incorporated herein by reference.

[0002] The present application belongs to the field of communication technology, and specifically relates to a communication method, a terminal, and a network side device. [Background technology]

[0003] In the current standard, if a slice requested by a terminal is rejected, in fact, this slice may only be rejected in a certain tracking area (Registration Area, TA) within a registration area (RA), but the network side informs the terminal that this slice cannot be used in the entire RA, so that the terminal cannot use this slice in the entire RA and can only wait until the relevant timer expires, the terminal moves away from this RA, or the terminal shuts down, etc., before it can use this slice again, resulting in relatively low slice usage efficiency. Summary of the Invention [Problem to be solved by the invention]

[0004] The embodiments of the present application provide a communication method, a terminal, and a network side device that can solve the communication problem between a terminal and a network side device. [Means for solving the problem]

[0005] According to a first aspect, there is provided a communication method for use in a terminal, the method comprising: The terminal transmits a first message to a network side device to request that the terminal establish a connection with the network side device using a request slice; The terminal includes receiving a second message sent by the network side equipment, the second message carrying information for indicating whether or not to support use of the requested slice within the target tracking area TA.

[0006] According to a second aspect, there is provided a communication method for use in a network side device, the method comprising: The network side device receives a first message sent by the terminal to request establishing a connection with the network side device using the request slice; The network side device includes transmitting, to the terminal, a second message carrying information for indicating whether or not to support use of the requested slice in the target tracking area TA.

[0007] According to a third aspect, there is provided a communications device, the communications device comprising: a sending module for sending a first message to a network side device to request the network side device to establish a connection with the network side device using the request slice; and a receiving module for receiving a second message transmitted by the network side device, the second message carrying information for indicating whether or not to support use of the requested slice within the target tracking area TA.

[0008] According to a fourth aspect, there is provided a communications device, the communications device comprising: a receiving module for receiving a first message sent by a terminal to request establishing a connection with a network side device using a request slice; and a transmitting module for transmitting, to the terminal, a second message carrying information for indicating whether the terminal supports use of the requested slice in the target tracking area TA.

[0009] According to a fifth aspect, there is provided a terminal including a processor and a memory, the memory storing a program or instructions executable on the processor, the program or instructions, when executed by the processor, implementing a method according to the first aspect.

[0010] According to a sixth aspect, there is provided a terminal including a processor and a communication interface, wherein the communication interface is used for sending a first message to a network side device to request that the network side device establish a connection with the network side device using a requested slice, and for receiving a second message sent by the network side device carrying information for indicating whether or not the network side device supports use of the requested slice within a target tracking area (TA).

[0011] According to a seventh aspect, there is provided a network side device including a processor and a memory, the memory storing a program or instructions operable to run on the processor, the program or instructions, when executed by the processor, realizing the method of the second aspect.

[0012] According to an eighth aspect, there is provided a network side device, comprising: a processor; and a communication interface, wherein the communication interface is adapted to receive a first message sent by a terminal to request establishing a connection with the network side device using a requested slice; and to send a second message carrying information to indicate to the terminal whether or not to support use of the requested slice within a target tracking area (TA).

[0013] According to a ninth aspect, there is provided a communication system including a terminal and a network side device, wherein the terminal may be used to execute the communication method described in the first aspect, and the network side device may be used to execute the communication method described in the second aspect.

[0014] According to a tenth aspect, there is provided a readable storage medium having a program or instructions stored thereon, the program or instructions implementing the method of the first aspect or the method of the second aspect when executed by a processor.

[0015] According to an eleventh aspect, there is provided a chip, the chip including a processor and a communication interface, the communication interface being coupled to the processor, the processor running a program or instruction to implement the method of the first aspect or to be used to implement the method of the second aspect.

[0016] According to a twelfth aspect, there is provided a computer program / program product, the computer program / program product being stored on a storage medium and being executed by at least one processor to implement the communication method according to the first aspect. [Effects of the Invention]

[0017] In an embodiment of the present application, the network side equipment sends a second message to the terminal indicating whether it supports the use of the requested slice within the target tracking area TA, so that the terminal can select and use the slice based on the granularity of the TA after receiving the second message, which can effectively improve the efficiency of slice use, thereby allowing the terminal to use the slice more efficiently. [Brief explanation of the drawings]

[0018] [Figure 1a] 1 is a structural diagram of a wireless communication system to which an embodiment of the present application can be applied; [Figure 1b] 1 is a schematic diagram of a communication method according to an embodiment of the present application; [Figure 2] 1 is a flowchart of a communication method according to an embodiment of the present application; [Figure 3]FIG. 1 is a schematic diagram of information elements of rejection network slice selection support information in a communication method according to an embodiment of the present application. [Figure 4] FIG. 1 is a schematic diagram of a rejection network slice selection support information domain of a communication method according to an embodiment of the present application. [Figure 5] FIG. 1 is a schematic diagram of an information element of extended rejection network slice selection support information of a communication method according to an embodiment of the present application. [Figure 6a] FIG. 1 is a schematic diagram of a partial extension rejection network slice selection support information list domain of a communication method according to an embodiment of the present application. [Figure 6b] This is a second schematic diagram of a partially extended rejected network slice selection support information list domain of a communication method according to an embodiment of the present application. [Figure 7] FIG. 2 is a second schematic diagram of a rejection network slice selection support information domain of a communication method according to an embodiment of the present application. [Figure 8] This is a second schematic diagram of information elements of rejection network slice selection support information in a communication method according to an embodiment of the present application. [Figure 9] FIG. 3 is a third schematic diagram of a rejection network slice selection support information domain of a communication method according to an embodiment of the present application. [Figure 10] This is a second schematic diagram of information elements of extended rejection network slice selection support information of a communication method according to an embodiment of the present application. [Figure 11a] This is the third schematic diagram of the partially extended rejected network slice selection support information list domain of the communication method according to an embodiment of the present application. [Figure 11b] This is part four of a schematic diagram of a partially extended rejected network slice selection support information list domain of a communication method according to an embodiment of the present application. [Figure 12] FIG. 4 is a fourth schematic diagram of a rejection network slice selection support information domain of a communication method according to an embodiment of the present application. [Figure 13] FIG. 10 is a schematic diagram of a network slice selection assistance information service area list information element of a communication method according to an embodiment of the present application. [Figure 14] FIG. 10 is a schematic diagram of a network slice selection support information service area list domain of a communication method according to an embodiment of the present application; [Figure 15a] FIG. 1 is a schematic diagram of a network slice selection support information service area list field of a communication method according to an embodiment of the present application. [Figure 15b] This is a second schematic diagram of the network slice selection support information service area list field of the communication method according to an embodiment of the present application. [Figure 15c] This is the third schematic diagram of the network slice selection support information service area list field of the communication method according to an embodiment of the present application. [Figure 15d] This is part four of a schematic diagram of the network slice selection support information service area list field of the communication method according to an embodiment of the present application. [Figure 16] FIG. 10 is a schematic diagram of information elements of extended granted network slice selection assistance information of a communication method according to an embodiment of the present application. [Figure 17] FIG. 10 is a schematic diagram of an authorized network slice selection support information domain of a communication method according to an embodiment of the present application; [Figure 18] 4 is a schematic diagram of terminal capability indication information of a communication method according to an embodiment of the present application; [Figure 19] 2 is a second flowchart of a communication method according to an embodiment of the present application. [Figure 20] 1 is an interaction flowchart of a communication method according to an embodiment of the present application; [Figure 21] 1 is a structural schematic diagram of a communication device according to an embodiment of the present application; [Figure 22] 2 is a second structural schematic diagram of a communication device according to an embodiment of the present application; [Figure 23] 1 is a structural schematic diagram of a communication device according to an embodiment of the present application; [Figure 24] 1 is a hardware structure schematic diagram of a terminal according to an embodiment of the present application; [Figure 25] FIG. 2 is a structural schematic diagram of a network-side device according to an embodiment of the present application; DETAILED DESCRIPTION OF THE INVENTION

[0019] The following clearly and completely describes the technical solutions in the embodiments of the present application, in conjunction with the drawings in the embodiments of the present application, and it is obvious that the described embodiments are only some of the embodiments of the present application, and not all of the embodiments. All other embodiments obtained by those skilled in the art based on the embodiments of the present application fall within the scope of protection of the present application.

[0020] The terms "first," "second," etc. in the specification and claims of this application are intended to distinguish between similar objects and are not intended to describe a particular order or sequence. It should be understood that terms used in this manner are interchangeable where appropriate, so that embodiments of this application may be performed in orders other than those illustrated or described herein, and that objects distinguished by "first" and "second" are generally of the same type and do not limit the number of objects; for example, a first object may be one or more. Furthermore, "and / or" in the specification and claims indicates at least one of the connected objects, and the character " / " generally indicates an "or" relationship between the related objects.

[0021] It should be noted that the techniques described in the embodiments of the present application are not limited to Long Term Evolution (LTE) / LTE-Advanced (LTE-A) systems, but can also be applied to other wireless communication systems, such as Code Division Multiple Access (CDMA), Time Division Multiple Access (TDMA), Frequency Division Multiple Access (FDMA), Orthogonal Frequency Division Multiple Access (OFDMA), Single-Carrier Frequency Division Multiple Access (SC-FDMA), and other systems. The terms "system" and "network" in the embodiments of the present application are always used interchangeably, and the described techniques may be used in the above-mentioned systems and radio technologies, as well as other systems and radio technologies. The following description describes a New Radio (NR) system for illustrative purposes, and NR terminology is used in most of the following description. However, these techniques may also be used in applications other than NR system applications, such as sixth generation (6G) networks. th This may be applied to 6G (6th Generation) communication systems.

[0022] 1a shows a block diagram of a wireless communication system to which the embodiment of the present application can be applied. The wireless communication system includes a terminal 11 and a network side device 12. Here, the terminal 11 may be a terminal-side device such as a mobile phone, a tablet personal computer, a laptop computer (also called a notebook computer), a personal digital assistant (PDA), a palmtop computer, a netbook, an ultra-mobile personal computer (UMPC), a mobile internet device (MID), an augmented reality (AR) / virtual reality (VR) device, a robot, a wearable device, a vehicle-mounted equipment (VUE), a pedestrian-mounted equipment (PUE), a smart home (home devices with wireless communication capabilities, such as a refrigerator, television, washing machine, or furniture), a game console, a personal computer (PC), a teller machine, or a self-service machine, and the wearable device includes a smart watch, a smart band, a smart earphone, a smart glasses, a smart accessory (smart bracelet, smart bracelet, smart ring, smart necklace, smart anklet, smart wristband, smart wristband, smart clothing, etc.). It should be noted that the embodiments of the present application do not limit the specific type of the terminal 11. The network side equipment 12 may include access network equipment or core network equipment, where the access network equipment 12 may also be called radio access network equipment, radio access network (RAN), radio access network function or radio access network unit.The access network equipment 12 may include a base station, a WLAN access point, a WiFi node, or the like. The base station may also be called a Node B, an evolved Node B (eNB), an access point, a base transceiver station (BTS), a radio base station, a radio transceiver, a basic service set (BSS), an extended service set (ESS), a home B node, a home evolved B node, a transmitting and receiving point (TRP), or any other appropriate term in the field. As long as the same technical effect is achieved, the base station is not limited to a specific technical term. For illustrative purposes, the embodiments of this application only take base stations in an NR system as examples, but do not limit the specific type of base station.Core network devices include core network nodes, core network functions, mobility management entities (MMEs), access and mobility management functions (AMFs), session management functions (SMFs), user plane functions (UPFs), policy control functions (PCFs), policy and charging rules functions (PCRFs), edge application server discovery functions (EASDFs), unified data management (UDMs), unified data repository (UDRs), home subscriber servers (HSSs), centralized network configuration (CNCs), network repository functions (NRFs), network exposure functions (NEFs), local NEFs (or L-NEFs), binding support functions (BSFs), and application functions (Application Node Functions). The core network device may include, but is not limited to, at least one of a QoS function (e.g., QoS Function, QoS Function, QoS Control ...

[0023] In order to facilitate a clearer understanding of each embodiment of the present application, some relevant background knowledge is first introduced as follows.

[0024] RA and TA During network deployment, the AMF may establish multiple TAs within one RA area. When a terminal initiates registration, the AMF assigns one Tracking Area Identity List (TAI list) (e.g., up to 16) to the UE, and this TAI list is the registration area (RA) of the terminal. Within this RA, the terminal does not need to perform a registration update, and when the terminal moves away from this RA area, the UE needs to actively initiate a mobility registration update. As can be seen, one of the purposes for the network to establish the concept of RA and TA is that the UE does not need to frequently initiate a mobility registration update, and only needs to actively initiate a mobility registration update after moving away from the RA, thereby saving the signaling load of the network.

[0025] Allowing and Denying Slices In the registration flow, the terminal first sends a registration request message to the network side device, and the terminal reports requested slice information to the network. The requested slice information includes one or more Single Network Slice Selection Assistance Information (S-NSSAI). The network side device determines whether to allow the requested slice to be served based on the terminal subscription status and the current network status. If the requested slice can be served, the network side device returns this slice S-NSSAI to the terminal in an allowed NSSAI. If the requested slice cannot be served, the network side device returns this slice S-NSSAI to the terminal in a rejected NSSAI. Optionally, if the terminal indicates that it supports extended rejected NSSAI in the terminal capability indication information (5GMM capability IE) in the registration request message, the network side device further returns information about slices that it cannot serve in an extended rejected NSSAI to the terminal.

[0026] When returning a rejected NSSAI, the network side device may carry the cause value "slice is unavailable in the current registration area," meaning that this slice is unavailable for the entire RA. For example, as shown in Figure 1b, if a terminal initiates registration of an S-NSSAI in TA 1 and is rejected in TA 1, and the cause value used by the network side is "slice is unavailable in the current registration area," the terminal cannot currently use this slice. However, when the terminal moves to TA 2 or TA 3, these two TAs can support this slice. The prior art does not support the terminal using the slice in that area. This significantly reduces the efficiency of slice usage. In this way, the slice is unavailable in all TAs in the entire RA and can only be used in the following circumstances: The terminal is turned off, the terminal moves away from the current registration area, removes the Universal Integrated Circuit Card (UICC) including the Universal Subscriber Identity Module (USIM), and updates the "User Data List" entry with the Stand-alone Non-Public Network (SNPN) identifier of the current Stand-alone Non-Public Network (SNPN) or removes the rejected S-NSSAI.

[0027] The following describes in detail the communication method according to the embodiments of the present application through several embodiments and its application scenarios in conjunction with the drawings.

[0028] 2 is a flowchart of a communication method according to an embodiment of the present application. As shown in FIG. 2, the method according to this embodiment includes step S201 and step S202.

[0029] In step 201, the terminal sends a first message to the network side device to request the network side device to establish a connection with the network side device using a request slice.

[0030] Specifically, to realize communication between the terminal and the network side device, the terminal sends a first message to the network side device, where the first message is used to request establishing a connection with the network side device using a requested slice, optionally including information of the requested slice, and the requested slice including one or more S-NSSAIs, and the network side device can determine whether it can establish a connection and communication with the terminal using the requested slice based on the information of the requested slice in the first message, the terminal subscription status and the current network status.

[0031] In step 202, the terminal receives a second message sent by the network side device, carrying information for indicating whether to support the use of the requested slice in the target tracking area TA.

[0032] Specifically, in the current standard, if a slice requested by a terminal is rejected, the network side notifies the terminal that this slice cannot be used in the entire RA, resulting in relatively low slice usage efficiency. To solve the problem of low slice usage efficiency, in an embodiment of the present application, after the network side device receives the information of the requested slice sent by the terminal, the network side device sends a second message to the terminal, where the second message carries information for indicating whether the use of the requested slice in the target tracking area TA is supported, that is, the network side device notifies the terminal whether the requested slice can be used in the tracking area TA by sending the second message, so that the terminal can select and use the slice according to the granularity of the TA after receiving the second message, allowing the terminal to use the slice more efficiently, improving slice usage efficiency and solving the problem of not being able to use all slices in all TAs in the same RA.

[0033] In the method of the above embodiment, second information is sent to the terminal via the network side device, carrying information on whether the use of the requested slice within the target tracking area TA is supported. After the terminal receives the second message, it can select and use the slice based on the granularity of the TA, which can effectively improve the slice usage efficiency, thereby enabling the terminal to use the slice more efficiently.

[0034] In one embodiment, the second message comprises: The target tracking area (TA) includes at least one of information of at least one first slice and first indication information, wherein the first indication information is used to indicate that the at least one first slice is unavailable within the current TA, where the first slice is a slice in the request slice, and the target tracking area (TA) includes the current TA; or The second message is The target tracking area TA includes at least one of information of at least one first slice, information of a first TA corresponding to each first slice in the at least one first slice, information of at least one second slice, information of a second TA corresponding to each second slice in the at least one second slice, and second indication information, wherein the first TA is a TA that does not support use of the first slice, and the second TA is a TA that supports use of the second slice, and the second indication information is used to indicate that the first slice is not available in the first TA, where the first slice or the second slice is a slice in the requested slice, and the target tracking area TA includes the first TA or the second TA, or The second message is The information includes at least one of information on at least one third slice, information on a third TA, and third instruction information, where the third instruction information is used to indicate whether the third TA is a TA that supports the use of the third slice or a TA that does not support the use of the third slice, the target TA includes the third TA, and the third slice is a slice in the requested slice.

[0035] Specifically, in an embodiment of the present application, the network side device sends a second message to the terminal indicating whether the terminal supports the use of the requested slice in the target tracking area (TA). After the terminal receives the second message, the terminal can select and use the slice based on the granularity of the TA, thereby improving slice utilization efficiency. Optionally, in an embodiment of the present application, the first TA, the second TA, the third TA, and the target TA may be TAs included in the current registration area or TAs included in other registration areas. Optionally, one first slice corresponds to one or more first TAs, and one second slice corresponds to one or more second TAs. Optionally, one first TA corresponds to one or more first slices, and one second TA corresponds to one or more second slices.

[0036] Optionally, the second message includes at least one of information on at least one first slice and first indication information, where the first indication information is used to indicate that the first slice is unavailable in the current TA, and the current TA is the TA where the terminal is located when the terminal sends the first message to the network side device. That is, the network side device indicates that the first slice is unavailable in the current TA through the first indication information in the second message, so that after receiving the first indication information and the information on the first slice in the second message, the terminal can determine that it cannot use the first slice in the current TA, and the terminal can select another slice in the current TA to establish connection and communication with the network side device. When the terminal moves away from the current TA, the first slice can be used again. That is, after receiving the terminal's request, the network side device notifies the terminal of the information on the slice that is not applicable to the current TA through newly added indication information (cause value) based on the application status of multiple TAs in the RA of the slice, so that the terminal can determine whether the slice can be used in the current TA by combining the information on the TA where it is currently located after receiving the indication information.

[0037] Optionally, the second message includes at least one of information on at least one first slice, information on a first TA corresponding to each first slice in the at least one first slice, information on at least one second slice, information on a second TA corresponding to each second slice in the at least one second slice, and second instruction information, i.e., the network side device notifies the terminal in which TA the first slice can be used and in which TA the second slice cannot be used, based on the information on the first TA corresponding to the first slice, the information on the second TA corresponding to the second slice, and the second instruction information in the second message, so that the terminal can select and use a slice based on the information on the first TA corresponding to the first slice, the information on the second TA corresponding to the second slice, and the second instruction information in the second message, and based on the TA information in which the terminal is currently located.

[0038] Optionally, the second message includes at least one of information on at least one third slice, information on the third TA, and third instruction information, where the third instruction information is used to indicate whether the third TA is a TA that supports the use of the third slice or a TA that does not support the use of the third slice, i.e., the network side device indicates which TA is a TA that supports the use of the third slice and which TA is a TA that does not support the use of the third slice through the third instruction message in the second message, so that after receiving the third instruction message in the second message, the terminal can determine whether it can establish connection and communication with the network side device using the third slice in the target TA based on the third instruction message in the second message, and optionally the target TA may be a TA in the current RA or another RA. That is, after receiving a request from the terminal, the network side device notifies the terminal of TA list information that supports and / or denies the use of slices based on slice granularity based on the application status of multiple TAs in the RA of the slice, and after receiving the TA list information that supports and / or denies the use of slices based on slice granularity, the terminal can combine the TA information of its current location to determine whether the slice can be used in the current TA.

[0039] In the method of the above embodiment, the network side device indicates slice application information of TA granularity to the terminal by carrying indication information, slice information, and / or TA information in the second message; that is, after receiving the terminal's request, the network side device may notify the terminal of TA list information supporting and / or denying the use of the slice based on slice granularity according to the application status of multiple TAs in the RA of the slice, and notify the terminal of information that the slice is not applicable to the current TA through indication information (newly added cause value). After the terminal receives the indication information and / or TA list information supporting and / or denying the use of the slice based on slice granularity, the terminal can combine the information of the TA where it is currently located to accurately determine whether the slice can be used in the current TA. The method of the embodiment of the present application realizes accurate indication of whether the terminal can use the requested slice in a tracking area TA in multiple ways, and is relatively flexible.

[0040] In one embodiment, the second message includes a Reject Network Slice Selection Assistance Information (NSSAI) information element (IE) or a first IE, wherein the Reject NSSAI IE or the first IE includes a Reject NSSAI domain corresponding to each first slice in the at least one first slice, and the Reject NSSAI domain corresponding to each first slice includes at least one of information of the first slice and first indication information; and / or The second message includes an extended Rejected NSSAI IE, the extended Rejected NSSAI IE includes a partial extended Rejected NSSAI List domain, the partial extended Rejected NSSAI List domain includes a Rejected NSSAI domain corresponding to each first slice in at least one first slice, and the Rejected NSSAI domain corresponding to each first slice includes at least one of information of the first slice and first indication information.

[0041] Specifically, the network side device indicates to the terminal whether to support the use of the first slice in the first TA by a Reject Network Slice Selection Support Information (NSSAI) information element (IE) or a first IE in the second message, where the first IE may be a newly defined information element. Optionally, as shown in FIG. 3, the Reject NSSAI IE includes a Reject NSSAI domain corresponding to each first slice in at least one first slice. Optionally, as shown in FIG. 4, the Reject NSSAI domain corresponding to each first slice includes at least one of information of the first slice and first indication information. Optionally, the first indication information is 0100 or 0011, indicating that the slice is unavailable in the current TA. Optionally, if the indication information is 0000, it indicates that the network slice is unavailable in the current network or the private network. Optionally, if the indication information is 0001, it indicates that the network slice is unavailable in the current registration area. Optionally, if the indication information is 0010, it indicates that the slice is unavailable due to a failure or revocation of identity authentication and authorization of a specific network slice. Optionally, the terminal may use the Reject NSSAI After receiving the Rejected NSSAI Domain information in the IE or the first IE, the terminal can determine that the first slice is not available in the current TA due to the information in the Rejected NSSAI Domain, so that the terminal can select another slice in the requested slice within the current TA to communicate and establish a connection with the network side device.

[0042] Optionally, the network side device may use an extended Rejected NSSAI IE in the second message to indicate to the terminal whether it supports use of the first slice in the first TA. Optionally, as shown in Figure 5, the extended Rejected NSSAI IE includes a partial extended Rejected NSSAI List domain. Optionally, as shown in Figures 6a and 6b, the partial extended Rejected NSSAI List domain includes a Rejected NSSAI domain corresponding to each first slice in at least one first slice. Optionally, as shown in Figure 7, the Rejected NSSAI domain in the partial extended Rejected NSSAI List domain includes at least one of information about the first slice and first indication information. Optionally, the first indication information is 0100, indicating that the slice is unavailable in the current TA. Furthermore, after receiving the Rejected NSSAI Domain information in the extended Rejected NSSAI IE, the terminal can determine that the first slice is unavailable in the current TA based on the information in the Rejected NSSAI domain, so that the terminal can select another slice in the requested slice in the current TA to communicate and establish a connection with the network side device.

[0043] In the method of the above embodiment, the network side device indicates that the slice is unavailable in the current TA by carrying information of the first slice and / or first indication information in the Rejection NSSAI IE, the first IE, or the extended Rejection NSSAI IE in the second message, and further, after receiving the second message, the terminal can determine that the first slice is unavailable in the current TA based on the Rejection NSSAI IE, the first IE, or the extended Rejection NSSAI IE in the second message, so that the terminal can select another slice in the requested slice in the current TA to establish communication and connection with the network side device. In the embodiments of the present application, the network side device can instruct the terminal whether the requested slice can be used in a tracking area TA in various manners, which is relatively flexible.

[0044] In one embodiment, the second message includes a Reject Network Slice Selection Assistance Information (NSSAI) information element (IE) or a first IE, wherein the Reject NSSAI IE or the first IE includes a Reject NSSAI domain corresponding to each first slice in the at least one first slice, and the Reject NSSAI domain corresponding to each first slice includes at least one of information of the first slice, second indication information, and information of the first TA; and / or The second message includes an extended Rejected NSSAI IE, the extended Rejected NSSAI IE includes a partial extended Rejected NSSAI List domain, the partial extended Rejected NSSAI List domain includes a Rejected NSSAI domain corresponding to each first slice in at least one first slice, and the Rejected NSSAI domain corresponding to each first slice includes at least one of information of the first slice, second indication information, and information of the first TA.

[0045] Specifically, the network side device indicates to the terminal whether to support the use of the requested slice in the target tracking area (TA) through a Reject Network Slice Selection Support Information (NSSAI) information element (IE) or a first IE in the second message, where the first IE may be a newly defined information element. Optionally, as shown in FIG. 8, the Reject NSSAI IE includes a Reject NSSAI domain corresponding to each first slice in at least one first slice. Optionally, as shown in FIG. 9, the Reject NSSAI domain corresponding to each first slice includes at least one of information of the first slice, second indication information, and information of the first TA. Optionally, the second indication information is 0100, indicating that the first slice is unavailable in the first TA. Furthermore, after receiving the Reject NSSAI IE in the second message or the Reject NSSAI domain information in the first IE, the terminal can determine that the first slice is unavailable in the first TA based on the information in the Reject NSSAI domain, and thus the terminal can select another slice in the requested slice to communicate and establish a connection with the network side device.

[0046] Optionally, the network side device may use an extended Rejected NSSAI IE in the second message to indicate to the terminal whether it supports use of the requested slice in the target tracking area (TA). Optionally, as shown in Figure 10, the extended Rejected NSSAI IE includes a partial extended Rejected NSSAI list domain. As shown in Figures 11a and 11b, the partial extended Rejected NSSAI list domain includes a Rejected NSSAI domain corresponding to at least one first slice. Optionally, as shown in Figure 12, the Rejected NSSAI domain includes at least one of information about the first slice, second indication information, and information about the first TA, where the second indication information is 0100 and indicates that the first slice is unavailable in the first TA. Further, after receiving the Rejected NSSAI domain information in the extended Rejected NSSAI IE, the terminal can determine that the first slice is unavailable in the first TA based on the information in the Rejected NSSAI domain, so that the terminal can select another slice in the requested slice to communicate and establish a connection with the network side device.

[0047] In the method of the above embodiment, the network side device indicates that the first slice is not available in the first TA through the information of the first slice, the second indication information, and / or the information of the first TA carried in the NSSAI-Rejection IE, the first IE, or the extended NSSAI-Rejection IE in the second message; furthermore, after receiving the second message, the terminal can determine that the first slice is not available in the first TA based on the NSSAI-Rejection IE, the first IE, or the extended NSSAI-Rejection IE in the second message, so that the terminal can select another slice in the requested slice to establish communication and connection with the network side device. In the embodiment of the present application, the network side device can instruct the terminal whether the requested slice can be used in the tracking area TA in various manners, which is relatively flexible.

[0048] In one embodiment, the second message includes an NSSAI Service Area List IE, wherein the NSSAI Service Area List IE includes at least one NSSAI Service Area List domain, each NSSAI Service Area List domain including an NSSAI field of a third slice, an NSSAI Service Area List field, and a target timer field, and the NSSAI Service Area List field includes at least one of third indication information and third TA information.

[0049] Specifically, the network side device uses an NSSAI Service Area List IE in the second message to indicate to the terminal whether it supports use of the third slice in the third TA. Optionally, the NSSAI Service Area List IE shown in FIG. 13 includes at least one NSSAI Service Area List domain, and the NSSAI Service Area List domain shown in FIG. 14 includes an NSSAI field for the third slice, an NSSAI Service Area List field, and a target timer field. Optionally, the third indication information carries the target timer field when indicating that the third TA is a TA that does not support use of the third slice. The target timer field is used to indicate that the third slice is unavailable in the third TA within a time period corresponding to the target timer field. After the time period corresponding to the target timer field, the terminal may attempt to use the third slice in the third TA. Optionally, as shown in FIG. 15a to FIG. 15d, the NSSAI Service Area List field includes at least one of the third indication information and information about the third TA. Here, the third indication information is used to indicate whether the third TA is a TA that supports the use of the third slice or a TA that does not support the use of the third slice. Optionally, if the third indication information is 0 and indicates that the third TA is a TA that supports the use of the third slice, the terminal can use the third slice when it is in the third TA. If the third indication information is 1 and indicates that the third TA is a TA that does not support the use of the third slice, the terminal cannot use the third slice when it is in the third TA. Optionally, the terminal starts a timer, which may be a default value or may be configured for the terminal by the network side device in the NSSAI Service Area List IE in the second message. Optionally, the third slice can be used for the terminal only when the terminal moves away from the third TA or after the timer expires. Optionally, the terminal needs to select another slice to communicate and establish a connection with the network side device when it is in the third TA.Optionally, the NSSAI Service Area List Domain may further include a List Type and a Number of Elements, where the List Type is used to indicate the type of the NSSAI Service Area List Domain and is represented by at least one bit, for example, where 00 represents a TAC list belonging to one PLMN and having non-consecutive TAC values, 01 represents a TAC list belonging to one PLMN and having consecutive TAC values, 10 represents a TAI list belonging to different PLMNs, and 11 represents all TAIs belonging to PLMNs in the registration area are in the allowed area. For example, the format of the NSSAI Service Area List field may be different for different list types. As shown in Figures 15a and 15b, the third indication information is used to indicate that the third TA is a TA that does not support the use of the third slice, and the element number is used to indicate the number of TAs that do not support the use of the third slice included in the NSSAI service area list domain, and the third indication information is used to indicate that the third TA is a TA that supports the use of the third slice, and the element number is used to indicate the number of TAs that support the use of the third slice included in the NSSAI service area list domain.

[0050] The information in tracking area 1 in Figures 15a-15c can be represented by one byte or multiple bytes, and the information in other tracking areas is similar, and one row in Figures 15a-15c represents one byte, and from left to right represents from top to bottom, and the information in other figures is similar.

[0051] For example, the network side device carries a TA list of one or more S-NSSAIs in the second message, and indicates by instruction information whether the TA list is a rejected TAI list and / or an allowed TAI list, and optionally, the rejected TAI list indicates that the use of a certain slice is rejected in the TA in the rejected TA list, and the allowed TAI list indicates that the use of a certain slice is permitted in the TA in the allowed TA list.

[0052] In the method of the above embodiment, the network side device indicates that the third TA is a TA that supports the use of the third slice or a TA that does not support the use of the third slice by carrying third indication information, namely, information on the third TA, in the NSSAI Service Area List IE in the second message. Furthermore, after receiving the second message, the terminal can determine whether a slice is available in the third TA based on the NSSAI Service Area List IE in the second message, thereby realizing the terminal's selection and use of slices based on the TA granularity and improving slice usage efficiency.

[0053] In one embodiment, the second message includes an extended Allowed NSSAI IE, where the extended Allowed NSSAI IE includes an Allowed NSSAI domain for each second slice in at least one second slice, and the Allowed NSSAI domain corresponding to each second slice includes at least one of the length of the Allowed NSSAI domain, the NSSAI field of the second slice, and information of the second TA.

[0054] Specifically, the network side device uses the extended allowed NSSAI IE in the second message to instruct the terminal whether to support the use of the second slice in the second TA. Optionally, as shown in FIG. 16, the extended allowed NSSAI IE includes an allowed NSSAI domain corresponding to at least one second slice, and as shown in FIG. 17, the allowed NSSAI domain includes at least one of the length of the allowed NSSAI domain, the NSSAI field of the second slice, and information about the second TA. After receiving the allowed NSSAI domain information in the extended allowed NSSAI IE, the terminal can determine that the second slice is available in the second TA based on the information in the allowed NSSAI domain, thereby realizing the selection and use of slices based on the TA granularity of the terminal.

[0055] In the method of the above embodiment, the network side device carries the NSSAI field of the second slice and information of the second TA in the extended authorization NSSAI IE in the second message, so that after the terminal receives the second message, it can determine that the second slice is available in the second TA based on the extended authorization NSSAI IE in the second message, thereby realizing the selection and use of slices based on the TA granularity of the terminal and improving the efficiency of slice use.

[0056] In one embodiment, the first TA includes a TA that does not support use of the first slice within a preset time range.

[0057] Specifically, the first TA includes a TA that does not support the use of the first slice within a predetermined time range, i.e., the target tracking area TA does not support the use of the first slice within the predetermined time range, and after the predetermined time range, the terminal may attempt to use the first slice within the target tracking area, so that the first slice is fully utilized within the target tracking area TA, thereby improving the slice utilization efficiency.

[0058] Optionally, the second message further includes information of a first timer, which is used to indicate that the terminal can use the first slice in the first TA after the first timer expires.

[0059] Specifically, if the first TA includes a TA that does not support the use of the first slice within a predetermined time range, the network side equipment conveys information of the first timer in the second message, where the first timer is used to indicate that the terminal can use the first slice in the first TA after the first timer expires, i.e., after the terminal receives the first timer in the second message and the first timer expires, the terminal may attempt to use the first slice in the first TA, thereby fully utilizing the first slice within the first TA and improving slice utilization efficiency.

[0060] In the method of the above embodiment, if the first TA includes a TA that does not support the use of the first slice within a predetermined time range, the network side equipment conveys information of the first timer in the second message, so that after the terminal receives the first timer in the second message and the first timer expires, the terminal may attempt to use the first slice in the first TA, thereby ensuring that the first slice is fully utilized within the first TA and improving slice utilization efficiency.

[0061] In one embodiment, after the terminal receives the second message sent by the network side device, The terminal further includes transmitting a third message to the network side device, wherein the third message is used to indicate that the terminal has received information for indicating whether the terminal supports use of the requested slice in the target tracking area TA.

[0062] Specifically, after the terminal receives the second message sent by the network side equipment, the terminal may send a third message to the network side equipment, which is used to inform the network side equipment that the terminal has received information to indicate whether it supports the use of the requested slice in the tracking area TA, and the network side equipment and the terminal can establish connection and communication based on the requested slice available in the target tracking area TA, thereby improving the efficiency of slice usage.

[0063] In one embodiment, after receiving the second message sent by the network side device, the terminal: For each first TA or current TA, the terminal adds information of the first slice that the first TA or current TA does not support to use to a rejected slice list corresponding to the first TA or current TA; For each second TA, the terminal adds information of a second slice that the second TA supports to use to an allowed slice list corresponding to the second TA; The terminal stores information of a first slice in each access type and information of a first TA that does not support use of the first slice; The terminal stores information of the second slice in each access type and information of the second TA supporting the use of the second slice; and starting a second timer, wherein the second timer is used to instruct the terminal to delete the first slice from a rejected slice list in the first TA or the current TA after the second timer expires, and the terminal can use the first slice in the first TA or the current TA.

[0064] Optionally, if the first timer is carried in the first message, the value of the second timer is the same as the value of the first timer, e.g., the start times of the first timer and the second timer are the same and the lengths of the timed periods are the same. In particular, if the value of the first timer is 0 or a negative value, the second timer is not started. If the first timer is not carried in the first message, the second timer is not started or is started as a default value.

[0065] Specifically, after receiving the second message sent by the network side device, the terminal may process slice application information indicated in the second message based on information indicated in the second message about whether the use of the requested slice in the target tracking area (TA) is supported; optionally, the terminal may add at least one first slice to a rejected slice list in its corresponding at least one first TA or current TA, so that the terminal cannot use the first slice in the first TA or the current TA and needs to select and use another slice in the requested slice; optionally, the terminal may store information of the at least one first slice in each access type and information of the first TA that does not support the use of the corresponding at least one first slice; optionally, the terminal may store information of the at least one first slice in each access type and information of the first TA that does not support the use of the at least one first slice; optionally, the terminal may store information of the at least one first slice in each access type and information of the first TA that does not support the use of the at least one first slice; optionally, the terminal may store information of the at least one first slice in each access type and information of the first TA that does not support the use of the at least one first slice; optionally, the terminal may store information of the at least one first slice in each access type and information of the first TA that does not support the use of the at least one first slice; optionally, the terminal may store information of the at least one first slice in each access type and information of the at least one ... Project, 3GPP) access type or non-3GPP access type, that is, the terminal may store information about the first slice and information about a first TA that does not support use of the first slice, and may not be able to use the first slice when located in the first TA. Correspondingly, the terminal may use a slice other than the first slice in the requested slice when located in the first TA. Optionally, the terminal may store information about a second slice for each access type and information about a second TA that supports use of the second slice, thereby allowing the terminal to use the second slice when located in the second TA, realizing slice use based on TA granularity and improving slice utilization efficiency. Optionally, the terminal starts a second timer, and after the second timer expires, the terminal removes the first slice from the rejected slice list in the first TA or the current TA, thereby allowing the terminal to use the first slice in the first TA or the current TA. That is, after the second timer expires, the terminal may attempt to use the first slice in the first TA or the current TA, thereby ensuring that the first slice is fully utilized in the first TA or the current TA and improving slice utilization efficiency.

[0066] For example, the terminal stores the first slice as a rejected slice within the current tracking area, and for each access type, the first slice is stored based on TA granularity, i.e., the first slice is associated with a TA.

[0067] For example, the terminal stores the second slice as a permitted slice within the current tracking area, and for each access type, the second slice is stored based on TA granularity, i.e., the second slice is associated with a TA.

[0068] In the method of the above embodiment, after receiving the second message sent by the network side equipment, the terminal can process the slice application information indicated in the second message, so that the terminal can accurately and effectively select and use slices based on the TA granularity based on the slice application information indicated in the second message, thereby improving the efficiency of slice usage.

[0069] In one embodiment, for any one first slice of the at least one first slice, if the first slice is included in the rejected slice list corresponding to a sixth TA, the sixth TA is any one TA of the one or more first TAs or the current TA, and the terminal: After the device shuts down and restarts, The terminal moves away from the first TA or the current TA; and the terminal is located within a second TA; After the universal subscriber identity module USIM of the terminal is removed, After the subscription data with the network identifier of the current network in which the terminal is located is updated, after a first timer configured by the network side device expires; and after a second timer that starts after the terminal receives the second message expires, the terminal may use the first slice; and The first timer or the second timer is used to indicate that after the timer expires, the terminal can use the first slice in the first TA or the current TA.

[0070] Specifically, to improve slice utilization efficiency, the embodiments of the present application may attempt to use the first slice if the following target conditions are met, so that the first slice is fully utilized within the tracking area TA and improve slice utilization efficiency: Alternatively, after the terminal is shut down and restarted, the terminal may attempt to use the first slice; optionally, the terminal may move away from the first TA or the current TA or attempt to use the first slice when the terminal is in a second TA; optionally, after the terminal's universal subscriber identity module (USIM) is removed or subscription data with a network identifier of the current network in which the terminal is located is updated, the terminal may attempt to use the first slice; optionally, the network side equipment carries a first timer in the second message, and after the first timer or the second timer expires, the terminal may attempt to use the first slice, that is, if the tracking area (TA) in which the terminal is located changes or the configuration information of the terminal changes, the terminal may attempt to use the first slice, so that the first slice is fully utilized in the TA, effectively meeting the demand for establishing connection and communication between the terminal and the network side equipment and improving slice utilization efficiency.

[0071] For example, when first TA information based on slice granularity is received, the TA in the first TA information of the terminal cannot use the first slice, and when the terminal moves away from the TA in the first TA information, the terminal may attempt to use the first slice; When receiving second TA information based on slice granularity, the TA in the second TA information of the terminal can use the second slice, and when the terminal moves away from the TA in the second TA information and is still within the current RA, the second slice is no longer permitted to be used, and the terminal stores the second slice as a rejected slice in the current tracking area; When receiving the first TA information based on slice granularity, the terminal cannot use the first slice in the TA in the first TA. When the terminal is in the TA in the first TA, the terminal moves the first slice to a rejected slice list; When receiving second TA information based on slice granularity, if the terminal is within a TA in the second TA information, the terminal moves the second slice to the allowed slice list, and the terminal can use the second slice in the second TA.

[0072] In the method of the above embodiment, if the target condition is met, the terminal attempts to use the first slice, so that the first slice is fully utilized within the TA, effectively meeting the demand for establishing connection and communication between the terminal and the network side equipment, and improving the utilization efficiency of the slice.

[0073] In one embodiment, if the terminal satisfies at least one target condition, the terminal: The terminal deletes the first slice from the rejected slice list corresponding to the sixth TA; An operation in which the terminal updates the first slice to a slice available in the sixth TA; and the terminal performs at least one operation of transmitting a fourth message to the network side device, and the fourth message is The terminal capability indication information includes at least one of first target slice information to be used and terminal capability indication information, where the terminal capability indication information is used to indicate whether the terminal supports the first capability, and the first capability is an ability to receive and use information to indicate whether the terminal supports the use of the requested slice within the target TA.

[0074] Specifically, if the terminal satisfies the target condition, the terminal may timely update the application status of the slice stored in the terminal in the TA and attempt to use the first slice in the TA, thereby improving the utilization efficiency of the TA and meeting the needs of the terminal and the network side device to establish connection and communication. Optionally, if the target condition is met, the terminal may delete the first slice from the rejected slice list in the first TA or the current TA, or update the first slice to an available slice in the first TA or the current TA, and the terminal may further attempt to use the first slice in the first TA or the current TA, so that the first slice is fully utilized in the TA and improving the utilization efficiency of the slice. Optionally, the terminal may send a fourth message to the network side device, i.e., send slice information that the terminal intends to use and terminal capability indication information shown in Figure 18 to the network side device. Optionally, the terminal capability indication information is used to characterize the terminal's support for network slice extended TA list information, so that the network side device can timely and accurately indicate to the terminal whether to support the use of the requested slice in the target tracking area TA based on the updated requested slice information.

[0075] Optionally, if the terminal capability indication information indicates that the terminal supports the first capability, the network side device carries information for indicating whether to support using the requested slice in the target tracking area TA in the second message; if the terminal capability indication information indicates that the terminal does not support the first capability, the network side device does not carry information for indicating whether to support using the requested slice in the target tracking area TA in the second message; In the method of the above embodiment, if the terminal meets the target conditions, the terminal may timely update the application status of the slice stored in itself within the TA and attempt to use the slice within the TA, thereby effectively improving the utilization efficiency of the slice and meeting the needs of the terminal and the network side equipment to establish connection and communication.

[0076] In one embodiment, the terminal receives slice information of a first target network configuration sent by a network side device; If the slice information includes second target slice information in the rejected slice list in the fourth TA, the terminal deletes the second target slice information from the rejected slice list and stops timing of the second timer associated with the second target slice information, and the fourth TA is a TA corresponding to the first target network.

[0077] Specifically, when the terminal receives new slice configuration information in a first target network (e.g., a public land mobile network PLMN or a standalone non-public network SNPN) sent by the network side equipment, if the slice information in the rejected slice list is included in the new slice configuration information in the target PLMN or SNPN network, the terminal deletes the information that does not support the use of the slice in the corresponding TA from the rejected slice list and stops the associated timer, so that the terminal can accurately and effectively use the slice in the TA based on the updated slice application information, thereby improving slice utilization efficiency.

[0078] In the method of the above embodiment, the terminal receives slice information of the first target network configuration sent by the network side equipment, and updates the slice information in the rejected slice list stored by the terminal itself based on the slice information of the first target network configuration sent by the network side equipment, so that the terminal can accurately and effectively use slices within the TA based on the updated slice application information, thereby improving slice utilization efficiency.

[0079] In one embodiment, the terminal receives slice information permitted by the second target network sent by the network side device; If the allowed slice information includes the third target slice information in the rejected slice list in the fifth TA, the terminal deletes the third target slice information from the rejected slice list and stops timing of the second timer associated with the third target slice information, and the fifth TA is a TA corresponding to the second target network.

[0080] Specifically, when the terminal receives network-approved slice information in a second target network (e.g., a target PLMN or an SNPN network) sent by a network side device, if the slice information in the rejected slice list is included in the network-approved slice information in the target PLMN or SNPN network, the terminal deletes the information that does not support the use of the slice in the corresponding TA from the rejected slice list and stops the associated timer, thereby enabling the terminal to accurately and effectively use the slice in the TA based on the updated slice application information, thereby improving slice utilization efficiency.

[0081] In the method of the above embodiment, the terminal receives slice information permitted by the second target network sent by the network side equipment, and updates the slice information in the rejected slice list stored by the terminal itself based on the slice information permitted by the second target network sent by the network side equipment.This allows the terminal to accurately and effectively use slices within the TA based on the updated slice application information, thereby improving slice utilization efficiency.

[0082] In one embodiment, the first message comprises: The information includes at least one of information on the requested slice and terminal capability indication information, where the terminal capability indication information is used to indicate whether the terminal supports a first capability, and the first capability is an ability to receive and use information to indicate whether the terminal supports use of the requested slice in the target TA.

[0083] Specifically, when the terminal sends a first message to the network side device, the first message may include information on a requested slice and terminal capability indication information, where the information on the requested slice is slice information that the terminal requests to use to establish a connection with the network side device, and the terminal capability indication information is used to indicate whether the terminal does not use the requested slice in the target TA and / or supports using the requested slice in the target TA, so that after receiving the information on the requested slice and the terminal capability indication information sent by the terminal, the terminal can determine whether it needs to instruct the terminal on slice application information based on TA granularity and / or whether the requested slice needs to accurately indicate the application status in the target tracking area to the terminal.

[0084] In the method of the above embodiment, the terminal sends a second message including requested slice information and terminal capability indication information to the network side equipment, so that the network side equipment can determine based on the second message whether it needs to instruct the terminal on slice application information based on TA granularity and / or whether it needs to accurately instruct the terminal on the application status of the requested slice in the target tracking area, thereby allowing the terminal and the network side equipment to efficiently utilize the requested slice to establish connection and communication.

[0085] 19 is a second flowchart of a communication method according to an embodiment of the present application. As shown in FIG. 19, the method according to this embodiment includes: In step 1901, the network side device receives a first message sent by a terminal to request establishing a connection with the network side device using a request slice; In step 1902, the network side device includes sending, to the terminal, a second message carrying information to indicate whether or not the terminal supports use of the requested slice in the target tracking area TA.

[0086] Optionally, the second message is The target tracking area (TA) includes at least one of information of at least one first slice and first indication information, wherein the first indication information is used to indicate that the at least one first slice is unavailable within the current TA, where the first slice is a slice in the request slice, and the target tracking area (TA) includes the current TA; or The second message is The target tracking area TA includes at least one of information on at least one first slice, information on one or more first TAs corresponding to each first slice in the at least one first slice, information on at least one second slice, information on one or more second TAs corresponding to each second slice in the at least one second slice, and second indication information, wherein the first TA is a TA that does not support use of the first slice, and the second TA is a TA that supports use of the second slice, and the second indication information is used to indicate that the first slice is not available within the first TA, where the first slice or the second slice is a slice in the requested slice, and the target tracking area TA includes the first TA or the second TA, or The second message is The request slice includes at least one of at least one third slice, information about the third TA, and third instruction information, where the third instruction information is used to indicate whether the third TA is a TA that supports the use of the third slice or a TA that does not support the use of the third slice, the target TA includes the third TA, and the third slice is a slice in the request slice.

[0087] Optionally, the second message includes a Reject Network Slice Selection Assistance Information NSSAI information element IE or a first IE, wherein the Reject NSSAI IE or the first IE includes a Reject NSSAI domain corresponding to each first slice in the at least one first slice, and the Reject NSSAI domain corresponding to each first slice includes at least one of information of the first slice and first indication information; and / or The second message includes an extended Rejected NSSAI IE, the extended Rejected NSSAI IE includes a partial extended Rejected NSSAI List domain, the partial extended Rejected NSSAI List domain includes a Rejected NSSAI domain corresponding to each first slice in at least one first slice, and the Rejected NSSAI domain corresponding to each first slice includes at least one of information of the first slice and first indication information.

[0088] Optionally, the second message includes a Reject Network Slice Selection Assistance Information (NSSAI) information element (IE) or a first IE, wherein the Reject NSSAI IE or the first IE includes a Reject NSSAI domain corresponding to each first slice in the at least one first slice, and the Reject NSSAI domain corresponding to each first slice includes at least one of information of the first slice, second indication information, and information of the first TA; and / or The second message includes an extended Rejected NSSAI IE, the extended Rejected NSSAI IE includes a partial extended Rejected NSSAI List domain, the partial extended Rejected NSSAI List domain includes a Rejected NSSAI domain corresponding to each first slice in at least one first slice, and the Rejected NSSAI domain corresponding to each first slice includes at least one of information of the first slice, second indication information, and information of the first TA.

[0089] Optionally, the second message includes an NSSAI Service Area List IE, each NSSAI Service Area List IE including at least one NSSAI Service Area List domain, the NSSAI Service Area List domain including an NSSAI field of a third slice, an NSSAI Service Area List field, and a target timer field, and the NSSAI Service Area List field including at least one of third indication information and information of a third TA.

[0090] Optionally, the second message includes an extended Authorization NSSAI IE, in which an Authorized NSSAI domain corresponding to each at least one second slice is included, and the Authorized NSSAI domain corresponding to each second slice includes at least one of the length of the Authorized NSSAI domain, the NSSAI field of the second slice, and information of the second TA.

[0091] Optionally, the first TA includes a TA that does not support use of the first slice within the preset time range.

[0092] Optionally, the second message further includes information of a first timer, which is used to indicate that the terminal can use the first slice in the first TA after the first timer expires.

[0093] Optionally, the network side equipment receives a third message sent by the terminal, the third message being used to indicate that the terminal has received information for indicating whether it supports the use of the requested slice within the target tracking area TA.

[0094] Optionally, the first message is: The information includes at least one of information on the requested slice and terminal capability indication information, where the terminal capability indication information is used to indicate whether the terminal supports a first capability, and the first capability is an ability to receive and use information to indicate whether the terminal supports use of the requested slice in the target TA.

[0095] Illustratively, one of the interaction flowcharts of the communication method according to an embodiment of the present application is as shown in FIG.

[0096] In step 1, the terminal sends a first message to a first core network network element AMF to establish an N1 connection between the terminal and the network, optionally, the first message may be a registration request message, and the first message may include: (1) terminal capability indication information, the terminal capability indication information being used to indicate whether the terminal supports a first capability, the first capability being a capability to receive and use information to indicate whether the terminal supports use of the requested slice in the target TA; (2) request slice information including one or more single network slice selection assistance information (S-NSSAI); The network side device (for example, the first core network network element AMF) performs at least one of the following operations when receiving the slicing request from the terminal: In step 2, the first core network network element AMF queries the second core network network element (e.g., unified data management unit UDM / network slice selection network element MSSF) to confirm the application status of each TA in the current and / or other RA of the S-NSSAI in the requested slice information. Here, the application status refers to whether to allow the requested slice to be provided with service or to deny the requested slice to be provided with service. If the slice is allowed to be provided with service, the slice is included in an allowed network slice selection support information domain S-NSSAI (allowed S-NSSAI) and returned to the terminal. If the slice is denied to be provided with service, the slice is included in a rejected network slice selection support information domain S-NSSAI (rejected S-NSSAI) and returned to the terminal. In step 3, the first core network network element AMF sends a second message to the terminal, where the second message is used to indicate whether the establishment of an N1 connection between the terminal and the network has been successful or failed.

[0097] Optionally, the first core network network element AMF carries one or more rejected network slice selection assistance information domains (rejected S-NSSAI) in the second message, where the rejected network slice selection assistance information domains (rejected S-NSSAI) indicate that the slice is not available within the current registration area (RA) and carry a first cause value of "the slice is not available in the current registration area", and optionally carry a timer a, which is used to instruct the terminal to attempt to initiate the request using the slice after waiting for the expiration of the timer a; Optionally, the second message is and / or The second message is At least one of information on at least one first slice, information on a first TA corresponding to each of the at least one first slice, information on at least one second slice, information on a second TA corresponding to each of the at least one second slice, and second instruction information; or The second message is The information includes at least one of at least one request slice, third TA information, and third instruction information.

[0098] That is, after receiving a request from the terminal, the first core network network element AMF notifies the terminal of TA list information that supports and / or denies the use of a slice based on slice granularity based on the application status of multiple TAs in the RA of the slice, and after receiving the TA list information that supports and / or denies the use of a slice based on slice granularity, the terminal combines the TA information of its current location to determine whether the slice can be used in the current TA.

[0099] Alternatively, when the network side device indicates that the N1 connection between the terminal and the network is successful, the first core network network element AMF conveys information that the terminal does not support not using the requested slice in the target TA to the terminal in a Rejected Network Slice Selection Support Information information element and / or an Extended Rejected Network Slice Selection Support Information information element and / or a newly defined first IE in the Registration Complete message, and conveys information that the terminal supports using the requested slice in the target TA to the terminal in an Extended Allowed Network Slice Selection Support Information information element and / or a newly defined IE in the Registration Complete message; If the network side equipment indicates that the N1 connection between the terminal and the network has failed, the first core network network element AMF conveys information that the terminal does not support not using the requested slice in the target TA to the terminal in the information element of rejected network slice selection support information and / or the information element of extended rejected network slice selection support information and / or the newly defined first IE in the registration rejection message.

[0100] In step 4, after receiving the second message, if the second message indicates that the N1 connection between the terminal and the network is successful and the second message includes first TA information and / or second TA information and / or indication information based on slice granularity, the terminal sends a third message to the first core network network element AMF, and the third message is used to confirm that the terminal has received the first TA information and / or second TA information and / or indication information based on slice granularity, i.e., to confirm that the terminal has received information to indicate whether it supports the use of the requested slice within the tracking area TA.

[0101] In step 5, after receiving the second message, the terminal cannot use the first slice in the first TA, and cannot use the slice until the timer expires or it moves to the second TA range.

[0102] In step 6, if the above use conditions are met, the terminal can use the first slice, and the terminal performs at least one of the following operations: (1) removing a first slice from a list of rejected slices in the current tracking area and identifying the slice as available for normal requests after removal; (2) Based on the service demand and slice selection, the terminal sends the following indication information to the first core network network element AMF, which is used for mobility or periodic registration update: Optionally, the terminal sends a fourth message to the network side device, the fourth message being a request message; A. Terminal capability indication information for instructing a terminal to support a function of initiating a slice request in a TA supported in the same RA, where the function of initiating a slice request in a TA supported in the same RA means that if the requested slice is rejected in the current TA but is acceptable in another TA in the same RA, the terminal can use the requested slice when moving to another TA; and B, and requested slice information including one or more first slices; In step 7, after receiving the terminal message, the first core network network element AMF confirms that the current network can provide the requested slice, and then indicates that the N1 connection between the terminal and the network is successful. Optionally, the fifth message includes first slice information available in the target tracking area, and optionally, the fifth message may be a registration acceptance message; In step 8, after the terminal receives the registration acceptance message, the terminal sends a sixth message to the first core network network element AMF, where the sixth message is used to check whether the terminal has received information instructing the terminal not to use the requested slice in the target TA and / or whether it supports using the requested slice in the target TA, and optionally, the sixth message may be a registration completion message.

[0103] The communication method according to the embodiment of the present application may be executed by a virtual device. In the embodiment of the present application, the communication device according to the embodiment of the present application will be described taking the case where the virtual device executes the communication method as an example.

[0104] 21 is a structural schematic diagram of a communication device according to an embodiment of the present application. As shown in FIG. 21, the communication device according to this embodiment includes: a sending module 2101 for sending a first message to a network side device to request the network side device to establish a connection with the network side device using a request slice; and a receiving module 2102 for receiving a second message transmitted by the network side device, the second message carrying information for indicating whether to support use of the requested slice within the target tracking area TA.

[0105] Optionally, the second message is The target tracking area (TA) includes at least one of information of at least one first slice and first indication information, wherein the first indication information is used to indicate that the at least one first slice is unavailable within the current TA, where the first slice is a slice in the request slice, and the target tracking area (TA) includes the current TA; or The second message is The target tracking area TA includes at least one of information on at least one first slice, information on one or more first TAs corresponding to each first slice in the at least one first slice, information on at least one second slice, information on one or more second TAs corresponding to each second slice in the at least one second slice, and second indication information, wherein the first TA is a TA that does not support use of the first slice, and the second TA is a TA that supports use of the second slice, and the second indication information is used to indicate that the first slice is not available in the first TA, where the first slice or the second slice is a slice in the requested slice, and the target tracking area TA includes the first TA or the second TA, or The second message is The information includes at least one of information on at least one third slice, information on a third TA, and third instruction information, where the third instruction information is used to indicate whether the third TA is a TA that supports the use of the third slice or a TA that does not support the use of the third slice, the target TA includes the third TA, and the third slice is a slice in the requested slice.

[0106] Optionally, the second message includes a Reject Network Slice Selection Assistance Information NSSAI information element IE or a first IE, wherein the Reject NSSAI IE or the first IE includes a Reject NSSAI domain corresponding to each first slice in the at least one first slice, and the Reject NSSAI domain corresponding to each first slice includes at least one of information of the first slice and first indication information; and / or The second message includes an extended Rejected NSSAI IE, the extended Rejected NSSAI IE includes a partial extended Rejected NSSAI List domain, the partial extended Rejected NSSAI List domain includes a Rejected NSSAI domain corresponding to each first slice in at least one first slice, and the Rejected NSSAI domain corresponding to each first slice includes at least one of information of the first slice and first indication information.

[0107] Optionally, the second message includes a Reject Network Slice Selection Assistance Information (NSSAI) information element (IE) or a first IE, wherein the Reject NSSAI IE or the first IE includes a Reject NSSAI domain corresponding to each first slice in the at least one first slice, and the Reject NSSAI domain corresponding to each first slice includes at least one of information of the first slice, second indication information, and information of the first TA; and / or The second message includes an extended Rejected NSSAI IE, the extended Rejected NSSAI IE includes a partial extended Rejected NSSAI List domain, the partial extended Rejected NSSAI List domain includes a Rejected NSSAI domain corresponding to each first slice in at least one first slice, and the Rejected NSSAI domain corresponding to each first slice includes at least one of information of the first slice, second indication information, and information of the first TA.

[0108] Optionally, the second message includes an NSSAI Service Area List IE, wherein the NSSAI Service Area List IE includes at least one NSSAI Service Area List domain, each NSSAI Service Area List domain includes an NSSAI field of a third slice, an NSSAI Service Area List field, and a target timer field, and the NSSAI Service Area List field includes at least one of third indication information and information of a third TA.

[0109] Optionally, the second message includes an extended Authorization NSSAI IE, in which an Authorized NSSAI domain corresponding to each at least one second slice is included, and the Authorized NSSAI domain corresponding to each second slice includes at least one of the length of the Authorized NSSAI domain, the NSSAI field of the second slice, and information of the second TA.

[0110] Optionally, the first TA includes a TA that does not support use of the first slice within the preset time range.

[0111] Optionally, the second message further includes information of a first timer, which is used to indicate that the terminal can use the first slice in the first TA after the first timer expires.

[0112] Optionally, the sending module 2101 is further used for sending a third message to the network side equipment, and the third message is used for indicating that the terminal has received information for indicating whether it supports the use of the requested slice within the target tracking area TA.

[0113] Optionally, the receiving module 2102 further comprises: for each first TA or the current TA, the terminal adds information of the first slice that the first TA or the current TA does not support for use to a rejected slice list corresponding to the first TA or the current TA; For each second TA, the terminal adds information of a second slice that the second TA supports to use to an allowed slice list corresponding to the second TA; Storing information of a first slice in each access type and information of a first TA that does not support the use of the first slice; storing information of a second slice for each access type and information of a second TA supporting the use of the second slice; and starting a second timer, which is used to indicate that the terminal can use the first slice in the first TA or the current TA after the second timer expires.

[0114] Optionally, the receiving module 2102 further determines, for any one first slice of the at least one first slice, if the first slice is included in the rejected slice list corresponding to a sixth TA, the sixth TA is any one TA of the one or more first TAs or the current TA; After the device shuts down and restarts, The terminal moves away from the first TA or the current TA; and the terminal is located within a second TA; After the universal subscriber identity module USIM of the terminal is removed, After the subscription data with the network identifier of the current network in which the terminal is located is updated, after a first timer configured by the network side device expires; and after a second timer that is started after the terminal receives the second message expires, the first slice can be used if the terminal satisfies at least one target condition; The first timer or the second timer is used to indicate that after the timer expires, the terminal can use the first slice in the first TA or the current TA.

[0115] Optionally, the receiving module 2102 further comprises, if at least one target condition is met: removing the first slice from a rejected slice list corresponding to the sixth TA; updating the first slice to a slice available in the sixth TA; and transmitting a fourth message to the network side device, wherein the fourth message is The terminal capability indication information includes at least one of first target slice information to be used and terminal capability indication information, where the terminal capability indication information is used to indicate whether the terminal supports the first capability, and the first capability is an ability to receive and use information to indicate whether the terminal supports the use of the requested slice within the target TA.

[0116] Optionally, the receiving module 2102 is further used for receiving slice information of the first target network configuration sent by the network side device; If the slice information includes second target slice information in the rejected slice list corresponding to the fourth TA, the second target slice information is deleted from the rejected slice list, and the second timer associated with the second target slice information is stopped, and the fourth TA is a TA corresponding to the first target network.

[0117] Optionally, the receiving module 2102 is further used for receiving slice information permitted by the second target network sent by the network side device; If the allowed slice information includes third target slice information in the rejected slice list corresponding to the fifth TA, the third target slice information is deleted from the rejected slice list, and the second timer associated with the third target slice information is stopped, and the fifth TA is a TA corresponding to the second target network.

[0118] Optionally, the first message is: The information includes at least one of information on the requested slice and terminal capability indication information, where the terminal capability indication information is used to indicate whether the terminal supports a first capability, and the first capability is an ability to receive and use information to indicate whether the terminal supports use of the requested slice in the target TA.

[0119] The device of this embodiment can be used to implement the method of any one of the embodiments of the terminal-side method described above, and its specific implementation process and technical effects are the same as those of the first device-side method embodiment. For details, please refer to the detailed description in the terminal-side method embodiment, and no further description will be given here.

[0120] 22 is a second structural schematic diagram of a communication device according to an embodiment of the present application. As shown in FIG. 22, the communication device according to this embodiment includes: a receiving module 2201 for receiving a first message sent by a terminal to request establishing a connection with a network side device using a request slice; and a transmitting module 2202 for transmitting, to the terminal, a second message carrying information for indicating whether the terminal supports use of the requested slice in the target tracking area TA.

[0121] Optionally, the second message is The target tracking area (TA) includes at least one of information of at least one first slice and first indication information, wherein the first indication information is used to indicate that the at least one first slice is unavailable within the current TA, where the first slice is a slice in the request slice, and the target tracking area (TA) includes the current TA; or The second message is The target tracking area TA includes at least one of information on at least one first slice, information on one or more first TAs corresponding to each first slice in the at least one first slice, information on at least one second slice, information on one or more second TAs corresponding to each second slice in the at least one second slice, and second indication information, wherein the first TA is a TA that does not support use of the first slice, and the second TA is a TA that supports use of the second slice, and the second indication information is used to indicate that the first slice is not available within the first TA, where the first slice or the second slice is a slice in the requested slice, and the target tracking area TA includes the first TA or the second TA, or The second message is The information includes at least one of information on at least one third slice, information on a third TA, and third instruction information, where the third instruction information is used to indicate whether the third TA is a TA that supports the use of the third slice or a TA that does not support the use of the third slice, the target TA includes the third TA, and the third slice is a slice in the requested slice.

[0122] Optionally, the second message includes a Reject Network Slice Selection Assistance Information NSSAI information element IE or a first IE, wherein the Reject NSSAI IE or the first IE includes a Reject NSSAI domain corresponding to each first slice in the at least one first slice, and the Reject NSSAI domain corresponding to each first slice includes at least one of information of the first slice and first indication information; and / or The second message includes an extended Rejected NSSAI IE, the extended Rejected NSSAI IE includes a partial extended Rejected NSSAI List domain, the partial extended Rejected NSSAI List domain includes a Rejected NSSAI domain corresponding to each first slice in at least one first slice, and the Rejected NSSAI domain corresponding to each first slice includes at least one of information of the first slice and first indication information.

[0123] Optionally, the second message includes a Reject Network Slice Selection Assistance Information (NSSAI) information element (IE) or a first IE, wherein the Reject NSSAI IE or the first IE includes a Reject NSSAI domain corresponding to each first slice in the at least one first slice, and the Reject NSSAI domain corresponding to each first slice includes at least one of information of the first slice, second indication information, and information of the first TA; and / or The second message includes an extended Rejected NSSAI IE, the extended Rejected NSSAI IE includes a partial extended Rejected NSSAI List domain, the partial extended Rejected NSSAI List domain includes a Rejected NSSAI domain corresponding to each first slice in at least one first slice, and the Rejected NSSAI domain corresponding to each first slice includes at least one of information of the first slice, second indication information, and information of the first TA.

[0124] Optionally, the second message includes an NSSAI Service Area List IE, wherein the NSSAI Service Area List IE includes at least one NSSAI Service Area List domain, each NSSAI Service Area List domain includes an NSSAI field of a third slice, an NSSAI Service Area List field, and a target timer field, and the NSSAI Service Area List field includes at least one of third indication information and information of a third TA.

[0125] Optionally, the second message includes an extended Authorization NSSAI IE, in which an Authorized NSSAI domain corresponding to each at least one second slice is included, and the Authorized NSSAI domain corresponding to each second slice includes at least one of the length of the Authorized NSSAI domain, the NSSAI field of the second slice, and information of the second TA.

[0126] Optionally, the first TA includes a TA that does not support use of the first slice within the preset time range.

[0127] Optionally, the second message further includes information of a first timer, which is used to indicate that the terminal can use the first slice in the first TA after the first timer expires.

[0128] Optionally, the receiving module 2201 is further used for receiving a third message sent by the terminal, the third message being used for indicating that the terminal has received information for indicating whether it supports the use of the requested slice within the target tracking area TA.

[0129] The first message is The information includes at least one of information on the requested slice and terminal capability indication information, where the terminal capability indication information is used to indicate whether the terminal supports a first capability, and the first capability is an ability to receive and use information to indicate whether the terminal supports use of the requested slice in the target TA.

[0130] The device of this embodiment can be used to implement the method of any one of the embodiments of the network device-side method described above, and its specific implementation process and technical effects are the same as those of the first device-side method embodiment. For specific details, please refer to the detailed description in the network device-side method embodiment, and no further description will be given here.

[0131] The communication device in the embodiments of the present application may be an electronic device, for example, an electronic device having an operating system, or a component of an electronic device, for example, an integrated circuit or a chip. The electronic device may be a terminal or other device other than a terminal. Exemplarily, the terminal may include, but is not limited to, the types of terminals 11 listed above. The other device may be a server, a network-attached storage (NAS), etc., and the embodiments of the present application are not specifically limited thereto.

[0132] Optionally, as shown in Figure 23, an embodiment of the present application further provides a communication device 2300, including a processor 2301 and a memory 2302, wherein the memory 2302 stores a program or instruction that can be executed on the processor 2301. For example, if the communication device 2300 is a terminal, when the program or instruction is executed by the processor 2301, it can realize each step of the above-mentioned communication method embodiment and achieve the same technical effect. If the communication device 2300 is a network-side device, when the program or instruction is executed by the processor 2301, it can realize each step of the above-mentioned communication method embodiment and achieve the same technical effect. In order to avoid repetition, no further description will be given here.

[0133] An embodiment of the present application further provides a terminal including a processor and a communication interface, wherein the communication interface is used to send a first message to a network side device to request the network side device to establish a connection with the network side device using the requested slice, and to receive a second message sent by the network side device carrying information indicating whether to support the use of the requested slice in the target tracking area (TA). This terminal embodiment corresponds to the above terminal-side method embodiment, and the implementation processes and embodiments of the above method embodiments may all be applied to this terminal embodiment, and similar technical effects can be achieved. Specifically, Figure 24 is a schematic diagram of a hardware structure for realizing a terminal of the embodiment of the present application.

[0134] The terminal 1000 includes at least some components such as, but not limited to, a radio frequency unit 1001, a network module 1002, an audio output unit 1003, an input unit 1004, a sensor 1005, a display unit 1006, a user input unit 1007, an interface unit 1008, a memory 1009, and a processor 1010.

[0135] As will be understood by those skilled in the art, the terminal 1000 may further include a power source (e.g., a battery) for powering each component, and the power source may be logically connected to the processor 1010 by a power management system, thereby enabling the power management system to realize functions such as charge / discharge management and power consumption management. The terminal structure shown in Figure 24 does not constitute a limitation on the terminal, and the terminal may include more or fewer components than those shown, or a combination of some components, or a different arrangement of components, which will not be further described here.

[0136] It should be understood that in the embodiment of the present application, the input unit 1004 may include a graphics processing unit (GPU) 10041 and a microphone 10042, and the graphics processor 10041 processes image data of still or video images captured by an image capture device (e.g., a camera) in a video capture mode or an image capture mode. The display unit 1006 may include a display panel 10061, which may be configured in the form of a liquid crystal display, an organic light-emitting diode, or the like. The user input unit 1007 includes at least one of a touch panel 10071 and other input devices 10072. The touch panel 10071 is also called a touch screen. The touch panel 10071 may include two parts: a touch detection device and a touch controller. The other input devices 10072 may include, but are not limited to, a physical keyboard, function keys (e.g., volume control buttons, switch buttons, etc.), a trackball, a mouse, and a control lever, which will not be further described herein.

[0137] In the embodiment of the present application, the radio frequency unit 1001 can receive downlink data from the network side device and then transmit the data to the processor 1010 for processing, and can also transmit uplink data to the network side device. Generally, the radio frequency unit 1001 includes, but is not limited to, an antenna, at least one amplifier, a transceiver, a coupler, a low-noise amplifier, a duplexer, etc.

[0138] The memory 1009 may be used to store software programs or instructions and various data. The memory 1009 may include a first storage area that primarily stores programs or instructions and a second storage area that stores data. Here, the first storage area may store an operating system, an application program or instructions required for at least one function (e.g., audio playback function, image playback function, etc.), etc. The memory 1009 may include volatile memory or nonvolatile memory, or may include both volatile and nonvolatile memory. It may include high-speed random access memory and may include nonvolatile memory, where the nonvolatile memory may be read-only memory (ROM), programmable read-only memory (PROM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), or flash memory. The volatile memory may be random access memory (RAM), static random access memory (SRAM), dynamic random access memory (DRAM), synchronous dynamic random access memory (SDRAM), double data rate synchronous dynamic random access memory (DDRSDRAM), enhanced synchronous dynamic random access memory (ESDRAM), synchronous link dynamic random access memory (SLDRAM), and direct memory bus random access memory (DRRAM). Memory 1009 in embodiments of the present application includes, but is not limited to, these and any other suitable types of memory.For example, it may be at least one magnetic disk memory device, flash memory device, or other non-volatile solid-state memory device.

[0139] The processor 1010 may include one or more processing units, and optionally, the processor 1010 may integrate an application processor and a modem processor, where the application processor mainly processes operations related to an operating system, a user interface, and application programs or instructions, and the modem processor mainly processes wireless communication signals, such as a baseband processor. As can be appreciated, the modem processor does not have to be integrated into the processor 1010.

[0140] Wherein, the radio frequency unit 1001 sends a first message to a network side device to request the network side device to establish a connection with the network side device using a request slice; and receiving a second message transmitted by the network side device, the second message carrying information for indicating whether or not the use of the requested slice within the target tracking area TA is supported.

[0141] Optionally, the second message is The target tracking area (TA) includes at least one of information of at least one first slice and first indication information, wherein the first indication information is used to indicate that the at least one first slice is unavailable within the current TA, where the first slice is a slice in the request slice, and the target tracking area (TA) includes the current TA; or The second message is The target tracking area TA includes at least one of information on at least one first slice, information on one or more first TAs corresponding to each first slice in the at least one first slice, information on at least one second slice, information on one or more second TAs corresponding to each second slice in the at least one second slice, and second indication information, wherein the first TA is a TA that does not support use of the first slice, and the second TA is a TA that supports use of the second slice, and the second indication information is used to indicate that the first slice is not available in the first TA, where the first slice or the second slice is a slice in the requested slice, and the target tracking area TA includes the first TA or the second TA, or The second message is The information includes at least one of information on at least one third slice, information on a third TA, and third instruction information, where the third instruction information is used to indicate whether the third TA is a TA that supports the use of the third slice or a TA that does not support the use of the third slice, the target TA includes the third TA, and the third slice is a slice in the requested slice.

[0142] Optionally, the second message includes a Reject Network Slice Selection Assistance Information NSSAI information element IE or a first IE, wherein the Reject NSSAI IE or the first IE includes a Reject NSSAI domain corresponding to each first slice in the at least one first slice, and the Reject NSSAI domain corresponding to each first slice includes at least one of information of the first slice and first indication information; and / or The second message includes an extended Rejected NSSAI IE, the extended Rejected NSSAI IE includes a partial extended Rejected NSSAI List domain, the partial extended Rejected NSSAI List domain includes a Rejected NSSAI domain corresponding to each first slice in at least one first slice, and the Rejected NSSAI domain corresponding to each first slice includes at least one of information of the first slice and first indication information.

[0143] Optionally, the second message includes a Reject Network Slice Selection Assistance Information (NSSAI) information element (IE) or a first IE, wherein the Reject NSSAI IE or the first IE includes a Reject NSSAI domain corresponding to each first slice in the at least one first slice, and the Reject NSSAI domain corresponding to each first slice includes at least one of information of the first slice, second indication information, and information of the first TA; and / or The second message includes an extended Rejected NSSAI IE, the extended Rejected NSSAI IE includes a partial extended Rejected NSSAI List domain, the partial extended Rejected NSSAI List domain includes a Rejected NSSAI domain corresponding to each first slice in at least one first slice, and the Rejected NSSAI domain corresponding to each first slice includes at least one of information of the first slice, second indication information, and information of the first TA.

[0144] Optionally, the second message includes an NSSAI Service Area List IE, wherein the NSSAI Service Area List IE includes at least one NSSAI Service Area List domain, each NSSAI Service Area List domain includes an NSSAI field of a third slice, an NSSAI Service Area List field, and a target timer field, and the NSSAI Service Area List field includes at least one of third indication information and information of a third TA.

[0145] Optionally, the second message includes an extended Authorization NSSAI IE, in which an Authorized NSSAI domain corresponding to each at least one second slice is included, and the Authorized NSSAI domain corresponding to each second slice includes at least one of the length of the Authorized NSSAI domain, the NSSAI field of the second slice, and information of the second TA.

[0146] Optionally, the first TA includes a TA that does not support use of the first slice within the preset time range.

[0147] Optionally, the second message further includes information of a first timer, which is used to indicate that the terminal can use the first slice in the first TA after the first timer expires.

[0148] Optionally, the radio frequency unit 1001 is further used to send a third message to the network side equipment, and the third message is used to indicate that the terminal has received information for indicating whether it supports the use of the requested slice within the target tracking area TA.

[0149] Optionally, the processor 1010 further For each first TA or current TA, the terminal adds information of the first slice that the first TA or current TA does not support to use to a rejected slice list corresponding to the first TA or current TA; For each second TA, the terminal adds information of a second slice that the second TA supports to use to an allowed slice list corresponding to the second TA; Storing information of a first slice in each access type and information of a first TA that does not support the use of the first slice; storing information of a second slice for each access type and information of a second TA supporting the use of the second slice; and starting a second timer, which is used to indicate that the terminal can use the first slice in the first TA or the current TA after the second timer expires.

[0150] Optionally, the processor 1010 further determines, for any one first slice of the at least one first slice, if the first slice is included in a rejected slice list corresponding to a sixth TA, that the sixth TA is any one TA of the one or more first TAs or the current TA; After the device shuts down and restarts, The terminal moves away from the first TA or the current TA; and the terminal is located within a second TA; After the universal subscriber identity module USIM of the terminal is removed, After the subscription data with the network identifier of the current network in which the terminal is located is updated, after a first timer configured by the network side device expires; and after a second timer that is started after the terminal receives the second message expires, the first slice can be used if the terminal satisfies at least one target condition; The first timer or the second timer is used to indicate that after the timer expires, the terminal can use the first slice in the first TA or the current TA.

[0151] Optionally, the processor 1010 further comprises, if at least one target condition is met: removing the first slice from a rejected slice list corresponding to the sixth TA; updating the first slice to a slice available in the sixth TA; and transmitting a fourth message to the network side device, wherein the fourth message is The terminal capability indication information includes at least one of first target slice information to be used and terminal capability indication information, where the terminal capability indication information is used to indicate whether the terminal supports the first capability, and the first capability is an ability to receive and use information to indicate whether the terminal supports the use of the requested slice within the target TA.

[0152] Optionally, the radio frequency unit 1001 is further used for receiving slice information of the first target network configuration sent by the network side device; If the slice information includes second target slice information in the rejected slice list corresponding to the fourth TA, the second target slice information is deleted from the rejected slice list, and the second timer associated with the second target slice information is stopped, and the fourth TA is a TA corresponding to the first target network.

[0153] Optionally, the radio frequency unit 1001 is further used for receiving slice information permitted by the second target network sent by the network side device; If the allowed slice information includes third target slice information in the rejected slice list corresponding to the fifth TA, the third target slice information is deleted from the rejected slice list, and the second timer associated with the third target slice information is stopped, and the fifth TA is a TA corresponding to the second target network.

[0154] Optionally, the first message is: The information includes at least one of information on the requested slice and terminal capability indication information, where the terminal capability indication information is used to indicate whether the terminal supports a first capability, and the first capability is an ability to receive and use information to indicate whether the terminal supports use of the requested slice in the target TA.

[0155] An embodiment of the present application further provides a network side device, including a processor and a communication interface, where the communication interface is used to receive a first message sent by a terminal to request establishing a connection with the network side device using the requested slice, and to send a second message carrying information to instruct the terminal whether to support using the requested slice in a target tracking area (TA). This embodiment of the network side device corresponds to the embodiment of the network side device method described above, and the implementation processes and realization manners of the embodiment of the method can all be applied to this embodiment of the network side device, and the same technical effects can be achieved.

[0156] Specifically, an embodiment of the present application further provides a network side device. As shown in Fig. 25, the network side device 1100 includes a processor 1101, a network interface 1102, and a memory 1103. Here, the network interface 1102 is, for example, a common public radio interface (CPRI).

[0157] Specifically, the network side device 1100 of the embodiment of the present application further includes instructions or programs stored in memory 1103 and capable of running on the processor 1101, and the processor 1101 can call the instructions or programs in the memory 1103 to execute the methods performed by each module shown in FIG. 22 and achieve the same technical effects, which will not be described further here to avoid repetition.

[0158] The embodiments of the present application further provide a readable storage medium, on which a program or instruction is stored, and when the program or instruction is executed by a processor, the respective processes of the above communication method embodiments can be realized and similar technical effects can be achieved. In order to avoid repetition of the description, no further description will be given here.

[0159] Here, the processor is the processor in the terminal described in the above embodiment. The readable storage medium includes a computer readable storage medium, such as a computer read only memory (ROM), a random access memory (RAM), a magnetic disk, or an optical disk.

[0160] The embodiments of the present application further provide a chip, which includes a processor and a communication interface, and the communication interface is coupled to the processor, and the processor runs a program or instruction to implement each process of the above-mentioned communication method embodiments, and can achieve the same technical effects. In order to avoid repetition, no further description will be given here.

[0161] It should be understood that the chips referred to in the embodiments of this application may be referred to as system level chips, system chips, chip systems, or system-on-chips.

[0162] The embodiments of the present application further provide a computer program / program product, which is stored in a storage medium and can be executed by at least one processor to realize each process of the above communication method embodiments and achieve the same technical effects. In order to avoid repetition, no further description will be given here.

[0163] An embodiment of the present application further provides a communication system including a terminal and a network side device, wherein the terminal may be used to perform steps of the communication method as described above, and the network side device may be used to perform steps of the communication method as described above.

[0164] It should be noted that, in this specification, the terms "comprises," "includes," or any other variations thereof are intended to cover the non-exclusive "comprises," whereby a process, method, article, or apparatus comprising a set of elements not only includes those elements, but also other elements not expressly listed or inherent in such process, method, article, or apparatus. Absent further limitations, an element defined by the phrase "comprises one of" does not preclude the presence of other identical elements in the process, method, article, or apparatus comprising that element. It should be noted that the scope of the methods and apparatuses in the embodiments of this application is not limited to performing functions in the order shown or discussed, but may include performing functions in an essentially simultaneous manner or in the reverse order based on the functions involved; for example, a described method may be performed in a different order than described, and various steps may be added, omitted, or combined. Furthermore, features described with reference to some examples may be combined in other examples.

[0165] From the above description of the embodiments, it will be apparent to those skilled in the art that the methods of the above embodiments can be realized in the form of software and a required general-purpose hardware platform. Of course, they can also be realized in hardware, but in many cases the former is a more preferred embodiment. From this understanding, the substantial or prior art contributions of the technical solution of the present application may be embodied in the form of a computer software product, which may be stored in a storage medium (e.g., ROM / RAM, magnetic disk, optical disk) and include some instructions for causing a terminal (which may be a mobile phone, computer, server, air conditioner, network device, etc.) to execute the methods of the embodiments of the present application.

[0166] Although the above describes the embodiments of the present application in conjunction with the drawings, the present application is not limited to the above specific embodiments. The above specific embodiments are merely illustrative and not limiting. Those skilled in the art can implement many forms under the guidance of the present application without departing from the spirit and scope of protection of the claims, and all forms fall within the scope of protection of the present application.

Claims

1. 1. A communication method comprising: The terminal transmits a first message to a network side device to request that a connection be established with the network side device using a request slice; The communication method includes the terminal receiving a second message transmitted by the network side equipment, the second message carrying information for indicating whether or not the terminal supports use of the requested slice within a target tracking area (TA).

2. The second message is The request information includes at least one of information of at least one first slice and first indication information, the first indication information being used to indicate that the at least one first slice is unavailable within a current TA, where the first slice is a slice in the requested slice, and the target tracking area TA includes the current TA; or The second message is The target tracking area (TA) includes at least one of information on at least one first slice, information on one or more first TAs corresponding to each first slice in the at least one first slice, information on at least one second slice, information on one or more second TAs corresponding to each second slice in the at least one second slice, and second indication information, wherein the first TA is a TA that does not support use of the first slice, and the second TA is a TA that supports use of the second slice, and the second indication information is used to indicate that the first slice is not available in the first TA, wherein the first slice or the second slice is a slice in the requested slice, and the target tracking area (TA) includes the first TA or the second TA, or The second message is 2. The communication method of claim 1, wherein the communication information includes at least one of information on at least one third slice, information on a third TA, and third instruction information, the third instruction information being used to indicate whether the third TA is a TA that supports use of the third slice or a TA that does not support use of the third slice, the target TA including the third TA, and the third slice being a slice in the requested slice.

3. The second message includes a Reject Network Slice Selection Assistance Information (NSSAI) information element (IE) or a first IE, wherein the Reject NSSAI IE or the first IE includes a Reject NSSAI domain corresponding to each first slice in the at least one first slice, and the Reject NSSAI domain corresponding to each first slice includes at least one of information about the first slice and the first indication information; and / or 3. The communication method of claim 2, wherein the second message includes an extended rejection NSSAI IE, the extended rejection NSSAI IE includes a partial extended rejection NSSAI list domain, the partial extended rejection NSSAI list domain includes a rejection NSSAI domain corresponding to each first slice in the at least one first slice, and the rejection NSSAI domain corresponding to each first slice includes at least one of information of the first slice and the first indication information.

4. The second message includes a Reject Network Slice Selection Assistance Information (NSSAI) information element (IE) or a first IE, wherein the Reject NSSAI IE or the first IE includes a Reject NSSAI domain corresponding to each first slice in the at least one first slice, and the Reject NSSAI domain corresponding to each first slice includes at least one of information of the first slice, the second indication information, and information of the first TA; and / or 3. The communication method of claim 2, wherein the second message includes an extended rejection NSSAI IE, the extended rejection NSSAI IE includes a partial extended rejection NSSAI list domain, the partial extended rejection NSSAI list domain includes a rejection NSSAI domain corresponding to each first slice in the at least one first slice, and the rejection NSSAI domain corresponding to each first slice includes at least one of information of the first slice, the second indication information, and information of the first TA.

5. 3. The communication method of claim 2, wherein the second message includes an NSSAI Service Area List IE, and the NSSAI Service Area List IE includes at least one NSSAI Service Area List domain, each of the NSSAI Service Area List domains including an NSSAI field of the third slice, an NSSAI Service Area List field, and a target timer field, and the NSSAI Service Area List field includes at least one of third indication information and information of the third TA.

6. 3. The communication method according to claim 2, wherein the second message includes an extended authorization NSSAI IE, and the extended authorization NSSAI IE includes an authorization NSSAI domain corresponding to each of the at least one second slice, and the authorization NSSAI domain corresponding to each of the second slices includes at least one of a length of the authorization NSSAI domain, an NSSAI field of the second slice, and information of the second TA.

7. The communication method according to claim 2 , wherein the first TA includes a TA that does not support use of the first slice within a preset time range.

8. 8. The communication method of claim 7, wherein the second message further includes information of a first timer, the first timer being used to indicate that the terminal can use the first slice in the first TA after the first timer expires.

9. After the terminal receives the second message sent by the network side device, 7. The communication method according to claim 1, further comprising: the terminal transmitting a third message to the network side device, the third message being used to indicate that the terminal has received information for indicating whether or not it supports use of the requested slice within a target tracking area (TA).

10. After receiving the second message sent by the network side device, the terminal: For each of the first TA or current TA, the terminal adds information of a first slice that the first TA or current TA does not support to a rejected slice list corresponding to the first TA or current TA; For each second TA, the terminal adds information of a second slice that the second TA supports for use to an allowed slice list corresponding to the second TA; The terminal stores information of the first slice for each access type and information of a first TA that does not support use of the first slice; The terminal stores information of the second slice in each access type and information of a second TA that supports use of the second slice; and starting a second timer, wherein the second timer is used to indicate that the terminal can use the first slice in the first TA or a current TA after the second timer expires.

11. For any one first slice of the at least one first slice, if the first slice is included in a rejected slice list corresponding to a sixth TA, the sixth TA is any one TA of the one or more first TAs or a current TA, and the terminal: After the device is shut down and restarted, The terminal has moved away from the first TA or the current TA; and the terminal is located within the second TA; after the Universal Subscriber Identity Module USIM of said terminal has been removed; After the subscription data with the network identifier of the current network in which the terminal is located is updated, after a first timer configured by the network side device expires; and after a second timer that is started after the terminal receives the second message expires, the terminal may use the first slice; and 7. The communication method according to claim 2, wherein the first timer or the second timer is used to indicate that the terminal can use the first slice in the first TA or a current TA after the timer expires.

12. If the terminal satisfies the at least one target condition, the method includes: The terminal The terminal deletes the first slice from a rejected slice list corresponding to the sixth TA; an operation of the terminal updating the first slice to a slice available in the sixth TA; and the terminal transmitting a fourth message to the network side device, wherein the fourth message comprises: The communication method of claim 11, comprising at least one of first target slice information to be used and terminal capability indication information, wherein the terminal capability indication information is used to indicate whether the terminal supports a first capability, and the first capability is a capability to receive and use information to indicate whether the terminal supports use of the requested slice within the target TA.

13. The method comprises: The terminal receives slice information of a first target network configuration transmitted by the network side device; A communication method described in any one of claims 2 to 6, further comprising: if the slice information includes second target slice information in a rejected slice list corresponding to a fourth TA, the terminal deletes the second target slice information from the rejected slice list and stops timing of a second timer associated with the second target slice information, and the fourth TA is a TA corresponding to the first target network.

14. The method comprises: The terminal receives slice information permitted by the second target network transmitted by the network side device; A communication method described in any one of claims 2 to 6, further comprising: if the allowed slice information includes third target slice information in a rejected slice list corresponding to a fifth TA, the terminal deletes the third target slice information from the rejected slice list and stops timing of a second timer associated with the third target slice information, and the fifth TA is a TA corresponding to the second target network.

15. The first message is 7. The communication method according to claim 2, further comprising at least one of requested slice information and terminal capability indication information, wherein the terminal capability indication information is used to indicate whether the terminal supports a first capability, and the first capability is a capability to receive and use information to indicate whether the terminal supports use of the requested slice in a target TA.

16. 1. A communication method comprising: The network side device receives a first message sent by the terminal to request establishing a connection with the network side device using the request slice; The communication method includes the network side device sending, to the terminal, a second message carrying information for indicating whether or not to support use of the requested slice within a target tracking area (TA).

17. The second message is The request information includes at least one of information of at least one first slice and first indication information, the first indication information being used to indicate that the at least one first slice is unavailable within a current TA, where the first slice is a slice in the requested slice, and the target tracking area TA includes the current TA; or The second message is The target tracking area (TA) includes at least one of information on at least one first slice, information on one or more first TAs corresponding to each first slice in the at least one first slice, information on at least one second slice, information on one or more second TAs corresponding to each second slice in the at least one second slice, and second indication information, wherein the first TA is a TA that does not support use of the first slice, and the second TA is a TA that supports use of the second slice, and the second indication information is used to indicate that the first slice is not available in the first TA, wherein the first slice or the second slice is a slice in the requested slice, and the target tracking area (TA) includes the first TA or the second TA, or The second message is 17. The communication method of claim 16, comprising at least one of information on at least one third slice, information on a third TA, and third instruction information, wherein the third instruction information is used to indicate whether the third TA is a TA that supports use of the third slice or a TA that does not support use of the third slice, the target TA includes the third TA, and the third slice is a slice in the requested slice.

18. The second message includes a Reject Network Slice Selection Assistance Information (NSSAI) information element (IE) or a first IE, wherein the Reject NSSAI IE or the first IE includes a Reject NSSAI domain corresponding to each first slice in the at least one first slice, and the Reject NSSAI domain corresponding to each first slice includes at least one of information about the first slice and the first indication information; and / or 18. The communication method of claim 17, wherein the second message includes an extended rejection NSSAI IE, the extended rejection NSSAI IE includes a partial extended rejection NSSAI list domain, the partial extended rejection NSSAI list domain includes a rejection NSSAI domain corresponding to each first slice in the at least one first slice, and the rejection NSSAI domain corresponding to each first slice includes at least one of information of the first slice and the first indication information.

19. The second message includes a Reject Network Slice Selection Assistance Information (NSSAI) information element (IE) or a first IE, wherein the Reject NSSAI IE or the first IE includes a Reject NSSAI domain corresponding to each first slice in the at least one first slice, and the Reject NSSAI domain corresponding to each first slice includes at least one of information of the first slice, the second indication information, and information of the first TA; and / or 18. The communication method of claim 17, wherein the second message includes an extended rejection NSSAI IE, the extended rejection NSSAI IE includes a partial extended rejection NSSAI list domain, the partial extended rejection NSSAI list domain includes a rejection NSSAI domain corresponding to each first slice in the at least one first slice, and the rejection NSSAI domain corresponding to each first slice includes at least one of information of the first slice, the second indication information, and information of the first TA.

20. 18. The communication method of claim 17, wherein the second message includes an NSSAI Service Area List IE, and the NSSAI Service Area List IE includes at least one NSSAI Service Area List domain, each of the NSSAI Service Area List domains including an NSSAI field of the third slice, an NSSAI Service Area List field, and a target timer field, and the NSSAI Service Area List field includes at least one of third indication information and information of the third TA.

21. 18. The communication method of claim 17, wherein the second message includes an extended authorization NSSAI IE, wherein the extended authorization NSSAI IE includes an authorized NSSAI domain corresponding to each of the at least one second slice, and the authorized NSSAI domain corresponding to each of the second slices includes at least one of a length of the authorized NSSAI domain, an NSSAI field of the second slice, and information of the second TA.

22. 22. The communication method according to claim 17, wherein the first TA includes a TA that does not support use of the first slice within a preset time range.

23. 23. The communication method of claim 22, wherein the second message further includes information of a first timer, the first timer being used to indicate that the terminal can use the first slice in the first TA after the first timer expires.

24. 22. The communication method according to claim 16, wherein the network side device receives a third message transmitted by the terminal, the third message being used to indicate that the terminal has received information for indicating whether it supports use of the requested slice within a target tracking area (TA).

25. The first message is 22. The communication method according to claim 17, further comprising at least one of requested slice information and terminal capability indication information, wherein the terminal capability indication information is used to indicate whether the terminal supports a first capability, and the first capability is a capability to receive and use information to indicate whether the terminal supports use of the requested slice in a target TA.

26. A communication device, a sending module for sending a first message to a network side device to request the network side device to establish a connection with the network side device using a request slice; A communication device comprising: a receiving module for receiving a second message transmitted by the network side equipment, the second message carrying information for indicating whether or not to support use of the requested slice within a target tracking area (TA).

27. A communication device, a receiving module for receiving a first message sent by a terminal to request establishing a connection with a network side device using a request slice; a transmitting module for transmitting a second message carrying information to indicate to a terminal whether or not the terminal supports use of the requested slice within a target tracking area (TA).

28. A terminal including a processor and a memory, the memory storing a program or instructions operable on the processor, the program or instructions implementing the steps of the communication method according to any one of claims 1 to 15 when executed by the processor.

29. A network side device including a processor and a memory, the memory storing a program or instructions operable on the processor, the program or instructions implementing the steps of the communication method according to any one of claims 16 to 25 when executed by the processor.

30. A readable storage medium having stored thereon a program or instructions, which, when executed by a processor, implements the communication method of any one of claims 1 to 15 or the steps of the communication method of any one of claims 16 to 25.

Images