WO2023010994A1

WO2023010994A1 - Network slice access control method and communication apparatus

Info

Publication number: WO2023010994A1
Application number: PCT/CN2022/097451
Authority: WO
Inventors: 孙海洋; 朱方园
Original assignee: 华为技术有限公司
Priority date: 2021-08-06
Filing date: 2022-06-07
Publication date: 2023-02-09
Also published as: CN115915337A

Abstract

Provided in the present application are a network slice access control method and a communication apparatus. The method comprises: a session management function network element receiving second information from a policy control function network element or a unified data repository or a unified data management function network element; and the session management function network element enabling, on the basis of the second information, a first packet data unit (PDU) session in a first network slice or the first network slice not to be subjected to network slice access control. On the basis of the method described in the present application, a session management function network element can enable, in a timely manner and on the basis of second information that is sent by a policy control function network element or a unified data repository or a unified data management function network element, a first PDU session or a first network slice not to be subjected to network slice access control, thereby avoiding the interruption or initiation failure of a priority service.

Description

A network slice access control method and communication device

This application claims the priority of the Chinese patent application with the application number 202110904547.4 and the application name "A Network Slicing Access Control Method and Communication Device" submitted to the China Patent Office on August 6, 2021, the entire contents of which are incorporated by reference in this application.

technical field

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

Background technique

Network slicing is to divide the physical network into multiple independent logical networks according to the requirements of different business applications on the number of users, quality of service (QoS), and bandwidth. 3GPP introduces the network slice admission control function (network slice admission control function, NSACF) to determine whether the number of user equipment (UE) in the network slice has reached the maximum number of UEs supported by the network slice, and to determine whether the network slice Whether the number of packet data unit (PDU) sessions in the network slice reaches the maximum number of PDU sessions supported by the network slice.

When the UE registers in the network slice, depending on the specific mode, the access and mobility management function (AMF) network element can notify the NSACF of the number of UEs in the network slice before or after the registration is accepted. plus one. When the UE de-registers, or receives a de-registration notification from a unified data management (UDM) network element, it notifies the NSACF that the number of UEs in the network slice is reduced by one.

In the first step of the PDU session establishment process of the UE, the session management function (SMF) will notify the NSACF to add one to the number of PDU sessions for the network slice. In the last step of PDU session release, SMF will notify 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 will notify the AMF that the quota has been reached. The AMF will set the S-NSSAI corresponding to the network slice as rejected (rejected) NSSAI, that is, the AMF will subsequently deny the UE access to 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 will notify the SMF that the quota has been reached. SMF will refuse to establish a PDU session in this network slice.

Network slice registration and PDU session establishment related to priority services (such as emergency services, multimedia priority services, or mission-critical services) 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 can be exempted from NSAC, that is, the number of UEs in the network slice is not limited. The UE may receive a priority header from the AMF during PDU session establishment when the registration type of the network slice indicates emergency registration. SMF determines the network slice where the PDU session resides based on the priority header, which can be exempted from NSAC, that is, the number of PDU sessions of the network slice is not limited.

However, if the registration type of the UE in the network slice is not emergency registration or the priority header is not carried when registering/initiating a PDU session (such as performing "called" priority services, using Invocation-related Priority Mechanisms, etc.) , the AMF/SMF has no way of judging that the UE or PDU session is used to deliver priority services, and the priority services may be interrupted or unable to be initiated due to slice access control.

Contents of the invention

Embodiments of the present application provide a network slice access control method and a communication device, which are beneficial to avoid interruption or inability to initiate priority services.

In a first aspect, the present application provides a network slice access control method, the method comprising: a session management function network element receives second information from a policy control function network element or a unified data storage library or a unified data management function network element; Based on the second information, the management function network element makes the first packet data unit PDU session in the first network slice or the first network slice not subject to network slice access control.

Based on the method described in the first aspect, the session management function network element can timely make the first PDU session or the first network Slices are not subject to network slice access control, thereby avoiding interruption or inability to initiate priority services.

In a possible implementation, the second information is used to indicate the first PDU session or the first network slice or the associated priority service of the terminal device corresponding to the first PDU session, or the second information is the allocation corresponding to the first PDU session and For preemptive priority ARP, the value of the second information is the first value. By using ARP to indicate the first PDU session or the first network slice or the terminal device associated priority service corresponding to the first PDU session, there is no need to send additional indication information indicating that the first PDU session or the first network slice or the first PDU session corresponds to The terminal equipment is associated with priority services, which is beneficial to save indication overhead.

Throughout this application, the first PDU session-associated priority service may refer to: the first PDU session is delivering priority services, or the first PDU session currently does not deliver priority services, but will deliver priority services in the future (i.e. the first PDU sessions may pass priority traffic).

Throughout this application, the first network slice associated with priority services may refer to: the first network slice is delivering priority services, or the first network slice is currently not delivering priority services, but will deliver priority services in the future (that is, first The network slice may deliver the priority service), or, the first network slice may use the contracted priority service.

In the full text of this application, the terminal equipment associated with priority services may refer to: the terminal equipment is delivering priority services, or the terminal equipment is currently not delivering priority services, but will deliver priority services in the future (that is, the terminal equipment may deliver priority services ), or the terminal equipment can use the subscribed priority service.

In a possible implementation, 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 first PDU session A terminal device corresponding to a PDU session is associated with priority services. By sending the third information to the network element with the access and mobility management function, after receiving the third information, the network element with the access and mobility management function can promptly prevent the terminal device corresponding to the first PDU session from the third information based on the third information. Access control for a network slice, or make the first network slice exempt from access control.

In a possible implementation, the specific implementation manner in which the session management function network element prevents the first PDU session or the first network slice in the first network slice from access control of the network slice is as follows:

When the number of PDU sessions of the first network slice reaches the threshold of the number of PDU sessions corresponding to the first network slice, the session management function network element does not refuse to establish the first PDU session; and/or,

The session management function network element does not instruct the network slice admission control function network element to add one to the number of PDU sessions of the first network slice; and/or,

The session management function network element instructs the network slice admission control function network element to reduce the number of PDU sessions of the first network slice by one; and/or,

The network element with the session management function indicates to the network element with the network slice admission control function that the first network slice is not subject to 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 subject to network slice access control based on the second information, the session management function network element may also Receive the fifth information from the policy control function network element or the unified data storage library or the unified data management function network element; based on the fifth information, the session management function network element enables the first PDU session or the first network slice to (re) accept the network slice acceptance into control.

Based on this possible implementation, the network element with the session management function can timely enable the first PDU session or the first network slice to be controlled based on the fifth information sent by the network element with the policy control function or the unified data repository or the network element with the unified data management function. Network slice access control.

In a possible implementation, 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 priority services, or the fifth information is the In allocating and preempting priority ARP, the value of the fifth information is the second value.

In a possible implementation, the specific implementation manner in which the session management function network element makes the first PDU session or the first network slice subject to network slice access control is as follows: the session management function network element indicates to the network slice admission control function network element Adding one to the number of PDU sessions of the first network slice; and/or, the session management function network element instructs the network slice admission control function network element to make the first network slice subject to network slice access control.

In a possible implementation, the session management function network element sends sixth information to the 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 is not associated Priority business.

Based on this possible implementation, after the access and mobility management function network element receives the sixth information, it can promptly make the terminal device corresponding to the first PDU session subject to the access control of the first network slice based on the sixth information, or make the The first network slice is subject to access control.

In a second aspect, the present application provides a network slice access control method, the method includes: when establishing a first PDU session, the session management function network element prevents the first PDU session from network slice access control; if the session management If the functional network element does not receive the second information within a preset time period after establishing the first PDU session, the first PDU session is subject to network slice access control; wherein the second information comes from the policy control functional network element or A unified data storage library or a unified data management function network element, the second information indicates the first PDU session in the first network slice or the terminal device associated priority service corresponding to the first network slice or the first PDU session, or, the The second information is the allocation and preemption priority ARP corresponding to the first PDU session, and the value of the second information is the first value.

Based on the method described in the second aspect, when establishing the first PDU session, the network element with the session management function makes the first PDU session not subject to network slice access control by default. There is no need to instruct the network slice admission control function network element to add one to the PDU session number of the first network slice after the first PDU session, and after receiving the second information, instruct the network slice admission control function network element to The number of PDU sessions of the first network slice is reduced by one. It is beneficial to reduce signaling interaction.

In a possible implementation, if the network element with the session management function receives the second information within a preset time period after establishing the first PDU session, the network element with the session management function sends a request to the access and The mobility management function network element sends third information, where the third information is used to indicate the first PDU session or the first network slice or the terminal device corresponding to the first PDU session to associate priority services.

By sending the third information to the network element with the access and mobility management function, after receiving the third information, the network element with the access and mobility management function can promptly prevent the terminal device corresponding to the first PDU session from the third information based on the third information. Access control for a network slice, or make the first network slice exempt from access control.

In a possible implementation, the specific implementation manner in which the session management function network element prevents the first PDU session from access control of the network slice is: when the number of PDU sessions in the first network slice reaches the number of PDU sessions corresponding to the first network slice When the threshold is reached, the session management functional network element does not refuse to establish the first PDU session; and/or does not instruct the network slice admission control functional network element to add one to the number of PDU sessions in the first network slice.

In a possible implementation, the specific implementation manner in which the session management function network element makes the first PDU session subject to network slice access control is as follows: the session management function network element instructs the network slice admission control function network element that the first network slice The number of PDU sessions plus one.

In a 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 subject to network slice access control based on the fifth information; The fifth information comes from the policy control function network element or the unified data storage library or the unified data management function network element, and 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 has no associated priority Alternatively, the fifth information is the allocation and preemption priority ARP corresponding to the first PDU session, and the value of the fifth information is the second value.

Based on this possible implementation, the session management function network element can timely make the first PDU session or the first network slice subject to network slice access control based on the fifth information sent by the policy control function network element.

In a possible implementation, the session management function network element sends sixth information to the access and mobility management function network element based on the fifth information, where the sixth information is used to indicate the first PDU session or the first network slice or the first PDU session The terminal equipment corresponding to a PDU session is not associated with priority services. Based on this possible implementation, after the access and mobility management function network element receives the sixth information, it can promptly make the terminal device corresponding to the first PDU session subject to the access control of the first network slice based on the sixth information, or make the The first network slice is subject to access control.

