Slice request method, terminal and network side device
By including the additional requested network slice selection auxiliary information NSSAI in the registration request message, the terminal can obtain the status of the pending slice in time, solving the problem of network-side device update delay and improving communication efficiency.
Patent Information
- Application Number
- CN202011010275.5
- Authority / Receiving Office
- CN · China
- Patent Type
- Patents(China)
- Current Assignee / Owner
- Filing Date
- 2020-09-23
- Publication Date
- 2024-11-15
- Estimated Expiration
- 2040-09-23
AI Technical Summary
During the network slice authentication and authorization process, the terminal cannot obtain the required slice services in time because the network side devices cannot update the allow and rejection of the pending slices in time, resulting in inefficient communication.
By including the additional requested network slice selection auxiliary information NSSAI in the registration request message, the terminal can request a pending slice from the network side device and receive the registration acceptance message according to the slice status, thereby promptly notifying the acceptance or rejection of the slice after the NSSAA process is completed.
It improves the timeliness of terminal acquisition of required slice services, reduces waiting time, and improves communication efficiency.
Smart Images

Figure CN114302492B_ABST
Abstract
Description
Technical Field
[0001] The present application belongs to the field of communication technology, and specifically relates to a slice request method, terminal and network side equipment. Background Art
[0002] Network slicing (slicing for short) is an important feature in 5G. When a terminal requests the required service, it must provide the requested slice, and the provided slice must also be the slice allowed by the network side device.
[0003] In the related Network Slice-Specific Authentication and Authorization (NSSAA) technology, if the slice requested by the terminal in the first access (3GPP or non-3GPP) is determined by the network side device to belong to pending Network Slice Selection Assistance Information (pending NSSAI) during the NSSAA process, the terminal cannot directly request the slice in the second access (non-3GPP access or 3GPP access). In this way, even after the NSSAA process is completed, the network side device cannot update the permission and rejection of the pending slice to the terminal in time on the second access, resulting in the terminal being unable to obtain the required slice service in time. Summary of the invention
[0004] The embodiments of the present application provide a slice request method, a terminal and a network-side device, which can solve the problem that the terminal cannot obtain the required slice service in time.
[0005] In a first aspect, a slice request method is provided, the method comprising: a network side device receives a first registration request message, the first registration request message includes additional request network slice selection auxiliary information NSSAI, the additional request NSSAI includes a first slice requested by a terminal, the first slice belongs to a first pending NSSAI; and sends a registration acceptance message according to the status of the first slice.
[0006] In a second aspect, a slice request method is provided, the method comprising: a terminal sends a first registration request message, the first registration request message includes an additional request NSSAI, the additional request NSSAI includes a first slice requested by the terminal, the first slice belongs to a first pending NSSAI; the terminal receives a registration acceptance message, the registration acceptance message is sent by a network side device according to the status of the first slice.
[0007] According to a third aspect, a network side device is provided, including: a receiving module for receiving a first registration request message, the first registration request message including additional requested network slice selection auxiliary information NSSAI, the additional requested NSSAI including a first slice requested by a terminal, the first slice belonging to a first pending NSSAI; and a sending module for sending a registration acceptance message according to the status of the first slice.
[0008] In a fourth aspect, a terminal is provided, including: a sending module, used to send a first registration request message, the first registration request message includes an additional request NSSAI, the additional request NSSAI includes a first slice requested by the terminal, and the first slice belongs to a first pending NSSAI; a receiving module, used to receive a registration acceptance message, the registration acceptance message is sent by a network side device according to the status of the first slice.
[0009] In a fifth aspect, a network side device is provided, which includes a processor, a memory, and a program or instruction stored in the memory and executable on the processor, wherein the program or instruction, when executed by the processor, implements the method described in the first aspect.
[0010] In a sixth aspect, a terminal is provided, comprising a processor, a memory, and a program or instruction stored in the memory and executable on the processor, wherein the program or instruction, when executed by the processor, implements the method described in the second aspect.
[0011] In a seventh aspect, a readable storage medium is provided, on which a program or instruction is stored. When the program or instruction is executed by a processor, the method described in the first aspect is implemented, or the method described in the second aspect is implemented.
[0012] In an eighth aspect, a computer program product is provided, which includes a processor, a memory, and a program or instruction stored in the memory and executable on the processor, wherein when the program or instruction is executed by the processor, the method described in the first aspect is implemented, or the method described in the second aspect is implemented.
[0013] In the ninth aspect, a chip is provided, comprising a processor and a communication interface, wherein the communication interface is coupled to the processor, and the processor is used to run a program or instruction to implement the method described in the first aspect, or to implement the method described in the second aspect.
[0014] In an embodiment of the present application, the terminal can request a slice belonging to the pending NSSAI from the network side device through a registration request message, so that the network side device can send a registration reception message to the terminal according to the status of the slice. In an embodiment of the present application, the network side device can know the slice status actually requested by the terminal in a timely manner, so as to notify the terminal of new accepted slices and rejected slices in a timely manner after the NSSAA process is completed, so that the terminal can obtain the required slice service in a timely manner and improve communication efficiency. BRIEF DESCRIPTION OF THE DRAWINGS
[0015] Figure 1 is a block diagram of a wireless communication system according to an embodiment of the present application;
[0016] Figure 2 is a schematic flow chart of a slice request method according to an embodiment of the present application;
[0017] Figure 3 is a schematic flow chart of a slice request method according to another embodiment of the present application;
[0018] Figure 4 is a schematic diagram of the structure of a network side device according to an embodiment of the present application;
[0019] Figure 5 is a schematic structural diagram of a terminal according to another embodiment of the present application;
[0020] Figure 6 is a schematic structural diagram of a communication device according to an embodiment of the present application;
[0021] Figure 7 is a schematic diagram of the structure of a terminal according to an embodiment of the present application;
[0022] Figure 8 It is a schematic diagram of the structure of a network side device according to an embodiment of the present application. DETAILED DESCRIPTION
[0023] The following will be combined with the drawings in the embodiments of the present application to clearly and completely describe the technical solutions in the embodiments of the present application. Obviously, the described embodiments are part of the embodiments of the present application, not all of the embodiments. Based on the embodiments in the present application, all other embodiments obtained by ordinary technicians in this field belong to the scope of protection of this application.
[0024] The terms "first", "second", etc. in the specification and claims of this application are used to distinguish similar objects, and are not used to describe a specific order or sequence. It should be understood that the data used in this way can be interchangeable under appropriate circumstances, so that the embodiments of the present application can be implemented in an order other than those illustrated or described here, and the objects distinguished by "first" and "second" are generally of the same type, and the number of objects is not limited. For example, the first object can be one or more. In addition, "and / or" in the specification and claims represents at least one of the connected objects, and the character " / " generally represents that the objects associated with each other are in an "or" relationship.
[0025] It is worth noting that the technology described in the embodiments of the present application is not limited to the 5G system, the Long Term Evolution (LTE) / LTE-Advanced (LTE-A) system, and can also be used in other wireless communication systems, such as Code Division Multiple Access (CDMA), Time Division Multiple Access (TDMA), Frequency Division Multiple Access (FDMA), Orthogonal Frequency Division Multiple Access (OFDMA), Single-carrier Frequency-Division Multiple Access (SC-FDMA) and other systems. The terms "system" and "network" in the embodiments of the present application are often used interchangeably, and the described technology can be used for the systems and radio technologies mentioned above, as well as for other systems and radio technologies. However, the following description describes a New Radio (NR) system for illustrative purposes, and the NR terminology is used in most of the following descriptions. These technologies can also be applied to applications other than NR system applications, such as the 6th generation (6 th Generation, 6G) communication system.
[0026] Figure 1A block diagram of a wireless communication system applicable to an embodiment of the present application is shown. The wireless communication system includes a terminal 11 and a network side device 12. Among them, the terminal 11 can also be called a terminal device or a user terminal (User Equipment, UE), and the terminal 11 can be a mobile phone, a tablet computer (Tablet Personal Computer), a laptop computer (Laptop Computer) or a notebook computer, a personal digital assistant (Personal Digital Assistant, PDA), a handheld computer, a netbook, an ultra-mobile personal computer (ultra-mobile personal computer, UMPC), a mobile Internet device (Mobile Internet Device, MID), a wearable device (Wearable Device) or a vehicle-mounted device (VUE), a pedestrian terminal (PUE) and other terminal side devices, and the wearable device includes: a bracelet, a headset, glasses, etc. It should be noted that the specific type of the terminal 11 is not limited in the embodiment of the present application. The network side device 12 can be a base station or a core network, wherein the base station can be referred to as a node B, an evolved node B, an access point, a base transceiver station (Base Transceiver Station, BTS), a radio base station, a radio transceiver, a basic service set (Basic Service Set, BSS), an extended service set (Extended Service Set, ESS), a B node, an evolved B node (eNB), a next generation node B (gNB), a home B node, a home evolved B node, a WLAN access point, a WiFi node, a transmitting and receiving point (Transmitting Receiving Point, TRP) or some other suitable term in the field. As long as the same technical effect is achieved, the base station is not limited to a specific technical vocabulary. It should be noted that in the embodiment of the present application, only the base station in the NR system is taken as an example, but the specific type of the base station is not limited.
[0027] The following, in combination with the accompanying drawings, describes in detail the slice request method, terminal and network side equipment provided in the embodiments of the present application through specific embodiments and their application scenarios.
[0028] like Figure 2 As shown, an embodiment of the present application provides a slice request method 200, which can be executed by a network side device. In other words, the method can be executed by software or hardware installed on the network side device. The method includes the following steps.
[0029] S202: The network side device receives a first registration request message (REGISTRATION REQUEST message), and the first registration request message includes additional request (additional requested) network slice selection assistance information (Network Slice Selection Assistance Information, NSSAI), and the additional request NSSAI includes a first slice requested by the terminal, and the first slice belongs to a first pending NSSAI (pending NSSAI).
[0030] The network side device mentioned in each embodiment of this specification may be an access and mobility management function (AMF) entity, etc.
[0031] Optionally, in an example, the first registration request message may further include a requested NSSAI (RequestedNSSAI), where the requested NSSAI includes a second slice requested by the terminal, and the second slice does not belong to the first pending NSSAI.
[0032] It can be understood that requesting NSSAI may be an optional option. In other examples, the first registration request message may also include only the additional requesting NSSAI but not the requesting NSSAI.
[0033] It should be noted that, in order to distinguish it from "requested NSSAI", the embodiment of the present application uses "additional requested NSSAI" to describe the NSSAI including the first slice (i.e., the slice belonging to the pending NSSAI). In fact, other similar technical terms can also be used to describe "additional requested NSSAI", for example, evolved NSSAI, newly added NSSAI, etc., which is not limited in the embodiment of the present application.
[0034] S204: The network side device sends a registration acceptance message according to the status of the first slice.
[0035] In this step, the status of the first slice may include at least one of the following: the Network Slice-Specific Authentication and Authorization (NSSAA) result of the first slice, whether the first slice is accepted by the network side device. Among them, the NSSAA result of the first slice includes the success of the NSSAA of the first slice, or the failure of the NSSAA of the first slice. In this embodiment, the network side device can also comprehensively consider the user's contract, the function of the network side device and the local policy to decide whether to accept the first slice requested by the terminal, for example, the network side device accepts the first slice, and the network side device does not accept the first slice.
[0036] In the slice request method provided in the embodiment of the present application, the terminal can request the slice belonging to the pending NSSAI from the network side device through a registration request message, so that the network side device can send a registration reception message to the terminal according to the status of the slice. In the embodiment of the present application, the network side device can know the slice status actually requested by the terminal in a timely manner, so as to notify the terminal of new accepted slices and rejected slices in a timely manner after the NSSAA process is completed, so that the terminal can obtain the required slice service in a timely manner and improve communication efficiency.
[0037] Optionally, the network side device mentioned in embodiment 200 sends a registration acceptance message according to the state of the first slice, including one of the following:
[0038] 1) If the NSSAA of the first slice succeeds and the first slice is accepted by the network side device, a first registration acceptance message is sent, where the first registration acceptance message includes a first allowed NSSAI (allowed NSSAI), where the first allowed NSSAI includes the first slice;
[0039] 2) If the NSSAA of the first slice fails and / or the first slice is not accepted by the network side device, sending a second registration acceptance message, where the second registration acceptance message includes a first rejected NSSAI (rejected NSSAI), where the first rejected NSSAI includes the first slice;
[0040] 3) If NSSAA of the first slice is in progress or is to be performed, a third registration acceptance message is sent, where the third registration acceptance message includes a second pending NSSAI, where the second pending NSSAI includes the first slice.
[0041] On the basis of the above 3), that is, when the first slice NSSAA is in progress or is about to be performed, the aforementioned embodiment may also include the following steps: when the first slice NSSAA is completed, the network side device initiates a generic terminal configuration update procedure (Generic UE Configuration Update procedure, referred to as generic UCU procedure), and provides the updated allowed NSSAI and / or rejected NSSAI in the configuration update command message.
[0042] In a specific example, the above-mentioned provision of the updated allowed NSSAI and / or rejected NSSAI in the configuration update command message includes at least one of the following:
[0043] 1) If the NSSAA of the first slice succeeds and the first slice is accepted by the network side device, sending a first configuration update command message, where the first configuration update command message includes a second allowed NSSAI, and the second allowed NSSAI includes the first slice;
[0044] 2) If the NSSAA of the first slice fails and / or the first slice is not accepted by the network side device, a second configuration update command message is sent, wherein the second configuration update command message includes a second rejected NSSAI, and the second rejected NSSAI includes the first slice.
[0045] Optionally, the initiating the general UCU process mentioned in the foregoing embodiments includes: initiating the general UCU process on a 3rd Generation Partnership Project (3GPP) access or a non-3GPP access.
[0046] The initiation of the general UCU process mentioned in the above embodiments includes: when the first slice is included in the request NSSAI or the additional request NSSAI provided during the last registration process of the terminal, the general UCU process is initiated. In this example, the criterion for the network side device to select whether to initiate the general UCU process on a certain access (i.e., 3GPP access or non-3GPP access) is: the request NSSAI or the additional request NSSAI provided by the terminal during the last registration process on a certain access contains the first slice. For example, if the request NSSAI or the additional request NSSAI provided by the terminal during the last registration process on the 3GPP access contains the first slice, then the network side device chooses to initiate the general UCU process on the 3GPP access.
[0047] Optionally, in parallel with the previous embodiments, the network side device may also receive a second registration request message, the second registration request message including a requested NSSAI, the requested NSSAI including a second slice requested by the terminal; wherein the second registration request message is sent by the terminal when there is no first pending NSSAI, or when the second slice does not belong to the first pending NSSAI.
[0048] To explain in detail the slice request method provided in the embodiments of the present application, several specific embodiments will be described below.
[0049] Embodiment 1
[0050] In this embodiment, the terminal (UE) registers to the same network side device through 3GPP access and non-3GPP access. Assuming that the UE requests slice a on 3GPP access, the network side device needs to perform NSSAA for slice a and return the pending NSSAI containing slice a to the UE. At this time, the UE obtains the pending NSSAI. In this embodiment, on 3GPP access and non-3GPP access, the pending NSSAI of the terminal is shared, while the allowed NSSAI is independent of each other.
[0051] When the UE registers to the same network side device in non-3GPP access, the UE wants to obtain the service of slice a, but slice a is a pending slice (i.e., slice a belongs to pending NSSAI). According to the existing technical regulations, the UE cannot request slice a (the slice a corresponds to the first slice in the previous embodiment) on non-3GPP access. Even if the NSSAA process of slice a of the network side device is successful, the network side device will only update the allowed NSSAI containing slice a on 3GPP access, and will not update the allowed NSSAI on non-3GPP (because the UE has not requested slice a on non-3GPP access before). If the UE wants to obtain the service of slice a on non-3GPP, the UE must initiate the registration process on non-3GPP access again, request slice a, and wait until the network side device returns the allowed NSSAI containing slice a on non-3GPP before the UE can obtain the service on slice a, which will greatly increase the waiting time of the terminal.
[0052] To solve the above technical problems, in an embodiment of the present application, when the UE registers to the same network side device in non-3GPP access, it sends a registration request message to the network side device, and the registration request message includes an additional request NSSAI, and the additional request NSSAI includes slice a requested by the terminal, and slice a belongs to pending NSSAI. In this way, the network side device can send a registration reception message to the terminal according to the status of slice a, and the network side device can know the slice status actually requested by the terminal in time, so as to notify the terminal of new accepted slices and rejected slices in time after the NSSAA process is completed, so that the terminal can obtain the required slice service in time, reduce the waiting time of the terminal, and improve communication efficiency.
[0053] Embodiment 2
[0054] This embodiment adds a new information element to the content of the registration request message, namely, an additional request NSSAI, see Table 1 for details, wherein the registration request message is sent by the terminal and received by the network side device, which may be the AMF.
[0055] It should be noted that the registration request message content may also include additional request NSSAI and other information elements besides the request NSSAI, which are not shown in Table 1 and are indicated by ellipsis.
[0056] Table 1 Registration request message content
[0057]
[0058] There is no limitation on the IEI value of the above additional request NSSAI, which is represented by "xx" in Table 1.
[0059] In an embodiment of the present application, the network side device can promptly know the slice status actually requested by the terminal, so as to promptly notify the terminal of new accepted slices and rejected slices after the NSSAA process is completed, so that the terminal can obtain the required slice service in time, reducing the waiting time of the terminal and improving communication efficiency.
[0060] Embodiment 3
[0061] This embodiment describes the behavior on the UE side: if the UE wants to request a slice during the registration process, there are three situations:
[0062] 1. If there is no pending NSSAI or the slice that the UE wants to request is not in the pending NSSAI, the UE only carries the requested NSSAI in the registration request message, which includes the slice that it wants to register.
[0063] 2. If some slices that the UE wants to request (corresponding to the first slice or slice a in the previous embodiment) are in the pending NSSAI, and some other slices that the UE wants to request (corresponding to the second slice in the previous embodiment) are not in the pending NSSAI, the UE provides both the requested NSSAI and the additional requested NSSAI in the registration request message. The requested NSSAI includes the slices that the UE wants to request and are not in the pending NSSAI; the additional requested NSSAI includes the slices that the UE wants to request and are in the pending NSSAI.
[0064] 3. If some of the slices that the UE wants to request (corresponding to the first slice or slice a in the previous embodiment) are in the pending NSSAI, the UE provides an additional requested NSSAI in the registration request, and the additional requested NSSAI includes the slices that the UE wants to request and are in the pending NSSAI.
[0065] In an embodiment of the present application, the network side device can promptly know the slice status actually requested by the terminal, so as to promptly notify the terminal of new accepted slices and rejected slices after the NSSAA process is completed, so that the terminal can obtain the required slice service in time, reducing the waiting time of the terminal and improving communication efficiency.
[0066] Embodiment 4
[0067] This embodiment describes the behavior of the network-side device during the registration process:
[0068] 1. During the registration process of the UE, the network side device receives a registration request message including an additional requested NSSAI information element; wherein the additional requested NSSAI includes slice a, and slice a belongs to the pending NSSAI of the terminal.
[0069] 2. In the UE context of the network side device, the status of slice a is:
[0070] a) If NSSAA succeeds and the network accepts the UE's request for slice a, the network puts slice a into the allowed NSSAI in the registration acceptance message and returns it to the UE.
[0071] b) If NSSAA fails and / or the network side device does not accept slice a, the network side device puts slice a into rejected NSSAI in the registration acceptance message and returns it to the UE.
[0072] c) If NSSAA is in progress or is about to be carried out, the network side device puts slice a into pending NSSAI in the registration acceptance message and returns it to the UE.
[0073] In an embodiment of the present application, the network side device can promptly know the slice status actually requested by the terminal, so as to promptly notify the terminal of new accepted slices and rejected slices after the NSSAA process is completed, so that the terminal can obtain the required slice service in time, reducing the waiting time of the terminal and improving communication efficiency.
[0074] Embodiment 5
[0075] This embodiment introduces the behavior of the network side device after the registration process, which belongs to the subsequent steps of c) of the fourth embodiment: if the NSSAA process of slice a is completed, the network side device chooses to initiate a general UCU process on 3GPP access or non-3GPP access, and sends the updated allowed NSSAI or rejected NSSAI to the UE. The specific steps are as follows:
[0076] 1) If the NSSAA of slice a succeeds and the network device accepts slice a, the network device puts slice a into the allowed NSSAI in the configuration update command message and returns it to the UE;
[0077] 2) If the NSSAA of slice a fails or the network does not accept slice a, the network side device puts slice a into rejected NSSAI in the configuration update command message and returns it to the UE;
[0078] Optionally, the criterion / basis for the network-side device to select whether to initiate a UCU update process on a certain access (3GPP access or non-3GPP access) is that the requested NSSAI or additional NSSAI provided by the UE during the last registration process on the access contains slice a.
[0079] In an embodiment of the present application, the network side device can promptly know the slice status actually requested by the terminal, so as to promptly notify the terminal of new accepted slices and rejected slices after the NSSAA process is completed, so that the terminal can obtain the required slice service in time, reducing the waiting time of the terminal and improving communication efficiency.
[0080] Combination of the above Figure 2 The slice request method according to the embodiment of the present application is described in detail. Figure 3 A slice request method according to another embodiment of the present application is described in detail. It can be understood that the interaction between the network side device and the terminal described by the terminal is similar to Figure 2The descriptions of the network-side devices in the methods shown are the same, and to avoid repetition, the relevant descriptions are appropriately omitted.
[0081] Figure 3 This is a schematic diagram of the implementation flow of the slice request method of the embodiment of the present application, which can be applied to the terminal. Figure 3 As shown, the method 300 includes:
[0082] S302: The terminal sends a first registration request message, where the first registration request message includes an additional request NSSAI, where the additional request NSSAI includes a first slice requested by the terminal, where the first slice belongs to a first pending NSSAI.
[0083] S304: The terminal receives a registration acceptance message, which is sent by the network side device according to the status of the first slice.
[0084] In an embodiment of the present application, the terminal can request a slice belonging to the pending NSSAI from the network side device through a registration request message, so that the network side device can send a registration reception message to the terminal according to the status of the slice. In an embodiment of the present application, the network side device can know the slice status actually requested by the terminal in a timely manner, so as to notify the terminal of new accepted slices and rejected slices in a timely manner after the NSSAA process is completed, so that the terminal can obtain the required slice service in a timely manner and improve communication efficiency.
[0085] Optionally, as an embodiment, the receiving a registration acceptance message includes one of the following:
[0086] receiving a first registration acceptance message, the first registration acceptance message including a first allowed NSSAI, the first allowed NSSAI including the first slice, wherein the NSSAA of the first slice is successful, and the first slice is accepted by the network side device;
[0087] receiving a second registration acceptance message, where the second registration acceptance message includes the first rejected NSSAI, where the first rejected NSSAI includes the first slice, where the first slice NSSAA fails and / or the first slice is not accepted by the network side device;
[0088] A third registration acceptance message is received, wherein the third registration acceptance message includes a second pending NSSAI, wherein the second pending NSSAI includes the first slice, wherein the first slice NSSAI is being performed or is to be performed.
[0089] Optionally, as an embodiment, when NSSAA of the first slice is being performed or is about to be performed, the method further includes:
[0090] The terminal receives a configuration update command message, which includes the updated allowed NSSAI and / or rejected NSSAI, wherein the network side device is also used to initiate a general UCU process when the NSSAA of the first slice is completed.
[0091] Optionally, as an embodiment, the receiving a configuration update command message includes at least one of the following:
[0092] receiving a first configuration update command message, the first configuration update command message including a second allowed NSSAI, the second allowed NSSAI including the first slice, wherein the NSSAA of the first slice succeeds and the first slice is accepted by the network side device;
[0093] Receive a second configuration update command message, wherein the second configuration update command message includes a second rejected NSSAI, wherein the second rejected NSSAI includes the first slice, wherein the NSSAA of the first slice fails and / or the first slice is not accepted by the network side device.
[0094] Optionally, as an embodiment, the first registration request message also includes a requested NSSAI, the requested NSSAI includes a second slice requested by the terminal, and the second slice does not belong to the first pending NSSAI.
[0095] Optionally, as an embodiment, the method further includes:
[0096] The terminal sends a second registration request message, where the second registration request message includes a request NSSAI, and the request NSSAI includes a second slice requested by the terminal;
[0097] The second registration request message is sent by the terminal when there is no first pending NSSAI, or when the second slice does not belong to the first pending NSSAI.
[0098] It should be noted that the slice request method provided in the embodiment of the present application can be executed by a network side device, or a control module in the network side device for executing the slice request method. In the embodiment of the present application, the slice request device provided in the embodiment of the present application is explained by taking the execution of the slice request method by a network side device as an example.
[0099] Figure 4 Schematic diagram of the structure of the network side device according to the embodiment of the present application. Figure 4 As shown, the network side device 400 includes:
[0100] The receiving module 402 can be used to receive a first registration request message, where the first registration request message includes additional requested network slice selection auxiliary information NSSAI, where the additional requested NSSAI includes a first slice requested by the terminal, and the first slice belongs to a first pending NSSAI.
[0101] The sending module 404 can be used to send a registration acceptance message according to the status of the first slice.
[0102] In an embodiment of the present application, the terminal can request a slice belonging to the pending NSSAI from the network side device through a registration request message, so that the network side device can send a registration reception message to the terminal according to the status of the slice. In an embodiment of the present application, the network side device can know the slice status actually requested by the terminal in a timely manner, so as to notify the terminal of new accepted slices and rejected slices in a timely manner after the NSSAA process is completed, so that the terminal can obtain the required slice service in a timely manner and improve communication efficiency.
[0103] Optionally, as an embodiment, the sending module 404 may be used for one of the following:
[0104] If the first slice network slice authentication and authorization NSSAA succeeds, and the first slice is accepted by the network side device, a first registration acceptance message is sent, where the first registration acceptance message includes a first allowed NSSAI, and the first allowed NSSAI includes the first slice;
[0105] If the NSSAA of the first slice fails and / or the first slice is not accepted by the network side device, sending a second registration acceptance message, where the second registration acceptance message includes the first rejected NSSAI, and the first rejected NSSAI includes the first slice;
[0106] If NSSAA of the first slice is being performed or is to be performed, a third registration acceptance message is sent, where the third registration acceptance message includes a second pending NSSAI, where the second pending NSSAI includes the first slice.
[0107] Optionally, as an embodiment, when the first slice NSSAA is in progress or is about to be performed, the sending module 404 can also be used to: when the first slice NSSAA is completed, initiate a universal terminal configuration update UCU process, and provide the updated allowed NSSAI and / or rejected NSSAI in the configuration update command message.
[0108] Optionally, as an embodiment, the sending module 404 may also be used for at least one of the following:
[0109] If the NSSAA of the first slice succeeds and the first slice is accepted by the network side device, sending a first configuration update command message, where the first configuration update command message includes a second allowed NSSAI, and the second allowed NSSAI includes the first slice;
[0110] If the NSSAA of the first slice fails and / or the first slice is not accepted by the network side device, a second configuration update command message is sent, wherein the second configuration update command message includes a second rejected NSSAI, and the second rejected NSSAI includes the first slice.
[0111] Optionally, as an embodiment, the sending module 404 is configured to: initiate a universal UCU process on a 3rd Generation Partnership Project 3GPP access or a non-3GPP access.
[0112] Optionally, as an embodiment, the initiating the general UCU process includes: initiating the general UCU process when the requested NSSAI or the additional requested NSSAI provided during the last registration process of the terminal contains the first slice.
[0113] Optionally, as an embodiment, the first registration request message also includes a requested NSSAI, the requested NSSAI includes a second slice requested by the terminal, and the second slice does not belong to the first pending NSSAI.
[0114] Optionally, as an embodiment, the receiving module 402 can also be used to: receive a second registration request message, the second registration request message includes a requested NSSAI, and the requested NSSAI includes a second slice requested by the terminal; wherein the second registration request message is sent by the terminal when there is no first pending NSSAI, or when the second slice does not belong to the first pending NSSAI.
[0115] According to the embodiment of the present application, the network side device 400 can refer to the process of the method 200 corresponding to the embodiment of the present application, and the various units / modules in the network side device 400 and the above-mentioned other operations and / or functions are respectively for implementing the corresponding processes in the method 200, and can achieve the same or equivalent technical effects. For the sake of brevity, they will not be repeated here.
[0116] The terminal in the embodiment of the present application may be a device, or a component, integrated circuit, or chip in the terminal. The device may be a mobile terminal or a non-mobile terminal. For example, the mobile terminal may include but is not limited to the types of terminal 11 listed above, and the non-mobile terminal may be a server, a network attached storage (Network Attached Storage, NAS), a personal computer (personal computer, PC), a television (television, TV), a teller machine or a self-service machine, etc., which is not specifically limited in the embodiment of the present application.
[0117] The terminal in the embodiment of the present application may be a device having an operating system. The operating system may be an Android operating system, an iOS operating system, or other possible operating systems, which are not specifically limited in the embodiment of the present application.
[0118] The terminal provided in the embodiment of the present application can achieve Figure 3 The various processes implemented by the method embodiment and achieving the same technical effect are not described here to avoid repetition.
[0119] Figure 5 is a schematic diagram of the structure of a terminal according to an embodiment of the present application, such as Figure 5 As shown, the terminal 500 includes:
[0120] The sending module 502 can be used to send a first registration request message, where the first registration request message includes an additional request NSSAI, where the additional request NSSAI includes a first slice requested by the terminal, and the first slice belongs to a first pending NSSAI.
[0121] The receiving module 504 can be used to receive a registration acceptance message, which is sent by the network side device according to the status of the first slice.
[0122] In an embodiment of the present application, the terminal can request a slice belonging to the pending NSSAI from the network side device through a registration request message, so that the network side device can send a registration reception message to the terminal according to the status of the slice. In an embodiment of the present application, the network side device can know the slice status actually requested by the terminal in a timely manner, so as to notify the terminal of new accepted slices and rejected slices in a timely manner after the NSSAA process is completed, so that the terminal can obtain the required slice service in a timely manner and improve communication efficiency.
[0123] Optionally, as an embodiment, the receiving module 504 may be used for one of the following:
[0124] receiving a first registration acceptance message, the first registration acceptance message including a first allowed NSSAI, the first allowed NSSAI including the first slice, wherein the NSSAA of the first slice is successful, and the first slice is accepted by the network side device;
[0125] receiving a second registration acceptance message, where the second registration acceptance message includes the first rejected NSSAI, where the first rejected NSSAI includes the first slice, where the first slice NSSAA fails and / or the first slice is not accepted by the network side device;
[0126] A third registration acceptance message is received, wherein the third registration acceptance message includes a second pending NSSAI, wherein the second pending NSSAI includes the first slice, wherein the first slice NSSAI is being performed or is to be performed.
[0127] Optionally, as an embodiment, when NSSAA of the first slice is being performed or is about to be performed, the receiving module 504 can also be used to: receive a configuration update command message, the configuration update command message including the updated allowed NSSAI and / or rejected NSSAI, wherein the network side device is also used to initiate a general UCU process when NSSAA of the first slice is completed.
[0128] Optionally, as an embodiment, the receiving module 504 can be used for at least one of the following: receiving a first configuration update command message, the first configuration update command message including a second allowed NSSAI, the second allowed NSSAI including the first slice, wherein the NSSAA of the first slice is successful and the first slice is accepted by the network side device; receiving a second configuration update command message, the second configuration update command message including a second rejected NSSAI, the second rejected NSSAI including the first slice, wherein the NSSAA of the first slice fails and / or the first slice is not accepted by the network side device.
[0129] Optionally, as an embodiment, the first registration request message also includes a requested NSSAI, the requested NSSAI includes a second slice requested by the terminal, and the second slice does not belong to the first pending NSSAI.
[0130] Optionally, as an embodiment, the sending module 502 can also be used to: send a second registration request message, the second registration request message includes a requested NSSAI, and the requested NSSAI includes a second slice requested by the terminal; wherein the second registration request message is sent by the terminal when there is no first pending NSSAI, or when the second slice does not belong to the first pending NSSAI.
[0131] According to the terminal 500 of the embodiment of the present application, the process of the method 300 corresponding to the embodiment of the present application can be referred to, and the various units / modules in the terminal 500 and the above-mentioned other operations and / or functions are respectively for implementing the corresponding processes in the method 300, and can achieve the same or equivalent technical effects. For the sake of brevity, they will not be repeated here.
[0132] Optional, such as Figure 6 As shown, the embodiment of the present application also provides a communication device 600, including a processor 601, a memory 602, and a program or instruction stored in the memory 602 and executable on the processor 601. For example, when the communication device 600 is a terminal, the program or instruction is executed by the processor 601 to implement the various processes of the above-mentioned slice request method embodiment, and can achieve the same technical effect. When the communication device 600 is a network side device, the program or instruction is executed by the processor 601 to implement the various processes of the above-mentioned slice request method embodiment, and can achieve the same technical effect. To avoid repetition, it will not be repeated here.
[0133] Figure 7 A schematic diagram of the hardware structure of a terminal for implementing an embodiment of the present application.
[0134] The terminal 700 includes but is not limited to: a radio frequency unit 701, a network module 702, an audio output unit 703, an input unit 704, a sensor 705, a display unit 706, a user input unit 707, an interface unit 708, a memory 709, and a processor 710.
[0135] Those skilled in the art will appreciate that the terminal 700 may also include a power source (such as a battery) for supplying power to various components, and the power source may be logically connected to the processor 710 through a power management system, thereby implementing functions such as managing charging, discharging, and power consumption management through the power management system. Figure 7 The terminal structure shown in the figure does not constitute a limitation on the terminal. The terminal may include more or fewer components than shown in the figure, or combine certain components, or arrange the components differently, which will not be described in detail here.
[0136] It should be understood that in the embodiment of the present application, the input unit 704 may include a graphics processor (Graphics Processing Unit, GPU) 7041 and a microphone 7042, and the graphics processor 7041 processes the image data of the static picture or video obtained by the image capture device (such as a camera) in the video capture mode or the image capture mode. The display unit 706 may include a display panel 7061, and the display panel 7061 may be configured in the form of a liquid crystal display, an organic light emitting diode, etc. The user input unit 707 includes a touch panel 7071 and other input devices 7072. The touch panel 7071 is also called a touch screen. The touch panel 7071 may include two parts: a touch detection device and a touch controller. Other input devices 7072 may include, but are not limited to, a physical keyboard, function keys (such as volume control keys, switch keys, etc.), a trackball, a mouse, and a joystick, which will not be repeated here.
[0137] In the embodiment of the present application, the radio frequency unit 701 receives downlink data from the network side device and sends it to the processor 710 for processing; in addition, the uplink data is sent to the network side device. Generally, the radio frequency unit 701 includes but is not limited to an antenna, at least one amplifier, a transceiver, a coupler, a low noise amplifier, a duplexer, etc.
[0138] The memory 709 can be used to store software programs or instructions and various data. The memory 709 can mainly include a program or instruction storage area and a data storage area, wherein the program or instruction storage area can store an operating system, an application program or instruction required for at least one function (such as a sound playback function, an image playback function, etc.), etc. In addition, the memory 709 can include a high-speed random access memory, and can also include a non-volatile memory, wherein the non-volatile memory can be a read-only memory (Read-Only Memory, ROM), a programmable read-only memory (Programmable ROM, PROM), an erasable programmable read-only memory (Erasable PROM, EPROM), an electrically erasable programmable read-only memory (Electrically EPROM, EEPROM) or a flash memory. For example, at least one disk storage device, a flash memory device, or other non-volatile solid-state storage devices.
[0139] The processor 710 may include one or more processing units; optionally, the processor 710 may integrate an application processor and a modem processor, wherein the application processor mainly processes an operating system, a user interface, and application programs or instructions, etc., and the modem processor mainly processes wireless communications, such as a baseband processor. It is understandable that the modem processor may not be integrated into the processor 710.
[0140] Among them, the radio frequency unit 701 is used to send a first registration request message, the first registration request message includes an additional request NSSAI, the additional request NSSAI includes the first slice requested by the terminal, and the first slice belongs to the first pending NSSAI; and receive a registration acceptance message, which is sent by the network side device according to the status of the first slice.
[0141] In an embodiment of the present application, the terminal can request a slice belonging to the pending NSSAI from the network side device through a registration request message, so that the network side device can send a registration reception message to the terminal according to the status of the slice. In an embodiment of the present application, the network side device can know the slice status actually requested by the terminal in a timely manner, so as to notify the terminal of new accepted slices and rejected slices in a timely manner after the NSSAA process is completed, so that the terminal can obtain the required slice service in a timely manner and improve communication efficiency.
[0142] The terminal 700 provided in the embodiment of the present application can also implement the various processes of the above-mentioned slice request method embodiment and can achieve the same technical effect. To avoid repetition, it will not be repeated here.
[0143] Specifically, the embodiment of the present application also provides a network side device. Figure 8 As shown, the network device 800 includes: an antenna 81, a radio frequency device 82, and a baseband device 83. The antenna 81 is connected to the radio frequency device 82. In the uplink direction, the radio frequency device 82 receives information through the antenna 81 and sends the received information to the baseband device 83 for processing. In the downlink direction, the baseband device 83 processes the information to be sent and sends it to the radio frequency device 82. The radio frequency device 82 processes the received information and sends it out through the antenna 81.
[0144] The frequency band processing device may be located in the baseband device 83 . The method executed by the network-side device in the above embodiment may be implemented in the baseband device 83 . The baseband device 83 includes a processor 84 and a memory 85 .
[0145] The baseband device 83 may include, for example, at least one baseband board on which a plurality of chips are arranged. Figure 8 As shown, one of the chips is, for example, a processor 84, which is connected to a memory 85 to call a program in the memory 85 to execute the network device operations shown in the above method embodiment.
[0146] The baseband device 83 may further include a network interface 86 for exchanging information with the radio frequency device 82 , and the interface may be, for example, a common public radio interface (CPRI for short).
[0147] Specifically, the network side device of the embodiment of the present invention further includes: an instruction or program stored in the memory 85 and executable on the processor 84, and the processor 84 calls the instruction or program in the memory 85 to execute Figure 4 The methods executed by the modules shown achieve the same technical effects, and therefore will not be described here in detail to avoid repetition.
[0148] An embodiment of the present application also provides a readable storage medium, on which a program or instruction is stored. When the program or instruction is executed by a processor, the various processes of the above-mentioned slice request method embodiment are implemented and the same technical effect can be achieved. To avoid repetition, it will not be repeated here.
[0149] The processor may be a processor in the terminal described in the above embodiment. The readable storage medium includes a computer readable storage medium, such as a computer read-only memory (ROM), a random access memory (RAM), a magnetic disk or an optical disk.
[0150] An embodiment of the present application further provides a chip, which includes a processor and a communication interface, wherein the communication interface is coupled to the processor, and the processor is used to run programs or instructions to implement the various processes of the above-mentioned slice request method embodiment, and can achieve the same technical effect. To avoid repetition, it will not be repeated here.
[0151] It should be understood that the chip mentioned in the embodiments of the present application can also be called a system-level chip, a system chip, a chip system or a system-on-chip chip, etc.
[0152] It should be noted that, in this article, the terms "comprise", "include" or any other variant thereof are intended to cover non-exclusive inclusion, so that the process, method, article or device including a series of elements includes not only those elements, but also includes other elements not explicitly listed, or also includes elements inherent to such process, method, article or device. In the absence of further restrictions, the elements defined by the sentence "comprise one..." do not exclude the presence of other identical elements in the process, method, article or device including the element. In addition, it should be pointed out that the scope of the methods and devices in the embodiments of the present application is not limited to performing functions in the order shown or discussed, and may also include performing functions in a substantially simultaneous manner or in reverse order according to the functions involved, for example, the described method may be performed in an order different from that described, and various steps may also be added, omitted, or combined. In addition, the features described with reference to certain examples may be combined in other examples.
[0153] Through the description of the above implementation methods, those skilled in the art can clearly understand that the above-mentioned embodiment methods can be implemented by means of software plus a necessary general hardware platform, and of course by hardware, but in many cases the former is a better implementation method. Based on such an understanding, the technical solution of the present application, or the part that contributes to the prior art, can be embodied in the form of a software product, which is stored in a storage medium (such as ROM / RAM, a magnetic disk, or an optical disk), and includes a number of instructions for a terminal (which can be a mobile phone, a computer, a server, an air conditioner, or a network device, etc.) to execute the methods described in each embodiment of the present application.
[0154] The embodiments of the present application are described above in conjunction with the accompanying drawings, but the present application is not limited to the above-mentioned specific implementation methods. The above-mentioned specific implementation methods are merely illustrative and not restrictive. Under the guidance of the present application, ordinary technicians in this field can also make many forms without departing from the purpose of the present application and the scope of protection of the claims, all of which are within the protection of the present application.
Claims
1. A slice request method, characterized in that: The method comprises: The network side device receives a first registration request message, where the first registration request message includes additional requested network slice selection auxiliary information NSSAI, where the additional requested NSSAI includes a first slice requested by the terminal, where the first slice belongs to a first pending NSSAI; Sending a registration acceptance message according to the state of the first slice; In a case where NSSAA of the first slice is being performed or is to be performed, the method further includes: In the case where the NSSAA of the first slice is completed, a universal terminal configuration update UCU process is initiated, and the updated allowed NSSAI and / or rejected NSSAI are provided in the configuration update command message; The process of initiating a universal UCU includes: When the requested NSSAI or the additional requested NSSAI provided by the terminal during the last registration process of 3GPP access or non-3GPP access includes the first slice, a general UCU process is initiated on the access corresponding to the last registration process.
2. The method according to claim 1, characterized in that: The sending of the registration acceptance message according to the state of the first slice includes one of the following: If the first slice network slice authentication and authorization NSSAA succeeds, and the first slice is accepted by the network side device, a first registration acceptance message is sent, where the first registration acceptance message includes a first allowed NSSAI, and the first allowed NSSAI includes the first slice; If the NSSAA of the first slice fails and / or the first slice is not accepted by the network side device, sending a second registration acceptance message, where the second registration acceptance message includes the first rejected NSSAI, and the first rejected NSSAI includes the first slice; If NSSAA of the first slice is being performed or is to be performed, a third registration acceptance message is sent, where the third registration acceptance message includes a second pending NSSAI, where the second pending NSSAI includes the first slice.
3. The method according to claim 1, characterized in that The providing of the updated allowed NSSAI and / or rejected NSSAI in the configuration update command message includes at least one of the following: If the NSSAA of the first slice succeeds and the first slice is accepted by the network side device, sending a first configuration update command message, where the first configuration update command message includes a second allowed NSSAI, and the second allowed NSSAI includes the first slice; If the NSSAA of the first slice fails and / or the first slice is not accepted by the network side device, a second configuration update command message is sent, wherein the second configuration update command message includes a second rejected NSSAI, and the second rejected NSSAI includes the first slice.
4. The method according to claim 1, characterized in that: The process of initiating a universal UCU includes: Generic UCU procedures are initiated on 3rd Generation Partnership Project 3GPP access or non-3GPP access.
5. The method according to claim 1, characterized in that The first registration request message also includes a requested NSSAI, where the requested NSSAI includes a second slice requested by the terminal, and the second slice does not belong to the first pending NSSAI.
6. The method according to claim 1, characterized in that The method further comprises: The network side device receives a second registration request message, where the second registration request message includes a request NSSAI, where the request NSSAI includes a second slice requested by the terminal; The second registration request message is sent by the terminal when there is no first pending NSSAI, or when the second slice does not belong to the first pending NSSAI.
7. A slice request method, characterized in that: The method comprises: The terminal sends a first registration request message, where the first registration request message includes an additional request NSSAI, where the additional request NSSAI includes a first slice requested by the terminal, where the first slice belongs to a first pending NSSAI; The terminal receives a registration acceptance message, where the registration acceptance message is sent by a network side device according to a state of the first slice; In a case where NSSAA of the first slice is being performed or is to be performed, the method further includes: The terminal receives a configuration update command message, wherein the configuration update command message includes an updated allowed NSSAI and / or a rejected NSSAI, wherein the network side device is further configured to complete the NSSAA of the first slice , And in the case where the first slice is included in the requested NSSAI or the additional requested NSSAI provided by the terminal during the last registration process of 3GPP access or non-3GPP access, a general UCU process is initiated on the access corresponding to the last registration process of the terminal.
8. The method according to claim 7, characterized in that The receiving of the registration acceptance message includes one of the following: receiving a first registration acceptance message, the first registration acceptance message including a first allowed NSSAI, the first allowed NSSAI including the first slice, wherein the NSSAA of the first slice is successful, and the first slice is accepted by the network side device; receiving a second registration acceptance message, where the second registration acceptance message includes the first rejected NSSAI, where the first rejected NSSAI includes the first slice, where the first slice NSSAA fails and / or the first slice is not accepted by the network side device; A third registration acceptance message is received, wherein the third registration acceptance message includes a second pending NSSAI, wherein the second pending NSSAI includes the first slice, wherein the first slice NSSAI is being performed or is to be performed.
9. The method according to claim 7, characterized in that: The receiving of a configuration update command message includes at least one of the following: receiving a first configuration update command message, where the first configuration update command message includes a second allowed NSSAI, where the second allowed NSSAI includes the first slice, where the NSSAA of the first slice succeeds and the first slice is accepted by the network side device; A second configuration update command message is received, wherein the second configuration update command message includes a second rejected NSSAI, wherein the second rejected NSSAI includes the first slice, wherein the NSSAA of the first slice fails and / or the first slice is not accepted by the network side device.
10. The method according to claim 7, characterized in that The first registration request message also includes a requested NSSAI, where the requested NSSAI includes a second slice requested by the terminal, and the second slice does not belong to the first pending NSSAI.
11. The method according to claim 7, characterized in that The method further comprises: The terminal sends a second registration request message, where the second registration request message includes a request NSSAI, and the request NSSAI includes a second slice requested by the terminal; The second registration request message is sent by the terminal when there is no first pending NSSAI, or when the second slice does not belong to the first pending NSSAI.
12. A network side device, characterized in that: include: A receiving module, configured to receive a first registration request message, where the first registration request message includes additional requested network slice selection auxiliary information NSSAI, where the additional requested NSSAI includes a first slice requested by the terminal, where the first slice belongs to a first pending NSSAI; A sending module, used to send a registration acceptance message according to the state of the first slice; In a case where NSSAA of the first slice is being performed or is about to be performed, the sending module is further configured to: In the case where the NSSAA of the first slice is completed, a universal terminal configuration update UCU process is initiated, and the updated allowed NSSAI and / or rejected NSSAI are provided in the configuration update command message; The process of initiating a universal UCU includes: When the requested NSSAI or the additional requested NSSAI provided by the terminal during the last registration process of 3GPP access or non-3GPP access includes the first slice, a general UCU process is initiated on the access corresponding to the last registration process.
13. The network side device according to claim 12, characterized in that: The sending module is used for one of the following: If the first slice network slice authentication and authorization NSSAA succeeds, and the first slice is accepted by the network side device, a first registration acceptance message is sent, where the first registration acceptance message includes a first allowed NSSAI, and the first allowed NSSAI includes the first slice; If the NSSAA of the first slice fails and / or the first slice is not accepted by the network side device, sending a second registration acceptance message, where the second registration acceptance message includes the first rejected NSSAI, and the first rejected NSSAI includes the first slice; If NSSAA of the first slice is being performed or is to be performed, a third registration acceptance message is sent, where the third registration acceptance message includes a second pending NSSAI, where the second pending NSSAI includes the first slice.
14. The network side device according to claim 12, characterized in that: The sending module is used for at least one of the following: If the NSSAA of the first slice succeeds and the first slice is accepted by the network side device, sending a first configuration update command message, where the first configuration update command message includes a second allowed NSSAI, and the second allowed NSSAI includes the first slice; If the NSSAA of the first slice fails and / or the first slice is not accepted by the network side device, a second configuration update command message is sent, wherein the second configuration update command message includes a second rejected NSSAI, and the second rejected NSSAI includes the first slice.
15. The network side device according to claim 12, characterized in that: The sending module is used for: Generic UCU procedures are initiated on 3rd Generation Partnership Project 3GPP access or non-3GPP access.
16. The network side device according to claim 12, characterized in that: The first registration request message also includes a requested NSSAI, where the requested NSSAI includes a second slice requested by the terminal, and the second slice does not belong to the first pending NSSAI.
17. The network side device according to claim 12, characterized in that: The receiving module is further used for: receiving a second registration request message, where the second registration request message includes a request NSSAI, where the request NSSAI includes a second slice requested by the terminal; The second registration request message is sent by the terminal when there is no first pending NSSAI, or when the second slice does not belong to the first pending NSSAI.
18. A terminal, characterized in that: include: A sending module, configured to send a first registration request message, where the first registration request message includes an additional request NSSAI, where the additional request NSSAI includes a first slice requested by the terminal, where the first slice belongs to a first pending NSSAI; A receiving module, configured to receive a registration acceptance message, where the registration acceptance message is sent by a network side device according to a state of the first slice; In a case where NSSAA of the first slice is being performed or is about to be performed, the receiving module is further configured to: Receive a configuration update command message, wherein the configuration update command message includes the updated allowed NSSAI and / or rejected NSSAI, wherein the network side device is further used to complete the NSSAA of the first slice , And when the first slice is included in the requested NSSAI or additional requested NSSAI provided by the terminal during the last registration process of 3GPP access or non-3GPP access, a general UCU process is initiated on the access corresponding to the last registration process of the terminal.
19. The terminal according to claim 18, characterized in that: The receiving module is used for one of the following: receiving a first registration acceptance message, the first registration acceptance message including a first allowed NSSAI, the first allowed NSSAI including the first slice, wherein the NSSAA of the first slice is successful, and the first slice is accepted by the network side device; receiving a second registration acceptance message, where the second registration acceptance message includes the first rejected NSSAI, where the first rejected NSSAI includes the first slice, where the first slice NSSAA fails and / or the first slice is not accepted by the network side device; A third registration acceptance message is received, wherein the third registration acceptance message includes a second pending NSSAI, wherein the second pending NSSAI includes the first slice, wherein the first slice NSSAI is being performed or is to be performed.
20. The terminal according to claim 18, characterized in that The receiving module is used for at least one of the following: receiving a first configuration update command message, where the first configuration update command message includes a second allowed NSSAI, where the second allowed NSSAI includes the first slice, where the NSSAA of the first slice succeeds and the first slice is accepted by the network side device; A second configuration update command message is received, wherein the second configuration update command message includes a second rejected NSSAI, wherein the second rejected NSSAI includes the first slice, wherein the NSSAA of the first slice fails and / or the first slice is not accepted by the network side device.
21. The terminal according to claim 18, characterized in that The first registration request message also includes a requested NSSAI, where the requested NSSAI includes a second slice requested by the terminal, and the second slice does not belong to the first pending NSSAI.
22. The terminal according to claim 18, characterized in that The sending module is further used for: Sending a second registration request message, where the second registration request message includes a request NSSAI, where the request NSSAI includes a second slice requested by the terminal; The second registration request message is sent by the terminal when there is no first pending NSSAI, or when the second slice does not belong to the first pending NSSAI.
23. A network side device, characterized in that: It includes a processor, a memory, and a program or instruction stored in the memory and executable on the processor, wherein the program or instruction, when executed by the processor, implements the slice request method as described in any one of claims 1 to 6.
24. A terminal, characterized in that: It includes a processor, a memory, and a program or instruction stored in the memory and executable on the processor, wherein the program or instruction, when executed by the processor, implements the slice request method as described in any one of claims 7 to 11.
25. A readable storage medium, characterized in that: The readable storage medium stores a program or instruction, and when the program or instruction is executed by the processor, it implements the slice request method as described in any one of claims 1 to 6, or implements the slice request method as described in any one of claims 7 to 11.
