CN115412434A

CN115412434A - Slicing request method and terminal equipment

Info

Publication number: CN115412434A
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: 2022-11-29
Anticipated expiration: 2042-08-26
Also published as: WO2024041288A1; CN115412434B

Abstract

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

Description

Slicing request method and terminal equipment

Technical Field

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

Background

The fifth Generation Mobile Communication Technology (5G, 5th Generation Mobile Communication Technology) system introduces the brand-new characteristic of Network Slicing (Network Slicing), which is also a representative function of the 5G system; the method aims to distribute different network resources such as bandwidth, rate, service quality and the like respectively by dividing different network slices under the same network environment, so that different service requirements can occupy the network resources more reasonably. When a terminal device initiates registration in a network, a network slice needs to be requested first; 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 slicing request method and terminal equipment, which are used for requesting network slicing.

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

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

An embodiment of the present application provides a terminal device, including: and the slicing request module is used for requesting the network slices based on the slicing rejection information of the network slice concurrent registration group.

An embodiment of the present application provides a network device, including: and the sending module is used for sending the slice rejection information based on the network slice concurrent registration group.

An embodiment of the application provides a device comprising 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 the processor is used for calling and running the computer program from the memory so that the equipment provided with the chip executes the method.

Embodiments of the present application provide a computer-readable storage medium for storing a computer program, which, when executed by an apparatus, causes the apparatus to perform the above-mentioned method.

An embodiment of the present application provides a computer program product, which includes computer program instructions, and the computer program instructions enable a computer to execute the method described above.

Embodiments of the present application provide a computer program which, when run on a computer, causes the computer to perform the above method.

According to the method and the device, the terminal equipment can request the network slice according to the NSSRG-based slice rejection information, so that the network slice request with NSSRG as a unit is realized, the network slice associated with 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 configuration 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 scheme of the embodiment of the application can be applied to various communication systems, for example: global System for Mobile communications (GSM) System, code Division Multiple Access (CDMA) System, wideband Code Division Multiple Access (WCDMA) System, general Packet Radio Service (GPRS), long Term Evolution (Long Term Evolution, LTE) System, LTE-a System, new Radio (NR) System, evolution System of NR System, LTE-based Access to unlicensed spectrum, LTE-U) System, NR-based to unlicensed spectrum (NR-U) System, non-Terrestrial communication network (NTN) System, universal Mobile Telecommunications System (UMTS), wireless Local Area Network (WLAN), wireless Fidelity (WiFi), 5th-Generation (5G) System, or other communication systems.

Generally, the conventional Communication system supports a limited number of connections and is 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 (M2M) Communication, machine Type Communication (MTC), vehicle to Vehicle (V2V) Communication, or Vehicle to internet (V2X) Communication, and the embodiments of the present application can also be applied to these Communication systems.

In an implementation manner, the communication system in the embodiment of the present application may be applied to a Carrier Aggregation (CA) scenario, may also be applied to a Dual Connectivity (DC) scenario, and may also be applied to a stand-alone (SA) networking scenario.

In one implementation, the communication system in the embodiment of the present application may be applied to an unlicensed spectrum, where the unlicensed spectrum may also be considered as a shared spectrum; alternatively, the communication system in the embodiment of the present application may also be applied to a licensed spectrum, where the licensed spectrum may also be regarded as an unshared spectrum.

Various embodiments are described in conjunction with network Equipment and terminal Equipment, where the terminal Equipment may also be referred to as User Equipment (UE), an access terminal, a subscriber unit, a subscriber station, a mobile station, a remote terminal, a mobile device, a User terminal, a wireless communication device, a User agent, or a User device.

The terminal device may be a Station (ST) in a WLAN, and may be a cellular phone, a cordless phone, a Session Initiation Protocol (SIP) phone, a Wireless Local Loop (WLL) station, a Personal Digital Assistant (PDA) device, a handheld device with Wireless communication capability, a computing device or other processing device connected to a Wireless modem, a vehicle-mounted 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 (PLMN) Network, and so on.

In the embodiment of the application, the terminal equipment can be deployed on land, including indoor or outdoor, handheld, wearable or vehicle-mounted; can also be deployed on the water surface (such as a ship and the like); and may also be deployed in the air (e.g., airplanes, balloons, satellites, etc.).

In this embodiment, 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 (AR) terminal device, a wireless terminal device in industrial control (industrial control), a wireless terminal device in self 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 safety (transportation safety), a wireless terminal device in city (smart city), a wireless terminal device in smart home (smart home), or the like.

