CN115412434A - Slicing request method and terminal equipment - Google Patents

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

A slice request method and terminal equipment

technical field

The present application relates to the communication field, and more specifically, to a slice request method and a terminal device.

Background technique

The fifth generation mobile communication technology (5G, 5th Generation Mobile Communication Technology) system introduces a new feature of network slicing (Network Slicing), which is also a representative function of the 5G system; its purpose is to By dividing different network slices, different network resources, such as bandwidth, rate, and service quality, are allocated respectively, so that different service requirements can occupy network resources more reasonably. When a terminal device initiates registration in the network, it needs to first request network slicing; how the terminal device requests network slicing is a technical problem that needs to be solved.

Contents of the invention

Embodiments of the present application provide a slice request method and a terminal device for requesting network slices.

An embodiment of the present application provides a slice request method, including: a terminal device requests a network slice according to slice rejection information based on a Network Slice Concurrent Registration Group (NSSRG).

An embodiment of the present application provides a slice configuration method, including: a network device sends slice rejection information based on a network slice concurrent registration group.

An embodiment of the present application provides a terminal device, including: a slice request module, configured to request a network slice based on slice rejection information of a network slice concurrent registration group.

An embodiment of the present application provides a network device, including: a sending module, configured to send slice rejection information based on concurrent registration groups of network slices.

An embodiment of the present application provides a device, including a processor and a memory. The memory is used to store computer programs, and the processor is used to invoke and run the computer programs stored in the memory, so that the device executes the above method.

An embodiment of the present application provides a chip configured to implement the foregoing method.

Specifically, the chip includes: a processor, configured to call and run a computer program from the memory, so that the device installed with the chip executes the above method.

An embodiment of the present application provides a computer-readable storage medium for storing a computer program, and when the computer program is run by a device, the device is made to execute the above method.

An embodiment of the present application provides a computer program product, including computer program instructions, where the computer program instructions cause a computer to execute the foregoing method.

An embodiment of the present application provides a computer program that, when running on a computer, causes the computer to execute the above method.

In this embodiment of the present application, the terminal device can request network slicing based on NSSRG-based slice rejection information, so as to implement a network slicing request in units of NSSRGs, request network slices associated with NSSRGs, and implement precise requests for network slicing.

Description of drawings

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

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

Fig. 3 is the implementation flow chart according to Embodiment 1 of the present application;

Fig. 4 is the realization flow chart according to embodiment 2 of the present application;

Fig. 5 is the realization flowchart according to embodiment 3 of the present application;

FIG. 6 is a schematic flowchart 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 device 1000 according to an embodiment of the present application;

FIG. 11 is a schematic structural 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 ways

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 present application can be applied to various communication systems, such as: Global System of Mobile communication (Global System of Mobile communication, GSM) system, 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 (GPRS), Long Term Evolution (LTE) system, Advanced long term evolution (LTE-A) system, new wireless (New Radio, NR) system, evolution system of NR system, LTE (LTE-based access to unlicensed spectrum, LTE-U) system on unlicensed spectrum, NR (NR-based access to unlicensed spectrum, NR- U) system, Non-Terrestrial Networks (NTN) system, Universal Mobile Telecommunication System (UMTS), Wireless Local Area Networks (WLAN), Wireless Fidelity (WiFi) , the fifth generation communication (5th-Generation, 5G) system or other communication systems, etc.

Generally speaking, the number of connections supported by traditional communication systems is limited and easy to implement. However, with the development of communication technology, mobile communication systems will not only support traditional communication, but also support, for example, Device to Device (D2D ) communication, machine to machine (Machine to Machine, M2M) communication, machine type communication (Machine Type Communication, MTC), vehicle to vehicle (Vehicle to Vehicle, V2V) communication, or vehicle networking (Vehicle to everything, V2X) communication, etc., this application Embodiments are also applicable 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 (CarrierAggregation, CA) scenario, may also be applied to a dual connectivity (Dual Connectivity, DC) scenario, and may also be applied to an independent (Standalone, SA ) meshing scene.

In one embodiment, the communication system in the embodiment of the present application can be applied to an unlicensed spectrum, where the unlicensed spectrum can also be considered as a shared spectrum; or, the communication system in the embodiment of the present application can also be applied to a licensed spectrum , where the licensed spectrum can also be considered as a non-shared spectrum.

The embodiments of the present application describe various embodiments in conjunction with network equipment and terminal equipment, where the terminal equipment may also be referred to as user equipment (User Equipment, UE), access terminal, user unit, user station, mobile station, mobile station, remote station, remote terminal, mobile device, user terminal, terminal, wireless communication device, user agent or user device, etc.

