Communication methods, terminals, and network-side equipment

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, titled "Communication Method, Terminal, and Network - side Device", filed on August 19, 2022, and the entire content of the same application is incorporated herein by reference.

[0002] This application belongs to the field of communication technology, specifically relating to communication methods, terminals, and network - side devices.

Background Art

[0003] In the current standard, when a slice requested by a terminal is rejected, actually, this slice may only be rejected in a certain Tracking Area (TA) within the Registration Area (RA). However, the network - side notifies the terminal that this slice cannot be used throughout the RA, so that the terminal cannot use this slice throughout the RA, and can only wait until the relevant timer expires, the terminal moves away from this RA, or the terminal shuts down, etc., after which it can use this slice again, resulting in relatively low usage efficiency of the slice. Tracking

Summary of the Invention

Problems to be Solved by the Invention

[0004] Embodiments of this application provide a communication method, a terminal, and a network - side device that can solve the communication problems between the terminal and the network - side device.

Means for Solving the Problems

[0005] According to a first aspect, a communication method for a terminal is provided. This method includes: The terminal transmits a first message to the network - side device to request establishing a connection with the network - side device using the requested slice. The terminal includes receiving a second message transmitted by a network-side device, which carries information to indicate whether or not it supports the use of a requested slice within the target tracking area (TA).

[0006] According to a second aspect, a communication method used for network-side equipment is provided, and this method is: The network-side device receives a first message sent by the terminal requesting to establish a connection with the network-side device using the request slice. The network-side device includes sending a second message to the terminal that carries information to instruct whether or not it supports the use of the requested slice within the target tracking area TA.

[0007] According to a third aspect, a communication device is provided, and this communication device is A transmission module for sending a first message to a network-side device requesting it to establish a connection with the network-side device using a request slice, It includes a receiving module for receiving a second message transmitted by network-side equipment, which carries information to indicate whether or not to support the use of a requested slice within the target tracking area (TA).

[0008] According to the fourth aspect, a communication device is provided, and this communication device is A receiving module for receiving a first message sent by a terminal requesting to establish a connection with a network-side device using a request slice, The terminal includes a transmission module for sending a second message that carries information to instruct whether or not to support the use of requested slices within the target tracking area (TA).

[0009] According to the fifth aspect, a terminal is provided which includes a processor and memory, the memory storing a program or instruction that can be executed on the processor, and when the program or instruction is executed by the processor, the method of the first aspect is realized.

[0010] According to a sixth aspect, a terminal is provided including a processor and a communication interface, wherein the communication interface is used to send a first message requesting a network-side device to establish a connection with the network-side device using a request slice, and to receive a second message sent by the network-side device, which carries information indicating whether or not to support the use of a request slice within a target tracking area TA.

[0011] According to the seventh aspect, a network-side device is provided, which includes a processor and memory, the memory storing a program or instruction that can be run on the processor, and when the program or instruction is executed by the processor, the method according to the second aspect is realized.

[0012] According to the eighth aspect, a network-side device is provided, comprising a processor and a communication interface, wherein the communication interface is used to receive a first message transmitted by a terminal requesting to establish a connection with the network-side device using a request slice, and to transmit a second message to the terminal carrying information to indicate whether or not to support the use of the request slice within a target tracking area (TA).

[0013] According to the ninth aspect, a communication system including a terminal and network-side equipment is provided, wherein the terminal is used to perform the communication method described in the first aspect, and the network-side equipment is used to perform the communication method described in the second aspect.

[0014] According to the tenth aspect, a readable storage medium is provided, on which a program or instruction is stored, and when the program or instruction is executed by a processor, the method according to the first aspect is realized, or the method according to the second aspect is realized.

[0015] According to the eleventh aspect, a chip is provided, the chip comprising a processor and a communication interface, the communication interface being coupled with the processor, the processor running a program or instructions, and being used to implement the method according to the first aspect or the method according to the second aspect.

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

[0017] In the embodiments of this application, a second message is sent from the network-side device to the terminal indicating whether it supports the use of requested slices within the target tracking area TA. After the terminal receives the second message, it can select and use slices based on the granularity of the TA, thereby effectively improving the efficiency of slice usage and enabling the terminal to use slices more efficiently. [Brief explanation of the drawing]

[0018] [Figure 1a] This is a structural diagram of a wireless communication system to which the embodiments of this application can be applied. [Figure 1b] This is a schematic diagram of a communication method according to an embodiment of this application. [Figure 2] This is one of the flowcharts for the communication method according to the embodiment of this application. [Figure 3]This is one of the schematic diagrams of the information elements of the rejection network slice selection assistance information of the communication method according to the embodiment of the present application. [Figure 4] This is one of the schematic diagrams of the rejection network slice selection assistance information domain of the communication method according to the embodiment of the present application. [Figure 5] This is one of the schematic diagrams of the information elements of the extended rejection network slice selection assistance information of the communication method according to the embodiment of the present application. [Figure 6a] This is one of the schematic diagrams of the partial extended rejection network slice selection assistance information list domain of the communication method according to the embodiment of the present application. [Figure 6b] This is the second of the schematic diagrams of the partial extended rejection network slice selection assistance information list domain of the communication method according to the embodiment of the present application. [Figure 7] This is the second of the schematic diagrams of the rejection network slice selection assistance information domain of the communication method according to the embodiment of the present application. [Figure 8] This is the second of the schematic diagrams of the information elements of the rejection network slice selection assistance information of the communication method according to the embodiment of the present application. [Figure 9] This is the third of the schematic diagrams of the rejection network slice selection assistance information domain of the communication method according to the embodiment of the present application. This is the second of the schematic diagrams of the information elements of the extended rejection network slice selection assistance information of the communication method according to the embodiment of the present application. [Figure 11a] This is the third of the schematic diagrams of the partial extended rejection network slice selection assistance information list domain of the communication method according to the embodiment of the present application. [Figure 11b] This is the fourth of the schematic diagrams of the partial extended rejection network slice selection assistance information list domain of the communication method according to the embodiment of the present application. [Figure 12] This is the fourth of the schematic diagrams of the rejection network slice selection assistance information domain of the communication method according to the embodiment of the present application. [Figure 13] This is the schematic diagram of the network slice selection assistance information service area list information element of the communication method according to the embodiment of the present application. [Figure 14] This is a schematic diagram of the network slice selection support information service area list domain of the communication method according to an embodiment of this application. [Figure 15a] This is one schematic diagram of the network slice selection support information service area list field of the communication method according to the embodiment of this application. [Figure 15b] This is the second schematic diagram of the network slice selection support information service area list field of the communication method according to the embodiment of this 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 the embodiment of this application. [Figure 15d] This is the fourth schematic diagram of the network slice selection support information service area list field of the communication method according to the embodiment of this application. [Figure 16] This is a schematic diagram of the information elements of the extended permission network slice selection support information for the communication method according to the embodiment of this application. [Figure 17] This is a schematic diagram of the authorized network slice selection support information domain of the communication method according to an embodiment of this application. [Figure 18] A schematic diagram of terminal capability instruction information for a communication method according to an embodiment of this application. [Figure 19] This is the second flowchart of the communication method according to the embodiment of this application. [Figure 20] This is an interaction flowchart of the communication method according to the embodiment of this application. [Figure 21] This is one of the schematic diagrams of the structure of a communication device according to an embodiment of this application. [Figure 22] This is the second schematic diagram of the structure of a communication device according to an embodiment of this application. [Figure 23] This is a schematic diagram of the structure of a communication device according to an embodiment of this application. [Figure 24] This is a schematic diagram of the hardware structure of a terminal according to an embodiment of this application. [Figure 25] This is a schematic diagram of the network-side equipment structure of the embodiment of this application. [Modes for carrying out the invention]

[0019] The following clearly and completely describes the technical concepts in the embodiments of this application, linking them to the drawings of the embodiments. Clearly, the embodiments described are only some, and not all, embodiments of this application. All other embodiments obtained by those skilled in the art based on the embodiments of this application are all within the scope of protection of this application.

[0020] The terms "first," "second," etc., used in the specification and claims of this application are intended to distinguish similar subjects and not to describe a specific order or sequence. It should be understood that these terms are interchangeable where appropriate, so that the embodiments of this application may be carried out in an order other than those illustrated or described herein, and that the subjects distinguished by "first" and "second" are generally of the same kind and do not limit the number of subjects; for example, the first subject may be one or more. Furthermore, "and / or" in the specification and claims indicates at least one of the connected subjects, and the letter " / " generally indicates that the preceding and succeeding related subjects are in an "or" relationship.

[0021] It should be noted that the technologies described in the embodiments of this application are not limited to Long Term Evolution (LTE) / LTE-Advanced (LTE-A) systems, but are also applicable 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 this application are always used interchangeably, and the technologies described may be used for the systems and radio technologies mentioned above, or for other systems and radio technologies. The following description describes a New Radio (NR) system for illustrative purposes, and uses NR terminology in most of the following descriptions, but these technologies are also applicable to applications other than NR system applications, such as sixth-generation (6) radio. th It may be applied to 6G (Generation 6G) communication systems.