By way of example and not limitation, in the embodiments of the present application, the terminal device may also be a wearable device. Wearable equipment can also be called wearable intelligent equipment, is the general term of applying wearable technique to carry out intelligent design, develop the equipment that can dress to daily wearing, like glasses, gloves, wrist-watch, dress and shoes etc.. A 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 realizes powerful functions through software support, data interaction and cloud interaction. The generalized wearable smart device includes full functionality, large size, and can implement full or partial functionality without relying on a smart phone, such as: smart watches or smart glasses and the like, and only focus on a certain type of application function, and need to be matched with other equipment such as a smart phone for use, such as various smart bracelets for physical sign monitoring, smart jewelry and the like.

In this embodiment of the present application, the network device may be a device for communicating with a mobile device, and the network device may be an Access Point (AP) in a WLAN, a Base Station (BTS) in GSM or CDMA, a Base Station (NodeB, NB) in WCDMA, an evolved Node B (eNB or eNodeB) in LTE, a relay Station or an Access Point, a vehicle-mounted 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.

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, balloon station. For example, the satellite may be a Low Earth Orbit (LEO) satellite, a Medium Earth Orbit (MEO) satellite, a geosynchronous Orbit (GEO) satellite, a High Elliptic Orbit (HEO) satellite, and the like. Alternatively, the network device may be a base station installed on land, water, or the like.

In this embodiment of the present application, a network device may provide a service for a cell, and 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 the network device (e.g., a base station), and the cell may belong to a macro base station or 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 transmission power, and are suitable for providing high-rate data transmission services.

Fig. 1 schematically illustrates a communication system 100. The communication system comprises a network device 110 and two terminal devices 120. In an implementation, 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, which is not limited in this embodiment.

In an embodiment, the communication system 100 may further include other network entities such as a Mobility Management Entity (MME), an Access and Mobility Management Function (AMF), which is not limited in this embodiment.

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 Radio (NR) system, or an evolved base station (evolved Node B) in an authorized assisted access long-term evolution (LAA-LTE) system, such as an eNB or an e-NodeB) macro base station, a micro base station (also referred to as a "small base station"), a pico base station, an Access Point (AP), a Transmission Point (TP), or a new generation base station (g-NodeB).

It should be understood that, in the embodiments of the present application, a device having a communication function in a network/system 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 having a communication function, and the network device and the terminal device may be specific devices in this embodiment, which are not described herein again; the communication device may further include other devices in the communication system, such as other network entities like a network controller, a mobility management entity, and the like, which is not limited in this embodiment.

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

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

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

For the convenience of understanding of the technical solutions of the embodiments of the present application, the following related technologies of the embodiments of the present application are described below, and the following related technologies may be optionally combined with the technical solutions of the embodiments of the present application as alternatives, and all of them belong to the protection scope of the embodiments of the present application.

The 5G system introduces the brand-new characteristic of Network Slicing (Network Slicing), which is also a representative function of the 5G system. The method aims to distribute different network resources such as bandwidth, rate, service quality and the like respectively by dividing different network slices under the same network environment, so that different service requirements can occupy the network resources more reasonably.

When a UE initiates Registration in a Public Land Mobile Network (PLMN), the UE needs to exclude the Rejected slicing Information (e.g., rejected NSSAI) from the Default Configured slicing Information (e.g., default Configured NSSAI) and carry the slicing Information (e.g., requested NSSAI) Requested by the UE in a Non-Access Stratum (Non-Access-Stratum) message (e.g., registration Request) of the Registration Request (Registration Request) to the Network according to the available slicing Information (e.g., available Network Slice Selection Assistance Information (Allowed NSSAI)) and the Configured slicing Information (e.g., configured NSSAI (Default Configured NSSAI)) in the Network, which are stored by the UE. The network confirms the configuration slice information (such as configured NSSAI), the available slice information (such as available NSSAI) and the reject slice information (such as reject NSSAI) of the UE in the current network according to the requested slice information, and configures the information to the UE in the NAS message of Registration response (such as request Accept). Each of these NSSAIs may contain one or more Single network slice selection assistance information (S-NSSAI, single NSSAI). The UE may then select the S-NSSAI available in the particular current network to initiate the data session based on the configuration information and its own policy.

On the basis of the above, a new concept, namely Network Slice concurrent Registration Group (NSSRG), is introduced. 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 information is defined in the protocol as table 1:

TABLE 1 NSSRG configuration information definition

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

TABLE 2 definition of S-NSSAI associated NSSRG values