The terminal device can be a station (STAION, ST) in the WLAN, and can be a cellular phone, a cordless phone, a Session Initiation Protocol (Session Initiation Protocol, SIP) phone, a wireless local loop (Wireless Local Loop, WLL) station, a personal digital processing (Personal Digital Assistant, PDA) devices, handheld devices with wireless communication functions, computing devices or other processing devices connected to wireless modems, vehicle-mounted devices, wearable devices, next-generation communication systems such as terminal devices in NR networks, or future A terminal device and the like in an evolved public land mobile network (Public LandMobile Network, PLMN) network.

In the embodiment of this application, the terminal device can be deployed on land, including indoor or outdoor, handheld, wearable or vehicle-mounted; it can also be deployed on water (such as ships, etc.); it can also be deployed in the air (such as aircraft, balloons and satellites) superior).

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 transceiver function, a virtual reality (Virtual Reality, VR) terminal device, an augmented reality (AugmentedReality, AR) terminal device , wireless terminal devices in industrial control, wireless terminal devices in self driving, wireless terminal devices in remote medical, wireless terminal devices in smart grid, Wireless terminal equipment in transportation safety, wireless terminal equipment in smart city, or wireless terminal equipment in smart home.

As an example but not a limitation, in this embodiment of the present application, the terminal device may also be a wearable device. Wearable devices can also be called wearable smart devices, which is a general term for the application of wearable technology to intelligently design daily wear and develop wearable devices, such as glasses, gloves, watches, clothing and shoes. A wearable device is a portable device that is worn directly on the body or integrated into the user's clothing or accessories. Wearable devices are not only a hardware device, but also achieve powerful functions through software support, data interaction, and cloud interaction. Generalized wearable smart devices include full-featured, large-sized, complete or partial functions without relying on smart phones, such as smart watches or smart glasses, etc., and only focus on a certain type of application functions, and need to cooperate with other devices such as smart phones Use, such as various smart bracelets and smart jewelry for physical sign monitoring.

In the embodiment of the present application, the network device may be a device used to communicate with the mobile device, and the network device may be an access point (Access Point, AP) in WLAN, a base station (Base Transceiver Station, BTS) in GSM or CDMA , it can also be a base station (NodeB, NB) in WCDMA, or an evolved base station (EvolutionalNode B, eNB or eNodeB) in LTE, or a relay station or access point, or in-vehicle devices, wearable devices, and NR networks The network equipment (gNB) or the network equipment in the future evolved PLMN network or the network equipment in the NTN network, etc.

As an example but not a limitation, in this embodiment of the present application, the network device may have a mobile feature, for example, the network device may be a mobile device. Optionally, the network equipment may be a satellite or a balloon station. For example, the satellite may be a low earth orbit (low earth orbit, LEO) satellite, a medium earth orbit (medium earth orbit, MEO) satellite, a geosynchronous earth orbit (geostationary earth orbit, GEO) satellite, a high elliptical orbit (High Elliptical Orbit, HEO) satellite. ) Satellite etc. Optionally, the network device may also be a base station installed on land, water, and other locations.

In this embodiment of the present application, the network device may provide services for a cell, and the terminal device communicates with the network device through the transmission resources (for example, frequency domain resources, or spectrum resources) used by the cell, and the cell may be a network device ( For example, a cell corresponding to a base station), the cell may belong to a macro base station, or may belong to a base station corresponding to a small cell, where the small cell may include: a metro cell, a micro cell, a pico cell ( Pico cell), Femto cell, etc. These small cells have the characteristics of small coverage and low transmission power, and are suitable for providing high-speed data transmission services.

FIG. 1 exemplarily shows a communication system 100 . The communication system includes a network device 110 and two terminal devices 120 . In an implementation manner, the communication system 100 may include multiple network devices 110, and the coverage of each network device 110 may include other numbers of terminal devices 120, which is not limited in this embodiment of the present application.

In one embodiment, the communication system 100 may also include other network entities such as a mobility management entity (MobilityManagement Entity, MME), an access and mobility management function (Access and Mobility ManagementFunction, AMF). This is not limited.

Wherein, the network equipment may further include access network equipment and core network equipment. That is, the wireless communication system also includes multiple core networks for communicating with access network devices. The access network equipment may be a long-term evolution (long-termevolution, LTE) system, a next-generation (mobile communication system) (next radio, NR) system or an authorized auxiliary access long-term evolution (authorized auxiliary access long-term evolution, LAA-LTE ) system in the evolved base station (evolutional node B, referred to as eNB or e-NodeB) macro base station, micro base station (also called "small base station"), pico base station, access point (access point, AP), transmission A station (transmission point, TP) or a new generation base station (new generation Node B, gNodeB), etc.

