CN117751594A

CN117751594A - Method and device for registering network slice

Info

Publication number: CN117751594A
Application number: CN202180100864.9A
Authority: CN
Inventors: 杨林平; 胡文; 强鹂
Original assignee: Huawei Technologies Co Ltd
Current assignee: Huawei Technologies Co Ltd
Priority date: 2021-10-28
Filing date: 2021-10-28
Publication date: 2024-03-22
Also published as: WO2023070446A1

Abstract

The application provides a method and a device for registering network slices, wherein the method comprises the following steps: transmitting a first registration request message on a first access, the first registration request message including first single network slice selection support information; receiving a first registration accept message on the first access in response to the first registration request message, the first registration accept message indicating that the first single network slice selection support information belongs to pending network slice selection support information; receiving first information on the first access, the first information being used to instruct the first single-network-slice-selection-support information to change to belong to the allowed network slice-selection-support information, in case there is a need on the second access to obtain a service of the first single network slice; and sending a second registration request message on the second access, wherein the second registration request message comprises second single-network slice selection support information, and the second single-network slice selection support information is used for indicating the first single-network slice, so that the reliability of acquiring the network slice service is improved.

Description

Method and device for registering network slice

Technical Field

The present application relates to the field of communication technology, and more particularly, to a method and apparatus for registering network slices.

Background

Current communication system architecture allows core network devices to serve both access networks and supports terminal devices requesting corresponding services on both third generation partnership project (3rd generation partnership project,3GPP) access and non-3 GPP access, respectively. For example, if the terminal device has a requirement of a single network slice on the 3GPP access, a registration request message may be sent to the core network device, where the registration request message may carry single network slice selection support information (which may also be referred to as single network slice selection auxiliary information, single network slice selection assistance information, S-nsai) corresponding to the single network slice, so as to obtain a service provided by the single network slice.

When the core network device attributes the S-nsai to the pending nsai in a registration accept message corresponding to the response registration request message of the 3GPP access, the terminal device uniformly manages the pending nsai on both accesses, if the terminal device also has the requirement of the single network slice on the non-3 GPP access at this time, since the current protocol specifies that the S-nsai belonging to the pending nsai cannot be carried in the registration request message, the terminal device cannot send the registration request message including the S-nsai to the core network device on the non-3 GPP access, even if the core network device changes the S-nsai to belong to the allowed nsai on the 3GPP access, since the terminal device separately manages the allowed nsai on both accesses, the terminal device cannot timely sense when the service of the single network slice can be acquired on the non-3 GPP access, and the terminal device cannot still acquire the service on the non-3 GPP access, and vice versa. Therefore, a method for registering a network slice is needed to improve the reliability of acquiring a network slice service by a terminal device.

Disclosure of Invention

The application provides a method and a device for registering network slices, which can improve the reliability of acquiring network slice services by terminal equipment.

In a first aspect, a method of registering a network slice is provided, the method being executable by a terminal device or a chip in a terminal device, the method comprising: transmitting a first registration request message on the first access, the first registration request message being for registering a first single network slice, the first registration request message including first single network slice selection support information for indicating the first single network slice; receiving a first registration accept message on the first access in response to the first registration request message, the first registration accept message indicating that the first single network slice selection support information belongs to pending network slice selection support information; receiving first information on the first access, the first information being used to instruct the first single-network-slice-selection-support information to change to belong to the allowed network slice-selection-support information, in case there is a need on the second access to obtain a service of the first single network slice; transmitting a second registration request message on the second access, the second registration request message including second single-network-slice selection support information for indicating the first single-network slice; receiving a second registration accept message on the second access in response to the second registration request message; wherein the access types of the first access and the second access are different.

Wherein the first information may be first single network slice selection support information belonging to the pending network slice selection support information.

Therefore, in the application, when the single network slice selection support information corresponding to the single network slice is changed from pending to the allowed network slice selection support information on one access, the terminal equipment can actively judge whether the access has the requirement of the single network slice on the other access, if so, a registration request message is sent to the core network equipment, so that the situation that the terminal equipment cannot timely sense when the single network slice service can be acquired is avoided, and the reliability of acquiring the network slice service by the terminal equipment is improved.

With reference to the first aspect, in certain implementations of the first aspect, the first information is carried in a configuration update message, where the configuration update message is used to update a configuration of the first single network slice.

With reference to the first aspect, in certain implementations of the first aspect, the first single-network-slice selection support information is in a different format than the second single-network-slice selection support information.

For example, the first registration request message belongs to a roaming network, the second registration request message belongs to a home network, and the first single network slice selection support information and the second single network slice selection support information belong to different formats.

Therefore, in the method, the reliability of acquiring the network slicing service by the terminal equipment can be improved.

In a second aspect, a method of registering a network slice is provided, the method being executable by a core network device or a chip in the core network device, the method comprising: receiving a first registration request message sent on a first access, the first registration request message being for registering a first single network slice, the first registration request message including first single network slice selection support information for indicating the first single network slice; transmitting a first registration acceptance message responding to the first registration request message to the first access, wherein the first registration acceptance message indicates that the first single network slice selection support information belongs to the undetermined network slice selection support information; when the second access has a requirement of acquiring the service of the first single network slice, sending first information to the first access, wherein the first information is used for indicating the first single network slice selection supporting information to be changed to be the allowed network slice selection supporting information; receiving a second registration request message sent on a second access, the second registration request message including second single-network-slice selection support information, the second single-network-slice selection support information being used to indicate the first single-network slice; transmitting a second registration accept message in response to the second registration request message to the second access; wherein the access types of the first access and the second access are different.

Therefore, in the application, when the single network slice selection support information corresponding to the single network slice is changed from pending to the allowed network slice selection support information on one access, the terminal device can actively judge whether the access has the requirement of the single network slice on the other access, if so, the core network device can receive the registration request message about the single network slice on the access, can provide the service on the single network slice for the access, and improves the reliability of the network slice service.

With reference to the second aspect, in some implementations of the second aspect, the first information is carried in a configuration update message, where the configuration update message is used to update a configuration of the first single network slice.

With reference to the second aspect, in certain implementations of the second aspect, the first single-network slice selection support information is in a different format than the second single-network slice selection support information.

In a third aspect, a method of registering for a network slice service is provided, the method comprising: transmitting a first registration request message on the first access, the first registration request message being for registering a first single network slice, the first registration request message including first single network slice selection support information for indicating the first single network slice; receiving a first registration accept message on the first access for responding to the first registration request message, the first registration accept message indicating that the single network slice selection support information belongs to the pending network slice selection support information; transmitting a second registration request message on the second access, the second registration request message including second single-network-slice selection support information for indicating the first single-network slice; receiving a second registration accept message on the second access in response to the second registration request message; wherein the access types of the first access and the second access are different.

Therefore, in the application, the terminal equipment has the service requirement of the single network slice on a certain access, even if the single network slice selection support information corresponding to the single network slice is attributed to the undetermined network slice selection support information on another access, the terminal equipment can send the registration request message carrying the single network slice selection support information of the single network slice on the access, and the reliability of the terminal equipment for acquiring the network slice service is improved.

With reference to the third aspect, in some implementations of the third aspect, the first single-network-slice-selection support information belongs to pending single-network-slice-selection support information on the first access and on the second access.

Therefore, in the application, the registration request message may also carry single network slice selection support information belonging to the pending network slice selection support information, and the terminal device may send the registration request message to directly carry the corresponding single network slice selection support information under the condition that the terminal device has a single network slice requirement corresponding to the single network slice selection support information of the pending network slice selection support information, so that the reliability of acquiring network slice services by the terminal device can be improved.

With reference to the third aspect, in some implementations of the third aspect, before the terminal device sends the second registration request message to the core network device on the second access, the method further includes: the terminal device deletes the single network slice selection support information from the network slice selection support information to be determined, or the terminal device deletes the network slice selection support information to be determined.

Therefore, in the application, under the condition that the terminal equipment has the requirement of acquiring the single network slice belonging to the undetermined state, the corresponding single network slice selection support information can be deleted in the undetermined network slice selection support information, or the undetermined network slice selection support information can be deleted, and the terminal equipment can send a registration request message comprising the corresponding single network slice selection support information, so that the reliability of acquiring the network slice service by the terminal equipment can be improved.

With reference to the third aspect, in some implementations of the third aspect, the first single-network-slice-selection support information belongs to the pending single-network-slice-selection support information only on the first access.

Therefore, in the application, the terminal equipment can independently manage the single network slice selection support information to be determined based on the access type, and the reliability of acquiring the network slice service by the terminal equipment can be improved.

In a fourth aspect, a method of registering a network slice is provided, the method being executable by a core network device or a chip in the core network device, the method comprising: receiving a first registration request message sent on a first access, the first registration request message being for registering a first single network slice, the first registration request message including first single network slice selection support information for indicating the first single network slice; transmitting a first registration acceptance message for responding to the first registration request message to the first access, wherein the first registration acceptance message indicates that the single network slice selection support information belongs to the undetermined network slice selection support information; receiving a second registration request message sent on a second access, the second registration request message including second single-network-slice selection support information, the second single-network-slice selection support information being used to indicate the first single-network slice; transmitting a second registration accept message for responding to the second registration request message to the second access; wherein the access types of the first access and the second access are different.

Therefore, in the application, the single network slice selection supporting information corresponding to the single network slice is attributed to the undetermined network slice selection supporting information on the other access, and even if the terminal equipment sends the registration request message carrying the single network slice selection supporting information of the single network slice on the access, the core network equipment can support to process the registration request message, so that the reliability of the network slice service is improved.

With reference to the fourth aspect, in some implementations of the fourth aspect, the first single-network-slice selection support information belongs to pending single-network-slice selection support information on the first access and on the second access.

With reference to the fourth aspect, in some implementations of the fourth aspect, the first single-network-slice selection support information belongs to the pending single-network-slice selection support information only on the first access.

In a fifth aspect, there is provided a method of registering a network slice, the method being executable by a terminal device or a chip in a terminal device, the method comprising: the method comprises the steps that a terminal device sends a registration request message to core network equipment at a first access, wherein the registration request message is used for registering a single network slice, and the registration request message comprises single network slice selection supporting information corresponding to the single network slice; the terminal device receives a registration acceptance message for responding to the registration request message at the first access, wherein the registration acceptance message comprises single network slice selection support information, the single network slice selection support information belongs to allowed network slice selection support information at the first access and the second access, and the access types of the first access and the second access are different.

Therefore, in the application, the terminal equipment can uniformly manage the allowed single-network slice selection support information without depending on the access type, so that the situation that the terminal equipment cannot initiate a registration request message on a certain access and cannot obtain the single-network slice service is avoided, and the reliability of acquiring the network slice service by the terminal equipment is improved.

