CN115915337A

CN115915337A - Network slice access control method and communication device

Info

Publication number: CN115915337A
Application number: CN202110904547.4A
Authority: CN
Inventors: 孙海洋; 朱方园
Original assignee: Huawei Technologies Co Ltd
Current assignee: Huawei Technologies Co Ltd
Priority date: 2021-08-06
Filing date: 2021-08-06
Publication date: 2023-04-04
Also published as: WO2023010994A1

Abstract

The application provides a network slice access control method and a communication device, wherein the method comprises the following steps: the session management function network element receives second information from the policy control function network element or the unified data storage library or the unified data management function network element; and the session management functional network element enables the first Packet Data Unit (PDU) session in the first network slice or the first network slice not to be controlled by the network slice access based on the second information. Based on the method described in the present application, the session management function network element can timely enable the first PDU session or the first network slice to be free from network slice access control based on the second information sent by the policy control function network element or the unified data repository or the unified data management function network element, thereby avoiding interruption or failure to initiate the priority service.

Description

Network slice access control method and communication device

Technical Field

The present application relates to the field of communications technologies, and in particular, to a network slice access control method and a communications apparatus.

Background

The network slice is to divide a physical network into a plurality of mutually independent logical networks according to requirements of different service applications on user quantity, quality of service (QoS) and bandwidth. A Network Slice Admission Control Function (NSACF) is introduced in 3GPP to determine whether the number of User Equipments (UEs) in a network slice reaches the maximum number of UEs supported by the network slice, and determine whether the number of Packet Data Units (PDUs) in the network slice reaches the maximum number of PDU sessions supported by the network slice.

When a UE is registered in a network slice, depending on the specific mode, an access and mobility management function (AMF) network element may notify the NSACF that the number of UEs for the network slice is increased by one before or after registration acceptance. When the UE deregisters, or receives a deregistration notification of a Unified Data Management (UDM) network element, the NSACF is notified that the number of UEs in the network slice is reduced by one.

In the first step of the PDU session establishment procedure, a Session Management Function (SMF) notifies the NSACF that the PDU session number of the network slice is increased by one. At the last step of PDU session release, the SMF will inform the NSACF that the number of PDU sessions for the network slice is reduced by one.

When the NSACF finds that the number of UEs in the network slice reaches the maximum number of UEs supported by the network slice, it notifies the AMF quota has been reached. The AMF will set the S-NSSAI corresponding to the network slice as rejected NSSAI, i.e., the AMF will subsequently reject the UE to access the network slice. When the NSACF finds that the number of PDU sessions in the network slice reaches the maximum number of PDU sessions supported by the network slice, it informs the SMF quota has been reached. SMF will refuse to establish a PDU session in that network slice.

Network slice registration, PDU session setup, related to priority traffic (e.g., emergency traffic, multimedia priority service, or mission critical service) should not be affected by network slice access control. When the registration type of the UE in the network slice indicates emergency registration, the AMF determines that the network slice may exempt NSAC, i.e., does not limit the number of UEs in the network slice. The UE may receive a priority header from the AMF during PDU session setup when the registration type of the network slice indicates emergency registration. The SMF determining the network slice in which the PDU session is based on the priority header may exempt NSAC, i.e. not limit the number of PDU sessions for that network slice.

However, if the UE does not carry a Priority header when the registration type of the network slice is not emergency registration or when the network slice is registered/initiated for PDU session (e.g. performing "called" Priority service, using call-related Priority mechanism, etc.), the AMF/SMF has no way to determine that the UE or the PDU session is used for transferring the Priority service, and may cause interruption or failure of the Priority service due to slice access control.

Disclosure of Invention

The embodiment of the application provides a network slice access control method and a communication device, which are beneficial to avoiding interruption or incapability of initiating a priority service.

In a first aspect, the present application provides a method for controlling network slice access, where the method includes: the session management function network element receives second information from the policy control function network element or the unified data storage library or the unified data management function network element; and the session management functional network element enables the first Packet Data Unit (PDU) session in the first network slice or the first network slice not to be controlled by the network slice access based on the second information.

Based on the method described in the first aspect, the session management function network element can timely enable the first PDU session or the first network slice to be free from network slice access control based on the second information sent by the policy control function network element or the unified data repository or the unified data management function network element, thereby avoiding interruption or failure to initiate the priority service.

In a possible implementation, the second information is used to indicate that the terminal device corresponding to the first PDU session or the first network slice or the first PDU session is associated with a priority service, or the second information is an ARP that is assigned and preempted to the first PDU session, and a value of the second information is the first value. By using the ARP to indicate the first PDU session or the first network slice or the terminal equipment associated priority service corresponding to the first PDU session, no additional indication information is required to be sent to indicate the first PDU session or the first network slice or the terminal equipment associated priority service corresponding to the first PDU session, which is beneficial to saving indication overhead.

Throughout this application, the first PDU session associated priority service may refer to: the first PDU session is delivering priority traffic or the first PDU session is not currently delivering priority traffic but is delivering priority traffic in the future (i.e., the first PDU session may be delivering priority traffic).

Throughout this application, the first network slice associated priority service may refer to: the first network slice is delivering priority traffic, or the first network slice is not currently delivering priority traffic but is to be delivered in the future (i.e., the first network slice may deliver priority traffic), or subscribed priority traffic may be used at the first network slice.

Throughout this application, the terminal device associated priority service may refer to: the terminal device is transmitting the priority service, or the terminal device is not transmitting the priority service currently but transmits the priority service in the future (i.e. the terminal device may transmit the priority service), or the terminal device may use the contracted priority service.

In a possible implementation, the session management function network element sends, to the access and mobility management function network element, third information based on the second information, where the third information is used to indicate that the first PDU session or the first network slice or the terminal device corresponding to the first PDU session is associated with the priority service. By sending the third information to the access and mobility management function network element, after the access and mobility management function network element receives the third information, the terminal device corresponding to the first PDU session can be timely isolated from access control of the first network slice or isolated from access control of the first network slice based on the third information.

In a possible implementation, a specific implementation manner of the session management function network element enabling the first PDU session in the first network slice or the first network slice not to be controlled by the network slice access is as follows:

when the PDU session number of the first network slice reaches the PDU session number threshold corresponding to the first network slice, the session management function network element does not refuse to establish the first PDU session; and/or the presence of a gas in the gas,

the session management function network element does not indicate to the network slice admission control function network element to increase the PDU session number of the first network slice by one; and/or the presence of a gas in the atmosphere,

the session management function network element indicates to the network slice admission control function network element to reduce the PDU session number of the first network slice by one; and/or the presence of a gas in the atmosphere,

the session management function network element indicates to the network slice admission control function network element to leave the first network slice out of network slice access control.

In a possible implementation, after the session management function network element makes the first PDU session or the first network slice in the first network slice not be controlled by the network slice access based on the second information, the session management function network element may further receive fifth information from the policy control function network element or the unified data repository or the unified data management function network element; the session management function network element (re) subjects the first PDU session or the first network slice to network slice access control based on the fifth information.

Based on the possible implementation manner, the session management function network element can timely enable the first PDU session or the first network slice to be under access control of the network slice based on the fifth information sent by the policy control function network element or the unified data storage library or the unified data management function network element.

In a possible implementation, the fifth information is used to indicate that the terminal device corresponding to the first PDU session or the first network slice or the first PDU session is not associated with a priority service, or the fifth information is an allocation and preemption priority ARP corresponding to the first PDU session, and a value of the fifth information is a second value.

In one possible implementation, the specific implementation manner that the session management function network element enables the first PDU session or the first network slice to be controlled by the network slice access is as follows: the session management function network element indicates to the network slice admission control function network element to increase the PDU session number of the first network slice by one; and/or the session management function network element indicates to the network slice admission control function network element to subject the first network slice to network slice access control.

In a possible implementation, the session management function network element sends, to the access and mobility management function network element, sixth information based on the fifth information, the sixth information being used to indicate that the first PDU session or the first network slice is not associated with priority traffic.

Based on the possible implementation manner, after the access and mobility management function network element receives the sixth information, the terminal device corresponding to the first PDU session can be timely subjected to access control of the first network slice or the first network slice is subjected to access control based on the sixth information.

In a second aspect, the present application provides a network slice access control method, including: when a first PDU session is established, a session management function network element enables the first PDU session not to be controlled by network slice access; if the session management function network element does not receive the second information within a preset time period after the first PDU session is established, enabling the first PDU session to be controlled by network slice access; the second information is from a policy control function network element or a unified data storage library or a unified data management function network element, the second information indicates a first PDU session in the first network slice or a terminal device associated priority service corresponding to the first network slice or the first PDU session, or the second information is an allocation and preemption priority ARP corresponding to the first PDU session, and a value of the second information is a first value.

Based on the method described in the second aspect, when establishing the first PDU session, the session management function network element defaults to leaving the first PDU session out of network slice access control. The network slice admission control function network element is not required to be instructed to increase the number of PDU sessions of the first network slice by one immediately after the first PDU session and to decrease the number of PDU sessions of the first network slice by one again after the second information is received. And is beneficial to reducing signaling interaction.

In a possible implementation, if the session management function network element receives the second information within a preset time period after the first PDU session is established, the session management function network element sends third information to the access and mobility management function network element based on the second information, where the third information is used to indicate the first PDU session or the first network slice or the terminal device associated priority service corresponding to the first PDU session.

By sending the third information to the access and mobility management function network element, after the access and mobility management function network element receives the third information, the terminal device corresponding to the first PDU session can be timely isolated from access control of the first network slice or isolated from access control of the first network slice based on the third information.

In a possible implementation, the specific implementation manner that the session management function network element makes the first PDU session not controlled by the network slice access is: when the PDU session number of the first network slice reaches the PDU session number threshold corresponding to the first network slice, the session management function network element does not refuse to establish the first PDU session; and/or not indicating to the network slice admission control function network element to increase the number of PDU sessions of the first network slice by one.

In a possible implementation, the specific implementation manner of the session management function network element enabling the first PDU session to be controlled by network slice access is as follows: the session management function network element indicates to the network slice admission control function network element to increment the number of PDU sessions of the first network slice by one.

In one possible implementation, if the session management function network element receives the fifth information after receiving the second information, the session management function network element makes the first PDU session under network slice access control based on the fifth information; the fifth information is from a policy control function network element or a unified data storage library or a unified data management function network element, and the fifth information is used for indicating that the terminal equipment corresponding to the first PDU session or the first network slice or the first PDU session is not associated with a priority service, or the fifth information is an allocation and preemption priority ARP corresponding to the first PDU session, and the value of the fifth information is a second value.

Based on the possible implementation manner, the session management function network element can timely enable the first PDU session or the first network slice to be under access control of the network slice based on the fifth information sent by the policy control function network element.

In a possible implementation, the session management function network element sends, to the access and mobility management function network element, sixth information based on the fifth information, where the sixth information is used to indicate that the terminal device corresponding to the first PDU session or the first network slice or the first PDU session is not associated with the priority service. Based on the possible implementation manner, after the access and mobility management function network element receives the sixth information, the terminal device corresponding to the first PDU session can be timely subjected to access control of the first network slice or the first network slice is subjected to access control based on the sixth information.

In a third aspect, the present application provides a network slice access control method, including: the access and mobility management function network element receives third information from the session management function network element or the unified data repository or the unified data management function network element, where the third information is used to indicate a first PDU session in a first network slice or a terminal device associated with a priority service, and the terminal device is a terminal device corresponding to the first PDU session, or the terminal device is a terminal device requesting to register the first network slice; and the access and mobile management functional network element enables the terminal equipment not to be subjected to access control of the first network slice or enables the first network slice not to be subjected to access control based on the third information.

Based on the method described in the third aspect, the access and mobility management function network element can timely enable the terminal device or the first network slice to be free from network slice access control when the first PDU session or the first network slice or the terminal device is associated with the priority service, thereby avoiding interruption or incapability of initiating the priority service.

In a possible implementation, the specific implementation manner that the access and mobility management function network element enables the terminal device not to be controlled by the access of the first network slice, or enables the first network slice not to be controlled by the access, is as follows:

the access and mobility management function network element indicates to the network slice admission control function network element to reduce the number of the terminal devices of the first network slice by one; and/or;