It should be understood that a device with a communication function in the network/system in the embodiment of the present application may be referred to as a communication device. Taking the communication system shown in Figure 1 as an example, the communication equipment may include network equipment and terminal equipment with communication functions. It may include other devices in the communication system, such as network controllers, mobility management entities 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 often used interchangeably herein. The term "and/or" in this article is just an association relationship describing associated objects, which means that there can be three relationships, for example, A and/or B can mean: A exists alone, A and B exist simultaneously, and there exists alone B these three situations. In addition, the character "/" in this article generally indicates that the contextual objects are an "or" relationship.

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

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

In order to facilitate the understanding of the technical solutions of the embodiments of the present application, the related technologies of the embodiments of the present application are described below. The following related technologies can be combined with the technical solutions of the embodiments of the present application as optional solutions, and all of them belong to the embodiments of the present application. protected range.

The 5G system introduces a new feature of network slicing (Network Slicing), which is also a representative function of the 5G system. Its purpose is to allocate different network resources, such as bandwidth, rate, and service quality, by dividing different network slices in the same network environment, so that different service requirements can occupy network resources more reasonably.

When a UE initiates registration on a public land mobile network (PLMN, public land mobile network), the UE needs to select auxiliary information (Allowed NSSAI, Allowed Network Slice Selection Assistance Information)) and configured slice information (such as configured NSSAI (Configured NSSAI)), or default configured slice information (such as default configured NSSAI (Default Configured NSSAI)), exclude rejected slices Information (such as rejected NSSAI (Rejected NSSAI)), combined with the UE's own policy, carries the information requested by the UE in the non-access stratum (NAS, Non-Access-Stratum) message of the registration request (such as the registration request (Registration Request)) Slicing information (such as the requested NSSAI (Requested NSSAI)) to the network. According to the requested slice information, the network confirms the configuration slice information (such as configured NSSAI), available slice information (such as available NSSAI) and rejected slice information (such as rejected NSSAI) of the UE under the current network, and responds to These information are configured to the UE in the NAS message (eg, Registration Accept) of the request. All of the above NSSAIs may contain one or more single network slice selection auxiliary information (S-NSSAI, Single NSSAI). Afterwards, the UE can select a specific S-NSSAI available under the current network to initiate a data session according to the configuration information and its own policy.

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

The definition of this information in the agreement is shown in Table 1:

Table 1-NSSRG configuration information definition

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

Table 2-S-NSSAI associated NSSRG value definition

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

The NSSRG information is associated with the configured slice (Configured NSSAI) under the current network, that is, all S-NSSAIs configured under the current network can be associated with one or more NSSRGs. The available slices (such as available NSSAIs) are a subset of the current network configuration slices, so each available S-NSSAI is associated with one or more NSSRGs.

The slice requested by the user when registering is generally associated with the same NSSRG. Therefore, after each successful registration on the network side, the available slices allocated to the user will be associated with the same NSSRG. Each data session initiated by the user can also be associated with a specific A certain NSSRG. Use NSSRG to implement classified management of user slice configurations. Based on specific implementation strategies, you can confirm which associated slices users can use on a specific NSSRG, and then configure corresponding available slices (such as Allowed NSSAI) to users. A data session can only be initiated on the corresponding associated NSSRG. Different users can only use the available slices associated with their available NSSRGs according to their different subscription information, and will not access slices associated with other NSSRGs, thus realizing further refined management of network slices.

The main disadvantage of the existing slice request process lies in the following scenarios:

The current slice rejection definition is still based on S-NSSAI, that is, slice requests can only be rejected according to the specific S-NSSAI. If an S-NSSAI is associated with multiple NSSRGs, if the network rejects it within the framework of the current protocol, it cannot reject it based on the NSSRG.

For example, if a user subscribes to two NSSRGs: Group 1 and Group 2, the current terminal requests slices on Group 1 but not on Group 2 when registering; if the requested S-NSSAI is associated with both Group 1 and Group 2 For group 2, when the network side rejects the slice request, it will reject all S-NSSAI, which results in the end user's available slices on group 2 being also rejected. Subsequently, if the user switches to group 2, re-initiates registration and requests slices, the S-NSSAI on group 2 requested by the user will exclude the previously rejected S-NSSAI, so the number of slices currently requested on group 2 must be The number of slices that is smaller than the actual number of slices that can be requested by group 2, that is, the S-NSSAI that was rejected when the slice request was initiated on group 1 cannot be requested on group 2. It can be seen that the existing request and rejection slices are implemented in units of S-NSSAI, and fine management of slices based on NSSRG is not actually implemented.

Fig. 2 is a schematic flowchart of a slice request method 200 according to an embodiment of the present application. The method can optionally be applied to the system shown in Fig. 1, but is not limited thereto. The method includes at least some of the following.

S210. The terminal device requests network slicing according to the NSSRG-based slicing rejection information.