With reference to the fifth aspect, in certain implementations of the fifth aspect, the method further includes: the terminal device receives a configuration update message on the first access, the configuration update message including single network slice selection support information.

In a sixth aspect, a method of registering a network slice is provided, the method being executable by a core network device or a chip in the core network device, the method comprising: in the case that the terminal equipment hopes to have the requirement of acquiring the service of the single network slice on the first access and the second access, the core network equipment receives a registration request message sent by the terminal equipment on the first access or the second access, wherein the registration request message comprises single network slice selection supporting information corresponding to the single network slice, and the access types of the first access and the second access are different; the core network device transmits a registration accept message for responding to the registration request message to the first access or to the second access of the terminal device, the registration accept message including single network slice selection support information.

Therefore, in the application, the terminal equipment can uniformly manage the allowed single-network slice selection support information independent of the access type, so that the situation that the terminal equipment cannot initiate a registration request message on a certain access and the core network equipment cannot know that the access has the single-network slice service requirement is avoided, and the reliability of network slice service is improved.

With reference to the sixth aspect, in certain implementations of the sixth aspect, the method further includes: the core network device sends a configuration update message to the terminal device on the first access or on the second access, the configuration update message including single network slice selection support information.

In a seventh aspect, an apparatus for registering a network slice service is provided, the apparatus including a transmitting unit and a receiving unit, wherein: the sending unit is used for sending a first registration request message on the first access, the first registration request message is used for registering a first single-network slice, the first registration request message comprises first single-network slice selection supporting information, and the first single-network slice selection supporting information is used for indicating the first single-network slice; the receiving unit is configured to receive, on a first access, a first registration acceptance message in response to the first registration request message, the first registration acceptance message indicating that the first single network slice selection support information belongs to pending network slice selection support information; the receiving unit is further configured to, when there is a need to obtain a service of the first single network slice on the second access, receive first information on the first access, where the first information is used to instruct the first single network slice selection support information to change to belong to allowed network slice selection support information; the sending unit is further configured to send a second registration request message on the second access, where the second registration request message includes second single-network slice selection support information, and the second single-network slice selection support information is used to indicate the first single-network slice; the receiving unit is further configured to receive a second registration accept message on the second access in response to the second registration request message; wherein the access types of the first access and the second access are different.

With reference to the seventh aspect, in certain implementation manners of the first aspect, the first information is carried in a configuration update message, and the configuration update message is used to update a configuration of the first single network slice.

With reference to the seventh aspect, in certain implementation manners of the first aspect, the first single-network slice selection support information is in a different format from the second single-network slice selection support information.

In an eighth aspect, an apparatus for registering a network slice service is provided, the apparatus including a transmitting unit and a receiving unit, wherein: the receiving unit is configured to receive a first registration request message sent on a first access, the first registration request message being configured to register a first single-network slice, the first registration request message including first single-network slice selection support information, the first single-network slice selection support information being configured to indicate the first single-network slice; the sending unit is used for sending a first registration acceptance message responding to the first registration request message to the first access, wherein the first registration acceptance message indicates that the first single network slice selection support information belongs to the undetermined network slice selection support information; the sending unit is further configured to send, when the second access has a requirement for acquiring a service of the first single network slice, first information to the first access, where the first information is used to instruct the first single network slice selection support information to change to belong to allowed network slice selection support information; the receiving unit is further configured to receive a second registration request message sent on a second access, where the second registration request message includes second single-network slice selection support information, and the second single-network slice selection support information is used to indicate the first single-network slice; the sending unit is further configured to send a second registration acceptance message to the second access in response to the second registration request message; wherein the access types of the first access and the second access are different.

With reference to the eighth aspect, in some implementations of the eighth aspect, the first information is carried in a configuration update message, where the configuration update message is used to update a configuration of the first single network slice.

With reference to the eighth aspect, in some implementations of the eighth aspect, the first single-network slice selection support information is in a different format than the second single-network slice selection support information.

In a ninth aspect, an apparatus for registering a network slice service is provided, the apparatus including a transmitting unit and a receiving unit, wherein: the sending unit is used for sending a first registration request message on the first access, the first registration request message is used for registering a first single-network slice, the first registration request message comprises first single-network slice selection supporting information, and the first single-network slice selection supporting information is used for indicating the first single-network slice; the receiving unit is configured to receive, on a first access, a first registration acceptance message for responding to a first registration request message, the first registration acceptance message indicating that the single network slice selection support information belongs to pending network slice selection support information; the sending unit is configured to send a second registration request message on a second access, where the second registration request message includes second single-network slice selection support information, and the second single-network slice selection support information is used to indicate the first single-network slice; the receiving unit is configured to receive a second registration accept message on a second access in response to the second registration request message; wherein the access types of the first access and the second access are different.

With reference to the ninth aspect, in certain implementations of the ninth aspect, the first single-network-slice-selection support information belongs to pending single-network-slice-selection support information on the first access and on the second access.

With reference to the ninth aspect, in some implementations of the ninth aspect, the apparatus further includes a processing unit, where the processing unit is configured to delete the first single network slice selection support information from the pending network slice selection support information, or delete the pending network slice selection support information, before the sending unit sends the second registration request message to the core network device on the second access.

With reference to the ninth aspect, in certain implementations of the ninth aspect, the first single-network-slice selection support information belongs to the pending single-network-slice selection support information only on the first access.

In a tenth aspect, there is provided an apparatus for registering a network slice service, the apparatus comprising a transmitting unit and a receiving unit, wherein: the receiving unit is configured to receive a first registration request message sent on a first access, the first registration request message being configured to register a first single-network slice, the first registration request message including first single-network slice selection support information, the first single-network slice selection support information being configured to indicate the first single-network slice; the sending unit is used for sending a first registration acceptance message for responding to the first registration request message to the first access, wherein the first registration acceptance message indicates that the single network slice selection support information belongs to the undetermined network slice selection support information; the receiving unit is configured to receive a second registration request message sent on a second access, where the second registration request message includes second single-network slice selection support information, and the second single-network slice selection support information is used to indicate the first single-network slice; the sending unit is used for sending a second registration acceptance message for responding to the second registration request message to the second access; wherein the access types of the first access and the second access are different.

With reference to the tenth aspect, in certain implementations of the tenth aspect, the first single-network-slice-selection support information belongs to pending single-network-slice-selection support information on the first access and on the second access.

With reference to the tenth aspect, in certain implementations of the tenth aspect, the first single-network-slice selection support information belongs to the pending single-network-slice selection support information only on the first access.

An eleventh aspect provides an apparatus for registering a network slice service, the apparatus including a transmitting unit configured to transmit a registration request message on a first access, the registration request message being used to register a single network slice, the registration request message including single network slice selection support information corresponding to the single network slice; the receiving unit is configured to receive, at the first access, a registration acceptance message for responding to the registration request message, the registration acceptance message including single network slice selection support information belonging to the allowed network slice selection support information on the first access and on the second access, the first access and the second access being different in access type.

With reference to the eleventh aspect, in certain implementations of the eleventh aspect, the receiving unit is further configured to receive a configuration update message on the first access, the configuration update message including single network slice selection support information.

In a twelfth aspect, an apparatus for registering a network slice service is provided, where the apparatus includes a transmitting unit and a receiving unit, where the receiving unit is configured to receive a registration request message sent by a terminal device on a first access, where the registration request message is used to register a single network slice, and the registration request message includes single network slice selection support information corresponding to the single network slice; the transmitting unit is configured to transmit, to a first access of the terminal device, a registration acceptance message for responding to the registration request message, where the registration acceptance message includes single network slice selection support information, and the single network slice selection support information belongs to allowed network slice selection support information on the first access and on a second access, and access types of the first access and the second access are different.

With reference to the twelfth aspect, in some implementations of the twelfth aspect, the sending unit is configured to send a configuration update message to the first access of the terminal device, where the configuration update message includes single network slice selection support information.

In a thirteenth aspect, an apparatus for registering for network slice services is provided, comprising a processor and a transceiver in communication with an internal connection of the processor; the transceiver is configured to send a first registration request message on a first access, the first registration request message being configured to register a first single-network slice, the first registration request message including first single-network slice selection support information, the first single-network slice selection support information being configured to indicate the first single-network slice; the transceiver is configured to receive a first registration accept message on the first access in response to the first registration request message, the first registration accept message indicating that the first single network slice selection support information belongs to pending network slice selection support information; the transceiver is further configured to receive, on the second access, first information indicating that the first single-network-slice-selection-support information is changed to belong to the allowed network slice-selection-support information, in case there is a need to acquire a service of the first single-network slice on the second access; the transceiver is further configured to send a second registration request message on the second access, the second registration request message including second single-network-slice-selection support information, the second single-network-slice-selection support information being used to indicate the first single-network slice; the transceiver is further configured to receive a second registration accept message on the second access in response to the second registration request message; wherein the access types of the first access and the second access are different.

The apparatus for registering a network slice provided in the thirteenth aspect is configured to perform the first aspect or any possible implementation manner of the first aspect, and specific details may be referred to the first aspect or any possible implementation manner of the first aspect, which are not described herein.

In a fourteenth aspect, an apparatus for registering for network slice services is provided, comprising a processor and a transceiver in communication with an internal connection of the processor; the transceiver is configured to receive a first registration request message sent on a first access, the first registration request message being configured to register a first single-network slice, the first registration request message including first single-network slice selection support information, the first single-network slice selection support information being configured to indicate the first single-network slice; the transceiver is configured to send a first registration accept message on the first access in response to the first registration request message, the first registration accept message indicating that the first single network slice selection support information belongs to pending network slice selection support information; the transceiver is further configured to send, to the first access, first information indicating that the first single-network-slice selection support information is changed to belong to allowed network-slice selection support information, in a case where there is a need to obtain a service of the first single-network slice on the second access; the transceiver is further configured to receive a second registration request message sent on a second access, the second registration request message including second single-network-slice-selection support information, the second single-network-slice-selection support information being used to indicate the first single-network slice; the transceiver is further configured to send a second registration accept message to the second access in response to the second registration request message; wherein the access types of the first access and the second access are different.

The apparatus for registering with a network slice service according to the fourteenth aspect is configured to perform the second aspect or any possible implementation manner of the second aspect, and specific details may be found in the second aspect or any possible implementation manner of the second aspect, which is not described herein.