It can be seen that an 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 a configuration slice (Configured NSSAI) under the current network, that is, all S-NSSAIs Configured under the current network may each be associated with one or more NSSRGs. The available slices (e.g., available NSSAIs) are a subset of the slices configured under the current network, so that each available S-NSSAI is associated with one or more NSSRGs.

The slice requested when the user initiates registration generally associates the same NSSRG, so that the available slice allocated to the user associates the common NSSRG after each successful registration at the network side, and each data session initiated by the user can also be associated to a specific NSSRG. The NSSRG may be used to implement classification management on the slice configuration of the user, and based on a specific implementation policy, it may be determined which associated slices the user may use on a specific NSSRG, and then a corresponding available slice (e.g., allowed NSSAI) is configured for the user, so that the user may only initiate a data session on the corresponding associated NSSRG subsequently. Different users can only use the available slices associated with the available NSSRG according to different subscription information of the users, and cannot access the slices associated with other NSSRGs, so that further refined management of the network slices is realized.

The main disadvantages of the existing slice request process are the following scenarios:

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

For example, say one user has signed up for two NSSRGs: group 1 and group 2, when the current terminal is registered, the slice is requested on the group 1, and the slice is not requested on the 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, re-initiates registration and requests slicing, the S-NSSAI on group 2 that he requested will exclude the previously rejected S-NSSAI, and therefore the number of slices currently requested on group 2 will be less than the number of slices actually requested by group 2, i.e., the S-NSSAI that was rejected when the slicing request was previously initiated on group 1 may not be requested on group 2. It can be seen that the existing requesting and rejecting slices are implemented in units of S-NSSAI, and there is no NSSRG-based slice fine management.

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 part of the following.

S210, the terminal equipment requests network slicing according to the NSSRG-based slicing rejection information.

By requesting a network slice according to NSSRG-based reject slice information, the embodiment of the application can realize accurate management and request of the network slice based on NSSRG.

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

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

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., NSSAI), where the NSSRG-based reject slice information may be S-NSSAI based on NSSRG.

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

TABLE 4

In some embodiments, the value of the list Type (Type of list) of the extended rejection NSSAI shown in table 4 is a first value for indicating that the extended rejection NSSAI is an extended rejection NSSAI carrying NSSRG-based reject 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, the list Type (Type of list) of which has a value of 000; another is extended reject NSSAI with increased back-off timer duration, whose list Type (Type of list) has a value of 001. In order to distinguish from the existing extended reject NSSAI, in the extended reject NSSAI carrying NSSRG-based reject slice information proposed in the embodiment of the present application, a value of a list Type (Type of list) (i.e., the first value) may be a value other than the aforementioned 000 and 001, for example, the first value is 010.

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

TABLE 5

As shown in table 5, table 5 includes information of S-NSSAI 1 and a plurality of NSSRG values, indicating that S-NSSAI 1 is rejected when associated NSSRG 1, associated NSSRG 2, …, or associated NSSRG y. Therefore, the method and the device for managing the network slices can accurately manage the network slices according to the combined information of the S-NSSAI and the NSSRG by adopting the NSSRG-based slice rejection information. For example, S-nssaii a associates NSSRG 1 and NSSRG 2; the method comprises the steps that when a terminal device requests S-NSSAI A on NSSRG 1, the terminal device is rejected by a network device, the terminal device receives and stores NSSRG-based rejected slice information sent by the network device, wherein the NSSRG-based rejected slice information comprises information of the S-NSSAI A and NSSRG 1; after that, when the terminal device switches to NSSRG 2, the terminal device re-initiates the registration request, and since the reject slice information based on NSSRG only includes information of S-NSSAI a and NSSRG 1, but does not include information of S-NSSAI a and NSSRG 2, the terminal device may request the S-NSSAI a on NSSRG 2. Therefore, the network slice associated with the NSSRG is controlled accurately.

In some embodiments, the slicing request method provided in the embodiments of the present application further includes: and the terminal equipment records rejection slice information based on NSSRG.

The NSSRG-based slice rejection information may be sent by a network device (e.g., AMF) through a Registration response (Registration Accept) or a Configuration Update Command (Configuration Update Command), for example, the terminal device receives the Registration response or the Configuration Update Command, and the Registration response or the Configuration Update Command carries the NSSRG-based slice rejection information.

After receiving NSSRG-based reject slice information, the terminal device may update the previously saved available NSSAI, e.g., the terminal device deletes the first S-NSSAI from the available NSSAI; wherein the first S-NSSAI is an S-NSSAI associated with a first NSSRG, and the NSSRG-based reject slice information includes information of the first S-NSSAI and 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 currently Allowed S-NSSAI (among available NSSAIs) and its currently associated NSSRG group have 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 and then the S-NSSAI may be deleted.