By requesting network slicing according to NSSRG-based slicing rejection information, the embodiment of the present application can realize accurate management and requesting network slicing based on NSSRG.

The slice rejection information based on the NSSRG can be configured by the network side, for example, by the AMF.

In some implementations, the NSSRG-based rejected slice information is carried in the extended rejected slice information. For example, the extended rejected slice information may be extended rejected network slice selection auxiliary information (Extended RejectedNSSAI).

The format of the extended rejection network slice selection auxiliary information is shown in Table 3:

Table 3 - Extended Deny NSSAI

The extended rejected slice information (such as extended rejected NSSAI) may carry one or more rejected slice information based on NSSRG, wherein the rejected slice information based on NSSRG may be S-NSSAI based on NSSRG.

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

Table 4

In some implementations, the value of the extended rejection NSSAI list type (Type of list) shown in Table 4 is the first value, which is used to indicate that the extended rejection NSSAI is an extended rejection NSSAI carrying NSSRG-based rejected slice information. In related technologies, two types of extended rejection NSSAI have been defined, one of which is a list of rejection of S-NSSAI, and the value of the list type (Type of list) is 000; the other is an increase of a fallback timer The duration extension rejects the NSSAI, whose Type of list has a value of 001. In order to distinguish it from the existing extended rejection NSSAI, in the extended rejection NSSAI carrying NSSRG-based rejection slice information proposed in the embodiment of this application, the value of the list type (Type of list) (that is, the above-mentioned first value) can be other than the aforementioned 000 and values other than 001, for example, the first value is 010.

As shown in Table 4, the extended reject NSSAI proposed by the embodiment of the present application carries one or more rejected S-NSSAI (Rejected S-NSSAI with NSSRG) based on NSSRG. Taking the NSSRG-based rejection S-NSSAI 1 (Rejected S-NSSAI 1 with NSSRG) in Table 4 as an example, in some implementations, its content is as shown in Table 5:

table 5

As shown in Table 5, Table 5 contains the information of S-NSSAI 1 and multiple NSSRG values, indicating that S-NSSAI 1 is rejected when it is associated with NSSRG 1, associated with NSSRG 2, ... or associated with NSSRG y. It can be seen that the embodiment of the present application adopts NSSRG-based slice rejection information, and can implement accurate management of network slices according to combined information of S-NSSAI and NSSRG. For example, S-NSSAI A is associated with NSSRG 1 and NSSRG 2; when a terminal device requests S-NSSAI A on NSSRG 1, it is rejected by the network device, and the terminal device receives and saves the NSSRG-based rejection slice information sent by the network device. The rejected slice information includes the information of S-NSSAI A and NSSRG 1; later, when the terminal device switches to NSSRG 2, it re-initiates the registration request, because the rejected slice information based on NSSRG only contains the information of S-NSSAI A and NSSRG 1 , but does not contain the information of S-NSSAIA A and NSSRG 2, so the terminal device can request the S-NSSAIA A on NSSRG 2. It can be seen that the embodiment of the present application is beneficial to accurately control the network slice associated with the NSSRG.

In some implementation manners, the slice request method proposed in the embodiment of the present application further includes: a terminal device and recording NSSRG-based slice rejection information.

Among them, the NSSRG-based slice rejection information can be sent by a network device (such as AMF) through a registration response (Registration Accept) or a configuration update command (Configuration Update Command). For example, when a terminal device receives a registration response or a configuration update command, the registration response or The configuration update command carries the NSSRG-based rejected slice information.

After receiving the NSSRG-based rejection slice information, the terminal device can update the previously saved available NSSAI, for example, the terminal device deletes the first S-NSSAI from the available NSSAI; wherein, the first S-NSSAI is the associated first S-NSSAI An S-NSSAI of an NSSRG, and the NSSRG-based slice rejection information includes information about the first S-NSSAI and the first NSSRG. Wherein, the first NSSRG may be the NSSRG currently requested by the UE. Specifically, after receiving the NSSRG-based slice rejection information, the terminal device may check whether each current Allowed S-NSSAI (among available NSSAIs) and its currently associated NSSRG group have been rejected. If yes, delete the Allowed S-NSSAI from the Allowed NSSAI. If the S-NSSAI has been associated with an active PDU session (PDU Session), the PDU Session can be released first, and then the S-NSSAI can be deleted.

When the subsequent terminal device initiates a registration request, when filling in the registration request slice (Requested NSSAI), you can check whether the requested S-NSSAI and the associated NSSRG are in the NSSRG-based rejection slice list. If yes, this S-NSSAI cannot be requested, otherwise it can still be requested.

Specifically, the terminal device requests network slicing based on NSSRG-based slice rejection information, which may include:

In the case where the information about the network slice to be requested and the third NSSRG is included in the NSSRG-based rejection slice information, the terminal device does not request the network slice to be requested associated with the third NSSRG; or,

In a case where the information about the network slice to be requested and the third NSSRG is not included in the NSSRG-based slice rejection information, the terminal device requests the network slice to be requested associated with the third NSSRG.

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

In the case that the NSSRG-based rejected slice information does not include the requested S-NSSAI and the information of the third NSSRG, the terminal device requests the requested S-NSSAI associated with the third NSSRG.

In some implementations, if the available NSSAI saved by the terminal device is cleared, the terminal device may initiate an update registration request, and request to associate the second S-NSSAI of the second NSSRG in the update registration request, wherein the slice information based on NSSRG rejection does not contain the information of the second S-NSSAI and the second NSSRG. That is to say, when a terminal device initiates a registration update request on an NSSRG, the requested S-NSSAI and the information of the NSSRG are not included in the NSSRG-based slice rejection information.

The network device (such as AMF) should try to ensure that the terminal device has at least one available NSSRG group under the current PLMN, and has associated available slices. If the UE does not have any available NSSRG due to special reasons such as subscription information changes, manual control, etc., the network device can reject the UE's registration request, and the reason for the rejection can be -#7 "5G service is not available".

Example 1:

Fig. 3 is the realization flow chart according to embodiment 1 of the present application, comprises the following steps:

S301. The UE registers for the first time under the current PLMN. At this time, the UE has no available slice (AllowedNSSAI) and configured slice (Configured NSSAI) records under the current PLMN. The UE uses the default configured slice (Default ConfiguredNSSAI) as the requested slice (Requested NSSAI) to initiate Registration Request.

S302. The AMF sends the available slice (Allowed NSSAI) in the registration response (Registration Accept), configures the slice (Configured NSSAI), and rejects the slice (such as the existing slice rejection information in the related art that is not based on NSSRG). The NSSRG-based rejected slice information proposed in the example, and the NSSRG information associated with the slice. Wherein, the slice rejection information based on NSSRG may be carried in the extended rejection NSSAI shown in Table 4.

S303. The UE records the above information delivered by the AMF. For example, the UE records available slices (Allowed NSSAI), configured slices (Configured NSSAI), rejected slices, NSSRG-based slice rejected information, and the like.

S304. The UE initiates a registration request again. Based on the information recorded above, when filling in the RequestedNSSAI, you can check whether the requested S-NSSAI and the NSSRG associated with the S-NSSAI are in the rejected slice information based on the NSSRG; if If yes, the S-NSSAI is not requested; otherwise, the S-NSSAI can be requested.

Example 2:

Fig. 4 is the realization flow chart according to embodiment 2 of the present application, comprises the following steps:

S401. The UE is currently in the registration state, and one or some previously available NSSRGs are to be changed to be unavailable, and the AMF sends a configuration update command (Configuration Update Command) to the UE, which carries NSSRG-based rejected slice information to be updated. NSSRG-based rejected slice information can be updated in an additive manner, that is, AMF issues a new NSSRG-based rejected slice list, and new unavailable NSSRG records can be added on the basis of the previous one.

S402. The UE receives and records the NSSRG-based rejected slice information. Similarly, the UE may also use an additive recording method when 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 currently associated NSSRG group have been rejected. If yes, remove it from Allowed NSSAI. If the S-NSSAI has been associated with an active PDU session, the PDU session needs to be released locally first.

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

(1) Fill in the configured slices (Configured NSSAI) under the current PLMN, those slices associated with NSSRG that have not yet been rejected;

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

For example, assume that the UE initiates a registration update request under NSSRGA, and the configuration slices under the current PLMN include S-NSSAI1, S-NSSAI2, and S-NSSAI3. According to step (1), the UE checks whether the information of NSSRG A and S-NSSAI 1 is in the currently saved NSSRG-based rejected slice information, if the information of NSSRG A and S-NSSAI 1 is not in the NSSRG-based rejected slice information, then The UE can initiate an update registration request under NSSRG A, and the update registration request carries the identity of S-NSSAI 1; if the information of NSSRG A and S-NSSAI 1 is in the NSSRG-based rejected slice information, the UE can further search for NSSRG A and S-NSSAI 2 information; if the information of NSSRG A and S-NSSAI 1, the information of NSSRG A and S-NSSAI 2, the information of NSSRG A and S-NSSAI 3 are not in the NSSRG-based rejected slice information, then UE Step (2) can be performed to continue to search for unrejected slices from the Default Configured NSSAI and initiate an update registration request. The search method can refer to the aforementioned step (1), and will not be repeated here.