In a third aspect, the present application provides a network slice access control method, the method comprising: the access and mobility management function network element receives the third Information, the third information is used to indicate the first PDU session in the first network slice or the first network slice or the terminal device associated priority service, the terminal device is the terminal device corresponding to the first PDU session, or the terminal device It is a terminal device requesting to register with the first network slice; based on the third information, the access and mobility management functional network element prevents the terminal device from access control of the first network slice, or prevents the first network slice from being accessed control.

Based on the method described in the third aspect, the network element with the access and mobility management function can timely prevent the terminal device or the first network slice from the network when the first PDU session or the first network slice or the terminal device is associated with priority services Slice access control to avoid interruption or inability to initiate priority services.

In a possible implementation, the network element with the access and mobility management function prevents the terminal device from the access control of the first network slice, or the specific implementation manner of preventing the first network slice from the access control is as follows:

The access and mobility management functional network element instructs the network slice admission control functional network element to reduce the number of terminal devices in the first network slice by one; and/or;

When the number of terminal devices in the first network slice reaches the threshold of the number of 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 device; and/or,

The access and mobility management functional network element does not instruct the network slice admission control functional network element to increase the number of terminal devices in the first network slice by one; and/or,

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

In a 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, and 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 priority services; the access and mobility management function network element, based on the sixth information, makes the terminal device subject to the access control of the first network slice, or makes the first network slice subject to access control .

Based on this possible implementation, when the first PDU session or the first network slice is not associated with priority services, the access and mobility management function network element can make the terminal device subject to the access control of the first network slice in time, or make the first network slice Network slices are subject to access control.

In a possible implementation, the network element with the access and mobility management function makes the terminal device subject to the access control of the first network slice, or the specific implementation manner of making the first network slice subject to the access control is as follows:

The access and mobility management functional network element instructs the network slice admission control functional network element to increase the number of terminal devices in the first network slice by one; and/or;

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

In a fourth aspect, the present application provides a network slice access control method, the method comprising: a network element with a policy control function receives first information from a network element with an application function or a unified data storage library or a network element with a unified data management function; The functional network element sends the second information to the session management functional network element based on the first information; wherein the first information is used to indicate that the first packet data unit PDU session in the first network slice or the first network slice or the first PDU session corresponds to The terminal device is associated with priority services; the second information is used by the session management function network element to make the first packet data unit PDU session in the first network slice or the first network slice not subject to network slice access control.

Based on the method described in the first aspect, when the first PDU session in the first network slice or the first network slice or the terminal device corresponding to the first PDU session is associated with priority services, the session management function network element can use The first PDU session or the first network slice is not subject to network slice access control, so as to avoid interruption or failure to initiate priority services.

In a possible implementation, the second 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, or the second information is the allocation corresponding to the first PDU session With the preemption priority ARP, the value of the second information is the first value. By using ARP to indicate the first PDU session or the first network slice or the terminal device associated priority service corresponding to the first PDU session, there is no need to send additional indication information to indicate the first PDU session or the first network slice associated priority service. It is beneficial to save the instruction 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 also receive the second information from the application function network element or the unified data storage library or the unified data management function network element. Fourth information: the policy control function network element sends fifth information to the session management function network element based on the fourth information; where the fourth information is used to indicate the first PDU session or the first network slice or the terminal device corresponding to the first PDU session The priority service is not associated; the fifth information is used to make the first PDU session or the first network slice subject to network slice access control.

Based on this possible implementation, when the first PDU session in the first network slice or the first network slice or the terminal device corresponding to the first PDU session is not associated with priority services, the session management function network element can timely make the first PDU session A PDU session or a first network slice is subject to network slice access control.

In a possible implementation, 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 priority services, or the fifth information is the In allocating and preempting priority ARP, the value of the fifth information is the second value. By using ARP 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, there is no need to send additional indication information to indicate that the first PDU session or the first network slice is not associated with the priority service , which is beneficial to save instruction overhead.

In a fifth aspect, the present application provides a communication device. The communication device may be a session management function network element, or a device in a session management function network element, or a device that can be matched with a session management function network element. Wherein, the communication device may also be a system on a chip. The communication device may execute the method described in the first aspect or the second aspect. The functions of the communication device may be realized by hardware, or may 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 can be software and/or hardware. For operations and beneficial effects performed by the communication device, reference may be made to the method and beneficial effects described in the first or second aspect above.

In the sixth aspect, the present application provides a communication device, which may be a network element with access and mobility management function, or a device in a network element with access and mobility management function, or a communication device capable of communicating with access and mobility The management function network element matches the device used. Wherein, the communication device may also be a system on a chip. The communication device can execute the method described in the third aspect. The functions of the communication device may be realized by hardware, or may 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 can be software and/or hardware. For the operations and beneficial effects performed by the communication device, refer to the method and beneficial effects described in the third aspect above.

In a seventh aspect, the present application provides a communication device. The communication device may be a network element with a policy control function, or a device in a network element with a policy control function, or a device that can be used in conjunction with a network element with a policy control function. Wherein, the communication device may also be a system on a chip. The communication device can execute the method described in the fourth aspect. The functions of the communication device may be realized by hardware, or may 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 can be software and/or hardware. For operations and beneficial effects performed by the communication device, reference may be made to the method and beneficial effects described in the fourth aspect above.

In an eighth aspect, the present application provides a communication device, the communication device includes a processor, and when the processor calls the computer program in the memory, the method according to any one of the first aspect to the fourth aspect is executed .

In a ninth aspect, the present application provides a communication device, the communication device includes a processor and a memory, and the processor and the memory are coupled; the processor is used to implement the method according to any one of the first aspect to the fourth aspect.

In a tenth aspect, the present application provides a communication device. The communication device includes a processor, a memory, and a transceiver, and the processor and the memory are coupled; the transceiver is used to send and receive data, and the processor is used to implement any of the following aspects in the first to fourth aspects. one method.

In an eleventh aspect, the present application provides a communication device, the communication device includes a processor and an interface, the processor is coupled to the interface; the interface is used to receive or output signals, and the processor is used to execute code instructions, so that the The method of any one of the first aspect to the fourth aspect is performed.

In a twelfth aspect, the present application provides a computer-readable storage medium, where computer programs or instructions are stored in the storage medium. When the computer programs or instructions are executed by a communication device, the first to fourth aspects can be implemented. The method described in any one of the aspects.

In a thirteenth aspect, the present application provides a computer program product including an instruction. When the communication device reads and executes the instruction, the communication device executes the method according to any one of the first aspect to the fourth aspect.

In a fourteenth aspect, the present application provides a communication system, including a communication device for performing the method described in the first aspect or the second aspect above, and a communication device for performing the method described in the fourth aspect above.

In a fifteenth aspect, the present application provides a communication system, including a communication device for performing the method described in the first aspect or the second aspect above, and a communication device for performing the method described in the third aspect above.

Description of drawings

FIG. 1 is a schematic diagram of a 5G non-roaming system architecture based on a service interface provided by an embodiment of the present application;

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

3 is a schematic diagram of a system architecture based on a service interface in a roaming scenario of a local breakout (LBO) provided by an embodiment of the present application;

FIG. 4 is a schematic diagram of a system architecture based on a reference point in an LBO roaming scenario provided by an embodiment of the present application;

FIG. 5 is a schematic diagram of a system architecture based on a service interface in a roaming scenario of a home routed (HR) provided by an embodiment of the present application;

FIG. 6 is a schematic diagram of a system architecture based on a reference point in an HR roaming scenario provided by an embodiment of the present application;

FIG. 7 is a schematic flowchart of a network slice access control method provided in an embodiment of the present application;

FIG. 8 is a schematic flowchart of a network slice access control method provided in an embodiment of the present application;

FIG. 9 is a schematic flowchart of a network slice access control method provided in an embodiment of the present application;

FIG. 10 is a schematic flowchart of a network slice access control method provided in an embodiment of the present application;

FIG. 11 is a schematic flowchart of a network slice access control method provided by an embodiment of the present application;

FIG. 12 is a schematic flowchart of a network slice access control method provided in an embodiment of the present application;

FIG. 13 is a schematic flowchart of a network slice access control method provided by an embodiment of the present application;

FIG. 14 is a schematic flowchart of a network slice access control method provided in an embodiment of the present application;

FIG. 15 is a schematic flowchart of a network slice access control method provided by an embodiment of the present application;

FIG. 16 is a schematic flowchart of a network slice access control method provided by an embodiment of the present application;

FIG. 17 is a schematic flowchart of a network slice access control method provided in an embodiment of the present application;

FIG. 18 is a schematic flowchart of a network slice access control method provided by an embodiment of the present application;

FIG. 19 is a schematic structural diagram of a communication device provided by an embodiment of the present application;

FIG. 20 is a schematic structural diagram of a communication device provided by an embodiment of the present application;

FIG. 21 is a schematic structural diagram of a chip provided by an embodiment of the present application.

Detailed ways

The terms "first" and "second" in the specification, claims and drawings of the present application are used to distinguish different objects, rather than to describe a specific 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, product or device comprising a series of steps or units is not limited to the listed steps or units, but optionally also includes unlisted steps or units, or optionally further includes For other steps or units inherent in these processes, methods, products or apparatuses.

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 present application. The occurrences of this 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 understood explicitly and implicitly by those skilled in the art that the embodiments described herein can be combined with other embodiments.

In this application, "at least one (item)" means one or more, "multiple" means two or more, "at least two (items)" means two or three and three Above, "and/or" is used to describe the corresponding relationship between associated objects, indicating that there can be three kinds of relationships, for example, "A and/or B" can mean: only A exists, only B exists, and A and B exist simultaneously. A case where A and B can be singular or plural. The character "/" generally indicates that the contextual objects are an "or" relationship. "At least one of the following" or similar expressions refer to any combination of these items, including any combination of single or plural items. For example, at least one item (piece) of a, b or c can mean: a, b, c, "a and b", "a and c", "b and c", or "a and b and c ", where a, b, c can be single or multiple.

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

FIG. 1 is a schematic diagram of a 5G non-roaming system architecture based on a service interface provided by an embodiment of the present application.

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

FIG. 3 is a schematic diagram of a system architecture based on a service interface in a local breakout (LBO) roaming scenario provided by an embodiment of the present application.

FIG. 4 is a schematic diagram of a reference point-based system architecture in an LBO roaming scenario provided by an embodiment of the present application.

FIG. 5 is a schematic diagram of a system architecture based on a service interface in a home routed (HR) roaming scenario provided by an embodiment of the present application.

