CN115412434B

CN115412434B - Slicing request method and terminal equipment

Info

Publication number: CN115412434B
Application number: CN202211035415.3A
Authority: CN
Inventors: 卫威
Original assignee: Zeku Technology Beijing Corp Ltd
Current assignee: Zeku Technology Beijing Corp Ltd
Priority date: 2022-08-26
Filing date: 2022-08-26
Publication date: 2024-02-09
Anticipated expiration: 2042-08-26
Also published as: CN115412434A; WO2024041288A1

Abstract

The application relates to a slice request method and terminal equipment, wherein the slice request method comprises the following steps: the terminal device requests the network slice according to the reject slice information based on the network slice concurrent registration group (NSSRG). The method and the device can realize network slicing request.

Description

Slicing request method and terminal equipment

Technical Field

The present application relates to the field of communications, and more particularly, to a slice request method and a terminal device.

Background

A brand new feature of Network Slicing (Network slice) is introduced into the fifth generation mobile communication technology (5G,5th Generation Mobile Communication Technology) system, and is also a representative function of the 5G system; the method aims at respectively distributing different network resources such as bandwidth, speed, service quality and the like by dividing different network slices under the same network environment, so that different service demands can more reasonably occupy the network resources. When a terminal device initiates registration in a network, firstly requesting network slicing; how the terminal device requests the network slice is a technical problem to be solved.

Disclosure of Invention

The embodiment of the application provides a slice request method and terminal equipment, which are used for requesting network slices.

The embodiment of the application provides a slice request method, which comprises the following steps: the terminal device requests the network slice according to the reject slice information based on the network slice concurrent registration group (NSSRG).

The embodiment of the application provides a slice configuration method, which comprises the following steps: the network device transmits reject slice information based on the network slice concurrent registration group.

The embodiment of the application provides a terminal device, which comprises: and the slice request module is used for requesting the network slice based on the reject slice information of the network slice concurrent registration group.

The embodiment of the application provides a network device, which comprises: and the sending module is used for sending the refused slice information based on the network slice concurrent registration group.

An embodiment of the application provides an apparatus including a processor and a memory. The memory is used for storing a computer program, and the processor is used for calling and running the computer program stored in the memory so as to enable the device to execute the method.

The embodiment of the application provides a chip for realizing the method.

Specifically, the chip includes: and a processor for calling and running the computer program from the memory, so that the device mounted with the chip executes the method.

The present embodiments provide a computer readable storage medium storing a computer program which, when executed by a device, causes the device to perform the above-described method.

Embodiments of the present application provide a computer program product comprising computer program instructions for causing a computer to perform the above-described method.

The present embodiments provide a computer program which, when run on a computer, causes the computer to perform the above method.

According to the embodiment of the application, the terminal equipment can request the network slice according to the NSSRG-based reject slice information, so that the network slice request taking the NSSRG as a unit is realized, the network slice associated with the NSSRG is requested, and the accurate request for the network slice is realized.

Drawings

Fig. 1 is a schematic diagram of an application scenario according to an embodiment of the present application;

FIG. 2 is a schematic flow chart diagram of a slice request method 200 according to an embodiment of the present application;

FIG. 3 is a flow chart of an implementation according to embodiment 1 of the present application;

FIG. 4 is a flow chart of an implementation according to embodiment 2 of the present application;

FIG. 5 is a flow chart of an implementation according to embodiment 3 of the present application;

FIG. 6 is a schematic flow chart diagram of a slice configuration method 600 according to an embodiment of the present application;

Fig. 7 is a schematic block diagram of a terminal device 700 according to an embodiment of the present application;

fig. 8 is a schematic block diagram of a terminal device 800 according to an embodiment of the present application;

fig. 9 is a schematic block diagram of a network device 900 according to an embodiment of the present application;

fig. 10 is a schematic structural diagram of a communication apparatus 1000 according to an embodiment of the present application;

FIG. 11 is a schematic block diagram of a chip 1100 according to an embodiment of the present application;

fig. 12 is a schematic block diagram of a communication system 1200 according to an embodiment of the present application.

Detailed Description

The technical solutions in the embodiments of the present application will be described below with reference to the drawings in the embodiments of the present application.

The technical solution of the embodiment of the application can be applied to various communication systems, for example: global system for mobile communications (Global System of Mobile communication, GSM), code division multiple access (Code Division Multiple Access, CDMA) system, wideband code division multiple access (Wideband Code Division Multiple Access, WCDMA) system, general packet Radio service (General Packet Radio Service, GPRS), long term evolution (Long Term Evolution, LTE) system, advanced long term evolution (Advanced long term evolution, LTE-a) system, new Radio (NR) system, evolved system of NR system, LTE-based access to unlicensed spectrum, LTE-U) system on unlicensed spectrum, NR (NR-based access to unlicensed spectrum, NR-U) system on unlicensed spectrum, non-terrestrial communication network (Non-Terrestrial Networks, NTN) system, universal mobile communication system (Universal Mobile Telecommunication System, UMTS), wireless local area network (Wireless Local Area Networks, WLAN), wireless fidelity (Wireless Fidelity, wiFi), fifth Generation communication (5 th-Generation, 5G) system, or other communication system, etc.

Generally, the number of connections supported by the conventional communication system is limited and easy to implement, however, with the development of communication technology, the mobile communication system will support not only conventional communication but also, for example, device-to-Device (D2D) communication, machine-to-machine (Machine to Machine, M2M) communication, machine type communication (Machine Type Communication, MTC), inter-vehicle (Vehicle to Vehicle, V2V) communication, or internet of vehicles (Vehicle to everything, V2X) communication, etc., and the embodiments of the present application may also be applied to these communication systems.

In one implementation, the communication system in the embodiment of the present application may be applied to a carrier aggregation (Carrier Aggregation, CA) scenario, a dual connectivity (Dual Connectivity, DC) scenario, and a Stand Alone (SA) networking scenario.

In one implementation, the communication system in the embodiments of the present application may be applied to unlicensed spectrum, where unlicensed spectrum may also be considered as shared spectrum; alternatively, the communication system in the embodiments of the present application may also be applied to licensed spectrum, where licensed spectrum may also be considered as non-shared spectrum.

Embodiments of the present application describe various embodiments in connection with network devices and terminal devices, where a terminal device may also be referred to as a User Equipment (UE), access terminal, subscriber unit, subscriber station, mobile station, remote terminal, mobile device, user terminal, wireless communication device, user agent, user Equipment, or the like.

The terminal device may be a Station (ST) in a WLAN, may be a cellular telephone, a cordless telephone, a session initiation protocol (Session Initiation Protocol, SIP) phone, a wireless local loop (Wireless Local Loop, WLL) station, a personal digital assistant (Personal Digital Assistant, PDA) device, a handheld device with wireless communication capabilities, a computing device or other processing device connected to a wireless modem, a vehicle device, a wearable device, a terminal device in a next generation communication system such as an NR network, or a terminal device in a future evolved public land mobile network (Public Land Mobile Network, PLMN) network, etc.