The foregoing describes an implementation manner for the terminal device to receive and save NSSRG-based slice rejection information when the originally available NSSRG is changed to be unavailable. Specifically, an update-type adding method may be adopted, and the terminal device receives and records new NSSRG-based rejected slice information. In the case that the previously unavailable NSSRG is to be changed to be available, this embodiment of the present application may delete all previously stored NSSRG-based rejected slice information, and receive and record new NSSRG-based rejected slice information.

In some implementation manners, the slice request method proposed in the embodiment of the present application further includes:

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

The terminal device clears the NSSRG-based slice rejection information. Specifically, the terminal device may clear the NSSRG-based rejected slice information stored locally.

In some implementation manners, the method may further include: the terminal device initiates a registration update request, and the terminal device receives NSSRG-based slice rejection information.

Example 3:

Figure 5 is an implementation flowchart 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 network slicing subscription changed (Network slicing subscription changed), and the configuration update command (Configuration Update Command) does not carry other change information.

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

S503. The AMF sends a registration response to the UE, and carries a new available slice (AllowedNSSAI) and a new NSSRG-based rejected slice list in the registration response.

S504. The UE receives and records the aforementioned information, such as the new available slice (Allowed NSSAI), and the new NSSRG-based rejected slice list.

In some implementation manners, the NSSRG-based slice rejection information proposed in the embodiment of the present application only takes effect under the current PLMN, and when the terminal device changes the PLMN, the current NSSRG-based slice rejection information is deleted. Afterwards, the terminal device may wait for the AMF to issue a new list, for example, the terminal device re-initiates a registration request, and the AMF issues new NSSRG-based slice information in the registration response.

In some implementation manners, when the terminal device de-registers, the terminal device deletes the slice rejection information based on the NSSRG. For example, when the terminal device is turned off, restarted, enters the airplane mode, pulls out the USIM card, or initiates de-registration from the network side, the currently stored NSSRG-based rejected slice list is deleted. Afterwards, the terminal device may wait for the AMF to issue a new list, for example, the terminal device re-initiates a registration request, and the AMF issues new NSSRG-based slice information in the registration response.

The embodiment of the present application also proposes a slice configuration method, which may optionally be applied to the system shown in FIG. 1 , but is not limited thereto. Fig. 6 is a schematic flowchart of a slice configuration method 600 according to an embodiment of the present application. The method includes at least some of the following.

S610. The network device sends NSSRG-based slice rejection information.

The network device may be an AMF.

The network device sends NSSRG-based slice rejection information to the terminal device. The NSSRG-based slice rejection information may include a combination of multiple slice information and NSSRG information, which is used for the terminal device to request network slices according to the NSSRG-based slice rejection information. , so as to realize accurate management of network slicing based on NSSRG.

In some implementation manners, the rejected slice information of the NSSRG is carried in the extended rejected slice information.

In some implementations, the extension rejection slice information includes an extension rejection NSSAI, and the value of the list type of the extension rejection NSSAI is the first value. The first value is used to indicate that the extended reject NSSAI is an extended reject NSSAI carrying NSSRG rejected slice information.

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

In some implementation manners, the network device sends NSSRG-based slice rejection information, including:

The network device sends a registration response or a configuration update command, which carries the NSSRG-based slice rejection information in the registration response or configuration update command.

In some implementation manners, when 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, and the configuration update command carries the information based on the fourth NSSRG Reject slice information.

Using the above method, when NSSRG is changed from available to unavailable, the network device can issue new NSSRG-based slice rejection information in an additive update mode; UE can locally store the basis of NSSRG-based slice rejection information Above, add the new NSSRG-based rejection slice information.

In some embodiments, when 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, and the configuration update command is used to notify the network slice of subscription information change .

With the above method, when the NSSRG is changed from unavailable to available, the network device can notify the UE to delete the previously stored NSSRG-based rejected slice information, and then re-deliver new NSSRG-based rejected slice information.

In some implementation manners, the method further includes: if there is new NSSRG-based rejected slice information, the network device sends the new NSSRG-based rejected slice information.

For a specific example of the method 600 executed by the network device in this embodiment, reference may be made to the relevant description about the network device in the method 200 above, and details are not repeated here 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:

A slice requesting module 710, configured to request a network slice based on slice rejection information of a Network Slice Concurrent Registration Group (NSSRG).

In some implementations, NSSRG-based slice rejection information is configured by a network device.

In some implementations, the NSSRG-based rejected slice information is carried in the extended rejected slice information.

In some implementations, the extended rejection slice information includes extended rejection network slice selection assistance information (NSSAI), and the value of the list type of the extended rejection NSSAI is the first value.

In some embodiments, the NSSRG-based slice rejection 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 a possible implementation manner, in the embodiment of this application, it also includes:

The receiving and information maintaining module 820 is configured to receive and record the slice rejection information based on NSSRG.

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