[0022] Figure 1a shows a block diagram of an applicable wireless communication system according to an embodiment of this application. The wireless communication system includes a terminal 11 and a network-side device 12. Here, terminal 11 may be a terminal-side device such as a mobile phone, tablet personal computer, laptop computer (or notebook computer), personal digital assistant (PDA), palmtop computer, netbook, ultra-mobile personal computer (UMPC), mobile internet device (MID), augmented reality (AR) / virtual reality (VR) equipment, robot, wearable device, in-vehicle equipment (VUE), pedestrian terminal (PUE), smart home (home appliances with wireless communication capabilities, such as refrigerators, televisions, washing machines, or furniture), game console, personal computer (PC), deposit machine, or self-service machine, and wearable devices include smartwatches, smart bands, smart earphones, smart glasses, smart accessories (smart bracelets, smart rings, smart necklaces, smart anklets, etc.), smart wristbands, smart clothing, etc. It should be noted that the embodiments of this application do not limit the specific type of terminal 11. The network-side equipment 12 may include access network equipment or core network equipment, where access network equipment 12 may also be called wireless access network equipment, radio access network (RAN), wireless access network function, or wireless access network unit.The access network equipment 12 may include base stations, WLAN access points, or WiFi nodes, and base stations may also be called node B, evolving node B (eNB), access point, base transceiver station (BTS), radio base station, radio transceiver, basic service set (BSS), extended service set (ESS), home B node, home evolving B node, transmitting and receiving point (TRP), or any other appropriate term in the field, and are not limited to specific technical terms as long as the same technical effect is achieved. For the purposes of this explanation, only base stations in NR systems are given as examples in the embodiments of this application, but this does not limit the specific types of base stations.The core network equipment includes core network nodes, core network functions, Mobility Management Entity (MME), Access and Mobility Management Function (AMF), Session Management Function (SMF), User Plane Function (UPF), Policy Control Function (PCF), Policy and Charging Rules Function (PCRF), Edge Application Server Discovery Function (EASDF), Unified Data Management (UDM), Unified Data Repository (UDR), Home Subscriber Server (HSS), Centralized network configuration (CNC), Network Repository Function (NRF), Network Exposure Function (NEF), Local NEF (or L-NEF), Binding Support Function (BSF), and Application Function (Application It may include, but is not limited to, at least one of the following: Function (AF), etc. For illustrative purposes, the embodiments of this application only use core network equipment in an NR system as an example, but this does not limit the specific type of core network equipment.

[0023] To make each embodiment of this application easier to understand, some relevant background information is introduced below.

[0024] RA and TA During network deployment, the AMF can establish multiple TAs within a single RA area. When a device begins registration, the AMF assigns a Tracking Area Identity List (TAI list) (for example, up to 16) to the UE, and this TAI list is the device's registration area (RA). Within this RA, the device does not need to perform registration updates, and if the device moves away from this RA area, the UE must proactively initiate mobile registration updates. As can be seen, one of the purposes of the network establishing the concepts of RAs and TAs is to reduce the network signaling load by eliminating the need for the UE to frequently initiate mobile registration updates, and only requiring the UE to proactively initiate mobile registration updates after moving away from the RA.

[0025] Permission and denial of slicing In the registration flow, the terminal first sends a registration request message to the network-side device. The terminal reports the requested slice information to the network, which includes one or more Single Network Slice Selection Assistance Information (S-NSSAI). The network-side device then determines whether to allow service to the requested slice based on the terminal's subscription status and the current network status. If service can be provided to the requested slice, the S-NSSAI for this slice is placed in the allowed NSSAI and returned to the terminal. If service cannot be provided to the requested slice, the S-NSSAI for this slice is placed in the rejected NSSAI and returned to the terminal. Selectively, if the terminal indicates in the terminal capability information (5GMM capability IE) in the registration request message that it supports extended rejected network slice selection assistance information, the network-side device further places information about slices that cannot be served in the extended rejected NSSAI and returns it to the terminal.

[0026] When a rejected NSSAI is returned, the network-side equipment may carry the cause value "The slice is unavailable in the current registration area," meaning this slice is unavailable across the entire RA. For example, as shown in Figure 1b, if a terminal initiates S-NSSAI registration at TA 1 and is rejected at TA 1, and the cause value used by the network side is "The 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. Conventional technology does not support the terminal using the slice in that area. The efficiency of slice utilization is significantly reduced. Thus, the slice is unavailable at all TAs across the entire RA and can only be used in the following situations: The device is turned off, the device moves away from the current registration area, the Universal Integrated Circuit Card (UICC) containing the Universal Subscriber Identity Module (USIM) is removed, the "User Data List" entry with the Standalone Non-Public Network (SNPN) identifier for the current Standalone Non-Public Network (SNPN) is updated, or the rejected S-NSSAI is removed.

[0027] In the following sections, the communication method according to the embodiments of this application will be described in detail with reference to several embodiments and their application scenarios, accompanied by drawings.

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

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

[0030] Specifically, in order to enable communication between a terminal and a network-side device, the terminal sends a first message to the network-side device, which is used to request the establishment of a connection with the network-side device using a request slice. The first message optionally includes information about the request slice, and the request slice includes one or more S-NSSAIs. Furthermore, the network-side device can determine whether it can establish a connection and communication with the terminal using the request slice based on the information about the request 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 equipment, which carries information to indicate whether or not it supports the use of the requested slice within the target tracking area TA.

[0032] Specifically, under current standards, if a slice requested by a terminal is rejected, the network notifies the terminal that this slice cannot be used across the entire RA, resulting in relatively low slice utilization efficiency. To solve the problem of low slice utilization efficiency, in the embodiment of this application, after receiving information on the requested slice transmitted by the terminal, the network-side device sends a second message to the terminal, where the second message carries information indicating whether or not it supports the use of the requested slice within the target tracking area (TA). In other words, by sending the second message, the network-side device notifies the terminal whether or not the requested slice can be used within the tracking area (TA), thereby allowing the terminal to select and use slices based on the granularity of the TA after receiving the second message, enabling the terminal to use slices more efficiently, improving slice utilization efficiency, and solving the problem of not being able to use any slices within any of the TAs in the same RA.

[0033] In the method of the above embodiment, a second piece of information is transmitted to the terminal via network-side equipment, carrying information on whether or not 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 a slice based on the granularity of the TA, effectively improving the efficiency of slice usage, thereby enabling the terminal to use slices more efficiently.

[0034] In one embodiment, the second message is: The system includes at least one of the following: information of at least one first slice and at least one of the first instruction information, the first instruction information being used to indicate that at least one first slice is unavailable within the 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 the following: information of at least one first slice, information of a first TA corresponding to each first slice in at least one first slice, information of at least one second slice, information of a second TA corresponding to each second slice in at least one second slice, and second instruction information, wherein the first TA is a TA that does not support the use of the first slice, the second TA is a TA that supports the use of the second slice, and the second instruction information is used to indicate that the first slice is unavailable within the first TA, where the first slice or the second slice is a slice in the request slice, and the target tracking area TA includes the first TA or the second TA, or The second message is, The target TA includes information on at least one third slice, information on a third TA, and at least one of third instruction information, the third instruction information being 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 the embodiments of this application, the network-side device sends a second message to the terminal indicating whether or not it supports the use of a requested slice within the target tracking area TA, thereby enabling the terminal to select and use a slice based on the granularity of the TA after receiving the second message, thereby improving the efficiency of slice utilization. Selectively, in the embodiments of this application, the first TA, second TA, third TA and target TA may be TAs included in the current registration area or TAs included in other registration areas, selectively, one first slice may correspond to one or more first TAs, one second slice may correspond to one or more second TAs, selectively, one first TA may correspond to one or more first slices, and one second TA may correspond to one or more second slices.

[0036] Selectively, the second message includes at least one of the following: information on at least one first slice and at least one of the first instruction information, the first instruction information being used to indicate that the first slice is unavailable within the current TA, the current TA being the TA where the terminal is located when the terminal sends the first message to the network-side device, i.e., the network-side device, based on the first instruction information in the second message, indicates that the first slice is unavailable within the current TA, and thereafter, after receiving the first instruction information and the information on the first slice in the second message, the terminal can determine that the first slice is unavailable within the current TA, the terminal can select another slice within the current TA and establish connection and communication with the network-side device, and 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 information that the slice is not applicable to the current TA by newly added instruction information (cause value) based on the application status of multiple TAs in the slice's RA, and thereafter, after receiving the instruction information, the terminal can combine it with the information of the TA where it is currently located and determine whether or not the slice is available in the current TA.

[0037] Selectively, the second message includes at least one of the following: information on at least one first slice; information on a first TA corresponding to each first slice in at least one first slice; information on at least one second slice; information on a second TA corresponding to each second slice in at least one second slice; and second instruction information. In other words, the network-side device notifies the terminal of which TAs can use the first slices and which TAs cannot use the second slices based on the first TA information corresponding to the first slices, the second TA information corresponding to the second slices, and the second instruction information in the second message. The terminal can then select and use slices based on the first TA information corresponding to the first slices, the second TA information corresponding to the second slices, and the second instruction information in the second message, as well as the TA information where the terminal is currently located.

[0038] Selectively, the second message includes at least one of the following: 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 the use of a third slice or a TA that does not support the use of a third slice. That is, the network-side device is indicated by the third instruction message in the second message as to which TAs support the use of a third slice and which TAs do not support the use of a third slice. Thereafter, after receiving the third instruction message in the second message, the terminal can determine, based on the third instruction message in the second message, whether it can establish a connection and communication with the network-side device using a third slice at the target TA. Selectively, the target TA may be a TA in the current RA or another RA. In other words, after receiving a request from a terminal, the network-side equipment notifies the terminal of a list of TAs that support and / or deny the use of slices based on slice granularity, based on the application status of multiple TAs in the slice's RA. After receiving this list of TAs that support and / or deny the use of slices based on slice granularity, the terminal can combine this information with the currently located TA information to determine whether or not slices can be used at the current TA.

[0039] In the method of the above embodiment, the network-side device provides instructions to the terminal regarding the application of slices based on TA granularity by carrying instruction 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 a list of TAs that support and / or reject the use of slices based on slice granularity, based on the application status of multiple TAs in the slice's RA. The instruction information (newly added cause value) notifies the terminal that the slice is not applicable to the current TA. Furthermore, after the terminal receives the instruction information and / or the list of TAs that support and / or reject the use of slices based on slice granularity, the terminal can accurately determine whether or not a slice can be used in the current TA by linking it with the TA information where it is currently located. The method of the embodiment of this application provides relatively high flexibility in enabling the terminal to accurately instruct whether or not a requested slice can be used within the tracking area TA in multiple ways.

[0040] In one embodiment, the second message includes a reject network slice selection support information NSSAI information element IE or a first IE, and the reject NSSAI IE or first IE includes reject NSSAI domains corresponding to each first slice in at least one first slice, and each reject NSSAI domain corresponding to a first slice includes at least one of the first slice information and first instruction information, and / or The second message includes an extended reject NSSAI IE, the extended reject NSSAI IE includes a partial extended reject NSSAI list domain, the partial extended reject NSSAI list domain includes reject NSSAI domains corresponding to each first slice in at least one first slice, and each reject NSSAI domain corresponding to a first slice includes at least one of the information of the first slice and the first instruction information.

[0041] Specifically, the network-side device instructs the terminal whether to support the use of the first slice within the first TA by the Reject Network Slice Selection Support Information NSSAI information element IE or the first IE in the second message, where the first IE may be a newly defined information element, and optionally, as shown in Figure 3, the Reject NSSAI IE includes a Reject NSSAI domain corresponding to each first slice in at least one first slice, and as shown in Figure 4, the Reject NSSAI domain corresponding to each first slice includes at least one of the first slice information and the first instruction information, optionally, the first instruction information is 0100 or 0011, indicating that the slice is unavailable in the current TA, optionally, if the instruction information is 0000, it indicates that the network slice is unavailable in the current network or private network, if the instruction information is 0001, it indicates that the network slice is unavailable in the current registration area, and if the instruction information is 0010, it indicates that the slice is unavailable due to a failure or revocation of identity authentication and authorization for a particular network slice, and further the terminal rejects the NSSAI After receiving rejected NSSAI domain information in the IE or the first IE, the terminal can determine that the first slice is unavailable in the current TA based on the information in the rejected NSSAI domain, thereby allowing the terminal to select another slice in the requested slice within the current TA and establish communication and connection with the network-side equipment.

[0042] Selectively, the network-side device may instruct the terminal whether or not to support the use of the first slice within the first TA by an extended reject NSSAI IE in the second message, selectively, as shown in Figure 5, the extended reject NSSAI IE includes a partial extended reject NSSAI list domain, as shown in Figures 6a and 6b, the partial extended reject NSSAI list domain includes reject NSSAI domains corresponding to each first slice in at least one first slice, selectively, as shown in Figure 7, the reject NSSAI domain in the partial extended reject NSSAI list domain includes at least one of information about the first slice and first instruction information, selectively, the first instruction information is 0100, indicating that the slice is not available in the current TA, and further, after receiving the reject NSSAI domain information in the extended reject NSSAI IE, the terminal can determine from the information in the reject NSSAI domain that the first slice is not available in the current TA, thereby enabling the terminal to select another slice in the requested slice within the current TA and establish communication and connection with the network-side device.

[0043] In the method of the above embodiment, the network-side device indicates that a slice is unavailable in the current TA by carrying information about the first slice and / or first instruction information in the reject NSSAI IE, first IE, or extended reject NSSAI IE in the second message. Furthermore, after receiving the second message, the terminal can determine that the first slice is unavailable in the current TA based on the reject NSSAI IE, first IE, or extended reject NSSAI IE in the second message, thereby enabling the terminal to select another slice in the requested slice within the current TA and establish communication and connection with the network-side device. In the embodiment of this application, the network-side device can instruct the terminal in various ways whether the requested slice is available within the tracking area TA, providing relatively high flexibility.

[0044] In one embodiment, the second message includes a reject network slice selection support information NSSAI information element IE or a first IE, and the reject NSSAI IE or first IE includes a reject NSSAI domain corresponding to each first slice in at least one first slice, and each reject NSSAI domain corresponding to a first slice includes at least one of the first slice information, second instruction information, and first TA information, and / or The second message includes an extended reject NSSAI IE, the extended reject NSSAI IE includes a partial extended reject NSSAI list domain, the partial extended reject NSSAI list domain includes reject NSSAI domains corresponding to each first slice in at least one first slice, and each reject NSSAI domain corresponding to a first slice includes at least one of the first slice information, second instruction information, and first TA information.

[0045] Specifically, the network-side device instructs the terminal whether to support the use of the requested slice within the target tracking area TA, using the Denied Network Slice Selection Support Information NSSAI information element IE or the first IE in the second message, where the first IE may be a newly defined information element, and optionally, as shown in Figure 8, the Denied NSSAI IE includes at least one Denied NSSAI domain corresponding to each first slice in the first slice, and as shown in Figure 9, the Denied NSSAI domain corresponding to each first slice includes at least one of the first slice information, second instruction information, and first TA information, where optionally, the second instruction information is 0100, indicating that the first slice is unavailable within the first TA. Furthermore, after receiving the Denied NSSAI IE or Denied NSSAI domain information in the second message, the terminal can determine from the information in the Denied NSSAI domain that the first slice is unavailable within the first TA, thereby allowing the terminal to select another slice in the requested slice and establish communication and connection with the network-side device.

[0046] Selectively, the network-side device may instruct the terminal by the Extended Deny NSSAI IE in the second message whether or not to support the use of the requested slice within the Target Tracking Area TA, and selectively, as shown in Figure 10, the Extended Deny NSSAI IE includes a Partial Extended Deny NSSAI List Domain, and as shown in Figures 11a and 11b, the Partial Extended Deny NSSAI List Domain includes at least one Deny NSSAI Domain to which at least one first slice corresponds, and selectively, as shown in Figure 12, the Deny NSSAI Domain includes at least one of the first slice information, second instruction information, and first TA information, where the second instruction information is 0100, indicating that the first slice is unavailable within the first TA, and further, after receiving the Deny NSSAI Domain information in the Extended Deny NSSAI IE, the terminal can determine from the information in the Deny NSSAI Domain that the first slice is unavailable within the first TA, thereby allowing the terminal to select another slice in the requested slice and establish communication and connection with the network-side device.

[0047] In the method of the above embodiment, the network-side device indicates that the first slice is unavailable within the first TA based on the information of the first slice carried in the reject NSSAI IE, first IE, or extended reject NSSAI IE in the second message, the second instruction information, and / or the information of the first TA. Furthermore, after receiving the second message, the terminal can determine that the first slice is unavailable within the first TA based on the reject NSSAI IE, first IE, or extended reject NSSAI IE in the second message, thereby allowing the terminal to select another slice in the requested slice and establish communication and connection with the network-side device. In the embodiment of this application, the network-side device can instruct the terminal in various ways whether the requested slice is available within the tracking area TA, providing relatively high flexibility.

[0048] In one embodiment, the second message includes an NSSAI service area list IE, 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 the third slice, an NSSAI service area list field, and a target timer field, the NSSAI service area list field includes at least one of third instruction information and third TA information.

[0049] Specifically, the network-side device instructs the terminal whether or not to support the use of the third slice within the third TA using the NSSAI service area list IE in the second message. Selectively, the NSSAI service area list IE shown in Figure 13 includes at least one NSSAI service area list domain, and the NSSAI service area list domain shown in Figure 14 includes an NSSAI field for the third slice, an NSSAI service area list field, and a target timer field. Selectively, the third instruction information carries a target timer field if it indicates that the third TA is a TA that does not support the use of the third slice. The target timer field is used to indicate that the third slice is unavailable within the third TA during the time period corresponding to the target timer field, after which the terminal may attempt to use the third slice within the third TA. Selectively, as shown in Figures 15a-15d, the NSSAI service area list field includes at least one of the third instruction information and information about the third TA. Here, 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. Optionally, if the third instruction information is 0, indicating that the third TA supports the use of the third slice, the terminal can use this third slice when it is at the third TA. If the third instruction information is 1, indicating that the third TA does not support the use of the third slice, the terminal cannot use this third slice when it is at the third TA. Optionally, the terminal activates a timer, which may be a default value or one configured for the terminal by the network-side equipment in the NSSAI service area list IE in the second message. Optionally, the third slice can only be used by the terminal when it has moved away from the third TA or after the timer has expired. The terminal must select another slice while at the third TA to establish communication and connection with the network-side equipment.Selectively, an NSSAI service area list domain further includes a Type of list and a Number of elements, where the list type is used to indicate the type of NSSAI service area list domain and is represented, for example, by at least one bit, where 00 represents a TAC list belonging to one PLMN and having non-contiguous TAC values, 01 represents a TAC list belonging to one PLMN and having continuous TAC values, 10 represents a TAI list belonging to different PLMNs, and 11 represents all TAIs belonging to PLMNs in a registration area that are all in an authorized area. For example, the format of the NSSAI service area list field may differ for different list types. As shown in Figures 15a and 15b, the third instruction information is used to indicate that the third TA is a TA that does not support the use of the third slice, and the number of elements is used to indicate the number of TAs in the NSSAI service area list domain that do not support the use of the third slice, and the third instruction information is used to indicate that the third TA is a TA that supports the use of the third slice, and the number of elements is used to indicate the number of TAs in the NSSAI service area list domain that support the use of the third slice.

[0050] The information in tracking area 1 in Figures 15a-15c can be represented by one or more bytes, and other tracking areas are similar. In Figures 15a-15c, one row represents one byte, and left to right represents from most significant to least significant. Other figures are similar.

[0051] For example, a network-side device carries one or more S-NSSAI TA lists in the second message, and the instruction information indicates whether the TA list is a rejected TA list and / or an allowed TA list. Selectively, a rejected TA list indicates that the use of a certain slice is denied to the TAs in this rejected TA list, and an allowed TA list indicates that the use of a certain slice is permitted to the TAs in this allowed TA list.

[0052] In the method of the above embodiment, the network-side device indicates whether the third TA supports the use of the third slice or does not support the use of the third slice by carrying third instruction information and third TA information 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 within the third TA based on the NSSAI service area list IE in the second message, thereby enabling the selection and use of slices based on the terminal's TA granularity and improving the efficiency of slice usage.

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

[0054] Specifically, the network-side device instructs the terminal whether to support the use of the second slice within the second TA via the extended authorization NSSAI IE in the second message. Selectively, as shown in Figure 16, the extended authorization NSSAI IE includes at least one authorization NSSAI domain corresponding to each second slice, and as shown in Figure 17, the authorization NSSAI domain includes at least one of the length of the authorization NSSAI domain, the NSSAI fields of the second slice, and information about the second TA. Furthermore, after receiving the authorization NSSAI domain information in the extended authorization NSSAI IE, the terminal can determine whether the second slice is available within the second TA based on the information in the authorization NSSAI domain, thereby enabling the terminal's selection and use of slices based on TA granularity.

[0055] In the method of the above embodiment, the network-side device carries the NSSAI field of the second slice and the information of the second TA in the extended authorization NSSAI IE in the second message. After the terminal receives the second message, it can determine whether the second slice is available within the second TA based on the extended authorization NSSAI IE in the second message, enabling the terminal to select and use slices based on TA granularity and improving slice utilization efficiency.

[0056] In one embodiment, the first TA includes a TA that does not support the use of the first slice within a predetermined 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; that is, within a predetermined time range, the target tracking area TA does not support the use of the first slice, and after the predetermined time range, the terminal may attempt to use the first slice within the target tracking area, thereby ensuring that the first slice is fully utilized within the target tracking area TA and improving the efficiency of slice utilization.

[0058] Selectively, the second message further includes information about the first timer, which is used to indicate that the terminal can use the first slice in the first TA after the first timer has expired.

[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 carries information about the first timer in the second message, where the first timer is used to indicate that a terminal can use the first slice in the first TA after the first timer has expired. That is, after a terminal receives the first timer in the second message and the first timer has expired, 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.

[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 preset time range, the network-side equipment may carry information about the first timer in the second message so that the terminal receives the first timer in the second message and, after the first timer has expired, 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 the efficiency of slice utilization.

[0061] In one embodiment, after the terminal receives a second message transmitted by the network-side device, The terminal further includes sending a third message to the network-side device, which is used to indicate that the terminal has received information to indicate whether or not it supports the use of a requested slice within the target tracking area (TA).

[0062] Specifically, after receiving a second message from the network-side device, the terminal may send a third message to the network-side device to inform the network-side device that the terminal has received information to instruct whether or not it supports the use of requested slices within the tracking area TA. Furthermore, the network-side device and the terminal can establish a connection and communication based on the requested slices available within the target tracking area TA, thereby improving the efficiency of slice usage.

[0063] In one embodiment, after the terminal receives a second message transmitted by the network-side device, For each first TA or current TA, the terminal adds information about first slices that the first TA or current TA does not support using to the denied slice list corresponding to the first TA or current TA. For each second TA, the terminal adds information about the second slices that the second TA supports using to the authorized slice list corresponding to the second TA. The terminal stores information about the first slice for each access type and information about the first TA that does not support the use of the first slice. The terminal stores information about the second slice for each access type and information about the second TA that supports the use of the second slice. The process further includes at least one of activating a second timer, the second timer being used to instruct a terminal to remove the first slice from the rejected slice list in the first TA or the current TA after the second timer has expired, and the terminal can then use the first slice in the first TA or the current TA.

[0064] Selectively, if the first timer is carried in the first message, the value of the second timer and the value of the first timer are the same; for example, the start times of the first and second timers are the same, and the duration of the timing is 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 either not started or started with its default value.

[0065] Specifically, after receiving a second message transmitted by a network-side device, the terminal can process the slice application information indicated in the second message based on the information in the second message indicating whether or not it supports using the requested slice within the target tracking area TA. Optionally, the terminal may add at least one first slice to a list of denied slices in its corresponding at least one first TA or current TA, thereby preventing the terminal from using the first slice in the first TA or current TA and requiring it to select and use another slice in the requested slice. Optionally, the terminal may store information on at least one first slice for each access type and information on the corresponding at least one first TA that does not support the use of the first slice. Optionally, the terminal may store information on the access type being a 3rd Generation Partnership Project. In the case of a Project, 3GPP access type or a non-3GPP access type, i.e., the terminal can store information about the first slice and information about the first TA that does not support the use of the first slice, so that when the terminal is located at the first TA, the first slice cannot be used. Correspondingly, when the terminal is located at the first TA, it can use other slices in the requested slices other than the first slice. Selectively, the terminal can store information about the second slice and information about the second TA that supports the use of the second slice in each access type, so that when the terminal is located at the second TA, it can use the second slice, realizing slice use based on TA granularity and improving slice utilization efficiency. Selectively, the terminal can start 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, so that the terminal can use the first slice in the first TA or the current TA. I.e., after the second timer expires, the terminal may attempt to use the first slice in the first TA or the current TA, so that the first slice is fully utilized within the first TA or the current TA and improve slice utilization efficiency.

[0066] For example, the terminal stores a 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 related to the TA.

[0067] For example, the terminal stores a second slice as an authorized 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 related to the TA.

[0068] In the method of the above embodiment, after receiving a second message transmitted by the network-side device, the terminal can process the slice application information indicated in the second message. As a result, 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 utilization.

[0069] In one embodiment, for any one of at least one first slice, if the first slice is included in the reject slice list corresponding to the sixth TA, the sixth TA is any one of the one or more first TAs or the current TA, and the terminal is After the device shuts down and restarts, The terminal has moved away from the first TA or the current TA, The terminal is located within the second TA, After the Universal Subscriber Identification Module (USIM) of the terminal has been removed, After the subscription data with the network identifier of the current network where the device is located is updated, After the first timer configured by the network-side equipment expires, The terminal can use the first slice if at least one of the following target conditions is met: the terminal has received the second message and the second timer that starts has expired. The first or 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, in order to improve the efficiency of slice utilization, the embodiments of this application may attempt to use a first slice if the following target conditions are met, thereby ensuring that the first slice is fully utilized within the tracking area TA and improving the efficiency of slice utilization. Selectively, after a terminal has shut down and restarted, the terminal may attempt to use the first slice; selectively, after a terminal has moved away from the first TA or the current TA, or while the terminal is in a second TA, the terminal may attempt to use the first slice; selectively, after the terminal's Universal Subscriber Identification Module (USIM) has been removed, or after the subscription data having the network identifier of the current network in which the terminal is located has been updated, the terminal may attempt to use the first slice; selectively, after a network-side device has carried the first timer to a second message, and the first or second timer has expired, the terminal may attempt to use the first slice, i.e., if the tracking area TA in which the terminal is located has changed or the terminal's configuration information has changed, the terminal may attempt to use the first slice, thereby ensuring that the first slice is fully utilized within the TA, effectively meeting the need to establish connection and communication between the terminal and the network-side device, and improving the efficiency of slice utilization.

[0071] For example, if a terminal receives first TA information based on slice granularity, the TA in the terminal's first TA information cannot use the first slice, and the terminal moves away from the TA in the first TA information, the terminal may attempt to use the first slice. When a second TA information based on slice granularity is received, the TA in the terminal's second TA information can use the second slice. If 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 remembers the second slice as a rejected slice in the current tracking area. When the terminal receives first TA information based on slice particle size, the terminal will receive first TA information The first slice cannot be used in the TA in the terminal. information If it is within the TA, the terminal moves the first slice to the rejected slice list. When a terminal receives second TA information based on slice granularity, and the terminal is within the 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 conditions are met, the terminal attempts to use the first slice, thereby ensuring that the first slice is fully utilized within the TA, effectively meeting the need to establish connection and communication between the terminal and network-side equipment, and improving the efficiency of slice utilization.

[0073] In one embodiment, if the terminal satisfies at least one target condition, the terminal is The terminal removes the first slice from the rejected slice list corresponding to the sixth TA, The operation in which the terminal updates the first slice to a slice usable within the sixth TA, The terminal performs at least one of the following operations: sending a fourth message to a network-side device, and the fourth message is: The system includes at least one of the following: first target slice information to be used and terminal capability instruction information, the terminal capability instruction information being used to indicate whether the terminal supports the first capability, and the first capability being the capability to receive and use information indicating whether or not it supports the use of the requested slice within the target TA.

[0074] Specifically, if the terminal satisfies the target conditions, the terminal may timely update the application status of the slices stored within the TA and attempt to use the first slice within the TA, thereby improving the utilization efficiency of the TA and meeting the need for the terminal and network-side equipment to establish connection and communication. Optionally, if the target conditions are met, the terminal may remove 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 within the first TA or the current TA. Furthermore, the terminal may attempt to use the first slice in the first TA or the current TA, thereby ensuring the first slice is fully utilized within the TA and improving slice utilization efficiency. Optionally, the terminal may send a fourth message to the network-side equipment, namely, the slice information the terminal intends to use and the terminal capability instruction information shown in Figure 18 to the network-side equipment. Optionally, the terminal capability instruction information is used to characterize the terminal's ability to support network slice extended TA list information, thereby enabling the network-side equipment to timely and accurately instruct the terminal whether or not to support the use of the requested slice within the target tracking area TA based on the updated requested slice information.

[0075] Selectively, if terminal capability information indicates that the terminal supports the first capability, the network-side equipment carries information in the second message to indicate whether or not it supports the use of the requested slice within the target tracking area TA; if terminal capability information indicates that the terminal does not support the first capability, the network-side equipment does not carry information in the second message to indicate whether or not it supports the use of the requested slice within the target tracking area TA. In the method of the above embodiment, if the terminal satisfies the target conditions, the terminal may timely update the application status of the slices stored within the TA and attempt to use the slices within the TA, thereby effectively improving the efficiency of slice utilization and meeting the need for the terminal and network-side equipment to establish connection and communication.

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

[0077] Specifically, when a terminal receives new slice configuration information in a first target network (e.g., a public land mobile communications network (PLMN) or a standalone non-public network (SNPN)) transmitted by a network-side device, if slice information in the rejected slice list is included in the new slice configuration information in the target PLMN or SNPN network, the terminal removes the information from the rejected slice list that does not support the use of slices in the corresponding TA and stops the associated timer. 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.

[0078] In the method of the above embodiment, the terminal receives slice information of the first target network configuration transmitted by the network-side device, 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 transmitted by the network-side device. As a result, the terminal can accurately and effectively use slices within the TA based on the updated slice application information, thereby improving the efficiency of slice utilization.

[0079] In one embodiment, the terminal receives slice information permitted by the second target network transmitted by the network-side device, If the permitted slice information includes the third target slice information in the denied slice list of the fifth TA, the terminal removes the third target slice information from the denied slice list and stops the second timer associated with the third target slice information, and the fifth TA is the TA corresponding to the second target network.

[0080] Specifically, when a terminal receives network permission slice information for a second target network (e.g., a target PLMN or SNPN network) transmitted by a network-side device, and the slice information in the denied slice list is included in the network-permitted slice information for the target PLMN or SNPN network, the terminal removes the information that does not support the use of the slice in the corresponding TA from the denied slice list and stops the associated timer. This allows the terminal to use the slices within the TA accurately and effectively based on the updated slice application information, thereby improving the efficiency of slice utilization.

[0081] In the method of the above embodiment, the terminal receives slice information permitted by the second target network transmitted by the network-side device, and updates the slice information in the denied slice list stored by the terminal itself based on the slice information permitted by the second target network transmitted by the network-side device. As a result, the terminal can accurately and effectively use slices within the TA based on the updated slice application information, thereby improving the efficiency of slice utilization.

[0082] In one embodiment, the first message is: The system includes at least one of request slice information and terminal capability indication information, the terminal capability indication information being used to indicate whether the terminal supports a first capability, and the first capability being the capability to receive and use information indicating whether or not the use of request slices within the target TA is supported.

[0083] Specifically, when a terminal sends a first message to a network-side device, the first message may include request slice information and terminal capability instruction information, where request slice information is slice information that the terminal requests to use to establish a connection with the network-side device, and terminal capability instruction information is used to indicate whether the terminal will not use the request slice in the target TA and / or whether it supports using the request slice in the target TA, thereby Network-side devices After receiving the requested slice information and terminal capability instruction information transmitted by the terminal, it can determine whether it is necessary to instruct the terminal on slice application information based on TA granularity, and / or whether it is necessary to accurately instruct the terminal on the application status of the requested slice in the target tracking area.

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

[0085] Figure 19 is the second flowchart of the communication method according to an embodiment of this application. As shown in Figure 19, the method according to this embodiment is Step 1901 involves the network-side device receiving a first message sent by the terminal requesting to establish a connection with the network-side device using a request slice. Step 1902 includes the step of the network-side device sending a second message to the terminal that carries information to instruct whether or not it supports the use of a requested slice within the target tracking area TA.

[0086] Selectively, the second message is, The system includes at least one of the following: information of at least one first slice and at least one of the first instruction information, the first instruction information being used to indicate that at least one first slice is unavailable within the 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 the following: information of at least one first slice, information of one or more first TAs corresponding to each first slice in at least one first slice, information of at least one second slice, information of one or more second TAs corresponding to each second slice in at least one second slice, and second instruction information, wherein the first TA is a TA that does not support the use of the first slice, the second TA is a TA that supports the use of the second slice, and the second instruction 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 request slice, and the target tracking area TA includes the first TA or the second TA, or The second message is, The target TA includes at least one third slice, information for a third TA, and at least one of third instruction information, the third instruction information being 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] Selectively, the second message includes a reject network slice selection support information NSSAI information element IE or a first IE, and the reject NSSAI IE or first IE includes reject NSSAI domains corresponding to each first slice in at least one first slice, and each reject NSSAI domain corresponding to a first slice includes at least one of the first slice information and first instruction information, and / or The second message includes an extended reject NSSAI IE, the extended reject NSSAI IE includes a partial extended reject NSSAI list domain, the partial extended reject NSSAI list domain includes reject NSSAI domains corresponding to each first slice in at least one first slice, and each reject NSSAI domain corresponding to a first slice includes at least one of the information of the first slice and the first instruction information.

[0088] Selectively, the second message includes a reject network slice selection support information NSSAI information element IE or a first IE, and the reject NSSAI IE or first IE includes a reject NSSAI domain corresponding to each first slice in at least one first slice, and each reject NSSAI domain corresponding to a first slice includes at least one of the first slice information, the second instruction information, and the first TA information, and / or The second message includes an extended reject NSSAI IE, the extended reject NSSAI IE includes a partial extended reject NSSAI list domain, the partial extended reject NSSAI list domain includes reject NSSAI domains corresponding to each first slice in at least one first slice, and each reject NSSAI domain corresponding to a first slice includes at least one of the first slice information, second instruction information, and first TA information.

[0089] Selectively, the second message includes an NSSAI service area list IE, each NSSAI service area list IE includes at least one NSSAI service area list domain, the NSSAI service area list domain includes an NSSAI field of the third slice, an NSSAI service area list field, and a target timer field, the NSSAI service area list field includes at least one of the third instruction information and the third TA information.

[0090] Selectively, the second message includes an extended authorization NSSAI IE, which includes an authorization NSSAI domain corresponding to at least one second slice, and each authorization NSSAI domain corresponding to a second slice includes at least one of the length of the authorization NSSAI domain, the NSSAI fields of the second slice, and information of the second TA.

[0091] Selectively, the first TA includes TAs that do not support the use of the first slice within a predetermined time range.

[0092] Selectively, the second message further includes information about the first timer, which is used to indicate that the terminal can use the first slice in the first TA after the first timer has expired.

[0093] Selectively, the network-side device receives a third message sent by the terminal, which is used to indicate that the terminal has received information to indicate whether or not it supports the use of a requested slice within the target tracking area (TA).

[0094] Selectively, the first message is, The system includes at least one of request slice information and terminal capability indication information, the terminal capability indication information being used to indicate whether the terminal supports a first capability, and the first capability being the capability to receive and use information indicating whether or not the use of request slices within the target TA is supported.

[0095] As an example, one interaction flowchart of a communication method according to an embodiment of this application is shown in Figure 20.

[0096] In step 1, the terminal sends a first message to the first core network element AMF to establish an N1 connection between the terminal and the network, and optionally the first message may be a registration request message, and the first message is (1) Terminal capability instruction information, the terminal capability instruction information is used to indicate whether the terminal supports a first capability, and the first capability is the capability to receive and use information to indicate whether the terminal supports the use of a requested slice within the target TA, (2) Transport at least one of the requested slice information including one or more single network slice selection support information S-NSSAI, When a network-side device (e.g., the first core network element AMF) receives a slice request from a terminal, it performs at least one of the following operations: In step 2, the first core network element AMF is replaced by the second core network element (e.g., Unified Data Management Unit UDM / Network Slice Selection Network Element). NSSF The system queries and confirms the current status of S-NSSAI in the requested slice information and / or the application status of each TA in other RAs. Here, the application status is whether to allow or deny the provision of services to the requested slice. If service is allowed, the slice is placed in the allowed network slice selection support information domain S-NSSAIallowed S-NSSAI and sent back to the terminal. If service is denied, the slice is placed in the rejected network slice selection support information domain rejected S-NSSAI and sent back to the terminal. In step 3, the first core network element AMF sends a second message to the terminal, which is used to indicate whether the establishment of an N1 connection between the terminal and the network was successful or failed.

[0097] Selectively, the first core network element AMF carries one or more rejected network slice selection support information domains (rejected S-NSSAI) in the second message, the rejected network slice selection support information domains (rejected S-NSSAI) indicating that the slice is currently unavailable within the registration area (RA) range and carrying the first cause value "The slice is unavailable in the current registration area", selectively carrying timer a, which is used to instruct the terminal to wait for timer a to expire before attempting to initiate a request using the slice. Selectively, the second message is, It may include at least one of the information of at least one first slice and the first referencing information, or The second message is, It includes at least one of the following: information of at least one first slice, information of a first TA corresponding to each of the at least one first slice, information of at least one second slice, information of a second TA corresponding to each of the at least one second slice, and second referencing information, or The second message is, It includes at least one request slice, information about a third TA, and information about a third instruction.

[0098] In other words, the first core network element AMF, after receiving a request from a terminal, notifies the terminal of a list of TAs that support and / or deny the use of slices based on slice granularity, based on the application status of multiple TAs in the slice's RA. After the terminal receives the list of TAs that support and / or deny the use of slices based on slice granularity, it combines this with the currently located TA information to determine whether or not slices can be used at the current TA.

[0099] Selectively, when a network-side device indicates that an N1 connection between the terminal and the network has been successfully established, the first core network element AMF transports to the terminal information that does not support the terminal not using the requested slice within the target TA by placing it in the information element of the denied network slice selection support information in the registration completion message and / or the information element of the extended denied network slice selection support information and / or the newly defined first IE, and transports to the terminal information that supports the terminal using the requested slice within the target TA by placing it in the information element of the extended permitted network slice selection support information in the registration completion message and / or the newly defined IE. If a network-side device indicates that the N1 connection between the terminal and the network has failed, the first core network element AMF carries to the terminal information that it does not support the terminal not using the requested slice within the target TA, by including this information in the information elements of the rejected network slice selection support information in the registration rejection message and / or the information elements of the extended rejected network slice selection support information and / or the newly defined first IE.

[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 instruction information based on slice granularity, the terminal sends a third message to the first core network element AMF, which is used to confirm that the terminal has received first TA information and / or second TA information and / or instruction information based on slice granularity, i.e., to confirm that the terminal has received information to indicate whether or not it supports the use of requested slices within the tracking area TA.

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

[0102] In step 6, if the above usage conditions are met, the terminal may use the first slice and perform at least one of the following operations: (1) Remove the first slice from the list of rejected slices in the current tracking area, and identify that this slice can be used for a valid request after it has been removed. (2) Based on service demand and slice selection, the terminal transmits the following instruction information to the first core network element AMF, which is used for mobile or periodic registration updates. Selectively, the terminal sends a fourth message to the network-side device, and this fourth message is a request message. A. Terminal capability instruction information for instructing a terminal to support the function of initiating a slice request in a TA supported within the same RA, wherein the function of initiating a slice request in a TA supported within the same RA refers to terminal capability instruction information that allows the terminal to use the requested slice when moving to another TA if the requested slice is rejected in the current TA but is acceptable in another TA within the same RA. B, including at least one of the following: request slice information which includes one or more first slices, In step 7, the first core network element AMF, after receiving the terminal message and confirming that the current network can serve the requested slice, indicates that the N1 connection between the terminal and the network is successful. Optionally, the fifth message may contain the first slice information available in the target tracking area, and optionally, the fifth message may be a registration acceptance message. In step 8, after receiving the registration acceptance message, the terminal sends a sixth message to the first core network element AMF, which is used to confirm whether the terminal has received information instructing it whether it will not use the requested slice in the target TA and / or whether it will support the use of the requested slice in the target TA. Optionally, the sixth message may be a registration completion message.

[0103] In the embodiments of this application, the communication method may be implemented by a virtual device. In the embodiments of this application, the communication device according to the embodiments of this application will be described as an example in which a virtual device implements the communication method.

[0104] Figure 21 is one of the schematic diagrams of the structure of a communication device according to an embodiment of this application. As shown in Figure 21, the communication device according to this embodiment is A transmission module 2101 sends a first message to a network-side device requesting it to establish a connection with the network-side device using a request slice, The system includes a receiving module 2102 for receiving a second message transmitted by a network-side device, which carries information indicating whether or not to support the use of a requested slice within the target tracking area TA.

[0105] Selectively, the second message is, The system includes at least one of the following: information of at least one first slice and at least one of the first instruction information, the first instruction information being used to indicate that at least one first slice is unavailable within the 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 the following: information of at least one first slice, information of one or more first TAs corresponding to each first slice in at least one first slice, information of at least one second slice, information of one or more second TAs corresponding to each second slice in at least one second slice, and second instruction information, wherein the first TA is a TA that does not support the use of the first slice, the second TA is a TA that supports the use of the second slice, and the second instruction information is used to indicate that the first slice is unavailable within the first TA, where the first slice or the second slice is a slice in the request slice, and the target tracking area TA includes the first TA or the second TA, or The second message is, The target TA includes information on at least one third slice, information on a third TA, and at least one of third instruction information, the third instruction information being 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] Selectively, the second message includes a reject network slice selection support information NSSAI information element IE or a first IE, and the reject NSSAI IE or first IE includes reject NSSAI domains corresponding to each first slice in at least one first slice, and each reject NSSAI domain corresponding to a first slice includes at least one of the first slice information and first instruction information, and / or The second message includes an extended reject NSSAI IE, the extended reject NSSAI IE includes a partial extended reject NSSAI list domain, the partial extended reject NSSAI list domain includes reject NSSAI domains corresponding to each first slice in at least one first slice, and each reject NSSAI domain corresponding to a first slice includes at least one of the information of the first slice and the first instruction information.

[0107] Selectively, the second message includes a reject network slice selection support information NSSAI information element IE or a first IE, and the reject NSSAI IE or first IE includes a reject NSSAI domain corresponding to each first slice in at least one first slice, and each reject NSSAI domain corresponding to a first slice includes at least one of the first slice information, the second instruction information, and the first TA information, and / or The second message includes an extended reject NSSAI IE, the extended reject NSSAI IE includes a partial extended reject NSSAI list domain, the partial extended reject NSSAI list domain includes reject NSSAI domains corresponding to each first slice in at least one first slice, and each reject NSSAI domain corresponding to a first slice includes at least one of the first slice information, second instruction information, and first TA information.

[0108] Selectively, the second message includes an NSSAI service area list IE, 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 the third slice, an NSSAI service area list field, and a target timer field, the NSSAI service area list field includes at least one of the third instruction information and the third TA information.

[0109] Selectively, the second message includes an extended authorization NSSAI IE, which includes an authorization NSSAI domain corresponding to at least one second slice, and each authorization NSSAI domain corresponding to a second slice includes at least one of the length of the authorization NSSAI domain, the NSSAI fields of the second slice, and information of the second TA.

[0110] Selectively, the first TA includes TAs that do not support the use of the first slice within a predetermined time range.

[0111] Selectively, the second message further includes information about the first timer, which is used to indicate that the terminal can use the first slice in the first TA after the first timer has expired.

[0112] Selectively, the transmitting module 2101 is further used to send a third message to network-side equipment, which indicates that the terminal has received information to indicate whether or not it supports the use of a requested slice within the target tracking area TA.

[0113] Selectively, the receiving module 2102 further allows the terminal to add information about first slices that the first TA or current TA does not support using to the denied slice list corresponding to the first TA or current TA. For each second TA, the terminal adds information about the second slices that the second TA supports using to the authorized slice list corresponding to the second TA. To store information about the first slice for each access type and information about the first TA that does not support the use of the first slice, To store information about the second slice for each access type and information about the second TA that supports the use of the second slice, It is used to activate a second timer, which, after the second timer expires, is used to indicate that the terminal can use the first slice in the first TA or the current TA.

[0114] Selectively, the receiving module 2102 further determines, for any one of the first slices of at least one first slice, if the first slice is included in the reject slice list corresponding to the sixth TA, the sixth TA is any one of the one or more first TAs or the current TA. After the device shuts down and restarts, The terminal has moved away from the first TA or the current TA, The terminal is located within the second TA, After the Universal Subscriber Identification Module (USIM) of the terminal has been removed, After the subscription data with the network identifier of the current network where the device is located is updated, After the first timer configured by the network-side equipment expires, The first slice can be used if at least one of the following target conditions is met: the terminal receives the second message, and the second timer that starts has expired. The first or 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] Selectively, the receiving module 2102 further satisfies at least one target condition, The operation of removing the first slice from the rejection slice list corresponding to the sixth TA, The operation of updating the first slice to a slice usable within the sixth TA, It is used to perform at least one of the following operations: sending a fourth message to a network-side device, and the fourth message is: The system includes at least one of the following: first target slice information to be used and terminal capability instruction information, the terminal capability instruction information being used to indicate whether the terminal supports the first capability, and the first capability being the capability to receive and use information indicating whether or not it supports the use of the requested slice within the target TA.

[0116] Selectively, the receiving module 2102 is further used to receive slice information of a first target network configuration transmitted by network-side equipment. If the slice information includes the second target slice information in the rejected slice list corresponding to the fourth TA, the second target slice information is removed from the rejected slice list, and the second timer associated with the second target slice information is stopped. The fourth TA is the TA corresponding to the first target network.

[0117] Selectively, the receiving module 2102 is further used to receive slice information permitted by a second target network transmitted by network-side equipment. If the permitted slice information includes the third target slice information in the denied slice list corresponding to the fifth TA, the third target slice information is removed from the denied slice list, and the second timer associated with the third target slice information is stopped. The fifth TA is the TA corresponding to the second target network.

[0118] Selectively, the first message is, The system includes at least one of request slice information and terminal capability indication information, the terminal capability indication information being used to indicate whether the terminal supports a first capability, and the first capability being the capability to receive and use information indicating whether or not the use of request slices within the target TA is supported.

[0119] The apparatus of this embodiment can be used to carry out the method of any one embodiment of the terminal-side method described above. Its specific implementation process and technical effects are the same as those of the first device-side method embodiment, and a detailed description can be found in the specific terminal-side method embodiment; no further explanation is provided here.

[0120] Figure 22 is the second schematic diagram of the structure of a communication device according to an embodiment of this application. As shown in Figure 22, the communication device according to this embodiment is A receiving module 2201 for receiving a first message sent by the terminal requesting to establish a connection with a network-side device using a request slice, The terminal includes a transmit module 2202 for sending a second message that carries information to indicate whether or not it supports the use of a requested slice within the target tracking area TA.

[0121] Selectively, the second message is, The system includes at least one of the following: information of at least one first slice and at least one of the first instruction information, the first instruction information being used to indicate that at least one first slice is unavailable within the 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 the following: information of at least one first slice, information of one or more first TAs corresponding to each first slice in at least one first slice, information of at least one second slice, information of one or more second TAs corresponding to each second slice in at least one second slice, and second instruction information, wherein the first TA is a TA that does not support the use of the first slice, the second TA is a TA that supports the use of the second slice, and the second instruction 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 request slice, and the target tracking area TA includes the first TA or the second TA, or The second message is, The target TA includes information on at least one third slice, information on a third TA, and at least one of third instruction information, the third instruction information being 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] Selectively, the second message includes a reject network slice selection support information NSSAI information element IE or a first IE, and the reject NSSAI IE or first IE includes reject NSSAI domains corresponding to each first slice in at least one first slice, and each reject NSSAI domain corresponding to a first slice includes at least one of the first slice information and first instruction information, and / or The second message includes an extended reject NSSAI IE, the extended reject NSSAI IE includes a partial extended reject NSSAI list domain, the partial extended reject NSSAI list domain includes reject NSSAI domains corresponding to each first slice in at least one first slice, and each reject NSSAI domain corresponding to a first slice includes at least one of the information of the first slice and the first instruction information.