when the number of the terminal equipment of the first network slice reaches the threshold value of the number of the terminal equipment corresponding to the first network slice, the access and mobile management functional network element does not reject the first network slice requested by the terminal equipment; and/or the presence of a gas in the gas,

the access and mobility management function network element does not indicate to the network slice admission control function network element to increase the number of the terminal equipment of the first network slice by one; and/or the presence of a gas in the atmosphere,

the access and mobility management function network element indicates to the network slice admission control function network element that the first network slice is not under network slice access control.

In one possible implementation, the access and mobility management function network element receives sixth information from the session management function network element or the unified data repository or the unified data management function network element, where the sixth information is used to indicate that the first PDU session or the first network slice or the terminal device is not associated with a priority service; and the access and mobile management functional network element enables the terminal equipment to be under access control of the first network slice or enables the first network slice to be under access control based on the sixth information.

Based on the possible implementation manner, when the first PDU session or the first network slice is not associated with the priority service, the access and mobility management function network element can enable the terminal device to be under access control of the first network slice in time, or enable the first network slice to be under access control.

In a possible implementation, the specific implementation manner of enabling the terminal device to be under access control of the first network slice, or enabling the first network slice to be under access control by the access and mobility management function network element, is:

the access and mobility management function network element indicates to the network slice admission control function network element to increase the number of the terminal devices of the first network slice by one; and/or;

the access and mobility management function network element indicates to the network slice admission control function network element that the first network slice is under network slice access control.

In a fourth aspect, the present application provides a network slice access control method, including: the method comprises the steps that a policy control function network element receives first information from an application function network element or a unified data storage library or a unified data management function network element; the policy control function network element sends second information to the session management function network element based on the first information; the first information is used for indicating a first Packet Data Unit (PDU) session in a first network slice or a terminal equipment associated priority service corresponding to the first PDU session; the second information is used for the session management function network element to enable the first packet data unit PDU session in the first network slice or the first network slice not to be controlled by the network slice access.

Based on the method described in the first aspect, when the first PDU session in the first network slice or the terminal device corresponding to the first PDU session is associated with the priority service, the session management function network element timely enables the first PDU session or the first network slice not to be controlled by the network slice access, thereby avoiding interruption or failure to initiate the priority service.

In a possible implementation, the second information is used to indicate a priority service associated with the terminal device corresponding to the first PDU session or the first network slice or the first PDU session, or the second information is an ARP that is allocated and preempted to the first PDU session, and a value of the second information is a first value. By using the ARP to indicate the first PDU session or the first network slice or the terminal equipment associated priority service corresponding to the first PDU session, no additional indication information is required to be sent to indicate the first PDU session or the first network slice associated priority service, which is beneficial to saving indication overhead.

In a possible implementation, after the policy control function network element sends the second information to the session management function network element, the policy control function network element may further receive fourth information from the application function network element or the unified data repository or the unified data management function network element; the policy control function network element sends fifth information to the session management function network element based on the fourth information; the fourth information is used for indicating that the first PDU session or the first network slice or the terminal equipment corresponding to the first PDU session is not associated with the priority service; the fifth information is for making the first PDU session or the first network slice under network slice access control.

Based on the possible implementation manner, when the first PDU session in the first network slice or the terminal device corresponding to the first PDU session is not associated with the priority service, the session management function network element enables the first PDU session or the first network slice to be under the access control of the network slice in time.

In a possible implementation, the fifth information is used to indicate that the terminal device corresponding to the first PDU session or the first network slice or the first PDU session is not associated with a priority service, or the fifth information is an ARP that is allocated and preempted to the first PDU session, and a value of the fifth information is a second value. The first PDU session or the first network slice or the terminal equipment corresponding to the first PDU session is indicated to be not associated with the priority service by using the ARP, and no additional indication information is required to be sent to indicate that the first PDU session or the first network slice is not associated with the priority service, so that the indication overhead is saved.

In a fifth aspect, the present application provides a communication apparatus, where the communication apparatus may be a session management function network element, may also be an apparatus in the session management function network element, or may be an apparatus capable of being used in cooperation with the session management function network element. Wherein, the communication device can also be a chip system. The communication device may perform the method of the first or second aspect. The functions of the communication device can be realized by hardware, and can also be realized by executing corresponding software by hardware. The hardware or software includes one or more units or modules corresponding to the above functions. The unit or module may be software and/or hardware. The operations and advantages performed by the communication device can be referred to the methods and advantages described in the first aspect or the second aspect.

In a sixth aspect, the present application provides a communication apparatus, where the communication apparatus may be an access and mobility management function network element, or an apparatus in an access and mobility management function network element, or an apparatus that can be used in cooperation with an access and mobility management function network element. Wherein, the communication device can also be a chip system. The communication device may perform the method of the third aspect. The functions of the communication device can be realized by hardware, and can also be realized by executing corresponding software by hardware. The hardware or software includes one or more units or modules corresponding to the above functions. The unit or module may be software and/or hardware. The operations and advantageous effects performed by the communication apparatus can be found in the method and advantageous effects described in the third aspect.

In a seventh aspect, the present application provides a communication device, where the communication device may be a policy control function network element, may also be a device in a policy control function network element, or may be a device that can be used in cooperation with a policy control function network element. Wherein, the communication device can also be a chip system. The communication device may perform the method of the fourth aspect. The functions of the communication device can be realized by hardware, and can also be realized by executing corresponding software by hardware. The hardware or software includes one or more units or modules corresponding to the above functions. The unit or module may be software and/or hardware. The operations and advantages performed by the communication device may refer to the methods and advantages described in the fourth aspect above.

In an eighth aspect, the present application provides a communication device comprising a processor, wherein the method according to any one of the first to fourth aspects is performed when the processor invokes a computer program in a memory.

In a ninth aspect, the present application provides a communication device comprising a processor and a memory, the processor and the memory coupled; a processor is configured to implement the method of any one of the first to fourth aspects.

In a tenth aspect, the present application provides a communication device comprising a processor, a memory, and a transceiver, the processor and the memory coupled; the transceiver is for transceiving data and the processor is for implementing a method as in any one of the first to fourth aspects.

In an eleventh aspect, the present application provides a communication device comprising a processor and an interface, the processor and the interface being coupled; the interface is adapted to receive or output signals and the processor is adapted to execute code instructions to cause a method according to any of the first to fourth aspects to be performed.

In a twelfth aspect, the present application provides a computer-readable storage medium having stored thereon a computer program or instructions for implementing the method according to any one of the first to fourth aspects when executed by a communication device.

In a thirteenth aspect, the present application provides a computer program product comprising instructions that, when read and executed by a communication apparatus, cause the communication apparatus to perform the method according to any one of the first to fourth aspects.

In a fourteenth aspect, the present application provides a communication system comprising a communication device for performing the method of the first or second aspect and a communication device for performing the method of the fourth aspect.

In a fifteenth aspect, the present application provides a communication system comprising a communication device for performing the method of the first or second aspect and a communication device for performing the method of the third aspect.

Drawings

Fig. 1 is a schematic diagram of a 5G non-roaming service-based interface system architecture according to an embodiment of the present application;

FIG. 2 is a schematic diagram of a 5G non-roaming reference point-based system architecture according to an embodiment of the present application;

fig. 3 is a schematic diagram of a system architecture based on a service interface in a roaming scenario of Local Breakout (LBO) according to an embodiment of the present application;

fig. 4 is a schematic diagram of a reference point-based system architecture in an LBO roaming scenario according to an embodiment of the present disclosure;

fig. 5 is a schematic diagram of a system architecture based on a service interface in a Home Routed (HR) roaming scenario according to an embodiment of the present application;

FIG. 6 is a schematic diagram of a reference point-based system architecture in a roaming scenario of an HR according to an embodiment of the present disclosure;

fig. 7 is a flowchart illustrating a network slice access control method according to an embodiment of the present application;

fig. 8 is a flowchart illustrating a network slice access control method according to an embodiment of the present application;

fig. 9 is a flowchart illustrating a network slice access control method according to an embodiment of the present application;

fig. 10 is a flowchart illustrating a network slice access control method according to an embodiment of the present application;

fig. 11 is a flowchart illustrating a network slice access control method according to an embodiment of the present application;

fig. 12 is a flowchart illustrating a network slice access control method according to an embodiment of the present application;

fig. 13 is a flowchart illustrating a network slice access control method according to an embodiment of the present application;

fig. 14 is a flowchart illustrating a network slice access control method according to an embodiment of the present application;

fig. 15 is a flowchart illustrating a network slice access control method according to an embodiment of the present application;

fig. 16 is a flowchart illustrating a network slice access control method according to an embodiment of the present application;

fig. 17 is a flowchart illustrating a network slice access control method according to an embodiment of the present application;

fig. 18 is a flowchart illustrating a network slice access control method according to an embodiment of the present application;

fig. 19 is a schematic structural diagram of a communication device according to an embodiment of the present application;

fig. 20 is a schematic structural diagram of a communication device according to an embodiment of the present application;

fig. 21 is a schematic structural diagram of a chip according to an embodiment of the present application.

Detailed Description

The terms "first" and "second," and the like in the description, claims, and drawings of the present application are used for distinguishing between different objects and not for describing a particular order. Furthermore, the terms "include" and "have," as well as any variations thereof, are intended to cover a non-exclusive inclusion. For example, a process, method, system, article, or apparatus that comprises a list of steps or elements is not limited to only those steps or elements listed, but may alternatively include other steps or elements not listed, or inherent to such process, method, article, or apparatus.

Reference herein to "an embodiment" means that a particular feature, structure, or characteristic described in connection with the embodiment can be included in at least one embodiment of the application. The appearances of the phrase in various places in the specification are not necessarily all referring to the same embodiment, nor are separate or alternative embodiments mutually exclusive of other embodiments. It is explicitly and implicitly understood by one skilled in the art that the embodiments described herein can be combined with other embodiments.

In this application, "at least one" means one or more, "a plurality" means two or more, "at least two" means two or three and three or more, "and/or" for describing the correspondence of the associated objects, indicating that three relationships may exist, for example, "a and/or B" may indicate: only A, only B and both A and B are present, wherein A and B may be singular or plural. The character "/" generally indicates that the former and latter associated objects are in an "or" relationship. "at least one of the following" or similar expressions refer to any combination of these items, including any combination of single item(s) or plural items. For example, at least one (one) of a, b, or c, may represent: a, b, c, "a and b", "a and c", "b and c", or "a and b and c", wherein a, b, c may be single or plural.

In order to better understand the present application, several system architectures provided by the embodiments of the present application are described below:

fig. 1 is a schematic diagram of a 5G non-roaming service-based interface system architecture according to an embodiment of the present application.

Fig. 2 is a schematic diagram of a 5G non-roaming reference point-based system architecture according to an embodiment of the present application.

Fig. 3 is a schematic diagram of a system architecture based on a service interface in a roaming scenario of Local Breakout (LBO) according to an embodiment of the present application.

Fig. 4 is a schematic diagram of a reference point-based system architecture in an LBO roaming scenario according to an embodiment of the present disclosure.

Fig. 5 is a schematic diagram of a system architecture based on a service interface in a Home Routed (HR) roaming scenario according to an embodiment of the present application.

Fig. 6 is a schematic diagram of a reference point-based system architecture in a roaming scenario of an HR according to an embodiment of the present disclosure.

The system architectures shown in fig. 1 to 6 are divided into a terminal device, an operator network, and a Data Network (DN).