In some implementations, the receiving and information maintenance module 820 is further configured to delete the first S-NSSAI from the available NSSAI; wherein, the first S-NSSAI is the S-NSSAI associated with the first NSSRG, and the slice is rejected based on the NSSRG The information includes the information of the first S-NSSAI and the first NSSRG.

In some implementations, the slice request module 710 is further configured to initiate an update registration request when the available NSSAI is cleared, and request the second S-NSSAI associated with the second NSSRG in the update registration request, wherein, based on the NSSRG The rejected slice information does not include the information of the second S-NSSAI and the second NSSRG.

In some implementation manners, the receiving and information maintaining module 820 is configured to receive a configuration update command for notifying the change of subscription information of the network slice, and clear the slice rejection information based on NSSRG.

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

In some embodiments, also include:

The first deletion module 830 is configured to delete slice rejection information based on the NSSRG when the terminal device 800 changes the PLMN.

In some embodiments, also include:

The second deletion module 840 is configured to delete the NSSRG-based slice rejection information when the terminal device 800 is deregistered.

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

In the case where the information about the network slice to be requested and the third NSSRG is included in the NSSRG-based rejection slice information, the network slice to be requested associated with the third NSSRG is not requested; or,

In a case where the information about the network slice to be requested and the third NSSRG is not included in the NSSRG-based slice rejection information, request the network slice to be requested associated with the third NSSRG.

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

In the case where the NSSRG-based rejection slice information includes information about the S-NSSAI to be requested and the third NSSRG, do not request to associate the S-NSSAI to be requested with the third NSSRG; or,

If the NSSRG-based rejected slice information does not include the information about the requested S-NSSAI and the third NSSRG, request the associated third NSSRG with the requested S-NSSAI.