In a fifteenth aspect, an apparatus for registering for network slice services is provided, comprising a processor and a transceiver in communication with an internal connection of the processor; the transceiver is configured to send a first registration request message on a first access, the first registration request message being configured to register a first single-network slice, the first registration request message including first single-network slice selection support information, the first single-network slice selection support information being configured to indicate the first single-network slice; the transceiver is configured to receive a first registration accept message on the first access for responding to the first registration request message, the first registration accept message indicating that the single network slice selection support information belongs to pending network slice selection support information; the transceiver is configured to send a second registration request message on a second access, the second registration request message including second single-network-slice selection support information, the second single-network-slice selection support information being used to indicate the first single-network slice; the transceiver is configured to receive a second registration accept message on the second access in response to the second registration request message; wherein the access types of the first access and the second access are different.

The apparatus for registering a network slice service according to the fifteenth aspect is configured to perform any possible implementation manner of the third aspect or any possible implementation manner of the third aspect, and specific details may be found in any possible implementation manner of the third aspect or any possible implementation manner of the third aspect, which is not described herein.

In a sixteenth aspect, an apparatus for registering for network slice services is provided, comprising a processor and a transceiver in communication with an internal connection of the processor; the transceiver is configured to receive a first registration request message sent on a first access, the first registration request message being configured to register a first single-network slice, the first registration request message including first single-network slice selection support information, the first single-network slice selection support information being configured to indicate the first single-network slice; the transceiver is configured to send a first registration accept message to the first access for responding to the first registration request message, the first registration accept message indicating that the single network slice selection support information belongs to pending network slice selection support information; the transceiver is configured to receive a second registration request message sent on a second access, the second registration request message including second single-network-slice-selection support information, the second single-network-slice-selection support information being configured to indicate the first single-network slice; the transceiver is configured to send a second registration accept message to the second access in response to the second registration request message; wherein the access types of the first access and the second access are different.

The apparatus for registering with a network slice service according to the sixteenth aspect is configured to perform any possible implementation manner of the fourth aspect or the fourth aspect, and specific details may be found in any possible implementation manner of the fourth aspect or the fourth aspect, which are not repeated herein.

In a seventeenth aspect, an apparatus for registering for network slice services is provided, comprising a processor and a transceiver in communication with an internal connection of the processor; the transceiver is used for sending a registration request message on the first access, wherein the registration request message is used for registering a single network slice, and the registration request message comprises single network slice selection supporting information corresponding to the single network slice; the transceiver is configured to receive a registration accept message on the first access in response to the registration request message, the registration accept message including single network slice selection support information belonging to allowed network slice selection support information on the first access and on the second access; wherein the access types of the first access and the second access are different.

The apparatus for registering a network slice service according to the seventeenth aspect is configured to perform the fifth aspect or any possible implementation manner of the fifth aspect, and specific details may be found in the fifth aspect or any possible implementation manner of the fifth aspect, which is not described herein.

In an eighteenth aspect, an apparatus for registering for network slice services is provided, comprising a processor and a transceiver in communication with an internal connection of the processor; the transceiver is used for receiving a registration request message sent by the terminal equipment on the first access, wherein the registration request message is used for registering a single network slice, and the registration request message comprises single network slice selection supporting information corresponding to the single network slice; the transceiver is configured to send a registration accept message to the first access of the terminal device in response to the registration request message, where the registration accept message includes single network slice selection support information belonging to the allowed network slice selection support information on the first access and on the second access; wherein the access types of the first access and the second access are different.

The apparatus for registering a network slice service according to the eighteenth aspect is configured to perform the sixth aspect or any possible implementation manner of the sixth aspect, and specific details may be found in the sixth aspect or any possible implementation manner of the sixth aspect, which is not described herein.

In a nineteenth aspect, an apparatus for registering a network slice service is provided, comprising a processing circuit and an input-output interface in communication with an internal connection of the processing circuit; the input-output interface is used for sending a first registration request message on the first access, the first registration request message is used for registering a first single-network slice, the first registration request message comprises first single-network slice selection supporting information, and the first single-network slice selection supporting information is used for indicating the first single-network slice; the input-output interface is used for receiving a first registration acceptance message responding to a first registration request message on the first access, wherein the first registration acceptance message indicates that the first single network slice selection support information belongs to the undetermined network slice selection support information; the input/output interface is further configured to receive, on the second access, first information indicating that the first single-network-slice selection support information is changed to belong to the allowed network-slice selection support information, in a case where there is a need to acquire a service of the first single-network slice on the second access; the input-output interface is further configured to send a second registration request message on the second access, where the second registration request message includes second single-network slice selection support information, and the second single-network slice selection support information is used to indicate the first single-network slice; the input-output interface is further configured to receive a second registration accept message on the second access in response to the second registration request message; wherein the access types of the first access and the second access are different.

The apparatus for registering a network slice service according to the nineteenth aspect is configured to perform the first aspect or any possible implementation manner of the first aspect, and specific details may be found in the first aspect or any possible implementation manner of the first aspect, which is not described herein.

In a twentieth aspect, an apparatus for registering a network slice service is provided, comprising a processing circuit and an input-output interface in communication with an internal connection of the processing circuit; the input-output interface is configured to receive a first registration request message sent on the first access, the first registration request message being configured to register a first single-network slice, the first registration request message including first single-network slice selection support information, the first single-network slice selection support information being configured to indicate the first single-network slice; the input-output interface is used for sending a first registration acceptance message responding to the first registration request message to the first access, wherein the first registration acceptance message indicates that the first single-network slice selection support information belongs to the undetermined network slice selection support information; the input/output interface is further configured to send first information to the first access when the second access has a requirement for acquiring a service of the first single network slice, where the first information is used to instruct the first single network slice selection support information to change to belong to the allowed network slice selection support information; the input-output interface is further configured to receive a second registration request message sent on the second access, where the second registration request message includes second single-network slice selection support information, and the second single-network slice selection support information is used to indicate the first single-network slice; the input-output interface is further configured to send a second registration accept message to the second access in response to the second registration request message; wherein the access types of the first access and the second access are different.

The apparatus for registering a network slice service according to the twentieth aspect is configured to perform the second aspect or any possible implementation manner of the second aspect, and specific details may be found in the second aspect or any possible implementation manner of the second aspect, which is not described herein.

In a twenty-first aspect, an apparatus for registering a network slice service is provided, comprising a processing circuit and an input-output interface in communication with an internal connection of the processing circuit; the input-output interface is used for sending a first registration request message on the first access, the first registration request message is used for registering a first single-network slice, the first registration request message comprises first single-network slice selection supporting information, and the first single-network slice selection supporting information is used for indicating the first single-network slice; the input-output interface is used for receiving a first registration acceptance message for responding to a first registration request message on the first access, wherein the first registration acceptance message indicates that the single network slice selection support information belongs to the undetermined network slice selection support information; the input-output interface is used for sending a second registration request message on a second access, the second registration request message comprises second single-network slice selection supporting information, and the second single-network slice selection supporting information is used for indicating the first single-network slice; the input-output interface is used for receiving a second registration acceptance message for responding to the second registration request message on a second access; wherein the access types of the first access and the second access are different.

The apparatus for registering a network slice service according to the twenty-first aspect is configured to perform any possible implementation manner of the third aspect or the third aspect, and specific details may be found in any possible implementation manner of the third aspect or the third aspect, which are not described herein.

In a twenty-second aspect, an apparatus for registering a network slice service is provided, comprising a processing circuit and an input-output interface in communication with an internal connection of the processing circuit; the input-output interface is configured to receive a first registration request message sent on the first access, the first registration request message being configured to register a first single-network slice, the first registration request message including first single-network slice selection support information, the first single-network slice selection support information being configured to indicate the first single-network slice; the input-output interface is used for sending a first registration acceptance message for responding to the first registration request message to the first access, wherein the first registration acceptance message indicates that the single network slice selection support information belongs to the undetermined network slice selection support information; the input-output interface is configured to receive a second registration request message sent on a second access, where the second registration request message includes second single-network slice selection support information, and the second single-network slice selection support information is configured to indicate the first single-network slice; the input-output interface is used for sending a second registration acceptance message for responding to the second registration request message to the second access; wherein the access types of the first access and the second access are different.

The apparatus for registering a network slice service according to the twenty-second aspect is configured to perform any possible implementation manner of the fourth aspect or the fourth aspect, and specific details may be found in any possible implementation manner of the fourth aspect or the fourth aspect, which are not repeated herein.

In a twenty-third aspect, an apparatus for registering a network slice service is provided, comprising a processing circuit and an input-output interface in communication with an internal connection of the processing circuit; the input/output interface is used for sending a registration request message on the first access, the registration request message is used for registering a single network slice, and the registration request message comprises single network slice selection supporting information corresponding to the single network slice; the input/output interface is configured to receive a registration acceptance message on the first access or the second access, the registration acceptance message being configured to respond to the registration request message, the single network slice selection support information belonging to the allowed network slice selection support information on the first access and the second access, the registration acceptance message including the single network slice selection support information; wherein the access types of the first access and the second access are different.

The apparatus for registering a network slice service according to the twenty-third aspect is configured to perform the fifth aspect or any possible implementation manner of the fifth aspect, and specific details may be found in the fifth aspect or any possible implementation manner of the fifth aspect, which is not repeated herein.

In a twenty-fourth aspect, an apparatus for registering a network slice service is provided, comprising a processing circuit and an input-output interface in communication with an internal connection of the processing circuit; the input/output interface is used for receiving a registration request message sent by the terminal equipment in the first access, wherein the registration request message is used for registering a single network slice, and the registration request message comprises single network slice selection support information corresponding to the single network slice; the input-output interface is used for sending a registration acceptance message for responding to the registration request message to the first access of the terminal equipment, wherein the registration acceptance message comprises single network slice selection support information, and the single network slice selection support information belongs to allowed network slice selection support information on the first access and the second access; wherein the access types of the first access and the second access are different.

The apparatus for registering a network slice service according to the twenty-fourth aspect is configured to perform the sixth aspect or any possible implementation manner of the sixth aspect, and specific details may be found in the sixth aspect or any possible implementation manner of the sixth aspect, which is not described herein.

In a twenty-fifth aspect, an embodiment of the present application provides a computer readable storage medium, configured to store a computer program, where the computer program includes instructions for executing the first aspect or any possible implementation manner of the first aspect, or any possible implementation manner of the second aspect, or any possible implementation manner of the third aspect, or any possible implementation manner of the fourth aspect, or any possible implementation manner of the fifth aspect, or any possible implementation manner of the sixth aspect.

In a twenty-sixth aspect, embodiments of the present application provide a computer program comprising instructions for performing the above-described first aspect or any possible implementation of the first aspect.