[0123] Selectively, the second message includes a reject network slice selection support information NSSAI information element IE or a first IE, and the reject NSSAI IE or first IE includes a reject NSSAI domain corresponding to each first slice in at least one first slice, and each reject NSSAI domain corresponding to a first slice includes at least one of the first slice information, the second instruction information, and the first TA information, and / or The second message includes an extended reject NSSAI IE, the extended reject NSSAI IE includes a partial extended reject NSSAI list domain, the partial extended reject NSSAI list domain includes reject NSSAI domains corresponding to each first slice in at least one first slice, and each reject NSSAI domain corresponding to a first slice includes at least one of the first slice information, second instruction information, and first TA information.

[0124] Selectively, the second message includes an NSSAI service area list IE, 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 the third slice, an NSSAI service area list field, and a target timer field, the NSSAI service area list field includes at least one of the third instruction information and the third TA information.

[0125] Selectively, the second message includes an extended authorization NSSAI IE, which includes an authorization NSSAI domain corresponding to at least one second slice, and each authorization NSSAI domain corresponding to a second slice includes at least one of the length of the authorization NSSAI domain, the NSSAI fields of the second slice, and information of the second TA.

[0126] Selectively, the first TA includes TAs that do not support the use of the first slice within a predetermined time range.

[0127] Selectively, the second message further includes information about the first timer, which is used to indicate that the terminal can use the first slice in the first TA after the first timer has expired.