The terminal device 800 in the embodiment of the present application can implement the corresponding functions of the terminal device in the foregoing method embodiments. For the processes, functions, implementations and beneficial effects corresponding to each module (submodule, unit or component, etc.) in the terminal device 800, refer to the corresponding description in the above method embodiment, and details are not repeated here. It should be noted that the functions described by the modules (submodules, units or components, etc.) in the terminal device 700 and the terminal device 800 in the embodiment of the application may be implemented by different modules (submodules, units or components, etc.), or Can be realized by the same module (submodule, unit or component, 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:

The sending module 910 is configured to send NSSRG-based slice rejection information.

In some implementations, the NSSRG-based rejected slice information is carried in the extended rejected slice information.

In some implementations, the extension rejection slice information includes the extension rejection NSSAI, and the value of the list type of the extension rejection NSSAI is the first value.

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

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

In some implementations, when 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 slice rejection information based on the fourth NSSRG.

In some implementations, when the fifth NSSRG of the terminal device changes 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 of subscription information change.

In some implementations, the sending module 910 is further configured to, if there is new NSSRG-based rejected slice information, send new NSSRG-based rejected slice information.

In some implementations, network device 900 includes an AMF.

The network device 900 in the embodiment of the present application can implement the corresponding functions of the network device in the foregoing method embodiments. For the processes, functions, implementations and beneficial effects corresponding to each module (submodule, unit or component, etc.) in the network device 900 , refer to the corresponding description in the above method embodiments, and details are not repeated here. It should be noted that the functions described by the various modules (submodules, units or components, etc.) in the network device 900 of the embodiment of the application can be realized by different modules (submodules, units or components, etc.), or by the same Module (submodule, unit or component, etc.) implementation.

Fig. 10 is a schematic structural diagram of a communication device 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, so that the communication device 1000 implements the method in the embodiment of the present application.

In an implementation manner, the communication device 1000 may further include a memory 1020 . Wherein, the processor 1010 may call and run a computer program from the memory 1020, so that the communication device 1000 implements the method in the embodiment of the present application.

Wherein, the memory 1020 may be an independent device independent of the processor 1010 , or may be integrated in 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, specifically, to send information or data to other devices, or to receive information sent by other devices. information or data.

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

In an implementation manner, the communication device 1000 may be the network device of the embodiment of the present application, and the communication device 1000 may implement the corresponding processes implemented by the network device in each method of the embodiment of the present application. For the sake of brevity, the Let me repeat.

In one implementation, the communication device 1000 may be the terminal device of the embodiment of the present application, and the communication device 1000 may implement the corresponding processes implemented by the terminal device in the methods of the embodiment of the present application. For the sake of brevity, the Let me repeat.

FIG. 11 is a schematic structural diagram of a chip 1100 according to an embodiment of the present application. The chip 1100 includes a processor 1110, and the processor 1110 can invoke and run a computer program from a memory, so as to implement the method in the embodiment of the present application.

In one embodiment, the chip 1100 may further include a memory 1120 . Wherein, the processor 1110 may call and run a computer program from the memory 1120, so as to implement the method executed by the terminal device or the network device in the embodiment of the present application.

Wherein, the memory 1120 may be an independent device independent of the processor 1110 , or may be integrated in the processor 1110 .

In an implementation manner, the chip 1100 may further include an input interface 1130 . Wherein, the processor 1110 can control the input interface 1130 to communicate with other devices or chips, specifically, can obtain information or data sent by other devices or chips.

In an implementation manner, the chip 1100 may further include an output interface 1140 . Wherein, the processor 1110 can control the output interface 1140 to communicate with other devices or chips, specifically, can output information or data to other devices or chips.

In one embodiment, the chip can be applied to the network device in the embodiment of the present application, and the chip can implement the corresponding processes implemented by the network device in the various methods of the embodiment of the present application. For the sake of brevity, details are not repeated here. .

In one embodiment, the chip can be applied to the terminal device in the embodiment of the present application, and the chip can implement the corresponding processes implemented by the terminal device in the various methods of the embodiment of the present application. For the sake of brevity, no further details are given here. .

Chips applied to network devices and terminal devices may be the same chip or different chips.

It should be understood that the chip mentioned in the embodiment of the present application may also be called a system-on-chip, a system-on-chip, a system-on-a-chip, or a system-on-a-chip.

The processor mentioned above may be a general-purpose processor, a digital signal processor (DSP), an off-the-shelf programmable gate array (field programmable gate array, FPGA), an application specific integrated circuit (ASIC) or other Programmable Logic Devices, Transistor Logic Devices, Discrete Hardware Components, etc. Wherein, the general-purpose processor mentioned above may be a microprocessor or any conventional processor or the like.

The aforementioned memories may be volatile memories or nonvolatile memories, or may include both volatile and nonvolatile memories. Among them, the non-volatile memory can be read-only memory (read-only memory, ROM), programmable read-only memory (programmable ROM, PROM), erasable programmable read-only memory (erasable PROM, EPROM), electrically programmable Erases programmable read-only memory (electrically EPROM, EEPROM) or flash memory. The volatile memory may be random access memory (random access memory, RAM).

It should be understood that the above-mentioned memory is illustrative but not restrictive. For example, the memory in the embodiment of the present application may also be a static random access memory (static RAM, SRAM), a dynamic random access memory (dynamic RAM, DRAM), Synchronous dynamic random access memory (synchronous DRAM, SDRAM), double data rate synchronous dynamic random access memory (double data rate SDRAM, DDR SDRAM), enhanced synchronous dynamic random access memory (enhanced SDRAM, ESDRAM), synchronous connection Dynamic random access memory (synch link DRAM, SLDRAM) and direct memory bus random access memory (Direct Rambus RAM, DR RAM), etc. That is, the memory in the embodiments of the present application is intended to include, but not be 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 used to realize the corresponding functions realized by the terminal device in the above method, and the network device 1220 may be used to realize the corresponding functions realized by the network device in the above method. For the sake of brevity, details are not repeated here.

In the above embodiments, all or part of them may be implemented by software, hardware, firmware or any combination thereof. When implemented using software, it 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 the computer, the processes or functions according to the embodiments of the present application will be generated in whole or in part. The computer can be a general purpose computer, a special purpose computer, a computer network, or other programmable device. The computer instructions may be stored in or transmitted from one computer-readable storage medium to another computer-readable storage medium, for example, the computer instructions may be transferred from a website, computer, server, or data center by wire (such as coaxial cable, optical fiber, digital subscriber line (Digital Subscriber Line, DSL)) or wireless (such as infrared, wireless, microwave, etc.) to another website site, computer, server or data center. 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 or a data center integrated with one or more available media. The available medium may be a magnetic medium (such as a floppy disk, a hard disk, or a magnetic tape), an optical medium (such as a DVD), or a semiconductor medium (such as a solid state disk (Solid State Disk, SSD)) and the like.

It should be understood that, in various embodiments of the present application, the sequence numbers of the above-mentioned processes do not mean the order of execution, and the execution order of the processes should be determined by their functions and internal logic, and should not be used in the embodiments of the present application. The implementation process constitutes any limitation.

Those skilled in the art can clearly understand that for the convenience and brevity of the description, the specific working process of the above-described system, device and unit can refer to the corresponding process in the foregoing method embodiment, which will not be repeated here.

The above is only the specific implementation of the application, but the scope of protection of the application is not limited thereto. Anyone familiar with the technical field can easily think of changes or substitutions within the technical scope disclosed in the application, and should covered within the scope of protection of this application. Therefore, the protection scope of the present application should be based on the protection scope of the claims.

Claims (54)

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; 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 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; or,

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; 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 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; or,

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.

Images