In a twenty-seventh aspect, an embodiment of the present application provides a computer program, where the computer program includes instructions for performing any of the possible implementations of the first aspect or the first aspect, or any of the possible implementations of the second aspect or the second aspect, or any of the possible implementations of the third aspect or the third aspect, or any of the possible implementations of the fourth aspect or the fifth aspect, or any of the possible implementations of the fifth aspect or the fifth aspect, or any of the possible implementations of the sixth aspect or the sixth aspect.

An twenty-eighth aspect of the present application provides a communication system, where the communication system includes the apparatus for registering a network slice service provided in the seventh aspect or the ninth aspect or the eleventh aspect or the thirteenth aspect or the fifteenth aspect or the seventeenth aspect, and the apparatus for reporting cache data provided in the eighth aspect or the tenth aspect or the twelfth aspect or the fourteenth aspect or the sixteenth aspect or the eighteenth aspect.

In a twenty-ninth aspect, a method of requesting a network slice service is provided, the method being executable by a terminal device or a chip in the terminal device, the method comprising: the terminal equipment sends a first registration request message on a first access, wherein the first registration request message is used for registering a single network slice, and the first registration request message comprises single network slice selection supporting information corresponding to the single network slice; the terminal equipment receives a first registration acceptance message responding to the first registration request message on the first access, wherein the first registration acceptance message comprises single network slice selection supporting information, and the single network slice selection supporting information in the first registration acceptance message belongs to undetermined network slice selection supporting information; the terminal equipment receives first information on the first access, wherein the first information is used for indicating that single network slice selection supporting information is changed to be allowed network slice selection supporting information; in the case that the terminal device has a requirement of acquiring the service of the single network slice on the second access, the terminal device sends a second registration request message on the second access, wherein the second registration request message is used for registering the single network slice, and the second registration request message comprises single network slice selection supporting information; wherein the access types of the first access and the second access are different.

Drawings

Fig. 1 is a schematic block diagram of a communication system to which embodiments of the present application are applied;

FIG. 2 is a schematic flow chart of a method of registering a network slice service;

FIG. 3 is a schematic flow chart of a method for registering network slice services provided in an embodiment of the present application;

FIG. 4 is a schematic flow chart of another method for registering network slice services provided by an embodiment of the present application;

FIG. 5 is a schematic flow chart diagram of yet another method for registering network slice services provided by an embodiment of the present application;

fig. 6 is a schematic structural diagram of an apparatus for registering a network slice service according to an embodiment of the present application.

Detailed Description

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

The technical solution of the embodiment of the application can be applied to various communication systems, for example: long term evolution (long term evolution, LTE) system, LTE frequency division duplex (frequency division duplex, FDD) system, LTE time division duplex (time division duplex, TDD), universal mobile telecommunications system (universal mobile telecommunication system, UMTS), fifth generation (5th generation,5G) system, future sixth generation (6th generation,6G) or New Radio (NR), and the like.

In this application, a dashed box or a dashed line of the abstract drawing indicates that the corresponding performed step is an optional step or that the corresponding unit is an optional unit.

The configuration of the communication system of the present application will be described below with reference to fig. 1.

As shown in fig. 1, the communication system includes, but is not limited to, the following network elements:

1. terminal equipment

The terminal device in the embodiment of the present application may also be referred to as: a User Equipment (UE), a Mobile Station (MS), a Mobile Terminal (MT), 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 equipment, etc.

The terminal device may be a device providing voice/data connectivity to a user, e.g., a handheld device with wireless connectivity, an in-vehicle device, etc. Currently, some examples of terminals are: a mobile phone, tablet, laptop, palmtop, mobile internet device (mobile internet device, MID), wearable device, virtual Reality (VR) device, augmented reality (augmented reality, AR) device, wireless terminal in industrial control (industrial control), wireless terminal in unmanned (self driving), wireless terminal in teleoperation (remote medical surgery), wireless terminal in smart grid (smart grid), wireless terminal in transportation security (transportation safety), wireless terminal in smart city (smart city), wireless terminal in smart home (smart home), cellular phone, cordless phone, session initiation protocol (session initiation protocol, SIP) phone, wireless local loop (wireless local loop, WLL) station, personal digital assistant (personal digital assistant, PDA), handheld device with wireless communication function, public or other processing device connected to a wireless modem, vehicle-mounted device, wearable device, terminal device in future 5G network or evolving land communication device (public land mobile network), and the like, without limiting the examples of this.

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

In addition, in the embodiment of the present application, the terminal device may also communicate with terminal devices of other communication systems, for example, inter-device communication, and the like. For example, the terminal device may also transmit (e.g., send and/or accept) time synchronization messages with terminal devices of other communication systems.

2. Access device

In addition, the access device in the embodiment of the present application may be a device for communicating with a terminal device, which may also be referred to as an access network device or a radio access network device, for example, the access device may be an evolved NodeB (eNB or eNodeB) in an LTE system, may also be a wireless controller in a cloud wireless access network (cloud radio access network, CRAN) scenario, or the access device may be a relay station, an access point, a vehicle device, a wearable device, and an access device in a 5G network, or an access device in a PLMN network that evolves in the future, or may be an Access Point (AP) in a WLAN, or may be a gNB in an NR system.

In addition, in the embodiment of the present application, the access device is a device in the RAN, or a RAN node that accesses the terminal device to the wireless network. For example, by way of illustration and not limitation, as access devices, there may be cited: a gNB, a transmission and reception point (transmission reception point, TRP), an evolved Node B (eNB), a radio network controller (radio network controller, RNC), a Node B (Node B, NB), a base station controller (base station controller, BSC), a base transceiver station (base transceiver station, BTS), a home base station (e.g., home evolved NodeB, or home Node B, HNB), a baseband unit (BBU), or a wireless fidelity (wireless fidelity, wifi) Access Point (AP), etc. In one network architecture, the network devices may include Centralized Unit (CU) nodes, or Distributed Unit (DU) nodes, or RAN devices including CU nodes and DU nodes, or RAN devices including control plane CU nodes (CU-CP nodes) and user plane CU nodes (CU-UP nodes) and DU nodes.

The access device provides services for a cell, and the terminal device communicates with the access device through transmission resources (e.g., frequency domain resources, or spectrum resources) used by the cell, where the cell may be a cell corresponding to the access 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 transmitting power and are suitable for providing high-rate data transmission services.

In addition, the carrier wave in the LTE system or the 5G system may have multiple cells operating in the same frequency at the same time, and in some special scenarios, the carrier wave may be considered to be identical to the concept of the cell. For example, in the scenario of carrier aggregation (carrier aggregation, CA), when configuring a secondary carrier for a UE, the carrier index of the secondary carrier and the Cell identity (Cell indentification, cell ID) of the secondary Cell operating on the secondary carrier are carried at the same time, in which case the concept of the carrier and the Cell may be considered to be equivalent, such as that the terminal device accesses one carrier and accesses one Cell to be equivalent.

The communication system of the present application may also be adapted for internet of vehicles (vehicle to everything, V2X) technology, i.e. the terminal device of the present application may also be a car, e.g. a smart car or an autopilot car.

"X" in V2X represents a different communication target, and V2X may include, but is not limited to: automobile-to-automobile (vehicle to vehicl, V2V), automobile-to-road marking (vehicle to infrastructure, V2I), automobile-to-network (vehicle to network, V2N), and automobile-to-pedestrian (vehicle to pedestrian, V2P).

In V2X, the access device may configure a "zone" for the UE. Wherein the area may also be referred to as a geographic area. When the area is configured, the world will be divided into a number of areas, which are defined by reference points, length, width. When the UE determines a region Identifier (ID), the UE performs the remaining operations using the length, the width, the number of regions over the length, the number of regions over the width, and the reference point of the region. The above information may be configured by the access device.

3. Access management function entity

The access management functional entity is mainly used for mobility management, access management and the like, and can be used for realizing other functions except session management in the functions of a mobility management entity (mobility management entity, MME) in the LTE system, such as legal monitoring, access authorization/authentication and the like.

In a 5G communication system, the access management network element may be an access management function (access and mobility management function, AMF) entity.

In future communication systems, the access management function entity may still be an AMF entity, or may have other names, which are not limited in this application.

4. Session management function entity

Session management function (session management function, SMF) entities are mainly used for session management, network interconnection protocol (internet protocol, IP) address allocation and management of terminal devices, termination points for selecting manageable user plane functions, policy control and charging function interfaces, downstream data notification, etc.

In future communication systems, the session management network element may still be an SMF entity, or may have other names, which are not limited in this application.

5. Unified data management entity

The unified data management entity (unified data management, UDM) is responsible for the same handling of foreground data including user identification, user subscription data, authentication data, etc.

The "entity" may also be referred to as a network element, a device, an apparatus, a module, or the like, and is not particularly limited in this application. Also, in this application, for convenience of understanding and explanation, a description of "entity" is omitted in some descriptions, for example, an SMF entity is abbreviated as SMF, in which case, the "SMF" is understood as an SMF network element or an SMF entity, and hereinafter, description of the same or similar cases is omitted.

It will be appreciated that the entities or functions described above may be either network elements in a hardware device, software functions running on dedicated hardware, or virtualized functions instantiated on a platform (e.g., a cloud platform).

It should be understood that the above-listed communication systems include network elements or entities that are merely exemplary and are not particularly limited in this application. For example, the communication system may also include, but is not limited to, an application function (application function, AF), a network capability open function entity (Network Exposure Function, NEF) entity, a user plane function (user plane function, UPF) entity, a Data Network (DN), a policy control function (Policy Control Function, PCF) entity, and the like.

The "core network device" of the present application may include any device capable of communicating with the terminal device via transparent transmission of one or more intermediate devices (e.g., access devices) such as the above-mentioned access management function entity, or, in other words, the "core network device" of the present application may be a device capable of communicating with the terminal device.

Hereinafter, for convenience of understanding and explanation, the processing procedure of the present application will be described in detail by taking AMF as an example of the core network device.

In the following, some terms related to the present application are explained.

1. Single network slice selection support information (single network slice selection assistance information, S-NSSAI)

The S-NSSAI may include slice/service type (SST) information, which may be used to distinguish between multiple network slices. Optionally, the S-NSSAI may also include slice differentiation (slice differentiator, SD) information, which is used to supplement SST information.

In addition, the network slice selection support information (network slice selection assistance information, NSSAI) can be understood as a set of S-NSSAIs.