In embodiments of the present application, the terminal device may be deployed on land, including indoor or outdoor, hand-held, wearable or vehicle-mounted; can also be deployed on the water surface (such as ships, etc.); but may also be deployed in the air (e.g., on aircraft, balloon, satellite, etc.).

In the embodiment of the present application, the terminal device may be a Mobile Phone (Mobile Phone), a tablet computer (Pad), a computer with a wireless transceiving function, a Virtual Reality (VR) terminal device, an augmented Reality (Augmented Reality, AR) terminal device, a wireless terminal device in industrial control (industrial control), a wireless terminal device in unmanned driving (self driving), a wireless terminal device in remote medical (remote medical), a wireless terminal device in smart grid (smart grid), a wireless terminal device in transportation security (transportation safety), a wireless terminal device in smart city (smart city), or a wireless terminal device in smart home (smart home), and the like.

By way of example, and not limitation, in embodiments of the present application, the terminal device may also be a wearable device. The wearable device can also be called as a wearable intelligent device, and is a generic name for intelligently designing daily wear by applying wearable technology and developing wearable devices, such as glasses, gloves, watches, clothes, shoes and the like. The wearable device is a portable device that is worn directly on the body or integrated into the clothing or accessories of the user. The wearable device is not only a hardware device, but also can realize a powerful function through software support, data interaction and cloud interaction. The generalized wearable intelligent device includes full functionality, large size, and may not rely on the smart phone to implement complete or partial functionality, such as: smart watches or smart glasses, etc., and focus on only certain types of application functions, and need to be used in combination with other devices, such as smart phones, for example, various smart bracelets, smart jewelry, etc. for physical sign monitoring.

In this embodiment of the present application, the network device may be a device for communicating with a mobile device, where the network device may be an Access Point (AP) in WLAN, a base station (Base Transceiver Station, BTS) in GSM or CDMA, a base station (NodeB, NB) in WCDMA, an evolved base station (Evolutional Node B, eNB or eNodeB) in LTE, a relay station or an Access Point, a vehicle device, a wearable device, and a network device (gNB) in an NR network, or a network device in a PLMN network for future evolution, or a network device in an NTN network, etc.

By way of example and not limitation, in embodiments of the present application, a network device may have a mobile nature, e.g., the network device may be a mobile device. Alternatively, the network device may be a satellite, a balloon station. For example, the satellite may be a Low Earth Orbit (LEO) satellite, a medium earth orbit (medium earth orbit, MEO) satellite, a geosynchronous orbit (geostationary earth orbit, GEO) satellite, a high elliptical orbit (High Elliptical Orbit, HEO) satellite, or the like. Alternatively, the network device may be a base station disposed on land, in a water area, or the like.

In this embodiment of the present application, a network device may provide a service for a cell, where a terminal device communicates with the network device through a transmission resource (e.g., a frequency domain resource, or a spectrum resource) used by the cell, where the cell may be a cell corresponding to a network device (e.g., a base station), and the cell may belong to a macro base station, or may belong to a base station corresponding to a Small cell (Small cell), where the Small cell may include: urban cells (Metro cells), micro cells (Micro cells), pico cells (Pico cells), femto cells (Femto cells) and the like, and the small cells have the characteristics of small coverage area and low transmitting power and are suitable for providing high-rate data transmission services.

Fig. 1 schematically illustrates a communication system 100. The communication system comprises one network device 110 and two terminal devices 120. In one embodiment, the communication system 100 may include a plurality of network devices 110, and each network device 110 may include other numbers of terminal devices 120 within a coverage area of the network device 110, which is not limited in this embodiment.

In one embodiment, the communication system 100 may further include other network entities such as a mobility management entity (Mobility Management Entity, MME), an access and mobility management function (Access and Mobility Management Function, AMF), and the present embodiment is not limited thereto.

The network device may further include an access network device and a core network device. I.e. the wireless communication system further comprises a plurality of core networks for communicating with the access network devices. The access network device may be a long-term evolution (LTE) system, a next-generation (NR) system, or an evolved base station (evolutional node B, abbreviated as eNB or e-NodeB) macro base station, a micro base station (also called "small base station"), a pico base station, an Access Point (AP), a transmission point (transmission point, TP), a new generation base station (new generation Node B, gNodeB), or the like in an licensed assisted access long-term evolution (LAA-LTE) system.

It should be understood that a device having a communication function in a network/system in an embodiment of the present application may be referred to as a communication device. Taking the communication system shown in fig. 1 as an example, the communication device may include a network device and a terminal device with a communication function, where the network device and the terminal device may be specific devices in the embodiments of the present application, and are not described herein again; the communication device may also include other devices in the communication system, such as a network controller, a mobility management entity, and other network entities, which are not limited in this embodiment of the present application.

It should be understood that the terms "system" and "network" are used interchangeably herein. The term "and/or" is herein merely an association relationship describing an associated object, meaning that there may be three relationships, e.g., a and/or B, may represent: a exists alone, A and B exist together, and B exists alone. In addition, the character "/" herein generally indicates that the front and rear associated objects are an "or" relationship.

It should be understood that, in the embodiments of the present application, the "indication" may be a direct indication, an indirect indication, or an indication having an association relationship. For example, a indicates B, which may mean that a indicates B directly, e.g., B may be obtained by a; it may also indicate that a indicates B indirectly, e.g. a indicates C, B may be obtained by C; it may also be indicated that there is an association between a and B.

In the description of the embodiments of the present application, the term "corresponding" may indicate that there is a direct correspondence or an indirect correspondence between the two, or may indicate that there is an association between the two, or may indicate a relationship between the two and the indicated, configured, or the like.

In order to facilitate understanding of the technical solutions of the embodiments of the present application, the following description is given of related technologies of the embodiments of the present application, and the following related technologies may be optionally combined with the technical solutions of the embodiments of the present application as an alternative, which all belong to the protection scope of the embodiments of the present application.

A completely new feature of Network Slicing (Network slice) is introduced into the 5G system, and is also a representative function of the 5G system. The method aims at respectively distributing different network resources such as bandwidth, speed, service quality and the like by dividing different network slices under the same network environment, so that different service demands can more reasonably occupy the network resources.