(1) The terminal equipment may also be referred to as User Equipment (UE). The terminal device in this embodiment is a device with a wireless transceiving function, and may communicate with one or more Core Networks (CNs) through AN access network device in AN Access Network (AN). A terminal device can also be called an access terminal, subscriber unit, subscriber station, mobile, remote station, remote terminal, mobile device, user terminal, wireless network device, user agent, or user equipment, etc. The terminal equipment can be deployed on land, including indoors or outdoors, handheld or vehicle-mounted; can also be deployed on the water surface (such as a ship and the like); and may also be deployed in the air (e.g., airplanes, balloons, satellites, etc.). The terminal device may be a cellular phone (cellular phone), a cordless phone, a Session Initiation Protocol (SIP) phone, a smart phone (smart phone), a mobile phone (mobile phone), a Wireless Local Loop (WLL) station, a Personal Digital Assistant (PDA), a handheld device having a wireless communication function, a computing device or other device connected to a wireless modem, a vehicle-mounted device, a wearable device, a drone device or internet of things, a terminal in a vehicle network, a terminal in a fifth generation mobile communication (5G) network and any form of terminal in a future network, a relay user device or a terminal in a future public land mobile communication network (PLMN), and the like, wherein the relay user device may be, for example, a 5G home gateway (PLMN). For example, the terminal device may be a Virtual Reality (VR) terminal, an Augmented Reality (AR) terminal, a wireless terminal in industrial control (industrial control), a wireless terminal in self driving (self driving), a wireless terminal in remote medical (remote medical), a wireless terminal in smart grid, a wireless terminal in transportation safety, a wireless terminal in smart city (smart city), a wireless terminal in smart home (smart home), or the like. The embodiments of the present application do not limit this.