When a subsequent terminal device initiates a registration request and fills in a registration request slice (Requested NSSAI), it may check whether the Requested S-NSSAI and the associated NSSRG are in a NSSRG-based reject slice list. If so, this S-NSSAI may not be requested, otherwise it may still be requested.

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

under the condition that the NSSRG-based rejection slice information contains the network slice to be requested and the information of the third NSSRG, the terminal equipment does not request the network slice to be requested associated with the third NSSRG; alternatively, the first and second electrodes may be,

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

For example, in the case where the NSSRG-based reject slice information includes information of the S-NSSAI to be requested and a third NSSRG, the terminal device does not request the S-NSSAI to be requested in association with the third NSSRG; alternatively, the first and second electrodes may be,

in the case that the NSSRG-based reject slice information does not include 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 empty, 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 NSSRG-based reject slice information 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 NSSRG, the requested S-NSSAI and the NSSRG information 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 slices available. If the UE does not have any NSSRG available for special reasons such as subscription information change, manual management and control, the network device may reject the registration request of the UE, where the reject reason may be that a- #7 "service 5g is unavailable.

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 initially registers in the current PLMN, at this time, the UE has no record of available slice (Allowed NSSAI) and Configured slice (Configured NSSAI) in the current PLMN, and the UE uses the Default Configured slice (Default Configured NSSAI) as a request slice (Requested NSSAI) to initiate a registration request.

S302, the AMF issues an available slice (Allowed NSSAI) in a Registration Accept (Registration Accept), configures a slice (Configured NSSAI), rejects slices (e.g., reject slice information existing in the related art and not based on NSSRG), reject slice information based on NSSRG proposed in this embodiment, and NSSRG information associated with slices. Wherein, the NSSRG-based reject slice information may be carried in the extended reject NSSAI shown in table 4.

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

S304, the UE initiates a registration request again, and based on the recorded information, when filling in a request slice (Requested NSSAI), the UE can check whether the Requested S-NSSAI and the NSSRG associated with the S-NSSAI are in NSSRG-based reject slice information; if so, not requesting the S-NSSAI; 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, UE is in register state currently, some or some originally available NSSRG is to be changed to be unavailable, AMF issues Configuration Update Command (Configuration Update Command) to UE, wherein the Configuration Update Command carries rejection slice information based on NSSRG to be updated. The NSSRG-based reject slice information may be updated in an additive manner, that is, the AMF issues a new NSSRG-based reject slice list, and a new unavailable NSSRG record may be added on the last time basis.

S402, the UE receives and records the NSSRG-based rejected slice information, and similarly, the UE may also adopt an add-type recording mode during recording, that is, add new NSSRG-based rejected slice information on the basis of the original record. And, the UE checks whether each current Allowed S-NSSAI, and its current associated NSSRG group, has been rejected. If so, it is deleted from the Allowed NSSAI. If the S-NSSAI has associated an active PDU session, the PDU session needs to be released locally first.

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

(1) Filling out the configuration slices (Configured NSSAI) under the current PLMN, wherein the slices of the associated NSSRG which are not rejected yet;

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

For example, assuming that the UE initiates an update registration request under NSSRGA, the configuration slice under the current PLMN includes S-NSSAI 1, S-NSSAI 2, S-NSSAI 3. According to the step (1), the UE searches whether the information of NSSRG A and S-NSSAI 1 is in the currently stored rejection slice information based on NSSRG, if the information of NSSRG A and S-NSSAI 1 is not in the rejection slice information based on NSSRG, the UE can initiate an update registration request under NSSRG A, and the update registration request carries the identification of S-NSSAI 1; if the information of NSSRG A and S-NSSAI 1 is in NSSRG-based reject slice information, the UE can further search the information of NSSRG A and S-NSSAI 2; if the NSSRG a and S-NSSAI 1 information, the NSSRG a and S-NSSAI 2 information, and the NSSRG a and S-NSSAI 3 information are not included in the NSSRG-based reject slice information, the UE may perform step (2), continue to search for a slice that is not rejected from a Default Configured slice (Default Configured NSSAI) and initiate an update registration request, where the search mode may refer to step (1), and is not described herein again.

The above describes an implementation manner in which the terminal device receives and stores NSSRG-based rejected slice information when an originally available NSSRG is changed to be unavailable. Specifically, an updated adding mode may be adopted, and the terminal device receives and records new NSSRG-based reject slice information. In the case that an originally unavailable NSSRG is to be changed to be available, the embodiment of the present application may delete all originally stored NSSRG-based rejected slice information, and receive and record new NSSRG-based rejected slice information.