When a UE initiates registration in a public land mobile network (PLMN, public land mobile network), the UE needs to carry the slice information (such as the requested NSSAI (Requested NSSAI)) requested by the UE in a Non-Access-Stratum (NAS) message (such as the registration request (Registration Request)) of the registration request to the network according to the available slice information (such as the available network slice selection assistance information (Allowed NSSAI, allowed Network Slice Selection Assistance Information)) and the configured slice information (such as the configured NSSAI (Configured NSSAI)) under the network stored by the UE or the default configured slice information (such as the default configured NSSAI (Default Configured NSSAI)), excluding the rejected slice information (such as the rejected NSSAI (Rejected NSSAI)), and combining with the UE's own policy. The network confirms the configuration slice information (e.g., configured nsai), available slice information (e.g., available nsai), and reject slice information (e.g., reject nsai) of the UE under the current network according to the slice information it requests, and configures these information to the UE in a NAS message (e.g., request response (Registration Accept)) of the registration response. One or more Single network slice selection assistance information (S-nsai, single nsai) may be included in each of these nsais. The UE may then select a specific S-nsai available under the current network to initiate the data session based on the configuration information and its own policy.

On this basis, a new concept is introduced, namely network slice concurrency registration group (Network Slice Simultaneous Registration Group, NSSRG). When the user indicates in the registration request that the terminal supports NSSRG functionality, the network will give NSSRG configuration information in the registration response.

The protocol defines this information as in table 1:

TABLE 1 NSSRG configuration information definition

As shown in table 1, the NSSRG information may include one or more S-NSSAI associated NSSRG values (NSSRG values for S-NSSAI), which is further defined in the protocol as in table 2:

TABLE 2 definition of NSSAI associated NSSRG values

It can be seen that one S-NSSAI may be associated with one or more NSSRG values to indicate which NSSRGs an S-NSSAI is associated with.

NSSRG information is associated with Configured nsais (Configured nsais) under the current network, that is, all Configured S-nsais under the current network may each be associated with one or more NSSRGs. While the available slices (e.g., available NSSAIs) are a subset of the configuration slices under the current network, each available S-NSSAI is also associated with one or more NSSRGs.

The slices requested by the user when initiating registration are generally associated with the same NSSRG, so that after each registration success, the available slices allocated to the user by the network side are associated with a common NSSRG, and each data session initiated by the user can be associated with a specific certain NSSRG. Using NSSRGs may enable classification management of a user's slice configuration, may confirm which associated slices the user may use on a particular NSSRG based on a particular implementation policy, and then configure the corresponding available slices (e.g., allowed NSSAIs) to the user, who may then initiate a data session only on the corresponding associated NSSRG. Different users can only use available slices associated with available NSSRGs according to different subscription information of the users, and can not access slices associated with other NSSRGs, so that further fine management of network slices is realized.

The main drawbacks of the existing slice request procedure are the following scenarios:

the current reject slice definition is still S-nsai based, i.e. the slice request can only be rejected for a specific S-nsai. If one S-NSSAI associates multiple NSSRGs, the network cannot reject it based on NSSRGs when it is rejected within the current protocol framework.

For example, such as a user signing up for two NSSRGs: group 1 and group 2, when the current terminal registers, slice is requested on group 1, and not requested on group 2; if the requested S-NSSAI is associated with both group 1 and group 2, the network side will reject the S-NSSAI uniformly when rejecting the slice request, which results in the end user' S available slices on group 2 also being rejected. Subsequently, if the user switches to group 2, and re-initiates registration and requests a slice, the S-nsai on group 2 requested by the user excludes the S-nsai that was rejected before, so the number of slices currently requested on group 2 is smaller than the number of slices actually requested by group 2, i.e. the S-nsai rejected before the slice request was initiated on group 1 cannot be requested on group 2. It can be seen that existing request and reject slices are implemented in units of S-NSSAI, and that NSSRG-based slice fine management is not actually achieved.

Fig. 2 is a schematic flow chart diagram of a slice request method 200 according to an embodiment of the present application. The method may alternatively be applied to the system shown in fig. 1, but is not limited thereto. The method includes at least some of the following.

And S210, the terminal equipment requests the network slice according to NSSRG-based reject slice information.

By requesting network slices according to NSSRG-based reject slice information, embodiments of the present application enable NSSRG-based accurate management and request of network slices.

The NSSRG based reject slice information may be configured by the network side, e.g. by AMF.

In some embodiments, NSSRG-based reject slice information is carried in extended reject slice information. For example, the extended rejection slice information may select auxiliary information for the extended rejection network slice (Extended Rejected NSSAI).

The format of the extended reject network slice selection assistance information is shown in table 3:

TABLE 3 extended rejection NSSAI

One or more NSSRG-based reject slice information may be carried in the extended reject slice information (e.g., extended reject NSSAI), where the NSSRG-based reject slice information may be an NSSRG-based S-NSSAI.

In some embodiments, extended rejection S-NSSAI carrying one or more NSSRG based slice rejection information is as shown in table 4:

TABLE 4 Table 4

In some embodiments, the value of the list Type (Type of list) of the extended rejection nsai shown in table 4 is a first value, which is used to indicate that the extended rejection nsai is an extended rejection nsai that carries NSSRG-based rejection slice information. In the related art, two types of extended rejection NSSAI have been defined, one of which is a list of rejection S-NSSAI, whose list Type (Type of list) has a value of 000; another is an extended rejection nsai with a list Type (Type of list) value of 001, which increases the back-off timer duration. In order to distinguish from the existing extended rejection nsai, in the extended rejection nsai carrying NSSRG-based reject slice information according to the embodiment of the present application, the value of the list Type (Type of list) (i.e., the first value described above) may be a value other than the foregoing 000 and 001, for example, the first value is 010.

As shown in table 4, the extended rejection nsai proposed in the embodiment of the present application carries one or more rejection S-nsai (reject S-nsai with NSSRG) based on NSSRG. Taking the NSSRG-based rejection S-NSSAI 1 (reject S-NSSAI 1 with NSSRG) of table 4 as an example, in some embodiments, the contents are as shown in table 5:

TABLE 5

As shown in table 5, the information in table 5 including S-NSSAI 1 and a plurality of NSSRG values indicates that S-NSSAI 1 is rejected in the case of associated NSSRG 1, associated NSSRG 2, …, or associated NSSRG y. Therefore, the embodiment of the application adopts the NSSRG-based reject slice information, so that the network slice can be accurately managed according to the combined information of the S-NSSAI and the NSSRG. For example, S-NSSAI A associates NSSRG 1 and NSSRG 2; when the terminal equipment requests S-NSSAI A on NSSRG 1, the terminal equipment is refused by the network equipment, the terminal equipment receives and stores refused slice information based on NSSRG sent by the network equipment, and the refused slice information based on NSSRG comprises the information of S-NSSAI A and NSSRG 1; after that, when the terminal device switches to NSSRG 2, the registration request is reinitiated, and the reject slice information based on NSSRG only contains the information of S-nsai a and NSSRG 1, but does not contain the information of S-nsai a and NSSRG 2, so the terminal device can request the S-nsai a on NSSRG 2. As can be seen, embodiments of the present application facilitate accurate control of NSSRG associated network slices.