[0128] Selectively, the receiving module 2201 is further used to receive a third message transmitted by the terminal, which indicates that the terminal has received information to indicate whether or not it supports the use of a requested slice within the target tracking area TA.

[0129] The first message is, The system includes at least one of request slice information and terminal capability indication information, the terminal capability indication information being used to indicate whether the terminal supports a first capability, and the first capability being the capability to receive and use information indicating whether or not the use of request slices within the target TA is supported.

[0130] The apparatus of this embodiment can be used to implement any one of the embodiments of the network equipment-side method described above. Its specific implementation process and technical effects are the same as those of the first embodiment of the equipment-side method, and a detailed description can be found in the specific embodiment of the network equipment-side method; no further explanation is provided here.

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

[0132] Selectively, 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 this program or instruction is executed by the processor 2301, each step of the embodiment of the communication method described above can be realized and the same technical effect can be achieved. If the communication device 2300 is a network-side device, when this program or instruction is executed by the processor 2301, each step of the embodiment of the communication method described above can be realized and the same technical effect can be achieved. To avoid repetition of the explanation, no further explanation is provided here.

[0133] An embodiment of this application further provides a terminal including a processor and a communication interface, the communication interface being used to send a first message to a network-side device requesting it to establish a connection with the network-side device using a requested slice, and to receive a second message sent by the network-side device, which carries information indicating whether or not to support the use of the requested slice within a target tracking area (TA). This terminal embodiment corresponds to the terminal-side method embodiment described above, and any of the implementation processes and embodiments of the method embodiment described above may be applied to this terminal embodiment and achieve similar technical effects. Specifically, Figure 24 is a schematic diagram of the hardware structure realizing the terminal of the embodiment of this application.