In some embodiments, the slicing request method provided in the embodiments of the present application further includes:

the method comprises the steps that terminal equipment receives a configuration updating command for notifying the change of network slice subscription information;

the terminal device empties the NSSRG-based reject slice information. 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 updating registration request, and the terminal equipment receives NSSRG-based slice rejection information.

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, where the Configuration Update Command is used for changing Network slice subscription information (Network slice subscription change), and 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 the new available slice (Allowed NSSAI) and the new NSSRG-based reject slice list in the registration response.

S504, the UE receives and records the aforementioned information, such as a new available slice (Allowed NSSAI) and a 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 after the terminal device changes the PLMN, the current NSSRG-based reject slice information is deleted. After that, the terminal device may wait for the AMF to issue a new list, for example, the terminal device re-initiates the registration request, and the AMF issues new NSSRG-based reject slice information in the registration response.

In some embodiments, in the case where the terminal device is unregistered, the terminal device deletes NSSRG-based reject slice information. For example, the terminal device deletes the currently stored rejected slice list based on NSSRG when the terminal device is turned off, restarted, enters into an airplane mode, pulls out a USIM card, or the network initiates deregistration. After that, the terminal device may wait for the AMF to issue a new list, for example, the terminal device re-initiates the registration request, and the AMF issues new NSSRG-based reject slice information in the registration response.

The embodiment of the present application also provides a slice configuration method, which may be optionally applied to the system shown in fig. 1, but is not limited thereto. 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 part of the following.

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

The network device may include an AMF.

The network device sends rejection slice information based on NSSRG to the terminal device, wherein the rejection slice information based on NSSRG may include combination information of a plurality of slice information and NSSRG, and is used for the terminal device to request network slices according to the rejection slice information based on NSSRG, so that accurate management of network slices based on NSSRG is achieved.

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

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

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

In some embodiments, the network device sends NSSRG-based reject slice information, including:

and the network equipment sends a registration response or a configuration update command, and the rejection slice information based on the NSSRG is carried with the registration response or the configuration update command.

In some embodiments, when a 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 above mode, when the NSSRG is changed from the original available state to the unavailable state, the network equipment can issue new NSSRG-based slice rejection information in an adding type 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 change.

By adopting the above mode, when the NSSRG is changed from the original unavailable state to the available state, the network device may notify the UE to delete the originally stored NSSRG-based slice rejection information, and then re-issue the new NSSRG-based slice rejection information.

In some embodiments, the method further comprises: in the presence of new NSSRG-based reject slice information, the network device sends the new NSSRG-based reject slice information.

For a specific example of the method 600 executed by the network device in this embodiment, reference may be made to the related description of the network device in the method 200, and for brevity, no further description is provided here.

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:

a slice request module 710 for requesting a network slice based on the reject slice information of the network slice concurrent registration group (NSSRG).

In some embodiments, NSSRG-based reject slice information is configured by a network device.

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

In some embodiments, the extended reject slice information includes extended reject Network Slice Selection Assistance Information (NSSAI), and a list type of the extended reject NSSAI has a first value.

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

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

a receiving and information maintaining module 820 for receiving and recording the 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 reception and information maintenance module 820 is further configured to delete the first S-NSSAI from the available NSSAI; wherein the first S-NSSAI is S-NSSAI associated with the first NSSRG, and the NSSRG-based reject slice information includes information of 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 NSSRG-based reject slice information 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 network slicing subscription information, and clear the NSSRG-based slice rejection information.

In some embodiments, a 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 a case that the terminal device 800 changes the PLMN.

In some embodiments, further comprising:

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

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

when the reject slice information based on the NSSRG includes the information of the network slice to be requested and the third NSSRG, not requesting the network slice to be requested associated with the third NSSRG; alternatively, the first and second electrodes may be,

and in the case that the information of the network slice to be requested and the third NSSRG is not contained in the NSSRG-based rejection slice information, requesting the network slice to be requested associated with the third NSSRG.

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

requesting no S-NSSAI to be requested associated with the third NSSRG in the case where the NSSRG-based reject slice information includes information of the S-NSSAI to be requested and the third NSSRG; alternatively, the first and second electrodes may be,