Currently, S-nsais may be assigned to a requested nsai, an allowed nsai, a rejected nsai, or a pending nsai based on information about a single network slice. The terminal device may take different management modes for different nsais based on the access type. For example, allowed NSSAI and rejected NSSAI are independently managed in the current registration procedure based on 3GPP access and non-3 GPP access, and rejected NSSAI is independently managed in the current registration procedure based on 3GPP access and non-3 GPP access.

2. Requested NSSAI (requested NSSAI)

The requested nsaai may be understood as a network slice indicating that the terminal device wishes to use.

For example, when the terminal device wants to acquire the service of a certain network slice, the terminal device may send a registration request message to the core network device, where the registration request message carries an S-nsai belonging to the requested nsai, and requests the core network device to select the network slice and the network slice instance for the terminal device, so as to provide the service for the terminal device.

3. Allowed NSSAI (allowed NSSAI)

The allowed NSSAI may be understood as a network slice for indicating that the terminal device is allowed to use in the network currently in place.

For example, the core network device sends a registration accept message to the terminal device, where the registration accept message includes S-nsai belonging to the allowed nsai, indicating the network slice and network slice instance that the terminal device is allowed to use.

Currently, the 3GPP protocol specifies that the allowed nsais are independently managed based on access type, e.g., the allowed nsais are independently managed in the current registration procedure based on 3GPP access and non-3 GPP access.

4. Refused NSSAI (rejected NSSAI)

The rejected NSSAI may be understood as a network slice for indicating that the terminal device is not available in the network currently in place.

For example, the core network device sends a registration accept message to the terminal device, where the registration accept message includes an S-nsai that belongs to the rejected nsai, indicating that the terminal device is unavailable to use the network slice and the network slice instance.

5. Pending NSSAI (pending NSSAI)

A pending nsai may be understood as a network slice indicating that a subsequent authentication and post-authentication terminal device is required to use.

For example, the core network device sends a registration accept message to the terminal device, where the registration accept message includes S-nsai belonging to the pending nsai. After the pending S-nsai completes a specific network slice authentication and authentication (nsaa) procedure, if the result of the authentication and authentication is successful, the pending S-nsai is updated to an allowed S-nsai through a user configuration update procedure (generic UE configuration update), and if the result of the authentication and authentication is unsuccessful, the pending S-nsai is updated to a rejected S-nsai.

Currently, the 3GPP protocol specifies that the pending nsai is uniformly managed independent of access types, for example, even if the core network device sends a message configuring the pending nsai to only one of the accesses, the pending nsai may be applicable to multiple types of accesses (e.g., 3GPP access and non-3 GPP access) at the same time.

Fig. 2 shows a schematic flow chart of a method 200 for a terminal device to request a slicing service.

It is assumed that the first access and the second access are different types of access, for example, the first access is a 3GPP access, the second access is a non-3 GPP access, or the first access is a non-3 GPP access, and the second access is a 3GPP access. The terminal device has a need to acquire slice services corresponding to the first S-nsai and the second S-nsai on the first access.

S201, the terminal equipment sends a registration request message #1 to the core network equipment on the first access.

The registration request message #1 is used for requesting to acquire the single network slice service corresponding to the first S-nsai and the second S-nsai, or the registration request message #1 includes the first S-nsai and the second S-nsai.

S202, the terminal device receives a registration accept message #1 from the core network device on the first access.

The registration accept message #1 is used to indicate that the first S-nsai is an allowed S-nsai and the second S-nsai is a pending S-nsai, or the registration accept message #1 includes the allowed first S-nsai and the pending second S-nsai.

And S203, the terminal equipment determines that the requirement of acquiring the slice service corresponding to the second S-NSSAI and the third S-NSSAI is met on the second access.

S204, the terminal equipment sends a registration request message #2 to the core network equipment on the second access.

The registration request message #2 is used for requesting to acquire the slice service corresponding to the third S-nsai, or the registration request message #2 includes the third S-nsai.

It should be noted that, the second S-nsai has been determined in step S202 to belong to the pending nsai, and since the pending nsai is not access-unified management-independent and the 3GPP protocol specifies that the pending nsai is not carried in the registration request message, the second S-nsai cannot be carried in the registration request message #2 even if the terminal device wishes to acquire the slice service corresponding to the second S-nsai.

S205, the terminal device receives the registration accept message #2 from the core network device on the second access.

The registration accept message is used to indicate that the third S-nsai is an allowed S-nsai or the registration accept message includes an allowed third S-nsai.

S206, the terminal equipment and the core network equipment execute authentication and authentication flow on the first access.

The authentication and authentication procedure is used to authenticate and authenticate the second S-NSSAI. In other words, the core network device initiates an NSSAA procedure of the second S-NSSAI on the first access of the terminal device.

S207, the terminal device receives a configuration update message #1 from the core network device on the first access.

The configuration update message is used to update the state of the first S-nsai and the second S-nsai, in other words, the core network device initiates a terminal device configuration update (UE configuration update, UCU) procedure of the first S-nsai and the second S-nsai on the first access of the terminal device.

As can be seen, in the procedure for the terminal device to request the slice service shown in fig. 2, since the terminal device uniformly manages the pending nsais on both accesses, and the current protocol specifies that the S-nsais belonging to the pending nsais cannot be carried in the registration request message, the terminal device cannot send the registration request message including the second S-nsais to the core network device on the second access, and even if the core network device changes the second S-nsais to belong to the allowed nsais on the first access, the terminal device cannot timely sense when the service of the single network slice can be acquired on the second access because the terminal device separately manages the allowed nsais on both accesses, and the terminal device cannot still acquire the service on the second access.

Therefore, there is a need for a method for acquiring slicing services, which can satisfy the reliability of acquiring slicing services by a terminal device.

Fig. 3 shows a schematic flowchart of a method 300 for registering a network slice service according to an embodiment of the present application.

S301, the terminal device sends a first registration request message #1 on the first access, and correspondingly, the core network device receives the first registration request message #1 sent by the terminal device on the first access.

The first registration request message #1 is used to register the single network slice #1 (an example of the first single network slice).

The first registration request message #1 includes single network slice selection support information S-nsai #1 (an example of the first single network slice selection support information). S-nsai #1 is used to indicate single network slice #1.

The terminal device has a requirement for the service of the single network slice #1 on the first access, and the S-nsai #1 of the single network slice #1 is carried in the first registration request message #1, and the S-nsai #1 belongs to the requested nsai.

Optionally, if the terminal device further has a requirement for the service of the single network slice #2 on the first access, the S-nsai #2 of the single network slice #2 may also be carried in the first registration request message #1, where the S-nsai #2 belongs to the requested nsai.

Wherein, the single network slice corresponding to the S-nsai belonging to the pending nsai may be understood as a pending state, the single network slice corresponding to the S-nsai belonging to the allowed nsai may be understood as an allowed state, and the single network slice corresponding to the S-nsai belonging to the rejected nsai may be understood as a rejected state.

The core network device may determine that the single network slice #1 is in a pending state, an allowed state, or a rejected state according to the S-nsai #1 and subscription information of the user or other policies. If the single network slice #1 is usable only by the terminal device after the subsequent authentication and the authentication, the single network slice #1 is in a pending state, if the single network slice #1 is usable by the terminal device, the single network slice #1 is in an allowed state, and if the single network slice #1 is unusable by the terminal device, the single network slice #1 is in a rejected state. Similarly, the core network device may also determine whether the single network slice #2 is in the pending state, the allowed state, or the reject state according to the S-nsai #2 and subscription information of the user or other policies.

If the core network device determines that the single network slice belongs to a pending state, the S-nsai in the first registration accept message #1 sent by the core network device and used for responding to the first registration request message #1 is a pending nsai; if the core network device determines that the single network slice belongs to the allowed state, the S-nsai in the first registration accept message #1 sent by the core network device and used for responding to the first registration request message #1 is an allowed nsai; if the core network device determines that the single network slice belongs to the reject state, the S-nsai in the first registration accept message #1 sent by the core network device and used for responding to the first registration request message #1 is the reject nsai.

By way of example and not limitation, a single network slice #1 is set as the pending state and a single network slice #2 is set as the allowed state.

S302, the terminal device receives the first registration accept message #1 in response to the first registration request message #1 on the first access, and correspondingly, the core network device transmits the first registration accept message #1 in response to the first registration request message #1 to the first access of the terminal device.

The first registration accept message #1 includes single network slice selection support information S-nsai #1, which belongs to the pending network slice selection support information nsai.

Optionally, the first registration accept message #1 further includes S-nsai #2, the S-nsai #2 belonging to the allowed nsais.

It should be noted that, at this time, the terminal device has a service requirement of the single network slice #1 on the second access, but since the protocol specifies that the registration request message cannot carry the S-nsai belonging to the pending nsai, the terminal device cannot send the registration request message carrying the S-nsai #1 to the core network device on the second access. At this time, the terminal device may not transmit the registration request message on the second access, or the terminal device may transmit the registration request message on the second access that does not include the S-nsai #1.

The first access and the second access are different in access type, for example, the first access is a 3GPP access, the second access is a non-3 GPP access, or the first access is a non-3 GPP access, and the second access is a 3GPP access.

For example, assuming that the terminal device also has a service requirement of single network slice #3 on the second access, the method 300 may further comprise steps S303 and S304.

S303, the terminal equipment sends a registration request message #2 to the core network equipment on the second access.

The registration request message #2 includes a corresponding S-nsai #3 to the single network slice #3, the S-nsai #3 belonging to the requested nsai.

As described above, the registration request message #2 does not carry S-nsai #1, although the terminal device also has the service requirement of single network slice #1 on the second access.

S304, the terminal device receives a registration accept message #2 for responding to the registration request message #2 from the core network device on the second access.

If the registration request message #2 carries the S-nsai #3 corresponding to the single network slice #3, the corresponding registration accept message #2 also carries the S-nsai #3, and the core network device may determine that the single network slice #3 is in the pending state, the allowed state or the rejected state according to the S-nsai #3 and subscription information of the user or other policies, and it is assumed that the S-nsai #3 belongs to the allowed nsai. .

S305, the terminal equipment receives the first information on the first access, and correspondingly, the core network equipment sends the first information to the first access of the terminal equipment.

The first information is used to indicate that the single network slice selection support information S-nsai #1 is changed to belong to an allowed nsai.

In one possible implementation, the terminal device receives first information on a first access, including:

the terminal device receives a configuration update message on the first access, the configuration update message comprising first information pertaining to allowed network slice selection support information.

The first information may be S-NSSAI #1.

For example, the core network device initiates a UCU procedure on the first access of the terminal device such that S-nsai #1 is changed to belong to an allowed nsai. If the first registration request message #1 also carries S-nsai #2, the configuration update message also carries S-nsai #2.