In some implementations, the slice request method provided by the embodiment of the present application further includes: the terminal equipment also records reject slice information based on NSSRG.

Wherein NSSRG based reject slice information may be sent by the network device (e.g., AMF) via a registration response (Registration Accept) or a configuration update command (Configuration Update Command), e.g., the terminal device receives a registration response or a configuration update command carrying the NSSRG based reject slice information.

After receiving the NSSRG-based reject slice information, the terminal device may update the previously saved available nsais, e.g., the terminal device deletes the first S-nsais from the available nsais; the first S-NSSAI is S-NSSAI associated with a first NSSRG, and the reject slice information based on NSSRG comprises the first S-NSSAI and the information of the first NSSRG. Wherein, the first NSSRG may be an NSSRG currently requested by the UE. Specifically, after receiving the NSSRG-based reject slice information, the terminal device may check whether each of the current Allowed S-NSSAIs (among the available NSSAIs) and its current associated NSSRG group has been rejected. If so, the Allowed S-NSSAI is deleted from the Allowed NSSAI. If the S-NSSAI has associated with it an active PDU Session (PDU Session), the PDU Session may be released first, after which the S-NSSAI may be deleted.

When a subsequent terminal device initiates a registration request, it can check to see if the Requested S-NSSAI and associated NSSRG are in the NSSRG based reject slice list when the registration request slice (Requested NSSAI) is filled. If so, then the S-NSSAI may not be requested, otherwise, still be requested.

Specifically, the terminal device requests the network slice according to the NSSRG-based reject slice information, and may include:

in the case that the reject slice information based on the NSSRG contains the network slice to be requested and the information of the third NSSRG, the terminal device does not request the network slice to be requested associated with the third NSSRG; or,

in the case that the reject slice information based on the NSSRG does not include the network slice to be requested and the information of the third NSSRG, the terminal device requests the network slice to be requested associated with the third NSSRG.

For example, in the case that the reject slice information based on NSSRG includes the S-NSSAI to be requested and the information of the third NSSRG, the terminal device does not request the S-NSSAI to be requested associated with the third NSSRG; or,

in case that the reject slice information based on the NSSRG does not contain the information of the S-NSSAI to be requested and the third NSSRG, the terminal device requests the S-NSSAI to be requested associated with the third NSSRG.

In some embodiments, if the available NSSAI stored by the terminal device is emptied, the terminal device may initiate an update registration request and request a second S-NSSAI associated with a second NSSRG in the update registration request, where the reject slice information based on the NSSRG does not include information of the second S-NSSAI and the second NSSRG. That is, when the terminal device initiates an update registration request on a certain NSSRG, the requested S-NSSAI and the information of the NSSRG are not included in the NSSRG-based reject slice information.

The network device (e.g., AMF) should try to ensure that the terminal device has at least one NSSRG group available under the current PLMN and has associated available slices. If the UE does not have any NSSRG available due to special reasons such as subscription information change, manual administration, etc., the network device may reject the registration request of the UE, which may be- #7"5g service is not available.

Example 1:

fig. 3 is a flowchart of an implementation according to embodiment 1 of the present application, including the following steps:

s301, the UE is initially registered under the current PLMN, at the moment, the UE does not have available slice (Allowed NSSAI) and Configured slice (Configured NSSAI) records under the current PLMN, and the UE initiates a registration request by using the default Configured slice (Default Configured NSSAI) as a request slice (Requested NSSAI).

S302, the AMF issues an available slice (Allowed nsai), a Configured slice (Configured nsai), a reject slice (reject slice information that is not NSSRG-based as existing in the related art), NSSRG-based reject slice information proposed in the embodiment of the present application, and NSSRG information associated with the slice in a registration response (Registration Accept). The NSSRG-based rejection slice information may be carried in the extended rejection nsai shown in table 4.

S303, the UE records the information issued by the AMF. For example, the UE records available slices (Allowed NSSAI), configured slices (Configured NSSAI), reject slices, NSSRG-based reject slice information, etc.

S304, the UE initiates a registration request again, and based on the recorded information, when a request slice (Requested NSSAI) is filled, whether the Requested S-NSSAI and NSSRG associated with the S-NSSAI are in NSSRG-based rejection slice information or not can be checked; if yes, the S-NSSAI is not requested; otherwise, the S-NSSAI may be requested.

Example 2:

fig. 4 is a flowchart of an implementation according to embodiment 2 of the present application, including the following steps:

s401, the UE is currently in a registration state, and one or some of the originally available NSSRGs are to be changed to be unavailable, and the AMF issues a configuration update command (Configuration Update Command) to the UE, where the configuration update command carries NSSRG-based reject slice information to be updated. The NSSRG-based reject slice information may be updated with an additive, i.e. the AMF issues a new NSSRG-based reject slice list, and a new unavailable NSSRG record may be added on the last basis.

And S402, the UE receives and records the NSSRG-based reject slice information, and similarly, the UE can also adopt an additive recording mode when recording, namely, new NSSRG-based reject slice information is added on the basis of the original recording. And the UE checks whether each of the current Allowed S-NSSAIs and its current associated NSSRG group has been rejected. If so, it is deleted from the Allowed NSSAI. If the S-NSSAI has associated with it an active PDU session, the PDU session needs to be released locally first.

S403, if all available slices (Allowed nsai) of the UE under the current PLMN are deleted, the UE may initiate update registration, and the following steps are specifically adopted to update the Requested slices (Requested nsai) carried in the registration request:

(1) Filling out those Configured NSSAI under the current PLMN that have not been rejected by the associated NSSRG;

(2) If there are no more non-rejected slices in the configuration slices, the UE may initiate an update registration request with the non-rejected slices in the default configuration slices (Default Configured NSSAI).

For example, assume that the UE initiates an update registration request under NSSRGA, and the configuration slice under the current PLMN includes S-NSSAI 1, S-NSSAI 2, S-NSSAI 3. According to step (1), the UE searches whether the NSSRG a and S-NSSAI 1 information is in the currently stored NSSRG-based reject slice information, and if the NSSRG a and S-NSSAI 1 information is not in the NSSRG-based reject slice information, the UE may initiate an update registration request under NSSRG a, where the update registration request carries an identifier of S-NSSAI 1; if the NSSRG A and S-NSSAI 1 information is in the NSSRG-based reject slice information, the UE can further search for NSSRG A and S-NSSAI 2 information; if none of the NSSRG a and S-NSSAI 1 information, NSSRG a and S-NSSAI 2 information, NSSRG a and S-NSSAI 3 information is in the NSSRG based reject slice information, the UE may perform step (2), continue to find the non-rejected slice from the default configuration slice (Default Configured NSSAI) and initiate an update registration request, and the manner of the search may refer to step (1) described above, which is not repeated here.