[0134] This terminal 1000 includes, but is not limited to, some of the following components: 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 those skilled in the art will understand, the terminal 1000 may further include a power supply (e.g., a battery) to power each component, and the power supply may be logically connected to the processor 1010 by a power management system, thereby enabling functions such as charge / discharge management and power consumption management by the power management system. 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 combinations of some components, or different arrangements of components, which will not be described further here.

[0136] It should be understood that, in the embodiments of this application, the input unit 1004 may include a graphics processing unit (GPU) 10041 and a microphone 10042, and the graphics processor 10041 processes still images or video image data obtained by an image capture device (e.g., a camera) in video capture mode or 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, organic light-emitting diodes, etc. 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 touchscreen. The touch panel 10071 may include two parts: a touch detection device and a touch controller. 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, or an operating lever, and will not be described further here.

[0137] In the embodiments of this application, the radio frequency unit 1001 can receive downlink data from network-side equipment and transmit it to the processor 1010 for processing, and the radio frequency unit 1001 can also transmit uplink data to network-side equipment. 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] Memory 1009 may be used to store software programs or instructions and various data. Memory 1009 may include a first storage area mainly for storing programs or instructions and a second storage area for storing data, where the first storage program or instruction storage area can store an operating system, an application program or instruction necessary for at least one function (e.g., audio playback function, image playback function, etc.), etc. Memory 1009 may also include volatile memory or non-volatile memory, or memory 1009 may include both volatile and non-volatile memory. It may include high-speed random access memory and non-volatile memory, where the non-volatile memory may be read-only memory (ROM), programmable read-only memory (PROM), erasable programmable read-only memory (Erasable PROM, EPROM), electrically erasable programmable read-only memory (Electrically EPROM, EEPROM), or flash memory. Volatile memory may be random access memory (RAM), static random access memory (Static RAM, SRAM), dynamic random access memory (DRAM), synchronous dynamic random access memory (Synchronous DRAM, SDRAM), double data rate synchronous dynamic random access memory (Double Data Rate SDRAM, DDRSDRAM), enhanced synchronous dynamic random access memory (Enhanced SDRAM, ESDRAM), synchronous link dynamic random access memory (Synch link DRAM, SLDRAM), and direct memory bus random access memory (Direct Rambus RAM, DRRAM). Memory 1009 in the embodiments of this 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, a flash memory device, or another non-volatile solid-state memory device.

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