Before the core network device initiates the UCU procedure on the first access of the terminal device, the core network device may initiate an nsaa procedure on the first access for authenticating and authenticating S-nsai #1.

S306, in the case that the second access of the terminal device has a requirement for acquiring the service of the single network slice #1, the terminal device transmits the second registration request message #3 on the second access, and correspondingly, the core network device receives the second registration request message #3 transmitted by the terminal device on the second access.

The second registration request message includes the single network slice selection support information S-nsai #1.

For example, after the terminal device receives the first information on the first access, it may be determined whether the second access has a need to obtain the service of the single network slice #1, if so, since the state of the single network slice #1 has been updated from the pending state to the allowed state, and the S-nsai #1 has been changed from the pending nsai to the allowed nsai, the terminal device re-triggers the registration request, sends a second registration request message #3 to the core network device on the second access, and carries the S-nsai #1 in the second registration request message #3. If the second access of the terminal device also has a need to obtain the service of the single network slice #3, the second registration request message #3 also carries S-nsai #3.

S307, the terminal device receives a second registration accept message #3 for responding to the second registration request message #3 from the core network device on the second access.

The second registration accept message #3 includes the S-NSSAI #1 (an example of second single network slice selection support information).

If the second registration request message #3 further includes S-nsai #3, the second registration accept message #3 further includes S-nsai #3.

The first registration request message #1 sent by the terminal device on the first access may correspond to the same public land mobile network (public land mobile network, PLMN) or may correspond to a different PLMN than the registration request message #2 and the second registration request message #3 sent by the terminal device on the second access.

In addition, the formats of the first single network slice selection support information and the second single network slice selection support information are different, in other words, the formats of the first registration request message #1, the first registration accept message #1, the registration request message #2, the second registration request message #3, the second registration accept message #3, the configuration update message, and the like may be the same or different, and the formats thereof may be related to the networks to which the corresponding messages belong, for example, the formats of the S-nsai #1 belonging to the requested or allowed nsai in the home network and the roaming network are different, and the formats of the S-nsai #1 belonging to the pending nsai in the home network and the roaming network are the same. It should be understood that in this application, it is not limited whether the formats of S-NSSAI #1 carried in different messages are the same or different.

Fig. 4 shows a schematic flow chart of another method 400 for registering a network slice service provided by an embodiment of the present application.

S401, the terminal device sends a first registration request message #a on the first access, and correspondingly, the core network device receives the first registration request message #a sent by the terminal device on the first access.

The first registration request message #a is used to register the single network slice #a (one example of the first single network slice)

The first registration request message #a includes single network slice selection support information S-nsai #a (an example of the first single network slice selection support information). S-NSSAI#A is used to indicate single network slice #A.

The terminal device has a requirement for a service of a single network slice #a on the first access, and the first registration request message #a carries an S-nsai #a of the single network slice #a, which belongs to the requested nsai.

Optionally, if the terminal device further has a requirement for a service of a single network slice #b on the first access, the first registration request message #a may also carry an S-nsai #b of the single network slice #b, where the S-nsai #b belongs to the requested nsai.

The core network device may determine that the single network slice #a is in a pending state, an allowed state, or a rejected state according to the S-nsai #a and subscription information of the user or other policies. If the single network slice #a is usable only by the terminal equipment after the subsequent authentication and the authentication, the single network slice #a is in a pending state, if the single network slice #a is usable by the terminal equipment, the single network slice #a is in an allowed state, and if the single network slice #a is unusable by the terminal equipment, the single network slice #a is in a rejected state. Similarly, the core network device may also determine whether the single network slice #b is in a pending state, an allowed state or a rejected state according to the S-nsai #b and subscription information of the user or other policies.

If the core network device determines that the single network slice belongs to a pending state, the S-nsai in the first registration accept message #a sent by the core network device and used for responding to the first registration request message #a is a pending nsai; if the core network device determines that the single network slice belongs to the allowed state, the S-nsai in the first registration accept message #a sent by the core network device and used for responding to the first registration request message #a is an allowed nsai; if the core network device determines that the single network slice belongs to the reject state, the S-nsai in the first registration accept message #a sent by the core network device for responding to the first registration request message #a is a reject nsai.

By way of example and not limitation, a single network slice #a is set as a pending state and a single network slice #b is set as an allowed state.

S402, the terminal device receives a first registration accept message #a in response to the first registration request message #a on the first access, and correspondingly, the core network device transmits a first registration accept message #a in response to the first registration request message #a to the first access of the terminal device.

The first registration accept message #a includes single network slice selection support information S-nsai #a, which belongs to the pending network slice selection support information nsai.

Optionally, the first registration accept message #a further includes S-nsai #b belonging to the allowed nsai.

If the terminal device has a service requirement of the single network slice #a on the second access at this time, the terminal device may send a registration request message to the core network device. The first access and the second access are different in access type, for example, the first access is a 3GPP access, the second access is a non-3 GPP access, or the first access is a non-3 GPP access, and the second access is a 3GPP access.

S403, the terminal device sends a second registration request message #B on the second access, and correspondingly, the core network device receives the second registration request message #B sent by the terminal device on the second access.

The second registration request message #b includes the single network slice selection support information S-nsai #a (an example of the second single network slice selection support information).

If the terminal device has a service requirement of another single network slice on the second access, the second registration request message #b may also carry other corresponding S-nsais, which will not be described herein for simplicity.

The following describes a manner in which the terminal device carries the single network slice selection support information S-nsai#a in the second registration request message #b to request acquisition of the single network slice #a.

Mode #1

The first registration accept message #a includes S-nsai #a belonging to pending nsai on both the first access and the second access.

The second registration request message #b includes S-nsai #a belonging to pending nsai.

That is, the pending NSSAI is uniformly managed based on different accesses. The S-nsai#a is assigned to the pending nsai on the first access and the registration request message sent by the terminal device on the second access is allowed to carry the pending S-nsai#a.

Therefore, in the application, the registration request message may also carry the S-nsai belonging to the pending nsai, and the terminal device may send the registration request message to request to register the pending S-nsai under the condition that the terminal device has a requirement of acquiring the single network slice belonging to the pending state, so that the reliability of acquiring the network slice service by the terminal device can be improved.

Mode #2

The second registration request message #b includes S-nsai #a belonging to the requested nsai.

The method 400 further comprises step S404 before step S403.

S404, the terminal device deletes the single network slice selection support information S-NSSAI#A from the undetermined network slice selection support information NSSAI, or the terminal device deletes the undetermined network slice selection support information NSSAI.

In other words, if the terminal device has a service requirement of acquiring the single network slice #a on the second access, and the corresponding S-nsai #a belongs to the pending nsai, the terminal device may delete the S-nsai #a in the pending nsai, or the terminal device may delete the entire pending nsai, and may generate the S-nsai #a in the requested nsai, so that the S-nsai #a included in the second registration request message #b belongs to the requested nsai.

Therefore, in the application, under the condition that the terminal equipment has the requirement of acquiring the single network slice belonging to the pending state, the corresponding S-NSSAI can be deleted in the pending NSSAI, or the pending NSSAI can be deleted, and the terminal equipment can send a registration request message including the corresponding S-NSSAI, so that the reliability of acquiring the network slice service by the terminal equipment can be improved.

Mode #3

The first registration accept message #a includes S-nsai #a belonging to the pending nsai #a only on the first access.

In other words, the pending NSSAI is managed independently based on different accesses. The S-nsai #a included in the first registration accepted message #a received on the first access belongs to the pending nsai, but the S-nsai #a does not belong to the pending nsai #a for the second access, and thus the S-nsai #a belongs to the pending nsai on the first access and does not affect the transmission of the second registration request message #b on the second access, which may carry the S-nsai #a.

The manner in which the second registration request message #b carries the S-nsai #a is explained above.

S405, the terminal device receives a second registration accept message #b from the core network device on the second access, the second registration accept message #b including the S-nsai #a.

The core network device may determine that the single network slice #a is in a pending state, an allowed state, or a rejected state according to the S-nsai #a and subscription information of the user or other policies. If the single network slice #a is usable only by the terminal device after the subsequent authentication and the authentication, the single network slice #a is in a pending state, if the single network slice #a is usable by the terminal device, or if the terminal device has initiated the nsaa procedure of the single network slice #a on the first access, the single network slice #a may be in an allowed state, and if the single network slice #a is unusable by the terminal device, the single network slice #a is in a rejected state.

S406, the terminal equipment and the core network equipment execute authentication and authentication flow on the first access.

For example, the core network device may initiate an nsaa procedure on the first access for authenticating and authenticating S-nsai#a.

Optionally, if the manner #3 is adopted, the pending nsais are managed independently based on different accesses, and the terminal device may also perform authentication and authentication on the first access and the second access, respectively, at this time, step S407 is also optionally performed.

S407, the terminal equipment and the core network equipment execute authentication and authentication flow on the second access.

After the core network device completes the authentication and authentication of the single network slice, step S408 and step S409 may also be performed.

The terminal device receives a configuration update message #a from the core network device on the first access S408.

The configuration update message #A includes S-NSSAI #A and S-NSSAI #B.

For example, the core network device may initiate UCU flows on the first access of the terminal device such that S-nsai #a and S-nsai #b are allowed nsais.

S409, the terminal device receives the configuration update message #B from the core network device on the second access.

The configuration update message #B includes S-NSSAI #A.

For example, the core network device may initiate UCU flows on the first access of the terminal device such that S-nsai#a is an allowed nsai.

Fig. 5 shows a schematic flow chart of yet another method 500 for registering with a network slice service according to an embodiment of the present application.

S501, the terminal device transmits a registration request message #a (an example of the first registration request message) at the first access, and correspondingly, the core network device receives the registration request message #a transmitted by the terminal device at the first access.

The registration request message #a includes single network slice selection support information S-nsai #a corresponding to the single network slice #a.

It is assumed that the terminal device has a service requirement of a single network slice #a on both the first access and the second access, by way of example and not limitation, the registration request message #a is sent on the first access. The first access and the second access are of different access types, e.g., the first access is a 3GPP access, the second access is a non-3 GPP access, or the first access is a non-3 GPP access, and the second access is a 3GPP access.

In other words, the terminal device performs unified management on the allowable nsais, not independent management by access. The terminal device, whether on the first access, the second access, or both the first access and the second access, has the requirement of a single network slice #a service, may choose to send a registration request message to the core network device on one of the accesses.

Assuming that the terminal device sends a registration request message #a on the first access, and the terminal device also has a service requirement of a single network slice #b on the first access at this time, the registration request message #a also carries an S-nsai #b corresponding to the single network slice #b.