The above describes the implementation manner that the terminal device receives and stores the reject slice information based on the NSSRG in the case that the originally available NSSRG is changed to be unavailable. The terminal equipment can receive and record new reject slice information based on NSSRG by adopting an updated adding mode. In the case that the original unavailable NSSRG is to be changed to be available, the embodiment of the application may delete all the originally stored NSSRG-based reject slice information, and receive and record new NSSRG-based reject slice information.

In some implementations, the slice request method provided by the embodiment of the present application further includes:

the terminal equipment receives a configuration update command for notifying the change of the network slice subscription information;

the terminal device clears the reject slice information based on NSSRG. Specifically, the terminal device may empty the locally stored NSSRG based reject slice information.

In some embodiments, the method may further comprise: the terminal equipment initiates an update registration request, and receives rejection slice information based on NSSRG.

Example 3:

fig. 5 is a flowchart of an implementation according to embodiment 3 of the present application, including the following steps:

s501, the AMF sends a configuration update command (Configuration Update Command) to the UE for the network slice subscription information change (Network slicing subscription changed), where the configuration update command (Configuration Update Command) does not carry other change information.

S502, the UE clears the current NSSRG-based reject slice list, and may clear other types of reject slice lists. The UE initiates an update registration.

S503, the AMF sends a registration response to the UE, and carries a new available slice (Allowed NSSAI) and a new NSSRG-based reject slice list in the registration response.

S504, the UE receives and records the foregoing information, such as new available slices (Allowed NSSAI), and new NSSRG-based reject slice list.

In some embodiments, the NSSRG-based reject slice information proposed in the embodiments of the present application is only valid under the current PLMN, and the current NSSRG-based reject slice information is deleted after the terminal device changes PLMNs. The terminal device may then wait for the AMF to issue a new list, e.g. the terminal device re-initiates a registration request, and the AMF issues new NSSRG based reject slice information in a registration response.

In some embodiments, the terminal device deletes NSSRG-based reject slice information in the event that the terminal device is deregistered. For example, the terminal device deletes the currently stored NSSRG-based reject slice list under the conditions of shutdown, restarting, entering a flight mode, pulling a USIM card, or network side initiating deregistration, and the like. The terminal device may then wait for the AMF to issue a new list, e.g. the terminal device re-initiates a registration request, and the AMF issues new NSSRG based reject slice information in a registration response.

The embodiment of the application also provides a slice configuration method, which can be optionally applied to the system shown in fig. 1, but is not limited to the method. Fig. 6 is a schematic flow chart diagram of a slice configuration method 600 according to an embodiment of the present application. The method includes at least some of the following.

And S610, the network equipment transmits rejection slice information based on NSSRG.

The network device includes a network interface that may be an AMF.

The network device sends NSSRG-based reject slice information to the terminal device, wherein the NSSRG-based reject slice information can comprise combined information of a plurality of slice information and NSSRG, and the combined information is used for the terminal device to request network slices according to the NSSRG-based reject slice information, so that accurate management of network slices based on NSSRG is realized.

In some embodiments, the reject slice information of the NSSRG is carried in the extended reject slice information.

In some embodiments, the extended rejection slice information includes an extended rejection nsai having a first value of a list type of the extended rejection nsai. The first value is used to indicate that the extended rejection nsai is an extended rejection nsai carrying reject slice information of NSSRG.

In some embodiments, the NSSRG based reject slice information includes single network slice selection assistance information S-NSSAI associated with the NSSRG.

In some embodiments, the network device transmits NSSRG based reject slice information, comprising:

and the network equipment sends a registration response or a configuration update command, wherein the registration response or the configuration update command carries the NSSRG-based reject slice information.

In some embodiments, in a case that the fourth NSSRG of the terminal device is changed from available to unavailable, the network device sends a configuration update command to the terminal device, where the configuration update command carries reject slice information based on the fourth NSSRG.

By adopting the mode, when the NSSRG is changed from the original available to the unavailable, the network equipment can issue new rejection slice information based on the NSSRG in an additive updating mode; the UE may add the new NSSRG based reject slice information on the basis of the locally stored NSSRG based reject slice information.

In some embodiments, in a case that the fifth NSSRG of the terminal device is changed from unavailable to available, the network device sends a configuration update command to the terminal device, where the configuration update command is used to notify the network slice subscription information of the change.

By adopting the above mode, when the NSSRG is changed from the original unavailable to the available, the network equipment can inform the UE to delete the original stored NSSRG-based reject slice information, and then, issue new NSSRG-based reject slice information again.

In some embodiments, the method further comprises: in the event that new NSSRG based reject slice information is present, the network device transmits the new NSSRG based reject slice information.

Specific examples of the method 600 for executing the network device in this embodiment may be referred to the description about the network device in the method 200, and are not repeated herein for brevity.

Fig. 7 is a schematic block diagram of a terminal device 700 according to an embodiment of the present application. The terminal device 700 may include:

the slice request module 710 is configured to request a network slice based on reject slice information of a network slice concurrent registration group (NSSRG).

In some implementations, the NSSRG based reject slice information is configured by the network device.

In some embodiments, NSSRG-based reject slice information is carried in extended reject slice information.

In some embodiments, the extended rejection slice information includes extended rejection network slice selection assistance information (nsai), the value of the list type of extended rejection nsai being a first value.

In some embodiments, the NSSRG based reject slice information includes NSSRG based single network slice selection assistance information S-NSSAI.

Fig. 8 is a schematic block diagram of a device 800 according to an embodiment of the present application. The device 800 includes one or more features of the device 700 embodiments described above. In one possible implementation manner, in an embodiment of the present application, the method further includes:

the receiving and information maintaining module 820 is configured to receive and record NSSRG-based reject slice information.

In some embodiments, the receiving and information maintaining module 820 is configured to receive a registration response or a configuration update command, where the registration response or the configuration update command carries the NSSRG-based reject slice information.

In some embodiments, the receiving and information maintenance module 820 is further configured to delete the first S-nsai from the available nsais; the first S-NSSAI is S-NSSAI associated with the first NSSRG, and the reject slice information based on the NSSRG comprises the first S-NSSAI and the first NSSRG.

In some embodiments, the slice request module 710 is further configured to initiate an update registration request if the available NSSAI is cleared, and request a second S-NSSAI associated with a second NSSRG in the update registration request, where the reject slice information based on the NSSRG does not include information of the second S-NSSAI and the second NSSRG.

In some embodiments, the receiving and information maintaining module 820 is configured to receive a configuration update command for notifying a change of the network slice subscription information, and empty the NSSRG-based reject slice information.