[0140] Here, the radio frequency unit 1001 sends a first message to the network-side device requesting it to establish a connection with the network-side device using the request slice. It is used to receive a second message transmitted by network-side equipment that carries information indicating whether or not to support the use of the requested slice within the target tracking area (TA).

[0141] Selectively, the second message is, The system includes at least one of the following: information of at least one first slice and at least one of the first instruction information, the first instruction information being used to indicate that at least one first slice is unavailable within the 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 the following: information of at least one first slice, information of one or more first TAs corresponding to each first slice in at least one first slice, information of at least one second slice, information of one or more second TAs corresponding to each second slice in at least one second slice, and second instruction information, wherein the first TA is a TA that does not support the use of the first slice, the second TA is a TA that supports the use of the second slice, and the second instruction information is used to indicate that the first slice is unavailable within the first TA, where the first slice or the second slice is a slice in the request slice, and the target tracking area TA includes the first TA or the second TA, or The second message is, The target TA includes information on at least one third slice, information on a third TA, and at least one of third instruction information, the third instruction information being 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] Selectively, the second message includes a reject network slice selection support information NSSAI information element IE or a first IE, and the reject NSSAI IE or first IE includes reject NSSAI domains corresponding to each first slice in at least one first slice, and each reject NSSAI domain corresponding to a first slice includes at least one of the first slice information and first instruction information, and / or The second message includes an extended reject NSSAI IE, the extended reject NSSAI IE includes a partial extended reject NSSAI list domain, the partial extended reject NSSAI list domain includes reject NSSAI domains corresponding to each first slice in at least one first slice, and each reject NSSAI domain corresponding to a first slice includes at least one of the information of the first slice and the first instruction information.