and requesting the S-NSSAI to be requested related to the third NSSRG under the condition that the rejection 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 800 of the embodiment of the present application can implement the corresponding function of the terminal device in the foregoing method embodiment. The corresponding processes, functions, implementation manners and beneficial effects of the modules (sub-modules, units or components, etc.) in the terminal device 800 may refer to the corresponding descriptions in the above method embodiments, and are not described herein again. It should be noted that the functions described in relation to the respective modules (sub-modules, units, or components, etc.) in the terminal device 700 and the terminal device 800 in the embodiments of the application may be implemented by different modules (sub-modules, units, or components, etc.), or may be implemented by the same module (sub-modules, units, or 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 reject slice information includes an extended reject NSSAI, and a value of a list type of the extended reject NSSAI is 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 a 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 the reject slice information based on the fourth NSSRG.

In some embodiments, in a case that 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 change.

In some embodiments, the sending module 910 is further configured to send new NSSRG-based reject slice information in the presence of the new NSSRG-based reject slice information.

In some embodiments, network device 900 includes an AMF.

The network device 900 in the embodiment of the present application can implement the corresponding function of the network device in the foregoing method embodiment. The corresponding processes, functions, implementation manners and beneficial effects of the modules (sub-modules, units or components, etc.) in the network device 900 may refer to the corresponding descriptions in the above method embodiments, and are not described herein again. It should be noted that the functions described in relation to 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, or components, etc.).

Fig. 10 is a schematic configuration diagram of a communication apparatus 1000 according to an embodiment of the present application. The communication device 1000 includes a processor 1010, and the processor 1010 can call and run a computer program from a memory to make the communication device 1000 implement the method in the embodiment of the present application.

In one implementation, the communication device 1000 may also include memory 1020. From the memory 1020, the processor 1010 may call and execute a computer program to make the communication device 1000 implement the method in the embodiment 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 specifically, may transmit information or data to the other devices or receive information or data transmitted by the other devices.

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

In an implementation manner, the communication device 1000 may be a network device in this embodiment, and the communication device 1000 may implement a corresponding process implemented by the network device in each method in this embodiment, which is not described herein again for brevity.

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

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

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

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 other devices or chips.

In one embodiment, the chip 1100 may also include an output interface 1140. 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 the other devices or chips.

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

In an implementation manner, the chip may be applied to the terminal device in this embodiment, and the chip may implement a corresponding process implemented by the terminal device in each method in this embodiment, which is not described herein again 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 mentioned in the embodiments of the present application may also be referred to as a system-on-chip, a system-on-chip or a system-on-chip, etc.

The aforementioned processors may be general purpose processors, digital Signal Processors (DSPs), field Programmable Gate Arrays (FPGAs), application Specific Integrated Circuits (ASICs), or other programmable logic devices, transistor logic devices, discrete hardware components, etc. The general purpose processor mentioned above may be a microprocessor or any conventional processor etc.

The above-mentioned memories may be either volatile or nonvolatile memories, or may include both volatile and nonvolatile memories. The non-volatile 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. Volatile memory can be Random Access Memory (RAM).

It should be understood that the above memories are exemplary but not limiting illustrations, for example, the memories in the embodiments of the present application may also be Static Random Access Memory (SRAM), dynamic random access memory (dynamic RAM, DRAM), synchronous Dynamic Random Access Memory (SDRAM), double data rate SDRAM (DDR SDRAM), enhanced SDRAM (enhanced SDRAM, ESDRAM), synchronous Link DRAM (SLDRAM), direct Rambus RAM (DR RAM), and the like. That is, the memory in the 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.

The terminal device 1210 may be configured to implement corresponding functions implemented by the terminal device in the foregoing methods, and the network device 1220 may be configured to implement corresponding functions implemented by the network device in the foregoing methods. For brevity, no further description is provided herein.

In the above embodiments, the implementation may be wholly or partially realized 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 loaded and executed on a computer, produce, in whole or in part, the procedures or functions according to the embodiments of the application. The computer may be a general purpose computer, a special purpose computer, a network of computers, or other programmable device. The computer instructions may be stored on a computer readable storage medium or transmitted from one computer readable storage medium to another, for example, from one website, computer, server, or data center to another website, computer, server, or data center via wire (e.g., coaxial cable, fiber optic, digital Subscriber Line (DSL)) or wireless (e.g., infrared, wireless, microwave, etc.). The computer-readable storage medium can be any available medium that can be accessed by a computer or a data storage device, such as a server, a data center, etc., that includes one or more available media. The usable medium may be a magnetic medium (e.g., floppy Disk, hard Disk, magnetic tape), an optical medium (e.g., DVD), or a semiconductor medium (e.g., solid State Disk (SSD)), among others.