S502, the terminal device receives a registration acceptance message #a for responding to the registration request message #a at the first access, and correspondingly, the core network device transmits the registration acceptance message #a for responding to the registration request message #a to the first access or the second access of the terminal device.

The registration accept message #a includes the S-nsai #a.

The core network device may determine that the single network slice #a is in a pending state, an allowed state, or a rejected state according to the S-nsai #a and subscription information of the user or other policies.

If the registration request message #a sent by the terminal device on the first access includes S-nsai #a and S-nsai #b, and the core network device determines that the single network slice #a is in the allowed state and the single network slice #b is in the pending state, the S-nsai #a in the registration accept message #a belongs to the allowed nsai on the first access and the second access, and since the terminal device uniformly manages the pending nsai based on different accesses, the S-nsai #b in the registration accept message #a belongs to the pending nsai on the first access and the second access.

The terminal device has new requirements for single network slices #b and #c on the second access, steps S503 and S504 are also performed.

S503, the terminal device sends a registration request message #b to the core network device on the second access.

The registration request message #b includes S-nsai #a and S-nsai #c corresponding to the single network slice #c.

It should be noted that, although the second access has a requirement of a single network slice #b, the S-nsai #b cannot be carried in the registration request message #b since the second access is assigned to the pending state. In addition, even if the second access does not have the requirement of the single network slice #a, the terminal device does not access to uniformly manage the slices which belong to the permission and uniformly manage the slices which belong to the pending, and the terminal device still carries all the S-nsais which can be carried by the terminal device and have the requirements on the two accesses in the process of sending the registration request message #b.

S504, the terminal device receives a registration accept message #b for responding to the registration request message #b from the core network device on the second access.

The registration accept message #b includes S-nsai #a and S-nsai #c.

S505, the terminal equipment and the core network equipment execute authentication and authentication flow on the first access.

For example, the core network device initiates an NSSAA procedure for S-NSSAI#b on the first access.

S506, the terminal equipment receives the configuration update message from the core network equipment on the first access.

The configuration update message includes S-NSSAI#a, S-NSSAI#b, and S-NSSAI#c.

For example, if single network slice #a, single network slice #b, and single network slice #c are all allowed, S-nsai #a, S-nsai #b, and S-nsai #c belong to allowed nsais.

It should be noted that, the single network slice #a, the single network slice #b, and the single network slice #c are updated to the allowed state in the first access or the second access, and since the terminal device may uniformly manage the allowed S-nsai independent of the access type in the present application, the single network slice is updated to the allowed state in only one access, and the terminal device may use the single network slice in both accesses.

Therefore, in the application, the terminal equipment can uniformly manage the allowed S-NSSAI without depending on the access type, so that the situation that the terminal equipment cannot initiate a registration request message on a certain access and cannot obtain a single network slice service is avoided, and the reliability of acquiring the network slice service by the terminal equipment is improved.

The method for registering network slice in the embodiment of the present application is described above, and the apparatus for registering network slice service in the embodiment of the present application is described below, where the apparatus for registering network slice service in the embodiment of the present application includes an apparatus for registering network slice service applied to a terminal device and an apparatus for registering network slice service applied to a core network device, and it should be understood that the apparatus for registering network slice service applied to a terminal device is a terminal device in the above method, and has any function of a terminal device in the above method, and the apparatus for registering network slice service applied to a core network device is a core network device in the above method, and has any function of a core network device in the above method.

As shown in fig. 6, when fig. 6 is applied to a terminal device registering a network slice service, it includes a transmitting unit and a receiving unit, wherein: the sending unit is used for sending a first registration request message on the first access, the first registration request message is used for registering a first single-network slice, the first registration request message comprises first single-network slice selection supporting information, and the first single-network slice selection supporting information is used for indicating the first single-network slice; the receiving unit is configured to receive, on a first access, a first registration acceptance message in response to the first registration request message, the first registration acceptance message indicating that the first single network slice selection support information belongs to pending network slice selection support information; the receiving unit is further configured to, when there is a need to obtain a service of the first single network slice on the second access, receive first information on the first access, where the first information is used to instruct the first single network slice selection support information to change to belong to allowed network slice selection support information; the sending unit is further configured to send a second registration request message on the second access, where the second registration request message includes second single-network slice selection support information, and the second single-network slice selection support information is used to indicate the first single-network slice; the receiving unit is further configured to receive a second registration accept message on the second access in response to the second registration request message; wherein the access types of the first access and the second access are different.

Or, an apparatus for registering a network slice service, comprising a transmitting unit and a receiving unit, wherein: the sending unit is used for sending a first registration request message on the first access, the first registration request message is used for registering a first single-network slice, the first registration request message comprises first single-network slice selection supporting information, and the first single-network slice selection supporting information is used for indicating the first single-network slice; the receiving unit is configured to receive, on a first access, a first registration acceptance message for responding to a first registration request message, the first registration acceptance message indicating that the single network slice selection support information belongs to pending network slice selection support information; the sending unit is configured to send a second registration request message on a second access, where the second registration request message includes second single-network slice selection support information, and the second single-network slice selection support information is used to indicate the first single-network slice; the receiving unit is configured to receive a second registration accept message on a second access in response to the second registration request message; wherein the access types of the first access and the second access are different.

Or, the device applied to the network slice service registration comprises a sending unit and a receiving unit, wherein the sending unit is used for sending a registration request message on the first access or the second access, the registration request message is used for registering a single network slice, and the registration request message comprises single network slice selection supporting information corresponding to the single network slice; the receiving unit is configured to receive a registration accept message on the first access or the second access for responding to the registration request message, where the registration accept message includes single network slice selection support information belonging to the allowed network slice selection support information on the first access and the second access, and the access types of the first access and the second access are different.

The device for registering network slice service applied to the terminal device provided in the embodiment of the present application is the terminal device in the above method 300, method 400 and method 500, and has any function of the terminal device in the above method, and specific details can be found in the above method, which is not repeated herein.

As shown in fig. 6, when fig. 6 is applied to a core network device registering a network slice service, it includes a transmitting unit and a receiving unit, in which: the receiving unit is configured to receive a first registration request message sent on a first access, the first registration request message being configured to register a first single-network slice, the first registration request message including first single-network slice selection support information, the first single-network slice selection support information being configured to indicate the first single-network slice; the sending unit is used for sending a first registration acceptance message responding to the first registration request message to the first access, wherein the first registration acceptance message indicates that the first single network slice selection support information belongs to the undetermined network slice selection support information; the sending unit is further configured to send, when the second access has a requirement for acquiring a service of the first single network slice, first information to the first access, where the first information is used to instruct the first single network slice selection support information to change to belong to allowed network slice selection support information; the receiving unit is further configured to receive a second registration request message sent on a second access, where the second registration request message includes second single-network slice selection support information, and the second single-network slice selection support information is used to indicate the first single-network slice; the sending unit is further configured to send a second registration acceptance message to the second access in response to the second registration request message; wherein the access types of the first access and the second access are different.

Or, an apparatus for registering a network slice service, comprising a transmitting unit and a receiving unit, wherein: the receiving unit is configured to receive a first registration request message sent on a first access, the first registration request message being configured to register a first single-network slice, the first registration request message including first single-network slice selection support information, the first single-network slice selection support information being configured to indicate the first single-network slice; the sending unit is used for sending a first registration acceptance message for responding to the first registration request message to the first access, wherein the first registration acceptance message indicates that the single network slice selection support information belongs to the undetermined network slice selection support information; the receiving unit is configured to receive a second registration request message sent on a second access, where the second registration request message includes second single-network slice selection support information, and the second single-network slice selection support information is used to indicate the first single-network slice; the sending unit is used for sending a second registration acceptance message for responding to the second registration request message to the second access; wherein the access types of the first access and the second access are different.

Or the device applied to the network slice service registration comprises a sending unit and a receiving unit, wherein the receiving unit is used for receiving a registration request message sent by the terminal equipment on the first access, the registration request message is used for registering the single network slice, and the registration request message comprises single network slice selection supporting information corresponding to the single network slice; the sending unit is configured to send a registration accept message for responding to the registration request message to the first access or the second access of the terminal device, where the registration accept message includes single network slice selection support information, and the single network slice selection support information belongs to allowed network slice selection support information on the first access and the second access, where access types of the first access and the second access are different.

The device for registering network slice service applied to the core network device provided in the embodiment of the present application is the core network device in the above method 300, method 400 or method 500, and has any function of the core network device in the above method, and specific details can be found in the above method, which is not described herein.

The apparatus for registering network slicing service applied to a terminal device and the apparatus for registering network slicing service applied to a core network device according to the embodiments of the present application are described above, and possible product forms of the apparatus for registering network slicing service applied to a terminal device and the apparatus for registering network slicing service applied to a core network device are described below. It should be understood that any form of product having the features of the apparatus for registering network slicing services for a terminal device as described in fig. 6 and any form of product having the features of the apparatus for registering network slicing services for a core network device as described in fig. 6 fall within the scope of protection of the present application. It should also be understood that the following description is given by way of example only, and is not limited to the product form of the apparatus for registering network slice service applied to a terminal device and the product form of the apparatus for registering network slice service applied to a core network device in the embodiments of the present application.

As a possible product form, the apparatus for registering network slice service applied to a terminal device and the apparatus for registering network slice service applied to a core network device according to the embodiments of the present application may be implemented by a general bus architecture.

As a possible product form, the apparatus for registering a network slice service applied to a terminal device and the apparatus for registering a network slice service applied to a core network device according to the embodiments of the present application may be implemented by a general purpose processor.

As a possible product form, the apparatus for registering a network slice service applied to a terminal device and the apparatus for registering a network slice service applied to a core network device according to the embodiments of the present application may be further implemented using the following: one or more FPGAs (field programmable gate arrays), PLDs (programmable logic devices), controllers, state machines, gate logic, discrete hardware components, any other suitable circuitry, or any combination of circuitry capable of performing the various functions described throughout this application.

It should be understood that the above-mentioned device for registering network slicing service applied to a terminal device and the device for registering network slicing service applied to a core network device in various product forms have any functions of the terminal device and the core network device in the above-mentioned method embodiment, respectively, and are not described herein again.

It should be understood that the term "and/or" is merely an association relationship describing the associated object, and means that three relationships may exist, for example, a and/or B may mean: a exists alone, A and B exist together, and B exists alone. In addition, the character "/" herein generally indicates that the front and rear associated objects are an "or" relationship.