FIG. 6 is a schematic diagram of a reference point-based system architecture in an HR roaming scenario provided by an embodiment of the present application.

The system architecture shown in Figures 1 to 6 is divided into terminal equipment, operator network and data network (data network, DN).

① A terminal device can also be called a user equipment (UE). The terminal device in the embodiment of the present application is a device with a wireless transceiver function, which can communicate with one or more core networks (core network, CN) via an access network device in an access network (AN) . A terminal device may also be called an access terminal, terminal, subscriber unit, subscriber station, mobile station, mobile station, remote station, remote terminal, mobile device, user terminal, wireless network equipment, user agent, or user device, among others. Terminal equipment can be deployed on land, including indoor or outdoor, handheld or vehicle-mounted; it can also be deployed on water (such as ships, etc.); it can also be deployed in the air (such as on aircraft, balloons, and satellites, etc.). The terminal device can be a cellular phone, a cordless phone, a session initiation protocol (SIP) phone, a smart phone, a mobile phone, a wireless local loop (WLL) station , personal digital assistant (PDA), which can be a handheld device with wireless communication function, a computing device or other device connected to a wireless modem, a vehicle device, a wearable device, a drone device or the Internet of Things, the Internet of Vehicles Terminals in the fifth generation mobile communication (fifth generation, 5G) network and any form of terminal in the future network, relay user equipment or terminals in the future evolution of the public land mobile network (PLMN) etc., where the relay user equipment may be, for example, a 5G residential gateway (residential gateway, RG). For example, the terminal device can be a virtual reality (virtual reality, VR) terminal, an augmented reality (augmented reality, AR) terminal, a wireless terminal in industrial control (industrial control), a wireless terminal in self driving (self driving), telemedicine Wireless terminals in remote medical, wireless terminals in smart grid, wireless terminals in transportation safety, wireless terminals in smart city, and smart home wireless terminals, etc. The embodiment of the present application does not limit this.

②The operator network can include network slice selection function (network slice selection function, NSSF), network exposure function (network exposure function, NEF), network storage function (network function repository function, NRF), policy control function (policy control function, PCF), unified data management (unified data management, UDM) network element, application function (application function, AF), network slice and SNPN authentication and authorization function (NSSAAF), authentication server function (authentication server function, AUSF), access Access and mobility management function (access and mobility management function, AMF), session management function (session management function, SMF), service communication proxy (service communication prox, SCP), network slice admission control function (network slice admission control function , NSACF), user plane function (user plane function, UPF), unified data repository (unified data repository, UDR) and (wireless) access network ((radio) access network, (R) AN), etc.

This application mainly involves AF network elements, PCF network elements, SMF network elements, AMF network elements, NSACF network elements, UDM network elements and UDR. The following is a further introduction to these network elements:

AF network element: It mainly supports interaction with the 3GPP core network to provide services, such as influencing data routing decisions, policy control functions, or providing some third-party services to the network side.

PCF network element: mainly supports the provision of a unified policy framework to control network behavior, provides policy rules to the control layer network functions, and is responsible for obtaining user subscription information related to policy decisions.

SMF network element: mainly responsible for session management in the mobile network, such as session establishment, modification, and release. Specific functions include assigning IP addresses to users, selecting UPF that provides message forwarding functions, and so on.

AMF network element: mainly responsible for mobility management in the mobile network, such as user location update, user registration network, user handover, etc.

NSACF network element: supports monitoring and controlling the number of registered users of each network slice. Support monitoring and controlling the number of PDU sessions established by each network slice. Supports event-based network slice status notification and reporting to other NFs.

UDM network element: used to generate authentication credentials, user identification processing (such as storing and managing user permanent identities, etc.), access authorization control and subscription data management, etc.

UDR: includes UDM subscription data, PCF policy data, NEF open structured data and application data (including packet flow description (PFD) for application detection, AF request information of multiple UEs, etc.). UDR can be deployed in each PLMN, and its functions are as follows:

- The UDR accessed by the NEF belongs to the same PLMN where the NEF resides.

- If the UDM supports split architecture, the UDR accessed by the UDM belongs to the same PLMN where the UDM resides.

- The UDR accessed by the PCF belongs to the same PLMN where the PCF resides.

③DN: refers to the service network that provides data transmission services for users, such as IMS (IP multi-media service, IP multimedia service), Internet, etc. The UE accesses the DN through the packet data unit (PDU) session established between the UE and the DN.

The network slicing access control method and communication device provided by this application are described in detail below:

The following embodiments relate to application function network elements, policy control function network elements, session management function network elements, access and mobility management function network elements, network slice admission control function network elements, unified data repository or unified data management function network Yuan. In the following, the application function network element is referred to as the AF network element, the policy control function network element is referred to as the PCF network element, the session management function network element is referred to as the SMF network element, the access and mobility management function network element is referred to as the AMF network element, and the network slice access control function The network element is an NSACF network element, the unified data repository is a UDR, and the unified data management function network element is a UDM as an example. 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 can also be other A network device with application functions, policy control functions, session management functions, access and mobility management functions, network slice admission control functions, data storage functions, and data management functions is not limited in this embodiment of the application. In particular, for example, in the scenario of intercommunication with the evolved packet core network (evolved packet core, EPC), the session management function network element can be SMF+PGW-C (session management function+packet data network gateway for control plane) network The access and mobility management functional network element may be a mobility management entity (mobility management entity, MME) or an AMF network element.

Please refer to FIG. 7 . FIG. 7 is a schematic flowchart of a network slice access control method provided by an embodiment of the present application. As shown in FIG. 7 , the network slice access control method includes the following parts 701-703. in:

701. The AF network element sends first information to the PCF network element. Correspondingly, the PCF network element may receive the first information.

Wherein, the first information is used to indicate that the first PDU session in the first network slice is associated with priority services. The first PDU session is associated with the priority service: the first PDU session is delivering the priority service, or the first PDU session is not currently delivering the priority service, but will deliver the priority service in the future (that is, the first PDU session may deliver the priority service level business).

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

In this embodiment of the present application, 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), or (MPS 5GS) priority indicator (priority indicator), etc.

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

Wherein, the second information is used for the SMF network element to prevent the first PDU session or the first network slice in the first network slice from being controlled by network slice access.

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