[0143] Selectively, the second message includes a reject network slice selection support information NSSAI information element IE or a first IE, and the reject NSSAI IE or first IE includes a reject NSSAI domain corresponding to each first slice in at least one first slice, and each reject NSSAI domain corresponding to a first slice includes at least one of the first slice information, the second instruction information, and the first TA information, and / or The second message includes an extended reject NSSAI IE, the extended reject NSSAI IE includes a partial extended reject NSSAI list domain, the partial extended reject NSSAI list domain includes reject NSSAI domains corresponding to each first slice in at least one first slice, and each reject NSSAI domain corresponding to a first slice includes at least one of the first slice information, second instruction information, and first TA information.

[0144] Selectively, the second message includes an NSSAI service area list IE, 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 the third slice, an NSSAI service area list field, and a target timer field, the NSSAI service area list field includes at least one of the third instruction information and the third TA information.

[0145] Selectively, the second message includes an extended authorization NSSAI IE, which includes an authorization NSSAI domain corresponding to at least one second slice, and each authorization NSSAI domain corresponding to a second slice includes at least one of the length of the authorization NSSAI domain, the NSSAI fields of the second slice, and information of the second TA.

[0146] Selectively, the first TA includes TAs that do not support the use of the first slice within a predetermined time range.

[0147] Selectively, the second message further includes information about the first timer, which is used to indicate that the terminal can use the first slice in the first TA after the first timer has expired.

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

[0149] Selectively, the processor 1010 further, For each first TA or current TA, the terminal adds information about first slices that the first TA or current TA does not support using to the denied slice list corresponding to the first TA or current TA. For each second TA, the terminal adds information about the second slices that the second TA supports using to the authorized slice list corresponding to the second TA. To store information about the first slice for each access type and information about the first TA that does not support the use of the first slice, To store information about the second slice for each access type and information about the second TA that supports the use of the second slice, It is used to activate a second timer, which, after the second timer expires, is used to indicate that the terminal can use the first slice in the first TA or the current TA.

[0150] Selectively, the processor 1010 further determines that for any one of the first slices, if the first slice is included in the rejected slice list corresponding to the sixth TA, the sixth TA is any one of the first TAs or the current TA. After the device shuts down and restarts, The terminal has moved away from the first TA or the current TA, The terminal is located within the second TA, After the Universal Subscriber Identification Module (USIM) of the terminal has been removed, After the subscription data with the network identifier of the current network where the device is located is updated, After the first timer configured by the network-side equipment expires, The first slice can be used if at least one of the following target conditions is met: the terminal receives the second message, and the second timer that starts has expired. The first or 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] Selectively, the processor 1010 further satisfies at least one target condition, The operation of removing the first slice from the rejection slice list corresponding to the sixth TA, The operation of updating the first slice to a slice usable within the sixth TA, It is used to perform at least one of the following operations: sending a fourth message to a network-side device, and the fourth message is: The system includes at least one of the following: first target slice information to be used and terminal capability instruction information, the terminal capability instruction information being used to indicate whether the terminal supports the first capability, and the first capability being the capability to receive and use information indicating whether or not it supports the use of the requested slice within the target TA.

[0152] Selectively, the radio frequency unit 1001 is also used to receive slice information of a first target network configuration transmitted by network-side equipment. If the slice information includes the second target slice information in the rejected slice list corresponding to the fourth TA, the second target slice information is removed from the rejected slice list, and the second timer associated with the second target slice information is stopped. The fourth TA is the TA corresponding to the first target network.

[0153] Selectively, the radio frequency unit 1001 is further used to receive slice information permitted by a second target network transmitted by network-side equipment. If the permitted slice information includes the third target slice information in the denied slice list corresponding to the fifth TA, the third target slice information is removed from the denied slice list, and the second timer associated with the third target slice information is stopped. The fifth TA is the TA corresponding to the second target network.

[0154] Selectively, the first message is, The system includes at least one of request slice information and terminal capability indication information, the terminal capability indication information being used to indicate whether the terminal supports a first capability, and the first capability being the capability to receive and use information indicating whether or not the use of request slices within the target TA is supported.

[0155] Embodiments of this application further provide a network-side device including a processor and a communication interface, the communication interface being used to receive a first message transmitted by a terminal requesting to establish a connection with the network-side device using a requested slice, and to transmit a second message to the terminal carrying information to indicate whether or not to support the use of the requested slice within 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 each implementation process and implementation of the embodiment of the method described above can be applied to this embodiment of the network-side device and achieve the same technical effects.

[0156] Specifically, embodiments of this application further provide network-side equipment. As shown in Figure 25, this network-side equipment 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 this application further includes instructions or programs stored in memory 1103 and operable on processor 1101, the processor 1101 can call instructions or programs in memory 1103 and perform the same technical effects as those shown in Figure 22, and will not be described further here to avoid repetition.

[0158] Embodiments of this application further provide a readable storage medium on which a program or instruction is stored, and when this program or instruction is executed by a processor, each process of the above-described communication method embodiment can be realized and similar technical effects can be achieved. To avoid repetition, no further explanation is provided here.

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

[0160] Embodiments of this application further provide a chip comprising a processor and a communication interface, the communication interface being coupled with the processor, the processor running programs or instructions and used to implement each process of the embodiments of the communication method described above, and achieving the same technical effects. To avoid repetition, no further explanation is provided here.

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

[0162] Embodiments of this application further provide a computer program / program product in which the computer program / program product is stored in a storage medium and executed by at least one processor to realize each process of the above-described communication method embodiment and achieve the same technical effects. To avoid repetition, no further explanation is provided here.

[0163] Embodiments of this application further provide a communication system including a terminal and network-side equipment, wherein the terminal may be used to perform the steps of the communication method described above, and the network-side equipment may be used to perform the steps of the communication method described above.

[0164] It should be noted that in this specification, the terms “including,” “contains,” or any other variation thereof are intended to cover the non-exclusive “including,” thereby including not only those elements but also other elements not explicitly listed, or elements specific to such process, method, article, or apparatus. Unless otherwise specified, an element limited by the phrase “including one of…” is not excluded from the existence of other identical elements in a process, method, article, or apparatus containing that element. It should also be noted that the scope of methods and apparatus in embodiments of this application is not limited to performing functions in the order shown or discussed, but may include performing functions in a manner that is essentially simultaneous or in reverse order based on the functions involved, for example, performing methods described in a different procedure than that described, and adding, omitting, or combining various steps. Furthermore, features described by reference to some examples may be combined with other examples.

[0165] As will be readily apparent to those skilled in the art from the above description of the embodiments, the methods of the above embodiments can be implemented in the form of software and a necessary general-purpose hardware platform. Of course, they may also be implemented in hardware, but in many cases the former is a more preferred embodiment. With this understanding, the substantial or prior art contributions of the technical proposals of this application are embodied in the form of a computer software product, which is stored on a single storage medium (e.g., ROM / RAM, magnetic disk, optical disk) and may include some instructions to cause a terminal (which may be a mobile phone, computer, server, air conditioner, or network device, etc.) to execute the methods of each embodiment of this application.