Those of ordinary skill in the art will appreciate that the various method steps and elements described in connection with the embodiments disclosed herein may be implemented as electronic hardware, computer software, or combinations of both, and that the steps and components of the various embodiments have been described generally in terms of functionality in the foregoing description to clearly illustrate this interchangeability of hardware and software. Whether such functionality is implemented as hardware or software depends upon the particular application and design constraints imposed on the solution. Those of ordinary skill in the art may implement the described functionality using different approaches for each particular application, but such implementation is not to be considered as beyond the scope of the present application.

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

In the several embodiments provided in this application, it should be understood that the disclosed systems, devices, and methods may be implemented in other manners. For example, the apparatus embodiments described above are merely illustrative, e.g., the division of the units is merely a logical function division, and there may be additional divisions when actually implemented, e.g., multiple units or components may be combined or integrated into another system, or some features may be omitted or not performed. In addition, the coupling or direct coupling or communication connection shown or discussed with each other may be an indirect coupling or communication connection via some interfaces, devices, or elements, or may be an electrical, mechanical, or other form of connection.

The units described as separate units may or may not be physically separate, and units shown as units may or may not be physical units, may be located in one place, or may be distributed on a plurality of network units. Some or all of the units may be selected according to actual needs to achieve the purposes of the embodiments of the present application.

In addition, each functional unit in each embodiment of the present application may be integrated in one processing unit, or each unit may exist alone physically, or two or more units may be integrated in one unit. The integrated units may be implemented in hardware or in software functional units.

The integrated units, if implemented in the form of software functional units and sold or used as stand-alone products, may be stored in a computer readable storage medium. Based on such understanding, the technical solution of the present application is essentially or a part contributing to the prior art, or all or part of the technical solution may be embodied in the form of a software product stored in a storage medium, comprising several instructions for causing a computer device (which may be a personal computer, a server, or a network device, etc.) to perform all or part of the steps of the method described in the embodiments of the present application. And the aforementioned storage medium includes: a U-disk, a removable hard disk, a read-only memory (ROM), a random access memory (random access memory, RAM), a magnetic disk, or an optical disk, or other various media capable of storing program codes.

While the invention has been described with reference to certain preferred embodiments, it will be understood by those skilled in the art that various changes and substitutions of equivalents may be made and equivalents will be apparent to those skilled in the art without departing from the scope of the invention. Therefore, the protection scope of the present application shall be subject to the protection scope of the claims.

Claims

A method of registering a network slice, the method comprising:

transmitting a first registration request message on a first access, wherein the first registration request message is used for registering a first single-network slice, the first registration request message comprises first single-network slice selection support information, and the first single-network slice selection support information is used for indicating the first single-network slice;

receiving a first registration accept message on the first access in response to the first registration request message, the first registration accept message indicating that the first single network slice selection support information belongs to pending network slice selection support information;

receiving first information on the first access, wherein the first information is used for indicating the first single-network slice selection supporting information to be changed to be the allowed network slice selection supporting information when the second access has the requirement of acquiring the service of the first single-network slice;

transmitting a second registration request message on the second access, the second registration request message including second single-network-slice selection support information for indicating the first single-network slice;

Receiving a second registration accept message on the second access in response to the second registration request message;

wherein the access types of the first access and the second access are different.
The method of claim 1, wherein the first information is carried in a configuration update message that is used to update a configuration of the first single network slice.
The method of claim 1 or 2, wherein the first single-network slice selection support information is in a different format than the second single-network slice selection support information.
A method of registering a network slice, the method comprising:

transmitting a first registration request message on a first access, wherein the first registration request message is used for registering a first single-network slice, the first registration request message comprises first single-network slice selection support information, and the first single-network slice selection support information is used for indicating the first single-network slice;

receiving a first registration accept message on the first access for responding to the first registration request message, the first registration accept message indicating that the single network slice selection support information belongs to pending network slice selection support information;

Transmitting a second registration request message on a second access, the second registration request message including second single-network-slice selection support information, the second single-network-slice selection support information being used to indicate the first single-network slice;

receiving a second registration accept message on the second access in response to the second registration request message;

wherein the access types of the first access and the second access are different.
The method of claim 4, wherein the first single-network-slice-selection-support information belongs to pending single-network-slice-selection-support information on the first access and on the second access.
The method of claim 4 or 5, wherein before the sending the second registration request message on the second access, the method further comprises:

and deleting the first single network slice selection support information from the undetermined network slice selection support information, or deleting the undetermined network slice selection support information.
The method of claim 4, wherein the first single-network-slice-selection-support information belongs to pending single-network-slice-selection-support information only on the first access.
A method of registering a network slice, the method comprising:

receiving a first registration request message sent on a first access, the first registration request message being used for registering a first single-network slice, the first registration request message comprising first single-network slice selection support information, the first single-network slice selection support information being used for indicating the first single-network slice;

transmitting a first registration acceptance message for responding to the first registration request message to the first access, wherein the first registration acceptance message indicates that the single network slice selection support information belongs to pending network slice selection support information;

receiving a second registration request message sent on a second access, the second registration request message including second single-network-slice selection support information, the second single-network-slice selection support information being used to indicate the first single-network slice;

transmitting a second registration accept message for responding to the second registration request message to the second access;

wherein the access types of the first access and the second access are different.
The method of claim 8, wherein the first single-network-slice-selection-support information belongs to pending single-network-slice-selection-support information on the first access and on the second access.
The method of claim 8, wherein the first single-network-slice-selection-support information belongs to pending single-network-slice-selection-support information only on the first access.
An apparatus for registering a network slice, the apparatus comprising a transmitting unit and a receiving unit, wherein:

the sending unit is configured to send a first registration request message on a first access, where the first registration request message is used to register a first single-network slice, the first registration request message includes first single-network slice selection support information, and the first single-network slice selection support information is used to indicate the first single-network slice;

the receiving unit is configured to receive, on the first access, a first registration accept message that responds to the first registration request message, where the first registration accept message indicates that the first single network slice selection support information belongs to pending network slice selection support information;

the receiving unit is further configured to receive, when there is a need to obtain a service of the first single network slice on the second access, first information on the first access, where the first information is used to indicate that the single network slice selection support information is changed to belong to allowed network slice selection support information;

The sending unit is further configured to send a second registration request message on the second access, where the second registration request message includes second single-network slice selection support information, and the second single-network slice selection support information is used to indicate the first single-network slice;

wherein the access types of the first access and the second access are different.
The apparatus of claim 11, wherein the first information is carried in a configuration update message that is used to update a configuration of the first single network slice.
The apparatus of claim 11 or 12, wherein the first single-network slice selection support information is in a different format than the second single-network slice selection support information.
An apparatus for registering a network slice, comprising a processing circuit and an input interface and an output interface in communication with an internal connection of the processing circuit, wherein the output interface is configured to send a first registration request message on a first access, the first registration request message being configured to register a first single network slice, the first registration request message including first single network slice selection support information, the first single network slice selection support information being configured to indicate the first single network slice, and further configured to send a second registration request message on the second access, the second registration request message including second single network slice selection support information, the second single network slice selection support information being configured to indicate the first single network slice; the input interface is configured to receive, on the first access, a first registration acceptance message in response to the first registration request message, where the first registration acceptance message indicates that the first single-network-slice selection support information belongs to pending network-slice selection support information, and receive, on a second access, first information for indicating that the first single-network-slice selection support information changes to belong to allowed network-slice selection support information if there is a need to obtain a service of the first single-network slice on the first access; wherein the access types of the first access and the second access are different.
An apparatus for registering a network slice, the apparatus comprising a transmitting unit and a receiving unit, wherein:

the sending unit is configured to send a first registration request message on a first access, where the first registration request message is used to register a first single-network slice, and the first registration request message includes first single-network slice selection support information, where the first single-network slice selection support information is used to indicate the first single-network slice;

the receiving unit receives a first registration acceptance message for responding to the first registration request message on the first access, wherein the first registration acceptance message indicates that the single network slice selection support information belongs to undetermined network slice selection support information;

the sending unit is further configured to send a second registration request message on a second access, where the second registration request message includes second single-network slice selection support information, and the second single-network slice selection support information is used to indicate the first single-network slice;

the receiving unit is further configured to receive a second registration accept message on the second access, where the second registration accept message is used to respond to the second registration request message;

Wherein the access types of the first access and the second access are different.
The apparatus of claim 15, wherein single network slice selection support information in the first registration accept message belongs to pending single network slice selection support information on the first access and the second access.
The apparatus according to claim 15 or 16, wherein the apparatus further comprises a processing unit configured to delete the first single network slice selection support information from the pending network slice selection support information or delete the pending network slice selection support information before the sending unit sends the second registration request message on the second access.
The apparatus of claim 15, wherein the first single-network-slice-selection-support information belongs to pending single-network-slice-selection-support information only on the first access.
An apparatus for registering a network slice, the apparatus comprising a transmitting unit and a receiving unit, wherein:

the receiving unit is configured to receive a first registration request message sent on a first access, where the first registration request message is used to register a first single-network slice, and the first registration request message includes first single-network slice selection support information, where the first single-network slice selection support information is used to indicate the first single-network slice;

The sending unit is configured to send, to the first access, a first registration accept message for responding to the first registration request message, where the first registration accept message indicates that the single network slice selection support information belongs to pending network slice selection support information;

the receiving unit is further configured to receive a second registration request message sent on a second access, where the second registration request message includes second single-network slice selection support information, and the second single-network slice selection support information is used to indicate the first single-network slice;

the sending unit is further configured to send a second registration accept message to the second access, where the second registration accept message is used to respond to the second registration request message;

wherein the access types of the first access and the second access are different.
The apparatus of claim 19, wherein the first single-network-slice-selection-support information belongs to pending single-network-slice-selection-support information on the first access and on the second access.
The apparatus of claim 19, wherein single network slice selection support information in the first registration accept message belongs to pending single network slice selection support information only on the first access.
A computer readable storage medium storing a computer program comprising instructions for performing the method of any one of claims 1 to 3, or 4 to 7, or 8 to 10.
A computer program product, characterized in that the computer program product, when run on a computer, causes the computer to perform the method of any of claims 1 to 3, or 4 to 7, or 8 to 10.
An apparatus for registering a network slice, comprising:

a processor and a memory, wherein the memory is for storing program instructions, the processor is for executing the program instructions in the memory to implement the method of any one of claims 1 to 3, or 4 to 7, or 8 to 10.
An apparatus for registering a network slice, comprising:

a processing circuit and an interface circuit; wherein,

the interface circuit is configured to couple with a memory external to the wireless communication device and provide a communication interface for the processing circuit to access the memory;

the processing circuitry is configured to execute program instructions in the memory to implement the method of any of claims 1 to 3, or 4 to 7, or 8 to 10.