In another possible implementation, the second information is the allocation and preemption priority (allocation and retention 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 priority service associated with the first PDU session to the SMF network element through the ARP.

Wherein, the ARP can 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 the ARP in the PCC rule corresponding to a certain service in the first PDU session, or may be the authorized default ARP of the first PDU session.

ARP contains information about priority, preemptability, and preemptability. This allows to decide whether QoS flow establishment/modification/switching is acceptable or needs to be rejected in case of resource constraints (typically used for admission control of GBR traffic). It can also be used to decide which existing QoS flow to preempt during resource constraints, i.e. which QoS flow to release to free up resources. The smaller the value of ARP, the less the QoS flow can be preempted. Therefore, the value of ARP can be set to a smaller value to indicate to the SMF network element the first PDU session association priority service. For example, the value of ARP can be set to 0 or 1. By using ARP to indicate the first PDU session-associated priority service to the SMF network element, there is no need to send additional indication information to indicate the first PDU session-associated priority service, which is beneficial to save indication overhead.

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

703. The SMF network element makes the first PDU session or the first network slice in the first network slice not subject to network slice access control based on the second information.

That is to say, the SMF network element may only make the first PDU session not subject to network slice access control based on the second information. Alternatively, the entire network slice where the first PDU session is located is not subject to access control.

In a possible implementation, the SMF network element executes the NSAC process after obtaining the policy information from the PCF network element (instead of the first step in the PDU session establishment, that is, not after the SMF network element receives the PDU session establishment request from the terminal device execute the NSAC process).

In a possible implementation, the SMF network element prevents the first PDU session or the first network slice in the first network slice from the network slice access control (that is, the SMF network element skips the corresponding NSAC process) It is: the SMF network element instructs the NSACF network element to reduce the number of PDU sessions of the first network slice by one; and/or, the SMF network element instructs the NSACF network element to make the first network slice not subject to network slice access control.

For example, since the first PDU session has been established, the NSACF network element has counted the first PDU session into the number of PDU sessions in the first network slice. Therefore, the specific implementation manner in which the SMF network element prevents the first PDU session from access control of the network slice may be: the SMF network element instructs the NSACF network element to reduce the number of PDU sessions in the first network slice by one. That is, the NSACF network element does not count the first PDU session into the number of PDU sessions of the first network slice.

For another example, the specific implementation manner in which the SMF network element prevents the first network slice from the network slice access control is as follows: the SMF network element instructs the NSACF network element to prevent the first network slice from the network slice access control. That is, 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 subject to network slice access control. The SMF network element does not need to report the change in the number of PDU sessions of the first network slice to the NSACF network element. The other SMF network elements here may be SMF network elements within the service range of all NSACF network elements; they may also be all SMF network elements serving the terminal equipment corresponding to the first PDU session. The service terminal device specifically refers to the PDU session corresponding to the service terminal device. The latter requires the SMF network element to report the UE ID at the same time when reporting the change in the number of PDU sessions to the NSACF network element, so that the NSACF network element knows which SMF network elements serve the sessions of a certain terminal device.

In a possible implementation, the SMF network element may also send third information to the AMF network element based on the second information, where the third information is used to indicate that the first PDU session is associated with a priority service. In this way, after the AMF network element receives the third information, based on the third information, the terminal device corresponding to the first PDU session can be exempted from the access control of the first network slice in a timely manner, or the first network slice can be exempted from the access control. For related operations after the AMF network element receives the third information, refer to the description in the embodiment corresponding to FIG. 15 , which will not be repeated here.

It can be seen that by implementing the method described in Figure 7, when the first PDU session is associated with priority services, the SMF network element can timely prevent the first PDU session or the first network slice in the first network slice from being accessed by the network slice control, thereby avoiding interruption or inability to initiate priority services.

Please refer to FIG. 8 . FIG. 8 is a schematic flowchart of another network slice access control method provided by an embodiment of the present application. As shown in FIG. 8 , the network slice access control method includes the following parts 801-806. in:

801. The AF network element sends first information to the PCF network element. Correspondingly, the PCF network element may receive the first information.

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

803. The SMF network element makes the first PDU session or the first network slice in the first network slice not subject to network slice access control based on the second information.

For related descriptions of steps 801 to 803, reference may be made to the descriptions of steps 701 to 703 in FIG. 7 , and details are not repeated here.

804. The AF network element sends fourth information to the PCF network element. Correspondingly, the PCF network element may receive the fourth information.

In this embodiment of the present application, the fourth information is used to indicate that the first PDU session is not associated with priority services.

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

In this embodiment of the present application, the fifth information is used by the SMF network element to make the first PDU session or the first network slice subject to network slice access control.

In a possible implementation, the fifth information is used to indicate that the first PDU session is not associated with priority services. That is, the PCF network element may explicitly indicate to the SMF network element that the first PDU session is not associated with priority services.

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

Alternatively, the fifth information may also be some other information used by the SMF network element to make the first PDU session or the first network slice subject to network slice access control.

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

That is to say, the SMF network element may only make the first PDU session subject to network slice access control based on the fifth information. Alternatively, the entire network slice where the first PDU session is located is subject to access control. For example, if the SMF network element can make only the first PDU session not subject to network slice access control based on the second information, then the SMF network element can make only the first PDU session subject to network slice access control based on the fifth information. If the SMF network element can make the entire network slice where the first PDU session resides not subject to access control based on the second information, then the SMF network element can make the entire network slice where the first PDU session resides subject to access control based on the fifth information.

In a possible implementation, the SMF network element makes the first PDU session or the first network slice subject to network slice access control (that is, the SMF network element executes the corresponding NSAC process). The element indicates to add one to the number of PDU sessions of the first network slice; and/or, the SMF network element indicates to the NSACF network element that the first network slice is subject to network slice access control.

For example, the specific implementation manner in which the SMF network element makes the first PDU session subject to network slice access control may be: the SMF network element instructs the NSACF network element to add one to the number of PDU sessions in the first network slice. That is, the NSACF network element counts the first PDU session into the number of PDU sessions in the first network slice.

For another example, the specific implementation manner in which the SMF network element makes the first network slice subject to network slice access control is: the SMF network element instructs the NSACF network element to make the first network slice subject 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 subject to network slice access control. The SMF network element may report the change in the number of PDU sessions of the first network slice to the NSACF network element. The other SMF network elements here may be SMF network elements within the service range of all NSACF network elements; they may also be all SMF network elements serving the terminal equipment corresponding to the first PDU session.

In a possible implementation, the SMF network element sends sixth information to the AMF network element based on the fifth information, where the sixth information is used to indicate that the first PDU session is not associated with a priority service. In this way, after the AMF network element receives the sixth information, the terminal device corresponding to the first PDU session can be subject to access control of the first network slice in a timely manner based on the sixth information, or the first network slice can be subject to access control. For related operations after the AMF network element receives the sixth information, refer to the description in the embodiment corresponding to FIG. 16 , which will not be repeated here. The AMF network element can also be other network devices with access and mobility management functions.

By executing the method described in FIG. 8 , the SMF network element can make the first PDU session or the first network slice subject to network slice access control in a timely manner when the first PDU session is not associated with priority services.

Please refer to FIG. 9 . FIG. 9 is a schematic flowchart of another network slice access control method provided by an embodiment of the present application. As shown in FIG. 9 , the network slice access control method includes the following parts 901-903. in:

901. The UDR/UDM network element sends first information to the PCF network element. Correspondingly, 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 a UDR/UDM network element. The application information may be written into the UDR/UDM network element in advance by the AF network element through the network exposure function (network exposure function, NEF) network element.

In a possible implementation, the first information is used to indicate that the first network slice is associated with priority services. In the full text of the embodiments of the present application, the first network slice associated with priority services means: the first network slice is delivering priority services, or the first network slice is currently not delivering priority services, but will deliver priority services in the future (that is, the first network slice A network slice may deliver priority traffic), or, the first network slice may use the subscribed priority traffic.

Optionally, the first information used to indicate the first network slice-associated priority service may specifically be: the first information is used to indicate the first DNN-associated priority service in the first network slice. The first network slice is the network slice where the first PDU session is located. The first DNN is a data network name (data network name, DNN) where the first PDU session is located. In the full text of the embodiments of the present application, the first DNN associated with priority services means: the first DNN is delivering priority services, or the first DNN is not currently delivering priority services, but will deliver priority services in the future (that is, the first DNN may The priority service will be delivered), or the signed priority service can be used in the first DNN.

In another possible implementation, the first information may also indicate that the terminal device/User is associated with a priority service. In the full text of the embodiments of the present application, the associated priority service of the terminal device may refer to: the terminal device is delivering the priority service, or the terminal device is not currently delivering the priority service, but will deliver the priority service in the future (that is, the terminal device may deliver the priority service class service), or the terminal device can use the contracted priority service (Indicates the user is subscribed to MPS). That is, the terminal device/User is the terminal device/User corresponding to the first PDU session. For example, the subscription information includes MPS priority.

In a possible implementation, the UDR/UDM network element may send the first information to the PCF network element during the establishment of the first PDU session. For example, during the establishment process of the first PDU session, the PCF network element will request the UDM network element to obtain the 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, when 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. The PCF network element sends the second information to the SMF network element based on the first information. Correspondingly, the SMF network element may receive the second information.

In a possible implementation, the second information is used to indicate the first network slice where the first PDU session is located or the terminal device corresponding to the first PDU session to associate priority services. That is, the PCF network element may explicitly indicate to the SMF network element the first network slice where the first PDU session is located or the terminal device association priority service corresponding to the first PDU session.

In another possible implementation, the second information is the 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 to the SMF network element the priority service associated with the first network slice through the ARP.

The value of the ARP may be set to a smaller value to indicate to the SMF network element the first network slice associated priority service. For example, the value of ARP can be set to 0 or 1. By using ARP to indicate the first network slice-associated priority service to the SMF network element, there is no need to send additional indication information to indicate the first network slice-associated priority service, which is beneficial to save indication overhead.

903. The SMF network element makes the first PDU session or the first network slice in the first network slice not subject to network slice access control based on the second information.

In a possible implementation, the SMF network element prevents the first PDU session or the first network slice in the first network slice from the network slice access control (that is, the SMF network element skips the corresponding NSAC process) It is: when the number of PDU sessions of the first network slice reaches the threshold of the number of PDU sessions 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 that the second The number of PDU sessions of a network slice is increased by one; and/or, the SMF network element indicates to the NSACF network element that the first network slice is not subject to network slice access control.

For example, the specific implementation manner in which the SMF network element prevents the first PDU session from the access control of the network slice may be: when the number of PDU sessions in the first network slice reaches the 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 in the first network slice, that is, the NSACF network element does not count the first PDU session into the PDU of the first network slice number of sessions.

Optionally, the NSACF network element may further notify other SMF network elements that the PDU session of the first network slice is not subject to network slice access control. The SMF network element does not need to report the change in the number of PDU sessions of the first network slice to the NSACF network element. The other SMF network elements here may be all SMF network elements within the service range of the NSACF network element; they may also be all SMF network elements serving the UE corresponding to the first PDU session.

In a possible implementation, the SMF network element may also 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 a priority service. In this way, after the AMF network element receives the third information, based on the third information, the terminal device corresponding to the first PDU session can be exempted from the access control of the first network slice in a timely manner, or the first network slice can be exempted from the access control. For related operations after the AMF network element receives the third information, refer to the description in the embodiment corresponding to FIG. 15 , which will not be repeated here. The AMF network element can also be other network devices with access and mobility management functions.

It can be seen that by implementing the method described in Figure 9, when the terminal device corresponding to the first network slice or the first PDU session is associated with priority services, the SMF network element can timely make the first PDU session or the first PDU session in the first network slice A network slice is not subject to network slice access control, thereby avoiding the interruption or inability to initiate priority services.

Please refer to FIG. 10 . FIG. 10 is a schematic flowchart of another network slice access control method provided by an embodiment of the present application. As shown in FIG. 10 , the network slice access control method includes the following parts 1001-1006. in:

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

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

1003. The SMF network element makes the first PDU session or the first network slice in the first network slice not subject to network slice access control based on the second information.

Wherein, for specific implementation manners of steps 1001 to 1003, reference may be made to the specific implementation manners of steps 901 to 903 in the embodiment corresponding to FIG. 9 , which will not be repeated here.

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

In this embodiment of the present application, the fourth information is used to indicate that the first network slice is not associated with priority services.

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

In a possible implementation, the fifth information is used to indicate that the first network slice where 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 explicitly indicate to the SMF network element that the first network slice where the first PDU session is located or the terminal device corresponding to the first PDU session is not associated with priority services.

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

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

For a specific implementation manner of step 1006, reference may be made to the specific implementation manner of step 806 in the embodiment corresponding to FIG. 8 , which will not be repeated here.

In a possible implementation, the SMF network element sends sixth information to the AMF network element based on the fifth information, where the sixth information is used to indicate that the first network slice is not associated with the priority service. In this way, after the AMF network element receives the sixth information, the terminal device corresponding to the first PDU session can be subject to access control of the first network slice in a timely manner based on the sixth information, or the first network slice can be subject to access control. For related operations after the AMF network element receives the sixth information, refer to the description in the embodiment corresponding to FIG. 16 , which will not be repeated here. The AMF network element can also be other network devices with access and mobility management functions.

By executing the method described in FIG. 10 , the SMF network element can timely enable the first PDU session or the first network slice to be accepted by the network slice when the terminal device corresponding to the first network slice or the first PDU session is not associated with priority services. into control.

Please refer to FIG. 11 . FIG. 11 is a schematic flowchart of another network slice access control method provided by an embodiment of the present application. As shown in FIG. 11 , the network slice access control method includes the following parts 1101-1102. in:

1101. The UDR/UDM network element sends second information to the SMF network element. Correspondingly, 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 in advance by the AF network element through the network exposure function (network exposure function, NEF) network element.

In a possible implementation, the second information is used to indicate that the first network slice is associated with priority services. That is, the UDR/UDM network element can explicitly indicate to the SMF network element the priority service associated with the first network slice. For the meaning of the priority service associated with the first network slice, refer to the foregoing description, and details are not repeated here.

Optionally, the second information used to indicate the first network slice-associated priority service may specifically be: the second information is used to indicate the first DNN-associated priority service in the first network slice. The first network slice is the network slice where the first PDU session is located. The first DNN is a data network name (data network name, DNN) where the first PDU session is located.

In another possible implementation, the second information may also indicate that the terminal device/User is associated with a priority service. The terminal device/User is the terminal device/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, please refer to the previous description, and details will not be repeated here.

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

Optionally, after the first PDU session is established, the UDM network element/UDR may send the second information to the SMF network element. For example, when 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 makes the first PDU session or the first network slice in the first network slice not subject to network slice access control based on the second information.

In a possible implementation, the SMF network element executes the NSAC process after obtaining the subscription information from the UDM network element/UDR (instead of the first step in the PDU session establishment, that is, not after the SMF network element receives the PDU session of the terminal device Execute the NSAC process when creating a request).

For a specific implementation manner of step 1102, reference may be made to the specific implementation manner of step 903 in the embodiment corresponding to FIG. 9 , which will not be repeated here.

In a possible implementation, the SMF network element may also send third information to the AMF network element based on the second information, where the third information is used to indicate the terminal device association priority corresponding to the first network slice or the first PDU session business. In this way, after the AMF network element receives the third information, based on the third information, the terminal device corresponding to the first PDU session can be exempted from the access control of the first network slice in a timely manner, or the first network slice can be exempted from the access control. For related operations after the AMF network element receives the third information, refer to the description in the embodiment corresponding to FIG. 15 , which will not be repeated here. The AMF network element can also be other network devices with access and mobility management functions.

By executing the method described in Figure 11, when the terminal device corresponding to the first network slice or the first PDU session is not associated with priority services, the SMF network element can timely make the first PDU session or the first PDU session in the first network slice Network slicing is not subject to network slicing access control, thereby avoiding interruption or inability to initiate priority services.

Please refer to FIG. 12 . FIG. 12 is a schematic flowchart of another network slice access control method provided by an embodiment of the present application. As shown in FIG. 12 , the network slice access control method includes the following parts 1201-1204. in:

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

1202. The SMF network element makes the first PDU session or the first network slice in the first network slice not subject to network slice access control based on the second information.

For the specific implementation manners of steps 1201 to 1202, refer to the specific implementation manners of steps 1101 to 1102 in the embodiment corresponding to FIG. 11 , which will not be repeated here.

1203. The UDR/UDM network element sends fifth information to the SMF network element. Correspondingly, 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 can explicitly indicate to the SMF network element that the first network slice is not associated with priority services.

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

For a specific implementation manner of step 1204, reference may be made to the specific implementation manner of step 803 in the embodiment corresponding to FIG. 8 , which will not be repeated here.

In a possible implementation, the SMF network element sends sixth information to the AMF network element 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 priority services . In this way, after the AMF network element receives the sixth information, the terminal device corresponding to the first PDU session can be subject to the access control of the first network slice in a timely manner based on the sixth information, or the first network slice can be subject to access control. For related operations after the AMF network element receives the sixth information, refer to the description in the embodiment corresponding to FIG. 16 , which will not be repeated here. The AMF network element can also be other network devices with access and mobility management functions.

By executing the method described in FIG. 12, the SMF network element can make the first PDU session or the first network slice accept the network slice in a timely manner when the first network slice or the terminal device corresponding to the first PDU session is not associated with priority services. into control.

Please refer to FIG. 13 . FIG. 13 is a schematic flowchart of another network slice access control method provided by an embodiment of the present application. As shown in FIG. 13 , the network slice access control method includes the following parts 1301-1302. in:

1301. When establishing a first PDU session, the SMF network element prevents the first PDU session from network slice access control.

1302. If the SMF network element does not receive the second information within a preset time period after establishing the first PDU session, the SMF network element makes the first PDU session subject to network slice access control.

Wherein, the second information comes from the PCF network element or the UDM network element or the UDR, and the second information is used by the SMF network element to prevent the first PDU session or the first network slice in the first network slice from being controlled by network slice access.

Optionally, the second information indicates the first PDU session in the first network slice or the terminal device associated priority service corresponding to the first network slice or the first PDU session. Alternatively, the second information is the 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 Associate priority business. For related operations of the PCF network element, reference may be made to the descriptions of the embodiments corresponding to FIG. 7 to FIG. 10 , and details are not repeated here. For related operations of the UDM network element or UDR, reference may be made to the descriptions in the embodiments corresponding to FIG. 11 and FIG. 12 , and details are not repeated here. For the meaning of the first PDU session, the first network slice, or the priority service associated with the terminal device, reference may be made to the foregoing description, and details are not repeated here.

In a possible implementation, the SMF network element prevents the first PDU session from the network slice access control (that is, the SMF network element skips the corresponding NSAC process). When the threshold of the number of PDU sessions corresponding to the first network slice is reached, the SMF network element does not refuse to establish the first PDU session; and/or, does not instruct the NSACF network element to add one to the number of PDU sessions of the first network slice, that is, the first PDU Sessions are not counted in the number of PDU sessions for the first network slice.

In a possible implementation, the specific implementation manner in which the SMF network element makes the first PDU session subject to network slice access control (that is, the SMF network element executes the corresponding NSAC process) is as follows: the SMF network element indicates to the NSACF network element that the first The number of PDU sessions in the network slice is increased by one, that is, the first PDU session is included in the number of PDU sessions in 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 the third information to the AMF network element based on the second information, 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 this way, the AMF network element can timely prevent the terminal device from the access control of the first network slice, or prevent the first network slice from the access control. For related operations after the AMF network element receives the third information, refer to the description in the embodiment corresponding to FIG. 15 , which will not be repeated here.

By executing the method described in FIG. 13 , when establishing the first PDU session, the SMF network element makes the first PDU session not subject to network slice access control by default. There is no need to instruct the NSACF network element to increase the number of PDU sessions of the first network slice by one after the first PDU session, and instruct the NSACF network element to decrease the number of PDU sessions of the first network slice by one after receiving the second information . It is beneficial to reduce signaling interaction.

Please refer to FIG. 14 . FIG. 14 is a schematic flowchart of another network slice access control method provided by an embodiment of the present application. As shown in FIG. 14 , the network slice access control method includes the following parts 1401-1403. in:

1401. When establishing a first PDU session, the SMF network element prevents the first PDU session from network slice access control.

1402. If the SMF network element does not receive the second information within a preset time period after establishing the first PDU session, the SMF network element makes the first PDU session subject to network slice access control.

For related descriptions of steps 1401 to 1402, refer to descriptions of steps 1301 to 1302 in FIG. 13 , and details are not repeated here.

1403. If the SMF network element receives fifth information after receiving the second information, the SMF network element makes the first PDU session subject to network slice access control based on the fifth information.

Wherein, the fifth information comes from the PCF network element or the UDM network element or the UDR, and the fifth information is used by the SMF network element to make the first PDU session subject to network slice access control.

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 priority services, or the fifth information is the ARP corresponding to the first PDU session, and the fifth The value of the information is the second value, that is, implicitly indicates to the SMF network element through ARP that the first PDU session or the first network slice or the terminal device corresponding to the first PDU session is not associated with priority services. The second value is different from the first value described above.

In a possible implementation, the SMF network element may also send sixth information to the AMF network element based on the fifth information, where the sixth information is used to indicate the first PDU session or the first network slice or the first PDU session corresponding Terminal equipment is not associated with priority services. In this way, the AMF network element can make the terminal device corresponding to the first PDU session subject to the access control of the first network slice in time, or make the first network slice subject to the access control. For related operations after the AMF network element receives the sixth information, refer to the description in the embodiment corresponding to FIG. 16 , which will not be repeated here.

By executing the method described in FIG. 14 , the SMF network element can make the first PDU session subject to network slice access control in a timely manner when the first PDU session is not associated with priority services.

Please refer to FIG. 15 . FIG. 15 is a schematic flowchart of another network slice access control method provided by an embodiment of the present application. As shown in FIG. 15 , the network slice access control method includes the following parts 1501-1502. in:

1501. The SMF network element sends third information to the AMF network element. Correspondingly, the AMF network element may receive the third information.

Wherein, 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.

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

As described in the embodiments corresponding to Figures 13 to 14, if the SMF network element receives the second information within the preset time period after the establishment of the first PDU session, the SMF network element based on the second information Send the third information to the AMF network element.

1502. Based on the third information, the AMF network element prevents the terminal device corresponding to the first PDU session from the access control of the first network slice, or prevents the first network slice from the access control.

In the embodiment of the present application, the AMF network element may only prevent the terminal device corresponding to the first PDU session from the network slice access control based on the third information. Alternatively, the entire network slice where the first PDU session is located is not subject to access control.

In a possible implementation, the AMF network element prevents the terminal device corresponding to the first PDU session from the access control of the first network slice, or prevents the first network slice from the access control (that is, the AMF network element skips the corresponding The specific implementation of the NSAC process) is: the AMF network element indicates to the NSACF network element that the number of terminal devices in the first network slice should be reduced by one; and/or, when the number of terminal devices in the first network slice reaches the number corresponding to the first network slice When the number of terminal devices exceeds the threshold, the AMF network element does not reject the first network slice requested by the terminal device; and/or, the AMF network element does not indicate to the NSACF network element that the number of terminal devices in the first network slice should be increased by one; and/or, The AMF network element indicates to the NSACF network element that the first network slice is not subject to network slice access control.

For example, the specific implementation manner in which the AMF network element prevents the terminal device corresponding to the first PDU session from the access control of the first network slice is: the AMF network element indicates to the NSACF network element that the number of terminal devices in the first network slice is reduced by one, That is, the NSACF network element does not count the terminal device corresponding to the first PDU session into the number of terminal devices in the first network slice.

For example, in the scenario of interworking with EPC, it is possible (for example, a terminal device with a PDN connection moves from EPC to 5GC) that the PDN connection (corresponding to the PDU session) will be established first, and then the terminal device will register in 5GS (due to moving from EPC By the time of 5GC, SMF+PGC has requested the number of terminal equipment from NSACF to be reduced by 1. At this time, AMF should have applied to NSACF for adding 1 to the number of terminal equipment. When receiving the third information, the AMF network element may skip the NSAC process and not instruct the NSACF network element to add one to the number of terminal devices in the first network slice. In order to avoid affecting the progress of priority services in the first network slice because the NSAC rejects the first network slice of the terminal device. During inter-PLMN handover (inter-PLMN Handover) or cross-NSACF movement, similar operations can also be performed (for example, after the PDU session is first established, switching to a new PLMN or a new NSACF service area may be performed by the new The NSACF performs admission control, that is, the old AMF has requested the NSACF to reduce the number of terminal devices by one, and at this time, the new AMF should apply to the new NSACF for the number of terminal devices 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 process and not instruct the NSACF network element to increase the number of terminal devices in the first network slice by one. In order to avoid affecting the progress of priority services in the first network slice because the NSAC rejects the first network slice of the terminal device.

For example, the specific implementation manner in which the AMF network element makes the first network slice not subject to access control is: the AMF network element indicates to the NSACF network element that the first network slice is not subject to network slice access control. That is, the NSACF network element does not count the number of terminal devices in the first network slice. Optionally, the NSACF network element may further notify other AMF network elements that the terminal devices of the first network slice are not subject to network slice access control. The AMF network element does not need to report the change in the number of terminal devices in the first network slice to the NSACF network element. The other AMF network elements here may be all AMF network elements within the service range of the NSACF network element; they may also be all AMF network elements serving the terminal equipment corresponding to the first PDU session. The service terminal device specifically refers to the PDU session corresponding to the service terminal device. The latter requires the AMF network element to report the terminal device identification when reporting the change in the number of 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 a possible implementation, the third information may be transmitted with the AMF as the context of the terminal device.

By executing the method described in Figure 15, the AMF network element can promptly prevent the terminal device corresponding to the first PDU session or the first network slice from being connected to the network slice when the first PDU session or the first network slice is associated with priority services. Incoming control, so as to avoid interruption or failure to initiate priority services.

Please refer to FIG. 16 . FIG. 16 is a schematic flowchart of another network slice access control method provided by an embodiment of the present application. As shown in FIG. 16 , the network slice access control method includes the following parts 1601-1604. in:

1601. The SMF network element sends third information to the AMF network element. Correspondingly, the AMF network element may receive the third information.

1602. Based on the third information, the AMF network element prevents the terminal device corresponding to the first PDU session from the access control of the first network slice, or prevents the first network slice from the access control.

For related descriptions of steps 1601 to 1602, refer to descriptions of steps 1501 to 1502 in FIG. 15 , and details are not repeated here.

1603. The SMF network element sends 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 embodiment 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. Based on the sixth information, the AMF network element makes the terminal device subject to the access control of the first network slice, or makes the first network slice subject to the access control.

In a possible implementation, the AMF network element makes the terminal device subject to the access control of the first network slice, or makes the first network slice subject to the access control (that is, the AMF network element does not skip the corresponding NSAC process). The method is: the AMF network element indicates to the NSACF network element that the number of terminal devices in 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 subject to network slice access control.

Optionally, the specific implementation manner in which the AMF network element makes the terminal device subject to the access control of the first network slice is: the AMF network element instructs the NSACF network element to add one to the number of terminal devices in the first network slice.

Optionally, a specific implementation manner in which the AMF network element makes the first network slice subject to access control is: the AMF network element indicates to the NSACF network element that the first network slice is subject to network slice access control. Optionally, the NSACF network element may further notify other AMF network elements that the terminal devices of the first network slice are subject to network slice access control. The AMF network element may report the change in the number of terminal devices in the first network slice to the NSACF network element. The other AMF network elements here may be all AMF network elements within the service range of the NSACF network element; they may also be all AMF network elements serving the terminal equipment corresponding to the first PDU session.

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

By executing 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 accepted by the network slice when the first PDU session or the first network slice is not associated with priority services. into control.

Please refer to FIG. 17 . FIG. 17 is a schematic flowchart of another network slice access control method provided by an embodiment of the present application. As shown in FIG. 17 , the network slice access control method includes the following parts 1701-1702. in:

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

Wherein, the third information is used to indicate that the first network slice or the terminal device is associated with priority services. The terminal device is a terminal device that requests to register the first network slice. For the meaning of the first network slice or the priority service associated with the terminal device, refer to the foregoing description, and details are not repeated here.

Wherein, the UDR/UDM network element may send the third information to the AMF network element during the process of the terminal device registering the first network slice.

1702. Based on the third information, the AMF network element exempts the terminal device from the access control of the first network slice, or exempts the first network slice from the access control.

In a possible implementation, the AMF network element prevents the terminal device from the access control of the first network slice, or prevents the first network slice from the access control (that is, the AMF network element skips the corresponding NSAC process). The implementation method is:

When the number of terminal devices in the first network slice reaches the threshold of the number of terminal devices corresponding to the first network slice, the AMF network element does not reject the first network slice requested by the terminal device; and/or, the AMF network element does not indicate to the NSACF network element Adding one to the number of terminal devices in the first network slice; and/or, the AMF network element indicates to the NSACF network element that the first network slice is not subject to network slice access control.

For example, the specific implementation method for the AMF network element to prevent the terminal device from the access control of the first network slice is: when the number of terminal devices in the first network slice reaches the threshold of the number of terminal devices corresponding to the first network slice, the AMF network element does not Rejecting the first network slice requested by the terminal device; and/or, the AMF network element does not instruct the NSACF network element to add one to the number of terminal devices in the first network slice.

For another example, the specific implementation manner in which the AMF network element makes the first network slice not subject to access control is as follows: the AMF network element indicates to the NSACF network element that the first network slice is not subject to network slice access control. Optionally, the NSACF network element may further notify other AMF network elements that the terminal devices of the first network slice are not subject to network slice access control. The AMF network element does not need to report the change in the number of terminal devices in the first network slice to the NSACF network element. The other AMF network elements here may be all AMF network elements within the service range of the NSACF network element; they may also be all AMF network elements serving the UE corresponding to the first PDU session.

In a possible implementation, the AMF network element may notify the SMF network element that the priority service is associated with the first network slice or the terminal device may use the priority service. The SMF network element can make the PDU session of the terminal device in the first network slice or the first network slice not subject to network slice access control.

By executing the method described in FIG. 17, the AMF network element can promptly make the terminal device or the first network slice requesting the first network slice not subject to network slice access control when the first network slice or the terminal device is associated with priority services .

Please refer to FIG. 18 . FIG. 18 is a schematic flowchart of another network slice access control method provided by an embodiment of the present application. As shown in FIG. 18 , the network slice access control method includes the following parts 1801-1804. in:

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

1802. Based on the third information, the AMF network element exempts the terminal device from the access control of the first network slice, or exempts the first network slice from the access control.

For the specific implementation manners of steps 1801 to 1802, refer to the specific implementation manners of steps 1701 to 1702 in the embodiment corresponding to FIG. 17 , and details are not repeated here.

1803. The UDR/UDM network element sends sixth information to the AMF network element. Correspondingly, 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 the priority service. The terminal device is a terminal device that requests to register the first network slice.

1804. Based on the sixth information, the AMF network element makes the terminal device subject to the access control of the first network slice, or makes the first network slice subject to the access control.

For the specific implementation manner of step 1804, reference may be made to the specific implementation manner of step 1604, which will not be repeated here.

In a possible implementation, the AMF network element may notify the SMF network element that the first network slice is not associated with the priority service or the terminal device cannot use the priority service. The SMF network element can make the PDU session of the terminal device in the first network slice or the first network slice subject to network slice access control.

By executing the method described in Figure 18, the AMF network element can promptly make the terminal device or the first network slice requesting the first network slice subject to network slice access control when the first network slice or the terminal device is not associated with priority services .

It can be understood that, in order to implement the functions in the foregoing embodiments, the communication device includes hardware structures and/or software modules corresponding to each function. Those skilled in the art should easily realize that the present application can be implemented in the form of hardware or a combination of hardware and computer software with reference to the units and method steps of the examples described in the embodiments disclosed in the present application. Whether a certain function is executed by hardware or computer software drives the hardware depends on the specific application scenario and design constraints of the technical solution.

Referring to FIG. 19 , FIG. 19 shows 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 execute part or all of the functions of the session management function network element (such as the SMF network element) in the method embodiments described above in FIGS. 7 to 12 . The device may be a network element with a session management function, or a device in a network element with a session management function, or a device that can be matched and used with a network element with a session management function. Wherein, the communication device may also be a system on a chip. The communication device shown in FIG. 19 may include a communication unit 1901 and a processing unit 1902 . Wherein, the processing unit 1902 is configured to perform data processing. The communication unit 1901 is integrated with a receiving unit and a sending unit. The communication unit 1901 may also be called a transceiver unit. Alternatively, the communication unit 1901 may also be split into a receiving unit and a sending unit. The processing unit 1902 and the communication unit 1901 below are the same, and will not be described in detail below. in:

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

In a possible implementation, the second information is used to indicate the first PDU session or the first network slice or the associated priority service of the terminal device corresponding to the first PDU session, or the second information is the allocation corresponding to the first PDU session and For preemptive priority ARP, the value of the second information is the first value. Optionally, the ARP may be carried in the policy information and sent to the network element with the session management function. 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 the ARP in the PCC rule corresponding to a certain service in the first PDU session, or may be the authorized default ARP of the first PDU session.

In a possible implementation, the communication unit 1901 is further configured to send 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 corresponding to the first PDU session is associated with the priority service.

In a possible implementation, the manner in which the processing unit 1902 prevents the first PDU session in the first network slice or the first network slice from the access control of the network slice is specifically: when the number of PDU sessions in the first network slice reaches the When the number of PDU sessions corresponding to a network slice is at a threshold, the establishment of the first PDU session is not rejected; and/or,

Not instructing the network slice admission control function network element to add one to the number of PDU sessions of the first network slice; and/or,

Instructing the network slice admission control function network element to reduce the number of PDU sessions of the first network slice by one; and/or,

Instructing the network element with the network slice admission control function that the first network slice is not subject to network slice access control.

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

In a possible implementation, the manner in which the processing unit 1902 makes the first PDU session or the first network slice subject to the access control of the network slice is: instructing the network element with the network slice admission control function to make the PDU session of the first network slice The number is increased by one; and/or, indicating to the network element with the network slice admission control function that the first network slice is subject to network slice access control.

In a possible implementation, the communication unit 1901 is further configured to send sixth information to the access and mobility management function network element based on the fifth information, where the sixth information is used to indicate 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.

Referring to FIG. 19 , FIG. 19 shows 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 execute part or all of the functions of the session management function network element (such as the SMF network element) in the method embodiments described above in FIGS. 13 to 14 . The device may be a network element with a session management function, or a device in a network element with a session management function, or a device that can be matched and used with a network element with a session management function. Wherein, the communication device may also be a system on a chip. The communication device shown in FIG. 19 may include a communication unit 1901 and a processing unit 1902 . in:

The processing unit 1902 is configured to, when establishing the first PDU session, make the first PDU session not subject to network slice access control;

The processing unit 1902 is further configured to make the first PDU session subject to network slice access control if the second information is not received within a preset period of time after the first PDU session is established; wherein the second information comes from a policy The control function network element or the unified data storage library or the unified data management function network element, the second information indicates the first PDU session in the first network slice or the terminal device association priority corresponding to the first network slice or the first PDU session Alternatively, the second information is the allocation and preemption priority ARP corresponding to the first PDU session, and the value of the second information is the 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 establishment of the first PDU session, send a message to the access and mobility management functional network based on the second information Sending third 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.

In a possible implementation, the manner in which the processing unit 1902 prevents the first PDU session from access control of the network slice is specifically: when the number of PDU sessions of the first network slice reaches the threshold of the number of PDU sessions corresponding to the first network slice, Not refusing to establish the first PDU session; and/or not instructing the network element with the network slice admission control function to add one to the number of PDU sessions in the first network slice.

In a possible implementation, the manner in which the processing unit 1902 makes the first PDU session subject to the access control of the network slice is: instructing the network element with the network slice admission control function to increase the number of PDU sessions of the first network slice by one.

In a possible implementation, the processing unit 1902 is further configured to, if fifth information is received after receiving the second information, make the first PDU session subject to network slice access control based on the fifth information; the fifth information From the policy control function network element or the unified data storage library or the unified data management function network element, 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 priority services , or, the fifth information is the allocation and preemption priority ARP corresponding to the first PDU session, and the value of the fifth information is the second value.

In a possible implementation, the communication unit 1901 is further configured to send sixth information to the access and mobility management functional network element based on the fifth information, where the sixth information is used to indicate 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.

Referring to FIG. 19 , FIG. 19 shows 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 execute part or all of the functions of the access and mobility management function network element (such as the AMF network element) in the method embodiments described above in FIGS. 15 to 18 . The device may be an access and mobility management function network element, or a device in the access and mobility management function network element, or a device that can be matched and used with the access and mobility management function network element. Wherein, the communication device may also be a system on a chip. The communication device shown in FIG. 19 may include a communication unit 1901 and a processing unit 1902 . in:

The communication unit 1901 is configured to receive third information from a network element with a session management function or a unified data repository or a network element with a unified data management function, where the third information is used to indicate the first PDU session in the first network slice or the first network slice Or the terminal device is associated with the priority service, and 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; the processing unit 1902 is configured to, based on the third information, The terminal device is not subject to access control of the first network slice, or the first network slice is not subject to access control.

In a possible implementation, the processing unit 1902 prevents the terminal device from the access control of the first network slice, or the manner in which the first network slice is not subject to the access control is specifically:

Instructing the network slice admission control function network element to reduce the number of terminal devices in the first network slice by one; and/or;

When the number of terminal devices in the first network slice reaches the threshold of the number of terminal devices corresponding to the first network slice, the first network slice requested by the terminal device is not rejected; and/or,

Not instructing the network element of the network slice admission control function to add one to the number of terminal devices in the first network slice; and/or,

Indicating to the network element with the network slice admission control function that the first network slice is not subject to network slice access control.

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

In a possible implementation, the processing unit 1902 makes the terminal device subject to the access control of the first network slice, or the manner of making the first network slice subject to the access control is: instructing the network element with the network slice admission control function to The number of terminal devices in the first network slice is increased by one; and/or; indicating to the network element with the network slice admission control function that the first network slice is subject to network slice access control.

In a possible implementation, the communication unit 1901 may notify the session management function network element that the priority service is associated with the first network slice or that the terminal device can use the priority service. In this way, the network element with the session management function can make the PDU session of the terminal device in the first network slice or the first network slice not subject to network slice access control.

In a possible implementation, the communication unit 1901 may notify the session management function network element that the first network slice is not associated with the priority service or that the terminal device cannot use the priority service. In this way, the network element with the session management function can make the PDU session of the terminal device in the first network slice or the first network slice subject to network slice access control.

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

Referring to FIG. 19 , FIG. 19 shows 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 execute part or all of the functions of the policy control function network element (such as the PCF network element) in the method embodiments described above in FIGS. 15 to 18 . The device may be a network element with a policy control function, or a device in a network element with a policy control function, or a device that can be matched and used with a network element with a policy control function. Wherein, the communication device may also be a system on a chip. The communication device shown in FIG. 19 may include a communication unit 1901 and a processing unit 1902 . in:

The communication unit 1901 is configured to receive the first information from the application function network element or the unified data repository or the unified data management function network element; the communication unit 1901 is further configured to send the second information to the session management function network element based on the first information; Wherein, the first information is used to indicate the first packet data unit PDU session in the first network slice or the first network slice or the terminal device associated priority service corresponding to the first PDU session; the second information is used for the session management function network element The first packet data unit PDU session or the first network slice in the first network slice is not subject to network slice access control.

In a possible implementation, the second 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, or the second information is the allocation corresponding to the first PDU session With the preemption priority ARP, the 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; the communication unit 1901 is further configured to send a session The management function network element sends fifth information; wherein, the fourth 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 priority services; the fifth information is used by the session management function network The element makes the first packet data unit PDU session in the first network slice or the first network slice subject to network slice access control.

FIG. 20 shows a schematic structural diagram of a communication device. The communication device 2000 may be the network element with the policy control function, the network element with the session management function, or the network element with the access and mobility management function in the foregoing method embodiments. It may also be a chip, a chip system, or a processor that supports the policy control function network element, the session management function network element or the access and mobility management function network element to implement the above method. The communication device can be used to implement the methods described in the above method embodiments, and for details, refer to the descriptions in the above method embodiments.

The communication device 2000 may include one or more processors 2001 . The processor 2001 may be a general purpose processor or a special purpose processor or the like. For example, it can be a baseband processor or a central processing unit. The baseband processor can be used to process communication protocols and communication data, and the central processing unit can be used to control communication devices (such as base stations, baseband chips, terminals, terminal chips, DU or CU, etc.), execute software programs, and process Data for Software Programs.

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 executes the above method Methods described in the Examples. Optionally, data may also be stored in the memory 2002 . The processor 2001 and the memory 2002 can be set separately or integrated together.

Optionally, the communication device 2000 may further include a transceiver 2005 and an antenna 2006 . The transceiver 2005 may be called a transceiver unit, a transceiver, or a transceiver circuit, etc., and is used to realize a transceiver function. The transceiver 2005 may include a receiver and a transmitter, and the receiver may be called a receiver or a receiving circuit for realizing a receiving function; the transmitter may be called a transmitter or a sending circuit for realizing a sending function.

The processor 2001 is configured to execute the data processing operation of the network element with the policy control function, the network element with the session management function, or the network element with the access and mobility management function in the foregoing method embodiments. The transceiver 2005 is used to execute the data transceiving operation of the network element with the policy control function, the network element with the session management function or the network element with the access and mobility management function in the above method embodiments.

In another possible design, the processor 2001 may include a transceiver for implementing receiving and sending functions. For example, the transceiver may be a transceiver circuit, or an interface, or an interface circuit. The transceiver circuits, interfaces or interface circuits for realizing the functions of receiving and sending can be separated or integrated together. The above-mentioned transceiver circuit, interface or interface circuit may be used for reading and writing code/data, or the above-mentioned transceiver circuit, interface or interface circuit may be used for signal transmission or transmission.

In yet another possible design, optionally, the processor 2001 may store instructions 2003, and the instructions 2003 run on the processor 2001, and may cause the communication device 2000 to execute the methods described in the foregoing method embodiments. The instruction 2003 may be fixed in the processor 2001, in this case, the processor 2001 may be implemented by hardware.

In yet another possible design, the communication device 2000 may include a circuit, and the circuit may implement the function of sending or receiving or communicating in the foregoing method embodiments. The processor and the transceiver described in the embodiment of the present application can be implemented in integrated circuit (integrated circuit, IC), analog IC, radio frequency integrated circuit RFIC, mixed signal IC, application specific integrated circuit (application specific integrated circuit, ASIC), printed circuit board (printed circuit board, PCB), electronic equipment, etc. The processor and transceiver can also be fabricated using various IC process technologies, such as complementary metal oxide semiconductor (CMOS), nMetal-oxide-semiconductor (NMOS), P-type Metal oxide semiconductor (positive channel metal oxide semiconductor, PMOS), bipolar junction transistor (Bipolar Junction Transistor, BJT), bipolar CMOS (BiCMOS), silicon germanium (SiGe), gallium arsenide (GaAs), etc.

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

(1) Stand-alone integrated circuits ICs, or chips, or chip systems or subsystems;

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

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

(4) Modules that can be embedded in other devices;

(5) Receivers, terminals, smart terminals, cellular phones, wireless devices, handsets, mobile units, vehicle-mounted devices, network devices, cloud devices, artificial intelligence devices, etc.;

(6) Others and so on.

For the case where the communication device may be a chip or a chip system, refer to the schematic structural diagram 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. Wherein, the number of processors 2101 may be one or more, and the number of interfaces 2102 may be more than one.

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

The interface 2102 is used to receive or output signals;

The processor 2101 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 above method embodiments.

It can be understood that, in some scenarios, some optional features in the embodiments of the present application may be implemented independently without depending on other features, such as the current solution on which they are based, to solve corresponding technical problems and achieve corresponding The effect can also be combined with other features according to requirements in some scenarios. Correspondingly, the communication device provided in the embodiment of the present application can also implement these features or functions correspondingly, which will not be repeated here.

It should be understood that the processor in this embodiment of the present application may be an integrated circuit chip that has a signal processing capability. In the implementation process, each step of the above-mentioned method embodiments may be completed by an integrated logic circuit of hardware in a processor or instructions in the form of software. The above-mentioned processor can be a general-purpose processor, a digital signal processor (digital signal processor, DSP), an application specific integrated circuit (application specific integrated circuit, ASIC), a field programmable gate array (field programmable gate array, FPGA) or other possible Program logic devices, discrete gate or transistor logic devices, discrete hardware components.

It can be understood that the memory in the embodiments of the present application may be a volatile memory or a nonvolatile memory, or may include both volatile and nonvolatile memories. Among them, the non-volatile memory can be read-only memory (read-only memory, ROM), programmable read-only memory (programmable ROM, PROM), erasable programmable read-only memory (erasable PROM, EPROM), electrically programmable Erases programmable read-only memory (electrically EPROM, EEPROM) or flash memory. Volatile memory can be random access memory (RAM), which acts as external cache memory. By way of illustration and not limitation, many forms of RAM are available such as static random access memory (static RAM, SRAM), dynamic random access memory (dynamic RAM, DRAM), synchronous dynamic random access memory (synchronous DRAM, SDRAM), double data rate synchronous dynamic random access memory (double data rate SDRAM, DDR SDRAM), enhanced synchronous dynamic random access memory (enhanced SDRAM, ESDRAM), synchronous connection dynamic random access memory (synchlink DRAM, SLDRAM ) and direct memory bus random access memory (direct rambus RAM, DR RAM). It should be noted that the memory of the systems and methods described herein is intended to include, but not be limited to, these and any other suitable types of memory.

The present application also provides a communication system, including 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 used to execute the methods described in the embodiments corresponding to Figures 7 to 10 .

The present application also provides a communication system, including a unified data repository or a network element with a unified data management function, and a network element with a session management function; a unified data repository or a network element with a unified data management function, and a network element with a session management function for Execute the methods described in the embodiments corresponding to FIG. 11 to FIG. 12 .

The present application also provides a communication system, including a policy control function network element and an access and mobility management function network element; the policy control function network element and the access and mobility management function network element are used to perform The method described in the examples.

The application also provides a communication system, including a unified data storage library or a unified data management function network element, and an access and mobility management function network element; a unified data storage library or a unified data management function network element, and an access and mobility management function network element; The management function network element is configured to execute the methods described in the embodiments corresponding to FIG. 17 to FIG. 18 .

The present application also provides a computer-readable medium, where computer-executable instructions are stored in the computer-readable storage medium, and when called by the computer, the computer-executable instructions are used to cause the computer to execute the The operation of the session management function network element in the method described in any one of Fig. 16, or, the computer-executable instruction is used to make the computer execute any one of Fig. 7 to Fig. 10 when called by the computer In the method, the policy controls the operation of the functional network element, or, when the computer-executable instruction is called by the computer, it is used to make the computer execute the method described in any one of Figures 15 to 18. Operation of network elements with entry and mobility management functions.

The present application also provides a computer program product, which is used to store computer software instructions. When the instructions are executed by the communication device, the operation of the session management function network element in the method described in any one of FIGS. 7 to 16 is realized. , or the operation of the policy control functional network element in the method described in any one of FIGS. 7 to 10 , or the operation of the access and mobility management functional network element in the method described in any one of FIGS. 15 to 18 .

In the above embodiments, all or part may be implemented by software, hardware, firmware or any combination thereof. When implemented using software, it may be implemented in whole or in part in the form of a computer program product. The computer program product includes one or more computer instructions. When the computer instructions are loaded and executed on the computer, the processes or functions according to the embodiments of the present application will be generated in whole or in part. The computer can be a general purpose computer, a special purpose computer, a computer network, or other programmable devices. The computer instructions may be stored in or transmitted from one computer-readable storage medium to another computer-readable storage medium, for example, the computer instructions may be transmitted from a website, computer, server or data center Transmission to another website site, computer, server or data center by wired (such as coaxial cable, optical fiber, digital subscriber line (DSL)) or wireless (such as infrared, wireless, microwave, etc.). The computer-readable storage medium may be any available medium that can be accessed by a computer, or a data storage device such as a server or a data center integrated with one or more available media. The available medium may be a magnetic medium (for example, a floppy disk, a hard disk, a magnetic tape), an optical medium (for example, a high-density digital video disc (digital video disc, DVD)), or a semiconductor medium (for example, a solid state disk (solid state disk, SSD)) etc.

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

Claims

A network slice access control method, characterized in that the method comprises:

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

Based on the second information, the session management function network element makes the first packet data unit PDU session in the first network slice or the first network slice not subject to network slice access control.
The method according to claim 1, wherein the second 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, Or the second information is the allocation and preemption priority ARP corresponding to the first PDU session, and the value of the second information is the first value.
The method according to claim 1 or 2, characterized in that the method further comprises:

The session management function network element sends third information to the access and mobility management function network element based on the second information, and the third information is used to indicate 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.
The method according to any one of claims 1-3, wherein the session management function network element prevents the first PDU session in the first network slice or the first network slice from being accessed by the network slice control, including:

When the number of PDU sessions of the first network slice reaches the threshold of the number of PDU sessions corresponding to the first network slice, the session management function network element does not refuse to establish the first PDU session; and/or,

The session management function network element does not instruct the network slice admission control function network element to add one to the number of PDU sessions of the first network slice; and/or,

The session management function network element instructs the network slice admission control function network element to reduce the number of PDU sessions 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 that the first network slice is not subject to network slice access control.
The method according to any one of claims 1-4, wherein the session management function network element makes the first PDU session in the first network slice or the first network After the slice is not controlled by network slice access, the method further includes:

The session management function network element receives fifth information from the policy control function network element or the unified data repository or the unified data management function network element, and the fifth information is used to indicate that the first PDU session Either the first network slice or the terminal device corresponding to the first PDU session is not associated with priority services, or the fifth information is the allocation and preemption priority ARP corresponding to the first PDU session, and the first The value of the fifth message is the second value;

The session management function network element makes the first PDU session or the first network slice subject to network slice access control based on the fifth information.
The method according to claim 5, wherein the session management function network element makes the first PDU session or the first network slice subject to network slice access control, comprising:

The session management function network element instructs the network slice admission control function network element to add one to the number of PDU sessions of the first network slice; and/or,

The session management function network element instructs the network slice admission control function network element to make the first network slice subject to network slice access control.
The method according to claim 6, further comprising:

The session management function network element sends sixth information to the access and mobility management function network element based on the fifth information, and the sixth information is used to indicate the first PDU session or the first network slice or The terminal device corresponding to the first PDU session is not associated with priority services.
A network slice access control method, characterized in that the method comprises:

When establishing the first PDU session, the session management function network element prevents the first PDU session from network slice access control;

If the session management function network element does not receive the second information within a preset time period after establishing the first PDU session, make the first PDU session subject to network slice access control; wherein, The second information comes from a policy control function network element or a unified data storage library or a unified data management function network element, and the second information indicates the first PDU session in the first network slice or the first network slice or the The terminal device association priority service corresponding to the first PDU session, or the second information is the allocation and preemption priority ARP corresponding to the first PDU session, and the value of the second information is the first value.
The method according to claim 8, characterized in that the method further comprises:

If the session management function network element receives the second information within a preset period of time after establishing the first PDU session, the session management function network element sends a message to the connection based on the second information The network element with the ingress and mobility management function sends third 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.
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 number of PDU sessions of the first network slice reaches the threshold of the number of PDU sessions corresponding to the first network slice, the session management function network element does not refuse to establish the first PDU session; and/or does not report to the network The network element with the slice admission control function instructs to add one to the number of PDU sessions of the first network slice.
The method according to any one of claims 8-10, wherein the session management function network element makes the first PDU session subject to network slice access control, including:

The session management functional network element instructs the network slice admission control functional network element to add one to the PDU session quantity of the first network slice.
The method according to any one of claims 8-11, wherein the method further comprises:

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 accessed by a network slice based on the fifth information Control; the fifth information comes from the policy control function network element or the unified data storage library or the unified data management function network element, and the fifth information is used to indicate the first PDU session or the first network slice or The terminal device corresponding to the first PDU session is not associated with priority services, or the fifth information is the allocation and preemption priority ARP corresponding to the first PDU session, and the value of the fifth information is the second value .
The method according to claim 12, characterized in that the method further comprises:

The session management function network element sends sixth information to the access and mobility management function network element based on the fifth information, and the sixth information is used to indicate the first PDU session or the first network slice or The terminal device corresponding to the first PDU session is not associated with priority services.
A network slice access control method, characterized in that the method comprises:

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, and the third information is used to indicate the first PDU session in the first network slice or The first network slice or the terminal device is associated with a priority service, 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;

The access and mobility management functional network element, based on the third information, exempts the terminal device from access control of the first network slice, or exempts the first network slice from access control.
The method according to claim 14, wherein the access and mobility management function network element prevents the terminal device from access control of the first network slice, or prevents the first network slice from Subject to access controls, including:

The access and mobility management functional network element instructs the network slice admission control functional network element to reduce the number of terminal devices in the first network slice by one; and/or;

When the number of terminal devices in the first network slice reaches the threshold of the number of terminal devices corresponding to the first network slice, the network element with the access and mobility management function does not reject the first network requested by the terminal device slices; and/or,

The access and mobility management functional network element does not instruct the network slice admission control functional network element to add one to the number of terminal devices in the first network slice; and/or,

The access and mobility management functional network element indicates to the network slice admission control functional network element that the first network slice is not subject to network slice access control.
The method according to claim 14 or 15, wherein 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, and the sixth information is used to indicate the The first PDU session or the first network slice or the terminal device is not associated with priority services;

The access and mobility management functional network element, based on the sixth information, makes the terminal device subject to access control of the first network slice, or makes the first network slice subject to access control.
The method according to claim 16, wherein the access and mobility management function network element makes the terminal device subject to the access control of the first network slice, or makes the first network slice accept access control, including:

The access and mobility management functional network element instructs the network slice admission control functional network element to add one to the number of terminal devices in the first network slice; and/or;

The access and mobility management functional network element indicates to the network slice admission control functional network element that the first network slice is subject to network slice access control.
A communication device, comprising a module for performing the method according to any one of claims 1 to 7, or comprising a module for performing the method according to any one of claims 8 to 13, or comprising A module for performing the method of any one of claims 14 to 17.
A communication device, characterized in that it includes a processor and a memory, the processor is coupled to the memory, and the processor is used to implement the method according to any one of claims 1 to 7, or the processing The processor is used to implement the method according to any one of claims 8 to 13, or the processor is used to implement the method according to any one of claims 14 to 17.
A communication device, characterized in that it includes a processor and an interface, and the processor is coupled to the interface;

The interface is used to receive or output signals, and the processor is used to execute code instructions, so that the method described in any one of claims 1 to 7 is executed, or to make the method described in any one of claims 8 to 13 The method described in the present invention is carried out, or, or the method described in any one of claims 14 to 17 is carried out.
A computer-readable storage medium, characterized in that computer programs or instructions are stored in the storage medium, and when the computer programs or instructions are executed by a communication device, the implementation of any one of claims 1 to 7 method, or implement the method as described in any one of claims 8 to 13, or realize the method as described in any one of claims 14 to 17.
A computer program product, characterized in that the computer program product comprises: computer program code, when the computer program code is run by a computer, the computer executes the method according to any one of claims 1-7 , or causing the computer to execute the method according to any one of claims 8-13, or causing the computer to execute the method according to any one of claims 14-17.