[0166] The above describes embodiments of this application, accompanied by drawings; however, this application is not limited to the specific embodiments described above. The specific embodiments described above are merely illustrative and not restrictive. Those skilled in the art can, by the suggestion of this application, make many forms, as long as they do not deviate from the spirit and scope protected by the claims of this application, and all of these fall within the scope of protection of this application.

Claims

1. A method of communication, The terminal sends a registration request message to the network-side device, which carries information about the requested slice. The terminal includes receiving a second message transmitted by the network-side device, which carries information indicating whether or not to support the use of the requested slice within the target tracking area TA. The second message includes information of at least one first slice and information of one or more first TAs corresponding to each first slice in the at least one first slice, wherein the first TA is a TA that does not support the use of the first slice, where the first slice is a slice in the requested slice. Or, A communication method wherein the second message includes information of at least one second slice and information of one or more second TAs corresponding to each second slice in the at least one second slice, the second TA being a TA that supports the use of the second slice, where the second slice is a slice in the request slice.

2. The second message includes a second instruction information, which is used to indicate that the first slice is unavailable within the first TA. Or, The communication method according to claim 1, wherein the second message is further used to indicate that the second slice is available within the second TA.

3. The second message mentioned above is, The system includes at least one of information of at least one first slice and at least one of first instruction information, wherein the first instruction 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 requested slice, and the target tracking area TA includes the current TA, or The second message mentioned above is, The communication method according to claim 1, comprising at least one of information of at least one third slice, information of 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 the use of the third slice or a TA that does not support the use of the third slice, the target TA comprises the third TA, and the third slice is a slice in the requested slice.

4. The second message includes a reject network slice selection support information NSSAI information element IE or a first IE, 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 each reject NSSAI domain corresponding to the first slice includes at least one of the information of the first slice and the first instruction information, and / or The second message includes the extended rejection NSSAI IE, and the extended rejection NSSAI The communication method according to claim 3, wherein the IE includes a partially extended reject NSSAI list domain, the partially extended reject NSSAI list domain includes reject NSSAI domains corresponding to each first slice in the at least one first slice, and each reject NSSAI domain corresponding to the first slice includes at least one of the information of the first slice and the first instruction information.

5. The second message includes a reject network slice selection support information NSSAI information element IE or a first IE, 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 each reject NSSAI domain corresponding to the first slice includes at least one of the information of the first slice and the information of the first TA, and / or The second message includes the extended rejection NSSAI IE, and the extended rejection NSSAI The communication method according to claim 1, wherein the IE includes a partially extended reject NSSAI list domain, the partially extended reject NSSAI list domain includes reject NSSAI domains corresponding to each first slice in the at least one first slice, and each reject NSSAI domain corresponding to the first slice includes at least one of the information of the first slice and the information of the first TA.

6. The communication method according to claim 5, wherein each of the first slices corresponding to the reject NSSAI domain includes second instruction information, the second instruction information is used to indicate that the first slice is unavailable within the first TA.

7. The communication method according to claim 3, wherein the second message includes an NSSAI service area list IE, the NSSAI service area list IE includes at least one NSSAI service area list domain, each of the NSSAI service area list domains includes 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 instruction information and third TA information.

8. The second message includes the extended authorization NSSAI IE, and the extended authorization NSSAI The communication method according to claim 1, wherein the IE includes an authorized NSSAI domain corresponding to each of the at least one second slice, and each authorized NSSAI domain corresponding to the 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.

9. The communication method according to any one of claims 1 to 8, wherein the first TA includes a TA that does not support the use of the first slice within a preset time range.

10. The communication method according to claim 9, wherein the second message further includes information of a first timer, the first timer is used to indicate that the terminal can use the first slice in the first TA after the first timer has expired.

11. After the terminal receives the second message transmitted by the network-side device, The communication method according to any one of claims 1 to 8, 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 to indicate whether or not it supports the use of the requested slice within the target tracking area TA.

12. After the terminal receives the second message transmitted by the network-side device, For each of the first TAs or current TAs, the terminal adds information about first slices that the first TA or current TA does not support using to the denied slice list corresponding to the first TA or current TA. For each of the second TAs, the terminal adds information about the second slices that the second TA supports using to the authorized slice list corresponding to the second TA. The terminal stores information about the first slice for each access type and information about the first TA that does not support the use of the first slice. The terminal stores information about the second slice for each access type and information about the second TA that supports the use of the second slice. The communication method according to any one of claims 1 to 8, further comprising at least one of activating a second timer, the second timer being used to indicate that the terminal can use the first slice in the first TA or the current TA after the second timer has expired.

13. If, for any one of the at least one first slices, the first slice is included in the reject slice list corresponding to the sixth TA, then the sixth TA is any one of the one or more first TAs or the current TA, and the terminal is After the aforementioned terminal has shut down and restarted, The aforementioned terminal has moved away from the first TA or the current TA, The terminal is located within the second TA, After the Universal Subscriber Identification Module (USIM) of the aforementioned terminal has been removed, After the subscription data with the network identifier of the current network where the terminal is located has been updated, After the first timer configured by the network-side device expires, The terminal may use the first slice if at least one of the following target conditions is met: the terminal has received the second message and a second timer that starts has expired. The communication method according to any one of claims 1 to 8, 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 the current TA after the timer has expired.

14. If the terminal satisfies at least one of the target conditions, the method The aforementioned terminal, The terminal performs an operation to remove the first slice from the rejected slice list corresponding to the sixth TA, The terminal performs an operation to update the first slice to a slice usable within the sixth TA, The operation further includes the terminal performing at least one of the operations of sending a fourth message to the network-side device, wherein the fourth message is: The communication method according to claim 13, comprising at least one of first target slice information to be used and terminal capability instruction information, wherein the terminal capability instruction information is used to indicate whether the terminal supports the first capability, and the first capability is the ability to receive and use information to indicate whether or not to support the use of the requested slice within the target TA.

15. The aforementioned method, The terminal receives slice information of the first target network configuration transmitted by the network-side device, The communication method according to any one of claims 1 to 8, wherein if the slice information includes second target slice information in a reject slice list corresponding to a fourth TA, the terminal further includes deleting the second target slice information from the reject slice list and stopping the timing of a second timer associated with the second target slice information, wherein the fourth TA is a TA corresponding to the first target network.

16. The aforementioned method, The terminal receives slice information permitted by the second target network transmitted by the network-side device, The communication method according to any one of claims 1 to 8, wherein if the permitted slice information includes third target slice information in a denied slice list corresponding to a fifth TA, the terminal further includes removing the third target slice information from the denied slice list and stopping the timing of a second timer associated with the third target slice information, the fifth TA being a TA corresponding to a second target network.

17. The aforementioned registration request message is: A communication method according to any one of claims 1 to 8, comprising at least one of request slice information and terminal capability instruction information, wherein the terminal capability instruction information is used to indicate whether the terminal supports a first capability, and the first capability is the capability to receive and use information to indicate whether or not to support the use of the request slice within a target TA.

18. A method of communication, The network-side equipment receives a registration request message sent by the terminal, which carries information about the requested slice. The network-side device includes sending a second message to the terminal that carries information to indicate whether or not to support the use of the requested slice within the target tracking area TA. The second message includes information of at least one first slice and information of one or more first TAs corresponding to each first slice in the at least one first slice, wherein the first TA is a TA that does not support the use of the first slice, where the first slice is a slice in the requested slice. Or, A communication method wherein the second message includes information of at least one second slice and information of one or more second TAs corresponding to each second slice in the at least one second slice, the second TA being a TA that supports the use of the second slice, where the second slice is a slice in the request slice.

19. The second message includes a second instruction information, which is used to indicate that the first slice is unavailable within the first TA. Or, The communication method according to claim 18, wherein the second message is further used to indicate that the second slice is available within the second TA.

20. The second message mentioned above is, The system includes at least one of information of at least one first slice and at least one of first instruction information, wherein the first instruction 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 requested slice, and the target tracking area TA includes the current TA, or The second message mentioned above is, The communication method according to claim 18, comprising at least one of information of at least one third slice, information of 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 the use of the third slice or a TA that does not support the use of the third slice, the target TA comprises the third TA, and the third slice is a slice in the requested slice.

21. A communication device, A transmission module for sending a registration request message that carries information about the requested slice to the network-side equipment, Includes a receiving module for receiving a second message transmitted by the network-side equipment that carries information indicating whether or not to support the use of the requested slice within the target tracking area TA, The second message includes information of at least one first slice and information of one or more first TAs corresponding to each first slice in the at least one first slice, wherein the first TA is a TA that does not support the use of the first slice, where the first slice is a slice in the requested slice. Or, The second message includes information of at least one second slice and information of one or more second TAs corresponding to each second slice in the at least one second slice, wherein the second TA is a TA that supports the use of the second slice, where the second slice is a slice in the requested slice, the communication device.

22. A communication device, A receiving module for receiving a registration request message that carries information about the requested slice, sent by a terminal, The terminal includes a transmission module for sending a second message that carries information to indicate whether or not to support the use of the requested slice within the target tracking area TA, The second message includes information of at least one first slice and information of one or more first TAs corresponding to each first slice in the at least one first slice, wherein the first TA is a TA that does not support the use of the first slice, where the first slice is a slice in the requested slice. Or, The second message includes information of at least one second slice and information of one or more second TAs corresponding to each second slice in the at least one second slice, wherein the second TA is a TA that supports the use of the second slice, where the second slice is a slice in the requested slice, the communication device.

23. A terminal comprising a processor and memory, wherein the memory stores a program or instruction that can be run on the processor, and when the program or instruction is executed by the processor, a step of the communication method described in any one of claims 1 to 8 is realized.

24. A network-side device comprising a processor and memory, wherein the memory stores a program or instruction that can be run on the processor, and when the program or instruction is executed by the processor, it realizes a step of the communication method according to any one of claims 18 to 20.

25. A readable storage medium in which a program or instruction is stored, wherein when the program or instruction is executed by a processor, the steps of the communication method described in any one of claims 1 to 8 are realized.

26. A readable storage medium in which a program or instruction is stored, wherein when the program or instruction is executed by a processor, a step of the communication method described in any one of claims 18 to 20 is realized.

Images