It should be understood that, in the various embodiments of the present application, the sequence numbers of the above-mentioned processes do not imply any order of execution, and the order of execution of the processes should be determined by their functions and inherent logic, and should not constitute any limitation to the implementation process of the embodiments of the present application.

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

The above description is only for the specific embodiments of the present application, but the scope of the present application is not limited thereto, and any person skilled in the art can easily conceive of the changes or substitutions within the technical scope of the present application, and shall be covered by the 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:

and the terminal equipment requests the network slice according to the slice rejection information based on the network slice concurrent registration group.

2. The method of claim 1, wherein the network slice co-registration group based reject slice information 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 reject slice information comprises extended reject network slice selection assistance information, a value of a list type of the extended reject network slice selection assistance information being a first value.

5. The method according to any of claims 1-4, wherein the network slice co-registration group based rejection slice information comprises network slice selection assistance information based on a single network slice of a network slice co-registration group.

6. The method according to any one of claims 1-5, further comprising: and the terminal equipment receives and records the slice rejection information based on the network slice concurrent registration group.

7. The method of claim 6, wherein the receiving, by the terminal device, the network slice co-registration group-based reject slice information comprises:

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

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

the terminal device deletes the first single network slice selection assistance information from the available network slice selection assistance information; wherein the first single network slice selection assistance information is single network slice selection assistance information associated with a first network slice concurrent registration group, and the network slice concurrent registration group-based reject slice information includes the first single network slice selection assistance information and information of the first network slice concurrent registration group.

9. The method of claim 8, further comprising:

and in the case that the available network slice selection assistance information is emptied, the terminal device initiates an update registration request, and requests, in the update registration request, second single network slice selection assistance information associated with a second network slice concurrent registration group, where the network slice concurrent registration group-based reject slice information does not include the second single network slice selection assistance information and information of the second network slice concurrent registration group.

10. The method according to any one of claims 1-8, further comprising:

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

and the terminal equipment clears the slice rejection information based on the network slice concurrent registration group.

11. The method of claim 10, further comprising:

the terminal equipment initiates an updating registration request;

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

12. The method according to any one of claims 1-8, further comprising:

and under the condition that the PLMN is replaced by the terminal equipment, deleting the slice rejection information based on the network slice concurrent registration group by the terminal equipment.

13. The method according to any one of claims 1-8, further comprising:

and under the condition that the terminal equipment is unregistered, the terminal equipment deletes the slice rejection information based on the network slice concurrent registration group.

14. The method according to any one of claims 1 to 13, wherein the requesting, by the terminal device, the network slice according to the network slice co-registration group-based reject slice information includes:

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 to associate the network slice to be requested of the third network slice concurrent registration group; alternatively, the first and second electrodes may be,

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 a 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.

15. The method of claim 14, wherein the requesting, by the terminal device, the network slice according to the network slice co-registration group-based reject slice information comprises:

when the slice rejection information based on the network slice concurrent registration group includes the single network slice selection auxiliary information to be requested and the information of the third network slice concurrent registration group, the terminal device does not request the single network slice selection auxiliary information to be requested in association with the third network slice concurrent registration group; alternatively, the first and second electrodes may be,

and under the condition that the rejected slice information based on the network slice concurrent registration group does not contain the single network slice selection auxiliary information to be requested and the information of the third network slice concurrent registration group, the terminal equipment requests the single network slice selection auxiliary information to be requested, which is associated with the third network slice concurrent registration group.

16. A slice configuration method, comprising:

the network device sends reject slice information based on the network slice concurrent registration group.

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

18. The method of claim 17, wherein the extended reject slice information comprises extended reject network slice selection assistance information, a list type of the extended reject network slice selection assistance information having a first value.

19. The method according to any of claims 16-18, wherein the network slice co-registration group based reject slice information comprises single network slice selection assistance information of an associated network slice co-registration group.

20. The method of any of claims 16-19, wherein the network device sending network slice concurrency registration group based reject slice information comprises:

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

21. The method of claim 20, wherein when a fourth network slice concurrent registration group of a 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 slice rejection information based on the fourth network slice concurrent registration group.

22. The method of claim 20, wherein in a case that 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.

23. The method according to any of claims 16-20, further comprising: the network device sends rejection slice information of a new network slice co-registration group when the rejection slice information of the new network slice co-registration group exists.

24. The method according to any of claims 16-23, wherein the network device comprises an access and mobility management function network element, AMF.

25. A terminal device, comprising:

and the slicing request module is used for requesting the network slices based on the slicing rejection information of the network slice concurrent registration group.

26. The terminal device of claim 25, wherein the network slice co-registration group based reject slice information is configured by a network device.