(2) The operator network may include a Network Slice Selection Function (NSSF), a network open function (NEF), a network storage function (NRF), a Policy Control Function (PCF), a Unified Data Management (UDM) network element, AN Application Function (AF), a network slice and SNPN identity verification and authorization function (nsaaf), AN authentication server function (SMF), a service communication agent (service communication x, service admission control function (sff), a network slice admission control function (AMF), a session management function (session management function, SMF), a service communication agent (service communication x, SCP), a network slice admission control function (rsf), a network slice access function (sip), a network access function (sip), a wireless access network (PCF), and a unified data access repository (network access network).

The application mainly relates to an AF network element, a PCF network element, an SMF network element, an AMF network element, an NSACF network element, a UDM network element and a UDR. These several network elements are further described below:

AF network element: mainly supports the interaction with the 3GPP core network to provide services, such as influencing data routing decision, strategy control function or providing some services of a third party to the network side.

PCF network element: the method mainly supports the provision of a unified policy framework to control network behaviors, provides policy rules to a control layer network function, and is responsible for acquiring user subscription information related to policy decision.

SMF network element: the method is mainly responsible for session management in the mobile network, such as session establishment, modification and release. The specific functions include allocating an IP address to a user, selecting a UPF providing a message forwarding function, and the like.

AMF network element: the method is mainly responsible for mobility management in the mobile network, such as user location update, user registration network, user switching and the like.

NSACF network element: and the method supports monitoring and controlling the number of registered users of each network slice. Support monitoring and controlling the number of PDU sessions established per network slice. Event-based network slice status notification is supported and reported to other NFs.

UDM network element: the method is used for generating authentication trusts, user identification processing (such as storing and managing user permanent identities and the like), access authorization control, subscription data management and the like.

UDR: including subscription data for UDMs, policy data for PCFs, open structured data for NEFs, and application data (including application-detected Packet Flow Descriptions (PFDs), AF request information for multiple UEs, etc.). UDRs may be deployed in each PLMN, and function as follows:

-UDRs visited by the NEF belong to the same PLMN the NEF is located in.

-if the UDM supports split architecture, the UDR visited by the UDM belongs to the same PLMN the UDM is located in.

-the UDR visited by the PCF belongs to the same PLMN the PCF is in.

(3) DN: refers to a service network providing data transmission service for users, such as IMS (IP multimedia service), internet, etc. The UE accesses the DN through a Packet Data Unit (PDU) session established between the UE and the DN.

The following describes the network slice access control method and the communication device provided by the present application in detail:

the following embodiments relate to an application function network element, a policy control function network element, a session management function network element, an access and mobility management function network element, a network slice admission control function network element, a unified data repository, or a unified data management function network element. In the following, an application function network element is taken as an AF network element, a policy control function network element is taken as a PCF network element, a session management function network element is taken as an SMF network element, an access and mobility management function network element is taken as an AMF network element, a network slice admission control function network element is taken as an NSACF network element, a unified data repository is taken as an UDR, and a unified data management function network element is taken as an UDM. The application function network element, the policy control function network element, the session management function network element, the access and mobility management function network element, the network slice admission control function network element, the unified data repository or the unified data management function network element may also be other network devices having an application function, a policy control function, a session management function, an access and mobility management function, a network slice admission control function, a data storage function and a data management function, which is not limited in the embodiments of the present application. Specifically, for example, in a scenario of interworking with an Evolved Packet Core (EPC), the session management function network element may be an SMF + PGW-C (session management function + packet data network for control plane) network element, and the access and mobility management function network element may be a Mobility Management Entity (MME) or an AMF network element.

Referring to fig. 7, fig. 7 is a flowchart illustrating a network slice access control method according to an embodiment of the present disclosure. As shown in fig. 7, the network slice access control method includes the following sections 701 to 703. Wherein:

701. and the AF network element sends the first information to the PCF network element. Accordingly, the PCF network element may receive the first information.

Wherein the first information is used to indicate that a first PDU session in a first network slice is associated with priority traffic. The first PDU session associated priority service representation: the first PDU session is delivering priority traffic or the first PDU session is not currently delivering priority traffic but is delivering priority traffic in the future (i.e., the first PDU session may be delivering priority traffic).

In the embodiment of the present application, the AF network element may identify whether the first PDU session is associated with the priority service, so the AF network element may send the first information to the PCF network element.

In this embodiment, the AF network element may send the first information to the PCF network element after the first PDU session is established. For example, the first information may be an emergency indicator (emergency indicator), a priority indicator (priority indicator) of (MPS 5 GS), or the like.

702. And the PCF network element sends second information to the SMF network element based on the first information. Accordingly, the SMF network element may receive the second information.

The second information is used for the SMF network element to enable the first PDU session in the first network slice or the first network slice not to be controlled by network slice access.

In one possible implementation, the second information is used to indicate that the first PDU is a session associated priority service. That is, the PCF network element may indicate the first PDU session association priority service to the SMF network element, illustratively.

In another possible implementation, the second information is an allocation and preemption priority (ARP) corresponding to the first PDU session, and the value of the second information is the first value. That is, the PCF network element may implicitly indicate the first PDU session association priority traffic to the SMF network element via ARP.

The ARP may be carried in the policy information and sent to the SMF network element. For example, the policy information may be a PCC rule corresponding to the first PDU session. Alternatively, the policy information may be PDU session policy information corresponding to the first PDU session. Specifically, the ARP may be an ARP in a PCC rule corresponding to a certain service in the first PDU session, or may be an authorized default ARP of the first PDU session.

ARP contains information about priority, preemption capability, and preempted capability. This allows deciding whether QoS flow establishment/modification/handover is acceptable or needs to be rejected (admission control for GBR traffic in general) in case of resource restrictions. It can also be used to decide which existing QoS flow to preempt during resource restriction, i.e. which QoS flow to release resources. A smaller value of ARP indicates that the QoS flow cannot be preempted. Accordingly, the value of ARP may be set to a smaller value to indicate that the first PDU session associated priority traffic is indicated to the SMF network element. For example, the value of ARP may be set to 0 or 1. The first PDU session association priority service is indicated to the SMF network element by using the ARP, and no additional indication information is required to be sent to indicate the first PDU session association priority service, so that indication overhead is saved.

Alternatively, the second information may be some other information for the SMF network element to make the first PDU session in the first network slice or the first network slice not controlled by the network slice access.

703. The SMF network element enables the first PDU session or the first network slice in the first network slice not to be controlled by network slice access based on the second information.

That is, the SMF network element may only leave the first PDU session out of network slice access control based on the second information. Alternatively, the entire network slice in which the first PDU session is located is left access-free.

In a possible implementation, the SMF network element performs the NSAC procedure after acquiring the policy information from the PCF network element (instead of performing the NSAC procedure in the first step of PDU session establishment, that is, instead of performing the NSAC procedure when the SMF network element receives a PDU session establishment request from the terminal device).

In one possible implementation, the specific implementation manner of the SMF network element enabling the first PDU session in the first network slice or the first network slice not to be controlled by the network slice access (i.e. the SMF network element skips the corresponding NSAC flow) is as follows: the SMF network element indicates to the NSACF network element to reduce the PDU conversation quantity of the first network slice by one; and/or the SMF network element indicates to the NSACF network element to leave the first network slice free of network slice access control.

For example, the NSACF network element has counted the first PDU session to the number of PDU sessions of the first network slice since the first PDU session has already been established. Therefore, a specific implementation of the SMF network element to make the first PDU session not controlled by the network slice access may be: the SMF network element indicates to the NSACF network element to reduce the number of PDU sessions of the first network slice by one. I.e., the NSACF network element does not count the first PDU session to the number of PDU sessions of the first network slice.

For another example, the specific implementation manner of the SMF network element enabling the first network slice not to be controlled by network slice access is as follows: the SMF network element indicates to the NSACF network element to make the first network slice free of network slice access control. I.e. the NSACF network element does not count the number of PDU sessions of the first network slice.

Optionally, the NSACF network element may further notify other SMF network elements that the PDU session of the first network slice is not controlled by the network slice access. The SMF network element may not need to report the PDU session number change of the first network slice to the NSACF network element. The other SMF network elements may be SMF network elements within all service ranges of the NSACF network element; or may be all SMF network elements serving the terminal device corresponding to the first PDU session. The service terminal device specifically refers to a PDU session corresponding to the service terminal device. The latter requires that the SMF network element reports the UE identity when reporting PDU session number change to the NSACF network element, so that the NSACF network element knows which SMF network elements serve a session of a certain terminal device.

In a possible implementation, the SMF network element may further send, to the AMF network element, third information based on the second information, where the third information is used to indicate that the first PDU session is associated with the priority service. Thus, after receiving the third information, the AMF network element may timely enable the terminal device corresponding to the first PDU session to be not under access control of the first network slice, or enable the first network slice to be not under access control, based on the third information. For the relevant operations after the AMF network element receives the third information, reference may be made to the description in the embodiment corresponding to fig. 15, which is not described herein again.

It can be seen that by implementing the method described in fig. 7, when the first PDU session is associated with a priority service, the SMF network element can timely enable the first PDU session or the first network slice in the first network slice to be not controlled by the network slice access, thereby avoiding interruption or failure to initiate the priority service.

Referring to fig. 8, fig. 8 is a flowchart illustrating another network slice access control method according to an embodiment of the present application.

As shown in fig. 8, the network slice access control method includes the following sections 801 to 806. Wherein:

801. and the AF network element sends the first information to the PCF network element. Accordingly, the PCF network element may receive the first information.

802. And the PCF network element sends second information to the SMF network element based on the first information. Accordingly, the SMF network element may receive the second information.

803. The SMF network element enables the first PDU session or the first network slice in the first network slice not to be controlled by network slice access based on the second information.

For the related description of step 801 to step 803, reference may be made to the description of step 701 to step 703 in fig. 7, which is not repeated herein.

804. And the AF network element sends the fourth information to the PCF network element. Accordingly, the PCF network element may receive the fourth information.

In this embodiment, the fourth information is used to indicate that the first PDU session is not associated with a priority service.

805. And the PCF network element sends fifth information to the SMF network element based on the fourth information. Accordingly, the SMF network element may receive the fifth information.

In this embodiment, the fifth information is used by the SMF network element to enable the first PDU session or the first network slice to be controlled by network slice access.

In one possible implementation, the fifth information is used to indicate that the first PDU session is not associated with priority traffic. I.e., the PCF network element may indicate to the SMF network element, explicitly, that the first PDU session is not associated with priority traffic.

In another possible implementation, the fifth information is an ARP corresponding to the first PDU session, and a value of the fifth information is a second value. I.e. the PCF network element may implicitly indicate to the SMF network element via ARP that the first PDU session is not associated with priority traffic. Wherein the second value is different from the first value above. The second value may be a larger value.

Alternatively, the fifth information may be some other information for the SMF network element to make the first PDU session or the first network slice under the network slice access control.

806. The SMF network element subjects the first PDU session or the first network slice to network slice access control based on the fifth information.

That is, the SMF network element may subject only the first PDU session to network slice access control based on the fifth information. Alternatively, the entire network slice in which the first PDU session is located is made access controlled. For example, if the SMF network element may only leave the first PDU session under network slice access control based on the second information, the SMF network element may only leave the first PDU session under network slice access control based on the fifth information. If the SMF network element can leave the entire network slice in which the first PDU session is located access-controlled based on the second information, the SMF network element can leave the entire network slice in which the first PDU session is located access-controlled based on the fifth information.

In a possible implementation, a specific implementation manner of the SMF network element enabling the first PDU session or the first network slice to be subjected to network slice access control (i.e. the SMF network element performs the corresponding NSAC procedure) is as follows: the SMF network element indicates to the NSACF network element to add one to the PDU session number of the first network slice; and/or the SMF network element indicates to the NSACF network element to subject the first network slice to network slice access control.

For example, a specific implementation of the SMF network element making the first PDU session under network slice access control may be: the SMF network element indicates to the NSACF network element to increment the number of PDU sessions of the first network slice by one. That is, the NSACF network element counts the first PDU session into the number of PDU sessions of the first network slice.

For another example, the specific implementation manner of the SMF network element making the first network slice under the access control of the network slice is as follows: the SMF network element indicates to the NSACF network element to subject the first network slice to network slice access control. That is, the NSACF network element will count the number of PDU sessions of the first network slice. Optionally, the NSACF network element may further notify other SMF network elements that the PDU session of the first network slice is under network slice access control. The SMF network element may report the PDU session number change of the first network slice to the NSACF network element. The other SMF network elements may be SMF network elements within all service ranges of the NSACF network element; or may be all SMF network elements serving the terminal device corresponding to the first PDU session.

In one possible implementation, the SMF network element sends, to the AMF network element, sixth information based on the fifth information, where the sixth information is used to indicate that the first PDU session is not associated with priority traffic. Thus, after receiving the sixth information, the AMF network element may enable the terminal device corresponding to the first PDU session to be under access control of the first network slice in time or enable the first network slice to be under access control based on the sixth information. For the relevant operations after the AMF network element receives the sixth information, refer to the description in the embodiment corresponding to fig. 16, which is not described herein again. The AMF network element may also be other network devices with access and mobility management functions.

By performing the method described in fig. 8, the SMF network element is able to timely subject the first PDU session or the first network slice to network slice access control when the first PDU session is not associated with priority traffic.

Referring to fig. 9, fig. 9 is a flowchart illustrating another network slice access control method according to an embodiment of the present application.

As shown in fig. 9, the network slice access control method includes the following sections 901 to 903. Wherein:

901. and the UDR/UDM network element sends the first information to the PCF network element. Accordingly, the PCF network element may receive the first information.

In this embodiment of the present application, the first information may be subscription information or application information in the UDR/UDM network element. The application information may be written into the UDR/UDM network element by the AF network element in advance through a network open function (NEF) network element.

In one possible implementation, the first information is used to indicate that the first network slice is associated with priority traffic. Throughout the embodiments of the present application, the first network slice associated priority service indicates: the first network slice is delivering priority traffic, or the first network slice is not currently delivering priority traffic but is to be delivered in the future (i.e., the first network slice may deliver priority traffic), or subscribed priority traffic may be used at the first network slice.

Optionally, the first information is used to indicate that the first network slice associated priority service specifically may be: the first information is used to indicate that a first DNN in a first network slice is associated with priority traffic. The first network slice is the network slice in which the first PDU session is located. The first DNN is a Data Network Name (DNN) where the first PDU session is located. Throughout the embodiments of the present application, the first DNN associated priority service indicates: the first DNN is delivering priority traffic, or the first DNN is not currently delivering priority traffic but is to deliver priority traffic in the future (i.e., the first DNN may deliver priority traffic), or subscribed priority traffic may be used at the first DNN.

In another possible implementation, the first information may also indicate that the terminal device/User is associated with a priority service. Throughout the embodiments of the present application, the service of the terminal device associated with the priority may refer to: the terminal device is delivering the priority service, or the terminal device is not currently delivering the priority service but is to deliver the priority service in the future (i.e., the terminal device may deliver the priority service), or the terminal device may use a subscribed priority service (indicating the user is subscribed to MPS). Namely, the terminal device/User is the terminal device/User corresponding to the first PDU session. For example, the subscription information includes MPS priority.

In one possible implementation, the UDR/UDM network element may send the first information to the PCF network element during a first PDU session setup. For example, in the process of establishing the first PDU session, the PCF network element may request the UDM network element to obtain subscription information of the terminal device corresponding to the first PDU session in the first network slice or the first DNN.

In another possible implementation, the UDM network element/UDR may also send the first information to the PCF network element after the first PDU session is established. For example, if the UDM network element/UDR detects that the subscription information or the application information is updated, the UDM network element/UDR may send the first information to the PCF network element.

902. And the PCF network element sends second information to the SMF network element based on the first information. Accordingly, the SMF network element may receive the second information.

In a possible implementation, the second information is used to indicate a first network slice in which the first PDU session is located or a terminal device associated priority service corresponding to the first PDU session. That is, the PCF network element may indicate, to the SMF network element, the first network slice in which the first PDU session is located or the terminal device associated priority service corresponding to the first PDU session.

In another possible implementation, the second information is an ARP corresponding to the first PDU session, and the value of the second information is the first value. I.e. the PCF network element may implicitly indicate the first network slice associated priority traffic to the SMF network element by ARP.

The value of ARP may be set to a smaller value to indicate that the first network slice associated priority traffic is indicated to the SMF network element. For example, the value of ARP may be set to 0 or 1. The ARP is used for indicating the first network slice associated priority service to the SMF network element, and no additional indication information is required to be sent to indicate the first network slice associated priority service, so that indication overhead is saved.

Alternatively, the second information may be some other information used by the SMF network element to make the first PDU session in the first network slice or the first network slice not under the access control of the network slice.

903. The SMF network element enables the first PDU session or the first network slice in the first network slice not to be controlled by network slice access based on the second information.

In a possible implementation, the specific implementation manner of the SMF element enabling the first PDU session in the first network slice or the first network slice not to be subject to the network slice access control (i.e. the SMF element skips the corresponding NSAC flow) is: when the PDU session number of the first network slice reaches the PDU session number threshold corresponding to the first network slice, the SMF network element does not refuse to establish the first PDU session; and/or the SMF network element does not indicate to the NSACF network element to increase the number of PDU sessions of the first network slice by one; and/or the SMF network element indicates to the NSACF network element to leave the first network slice free of network slice access control.

For example, a specific implementation of the SMF network element to make the first PDU session not controlled by the network slice access may be: when the PDU session number of the first network slice reaches the PDU session number threshold corresponding to the first network slice, the SMF network element does not refuse to establish the first PDU session; and/or the SMF network element does not indicate to the NSACF network element to add one to the number of PDU sessions of the first network slice, i.e., the NSACF network element does not count the first PDU session to the number of PDU sessions of the first network slice.

For another example, the specific implementation manner of the SMF network element making the first network slice not controlled by the network slice access is as follows: the SMF network element indicates to the NSACF network element to make the first network slice free of network slice access control. I.e. the NSACF network element does not count the number of PDU sessions of the first network slice.

Optionally, the NSACF network element may further notify other SMF network elements that the PDU session of the first network slice is not under network slice access control. The SMF network element may not need to report the PDU session number change of the first network slice to the NSACF network element. The other SMF network elements may be SMF network elements within all service ranges of the NSACF network element; or may be SMF network elements of all UEs serving the first PDU session.

In a possible implementation, the SMF network element may further send third information to the AMF network element based on the second information, where the third information is used to indicate that the first network slice is associated with the priority service. Thus, after receiving the third information, the AMF network element may timely enable the terminal device corresponding to the first PDU session to be not under access control of the first network slice, or enable the first network slice to be not under access control, based on the third information. For the relevant operations after the AMF network element receives the third information, reference may be made to the description in the embodiment corresponding to fig. 15, which is not described herein again. The AMF network element may also be other network devices with access and mobility management functions.

It can be seen that, by implementing the method described in fig. 9, when the terminal device corresponding to the first network slice or the first PDU session is associated with the priority service, the SMF network element can timely enable the first PDU session or the first network slice in the first network slice to be not controlled by network slice access, thereby avoiding interruption or failure to initiate the priority service.

Referring to fig. 10, fig. 10 is a flowchart illustrating another network slice access control method according to an embodiment of the present application.

As shown in fig. 10, the network slice access control method includes the following sections 1001 to 1006. Wherein:

1001. and the UDR/UDM network element sends the first information to the PCF network element. Accordingly, the PCF network element may receive the first information.

1002. And the PCF network element sends second information to the SMF network element based on the first information. Accordingly, the SMF network element may receive the second information.

1003. The SMF network element enables the first PDU session or the first network slice in the first network slice not to be controlled by network slice access based on the second information.

The specific implementation manners of steps 1001 to 1003 may refer to the specific implementation manners of steps 901 to 903 in the embodiment corresponding to fig. 9, which are not described herein again.

1004. And the UDR/UDM network element sends the fourth information to the PCF network element. Accordingly, the PCF network element may receive the fourth information.

In this embodiment, the fourth information is used to indicate that the first network slice is not associated with a priority service.

1005. And the PCF network element sends fifth information to the SMF network element based on the fourth information. Accordingly, the SMF network element may receive the fifth information.

In this embodiment, the fifth information is used by the SMF network element to enable the first PDU session or the first network slice to be under network slice access control.

In a possible implementation, the fifth information is used to indicate that the first network slice in which the first PDU session is located or the terminal device corresponding to the first PDU session is not associated with the priority service. That is, the PCF network element may indicate, to the SMF network element, the first network slice in which the first PDU session is located or the terminal device corresponding to the first PDU session is not associated with priority service.

In another possible implementation, the fifth information is an ARP corresponding to the first PDU session, and a value of the fifth information is a second value. That is, the PCF network element may implicitly indicate, through the ARP, to the SMF network element the first network slice in which the first PDU session is located or the terminal device corresponding to the first PDU session is not associated with the priority service. Wherein the second value is different from the first value above. The second value may be a larger value.

1006. The SMF network element subjects the first PDU session or the first network slice to network slice access control based on the fifth information.

The specific implementation of step 1006 may refer to the specific implementation of step 806 in the embodiment corresponding to fig. 8, which is not described herein again.

In a possible implementation, the SMF network element sends, to the AMF network element, sixth information based on the fifth information, where the sixth information is used to indicate that the first network slice is not associated with priority traffic. Thus, after receiving the sixth information, the AMF network element may enable the terminal device corresponding to the first PDU session to be under access control of the first network slice in time or enable the first network slice to be under access control based on the sixth information. For the relevant operations after the AMF network element receives the sixth information, refer to the description in the embodiment corresponding to fig. 16, which is not described herein again. The AMF network element may also be other network devices with access and mobility management functions.

By performing the method described in fig. 10, the SMF network element can timely make the first PDU session or the first network slice under the network slice access control when the terminal device corresponding to the first network slice or the first PDU session is not associated with priority traffic.

Referring to fig. 11, fig. 11 is a flowchart illustrating another network slice access control method according to an embodiment of the present application.

As shown in fig. 11, the network slice access control method includes the following 1101 to 1102 parts. Wherein:

1101. and the UDR/UDM network element sends the second information to the SMF network element. Accordingly, the SMF network element may receive the second information.

Optionally, the second information may be subscription information or application information in the UDR/UDM network element. The application information may be written into the UDR/UDM network element by the AF network element in advance through a network open function (NEF) network element.

In one possible implementation, the second information is used to indicate that the first network slice is associated with priority traffic. I.e. the UDR/UDM network element may indicate the first network slice associated priority traffic to the SMF network element explicitly. For the meaning of the first network slice associated priority service, reference may be made to the foregoing description, which is not repeated herein.

Optionally, the second information is used to indicate that the first network slice associated priority service specifically may be: the second information is used to indicate that the first DNN in the first network slice is associated with priority traffic. The first network slice is the network slice in which the first PDU session is located. The first DNN is a Data Network Name (DNN) where the first PDU session is located.

In another possible implementation, the second information may also indicate a terminal device/User associated priority service. The terminal equipment/User is the terminal equipment/User corresponding to the first PDU session. For example, the subscription information includes MPS priority. For the meaning of the terminal device/User associated priority service, reference may be made to the foregoing description, which is not repeated herein.

In this embodiment of the present application, the UDR/UDM network element may send the second information to the SMF network element in the session establishment procedure of the first PDU. For example, in the process of establishing the first PDU session, the SMF network element may request the UDM network element to acquire subscription information of the UE corresponding to the first PDU session in the first network slice or the first DNN.

Optionally, after the session establishment of the first PDU, the UDM network element/UDR may send the second information to the SMF network element. For example, if the UDM network element/UDR detects that the subscription information or the application information is updated, the UDM network element/UDR may send the second information to the SMF network element.

1102. The SMF network element enables the first PDU session or the first network slice in the first network slice not to be controlled by network slice access based on the second information.

In one possible implementation, the smaf network element performs the NSAC procedure after obtaining the subscription information from the UDM network element/UDR (instead of performing the NSAC procedure in the first PDU session establishment step, i.e. instead of performing the NSAC procedure when the SMF network element receives a PDU session establishment request from the terminal device).

The specific implementation manner of step 1102 may refer to the specific implementation manner of step 903 in the embodiment corresponding to fig. 9, which is not described herein again.

In a possible implementation, the SMF network element may further send, to the AMF network element, third information based on the second information, where the third information is used to indicate that the terminal device corresponding to the first network slice or the first PDU session is associated with the priority service. Thus, after receiving the third information, the AMF network element may timely enable the terminal device corresponding to the first PDU session to be not under access control of the first network slice or enable the first network slice to be not under access control based on the third information. For the relevant operations after the AMF network element receives the third information, reference may be made to the description in the embodiment corresponding to fig. 15, which is not described herein again. The AMF network element may also be other network devices with access and mobility management functions.

By executing the method described in fig. 11, when the terminal device corresponding to the first network slice or the first PDU session is not associated with the priority service, the SMF network element can timely enable the first PDU session or the first network slice in the first network slice to be not controlled by the network slice access, thereby avoiding interruption or failure to initiate the priority service.

Referring to fig. 12, fig. 12 is a flowchart illustrating another network slice access control method according to an embodiment of the present application.

As shown in fig. 12, the network slice access control method includes the following sections 1201 to 1204. Wherein:

1201. and the UDR/UDM network element sends the second information to the SMF network element. Accordingly, the SMF network element may receive the second information.

1202. The SMF network element enables the first PDU session or the first network slice in the first network slice not to be controlled by the network slice access based on the second information.

For specific implementation manners of steps 1201 to 1202, refer to specific implementation manners of steps 1101 to 1102 in the embodiment corresponding to fig. 11, which are not described herein again.

1203. And the UDR/UDM network element sends the fifth information to the SMF network element. Accordingly, the SMF network element may receive the fifth information.

Optionally, the fifth information is used to indicate that the terminal device corresponding to the first network slice or the first PDU session is not associated with the priority service. That is, the UDR/UDM network element may explicitly indicate to the SMF network element that the first network slice is not associated with priority traffic.

1204. The SMF network element subjects the first PDU session or the first network slice to network slice access control based on the fifth information.

The specific implementation of step 1204 can refer to the specific implementation of step 803 in the embodiment corresponding to fig. 8, which is not described herein again.

In a possible implementation, the SMF network element sends, to the AMF network element, sixth information based on the fifth information, where the sixth information is used to indicate that the terminal device corresponding to the first network slice or the first PDU session is not associated with the priority service. Thus, after receiving the sixth information, the AMF network element may enable the terminal device corresponding to the first PDU session to be under access control of the first network slice in time or enable the first network slice to be under access control based on the sixth information. For the relevant operations after the AMF network element receives the sixth information, refer to the description in the embodiment corresponding to fig. 16, which is not described herein again. The AMF network element may also be other network devices with access and mobility management functions.

By performing the method described in fig. 12, the SMF network element can timely make the first PDU session or the first network slice under the network slice access control when the terminal device corresponding to the first network slice or the first PDU session is not associated with priority traffic.

Referring to fig. 13, fig. 13 is a flowchart illustrating another network slice access control method according to an embodiment of the present application.

As shown in fig. 13, the network slice access control method includes the following parts 1301 to 1302. Wherein:

1301. when establishing the first PDU session, the SMF network element makes the first PDU session not controlled by the network slice access.

1302. And if the SMF network element does not receive the second information within the preset time period after the establishment of the first PDU session, the SMF network element enables the first PDU session to be controlled by network slice access.

The second information is from PCF network element or UDM network element or UDR, and the second information is used for SMF network element to make the first PDU session or the first network slice in the first network slice not controlled by network slice access.

Optionally, the second information indicates a first PDU session in the first network slice or a terminal device associated priority service corresponding to the first network slice or the first PDU session. Or the second information is an ARP corresponding to the first PDU session, and the value of the second information is the first value, that is, the second information implicitly indicates the first PDU session or the first network slice or the terminal device corresponding to the first PDU session to associate with the priority service. For the relevant operations of the PCF network element, reference may be made to the descriptions of the embodiments corresponding to fig. 7 to fig. 10, which are not described herein again. For the relevant operations of the UDM network element or the UDR, reference may be made to the descriptions in the embodiments corresponding to fig. 11 and fig. 12, which are not described herein again. For the meaning of the first PDU session or the first network slice or the terminal device associated with the priority service, reference may be made to the foregoing description, which is not repeated herein.

In a possible implementation, a specific implementation manner of the SMF element making the first PDU session not subject to network slice access control (i.e. the SMF element skips the corresponding NSAC flow) is as follows: when the PDU session number of the first network slice reaches the PDU session number threshold corresponding to the first network slice, the SMF network element does not refuse to establish the first PDU session; and/or, not indicating to the NSACF network element to add one to the number of PDU sessions of the first network slice, i.e. the first PDU session does not count into the number of PDU sessions of the first network slice.

In one possible implementation, the specific implementation of the SMF element making the first PDU session under the network slice access control (i.e. the SMF element performs the corresponding NSAC procedure) is as follows: the SMF network element indicates to the NSACF network element to add one to the number of PDU sessions of the first network slice, i.e. the first PDU session counts into the number of PDU sessions of the first network slice.

In a possible implementation, if the SMF network element receives the second information within a preset time period after establishing the first PDU session, the SMF network element sends, to the AMF network element, third information based on the second information, where the third information is used to indicate the first PDU session or the first network slice or the terminal device associated priority service corresponding to the first PDU session. Therefore, the AMF network element can timely enable the terminal equipment not to be controlled by the access of the first network slice or enable the first network slice not to be controlled by the access. For the relevant operations after the AMF network element receives the third information, reference may be made to the description in the embodiment corresponding to fig. 15, which is not described herein again.

By performing the method described in fig. 13, when establishing the first PDU session, the SMF network element defaults to leaving the first PDU session free from network slice access control. The NSACF network element need not be instructed to add one to the number of PDU sessions for the first network slice just after the first PDU session, and to subtract one from the number of PDU sessions for the first network slice again after receiving the second information. And is beneficial to reducing signaling interaction.

Referring to fig. 14, fig. 14 is a flowchart illustrating another network slice access control method according to an embodiment of the present application.

As shown in fig. 14, the network slice access control method includes the following sections 1401 to 1403. Wherein:

1401. when establishing the first PDU session, the SMF network element makes the first PDU session not controlled by the network slice access.

1402. And if the SMF network element does not receive the second information within the preset time period after the establishment of the first PDU session, the SMF network element enables the first PDU session to be controlled by network slice access.

For the description of step 1401 to step 1402, refer to the description of step 1301 to step 1302 in fig. 13, which is not described herein.

1403. And if the SMF network element receives the fifth information after receiving the second information, the SMF network element enables the first PDU session to be controlled by network slice access based on the fifth information.

And the fifth information is from a PCF network element or a UDM network element or a UDR, and the fifth information is used for the SMF network element to enable the first PDU session to be controlled by network slice access.

Optionally, the fifth information is used to indicate that the first PDU session or the first network slice or the terminal device corresponding to the first PDU session is not associated with the priority service, or the fifth information is an ARP corresponding to the first PDU session, and a value of the fifth information is a second value, that is, the ARP implicitly indicates to the SMF network element that the first PDU session or the first network slice or the terminal device corresponding to the first PDU session is not associated with the priority service. The second value is different from the first value.

In a possible implementation, the SMF network element may further send, to the AMF network element, sixth information based on the fifth information, where the sixth information is used to indicate that the terminal device corresponding to the first PDU session or the first network slice or the first PDU session is not associated with the priority service. Therefore, the AMF network element can enable the terminal equipment corresponding to the first PDU session to be under access control of the first network slice in time, or enable the first network slice to be under access control. For the relevant operations after the AMF network element receives the sixth information, refer to the description in the embodiment corresponding to fig. 16, which is not described herein again.

By performing the method described in fig. 14, the SMF network element is able to timely subject the first PDU session to network slice access control when the first PDU session is not associated with priority traffic.

Referring to fig. 15, fig. 15 is a flowchart illustrating another network slice access control method according to an embodiment of the present application.

As shown in fig. 15, the network slice access control method includes the following sections 1501 to 1502. Wherein:

1501. and the SMF network element sends the third information to the AMF network element. Accordingly, the AMF network element may receive the third information.

The third information is used for indicating the first PDU session or the first network slice or the terminal equipment associated priority service corresponding to the first PDU session.

As described in the embodiments corresponding to fig. 7 to fig. 12, after receiving the second information, the SMF network element sends third information to the AMF network element based on the second information.

As described in the embodiments corresponding to fig. 13 to fig. 14, if the SMF network element receives the second information within the preset time period after the first PDU session is established, the SMF network element sends third information to the AMF network element based on the second information.

1502. And the AMF network element enables the terminal equipment corresponding to the first PDU session not to be controlled by the access of the first network slice or enables the first network slice not to be controlled by the access based on the third information.

In this embodiment of the application, the AMF network element may only enable the terminal device corresponding to the first PDU session to be not controlled by network slice access based on the third information. Alternatively, the entire network slice in which the first PDU session is located is left access-free.

In a possible implementation, the specific implementation manner that the AMF network element enables the terminal device corresponding to the first PDU session to be not under access control of the first network slice, or enables the first network slice to be not under access control (that is, the AMF network element skips the corresponding NSAC procedure) is: the AMF network element indicates to the NSACF network element to reduce the number of the terminal equipment of the first network slice by one; and/or when the number of the terminal devices of the first network slice reaches the threshold value of the number of the terminal devices corresponding to the first network slice, the AMF network element does not reject the first network slice requested by the terminal devices; and/or the AMF network element does not indicate to the NSACF network element that the number of the terminal devices of the first network slice is increased by one; and/or, the AMF network element indicates to the NSACF network element that the first network slice is not under network slice access control.

For example, a specific implementation manner of the AMF network element enabling the terminal device corresponding to the first PDU session to be not subject to access control of the first network slice is as follows: and the AMF network element indicates to the NSACF network element to reduce the number of the terminal devices of the first network slice by one, namely the NSACF network element does not count the terminal devices corresponding to the first PDU session into the number of the terminal devices of the first network slice.

For example, in the scenario of interworking with EPC, it is possible (for example, a terminal device having a PDN connection moves from EPC to 5 GC) that a PDN connection (corresponding to PDU session) is established first, and then the terminal device registers in 5GS (since SMF + PGC has requested the number of terminal devices to NSACF minus one when moving from EPC to 5GC, AMF should newly apply for the number of terminal devices to NSACF plus 1), and when receiving the third information sent by the SMF (+ PGW-C) network element, the AMF network element may skip the NSAC procedure, and does not indicate to the NSACF network element to add one to the number of terminal devices of the first network slice. In order to avoid that the first network slice of the terminal device is rejected by the NSAC, which affects the proceeding of the priority traffic at the first network slice. Similar operations may also be performed during inter-PLMN Handover (inter-PLMN Handover) or during NSACF Handover (e.g. after a PDU session is established first, handover to a new PLMN or a service area of a new NSACF may be performed by the new NSACF for admission control, i.e. the old AMF has requested the number of terminal devices to the NSACF to be decreased by one, and at this time the new AMF should newly apply for the number of terminal devices to the new NSACF to be increased by 1). When receiving the third information sent by the SMF (+ PGW-C) network element, the AMF network element may skip the NSAC procedure, and does not indicate to the NSACF network element to add one to the number of terminal devices of the first network slice. In order to avoid that the first network slice of the terminal device is rejected by the NSAC, which affects the proceeding of the priority traffic at the first network slice.

For example, the specific implementation of the AMF network element to make the first network slice not under access control is: the AMF network element indicates to the NSACF network element that the first network slice is not under network slice access control. That is, the NSACF network element may not count the number of terminal devices of the first network slice. Optionally, the NSACF network element may further notify other AMF network elements that the terminal device of the first network slice is not controlled by the network slice access. The AMF network element may not need to report the change in the number of terminal devices of the first network slice to the NSACF network element. The other AMF network elements may be AMF network elements within all service ranges of the NSACF network element; or all AMF network elements serving the terminal device corresponding to the first PDU session. The service terminal device specifically refers to a PDU session corresponding to the service terminal device. The latter requires that the AMF network element reports the terminal device identifier when reporting the change of the number of the terminal devices to the NSACF network element, so that the NSACF network element knows which AMF network elements serve the session of a certain terminal device.

In one possible implementation, the third information may be passed with the AMF as a context of the terminal device.

By executing the method described in fig. 15, the AMF network element can timely enable the terminal device or the first network slice corresponding to the first PDU session to be not under the access control of the network slice when the first PDU session or the first network slice is associated with the priority service, thereby avoiding the interruption or the failure to initiate the priority service.

Referring to fig. 16, fig. 16 is a flowchart illustrating another network slice access control method according to an embodiment of the present application.

As shown in fig. 16, the network slice access control method includes the following sections 1601 to 1604. Wherein:

1601. and the SMF network element sends the third information to the AMF network element. Accordingly, the AMF network element may receive the third information.

1602. And the AMF network element enables the terminal equipment corresponding to the first PDU session not to be controlled by the access of the first network slice or enables the first network slice not to be controlled by the access based on the third information.

For the description of step 1601 to step 1602, refer to the description of step 1501 to step 1502 in fig. 15, which is not described herein again.

1603. And the SMF network element sends the sixth information to the AMF network element.

Wherein, the sixth information is used to indicate that the terminal device corresponding to the first PDU session or the first network slice or the first PDU session is not associated with the priority service.

As described in the embodiments corresponding to fig. 8, fig. 10, fig. 12, or fig. 14, after receiving the fifth information, the SMF network element sends sixth information to the AMF network element based on the fifth information.

1604. And the AMF network element enables the terminal equipment to be under access control of the first network slice or enables the first network slice to be under access control based on the sixth information.

In a possible implementation, the specific implementation manner of enabling the AMF network element to enable the terminal device to be under access control of the first network slice, or enabling the first network slice to be under access control (that is, the AMF network element does not skip the corresponding NSAC procedure) is: the AMF network element indicates to the NSACF network element to add one to the number of the terminal devices of the first network slice; and/or; the AMF network element indicates to the NSACF network element that the first network slice is under network slice access control.

Optionally, a specific implementation manner of enabling the AMF network element to enable the terminal device to be controlled by the access of the first network slice is as follows: and the AMF network element indicates to the NSACF network element to add one to the number of the terminal equipment of the first network slice.

Optionally, a specific implementation manner that the AMF network element enables the first network slice to be access-controlled is as follows: the AMF network element indicates to the NSACF network element that the first network slice is under network slice access control. Optionally, the NSACF network element may further notify other AMF network elements that the terminal device of the first network slice is under access control of the network slice. The AMF network element may report the change in the number of the terminal devices of the first network slice to the NSACF network element. The other AMF network elements may be the AMF network elements within all service ranges of the NSACF network element; or all AMF network elements serving the terminal device corresponding to the first PDU session.

In one possible implementation, the third information and the sixth information may be passed with the AMF as a context of the terminal device.

By performing the method described in fig. 16, the AMF network element can timely enable the terminal device or the first network slice corresponding to the first PDU session to be under the network slice access control when the first PDU session or the first network slice is not associated with priority traffic.

Referring to fig. 17, fig. 17 is a flowchart illustrating another network slice access control method according to an embodiment of the present application.

As shown in fig. 17, the network slice access control method includes the following parts 1701 to 1702. Wherein:

1701. and the UDR/UDM network element sends the third information to the AMF network element. Accordingly, the AMF network element may receive the third information.

The third information is used for indicating the first network slice or the terminal equipment to associate with the priority service. The terminal device is a terminal device requesting registration of the first network slice. For the meaning of the first network slice or the terminal device associated with the priority service, reference may be made to the foregoing description, which is not repeated herein.

The UDR/UDM network element may send the third information to the AMF network element in the process of registering the first network slice by the terminal device.

1702. And the AMF network element enables the terminal equipment not to be controlled by the access of the first network slice or the first network slice not to be controlled by the access based on the third information.

In a possible implementation, the specific implementation manner of enabling the AMF network element to enable the terminal device not to be controlled by the access of the first network slice, or enabling the first network slice not to be controlled by the access (that is, enabling the AMF network element to skip the corresponding NSAC procedure) is:

when the number of the terminal devices of the first network slice reaches the threshold value of the number of the terminal devices corresponding to the first network slice, the AMF network element does not reject the first network slice requested by the terminal devices; and/or the AMF network element does not indicate to the NSACF network element to increase the number of the terminal equipment of the first network slice by one; and/or, the AMF network element indicates to the NSACF network element that the first network slice is not under network slice access control.

For example, the specific implementation manner of the AMF network element enabling the terminal device not to be controlled by the access of the first network slice is: when the number of the terminal devices of the first network slice reaches the threshold value of the number of the terminal devices corresponding to the first network slice, the AMF network element does not reject the first network slice requested by the terminal devices; and/or the AMF network element does not indicate to the NSACF network element to increase the number of terminal devices of the first network slice by one.

For another example, the specific implementation manner of the AMF network element to enable the first network slice not to be controlled by the access is as follows: the AMF network element indicates to the NSACF network element that the first network slice is not under network slice access control. Optionally, the NSACF network element may further notify other AMF network elements that the terminal device of the first network slice is not under access control of the network slice. The AMF network element may not need to report the change in the number of terminal devices of the first network slice to the NSACF network element. The other AMF network elements may be AMF network elements within all service ranges of the NSACF network element; or may be an AMF network element of all UEs serving the first PDU session.

In one possible implementation, the AMF network element may notify the SMF network element that the first network slice is associated with priority traffic or that the terminal device may use priority traffic. The SMF network element may enable the terminal device to be in a PDU session of the first network slice or the first network slice to be free from network slice access control.

By performing the method described in fig. 17, the AMF network element is able to timely leave the terminal device or the first network slice requesting the first network slice out of network slice access control when the first network slice or the terminal device is associated with priority traffic.

Referring to fig. 18, fig. 18 is a flowchart illustrating another network slice access control method according to an embodiment of the present application.

As shown in fig. 18, the network slice access control method includes the following components 1801 to 1804. Wherein:

1801. and the UDR/UDM network element sends the third information to the AMF network element. Accordingly, the AMF network element may receive the third information.

1802. And the AMF network element enables the terminal equipment not to be controlled by the access of the first network slice or the first network slice not to be controlled by the access based on the third information.

The specific implementation of step 1801 to step 1802 may refer to the specific implementation of step 1701 to step 1702 in the embodiment corresponding to fig. 17, which is not described herein again.

1803. And the UDR/UDM network element sends the sixth information to the AMF network element. Accordingly, the AMF network element may receive the sixth information.

Wherein the sixth information is used to indicate that the first network slice or the terminal device is not associated with priority traffic. The terminal device is a terminal device requesting registration of the first network slice.

1804. And the AMF network element enables the terminal equipment to be under access control of the first network slice or enables the first network slice to be under access control based on the sixth information.

For a specific implementation of step 1804, reference may be made to the specific implementation of step 1604, which is not described herein.

In one possible implementation, the AMF network element may notify the SMF network element that the first network slice is not associated with priority traffic or that the terminal device may not use priority traffic. The SMF network element may cause the terminal device to be in a PDU session of the first network slice or the first network slice to be under network slice access control.

By performing the method described in fig. 18, the AMF network element is able to timely subject a terminal device or a first network slice requesting a first network slice to network slice access control when the first network slice or the terminal device is not associated with priority traffic.

It is to be understood that, in order to implement the functions of the above-described embodiments, the communication apparatus includes a corresponding hardware structure and/or software module that performs each function. Those of skill in the art will readily appreciate that the various illustrative elements and method steps described in connection with the embodiments disclosed herein may be implemented as hardware or combinations of hardware and computer software. Whether a function is performed in hardware or computer software driven hardware depends on the specific application scenario and design constraints of the solution.

Referring to fig. 19, fig. 19 is a schematic structural diagram of a communication device according to an embodiment of the present application. The communication apparatus shown in fig. 19 may be used to perform part or all of the functions of the session management function network element (e.g., SMF network element) in the embodiments of the methods described in fig. 7 to fig. 12. The device may be a session management function network element, a device in the session management function network element, or a device capable of being used in match with the session management function network element. Wherein, the communication device can also be a chip system. The communication apparatus shown in fig. 19 may include a communication unit 1901 and a processing unit 1902. The processing unit 1902 is configured to perform data processing. The communication unit 1901 is integrated with a receiving unit and a transmitting unit. The communication unit 1901 may also be referred to as a transceiving unit. Alternatively, communication section 1901 may be divided into a reception section and a transmission section. The processing unit 1902 and the communication unit 1901 are similar, and will not be described in detail below. Wherein:

a communication unit 1901, configured to receive second information from a policy control function network element or a unified data repository or a unified data management function network element; the processing unit 1902 is further configured to, based on the second information, make a first packet data unit, PDU, session in the first network slice or the first network slice not under network slice access control.

In a possible implementation, the second information is used to indicate that the terminal device corresponding to the first PDU session or the first network slice or the first PDU session is associated with a priority service, or the second information is an ARP that is assigned and preempted to the first PDU session, and a value of the second information is the first value. Optionally, the ARP may be carried in the policy information and sent to the session management function network element. For example, the policy information may be a PCC rule corresponding to the first PDU session. Alternatively, the policy information may be PDU session policy information corresponding to the first PDU session. Specifically, the ARP may be an ARP in a PCC rule corresponding to a certain service in the first PDU session, or may be an authorized default ARP of the first PDU session.

In a possible implementation, the communication unit 1901 is further configured to send, based on the second information, third information to an access and mobility management function network element, where the third information is used to indicate that the terminal device associated priority service corresponds to the first PDU session or the first network slice or the first PDU session.

In one possible implementation, the way that the processing unit 1902 makes the first PDU session in the first network slice or the first network slice not under the access control of the network slice is specifically: when the PDU session number of the first network slice reaches the PDU session number threshold corresponding to the first network slice, the first PDU session is not refused to be established; and/or the presence of a gas in the gas,

not indicating to the network slice admission control function network element to increase the PDU session number of the first network slice by one; and/or the presence of a gas in the gas,

indicating to a network slice admission control function network element to reduce the PDU session number of a first network slice by one; and/or the presence of a gas in the atmosphere,

indicating to a network slice admission control function network element to leave the first network slice out of network slice access control.

In a possible implementation, the communication unit 1901 is further configured to receive fifth information from a policy control function network element or a unified data repository or a unified data management function network element, where the fifth information is used to indicate that a terminal device corresponding to a first PDU session or a first network slice or the first PDU session is not associated with a priority service, or the fifth information is a second value and is used to allocate and preempt a priority ARP for the first PDU session; the processing unit 1902 is further configured to subject the first PDU session or the first network slice to network slice access control based on the fifth information.

In one possible implementation, the way that the processing unit 1902 makes the first PDU session or the first network slice under network slice access control is specifically: indicating to a network slice admission control function network element to increase the PDU session number of a first network slice by one; and/or indicating to a network slice admission control function network element to subject the first network slice to network slice access control.

In a possible implementation, the communication unit 1901 is further configured to send, based on the fifth information, sixth information to an access and mobility management function network element, where the sixth information is used to indicate that the first PDU session or the first network slice or a terminal device corresponding to the first PDU session is not associated with priority traffic.

Referring to fig. 19, fig. 19 is a schematic structural diagram of a communication device according to an embodiment of the present application. The communication apparatus shown in fig. 19 may be used to perform part or all of the functions of the session management function network element (e.g., SMF network element) in the method embodiments described in fig. 13 to fig. 14. The device may be a session management function network element, a device in the session management function network element, or a device capable of being used in match with the session management function network element. Wherein, the communication device can also be a chip system. The communication apparatus shown in fig. 19 may include a communication unit 1901 and a processing unit 1902. Wherein:

a processing unit 1902, configured to enable a first PDU session to be free from network slice access control when the first PDU session is established;

the processing unit 1902 is further configured to enable the first PDU session to be subject to network slice access control if the second information is not received within a preset time period after the first PDU session is established; the second information is from a policy control function network element or a unified data storage library or a unified data management function network element, the second information indicates a first PDU session in a first network slice or a terminal device associated priority service corresponding to the first network slice or the first PDU session, or the second information is an allocation and preemption priority ARP corresponding to the first PDU session, and a value of the second information is a first value.

In a possible implementation, the communication unit 1901 is configured to, if the second information is received within a preset time period after the first PDU session is established, send, based on the second information, third information to an access and mobility management function network element, where the third information is used to indicate that the first PDU session or the first network slice or the terminal device corresponding to the first PDU session is associated with a priority service.

In one possible implementation, the way that the processing unit 1902 makes the first PDU session not controlled by the network slice access is specifically: when the PDU session number of the first network slice reaches the PDU session number threshold corresponding to the first network slice, the first PDU session is not refused to be established; and/or not indicating to the network slice admission control function network element to increase the number of PDU sessions of the first network slice by one.

In one possible implementation, the way that the processing unit 1902 makes the first PDU session under network slice access control is specifically: indicating to a network slice admission control function network element to increase by one the number of PDU sessions of the first network slice.

In a possible implementation, the processing unit 1902, if fifth information is received after receiving the second information, is further configured to subject the first PDU session to network slice access control based on the fifth information; the fifth information is from a policy control function network element, a unified data storage library, or a unified data management function network element, and is used to indicate that the terminal device corresponding to the first PDU session, or the first network slice, or the first PDU session, is not associated with a priority service, or the fifth information is an allocation and preemption priority ARP corresponding to the first PDU session, and a value of the fifth information is a second value.

In a possible implementation, the communication unit 1901 is further configured to send, based on the fifth information, sixth information to an access and mobility management function network element, where the sixth information is used to indicate that the terminal device corresponding to the first PDU session or the first network slice or the first PDU session is not associated with the priority service.

Referring to fig. 19, fig. 19 is a schematic structural diagram of a communication device according to an embodiment of the present application. The communication device shown in fig. 19 may be used to perform part or all of the functions of the access and mobility management function network element (e.g., AMF network element) in the method embodiments described in fig. 15-18 above. The device may be an access and mobility management function network element, a device in the access and mobility management function network element, or a device capable of being used in cooperation with the access and mobility management function network element. Wherein, the communication device can also be a chip system. The communication apparatus shown in fig. 19 may include a communication unit 1901 and a processing unit 1902. Wherein:

a communication unit 1901, configured to receive third information from a session management function network element, a unified data repository, or a unified data management function network element, where the third information is used to indicate a first PDU session in a first network slice, or a priority service associated with a first network slice, where the terminal device is a terminal device corresponding to the first PDU session, or the terminal device is a terminal device that requests to register the first network slice; a processing unit 1902, configured to enable the terminal device to be free from access control of the first network slice or to enable the first network slice to be free from access control based on the third information.

In a possible implementation, the processing unit 1902 makes the terminal device not under access control of the first network slice, or makes the first network slice not under access control specifically:

indicating the network slice admission control function network element to reduce the number of the terminal equipment of the first network slice by one; and/or;

when the number of the terminal devices of the first network slice reaches the threshold value of the number of the terminal devices corresponding to the first network slice, not rejecting the first network slice requested by the terminal devices; and/or the presence of a gas in the gas,

not indicating the network slice admission control function network element to increase the number of the terminal equipment of the first network slice by one; and/or the presence of a gas in the gas,

indicating to a network slice admission control function network element that the first network slice is not under network slice access control.

In a possible implementation, the communication unit 1901 is further configured to receive sixth information from a session management function network element or a unified data repository or a unified data management function network element, where the sixth information is used to indicate that the first PDU session or the first network slice or the terminal device is not associated with a priority service; the processing unit 1902 is further configured to enable the terminal device to be under access control of the first network slice or to enable the first network slice to be under access control based on the sixth information.

In a possible implementation, the processing unit 1902 makes the terminal device under access control of the first network slice, or makes the first network slice under access control specifically: indicating the network element with the network slice admission control function to increase the number of the terminal equipment of the first network slice by one; and/or; indicating to a network slice admission control function network element that the first network slice is under network slice access control.

In one possible implementation, the communication unit 1901 may notify the session management function network element that the first network slice is associated with the priority service or that the terminal device may use the priority service. In this way, the session management function network element may enable the terminal device to be in the PDU session of the first network slice or the first network slice is not controlled by the network slice access.

In one possible implementation, the communication unit 1901 may notify the session management function network element that the first network slice is not associated with priority traffic or that the terminal device may not use priority traffic. In this way, the session management function network element may enable the terminal device to be controlled by the network slice access in the PDU session of the first network slice or the first network slice.

In one possible implementation, the third information and the sixth information may be passed with the access and mobility management function network element as context of the terminal device.

Referring to fig. 19, fig. 19 is a schematic structural diagram of a communication device according to an embodiment of the present application. The communication apparatus shown in fig. 19 may be used to perform part or all of the functions of the policy control function network element (e.g., PCF network element) in the embodiments of the methods described in fig. 15 to 18. The device may be a policy control function network element, a device in the policy control function network element, or a device capable of being used in match with the policy control function network element. Wherein, the communication device can also be a chip system. The communication apparatus shown in fig. 19 may include a communication unit 1901 and a processing unit 1902. Wherein:

a communication unit 1901, configured to receive first information from an application function network element or a unified data storage library or a unified data management function network element; a communication unit 1901, further configured to send second information to a session management function network element based on the first information; the first information is used for indicating a first Packet Data Unit (PDU) session in a first network slice or a terminal equipment associated priority service corresponding to the first PDU session; the second information is used for the session management function network element to enable the first packet data unit PDU session in the first network slice or the first network slice not to be controlled by the network slice access.

In a possible implementation, the second information is used to indicate that the terminal device corresponding to the first PDU session or the first network slice or the first PDU session is associated with a priority service, or the second information is an ARP that is assigned and preempted to the first PDU session, and a value of the second information is the first value.

In a possible implementation, the communication unit 1901 is further configured to receive fourth information from an application function network element or a unified data repository or a unified data management function network element; a communication unit 1901, further configured to send fifth information to the session management function network element based on the fourth information; the fourth information is used for indicating that the first PDU session or the first network slice or the terminal equipment corresponding to the first PDU session is not associated with the priority service; and the fifth information is used for the session management function network element to enable the first Packet Data Unit (PDU) session in the first network slice or the first network slice to be under the access control of the network slice.

In a possible implementation, the fifth information is used to indicate that the terminal device corresponding to the first PDU session or the first network slice or the first PDU session is not associated with a priority service, or the fifth information is an ARP that is allocated and preempted to the first PDU session, and a value of the fifth information is a second value.

Fig. 20 is a schematic structural diagram of a communication apparatus. The communication device 2000 may be a policy control function network element, a session management function network element or an access and mobility management function network element in the above method embodiments. The method can also be realized by a chip, a chip system, a processor or the like supporting a policy control function network element, a session management function network element or an access and mobility management function network element. The communication device may be configured to implement the method described in the above method embodiment, and specifically, refer to the description in the above method embodiment.

The communication device 2000 may include one or more processors 2001. The processor 2001 may be a general-purpose processor, a special-purpose processor, or the like. For example, a baseband processor or a central processor. The baseband processor may be configured to process communication protocols and communication data, and the central processor may be configured to control a communication device (e.g., a base station, a baseband chip, a terminal chip, a DU or CU, etc.), execute a software program, and process data of the software program.

Optionally, the communication device 2000 may include one or more memories 2002, on which instructions 2004 may be stored, and the instructions may be executed on the processor 2001, so that the communication device 2000 performs the method described in the above method embodiments. Optionally, the memory 2002 may further store data. The processor 2001 and the memory 2002 may be provided separately or may be integrated together.

Optionally, the communication device 2000 may further include a transceiver 2005 and an antenna 2006. The transceiver 2005 can be referred to as a transceiving unit, a transceiver, or a transceiving circuit, etc., and is used to implement transceiving functions. The transceiver 2005 can include a receiver and a transmitter, and the receiver can be referred to as a receiver or a receiving circuit, etc., for implementing a receiving function; the transmitter may be referred to as a transmitter or a transmission circuit, etc. for implementing the transmission function.

The processor 2001 is configured to perform data processing operations of the policy control function network element, the session management function network element, or the access and mobility management function network element in the foregoing method embodiments. The transceiver 2005 is configured to perform data transceiving operations of a policy control function network element, a session management function network element, or an access and mobility management function network element in the foregoing method embodiments.

In another possible design, a transceiver may be included in processor 2001 for performing receive and transmit functions. The transceiver may be, for example, a transceiver circuit, or an interface circuit. The transmit and receive circuitry, interfaces or interface circuitry used to implement the receive and transmit functions may be separate or integrated. The transceiver circuit, the interface circuit or the interface circuit may be used for reading and writing code/data, or the transceiver circuit, the interface circuit or the interface circuit may be used for transmitting or transferring signals.

In yet another possible design, the processor 2001 may optionally store instructions 2003, and the instructions 2003 run on the processor 2001, may cause the communication apparatus 2000 to perform the method described in the above method embodiment. The instructions 2003 may be solidified in the processor 2001, in which case the processor 2001 may be implemented in hardware.

In yet another possible design, the communication device 2000 may include a circuit, which may implement the functions of transmitting or receiving or communicating in the foregoing method embodiments. The processor and transceiver described in the embodiments of the present application may be implemented on an Integrated Circuit (IC), an analog IC, a Radio Frequency Integrated Circuit (RFIC), a mixed signal IC, an Application Specific Integrated Circuit (ASIC), a Printed Circuit Board (PCB), an electronic device, and the like. The processor and transceiver may also be fabricated using various IC process technologies, such as Complementary Metal Oxide Semiconductor (CMOS), N-type metal oxide semiconductor (NMOS), P-type metal oxide semiconductor (PMOS), bipolar Junction Transistor (BJT), bipolar CMOS (BiCMOS), silicon germanium (SiGe), gallium arsenide (GaAs), and the like.

The communication apparatus described in the above embodiment may be a policy control function network element, a session management function network element, or an access and mobility management function network element, but the scope of the communication apparatus described in the embodiment of the present application is not limited thereto, and the structure of the communication apparatus may not be limited by fig. 20. The communication means may be a stand-alone device or may be part of a larger device. For example, the communication means may be:

(1) A stand-alone integrated circuit IC, or chip, or system-on-chip or subsystem;

(2) A set of one or more ICs, which optionally may also include storage components for storing data, instructions;

(3) An ASIC, such as a modem (MSM);

(4) A module that may be embedded within other devices;

(5) Receivers, terminals, smart terminals, cellular phones, wireless devices, handsets, mobile units, in-vehicle devices, network devices, cloud devices, artificial intelligence devices, and the like;

(6) Others, and so forth.

For the case that the communication device may be a chip or a system of chips, reference may be made to the schematic structure of the chip shown in fig. 21. The chip 2100 shown in fig. 21 includes a processor 2101 and an interface 2102. Optionally, a memory 2103 may also be included. The number of the processors 2101 may be one or more, and the number of the interfaces 2102 may be plural.

In one design, for a case where a chip is used to implement functions of a policy control function network element, a session management function network element, or an access and mobility management function network element in an embodiment of the present application:

the interface 2102 for receiving or outputting a signal;

the processor 2101 is configured to perform data processing operations of a policy control function network element, a session management function network element, or an access and mobility management function network element in the foregoing method embodiments.

It is understood that some optional features in the embodiments of the present application may be implemented independently without depending on other features in some scenarios, such as a currently-based solution, to solve corresponding technical problems and achieve corresponding effects, or may be combined with other features according to requirements in some scenarios. Accordingly, the communication device provided in the embodiments of the present application may also implement these features or functions accordingly, which is not described herein again.

It should be understood that the processor in the embodiments of the present application may be an integrated circuit chip having signal processing capability. In implementation, the steps of the above method embodiments may be performed by integrated logic circuits of hardware in a processor or instructions in the form of software. The processor may be a general purpose processor, a Digital Signal Processor (DSP), an Application Specific Integrated Circuit (ASIC), a Field Programmable Gate Array (FPGA) or other programmable logic device, discrete gate or transistor logic device, or discrete hardware components.

It will be appreciated that the memory in the embodiments of the subject application can be either volatile memory or nonvolatile memory, or can include both volatile and nonvolatile memory. The non-volatile memory may be a read-only memory (ROM), a Programmable ROM (PROM), an Erasable PROM (EPROM), an electrically Erasable EPROM (EEPROM), or a flash memory. Volatile memory can be Random Access Memory (RAM), which acts as external cache memory. By way of example, and not limitation, many forms of RAM are available, such as Static Random Access Memory (SRAM), dynamic random access memory (dynamic RAM, DRAM), synchronous Dynamic Random Access Memory (SDRAM), double data rate SDRAM (DDR SDRAM), enhanced SDRAM (ESDRAM), SLDRAM (synchronous DRAM), and direct rambus RAM (DR RAM). It should be noted that the memory of the systems and methods described herein is intended to comprise, without being limited to, these and any other suitable types of memory.

The application also provides a communication system, which comprises a session management function network element and a policy control function network element; the session management function network element and the policy control function network element are configured to perform the methods described in the embodiments corresponding to fig. 7 to fig. 10.

The application also provides a communication system, which comprises a unified data storage library or a unified data management function network element and a session management function network element; the unified data repository or unified data management function network element, and the session management function network element are configured to perform the methods described in the embodiments corresponding to fig. 11 to fig. 12.

The application also provides a communication system, which comprises a strategy control function network element and an access and mobile management function network element; the policy control function network element and the access and mobility management function network element are configured to perform the methods described in the embodiments corresponding to fig. 15 to fig. 16.

The application also provides a communication system, which comprises a unified data storage library or a unified data management function network element and an access and mobile management function network element; the unified data repository or unified data management function network element, and the access and mobility management function network element are configured to perform the methods described in the embodiments corresponding to fig. 17 to fig. 18.

There is also provided a computer-readable storage medium having stored therein computer-executable instructions for causing a computer to perform the operations of a session management function network element in the method of any one of figures 7-16 when invoked by the computer, or for causing the computer to perform the operations of a policy control function network element in the method of any one of figures 7-10 when invoked by the computer, or for causing the computer to perform the operations of an access and mobility management function network element in the method of any one of figures 15-18 when invoked by the computer.

The present application also provides a computer program product for storing computer software instructions which, when executed by a communication device, implement the operations of a session management function network element in the method of any of fig. 7-16, or the operations of a policy control function network element in the method of any of fig. 7-10, or the operations of an access and mobility management function network element in the method of any of fig. 15-18.

The above embodiments may be implemented in whole or in part by software, hardware, firmware, or any combination thereof. When implemented in software, may be implemented in whole or in part in the form of a computer program product. The computer program product includes one or more computer instructions. When loaded and executed on a computer, cause the processes or functions described in accordance with the embodiments of the application to occur, in whole or in part. The computer may be a general purpose computer, a special purpose computer, a network of computers, or other programmable device. The computer instructions may be stored in a computer readable storage medium or transmitted from one computer readable storage medium to another computer readable storage medium, for example, the computer instructions may be transmitted from one website, computer, server, or data center to another website, computer, server, or data center via wire (e.g., coaxial cable, fiber optic, digital Subscriber Line (DSL)) or wireless (e.g., infrared, wireless, microwave, etc.). The computer-readable storage medium can be any available medium that can be accessed by a computer or a data storage device, such as a server, a data center, etc., that incorporates one or more of the available media. The usable medium may be a magnetic medium (e.g., a floppy disk, a hard disk, a magnetic tape), an optical medium (e.g., a Digital Video Disk (DVD)), or a semiconductor medium (e.g., a Solid State Disk (SSD)), among others.

The above description is only for the specific embodiments of the present application, but the scope of the present application is not limited thereto, and any person skilled in the art can easily conceive of the changes or substitutions within the technical scope of the present application, and shall be covered by the scope of the present application. Therefore, the protection scope of the present application shall be subject to the protection scope of the claims.

Claims

1. A method for network slice access control, the method comprising:

the session management function network element receives second information from the policy control function network element or the unified data storage library or the unified data management function network element;

and the session management function network element enables the first Packet Data Unit (PDU) session in the first network slice or the first network slice not to be subjected to network slice access control based on the second information.

2. The method of claim 1, wherein the second information is used to indicate a terminal device associated priority service corresponding to the first PDU session, or the first network slice, or the first PDU session, or wherein the second information is an allocation and preemption priority, ARP, corresponding to the first PDU session, and wherein a value of the second information is a first value.

3. The method according to claim 1 or 2, characterized in that the method further comprises:

and the session management function network element sends third information to an access and mobility management function network element based on the second information, wherein the third information is used for indicating the first PDU session or the first network slice or the terminal equipment corresponding to the first PDU session to associate with the priority service.

4. The method according to any of claims 1 to 3, wherein the session management function network element leaving a first PDU session in a first network slice or the first network slice free from network slice access control comprises:

the session management function network element does not indicate to a network slice admission control function network element to increase the PDU session number of the first network slice by one; and/or the presence of a gas in the atmosphere,

the session management function network element indicates to a network slice admission control function network element to reduce the number of PDU sessions of the first network slice by one; and/or the presence of a gas in the gas,

the session management function network element indicates to the network slice admission control function network element to leave the first network slice uncontrolled in network slice access.

5. The method according to any of claims 1 to 4, wherein after the session management function network element makes the first PDU session in the first network slice or the first network slice not subject to network slice access control based on the second information, the method further comprises:

the session management function network element receives fifth information from the policy control function network element, the unified data repository, or the unified data management function network element, where the fifth information is used to indicate that the first PDU session, the first network slice, or the terminal device corresponding to the first PDU session is not associated with a priority service, or the fifth information is an ARP that is allocated and preempted to a priority corresponding to the first PDU session, and a value of the fifth information is a second value;

and the session management function network element enables the first PDU session or the first network slice to be subjected to network slice access control based on the fifth information.

6. The method of claim 5, wherein the session management function network element subjecting the first PDU session or the first network slice to network slice access control comprises:

the session management function network element indicates to a network slice admission control function network element to increase the PDU session number of the first network slice by one; and/or the presence of a gas in the gas,

the session management function network element indicates to the network slice admission control function network element to subject the first network slice to network slice access control.

7. The method of claim 6, further comprising:

and the session management function network element sends sixth information to an access and mobility management function network element based on the fifth information, where the sixth information is used to indicate that the terminal device corresponding to the first PDU session or the first network slice or the first PDU session is not associated with a priority service.

8. A method for network slice access control, the method comprising:

when a first PDU session is established, a session management function network element enables the first PDU session not to be controlled by network slice access;

if the session management function network element does not receive the second information within a preset time period after the first PDU session is established, enabling the first PDU session to be controlled by network slice access; the second information is from a policy control function network element, a unified data storage library, or a unified data management function network element, and the second information indicates that the first PDU session in the first network slice, or the terminal device corresponding to the first network slice, or the terminal device associated with the priority service, or the second information is an ARP that is assigned and preempted to the priority corresponding to the first PDU session, and a value of the second information is a first value.

9. The method of claim 8, further comprising:

if the session management function network element receives the second information within a preset time period after the first PDU session is established, the session management function network element sends third information to an access and mobility management function network element based on the second information, where the third information is used to indicate that the first PDU session or the first network slice or the terminal device corresponding to the first PDU session is associated with a priority service.

10. The method according to claim 8 or 9, wherein the session management function network element makes the first PDU session not subject to network slice access control, comprising:

when the PDU session number of the first network slice reaches the PDU session number threshold corresponding to the first network slice, the session management function network element does not refuse to establish the first PDU session; and/or not indicating to a network slice admission control function network element to increase by one the number of PDU sessions of the first network slice.

11. The method according to any of claims 8-10, wherein the session management function network element subjecting the first PDU session to network slice access control comprises:

and the session management function network element indicates to a network slice admission control function network element to increase the PDU session number of the first network slice by one.

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

if the session management function network element receives fifth information after receiving the second information, the session management function network element enables the first PDU session to be controlled by network slice access based on the fifth information; the fifth information is from the policy control function network element, the unified data storage library, or the unified data management function network element, and the fifth information is used to indicate that the terminal device corresponding to the first PDU session, the first network slice, or the first PDU session is not associated with a priority service, or the fifth information is an allocation and preemption priority ARP corresponding to the first PDU session, and a value of the fifth information is a second value.

13. The method of claim 12, further comprising:

and the session management function network element sends sixth information to an access and mobility management function network element based on the fifth information, where the sixth information is used to indicate that the first PDU session or the first network slice or the terminal device corresponding to the first PDU session is not associated with a priority service.

14. A method for network slice access control, the method comprising:

the access and mobility management function network element receives third information from a session management function network element or a unified data storage library or a unified data management function network element, where the third information is used to indicate a first PDU session in a first network slice or a priority service associated with the first network slice or a terminal device, where the terminal device is a terminal device corresponding to the first PDU session or a terminal device requesting to register the first network slice;

and the access and mobility management function network element enables the terminal equipment not to be subjected to access control of the first network slice or enables the first network slice not to be subjected to access control based on the third information.

15. The method of claim 14, wherein the access and mobility management function network element is configured to leave the terminal device access-free from the first network slice or to leave the first network slice access-free, comprising:

the access and mobility management function network element indicates to a network slice admission control function network element to reduce the number of the terminal devices of the first network slice by one; and/or;

when the number of the terminal devices of the first network slice reaches the threshold of the number of the terminal devices corresponding to the first network slice, the access and mobility management functional network element does not reject the first network slice requested by the terminal devices; and/or the presence of a gas in the gas,

the network element with the access and mobility management function does not indicate to a network slice admission control function network element to increase the number of the terminal equipment of the first network slice by one; and/or the presence of a gas in the gas,

the access and mobility management function network element indicates to the network slice admission control function network element that the first network slice is not subject to network slice access control.

16. The method according to claim 14 or 15, characterized in that the method further comprises:

the access and mobility management function network element receives sixth information from the session management function network element or the unified data repository or the unified data management function network element, where the sixth information is used to indicate that the first PDU session or the first network slice or the terminal device is not associated with a priority service;

and the access and mobility management function network element enables the terminal equipment to be under access control of the first network slice or enables the first network slice to be under access control based on the sixth information.

17. The method of claim 16, wherein the access and mobility management function network element subjecting the terminal device to access control for the first network slice or subjecting the first network slice to access control comprises:

the access and mobility management function network element indicates to a network slice admission control function network element to increase the number of the terminal devices of the first network slice by one; and/or;

18. A communications device comprising means for performing the method of any of claims 1 to 7, or comprising means for performing the method of any of claims 8 to 13, or comprising means for performing the method of any of claims 14 to 17.

19. A communications apparatus comprising a processor and a memory, the processor and the memory being coupled, the processor being configured to implement the method of any one of claims 1 to 7, or the processor being configured to implement the method of any one of claims 8 to 13, or the processor being configured to implement the method of any one of claims 14 to 17.

20. A communications device comprising a processor and an interface, the processor and the interface being coupled;

the interface is configured to receive or output a signal, and the processor is configured to execute code instructions to cause the method of any one of claims 1 to 7 to be performed, or to cause the method of any one of claims 8 to 13 to be performed, or to cause the method of any one of claims 14 to 17 to be performed.

21. A computer-readable storage medium, in which a computer program or instructions is stored which, when executed by a communication apparatus, implements a method according to any one of claims 1 to 7, or implements a method according to any one of claims 8 to 13, or implements a method according to any one of claims 14 to 17.