In some implementations, the slice request module 710 is configured to initiate an update registration request.

In some embodiments, further comprising:

a first deleting module 830, configured to delete the NSSRG-based reject slice information in case the terminal device 800 changes PLMNs.

In some embodiments, further comprising:

the second deleting module 840 is configured to delete the NSSRG-based reject slice information in case the terminal device 800 is unregistered.

In some implementations, the slice request module 710 is to:

in the case that the reject slice information based on the NSSRG includes the network slice to be requested and the information of the third NSSRG, the network slice to be requested associated with the third NSSRG is not requested; or,

in the case that the reject slice information based on the NSSRG does not include the network slice to be requested and the information of the third NSSRG, the network slice to be requested associated with the third NSSRG is requested.

In some implementations, the slice request module 710 is to:

In the case that the reject slice information based on the NSSRG contains the S-NSSAI to be requested and the information of the third NSSRG, the S-NSSAI to be requested associated with the third NSSRG is not requested; or,

in the case that the reject slice information based on the NSSRG does not include the S-NSSAI to be requested and the information of the third NSSRG, the S-NSSAI to be requested associated with the third NSSRG is requested.

The terminal device 800 of the embodiment of the present application can implement the corresponding function of the terminal device in the foregoing method embodiment. The flow, function, implementation and beneficial effects corresponding to each module (sub-module, unit or assembly, etc.) in the terminal device 800 can be referred to the corresponding description in the above method embodiments, and will not be repeated here. It should be noted that, the functions described with respect to the respective modules (sub-modules, units, or components, etc.) in the terminal device 700 and the terminal device 800 of the application embodiment may be implemented by different modules (sub-modules, units, or components, etc.), or may be implemented by the same module (sub-modules, units, components, etc.).

Fig. 9 is a schematic block diagram of a network device 900 according to an embodiment of the present application. The network device 900 may include:

a sending module 910, configured to send NSSRG-based reject slice information.

In some embodiments, the extended rejection slice information includes an extended rejection nsai, the value of the list type of extended rejection nsai being a first value.

In some embodiments, the sending module 910 is configured to send a registration response or a configuration update command, where the registration response or the configuration update command carries NSSRG-based reject slice information.

In some embodiments, in the case that the fourth NSSRG of the terminal device is changed from available to unavailable, the sending module 910 sends a configuration update command to the terminal device, where the configuration update command carries reject slice information based on the fourth NSSRG.

In some embodiments, in a case where the fifth NSSRG of the terminal device is changed from unavailable to available, the sending module 910 sends a configuration update command to the terminal device, where the configuration update command is used to notify the network slice subscription information of the change.

In some embodiments, the sending module 910 is further configured to send the new NSSRG based reject slice information if the new NSSRG based reject slice information is present.

In some implementations, the network device 900 includes an AMF.

The network device 900 of the embodiment of the present application can implement the corresponding functions of the network device in the foregoing method embodiment. The flow, function, implementation and beneficial effects corresponding to each module (sub-module, unit or component, etc.) in the network device 900 can be referred to the corresponding description in the above method embodiments, which are not repeated herein. It should be noted that, the functions described in the respective modules (sub-modules, units, or components, etc.) in the network device 900 of the application embodiment may be implemented by different modules (sub-modules, units, or components, etc.), or may be implemented by the same module (sub-modules, units, components, etc.).

Fig. 10 is a schematic structural diagram of a communication device 1000 according to an embodiment of the present application. The communication device 1000 comprises a processor 1010, from which the processor 1010 may call and run a computer program to cause the communication device 1000 to implement the method in the embodiments of the present application.

In one implementation, the communication device 1000 may also include a memory 1020. Wherein the processor 1010 may invoke and run a computer program from the memory 1020 to cause the communication device 1000 to implement the method in the embodiments of the present application.

The memory 1020 may be a separate device from the processor 1010 or may be integrated into the processor 1010.

In one embodiment, the communication device 1000 may further include a transceiver 1030, and the processor 1010 may control the transceiver 1030 to communicate with other devices, and in particular, may transmit information or data to other devices or receive information or data transmitted by other devices.

The transceiver 1030 may include, among other things, a transmitter and a receiver. The transceiver 1030 may further include an antenna, the number of which may be one or more.

In an implementation manner, the communication device 1000 may be a network device of the embodiment of the present application, and the communication device 1000 may implement corresponding flows implemented by the network device in each method of the embodiment of the present application, which are not described herein for brevity.

In an implementation manner, the communication device 1000 may be a terminal device in the embodiment of the present application, and the communication device 1000 may implement a corresponding flow implemented by the terminal device in each method in the embodiment of the present application, which is not described herein for brevity.

Fig. 11 is a schematic block diagram of a chip 1100 according to an embodiment of the present application. The chip 1100 includes a processor 1110, and the processor 1110 may call and run a computer program from a memory to implement the methods in the embodiments of the present application.

In one embodiment, the chip 1100 may also include a memory 1120. The processor 1110 may call and execute a computer program from the memory 1120 to implement the method performed by the terminal device or the network device in the embodiment of the present application.

Wherein the memory 1120 may be a separate device from the processor 1110 or may be integrated into the processor 1110.

In one embodiment, the chip 1100 may also include an input interface 1130. The processor 1110 may control the input interface 1130 to communicate with other devices or chips, and in particular, may obtain information or data sent by the other devices or chips.

In one embodiment, the chip 1100 may also include an output interface 1140. Wherein the processor 1110 may control the output interface 1140 to communicate with other devices or chips, and in particular, may output information or data to other devices or chips.

In an implementation manner, the chip may be applied to a network device in the embodiment of the present application, and the chip may implement a corresponding flow implemented by the network device in each method in the embodiment of the present application, which is not described herein for brevity.

In an implementation manner, the chip may be applied to a terminal device in an embodiment of the present application, and the chip may implement a corresponding flow implemented by the terminal device in each method in the embodiment of the present application, which is not described herein for brevity.

The chips applied to the network device and the terminal device may be the same chip or different chips.

It should be understood that the chips referred to in the embodiments of the present application may also be referred to as system-on-chip chips, or the like.

The processors mentioned above may be general purpose processors, digital signal processors (digital signal processor, DSP), off-the-shelf programmable gate arrays (field programmable gate array, FPGA), application specific integrated circuits (application specific integrated circuit, ASIC) or other programmable logic devices, transistor logic devices, discrete hardware components, etc. The general-purpose processor mentioned above may be a microprocessor or any conventional processor.

The memory mentioned above may be volatile memory or nonvolatile memory, or may include both volatile and nonvolatile memory. The nonvolatile memory may be a read-only memory (ROM), a Programmable ROM (PROM), an Erasable PROM (EPROM), an electrically Erasable EPROM (EEPROM), or a flash memory. The volatile memory may be random access memory (random access memory, RAM).