27. The terminal device of claim 26, wherein the network slice co-registration group-based reject slice information is carried in extended reject slice information.

28. The terminal device of claim 27, wherein the extended reject slice information comprises extended reject network slice selection assistance information, a list type of the extended reject network slice selection assistance information having a first value.

29. The terminal device according to any of claims 25-28, wherein the network slice co-registration group based reject slice information comprises network slice selection assistance information for a single network slice of a network slice co-registration group.

30. The terminal device of any of claims 25-29, further comprising:

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

31. The terminal device of claim 30,

the receiving and information maintaining module is configured to receive a registration response or a configuration update command, where the registration response or the configuration update command carries the slice rejection information based on the network slice concurrent registration group.

32. The terminal device of claim 30 or 31,

the receiving and information maintaining module is further configured to delete the first single network slice selection assistance information from the available network slice selection assistance information; the first single network slice selection auxiliary information is single network slice selection auxiliary information associated with a first network slice concurrent registration group, and the network slice concurrent registration group-based rejection slice information includes the first single network slice selection auxiliary information and information of the first network slice concurrent registration group.

33. The terminal device of claim 32, wherein,

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

34. The terminal device of any of claims 25-32,

and the receiving and information maintaining module is used for receiving a configuration updating command for notifying the change of the network slicing subscription information and emptying the slicing rejection information based on the network slicing concurrence registration group.

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

36. The terminal device of any of claims 25-32, further comprising:

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

37. The terminal device of any of claims 25-32, further comprising:

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

38. The terminal device of any of claims 25-37, wherein the slicing request module is to:

when 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, not requesting to associate the network slice to be requested of the third network slice concurrent registration group; alternatively, the first and second electrodes may be,

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 a third network slice concurrent registration group, requesting to associate the network slice to be requested of the third network slice concurrent registration group.

39. The terminal device of claim 38, wherein the slicing request module is to:

when the slice rejection information based on the network slice concurrent registration group includes the single network slice selection auxiliary information to be requested and information of a third network slice concurrent registration group, not requesting the single network slice selection auxiliary information to be requested associated with the third network slice concurrent registration group; alternatively, the first and second electrodes may be,

requesting the single network slice selection auxiliary information to be requested associated with a third network slice concurrent registration group when the slice rejection information based on the network slice concurrent registration group does not include the single network slice selection auxiliary information to be requested and information of the third network slice concurrent registration group.

40. A network device, comprising:

and the sending module is used for sending the slice rejection information based on the network slice concurrent registration group.

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

42. The network device of claim 41, wherein the extended reject slice information comprises extended reject network slice selection assistance information, a list type of the extended reject network slice selection assistance information having a first value.

43. The network device of any of claims 40-42, wherein the network slice co-registration group-based reject slice information comprises single network slice selection assistance information of an associated network slice co-registration group.

44. The network device of any of claims 40-43,

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 the slice rejection information based on the network slice concurrent registration group.

45. The network device of claim 44, wherein, when a fourth network slice concurrent registration group of a terminal device is changed from available to unavailable, the sending module sends a configuration update command to the terminal device, where the configuration update command carries slice rejection information based on the fourth network slice concurrent registration group.

46. The network device of claim 44, wherein the sending module sends a configuration update command to the terminal device in case that a fifth network slice concurrent registration group of the terminal device is changed from unavailable to available, the configuration update command being used to notify a network slice subscription information change.

47. The network device of any of claims 40-44,

the sending module is further configured to send the new rejection slice information based on the network slice concurrent registration group when the new rejection slice information based on the network slice concurrent registration group exists.

48. A network device as claimed in any of claims 40 to 47, wherein the network device comprises access and mobility management functions.

49. An apparatus, comprising: a processor, a memory for storing a computer program, and a transceiver, the processor for invoking and executing the computer program stored in the memory and controlling the transceiver to cause the apparatus to perform the method of any of claims 1-15 or 16-24.

50. A chip, comprising: a processor for calling and running a computer program from a memory so that a device on which the chip is installed performs the method of any of claims 1 to 15 or 16-24.

51. A computer-readable storage medium storing a computer program which, when executed by an apparatus, causes the apparatus to perform the method of any one of claims 1 to 15 or 16-24.

52. A computer program product comprising computer program instructions to cause a computer to perform the method of any one of claims 1 to 15 or 16-24.

53. A computer program for causing a computer to perform the method of any one of claims 1 to 15 or 16-24.

54. A communication system, comprising:

a terminal device for performing the method of any one of claims 1 to 15;

network device for performing the method of any of claims 16 to 24.