It should be understood that the above memory is exemplary but not limiting, and for example, the memory in the embodiments of the present application may be Static RAM (SRAM), dynamic RAM (DRAM), synchronous DRAM (SDRAM), double data rate SDRAM (DDR SDRAM), enhanced SDRAM (ESDRAM), synchronous Link DRAM (SLDRAM), direct RAM (DR RAM), and the like. That is, the memory in embodiments of the present application is intended to comprise, without being limited to, these and any other suitable types of memory.

Fig. 12 is a schematic block diagram of a communication system 1200 according to an embodiment of the present application. The communication system 1200 includes a terminal device 1210 and a network device 1220.

Wherein the terminal device 1210 may be adapted to implement the corresponding functions implemented by the terminal device in the above-described method, and the network device 1220 may be adapted to implement the corresponding functions implemented by the network device in the above-described method. For brevity, the description is omitted here.

In the above embodiments, it may be implemented in whole or in part by software, hardware, firmware, or any combination thereof. When implemented in software, may be implemented in whole or in part in the form of a computer program product. The computer program product includes one or more computer instructions. When the computer program instructions are loaded and executed on a computer, the processes or functions in accordance with embodiments of the present application are produced in whole or in part. The computer may be a general purpose computer, a special purpose computer, a computer network, or other programmable apparatus. The computer instructions may be stored in a computer-readable storage medium or transmitted from one computer-readable storage medium to another computer-readable storage medium, for example, the computer instructions may be transmitted from one website, computer, server, or data center to another website, computer, server, or data center by a wired (e.g., coaxial cable, fiber optic, digital subscriber line (Digital Subscriber Line, DSL)) or wireless (e.g., infrared, wireless, microwave, etc.). The computer readable storage medium may be any available medium that can be accessed by a computer or a data storage device such as a server, data center, etc. that contains an integration of one or more available media. The usable medium may be a magnetic medium (e.g., a floppy Disk, hard Disk, magnetic tape), an optical medium (e.g., DVD), or a semiconductor medium (e.g., solid State Disk (SSD)), or the like.

It should be understood that, in various embodiments of the present application, the sequence numbers of the foregoing processes do not mean the order of execution, and the order of execution of the processes should be determined by the functions and internal logic thereof, and should not constitute any limitation on the implementation process of the embodiments of the present application.

It will be clear to those skilled in the art that, for convenience and brevity of description, specific working procedures of the above-described systems, apparatuses and units may refer to corresponding procedures in the foregoing method embodiments, and are not repeated herein.

The foregoing is merely a specific embodiment of the present application, but the protection scope of the present application is not limited thereto, and any person skilled in the art can easily think about changes or substitutions within the technical scope of the present application, and the changes and substitutions should be covered in the protection scope of the present application. Therefore, the protection scope of the present application shall be subject to the protection scope of the claims.

Claims

1. A slice request method, comprising:

the terminal equipment requests the network slice according to the reject slice information based on the network slice concurrent registration group; the reject slice information based on the network slice concurrent registration group includes single network slice selection assistance information based on the network slice concurrent registration group.

2. The method of claim 1, wherein the reject slice information based on network slice concurrent registration groups is configured by a network device.

3. The method of claim 2, wherein the network slice concurrent registration group based reject slice information is carried in extended reject slice information.

4. The method of claim 3, wherein the extended rejection slice information includes extended rejection network slice selection assistance information, the value of the list type of extended rejection network slice selection assistance information being a first value.

5. The method of claim 4, further comprising: and the terminal equipment receives and records the refused slice information based on the network slice concurrent registration group.

6. The method of claim 5, wherein the terminal device receiving the reject slice information based on the network slice concurrent registration group comprises:

and the terminal equipment receives a registration response or a configuration update command, wherein the registration response or the configuration update command carries the rejection slice information of the concurrent registration group based on the network slice.

7. The method of claim 5 or 6, further comprising:

the terminal equipment deletes the first single network slice selection auxiliary information from the available network slice selection auxiliary information; the first single network slice selection auxiliary information is single network slice selection auxiliary information related to a first network slice concurrent registration group, and the reject slice information based on the network slice concurrent registration group comprises the first single network slice selection auxiliary information and the first network slice concurrent registration group information.

8. The method of claim 7, further comprising:

and under the condition that the available network slice selection auxiliary information is cleared, the terminal equipment initiates an updating registration request and requests second single network slice selection auxiliary information associated with a second network slice concurrent registration group in the updating registration request, wherein the reject slice information based on the network slice concurrent registration group does not contain the second single network slice selection auxiliary information and the information of the second network slice concurrent registration group.

9. The method of claim 7, further comprising:

and the terminal equipment empties the refusal slice information based on the network slice concurrent registration group.

10. The method of claim 9, further comprising:

the terminal equipment initiates an update registration request;

and the terminal equipment receives the reject slice information based on the network slice concurrent registration group.

11. The method of claim 7, further comprising:

and deleting the refused slice information based on the network slice concurrent registration group by the terminal equipment under the condition that the terminal equipment replaces the PLMN.

12. The method of claim 7, further comprising:

and deleting the refusal slice information based on the network slice concurrent registration group by the terminal equipment under the condition that the terminal equipment is unregistered.

13. The method of claim 1, wherein the terminal device requesting the network slice according to reject slice information based on the network slice concurrent registration group comprises:

under the condition that the reject slice information based on the network slice concurrent registration group contains information of a network slice to be requested and a third network slice concurrent registration group, the terminal equipment does not request the network slice to be requested associated with the third network slice concurrent registration group; or,

and under the condition that the reject slice information based on the network slice concurrent registration group does not contain the information of the network slice to be requested and the third network slice concurrent registration group, the terminal equipment requests to associate the network slice to be requested of the third network slice concurrent registration group.

14. The method of claim 13, wherein the terminal device requesting the network slice according to reject slice information based on the network slice concurrent registration group comprises:

Under the condition that the single network slice selection auxiliary information to be requested and the information of the third network slice concurrent registration group are contained in the reject slice information based on the network slice concurrent registration group, the terminal equipment does not request the single network slice selection auxiliary information to be requested associated with the third network slice concurrent registration group; or,

and under the condition that the single network slice selection auxiliary information to be requested and the information of the third network slice concurrent registration group are not contained in the reject slice information based on the network slice concurrent registration group, the terminal equipment requests the single network slice selection auxiliary information to be requested associated with the third network slice concurrent registration group.

15. A slice configuration method, comprising:

the network equipment sends reject slice information based on the network slice concurrent registration group; the reject slice information based on the network slice concurrent registration group includes single network slice selection auxiliary information associated with the single network slice concurrent registration group.

16. The method of claim 15, wherein the network slice concurrent registration group based reject slice information is carried in extended reject slice information.

17. The method of claim 16, wherein the extended rejection slice information comprises extended rejection network slice selection assistance information, the value of the list type of extended rejection network slice selection assistance information being a first value.

18. The method of claim 17, wherein the network device transmitting reject slice information based on a network slice concurrent registration group comprises:

and the network equipment sends a registration response or a configuration update command, wherein the registration response or the configuration update command carries the rejection slice information of the concurrent registration group based on the network slice.

19. The method of claim 18, wherein in the event that a fourth network slice concurrent registration group of a terminal device changes from available to unavailable, the network device sends a configuration update command to the terminal device, the configuration update command carrying reject slice information based on the fourth network slice concurrent registration group.

20. The method of claim 18, wherein in a case where a fifth network slice concurrent registration group of a terminal device is changed from unavailable to available, the network device sends a configuration update command to the terminal device, the configuration update command being used to notify a network slice subscription information change.

21. The method of claim 18, further comprising: in the case that the reject slice information of the new network slice-based concurrent registration group exists, the network device transmits the reject slice information of the new network slice-based concurrent registration group.

22. The method of claim 21, wherein the network device comprises an access and mobility management function, AMF.

23. A terminal device, comprising:

the slice request module is used for requesting the network slice based on the reject slice information of the network slice concurrent registration group; the reject slice information based on the network slice concurrent registration group includes single network slice selection assistance information based on the network slice concurrent registration group.

24. The terminal device of claim 23, wherein the reject slice information based on network slice concurrent registration groups is configured by a network device.

25. The terminal device of claim 24, wherein the reject slice information based on the network slice concurrent registration group is carried in extended reject slice information.

26. The terminal device of claim 25, wherein the extended rejection slice information includes extended rejection network slice selection assistance information, the value of the list type of extended rejection network slice selection assistance information being a first value.

27. The terminal device of claim 26, further comprising:

and the receiving and information maintaining module is used for receiving and recording the refused slice information based on the network slice concurrent registration group.

28. The terminal device of claim 27, wherein,

the receiving and information maintaining module is used for receiving a registration response or a configuration updating command, wherein the registration response or the configuration updating command carries the reject slice information of the concurrent registration group based on the network slice.

29. The terminal device according to claim 27 or 28, wherein,

the receiving and information maintaining module is further configured to delete the first single network slice selection auxiliary information from the available network slice selection auxiliary information; the first single network slice selection auxiliary information is single network slice selection auxiliary information related to a first network slice concurrent registration group, and the reject slice information based on the network slice concurrent registration group comprises the first single network slice selection auxiliary information and the first network slice concurrent registration group information.

30. The terminal device of claim 29, wherein,

the slice request module is further configured to initiate an update registration request when the available network slice selection assistance information is cleared, and request second single network slice selection assistance information associated with a second network slice concurrent registration group in the update registration request, where the reject slice information based on the network slice concurrent registration group does not include the second single network slice selection assistance information and the information of the second network slice concurrent registration group.

31. The terminal device of claim 29, wherein,

the receiving and information maintaining module is used for receiving a configuration updating command for notifying the change of the network slice subscription information and clearing the reject slice information based on the network slice concurrent registration group.

32. The terminal device of claim 31, wherein the slice request module is configured to initiate an update registration request.

33. The terminal device of claim 29, further comprising:

and the first deleting module is used for deleting the refused slice information based on the network slice concurrent registration group under the condition that the terminal equipment changes PLMN.

34. The terminal device of claim 29, further comprising:

and the second deleting module is used for deleting the refused slice information based on the network slice concurrent registration group under the condition that the terminal equipment is unregistered.

35. The terminal device of claim 23, wherein the slice request module is configured to:

under the condition that the reject slice information based on the network slice concurrent registration group contains information of a network slice to be requested and a third network slice concurrent registration group, the network slice to be requested associated with the third network slice concurrent registration group is not requested; or,

And requesting to associate the network slice to be requested of the third network slice concurrent registration group under the condition that the reject slice information based on the network slice concurrent registration group does not contain the information of the network slice to be requested and the third network slice concurrent registration group.

36. The terminal device of claim 35, wherein the slice request module is configured to:

under the condition that the single network slice selection auxiliary information to be requested and the information of a third network slice concurrent registration group are contained in the reject slice information based on the network slice concurrent registration group, the single network slice selection auxiliary information to be requested, which is associated with the third network slice concurrent registration group, is not requested; or,

and under the condition that the single network slice selection auxiliary information to be requested and the information of the third network slice concurrent registration group are not contained in the reject slice information based on the network slice concurrent registration group, requesting to associate the single network slice selection auxiliary information to be requested of the third network slice concurrent registration group.

37. A network device, comprising:

the sending module is used for sending reject slice information based on the network slice concurrent registration group; the reject slice information based on the network slice concurrent registration group includes single network slice selection assistance information associated with the network slice concurrent registration group.

38. The network device of claim 37, wherein the network slice concurrent registration group-based reject slice information is carried in extended reject slice information.

39. The network device of claim 38, wherein the extended rejection slice information comprises extended rejection network slice selection assistance information, the value of the list type of extended rejection network slice selection assistance information being a first value.

40. The network device of claim 39, wherein,

the sending module is configured to send a registration response or a configuration update command, where the registration response or the configuration update command carries reject slice information based on the network slice concurrent registration group.

41. The network device of claim 40, wherein the sending module sends a configuration update command to the terminal device, where a fourth network slice concurrent registration group of the terminal device changes from available to unavailable, the configuration update command carrying reject slice information based on the fourth network slice concurrent registration group.

42. The network device of claim 40, wherein the sending module sends a configuration update command to the terminal device, where the fifth network slice concurrent registration group of the terminal device changes from unavailable to available, the configuration update command being used to notify the network slice subscription information of the change.

43. The network device of claim 40, wherein,

the sending module is further configured to send the reject slice information of the new network slice-based concurrent registration group if the reject slice information of the new network slice-based concurrent registration group exists.

44. The network device of claim 43, wherein the network device comprises access and mobility management functions.

45. An apparatus, comprising: a processor, a memory and a transceiver, the memory being for storing a computer program, the processor being for invoking and running the computer program stored in the memory and controlling the transceiver to cause the apparatus to perform the method of any of claims 1 to 14 or 15-22.

46. A chip, comprising: a processor for calling and running a computer program from a memory, causing a device on which the chip is mounted to perform the method of any one of claims 1 to 14 or 15-22.

47. A computer readable storage medium storing a computer program which, when executed by a device, causes the device to perform the method of any one of claims 1 to 14 or 15-22.

48. A communication system, comprising:

terminal device for performing the method of any of claims 1 to 14;

network device for performing the method of any of claims 15 to 22.