WO2023015973A1

WO2023015973A1 - Network slice admission control method and apparatus

Info

Publication number: WO2023015973A1
Application number: PCT/CN2022/090973
Authority: WO
Inventors: 朱方园; 施拉姆·米而科; 孙海洋
Original assignee: 华为技术有限公司
Priority date: 2021-08-09
Filing date: 2022-05-05
Publication date: 2023-02-16
Also published as: CN115707062A

Abstract

The present application provides a network slice admission control method and apparatus, the method comprising: a first network element acquires first information from a second network element, wherein the first information is used for associating a first session of a user equipment, the first network element supports controlling the number of users accessing a network slice, the first session is associated with the network slice, and the second network element serves the first session; the first network element receives a first request message from the second network element, the first request message being used for instructing to reduce the number of users who have accessed the network slice; and the first network element determines, according to the first information, whether to reduce the number of users who have accessed the network slice. According to the method, the number of users accessing the network slice and the number of sessions established in the network slice may be controlled, facilitating the admission control of the network slice.

Description

A network slice admission control method and device

This application claims the priority of the Chinese patent application with the application number 202110908693.4 and the application name "A Network Slice Access Control Method and Device" submitted to the State Intellectual Property Office of China on August 9, 2021, the entire contents of which are incorporated by reference incorporated in this application.

technical field

The present application relates to the communication field, and more specifically, to a network slice admission control method and device.

Background technique

With the development of communication technology, hundreds of billions of IoT devices will be connected to the network. Different types of application scenarios have different requirements for the network, and some even conflict with each other. Providing services for different types of application scenarios at the same time through a single network will lead to extremely complex network architecture, low network management efficiency, and low resource utilization efficiency. Network slicing technology provides isolated network environments for different application scenarios by virtualizing independent logical networks on the same network infrastructure, so that different application scenarios can customize network functions and characteristics according to their own needs, and can effectively guarantee the services of different businesses Quality (quality of service, QoS) requirements.

In the actual deployment scenario of network slicing, due to the limitation of network resources, the number of users that can be accommodated in a network slice and the number of sessions allowed to be established are limited. How to control the number of users accessing the network slice and the number of sessions established on the network slice has become an urgent problem to be solved.

Contents of the invention

The present application provides a network slice admission control method and device, capable of controlling the number of users accessing the network slice and the number of sessions established in the network slice, and contributing to the admission control of the network slice.

In a first aspect, the present application provides a network slice admission control method, the method comprising: a first network element acquires first information from a second network element, and the first information is used to associate a first session of a user equipment , the first network element supports the control of the number of users accessing the network slice, the first session is associated with the network slice, and the second network element serves the first session; the first The network element receives a first request message from the second network element, where the first request message is used to indicate to reduce the number of users who have accessed the network slice; the first network element, according to the first information, Determine whether to reduce the number of users who have accessed the network slice.

The first network element supports the control of the number of users accessing the network slice, which can also be described as, the first network element supports the number of UEs counting the number of users accessing the network slice or the first network element has the connection The ability to exercise control over the number of users entering the network slice.

The foregoing first information is used to associate the first session of the user equipment, and may also be described as information related to the first session of the user equipment. As an example, the first information is used to identify the first session, for example, the first information may include at least one of an identifier of the first session or an identifier of the second network element. Wherein, the identifier of the second network element can be the ID (identify) of the second network element, and the identifier of the first session is used to identify the first session, such as a protocol data unit (protocol data unit, PDU) session ID (PDU session ID) .

Optionally, the first network element may be a network slice admission control function (network slice admission control function, NSACF) network element, and the second network element may be a session management function (session management function, SMF) + packet data network (packetdata network, PDN) gateway-control plane (PDN gateway-control plane, PGW-C) network element, that is, SMF+PGW-C.

In a possible implementation manner, after the first network element acquires the first information, it may also store the correspondence between the first information, the network slice, and the user equipment.

In the above technical solution, the second network element will send the session-related information to the first network element, so that the first network element can save the corresponding relationship between the user equipment, the network slice, and the session-related information, and the first network element will receive When an instruction to reduce the number of users accessing the network slice is received, it may be determined according to the corresponding relationship whether the number of users accessing the network slice can be reduced. This enables network slice admission control.

With reference to the first aspect, in a possible implementation manner, the acquiring the first information from the second network element by the first network element includes: requesting the second network element to add users who have accessed the network slice During the process of counting, the first network element acquires the first information.

For example, when the user equipment establishes a PDN connection in the evolved packet core network (evolved packet core, EPC) network, the second network element determines the network slice corresponding to the PDN connection, and then triggers the control of the number of users of the network slice and the number of sessions of the network slice When controlling, the second network element can first interact with the first network element that supports the control of the number of users accessing the network slice, trigger the first network element to increase the number of users accessing the network slice, and communicate with the first network element In the process of element interaction, the first information is sent to the first network element; if the number of users accessing the network slice is not exceeded, it means that the number of users accessing the network slice has not reached the maximum number (such as the first threshold), the network The slice allows new user access, and the second network element interacts with the third network element that supports the control of the number of sessions established on the network slice, triggering the third network element to increase the number of sessions established on the network slice; if the second network element The second network element learns from the third network element that the number of established sessions of the network slice has not exceeded, indicating that the number of established sessions of the network slice has not reached the maximum number (such as the second threshold), then the network slice allows new session establishment, It can also be understood that the second network element learns from the third network element that the session number control is successful, then the second network element may no longer interact with the first network element, and continue to perform other steps in the PDN connection establishment process; The third network element learns that the number of established sessions of the network slice exceeds the limit, indicating that the number of established sessions of the network slice reaches the maximum number (such as the second threshold), then the network slice does not allow new session establishment, which can also be understood as the first The second network element learns from the third network element that the session number control fails, then the second network element can interact with the first network element again, triggering the first network element to control the number of users accessing the network slice, such as triggering the first network element Reduce the number of users accessing the network slice.

In the above technical solution, the first network element obtains the first information when the second network element requests to increase the number of users who have accessed the network slice, so that the second network element obtains the session number control from the third network element When successful, there is no need to interact with the first network element, which helps to reduce signaling overhead.

With reference to the first aspect or any implementation thereof, in another possible implementation, the first network element obtains the first information from the second network element, including: a session established on the network slice When the number of sessions does not exceed the maximum number of sessions allowed by the network slice, the first network element receives a second request message from the second network element, and the second request message includes the first information.

For example, when the user equipment establishes a PDN connection in the EPC network, and the second network element determines the network slice corresponding to the PDN connection, and then triggers the control of the number of users of the network slice and the control of the number of sessions of the network slice, the second network element may first communicate with the Support the interaction of the first network element that controls the number of users accessing the network slice, triggering the first network element to increase the number of users accessing the network slice; if the number of users accessing the network slice is not exceeded, it means If the number of users of the network slice does not reach the maximum number (such as the first threshold), the network slice allows new users to access, and the second network element communicates with the third network element that supports the control of the number of sessions established on the network slice Interaction, triggering the third network element to increase the number of sessions established on the network slice; if the second network element learns from the third network element that the number of established sessions of the network slice is not exceeded, it means that the number of established sessions of the network slice has not reached The maximum number (such as the second threshold), then the network slice allows new session establishment, and it can also be understood that the second network element learns from the third network element that the session number control is successful, then the second network element can send to the first network element A second request message, and carry the first information in the second request message, so that the first network element stores the first information, and continues to execute other steps of the PDN connection establishment process; if the second network element learns the information from the third network element If the number of sessions established in the network slice exceeds the limit, it means that the number of sessions established in the network slice reaches the maximum number (such as the second threshold), and the network slice does not allow new sessions to be established. It can also be understood that the second network element from the third When the network element learns that the control of the number of sessions fails, the second network element can interact with the first network element again, triggering the first network element to control the number of users accessing the network slice, such as triggering the first network element to reduce the number of users accessing the network slice of users.

In the above technical solution, the first network element obtains the first information when the number of established sessions on the network slice does not exceed the maximum number of sessions allowed by the network slice, so that when the second network element obtains the first information from When the third network element learns that the session number control fails, it does not need to instruct the first network element to delete the first information, which can simplify the processing.

With reference to the first aspect or any implementation manner thereof, in another possible implementation manner, the first network element determines whether to reduce the number of users who have accessed the network slice according to the first information, including : If the user equipment has established a session other than the first session on the network slice, the first network element determines to maintain the number of users who have accessed the network slice; if the user equipment is in If only the first session is established on the network slice, the first network element determines to reduce the number of users who have accessed the network slice. In this way, the number of users who have accessed the network slice can be more accurately controlled.

With reference to the first aspect or any implementation thereof, in another possible implementation, the method further includes: after the first network element determines whether to reduce the number of users who have accessed the network slice, The first network element deletes the first information.

With reference to the first aspect or any implementation thereof, in another possible implementation, the first session is a PDN connection established by the user equipment in the EPC network, or it can also be described as, the first session A session is a session corresponding to a PDN connection established by the user equipment in the EPC.

In a second aspect, the present application provides a network slice admission control method, the method includes: a second network element determines the network slice associated with the first session of the user equipment; the second network element sends the first network element to the first network element A piece of information, the first information is used to associate the first session, the first network element supports the control of the number of users accessing the network slice, and the second network element serves the first session ; The second network element sends a first request message to the first network element, where the first request message is used to indicate to reduce the number of users who have accessed the network slice; wherein, the first information is used for Determine whether to reduce the number of users who have accessed the network slice.

Wherein, the second network element serves the first session. The second network element serving the first session can be understood as associating the first session with the second network element when establishing the first session, or establishing the first session through network slice resources supported by the second network element.

The network slice associated with the first session may be understood as the network slice on which the first session is established, or the network slice used to establish the first session.

The first network element supports the control of the number of users accessing the network slice. It can also be described as that the first network element supports counting the number of users accessing the network slice or the first network element has the ability to control the number of users accessing the network slice. Ability to exercise control.

The foregoing first information is used to associate the first session of the user equipment, and may also be described as information related to the first session of the user equipment. As an example, the first information is used to identify the first session, for example, the first information may include at least one of an identifier of the first session or an identifier of the second network element. Wherein, the identifier of the second network element may be the ID of the second network element, and the identifier of the first session is used to identify the first session, such as a PDU session ID.

Optionally, the first network element may be NSACF, and the second network element may be SMF+PGW-C.

In the above technical solution, the second network element will send the session-related information to the first network element, so that the first network element can save the corresponding relationship between the user equipment, the network slice, and the session-related information, so that the first network element can When receiving an instruction to reduce the number of users accessing the network slice, it may be determined whether the number of users accessing the network slice can be reduced according to the corresponding relationship. This enables network slice admission control.

With reference to the second aspect, in a possible implementation manner, the sending the first information by the second network element to the first network element includes: during the process of requesting to increase the number of users who have accessed the network slice, the The second network element sends the first information to the first network element.

For example, when the user equipment establishes a PDN connection in the EPC network, and the second network element determines the network slice corresponding to the PDN connection, and then triggers the control of the number of users of the network slice and the control of the number of sessions of the network slice, the second network element may first communicate with the Support the interaction with the first network element that controls the number of users accessing the network slice, trigger the first network element to increase the number of users accessing the network slice, and report to the first network element during the interaction with the first network element Send the first information; if the number of users accessing the network slice is not exceeded, it means that the number of users accessing the network slice has not reached the maximum number (such as the first threshold), then the network slice allows new users to access, and the second The network element then interacts with a third network element that supports the control of the number of sessions established on the network slice, triggering the third network element to increase the number of sessions established on the network slice; if the second network element learns from the third network element that the The number of established sessions of the network slice is not exceeded, indicating that the number of established sessions of the network slice has not reached the maximum number (such as the second threshold), then the network slice allows new sessions to be established, which can also be understood as the second network element from the first When the three network elements know that the session number control is successful, the second network element may no longer interact with the first network element, and continue to perform other steps in the PDN connection establishment process; if the second network element learns from the third network element that the network slice has been established If the number of sessions exceeds the limit, it means that the number of established sessions of the network slice reaches the maximum number (such as the second threshold), and the network slice does not allow new sessions to be established. It can also be understood that the second network element learns the session from the third network element If the number control fails, the second network element can interact with the first network element again, triggering the first network element to control the number of users accessing the network slice, for example, triggering the first network element to reduce the number of users accessing the network slice.

With reference to the second aspect or any implementation thereof, in another possible implementation, the second network element sends the first information to the first network element, including: a session established on the network slice When the number of sessions does not exceed the maximum number of sessions allowed by the network slice, the second network element sends a second request message to the first network element, where the second request message includes the first information.

With reference to the second aspect or any implementation thereof, in another possible implementation, the method further includes: the second network element obtains from a third network element the number of sessions established on the network slice The maximum number of sessions allowed to be established by the network slice is reached, and the third network element supports performing control on the number of sessions established on the network slice; the second network element sends a first request message to the first network element , including: after the second network element learns that the number of established sessions on the network slice has reached the maximum number of sessions allowed by the network slice, the second network element sends a message to the first network element The first request message.

With reference to the second aspect or any implementation thereof, in another possible implementation, the second network element sending the first request message to the first network element includes: releasing the first session , the second network element sends the first request message to the first network element.

With reference to the second aspect or any implementation thereof, in another possible implementation, the first session is a PDN connection established by the user equipment in the EPC network, or it can also be described as, the first session A session is a session corresponding to a PDN connection established by the user equipment in the EPC.

In a third aspect, the present application provides a network slice admission control method, the method comprising: a second network element determines the network slice associated with the first session of the user equipment; the second network element sends the network storage function network element sending a third request message, where the third request message is used to request information about the fourth network element, where the third request message includes the identifier of the network slice and second information, where the second information is used to indicate the The fourth network element supports the control of the number of users accessing the network slice and the number of sessions established on the network slice; the second network element receives the third A response message, the third response message includes the information of the fourth network element; the second network element sends a fourth request message to the fourth network element, and the fourth request message is used to request the fourth network element The four network elements control the number of users accessed by the network slice, and control the number of sessions established by the network slice.

In the above technical solution, the second network element requests the network storage function network element to select a fourth network element that simultaneously supports the control of the number of users accessing the network slice and the control of the number of sessions established on the network slice, When determining the number of users and sessions corresponding to the network slice, the fourth network element can determine whether the user equipment has already accessed the network slice or whether the sessions of the user equipment should be released, so as to accurately control the access network slice Number of users and sessions established on the network slice. This enables network slice admission control.

With reference to the third aspect, in a possible implementation manner, the fourth request message includes an identifier of the user equipment, first information, third information, fourth information, and an identifier of the network slice, and the first The information is used to associate the first session, wherein: when the user equipment requests to establish the first session, the third information is used to indicate to increase the number of users who have accessed the network slice, and the fourth The information is used to indicate to increase the number of sessions established in the network slice; when the user equipment requests to release the first session, the third information is used to indicate to reduce the number of users who have accessed the network slice, The fourth information is used to indicate to reduce the number of established sessions in the network slice.

With reference to the third aspect or any implementation manner thereof, in another possible implementation manner, the first information includes at least one of an identifier of the second network element or an identifier of the session with the first network element .

With reference to the third aspect or any implementation manner thereof, in another possible implementation manner, the first session is a PDN connection established by the user equipment in the EPC network, or it can also be described as, the first session A session is a session corresponding to a PDN connection established by the user equipment in the EPC.

In a fourth aspect, the present application provides a network slice admission control method, the method includes: a network storage function network element receives a third request message from a second network element, and the third request message is used to request the fourth Network element information, the third request message includes the identifier of the network slice and second information, the second information is used to indicate that the fourth network element supports the control of the number of users accessing the network slice , and support the execution of control on the number of sessions established on the network slice; the network storage function network element sends a third response message to the second network element, and the third response message includes the fourth network element information.

In a fifth aspect, the present application provides a network slice admission control method, the method comprising: a fourth network element receives a fourth request message from a second network element, and the fourth network element supports access network slice performing control on the number of users and supporting the control on the number of sessions established on the network slice, the second network element serves the first session of the user equipment, and the first session is associated with the network slice; the second network element The four network elements perform control on the number of users who have accessed the network slice and the number of sessions established in the network slice according to the fourth request message; the fourth network element sends a message to the second network element A fourth response message, where the fourth response message is used to indicate a result of controlling the number of users who have accessed the network slice and a result of controlling the number of sessions established in the network slice.

With reference to the fifth aspect, in a possible implementation manner, the fourth request message includes an identifier of the user equipment, first information, third information, fourth information, and an identifier of the network slice, and the first The information is used to associate the first session, wherein: when the user equipment requests to establish the first session, the third information is used to indicate to increase the number of users who have accessed the network slice, and the fourth The information is used to indicate to increase the number of sessions established in the network slice; when the user equipment requests to release the first session, the third information is used to indicate to reduce the number of users who have accessed the network slice, The fourth information is used to indicate to reduce the number of established sessions in the network slice.

In a sixth aspect, the present application provides a communication device, and the device includes:

a transceiver unit, configured to obtain first information from a second network element, the first information is used to associate a first session of a user equipment, and the first network element supports performing control on the number of users accessing network slices, the A first session is associated with the network slice, and the second network element serves the first session; receiving a first request message from the second network element, where the first request message is used to indicate that the reduction has been made the number of users accessing the network slice;

A processing unit, configured to determine whether to reduce the number of users who have accessed the network slice according to the first information.

In a possible implementation manner, after acquiring the first information, the apparatus may further save the correspondence between the first information, the network slice, and the user equipment.

With reference to the sixth aspect, in a possible implementation manner, the transceiving unit is specifically configured to: acquire the first information.

With reference to the sixth aspect or any implementation thereof, in another possible implementation, the transceiver unit is specifically configured to: the number of established sessions on the network slice does not exceed the number of sessions allowed to be established by the network slice In the case of the maximum number of sessions, receive a second request message from the second network element, where the second request message includes the first information.

With reference to the sixth aspect or any implementation manner thereof, in another possible implementation manner, the processing unit is specifically configured to: if the user equipment establishes a session other than the first session on the network slice session, then determine to maintain the number of users who have accessed the network slice; if the user equipment has only established the first session on the network slice, determine to reduce the number of users who have accessed the network slice .

With reference to the sixth aspect or any implementation thereof, in another possible implementation, the processing unit is further configured to: after determining whether to reduce the number of users who have accessed the network slice, delete the first a message.

With reference to the sixth aspect or any implementation manner thereof, in another possible implementation manner, the first session is a PDN connection established by the user equipment in the EPC network.

In a seventh aspect, the present application provides a communication device, and the device includes:

a processing unit, configured to determine a network slice associated with the first session of the user equipment;

A transceiver unit, configured to send first information to a first network element, where the first information is used to associate the first session, and where the first network element supports controlling the number of users accessing the network slice, so The second network element serves the first session; and sends a first request message to the first network element, where the first request message is used to indicate to reduce the number of users who have accessed the network slice; wherein, The first information is used to determine whether to reduce the number of users who have accessed the network slice.

With reference to the seventh aspect, in a possible implementation manner, the transceiver unit is specifically configured to: send the first network element to the first network element during a process of requesting to increase the number of users who have accessed the network slice. a message.

With reference to the seventh aspect or any implementation thereof, in another possible implementation, the transceiver unit is specifically configured to: the number of established sessions on the network slice does not exceed the number of sessions allowed to be established by the network slice When the maximum number of sessions is reached, send a second request message to the first network element, where the second request message includes the first information.

With reference to the seventh aspect or any implementation manner thereof, in another possible implementation manner, the transceiver unit is specifically configured to: learn from a third network element that the number of established sessions on the network slice reaches the network The maximum number of sessions allowed to be established by the slice, the third network element supports the control of the number of sessions established on the network slice; the second network element learns that the number of sessions established on the network slice reaches the network After slicing the maximum number of sessions allowed to be established, the first request message is sent to the first network element.

With reference to the seventh aspect or any implementation thereof, in another possible implementation, the transceiver unit is specifically configured to: send the second network element to the first session when releasing the first session. The network element sends the first request message.

With reference to the seventh aspect or any implementation manner thereof, in another possible implementation manner, the first session is a PDN connection established by the user equipment in the EPC network.

In an eighth aspect, the present application provides a communication device, the device comprising:

A transceiver unit, configured to send a third request message to a network storage function network element, where the third request message is used to request information of a fourth network element, where the third request message includes the identifier of the network slice and second information The second information is used to indicate that the fourth network element supports controlling the number of users accessing the network slice and supporting controlling the number of sessions established on the network slice; receiving the network storage function A third response message from a network element, where the third response message includes information about the fourth network element; and sending a fourth request message to the fourth network element, where the fourth request message is used to request the fourth network element The four network elements control the number of users accessed by the network slice, and control the number of sessions established by the network slice.

With reference to the eighth aspect, in a possible implementation manner, the fourth request message includes an identifier of the user equipment, first information, third information, fourth information, and an identifier of the network slice, and the first The information is used to associate the first session, wherein: when the user equipment requests to establish the first session, the third information is used to indicate to increase the number of users who have accessed the network slice, and the fourth The information is used to indicate to increase the number of sessions established in the network slice; when the user equipment requests to release the first session, the third information is used to indicate to reduce the number of users who have accessed the network slice, The fourth information is used to indicate to reduce the number of established sessions in the network slice.

With reference to the eighth aspect or any implementation manner thereof, in another possible implementation manner, the first information includes at least one of an identifier of the second network element or an identifier of the session with the first network element .

With reference to the eighth aspect or any implementation manner thereof, in another possible implementation manner, the first session is a PDN connection established by the user equipment in the EPC network.

In a ninth aspect, the present application provides a communication device, the device comprising:

A transceiver unit, configured to receive a third request message from a second network element, where the third request message is used to request information of a fourth network element, where the third request message includes an identifier of the network slice and second information , the second information is used to indicate that the fourth network element supports controlling the number of users accessing the network slice, and supports controlling the number of sessions established on the network slice; The network element sends a third response message, where the third response message includes the information of the fourth network element.

In a tenth aspect, the present application provides a communication device, and the device includes:

a transceiver unit, configured to receive a fourth request message from a second network element, where the fourth network element supports performing control on the number of users accessing the network slice, and supports performing control on the number of sessions established on the network slice, a second network element serving a first session of a user equipment, the first session being associated with the network slice;

A processing unit, configured to control the number of users who have accessed the network slice and the number of sessions established in the network slice according to the fourth request message;

The transceiver unit is further configured to send a fourth response message to the second network element, where the fourth response message is used to indicate the result of controlling the number of users who have accessed the network slice and to control the number of users in the network slice. The result of the execution control of the number of sessions that the network slice has established.

With reference to the tenth aspect, in a possible implementation manner, the fourth request message includes an identifier of the user equipment, first information, third information, fourth information, and an identifier of the network slice, and the first The information is used to associate the first session, wherein: when the user equipment requests to establish the first session, the third information is used to indicate to increase the number of users who have accessed the network slice, and the fourth The information is used to indicate to increase the number of sessions established in the network slice; when the user equipment requests to release the first session, the third information is used to indicate to reduce the number of users who have accessed the network slice, The fourth information is used to indicate to reduce the number of established sessions in the network slice.

The sixth to tenth aspects are device embodiments corresponding to the first to fifth aspects, which can implement the methods described in the first to fifth aspects and achieve the benefits described in the first to fifth aspects For the effect, specific descriptions may refer to the first aspect to the fifth aspect, which will not be repeated here.

In an eleventh aspect, the present application provides a communication device, including a processor. The processor is coupled with the memory, and can be used to execute instructions in the memory, so that the device executes the method provided in any one of the first to fifth aspects above, or executes any possible method in the first to fifth aspects. method in the implementation. Optionally, the device further includes a memory. Optionally, the device further includes an interface circuit, and the processor is coupled to the interface circuit.

In a twelfth aspect, the present application provides a processor, including: an input circuit, an output circuit, and a processing circuit. The processing circuit is configured to receive a signal through the input circuit and transmit a signal through the output circuit, so that the processor executes the method provided in any one of the first aspect to the fifth aspect, or executes the method in the first aspect to the fifth aspect A method in any of the possible implementations.

In a specific implementation process, the above-mentioned processor can be a chip, the input circuit can be an input pin, the output circuit can be an output pin, and the processing circuit can be a transistor, a gate circuit, a flip-flop and various logic circuits. The input signal received by the input circuit may be received and input by, for example but not limited to, the receiver, the output signal of the output circuit may be, for example but not limited to, output to the transmitter and transmitted by the transmitter, and the input circuit and the output The circuit may be the same circuit, which is used as an input circuit and an output circuit respectively at different times. The embodiment of the present application does not limit the specific implementation manners of the processor and various circuits.

In a thirteenth aspect, the present application provides a processing device, including a processor and a memory. The processor is used to read instructions stored in the memory, and can receive signals through the receiver and transmit signals through the transmitter, so as to execute the method provided in any one of the first to fifth aspects, or to execute the first to the second aspects The method in any one of the possible implementation manners in the five aspects.

Optionally, there are one or more processors, and one or more memories.

Optionally, the memory can be integrated with the processor, or the memory can be set separately from the processor.

In the specific implementation process, the memory can be a non-transitory (non-transitory) memory, such as a read-only memory (read only memory, ROM), which can be integrated with the processor on the same chip, or can be respectively arranged in different On the chip, the embodiment of the present application does not limit the type of the memory and the configuration of the memory and the processor.

The processing device in the above-mentioned thirteenth aspect may be a chip, and the processor may be implemented by hardware or by software. When implemented by hardware, the processor may be a logic circuit or an integrated circuit; when implemented by software When implemented, the processor may be a general-purpose processor, which is realized by reading the software code stored in the memory, and the memory may be integrated in the processor, or it may be located outside the processor and exist independently.

In a fourteenth aspect, the present application provides a computer program product, the computer program product including: a computer program (also referred to as code, or instruction), when the computer program is executed, the computer executes the above-mentioned first aspect to The method provided in any one of the fifth aspects, or the method in any possible implementation manner of the first aspect to the fifth aspect.

In a fifteenth aspect, the present application provides a computer-readable medium, the computer-readable medium stores a computer program (also referred to as code, or instruction) when it is run on a computer, so that the computer executes the above-mentioned first aspect The method provided in any one of the fifth aspects, or the method in any possible implementation manner of the first aspect to the fifth aspect.

In a sixteenth aspect, the present application provides a communication system, including at least one of the devices provided in any of the foregoing aspects or possible implementations thereof.

Description of drawings

Fig. 1 is a schematic architecture diagram of a communication system to which the present application can be applied.

Fig. 2 is another schematic architecture diagram of a communication system to which the present application can be applied.

Fig. 3 is another schematic architecture diagram of a communication system to which the present application can be applied.

Fig. 4 is a schematic flowchart of a network slice admission control method provided by the present application.

Fig. 5 is a schematic flowchart of another network slice admission control method provided by the present application.

FIG. 6 is an example of a network slice admission control method provided by this application.

Fig. 7 is another example of the network slice admission control method provided by this application.

Fig. 8 is another example of the network slice admission control method provided by this application.

Fig. 9 is another example of the network slice admission control method provided by the present application.

Fig. 10 is another example of the network slice admission control method provided by this application.

Fig. 11 is a schematic structural diagram of a device provided by an embodiment of the present application.

Fig. 12 is another schematic structural diagram of the device provided by the embodiment of the present application.

Detailed ways

The technical solution in this application will be described below with reference to the accompanying drawings.

The technical solution of the embodiment of the present application can be applied to various communication systems, for example: long term evolution (long term evolution, LTE) system, LTE frequency division duplex (frequency division duplex, FDD) system, LTE time division duplex (time division duplex) , TDD), Universal Mobile Telecommunications System (UMTS), Worldwide Interoperability for Microwave Access (WiMAX) Communication System, Fifth Generation (5th Generation, 5G) Communication System, New Wireless (new radio, NR) communication system or satellite communication system. Wherein, the communication system may include non-standalone networking (non-standalone, NSA) and/or standalone networking (standalone, SA).

The technical solution provided by this application can also be applied to machine type communication (machine type communication, MTC), inter-machine communication long-term evolution technology (Long Term Evolution-machine, LTE-M), device-to-device (device-to-device, D2D) A network, a machine to machine (M2M) network, an Internet of things (IoT) network, or other networks. Wherein, the IoT network may include, for example, the Internet of Vehicles.

The technical solutions provided in this application can also be applied to future mobile communication systems, such as the sixth generation mobile communication system, which is not limited in this application.

The communication system to which the present application can be applied is described below by taking FIG. 1 to FIG. 3 as examples.

Fig. 1 is a schematic architecture diagram of a communication system to which the present application can be applied. Figure 1 is a schematic diagram of a 5G network architecture based on a service-based architecture. The 5G network architecture shown in FIG. 1 may include three parts, namely a user equipment (user equipment, UE) part, a data network (data network, DN) part, and an operator network part. Wherein, the operator network may include one or more of the following network elements: (wireless) access network ((radio) access network, (R)AN), user plane function (user plane function, UPF) network element, authentication Server function (authentication server function, AUSF) network element, NSACF network element, access and mobility management function (access and mobility management function, AMF) network element, SMF network element, network slice selection function (network slice selection function, NSSF) ) network element, network exposure function (network exposure function, NEF) network element, network repository function (network repository function, NRF) network element, policy control function module (policy control function, PCF) network element, unified data management (unified data management (UDM) network element and application function (application function, AF) network element. In the above operator network, the part other than the RAN part may be referred to as the core network part. The user equipment, wireless access network, UPF network element, AUSF network element, AMF network element, SMF network element, NEF network element, NRF network element, PCF network element, UDM network element, NSSF network element, NSACF network element, The AF network elements are referred to as UE, RAN, UPF, DN, AUSF, AMF, SMF, NEF, NRF, PCF, UDM, NSSF, NSACF, and AF respectively.

In this network architecture, Nnssf is the service-based interface presented by NSSF, Nnef is the service-based interface presented by NEF, Nnrf is the service-based interface presented by NRF, Npcf is the service-based interface presented by PCF, and Nudm is the service-based interface presented by UDM Naf is the service-based interface presented by AF, Nausf is the service-based interface presented by AUSF, Namf is the service-based interface presented by AMF, Nsmf is the service-based interface presented by SMF, Nnsacf is the service-based interface presented by NSACF service-based interface. N1 is the interface between UE and AMF, N2 is the interface between RAN and AMF, used to send NAS messages; N3 is the interface between RAN and UPF, used to transmit user plane data; N4 is between SMF and UPF The interface is used to transmit tunnel identification information such as N3 connection, data cache indication information, and downlink data notification message; N6 interface is the interface between UPF and DN, used to transmit user plane data; N9 is between UPF and UPF interface between.

The network elements involved in FIG. 1 are briefly described below.

1. UE

The UE mainly accesses the 5G network through the wireless air interface and obtains services. The UE interacts with the RAN through the air interface, and interacts with the AMF of the core network through non-access stratum signaling (non-access stratum, NAS).

The UE in this embodiment of the present application may also be referred to as a terminal device, user, access terminal, subscriber unit, subscriber station, mobile station, mobile station, remote station, remote terminal, mobile device, user terminal, terminal, wireless communication device, User Agent or User Device. A UE can be a cellular phone, a smart watch, a wireless data card, a mobile phone, a tablet computer, a personal digital assistant (PDA) computer, a wireless modem, a handheld device, a laptop computer, a machine type communication (MTC) ) terminals, computers with wireless transceiver functions, Internet of Things terminals, virtual reality terminal devices, augmented reality terminal devices, wearable devices, vehicles, terminals in device-to-device (D2D) communication, vehicles ( Terminals in vehicle to everything (V2X) communication, terminals in machine-type communication (MTC), terminals in Internet of Things (IOT), terminals in smart office, terminals in industrial control , terminals in unmanned driving, terminals in remote surgery, terminals in smart grids, terminals in transportation security, terminals in smart cities, terminals in smart homes, terminals in satellite communications (for example, satellite phones or satellite terminal). The UE may also be customer-premises equipment (CPE), telephone, router, network switch, residential gateway (residential gateway, RG), set-top box, fixed mobile convergence product, home network adapter, and Internet access gateway. The embodiment of the present application does not limit the specific technology and specific equipment form adopted by the UE.

2. Access network equipment

The access network device in this application may be a device for communicating with UE, and is mainly responsible for wireless resource management, service quality management, data compression and encryption functions on the air interface side. The access network equipment may be a base transceiver station (BTS) in a global system of mobile communication (GSM) system or a code division multiple access (CDMA) system, a broadband code division multiple access Base station (nodeB, NB) in (wideband code division multiple access, WCDMA) system, evolved base station (evolutional nodeB, eNB or eNodeB) in LTE system, worldwide interoperability for microwave access (WiMAX) communication A base station in the system, a wireless controller in a cloud radio access network (CRAN) scenario, an access point, a relay station, a vehicle-mounted device, or a wearable device in a wireless high-fidelity (wireless fidelity) system. Alternatively, the access network device may be a terminal that assumes the base station function in D2D communication or machine-to-machine communication. Alternatively, the access network device may be a network device in a 5G network or a network device in a future evolved PLMN network. In addition, the access network device may also be a module or unit that completes some functions of the base station, for example, it may be a centralized unit (central unit, CU) or a distributed unit (distributed unit, DU). The embodiment of the present application does not limit the specific technology and specific equipment form adopted by the access network equipment.

3. UPF

UPF is a functional network element of the user plane, supporting all or part of the following functions: interconnecting protocol data unit (protocol data unit, PDU) sessions with DN; packet routing and forwarding (for example, supporting uplink classifier for traffic Forward to DN, support branching point (Branching point) to support multi-connection (multi-homed) PDU session); packet inspection.

4. DN

DN is the destination accessed by the user's PDU session. The DN is an operator network that provides data transmission services for users, for example, Internet protocol (internet protocol, IP) multimedia service (IP multi-media service, IMS), Internet. The UE can access the DN by establishing a PDU session between the UE, the RAN, the UPF, and the DN.

5. AUSF

The AUSF belongs to the control plane network element of the core network, and is mainly responsible for authenticating and authorizing users to ensure that users are legitimate users.

6. AMF

AMF is a network element with mobility management function, which is responsible for user mobility management, including mobility state management, allocation of user temporary IDs, authentication and authorization of users.

7. SMF

SMF is a session management function network element, which is responsible for user plane network element selection, user plane network element redirection, IP address allocation, bearer establishment, modification and release, and QoS control.

8.NEF

NEF belongs to the core network control plane network element, which is responsible for the opening of mobile network capabilities to the outside world, and the opening of network capabilities and services to the outside world.

9. NRF

NRF belongs to the network element of the control plane of the core network, and is responsible for the registration and discovery of the network element, and maintains the information of the network element, for example, the instance identifier, type, PLMN, slice-related identifier, IP address or FQDN of the network element, the network element Meta capabilities, supporting services.

10. PCF

PCF includes policy control decision-making and flow-based charging control functions, including user subscription data management functions, policy control functions, charging policy control functions, and QoS control. It mainly supports the provision of a unified policy framework to control network behavior, and provides policy rules for The network function of the control layer is also responsible for obtaining user subscription information related to policy decisions.

11. UDM

The UDM belongs to the core network control plane network element, belongs to the user server, and is responsible for managing the subscription data, and is responsible for notifying the corresponding network element when the subscription data is modified.

12. NSSF

NSSF is responsible for the selection of network slices.

13. NSACF

NSACF is responsible for admission control on network slices. For example, when network slices need to perform admission control, NSACF can control the number of users connected to each network slice. The maximum number of users allowed per network slice (max number of UEs per network slice) can be configured on NSACF. When increasing the number of currently registered users of a network slice, NSACF first determines whether the number of users currently connected to the network slice has reached the maximum number of users under the network slice.

NSACF may also be responsible for controlling the number of established sessions on each network slice. The maximum number of sessions allowed per network slice (max number of PDU sessions per network slice) can be configured on NSACF. When increasing the current number of sessions in a network slice, NSACF first determines whether the number of currently established sessions on the network slice has reached the maximum number of sessions under the network slice.

14. AF

The AF is responsible for providing certain application layer services to the UE. When the AF provides services to the UE, it has requirements for QoS (policy) and charging policy (charging), and needs to notify the network. At the same time, the AF also needs application-related information fed back by the core network.

Fig. 2 is another schematic architecture diagram of a communication system to which the present application can be applied. Figure 2 is a schematic diagram of a 5G network architecture based on point-to-point interfaces. The main difference between Figure 2 and Figure 1 is that the interfaces between network elements in Figure 2 are point-to-point interfaces rather than service-oriented interfaces. The description of each network element can be Referring to FIG. 1 , details will not be repeated here.

Fig. 3 is another schematic architecture diagram of a communication system to which the present application can be applied. FIG. 3 is a non-roaming architecture for intercommunication between a fifth generation communication system (5 ^th generation system, 5GS) and an EPC/evolved universal terrestrial radio access network (e-UTRAN). Among them, some network elements of the EPC network and some network elements of the 5G network can be deployed on the same physical entity, so that the EPS network and the 5G network can interact. For example, as shown in FIG. 3 , a home subscriber server (home subscriber server, HSS) network element and a unified data management (unified data management, UDM) network element may be deployed in the same physical entity. A control plane function (PGW-C) and a session management function (session management function, SMF) network element of a packet data network gateway (packet data network gateway, PGW) can be deployed in the same physical entity. A user plane function (PGW-U) and a user plane function (User plane function, UPF) network element of a packet data network gateway (packet data network gateway, PGW) may be deployed in the same physical entity. The foregoing network element may also be a separate network element, which is not limited in this embodiment of the present application. The N26 interface is an inter-CN interface (inter-CN interface) between the mobility management entity (MME) and the 5GS AMF, and is used to realize the intercommunication between the EPC and the 5G core network. Support for the N26 interface is optional for interworking between 5GS and EPC/E-UTRAN. The N26 supports a subset of the functions supported by the S10 (basic functions of the interconnect). HSS+UDM network element is a network element with HSS function and UDM network element function, which can store user's subscription data. For example, the subscription data of the user includes subscription data related to mobility management and subscription data related to session management. The HSS+UDM network element may also be called HSS+UDM equipment or HSS+UDM entity or UDM+HSS network element or UDM+HSS equipment or UDM+HSS entity. The SMF+PGW-C network element has the functions of SMF and PGW-C, and the UPF+PGW-C network element has the functions of UPF network element and PGW-U. The UE residing in the EPC can obtain the service of the 5G core network or the service of the EPC through the SMF+PGW-C when establishing a PDN connection. The 5G part involved in Figure 3 can be shown in Figure 1 or Figure 2 .

It should be understood that the naming of each network element shown in FIG. 1 to FIG. 3 is only a name, and the name does not limit the function of the network element itself. In different networks, the foregoing network elements may also have other names, which are not specifically limited in this embodiment of the present application. For example, in a 6G network, some or all of the above-mentioned network elements may use the terms in 5G, or may be named by other names, etc., which will be described in a unified manner here, and will not be described in detail below. Similarly, the interfaces between network elements shown in Figures 1 to 3 are only examples, and in 5G networks and other networks in the future, the interfaces between network elements may not be the interfaces shown in the figure. There is no limit to this. It should also be understood that the embodiments of the present application are not limited to the system architectures shown in FIG. 1 to FIG. 3 . For example, a communication system to which the present application can be applied may include more or fewer network elements or devices. The devices or network elements in FIG. 1 to FIG. 3 may be hardware, or functionally divided software, or a combination of the above two. The devices or network elements in FIG. 1 to FIG. 3 may communicate through other devices or network elements.

In the 5G communication system, network slicing is introduced. Network slicing is a logic-based concept. By reorganizing resources, multiple logical subnets with different characteristics and isolated from each other can be virtualized on the same set of physical facilities to provide targeted services to users. Different logical subnets are identified and distinguished by single network slice selection assistance information (single network slice selection assistance information, S-NSSAI). In an actual deployment scenario of network slicing, due to the limitation of network resources, a network slice can accommodate a limited number of connected users and a limited number of established sessions.

According to the current 5G standard, if a network slice needs to perform admission control, then the network slice can be controlled through NSACF. For example, the NSACF performs admission control on the number of UEs accessed by the network slice or performs admission control on the number of sessions established by the network slice. Specifically, taking NSACF as an example to perform admission control on the number of UEs connected to the network slice, NSACF can configure network slice quotas (quota) and store the number of users currently connected to the network slice. During the registration process, the number of UEs connected to the network slice is controlled. Taking the control of the number of UEs connected to the network slice during the registration process as an example, the UE can carry the requested NSSAI (requested NSSAI); the AMF judges whether the requested NSSAI includes the network slice admission control (network slice admission control, NSAC) network slices, if the requested NSSAI contains network slices that need to perform NSAC, AMF can determine the target NSSAI (target NSSAI), the target NSSAI is the set of all network slices that the UE requests to access and needs to perform NSAC; AMF and NSACF The network elements interact to trigger the NSACF to judge whether the quota of the current network slice allows the UE to access the network slice. If the current quota of a network slice included in the target NSSAI is still available, the UE can access the network slice, and at the same time, the NSACF counts the number of users in the network slice with available quotas, and the NSACF returns "quota available" to the AMF Indication information, AMF "quota available" network slice is included in the allowed NSSAI (allowed NSSAI); if the current quota of a certain network slice contained in the target NSSAI is not available, the UE cannot access the network slice, and NSACF sends a message to AMF An indication of "no quota available" is returned, and AMF's "no quota available" network slice is included in the rejected NSSAI (rejected NSSAI). Similarly, the number of sessions established by the network slice can also be controlled through the NSACF. Specifically, the NSACF can configure the quota of the network slice and save the number of sessions currently established in the network slice. The NSACF can control the number of sessions established in the network slice during the PDU session management process of the UE. The specific process is related to the The process of controlling the number of UEs accessed by the network slice is similar and will not be repeated here.

It should be noted that the NSACF responsible for controlling the number of users accessed on each network slice and the NSACF responsible for controlling the number of established sessions on each network slice may be the same or different.

For the interworking scenario shown in Figure 3, when the UE initiates the PDN connection establishment process, the PDN connection will be associated with a core network element of a network slice, such as SMF+PGW-C, which can also be understood as the UE will use SMF+PGW -C's network slice resources establish a PDN connection; when the UE initiates the PDN connection release process, the SMF+PGW-C resources associated with the PDN connection will be released. When the UE residing in the EPC initiates the PDN connection establishment process or the PDN connection release process, it will simultaneously trigger the control of the number of UEs accessing the network slice and the number of sessions established by the network slice. In this case, how to control the number of users connected to the network slice and the number of sessions established by the network slice becomes an urgent problem to be solved.

In view of the above problems, the present application provides a network slice admission control method and device, which can realize the control of the number of users accessing the network slice and the number of sessions established in the network slice, and contribute to the admission control of the network slice.

Before describing the technical solutions of the present application, the terms involved in the present application will be described first.

The quota for the number of UEs in the network slice shown in this application can also be understood as: the number of UEs accessed by the network slice, or the maximum number of UEs accessed by the network slice, or the number of UEs allowed to be accessed by the network slice number, or, the number of UEs that the network slice allows to register. The quota for the number of UEs in the network slice is not available. It can also be understood as: the quota for the number of UEs in the network slice is exceeded, or the number of UEs connected to the network slice exceeds the quota, or the number of UEs connected to the network slice exceeds the quota. quota, or, the number of UEs accessed by the network slice exceeds the maximum value, or, the number of UEs accessed by the network slice has reached the maximum number of UEs allowed to be accessed, or, the number of UEs accessed by the network slice is greater than or equal to the preset A threshold is set, or the number of UEs that have accessed the network slice is greater than or equal to the preset threshold. The quota for the number of UEs in the network slice is available, which can also be understood as: the number of UEs accessed by the network slice does not exceed the maximum number, or the number of UEs accessed by the network slice does not reach the maximum number of UEs allowed to be accessed, or, The number of UEs that have accessed the network slice is less than or equal to a preset threshold, or the number of UEs that have accessed the network slice is smaller than the preset threshold.

Similarly, the quota for the number of sessions of the network slice shown in this application can also be understood as: the number of sessions that have been established by the network slice, or the maximum number of sessions that have been established by the network slice, or the maximum number of sessions that have been established by the network slice The number of sessions allowed to be established, or the number of PDN connections allowed to be established by the network slice. The quota of the number of sessions of the network slice is not available, which can be understood as: the quota of the number of sessions of the network slice is exceeded, or the number of sessions allowed to be established on the network slice exceeds the quota, or the number of established sessions on the network slice exceeds the quota The maximum value, or, the number of sessions established by the network slice has reached the maximum number of sessions allowed to be established, or, the number of sessions established by the network slice is greater than or equal to the preset threshold, or, the number of sessions established by the network slice is greater than preset threshold. The quota for the number of sessions of the network slice is available, which can also be understood as: the number of sessions established by the network slice does not exceed the maximum number, or, the number of sessions established by the network slice does not reach the maximum number of sessions allowed to be accessed, or, the network slice establishes The number of sessions of the network slice is less than the preset threshold, or the number of sessions established by the network slice is less than or equal to the preset threshold.

In this application, if the number of users accessing the network slice fails to be controlled or counted, it can be explained that the number of users accessing the network slice has not changed, or the number of users accessing the network slice remains Failed to update the number of users of the network slice. Similarly, if the number of sessions established on the network slice fails to be controlled or counted, it can be explained that the number of sessions established on the network slice has not changed, or that the number of sessions established on the network slice maintains the original value, or that the number of sessions established on the network slice Session count update failed for .

It should be noted that, in this application, the number of users connected to the network slice may also be described as the number of users who have accessed the network slice or the number of users corresponding to the network slice. The number of sessions established in the network slice can also be described as the number of sessions established in the network slice or the number of sessions corresponding to the network slice. The session in this application can be a PDU session or a PDN connection. A network slice admission control method provided by this application is described below.

Fig. 4 is a schematic flowchart of a network slice admission control method provided by the present application. The method shown in FIG. 4 may be executed by the first network element and the second network element, or may be executed by modules or units in the first network element and the second network element, which is not limited in this application. The following describes the technical solution of the present application by taking the first network element and the second network element as an example for execution.

In the method shown in Figure 4, the network element that controls the number of users accessing the network slice (hereinafter referred to as the first network element, for example, NSACF_1 that controls the number of users accessing the network slice) and the network element that controls the number of users accessing the network slice The network element that performs control on the number of sessions established on the access network slice (hereinafter referred to as the third network element, for example, NSACF_2 that performs control on the number of sessions established on the access network slice) is different.

Step 401, the second network element determines the network slice associated with the first session of the user equipment.

Wherein, the second network element serves the first session.

The second network element serving the first session can be understood as associating the first session with the second network element when establishing the first session, or establishing the first session through network slice resources supported by the second network element.

In a possible implementation manner, the first session is a PDN connection, and the second network element is an SMF+PGW-C. Specifically, the SMF+PGW-C can determine the network slice associated with the PDN connection according to the access point name (access point name, APN) carried in the session creation request message received during the PDN connection establishment process.

Step 402, the second network element sends the first information to the first network element. Correspondingly, the first network element receives the first information from the second network element.

Wherein, the first network element supports performing control on the number of users accessing the network slice. The first network element supports the control of the number of users accessing the network slice. It can also be described as, the first network element supports counting the number of UEs accessing the network slice (number of UEs counting) or the first network element has the connection The ability to exercise control over the number of users entering the network slice. The foregoing first information is used to associate the first session of the user equipment, and may also be described as information related to the first session of the user equipment. As an example, the first information is used to identify the first session, for example, the first information may include at least one of an identifier of the first session or an identifier of the second network element. Wherein, the identifier of the second network element may be the ID of the second network element, and the identifier of the first session is used to identify the first session, such as a PDU session ID.

This application does not limit the timing for the second network element to send the first information.

In some implementation manners, the second network element may send the first information to the first network element during the process of requesting to increase the number of users who have accessed the network slice determined in step 401 . For example, in the process of controlling the number of UEs and sessions triggered by the establishment of a PDN connection, the second network element may first interact with the first network element that supports the control of the number of users accessing the network slice, and trigger the first network element to increase The number of users accessing the network slice, and sending the first information to the first network element during the interaction with the first network element; if the number of users accessing the network slice is not exceeded, the second network element and the support pair The number of sessions established on the network slice is executed to interact with the third network element, and the third network element is triggered to increase the number of sessions established on the network slice. In this example, if the second network element learns from the third network element that session number control is successful, the second network element may no longer interact with the first network element, which can reduce signaling overhead.

In some other implementation manners, the second network element may send the second request message to the first network element when the number of established sessions on the network slice determined in step 401 does not exceed the maximum number of sessions allowed by the network slice, And carry the first information in the second request message. For example, in the process of controlling the number of UEs and sessions triggered by the establishment of a PDN connection, the second network element may first interact with the first network element that supports the control of the number of users accessing the network slice, and trigger the first network element to increase The number of users accessing the network slice; if the number of users accessing the network slice is not exceeded, the second network element interacts with the third network element that supports the control of the number of sessions established on the network slice to trigger the third network The element increases the number of sessions established on the network slice; if the second network element learns from the third network element that the session number control is successful, the second network element can send a second request message to the first network element, and in the second request message carry the first information, so that the first network element stores the first information.

The foregoing third network element may be an NSACF, and the third network element is different from the first network element. The first network element is responsible for controlling the number of users accessing the network slice, and the third network element is responsible for controlling the number of sessions established on the network slice. The third network element supports the control of the number of sessions established on the network slice, which can also be described as, the third network element supports the number of sessions counting on the network slice or the third network element has The ability to perform control over the number of sessions established.

In some other implementation manners, after receiving the first information, the first network element may also store the correspondence between the first information, the network slice, and the user equipment.

Step 403, the second network element sends a first request message to the first network element. Correspondingly, the first network element receives the first request message from the second network element.

Wherein, the first request message is used to indicate to reduce the number of users who have accessed the network slice.

Optionally, the first request message may be Nnsacf_NumberOfUEsPerSliceAvailabilityCheckAnd Update request.

This application does not limit the timing for the second network element to send the first request message.

In some implementation manners, the second network element may send the first request message to the first network element during the process of releasing the first session, so that the first network element controls the number of users that have accessed the network slice. For example, after the PDN connection is successfully established, the PDN connection is released at a certain moment. In the process of controlling the number of UEs and the number of sessions triggered by the release of the PDN connection, the second network element can support the execution of the number of sessions established on the network slice. The controlled third network element interacts, triggering the third network element to reduce the number of sessions established on the network slice; the second network element can also send the first The request message triggers the first network element to reduce the number of sessions established on the network slice.

In some other implementation manners, the second network element may send the first request message to the first network element when learning from the third network element that the session number control of the network slice fails during the PDN connection establishment process, so that the first network element Controls the number of users connected to the network slice. For example, in the process of controlling the number of UEs and sessions triggered by the establishment of a PDN connection, the second network element may first interact with the first network element that supports the control of the number of users accessing the network slice, and trigger the first network element to increase The number of users accessing the network slice; if the number of users accessing the network slice is not exceeded, the second network element interacts with the third network element that supports the control of the number of sessions established on the network slice to trigger the third network The second network element increases the number of sessions established on the network slice; if the second network element learns from the third network element that the control of the number of sessions fails, the second network element can send a request to the first network element that supports the control of the number of users accessing the network slice. The element sends a first request message, triggering the first network element to reduce the number of users established on the network slice.

Step 404, the first network element determines whether to reduce the number of users who have accessed the network slice according to the first information.

In some implementation manners, the first network element determines whether the user equipment has established a session other than the first session on the network slice. For example, the first network element stores the corresponding relationship between the user equipment, the network slice, and the session established by the user equipment in the network slice, and the first network element can determine whether there is a session other than the first session in the corresponding relationship Whether the user equipment has a session other than the first session on the network slice. If the user equipment has established a session other than the first session on the network slice, the first network element determines to maintain the number of users who have accessed the network slice, that is, the first network element determines not to reduce the number of users who have accessed the network slice of users. If the user equipment has only established the first session on the network slice, the first network element determines that the number of users who have accessed the network slice can be reduced.

In some other implementation manners, after receiving the first request message or determining whether to reduce the number of users who have accessed the network slice, the first network element may also delete the first information. That is to say, no matter whether the first network element determines whether to reduce the number of users who have accessed the network slice or maintain the number of users who have accessed the network slice, the first network element may delete the first information.

It should be noted that, for the first network element, whether the user equipment establishes a certain session on the network slice can be understood as whether the first network element stores information related to the session, such as the session identifier or The identifier of the session management network element serving the session.

Optionally, the first request message may also carry first information, so that the first network element determines the session that needs to be deleted.

It should be noted that the first session in FIG. 4 may also be a PDU session, and the second network element may also be an SMF, that is, the method shown in FIG. 4 is also applicable to a 5G communication system.

Fig. 5 is a schematic flowchart of another network slice admission control method provided by the present application. The method shown in FIG. 5 may be executed by the second network element, the fourth network element, and the NRF, or may be executed by modules or units in the second network element, the fourth network element, and the NRF, which is not limited in this application. The following describes the technical solution of the present application by taking the second network element, the fourth network element, and the NRF as an example for executing entities.

In the method shown in FIG. 5 , the network element that controls the number of users accessing the network slice is the same as the network element that controls the number of sessions established on the network slice, and is hereinafter referred to as the fourth network element. In other words, the fourth network element can not only control the number of users accessing the network slice, but also control the number of sessions established on the network slice.

Step 501, the second network element determines the network slice associated with the first session of the user equipment.

Wherein, the second network element serves the first session.

The second network element serves the first session. It can be understood that the first session is associated with the second network element when the first session is established, or the first session is established through the network slice resources of the second network element.

In a possible implementation manner, the first session is a PDN connection, and the second network element is an SMF+PGW-C. Specifically, the SMF+PGW-C can determine the network slice associated with the PDN connection according to the APN carried in the session creation request message received during the PDN connection establishment process.

Step 502, the second network element sends a third request message to the NRF. Correspondingly, the NRF receives the third request message from the second network element.

Wherein, the third request message is used to request information of the fourth network element.

Optionally, the third request message includes the identifier of the network slice and the second information. Wherein, the second information is used to indicate that the fourth network element requested by the second network element supports controlling the number of users accessing the network slice and supporting controlling the number of sessions established on the network slice. The second information may also be called network element capability information, and is used to indicate that the second network element requests a fourth network element capable of controlling the number of users accessing the network slice and the number of sessions established on the network slice.

In some implementation manners, the second network element may send the third request message during the process of establishing the PDN connection.

In a possible implementation manner, the second network element may call NRF service operation Nnrf_NFDiscovery request.

Optionally, the second network element may be SMF+PGW-C, and the fourth network element may be NSACF.

Step 503, the NRF sends a third response message to the second network element. Correspondingly, the second network element receives the third response message from the NRF.

Wherein, the third response message includes information of the fourth network element. For example, the third response message carries address information of the fourth network element. The fourth network element supports performing control on the number of users accessing the network slice, and supports performing control on the number of sessions established on the network slice.

In a possible implementation manner, the NRF may send the Nnrf_NFDiscovery response to the second network element.

Step 504, the second network element sends a fourth request message to the fourth network element. Correspondingly, the fourth network element receives the fourth request message from the second network element.

Wherein, the fourth request message is used to request the fourth network element to control the number of users accessing the network slice and to control the number of sessions established by the network slice. The fourth network element may be determined according to the third response message.

In some implementation manners, the fourth request message includes the identifier of the user equipment, the first information, the third information, the fourth information, and the identifier of the network slice. Wherein, the first information is used for associating the first session of the user equipment. For a detailed description of the first information, reference may be made to step 402 , which will not be repeated here. When the user equipment requests to establish the first session, the third information is used to indicate to increase the number of users who have accessed the network slice, and the fourth information is used to indicate to increase the number of sessions established on the network slice. When the user equipment requests to release the first session, the third information is used to indicate to reduce the number of users who have accessed the network slice, and the fourth information is used to indicate to reduce the number of sessions established on the network slice.

In a possible implementation manner, the second network element sends a Nnsacf_NumberOfUEsPerSliceAvailabilityCheckAndUpdate request to the fourth network element, or the second network element sends a Nnsacf_NumberOfPDUsPerSliceAvailabilityCheckAndUpdate request to the fourth network element.

Step 505, the fourth network element performs admission control on the network slice according to the fourth request message.

In some implementations, the fourth network element performing admission control on the network slice includes performing admission control on the number of users on the network slice and performing admission control on the number of sessions on the network slice, which can also be referred to as performing counting and summing of the number of UEs. Count the number of sessions, so as to ensure that the total number of UEs currently connected to the network slice does not exceed the maximum number/number of terminal devices that are allowed to access the network slice, and ensure that the total number of sessions currently established on the network slice does not exceed this The maximum number/number of sessions allowed to be established by network slicing, this application does not limit the order in which the fourth network element counts the number of users and counts the number of sessions. The fourth network element may store the number of users who have currently accessed the network slice, or store a list of UE identities that have currently accessed the network slice, and the identities in the UE identification list are used to identify UEs that have currently accessed the network slice. The fourth network element may also save the number of sessions currently established in the network slice. The fourth network element can also configure the maximum number of users allowed to access the network slice and the maximum number of sessions allowed to be established by the network slice, that is, the fourth network element can configure the maximum number of users allowed to access the network slice and the maximum number of sessions allowed to be established by the network slice. The maximum number of sessions that a network slice is allowed to establish.

When the user equipment requests to establish the first session, the third information is used to indicate to increase the number of users who have accessed the network slice, and the fourth information is used to indicate to increase the number of sessions established on the network slice. The fourth network element determines whether the number of users accessing the network slice exceeds the maximum number of users allowed by the network slice, and determines whether the number of sessions established on the network slice exceeds the maximum number of sessions allowed by the network slice. If the fourth network element determines that the number of users corresponding to the network slice does not exceed the maximum number of users allowed to access the network slice, and the ID of the user equipment is not stored in the user equipment identification list that has been accessed by the network slice , the fourth network element may increase the number of users corresponding to the network slice according to the third information and add the ID of the user equipment to the list of user equipment identifiers that have been accessed by the network slice, thereby saving the ID of the user equipment and the network slice, and the fourth network element judges that the number of sessions corresponding to the network slice does not exceed the maximum number of sessions allowed by the network slice, the fourth network element can increase the number of sessions corresponding to the network slice according to the fourth information, And save the corresponding relationship between the first information and the network slice. If the number of users corresponding to the network slice exceeds the maximum number of users allowed to access the network slice and/or the number of sessions exceeds the maximum number of sessions allowed to be established by the network slice, the fourth network element may not change the corresponding The number of users and the number of sessions corresponding to the network slice do not change.

When the user equipment requests to release the first session, the third information is used to indicate to reduce the number of users who have accessed the network slice, and the fourth information is used to indicate to reduce the number of sessions established on the network slice. The fourth network element reduces the number of sessions corresponding to the network slice according to the fourth information, and deletes the first information in the context information; the fourth network element determines whether the user equipment has established a session other than the first session on the network slice . For example, the first network element stores the corresponding relationship between the user equipment, the network slice, and the session established by the user equipment in the network slice, and the first network element can determine whether there is a session other than the first session in the corresponding relationship Whether the user equipment has a session other than the first session on the network slice. If the user equipment has established a session other than the first session on the network slice, the first network element determines to maintain the number of users who have accessed the network slice, that is, the first network element determines not to reduce the number of users who have accessed the network slice of users. If the user equipment has only established the first session on the network slice, the first network element determines that the number of users who have accessed the network slice can be reduced.

Step 506, the fourth network element sends a fourth response message to the second network element. Correspondingly, the second network element receives the fourth response message from the fourth network element.

Wherein, the fourth response message is used to indicate the result of performing admission control on the network slice. The result may include: performing admission control on the network slice successfully or failing to perform admission control on the network slice. If the second network element determines that the number of users accessing the network slice does not exceed the maximum number of users allowed by the network slice, and the number of sessions established on the network slice does not exceed the maximum number of sessions allowed by the network slice, then The network slice performs admission control successfully. According to the above description, it can be understood that if the admission control is successfully performed on the network slice, it means that both the counting of the number of UEs and the counting of the number of sessions are performed successfully. If the second network element judges that the number of users accessing the network slice has exceeded the maximum number of users allowed by the network slice, but the number of sessions established on the network slice does not exceed the maximum number of sessions allowed by the network slice, the network The slice fails to perform admission control; if the second network element judges that the number of users accessing the network slice does not exceed the maximum number of users allowed by the network slice, but the number of sessions established on the network slice has exceeded the number of sessions allowed by the network slice If the maximum number of sessions of the network slice fails, the network slice fails to perform admission control; if the second network element judges that the number of users accessing the network slice has exceeded the maximum number of users allowed to access the network slice, but the sessions established on the network slice If the number exceeds the maximum number of sessions allowed by the network slice, the network slice fails to perform admission control. According to the above description, it can be understood that if the admission control of the network slice fails, it means that the counting of the number of UEs and/or the counting of the number of sessions fails, and the fourth response message may also carry a failure reason value. If the user equipment Request to establish the first session, the failure reason value may be whether the number of users accessing the network slice exceeds the maximum number of users allowed by the network slice and/or whether the number of sessions established on the network slice exceeds the number allowed by the network slice The maximum number of established sessions. If the user equipment requests to release the first session, the failure cause value may be that the user equipment still has other sessions on the network slice.

Similarly, the first session in FIG. 5 may also be a PDU session, and the second network element may also be an SMF, that is, the method shown in FIG. 5 is also applicable to a 5G communication system.

In the above technical solution, firstly, the process of discovering the fourth network element by the second network element is enhanced. Specifically, the second network element requests the NRF to select for it while supporting the control of the number of UEs accessing the network slice and supporting the The fourth network element that controls the number of sessions established on the network slice and performs control. Secondly, when determining the number of users and the number of sessions corresponding to the network slice, the fourth network element also judges whether the user equipment has already connected to the network slice or whether all sessions of the user equipment should be released. In this way, network slice admission control in interworking scenarios can be realized.

The technical solution of the present application will be described in detail below in conjunction with specific examples.

Example 1

In Example 1, the UE respectively initiates the establishment process of establishing multiple PDN connections (PDN connection establishment), and multiple PDN connections are associated with the same network slice. The quota of the number of sessions managed by the NSACF is the same NSACF. FIG. 6 takes the UE establishing two PDN connections as an example.

FIG. 6 is an example of a network slice admission control method provided by this application. SMF+PGW-C_1 and SMF+PGW-C_2 in FIG. 6 may correspond to the second network element in FIG. 5 above, and NSACF may correspond to the fourth network element in FIG. 5 above.

In step 601, the UE initiates a PDN connection establishment procedure.

In a possible implementation, the UE sends a PDN connection establishment request message (PDN connectivity request) to the MME, and the message may carry an APN; after the MME receives the PDN connection establishment request message, it Location, select a serving gateway (serving gateway, SGW) and SMF+PGW-C network element; MME sends a create session request message (create session request) to the SGW, and then the SGW sends a create session request message to the selected SMF+PGW-C. For convenience of description, the PDN connection is referred to as PDN connection_1 hereinafter, and the selected SMF+PGW-C is referred to as SMF+PGW-C_1.

Step 602, SMF+PGW-C_1 determines the network slice associated with the PDN connection.

In a possible implementation manner, SMF+PGW-C_1 determines the network slice associated with the PDN connection according to the APN carried in the session creation request message.

In step 603, SMF+PGW-C_1 determines whether the network slice needs to execute the NSAC process according to the configuration information.

In a possible implementation manner, SMF+PGW-C_1 stores configuration information of network slicing that needs to perform NSAC. After SMF+PGW-C_1 determines the network slice associated with the PDN connection, SMF+PGW-C_1 determines whether the network slice needs to execute the NSAC process according to the configuration information.

If SMF+PGW-C_1 determines that the network slice needs to execute the NSAC process, it can continue to execute steps 604-608. If SMF+PGW-C_1 determines that the network slice does not need to execute the NSAC process, steps 604-608 can be skipped, and step 609 can be directly executed.

Step 604, SMF+PGW-C_1 sends a third request message_1 to NRF.

Wherein, the third request message_1 is used to request the NSACF that serves the network slice associated with PDN connection_1, supports the control of the number of UEs accessing the network slice, and supports the control of the number of sessions established on the network slice. As an example, the third request message_1 may carry S-NSSAI and NSACF service capability indication information (NSACF service capability) for identifying the network slice, and the NSACF service capability indication information is used to indicate the SMF+PGW-C_1 request The NSACF supports the control of the number of UEs accessing the network slice and the control of the number of sessions established on the network slice, that is, the second information described in FIG. 5 .

It should be noted that NSACF supports the control of the number of UEs accessing network slices. It can also be described as NSACF has the ability to control the number of UEs accessing network slices. The same description below is that NSACF supports the number of UEs accessing network slices. Executive control. NSACF supports the control of the number of sessions established on the control network slice. It can also be described as NSACF has the ability to control the number of sessions established on the network slice. The same description below is that NSACF supports the control of the number of sessions established on the control network slice.

One possible implementation, SMF+PGW-C_1 can call NRF's service operation Nnrf_NFDiscovery request.

Step 605, the NRF sends a third response message_1 to the SMF+PGW-C_1 according to the third request message_1.

Wherein, the third response message_1 carries relevant information of the NSACF. The relevant information of the NSACF may include the address of the NSACF. The NSACF is the NSACF serving the network slice identified by the S-NSSAI carried in the third request message_1, and the NSACF also supports the control and support of the number of UEs accessing the network slice identified by the S-NSSAI Control is performed on the number of sessions established on the network slice identified by the S-NSSAI.

In a possible implementation, NRF returns Nnrf_NFDiscovery response to SMF+PGW-C_1, carrying NSACF information, such as NSACF address information.

Optionally, SMF+PGW-C_1 saves the NSACF information returned by the NRF in the context.

Step 606, SMF+PGW-C_1 determines the NSACF according to the third response message_1, and sends the fourth request message_1 to the NSACF.

Wherein, the fourth request message_1 may carry UE ID, update flag_1 (update_flag_1), S-NSSAI, update flag_2 (update_flag_2), and session_1 related information. The UE ID can be determined by SMF+PGW-C_1 according to the session creation request message. For example, the session creation request message carries the UE ID. Exemplarily, the UE ID can be a permanent identifier of the UE, for example, International Mobile Subscriber Identity code (international mobile subscriber identity, IMSI). The update flag_1 is used to indicate to increase the number of UEs corresponding to the network slice identified by the S-NSSAI, for example, add 1 to the number of UEs. The update flag_2 is used to indicate to increase the number of sessions corresponding to the network slice identified by the S-NSSAI, for example, add 1 to the number of sessions. The information related to session_1 may include the identifier of SMF+PGW-C_1 and/or the identifier of session_1, the identifier of SMF+PGW-C_1 may be the ID of SMF+PGW-C_1, and the identifier of session_1 is used to identify the Session_1, such as PDU session ID_1, where PDU session ID_1 may be included in the create session request message.

A possible implementation, SMF+PGW-C_1 sends Nnsacf_NumberOfPDUsPerSliceAvailabilityCheckAndUpdate request to NSACF, or SMF+PGW-C_1 sends Nnsacf_NumberOfUEsPerSliceAvailabilityCheckAndUpdate request to NSACF, which is not limited in this application.

In step 607, the NSACF performs admission control on the network slice according to the fourth request message_1.

In a possible implementation, NSACF performs admission control on network slices, including performing admission control on the number of UEs on the network slices and performing admission control on the number of sessions on the network slices, which can also be called counting the number of UEs (number of UEs counting) and the number of sessions counting (number of sessions counting), so as to ensure that the sum of the number of UEs currently connected to the network slice does not exceed the maximum number/number of terminal devices that are allowed to access the network slice, and to ensure that the current The total number of sessions established by the network slice does not exceed the maximum number/number of sessions allowed by the network slice. The NSACF can store the number of UEs that have currently accessed the network slice, or store a list of UE identities that have currently accessed the network slice, and the identities in the UE identification list are used to identify UEs that have currently accessed the network slice. NSACF can also save the number of sessions currently established in the network slice. NSACF can also configure the maximum number of UEs allowed to access the network slice and the maximum number of sessions allowed to be established by the network slice, that is, NSACF can configure the maximum number of users allowed to access the network slice and the maximum The number of sessions.

For example, the NSACF judges whether the quota for the number of UEs corresponding to the network slice identified by the S-NSSAI is available (that is, whether the number of UEs currently accessing the network slice identified by the S-NSSAI exceeds the maximum number), Whether the quota of the number of sessions corresponding to the identified network slice is available (that is, whether the number of sessions currently established by the network slice identified by the S-NSSAI exceeds the maximum number). If the NSACF determines that the quota for the number of UEs corresponding to the network slice identified by the S-NSSAI is available, and the UE ID is not stored in the list of UE identities that have been accessed by the network slice identified by the S-NSSAI, the NSACF will update the Flag_1 increases the number of UEs corresponding to the network slice (for example, the number of UEs accessing the network slice identified by the S-NSSAI plus 1), and adds the UE ID to the list of UE identifiers that have been accessed by the network slice, so that Save the correspondence between UE ID and S-NSSAI. NSACF also judges that the quota of the number of sessions of the network slice identified by S-NSSAI is available, and NSACF increases the number of sessions corresponding to the network slice according to the update flag_2 (for example, the number of sessions established in the network slice identified by S-NSSAI plus 1), and save the corresponding relationship between session_1 related information and S-NSSAI. If the quota of the number of UEs and/or the number of sessions corresponding to the network slice identified by the S-NSSAI is not available, the NSACF may not change the number of UEs corresponding to the network slice and the number of sessions corresponding to the network slice.

It should be noted that the present application does not limit the order in which the NSACF performs the counting of the number of UEs and the number of sessions. For example, counting the number of UEs may be performed first and then counting the number of sessions. In this case, if it is determined that the quota for the number of UEs corresponding to the network slice identified by the S-NSSAI is available and the number of UEs is increased by one, NSACF If it is determined that the quota for the number of sessions is unavailable, then NSACF will update the number of UEs after determining that the quota for the number of sessions is unavailable, that is, NSACF will decrease the number of UEs by one and delete the UE ID from the identification list of terminal devices that have been connected to the network slice . For another example, counting the number of sessions may be performed first and then counting the number of UEs. In this case, if it is determined that the quota for the corresponding number of sessions of the network slice identified by the S-NSSAI is available and the number of sessions is increased by one, NSACF If it is determined that the quota for the number of UEs is unavailable, the NSACF updates the number of sessions after determining that the quota for the UE is unavailable, that is, the NSACF then subtracts one from the number of sessions. For another example, the counting of the number of UEs and the number of sessions may be performed simultaneously. In this case, the NSACF may integrate the judgment results of the quota of the number of UEs and the judgment result of the quota of the number of sessions, and update the number of UEs and the number of sessions in a unified manner.

Since Figure 6 takes the establishment of two PDN connections as an example, the first PDN connection is established at this time, so the NSACF will increase the number of UEs corresponding to the network slice (for example, the number of UEs accessing the network slice identified by the S-NSSAI plus 1) and increase the number of sessions corresponding to the network slice (for example, the number of sessions established in the network slice identified by S-NSSAI plus 1), and save the correspondence between UE ID, S-NSSAI, and session_1-related information .

Step 608, NSACF sends a fourth response message_1 to SMF+PGW-C_1.

Wherein, the fourth response message_1 is used to indicate the result of performing admission control on the network slice. The result may include: performing admission control on the network slice successfully or failing to perform admission control on the network slice. If the admission control on the network slice is successfully performed, it means that the counting of the number of UEs and the number of sessions are both performed successfully. If the admission control on the network slice fails, it means that the counting of the number of UEs and/or the number of sessions is failed If the counting fails, the fourth response message_1 may also carry a failure cause value, which may be used to indicate that the number of UEs that have been accessed by the network slice has reached the maximum value and/or that the number of sessions that have been established by the network slice has reached the maximum value. maximum value. In this example, the fourth response message_1 may indicate that admission control on the network slice is performed successfully.

A possible implementation mode, NSACF sends Nnsacf_NumberOfPDUsPerSliceAvailabilityCheckAndUpdate response to SMF+PGW-C_1, or NSACF sends Nnsacf_NumberOfUEsPerSliceAvailabilityCheckAndUpdate response to SMF+PGW-C_1, this application does not limit it, NSACF carries in the message sent by NSACF to perform admission control on network slices the result of.

Step 609, execute the remaining procedures of PDN connection establishment.

So far, the establishment of the PDN connection_1 is completed, and the NSACF stores the correspondence between the UE ID, S-NSSAI and session_1-related information.

In step 610, the UE initiates a PDN connection establishment procedure again.

The implementation manner of step 610 is the same as that of step 601, and reference may be made to the description of step 601, which will not be repeated here. For convenience of description, the PDN connection is called PDN connection_2 hereinafter, and the selected SMF+PGW-C is called SMF+PGW-C_2.

Step 611, SMF+PGW-C_2 determines the network slice associated with the PDN connection.

In a possible implementation manner, SMF+PGW-C_2 determines the network slice associated with the PDN connection according to the APN carried in the session creation request message.

The network slice determined in step 611 is the same as the network slice determined in step 603 .

In step 612, SMF+PGW-C_2 determines whether the network slice needs to execute the NSAC process according to the configuration information.

In a possible implementation manner, SMF+PGW-C_2 stores configuration information of network slicing that needs to perform NSAC. After SMF+PGW-C_2 determines the network slice associated with the PDN connection, SMF+PGW-C_2 determines whether the network slice needs to execute the NSAC process according to the configuration information.

If SMF+PGW-C_2 determines that the network slice needs to execute the NSAC process, it may continue to execute steps 613-617. If SMF+PGW-C_2 determines that the network slice does not need to execute the NSAC process, steps 613-617 may be skipped, and step 618 may be directly executed.

Step 613, SMF+PGW-C_2 sends a third request message_2 to NRF.

Among them, the third request message_2 is used to request the NSACF that serves the network slice associated with PDN connection_2 and supports the control of the number of UEs accessing the network slice and the number of sessions established on the network slice . As an example, the third request message_2 may carry S-NSSAI and NSACF service capability indication information used to identify the network slice, and the NSACF service capability indication information is used to indicate that the NSACF requested by SMF+PGW-C_2 simultaneously supports the The number of UEs accessing the network slice identified by the S-NSSAI is controlled and the number of sessions established on the network slice identified by the S-NSSAI is controlled.

One possible implementation, SMF+PGW-C_2 can call NRF's service operation Nnrf_NFDiscovery request.

Step 614, the NRF sends a third response message_2 to the SMF+PGW-C_2 according to the third request message_2.

Wherein, the third response message_2 carries relevant information of the NSACF. The relevant information of the NSACF may include the address of the NSACF. The NSACF is the NSACF serving the network slice identified by the S-NSSAI carried in the third request message_2, and the NSACF also supports the control and support of the number of UEs accessing the network slice identified by the S-NSSAI Control is performed on the number of sessions established on the network slice identified by the S-NSSAI. The NSACF in step 614 is the same as the NSACF in step 605 .

In a possible implementation, NRF returns Nnrf_NFDiscovery response to SMF+PGW-C_2, carrying NSACF information, such as NSACF address information.

Optionally, SMF+PGW-C_2 saves the NSACF information returned by the NRF in the context.

Step 615, SMF+PGW-C_2 determines the NSACF according to the third response message_2, and sends the fourth request message_2 to the NSACF.

Wherein, the fourth request message_2 may carry information related to UE ID, update flag_1, S-NSSAI, update flag_2, and session_2. The UE ID may be determined by SMF+PGW-C_2 according to the session creation request message. For example, the session creation request message carries the UE ID. Exemplarily, the UE ID may be the IMSI of the UE. The update flag_1 is used to indicate to increase the number of UEs corresponding to the network slice identified by the S-NSSAI, for example, add 1 to the number of UEs. The update flag_2 is used to indicate to increase the number of sessions corresponding to the network slice identified by the S-NSSAI, for example, add 1 to the number of sessions. The information related to session_2 may include the identifier of SMF+PGW-C_2 and/or the identifier of session_2, the identifier of SMF+PGW-C_2 may be the ID of SMF+PGW-C_2, and the identifier of session_2 is used to identify the Session_2, such as PDU session ID_2, where PDU session ID_2 may be included in the create session request message.

A possible implementation, SMF+PGW-C_2 sends Nnsacf_NumberOfPDUsPerSliceAvailabilityCheckAndUpdate request to NSACF, or SMF+PGW-C_2 sends Nnsacf_NumberOfUEsPerSliceAvailabilityCheckAndUpdate request to NSACF, which is not limited in this application.

In step 616, the NSACF performs admission control on the network slice according to the fourth request message_2.

In a possible implementation, NSACF performs admission control on network slices, including performing admission control on the number of UEs on the network slices and performing admission control on the number of sessions on the network slices, which can also be called counting the number of UEs and the number of sessions of counts.

Specifically, the NSACF judges whether the quota for the number of UEs corresponding to the network slice identified by the S-NSSAI is available (that is, whether the number of UEs currently accessing the network slice identified by the S-NSSAI exceeds the maximum number), and judges whether the quota specified by the S-NSSAI is available. Whether the quota of the number of sessions corresponding to the network slice identified by the NSSAI is available (that is, whether the number of sessions currently established by the network slice identified by the S-NSSAI exceeds the maximum number). NSACF judges that the UE ID has been stored in the network slice identified by the S-NSSAI according to the correspondence between the UE ID and the S-NSSAI stored in the context information (that is, the correspondence between the UE ID and the S-NSSAI stored in step 607). In the list of UE identifiers that have been accessed, it means that the UE has accessed the network slice identified by S-NSSAI. In this case, NSACF does not need to count the number of UEs corresponding to the network slice, that is, the number of UEs in the network slice Keep unchanged, and at the same time, NSACF judges that the quota of the number of sessions of the network slice identified by S-NSSAI is available, and NSACF increases the number of sessions corresponding to the network slice according to the update flag_2 (for example, established in the network slice identified by S-NSSAI number of sessions plus 1), and save the correspondence between the information related to session_2 and the S-NSSAI. If the quota of the number of UEs and/or the number of sessions corresponding to the network slice identified by the S-NSSAI is not available, the NSACF may not change the number of UEs corresponding to the network slice and the number of sessions corresponding to the network slice.

Likewise, the present application does not limit the order in which the NSACF performs the counting of the number of UEs and the number of sessions. For specific description, reference may be made to the above, and details are not repeated here.

Since Figure 6 takes the establishment of two PDN connections as an example, the second PDN connection is established at this time, so NSACF will keep the number of UEs corresponding to the network slice unchanged, increase the number of sessions corresponding to the network slice, and continue to save the UE ID , the corresponding relationship between the information related to session_2 and the S-NSSAI.

Step 617, NSACF sends a fourth response message_2 to SMF+PGW-C_2.

Wherein, the fourth response message_2 is used to indicate the result of performing admission control on the network slice. The result may include: performing admission control on the network slice successfully or failing to perform admission control on the network slice. If the admission control is successfully performed on the network slice, it means that both the counting of the number of UEs and the counting of the number of sessions are performed successfully. If the execution of admission control on the network slice fails, it means that the counting of the number of UEs and/or the counting of the number of sessions fails, then the fourth response message_2 may also carry a failure reason value, for example, the failure reason value is used for Indicating that the number of UEs that have accessed the network slice has reached the maximum value and/or indicating that the number of sessions that have been established in the network slice has reached the maximum value. In this example, the fourth response message_2 may indicate that the admission control on the network slice is successfully performed.

A possible implementation mode, NSACF sends Nnsacf_NumberOfPDUsPerSliceAvailabilityCheckAndUpdate response to SMF+PGW-C_2, or NSACF sends Nnsacf_NumberOfUEsPerSliceAvailabilityCheckAndUpdate response to SMF+PGW-C_2, this application does not make a limitation, NSACF carries the admission control on network slices in the sent message the result of.

Step 618, execute the remaining procedures of PDN connection establishment.

So far, the establishment of PDN connection_1 and PDN connection_2 is completed, and the corresponding relationship between UE ID, S-NSSAI, information related to session_1 and information related to session_2 is saved in NSACF.

It can be seen from the above that for the determination process of the number of UEs and the number of sessions triggered by the establishment of a PDN connection, in Example 1, the process of discovering NSACF by SMF+PGW-C is firstly enhanced, specifically, SMF+PGW-C requests NRF selects for it an NSACF that supports both the control of the number of UEs accessing the network slice and the control of the number of sessions established on the network slice. Secondly, when the NSACF determines the number of UEs and sessions corresponding to the network slice, it will also determine whether the UE has already accessed the network slice. If the UE has already accessed the network slice, the number of UEs may not be increased. In this way, network slice admission control in interworking scenarios can be realized.

Example 2

In Example 2, the UE initiates the release process of multiple PDN connections respectively, and multiple PDN connections are associated with the same network slice, the NSACF responsible for the quota management of the number of UEs in the network slice and the quota management of the number of sessions in the network slice The NSACF is the same NSACF. FIG. 7 takes the UE establishing two PDN connections as an example. Assuming that according to example 1, the UE has established two PDN connections (PDN connection_1 and PDN connection_2) for the same network slice, at a certain moment, the UE initiates a PDN connection release procedure (PDN connection release) to the network.

Fig. 7 is another example of the network slice admission control method provided by this application. SMF+PGW-C_1 and SMF+PGW-C_2 in FIG. 7 may correspond to the second network element in FIG. 5 above, and NSACF may correspond to the fourth network element in FIG. 5 above.

In step 701, the UE initiates a PDN connection_1 release procedure.

In a possible implementation, the UE sends a PDN connection release message (PDN disconnection request) to the MME; after the MME receives the message, it determines that the UE wants to release the PDN connection, and the MME sends a delete session request message (delete session request) to the SGW serving the PDN connection. session request), the SGW sends a delete session request message to the SMF+PGW-C_1 serving the PDN connection.

Step 702, SMF+PGW-C_1 sends a fourth request message_3 to NSACF.

Wherein, the fourth request message_3 may carry information related to UE ID, update flag_1, S-NSSAI, update flag_2, and session_1. The UE ID may be determined by SMF+PGW-C_1 according to the delete session request message. Exemplarily, the UE ID may be a permanent identifier of the UE, for example, IMSI. The update flag_1 is used to indicate to reduce the number of UEs corresponding to the network slice identified by the S-NSSAI, for example, the number of UEs is reduced by 1. The update flag_2 is used to indicate that the number of sessions corresponding to the network slice identified by the S-NSSAI is reduced, for example, the number of sessions is reduced by 1. The information related to session_1 may include the identifier of SMF+PGW-C_1 and/or the identifier of session_1, the identifier of SMF+PGW-C_1 may be the ID of SMF+PGW-C_1, and the identifier of session_1 is used to identify the Session_1, such as PDU session ID_1, where PDU session ID_1 may be included in the create session request message.

In a possible implementation manner, if the SMF+PGW-C_1 saves the information of the NSACF in the context, then the SMF+PGW-C_1 can directly determine the NSACF according to the information of the NSACF.

As another implementation, if SMF+PGW-C_1 does not save the information of NSACF in the context, then SMF+PGW-C_1 may request NRF to discover NSACF. For this method, reference may be made to step 604 and step 605 above.

In step 703, the NSACF performs admission control on the network slice according to the fourth request message_3.

In a possible implementation, NSACF performs admission control on network slices, including performing admission control on the number of UEs on the network slices and performing admission control on the number of sessions on the network slices, which can also be called counting the number of UEs and the number of sessions The present application does not limit the order in which the NSACF performs the counting of the number of UEs and the number of sessions.

In a possible implementation, the NSACF first performs the counting of the number of sessions, and the NSACF reduces the number of sessions corresponding to the network slice identified by the S-NSSAI according to the update flag_2 (for example, the NSACF will establish the session number in the network slice identified by the S-NSSAI The number of sessions minus 1), and delete the SMF+PGW-C ID_1 identifier in the context information; since NSACF_1 stores both session_1-related information and session_2-related information for the UE ID, and the UE currently only Release the PDN connection_1 corresponding to the information related to session_1, NSACF judges that the UE still has other sessions, and there is no need to reduce the number of UEs accessing the network slice identified by S-NSSAI, NSACF deletes the information related to session_1, and continues The corresponding relationship between UE ID, session_2 related information and S-NSSAI is saved. That is, the UE ID will continue to be stored in the UE ID list that the network slice identified by the S-NSSAI has already accessed.

Step 704, NSACF sends a fourth response message_3 to SMF+PGW-C_1.

Wherein, the fourth response message_3 is used to indicate the result of performing admission control on the network slice. The result may include: performing admission control on the network slice successfully or failing to perform admission control on the network slice. If the admission control is successfully performed on the network slice, it means that both the counting of the number of UEs and the counting of the number of sessions are performed successfully. If the execution of admission control on the network slice fails, it means that the counting of the number of UEs and/or the counting of the number of sessions fails, then the fourth response message_3 may also carry a failure reason value, and the failure reason value may be the UE There are also other sessions on that network slice. In step 704, the fourth response message_3 may indicate failure to perform admission control on the network slice, and the fourth response message_3 may also carry a failure reason value, for example, the UE still has other sessions on the network slice.

A possible implementation mode, NSACF sends Nnsacf_NumberOfPDUsPerSliceAvailabilityCheckAndUpdate response to SMF+PGW-C_1, or NSACF sends Nnsacf_NumberOfUEsPerSliceAvailabilityCheckAndUpdate response to SMF+PGW-C_1, this application does not make a limitation, NSACF carries the admission control on network slices in the sent message the result of.

Step 705, execute the remaining procedures of PDN connection release.

So far, the release of the PDN connection_1 is completed.

In step 706, the UE initiates the release procedure of the PDN connection_2 again.

The implementation manner of step 706 is the same as that of step 701, and reference may be made to the description of step 701, which will not be repeated here.

Step 707, SMF+PGW-C_2 sends a fourth request message_4 to the NSACF.

Wherein, the fourth request message_4 may carry UE ID, update flag_1, S-NSSAI, update flag_2, and session_2 related information. The UE ID may be determined by SMF+PGW-C_2 according to the delete session request message. Exemplarily, the UE ID may be the IMSI of the UE. The update flag_1 is used to indicate to reduce the number of UEs corresponding to the network slice identified by the S-NSSAI, for example, the number of UEs is reduced by 1. The update flag_2 is used to indicate that the number of sessions corresponding to the network slice identified by the S-NSSAI is reduced, for example, the number of sessions is reduced by 1. The information related to session_2 may include the identifier of SMF+PGW-C_2 and/or the identifier of session_2, the identifier of SMF+PGW-C_2 may be the ID of SMF+PGW-C_2, and the identifier of session_2 is used to identify the Session_2, such as PDU session ID_2, where PDU session ID_2 may be included in the create session request message.

In a possible implementation manner, if the SMF+PGW-C_2 saves the information of the NSACF in the context, then the SMF+PGW-C_2 can directly determine the NSACF according to the information of the NSACF.

As another implementation, if the SMF+PGW-C_2 does not save the information of the NSACF in the context, then the SMF+PGW-C_2 may request the NRF to discover the NSACF. For this method, reference may be made to step 613 and step 614 above.

In step 708, the NSACF performs admission control on the network slice according to the fourth request message_4.

In a possible implementation, the NSACF first performs the counting of the number of sessions, and the NSACF reduces the number of sessions corresponding to the network slice identified by the S-NSSAI according to the update flag_2 (for example, the NSACF will establish the session number in the network slice identified by the S-NSSAI The number of sessions minus 1), and delete the information related to session_2 in the context information; since only the information related to session_2 is stored in the context information for the UE ID, after deleting the information related to session_2, for the UE ID The UE has no other established sessions, so the NSACF can count the UE according to the update flag_1 (that is, the NSACF reduces the number of UEs accessing the network slice identified by the S-NSSAI), and delete the UE ID in the context information. That is, the NSACF deletes the UE ID from the list of UE identities that have been accessed by the network slice identified by the S-NSSAI.

Step 709, NSACF sends a fourth response message_4 to SMF+PGW-C_2.

Wherein, the fourth response message_4 is used to indicate the result of performing admission control on the network slice. The result may include: performing admission control on the network slice successfully or failing to perform admission control on the network slice. If the admission control is successfully performed on the network slice, it means that both the counting of the number of UEs and the counting of the number of sessions are performed successfully. If the execution of admission control on the network slice fails, it means that the counting of the number of UEs and/or the counting of the number of sessions fails, and the fourth response message_4 may also carry a failure reason value. In step 709, the fourth response message_4 may indicate that admission control on the network slice is performed successfully.

A possible implementation method, NSACF sends Nnsacf_NumberOfPDUsPerSliceAvailabilityCheckAndUpdate response to SMF+PGW-C_2, or NSACF sends Nnsacf_NumberOfUEsPerSliceAvailabilityCheckAndUpdate response to SMF+PGW-C_1, this application does not make a limitation, NSACF carries in the message sent to perform access control on network slices the result of.

Step 710, execute the remaining procedures of PDN connection release.

So far, the release of the PDN connection_1 and the PDN connection_2 is completed.

It can be seen from the above that for the determination process of the number of UEs and the number of sessions triggered by the release of the PDN connection, in Example 2, when the NSACF determines the number of UEs and the number of sessions corresponding to the network slice, it will also determine whether the PDN connection of the UE is all After release, when the UE has no established session, the NSACF reduces the number of UEs accessing the network slice identified by the S-NSSAI, and deletes the UE ID in the context information. In this way, network slice admission control in interworking scenarios can be realized.

Example 3

In example 3, the UE respectively initiates the establishment process of establishing multiple PDN connections, and the multiple PDN connections are associated with the same network slice, and the NSACF responsible for the quota management of the number of UEs in the network slice is responsible for the quota of the number of sessions in the network slice Managed NSACF is different. Figure 8 and Figure 9 take the UE establishing two PDN connections as an example, wherein Figure 8 shows the establishment process of the first PDN connection (hereinafter referred to as PDN connection_1), and Figure 9 shows the second PDN connection (hereinafter referred to as PDN connection_2) establishment process.

Fig. 8 is another example of the network slice admission control method provided by this application. SMF+PGW-C_1 in Figure 8 may correspond to the second network element in Figure 4 above, NSACF_1 may correspond to the first network element in Figure 4 above, and NSACF_2 may correspond to the above steps 402-403 involved The third network element.

In step 801, the UE initiates a PDN connection establishment procedure.

Step 802, SMF+PGW-C_1 determines the network slice associated with the PDN connection.

Step 803, SMF+PGW-C_1 determines whether the network slice needs to execute the NSAC process according to the configuration information.

The implementation manner of steps 801-803 is the same as that of steps 601-603, and reference may be made to the description of steps 601-603, which will not be repeated here. For convenience of description, the selected SMF+PGW-C is referred to as SMF+PGW-C_1 below.

If SMF+PGW-C_1 determines that the network slice needs to execute the NSAC process, it may continue to execute steps 804-816. If SMF+PGW-C_1 determines that the network slice does not need to perform the NSAC process, steps 804-816 may be skipped, and step 817 may be directly performed.

Step 804, SMF+PGW-C_1 sends a seventh request message_1 to NRF.

Wherein, the seventh request message_1 is used to request the NSACF serving the network slice associated with the PDN connection_1 and supporting the control of the number of UEs accessing the network slice. As an example, the seventh request message_1 may carry S-NSSAI and NSACF service capability indication information used to identify the network slice, and the NSACF service capability indication information is used to indicate that the NSACF requested by SMF+PGW-C_1 supports interconnection The number of UEs entering the network slice is controlled. For convenience of description, the NSACF is referred to as NSACF_1 hereinafter.

Step 805, the NRF sends a seventh response message_1 to the SMF+PGW-C_1 according to the seventh request message_1.

Wherein, the seventh response message_1 carries relevant information of NSACF_1. The relevant information of NSACF_1 may include the address of NSACF_1. The NSACF_1 is the NSACF serving the network slice identified by the S-NSSAI carried in the seventh request message_1, and the NSACF_1 supports the control of the number of UEs accessing the network slice identified by the S-NSSAI.

In a possible implementation manner, NRF returns Nnrf_NFDiscovery response to SMF+PGW-C_1, carrying information of NSACF_1, such as address information of NSACF_1.

Optionally, SMF+PGW-C_1 saves the information of NSACF_1 returned by NRF in the context.

Step 806, SMF+PGW-C_1 determines NSACF_1 according to the seventh response message_1, and sends the eighth request message_1 to the NSACF_1.

Wherein, the eighth request message_1 may carry UE ID, update flag_1, and S-NSSAI. The UE ID may be determined by SMF+PGW-C_1 according to the session creation request message. For example, the session creation request message carries the UE ID. Exemplarily, the UE ID may be the IMSI of the UE. The update flag_1 is used to indicate to increase the number of UEs corresponding to the network slice identified by the S-NSSAI, for example, add 1 to the number of UEs.

Optionally, the eighth request message_1 may also carry information related to session_1. The information related to session_1 may include the identifier of SMF+PGW-C_1 and/or the identifier of session_1, the identifier of SMF+PGW-C_1 may be the ID of SMF+PGW-C_1, and the identifier of session_1 is used to identify the Session_1, such as PDU session ID_1, where PDU session ID_1 may be included in the create session request message.

A possible implementation, SMF+PGW-C_1 sends Nnsacf_NumberOfUEsPerSliceAvailabilityCheckAndUpdate request to NSACF_1.

A possible implementation, optional, when SMF+PGW-C_1 judges that PDN connection_1 is the first PDN connection associated with S-NSSAI served by SMF+PGW-C_1 for the UE, then SMF+PGW- C_1 performs steps 806-808. Specifically, SMF+PGW-C_1 can judge whether PDN connection_1 is the first PDN connection established by the UE and associated with the network slice according to the context information stored by SMF+PGW-C_1, for example, SMF+PGW-C_1 saves The context information of all PDN connections currently established by the UE, if there are other PDN connections in the context that are the same as the network slice associated with the PDN connection_1, it means that the PDN connection_1 is not the first one initiated by the UE to be established with the network slice The PDN connection associated with the network slice. For example, the UE has currently established PDN connection_1', which is also served by SMF+PGW-C_1, and the network slice associated with PDN connection_1' is the same as the network slice associated with PDN connection_1. It should be noted that the APN corresponding to the PDN connection_1' may be different from the APN corresponding to the PDN connection_1. If there is no other PDN connection in the context that is the same as the network slice associated with the PDN connection_1, it means that the PDN connection_1 is the first one associated with the network slice initiated by the UE and is established by SMF+PGW-C_1 The PDN connection of the service.

If SMF+PGW-C_1 judges that PDN connection_1 is not the first PDN connection associated with S-NSSAI served by SMF+PGW-C_1 for the UE according to the above description, for example, the UE is currently on SMF+PGW-C_1 PDN connection_1' is established and the PDN connection_1' is associated with the same S-NSSAI, then the number of UEs corresponding to the network slice identified by the S-NSSAI execution control process has been executed in the establishment process of PDN connection_1' , since the current PDN connection_1 is established by the same UE and is associated with the same network slice, SMF+PGW-C_1 does not need to request NSACF_1 to control the number of users of the network slice, that is, steps 806-808 may not be executed .

It should be noted that, during the process of establishing a PDN connection, SMF+PGW-C_1 can store the information of the PDN connection in the local context. During the process of releasing the PDN connection, SMF+PGW-C_1 can delete the information of the PDN connection in the local context.

Step 807, NSACF_1 performs admission control on the network slice according to the eighth request message_1.

In a possible implementation, NSACF_1 performs admission control on the network slice including performing admission control on the number of UEs on the network slice, which can also be called counting the number of UEs, so as to ensure the sum of the number of UEs currently connected to the network slice Do not exceed the maximum number/number of terminal devices allowed to be accessed by the network slice. NSACF_1 may store the number of UEs that have currently accessed the network slice, and the identifiers in the UE identifier list are used to identify the UEs that have currently accessed the network slice. NSACF_1 can also configure the maximum number of UEs allowed to be accessed by the network slice, that is, NSACF_1 can configure the maximum number of users allowed to be accessed by the network slice.

Specifically, if the current quota of the network slice identified by the S-NSSAI is still available (that is, the number of UEs currently accessing the network slice identified by the S-NSSAI does not exceed the maximum number), and the UE ID is not stored in the S-NSSAI The network slice identified by the NSSAI has already been included in the UE identification list, and the UE can access the network slice identified by the S-NSSAI. In this case, NSACF_1 increases the number of UEs in the network slice. The UE number of the identified network slice is increased by 1), and the UE ID is added to the UE identification list that the network slice has accessed, so as to save the corresponding relationship between the UE ID and the S-NSSAI. If the current quota of the network slice identified by the S-NSSAI is still available, and the UE ID has been stored in the list of UE identifiers that have been accessed by the network slice identified by the S-NSSAI, it means that the UE has accessed the S-NSSAI The identified network slice, in this case, NSACF_1 does not change the number of UEs of the network slice. If the current quota of the network slice identified by the S-NSSAI is not available (that is, the number of UEs currently accessing the network slice identified by the S-NSSAI exceeds the maximum number), the UE cannot access the network slice identified by the S-NSSAI, In this case, NSACF_1 also does not change the number of UEs in the network slice.

In the process shown in Figure 8, NSACF_1 will increase the number of UEs in the network slice, and add the UE ID to the list of UE identifiers that have been accessed by the network slice, thereby saving the correspondence between the UE ID and the S-NSSAI.

Optionally, if the information related to session_1 is carried in the eighth request message_1, NSACF_1 may also save the information related to session_1. For example, configuration information or policy information is stored on NSACF_1: the configuration information or policy information is used to instruct NSACF_1 to store information related to session_1.

Step 808, NSACF_1 sends an eighth response message_1 to SMF+PGW-C_1.

Wherein, the eighth response message_1 is used to indicate the result of performing admission control on the network slice. The result may include: performing admission control on the network slice successfully or failing to perform admission control on the network slice. If the execution of admission control on the network slice is successful, it means that the counting of the number of UEs is successful, and if the execution of admission control on the network slice fails, it means that the counting of the number of UEs is failed, then the eighth response message_1 can also carry the failure reason value , the failure cause value is used to indicate that the number of UEs connected to the network slice has reached the maximum value. In this example, the eighth response message_1 may indicate that admission control on the network slice is performed successfully.

In a possible implementation manner, NSACF_1 sends Nnsacf_NumberOfUEsPerSliceAvailabilityCheckAndUpdate response to SMF+PGW-C_1, and NSACF_1 carries the result of performing admission control on network slices in the sent message.

Step 809, SMF+PGW-C_1 sends a fifth request message_1 to NRF.

Wherein, the fifth request message_1 is used to request the NSACF serving the network slice associated with the PDN connection_1 and supporting the control of the number of sessions established on the network slice. As an example, the fifth request message_1 may carry NS-NSSAI and NSACF service capability indication information used to identify the network slice, and the NSACF service capability indication information is used to indicate that the NSACF requested by SMF+PGW-C_1 supports support for The number of sessions established on the network slice identified by the S-NSSAI is controlled. For convenience of description, the NSACF is referred to as NSACF_2 hereinafter.

Step 810, the NRF sends a fifth response message_1 to the SMF+PGW-C_1 according to the fifth request message_1.

Wherein, the fifth response message_1 carries relevant information of NSACF_2. The related information of NSACF_2 may include the address of NSACF_2. The NSACF_2 is the NSACF serving the network slice identified by the S-NSSAI carried in the fifth request message_1, and the NSACF_2 supports the control of the number of sessions established on the network slice identified by the S-NSSAI.

In a possible implementation, NRF returns Nnrf_NFDiscovery response to SMF+PGW-C_1, carrying NSACF_2 information, such as NSACF_2 address information.

Optionally, SMF+PGW-C_1 saves the information of NSACF_2 returned by NRF in the context.

It should be noted that this application does not limit the order in which SMF+PGW-C_1 requests NRF to discover NSACF_1 and NSACF_2. A possible implementation, as shown in Figure 8, SMF+PGW-C_1 can first request the NRF to discover NSACF_1 and after determining that the count of the number of UEs is successful, then request the NRF to discover NSACF_2, that is, SMF+PGW-C_1 respectively send NRF sends two request messages to obtain the information of NSACF_1 and the information of NSACF_2. In another possible implementation manner, SMF+PGW-C_1 triggers NRF to discover NSACF_1 and NSACF_2 through a request message, and NRF returns the information of NSACF_1 and the information of NSACF_2 in a response message at the same time.

Step 811, SMF+PGW-C_1 determines NSACF_2 according to the fifth response message_1, and sends a sixth request message_1 to the NSACF_2.

Wherein, the sixth request message_1 may carry update flag_2, S-NSSAI, and information related to session_1. The update flag_2 is used to indicate to increase the number of sessions corresponding to the network slice identified by the S-NSSAI, for example, add 1 to the number of sessions. The information related to session_1 may include the identifier of SMF+PGW-C_1 and/or the identifier of session_1, the identifier of SMF+PGW-C_1 may be the ID of SMF+PGW-C_1, and the identifier of session_1 is used to identify the Session_1, such as PDU session ID_1, where PDU session ID_1 may be included in the create session request message.

Optionally, the sixth request message_1 may also carry a UE ID, where the UE ID may be determined by SMF+PGW-C_1 according to the session creation request message or context.

A possible implementation, SMF+PGW-C_1 sends Nnsacf_NumberOfPDUsPerSliceAvailabilityCheckAndUpdate request to NSACF_2.

Step 812, NSACF_2 performs admission control on the network slice according to the sixth request message_1.

In a possible implementation, NSACF_2 performs admission control on the network slice, including performing admission control on the number of sessions on the network slice, which can also be called counting the number of sessions, so as to ensure that the total number of sessions currently established in the network slice does not exceed The maximum number/number of sessions allowed to be established for this network slice. NSACF_2 can save the number of sessions currently established in the network slice. NSACF_2 can also configure the maximum number of sessions allowed by the network slice, that is, NSACF_2 can configure the maximum number of users allowed to access the network slice and the maximum number of sessions allowed by the network slice.

Specifically, if the current quota of the network slice identified by the S-NSSAI is still available (that is, the number of sessions currently established by the network slice identified by the S-NSSAI does not exceed the maximum number), the UE can use the network slice identified by the S-NSSAI A new session is established in the slice. In this case, NSACF_2 increases the number of sessions in the network slice (for example, the number of sessions accessing the network slice identified by S-NSSAI plus 1), and saves session_1 related information and S-NSSAI Correspondence of NSSAI. If the current quota of the network slice identified by the S-NSSAI is not available (that is, the number of sessions currently established by the network slice identified by the S-NSSAI exceeds the maximum number), the UE cannot establish a new session in the network slice identified by the S-NSSAI. sessions, in which case NSACF_2 does not change the quota for the number of sessions available for the network slice.

In the process shown in FIG. 8 , NSACF_2 will increase the number of sessions of the network slice, and save the corresponding relationship between session_1 related information and S-NSSAI. If the UE ID is carried in the sixth request message_1, NSACF_2 can save the correspondence between UE ID, S-NSSAI and session_1 related information

Step 813, NSACF_2 sends a sixth response message_1 to SMF+PGW-C_1.

Wherein, the sixth response message_1 is used for the result of performing admission control on the network slice. The result may include: performing admission control on the network slice successfully or failing to perform admission control on the network slice. If the admission control on the network slice is successfully performed, it means that the counting of the number of sessions is performed successfully, and if the admission control on the network slice fails, it means that the counting of the number of sessions is failed, then the sixth response message_1 can also carry the failure reason value , the failure reason value is used to indicate that the number of sessions established on the network slice has reached the maximum value. In the process shown in FIG. 8 , the sixth response message_1 may indicate that admission control is successfully performed on the network slice.

In a possible implementation, NSACF_2 sends Nnsacf_NumberOfPDUsPerSliceAvailabilityCheckAndUpdate response to SMF+PGW-C_1, and NSACF_2 carries the result of performing admission control on network slices in the sent message.

Step 814, SMF+PGW-C_1 sends a ninth request message_1 to NSACF_1.

Wherein, the reason for SMF+PGW-C_1 to execute step 814 may be any of the following:

1) The eighth request message_1 does not carry information related to session_1;

2) The eighth request message_1 carries information related to the session_1, but the sixth response message_1 indicates that counting the number of sessions fails.

If SMF+PGW-C_1 executes step 814 because of the above reason 1), the ninth request message_1 may have the following two situations:

a) If the sixth response message_1 indicates that the counting of the number of sessions is successful, then the ninth request message_1 may carry information related to UE ID, S-NSSAI, and session_1. The UE ID may be contextually determined. Optionally, the ninth request message_1 may also carry first indication information, which is used to instruct NSACF_1 to store information related to session_1, that is, NSACF_1 stores information related to session_1; it can be understood that if NSACF-2 returns The result is that the number of sessions is successfully counted, indicating that the current network resources allow the UE to establish a PDN connection on the network slice, and then NSACF_1 needs to store information related to the session_1. At this time, the ninth request message_1 may correspond to the second request message involved in step 402 above.

b) If the sixth response message_1 indicates that the counting of the number of sessions fails, then the ninth request message_1 may carry UE ID, S-NSSAI, and first indication information (such as update flag_1). The UE ID may be contextually determined. The first indication information indicates to reduce the number of UEs corresponding to the network slice identified by the S-NSSAI, for example, the number of UEs is reduced by 1.

If SMF+PGW-C_1 performs step 814 because of the above reason 2), then the ninth request message_1 may carry UE ID, S-NSSAI, and first indication information (such as update flag_1). The UE ID may be contextually determined. The first indication information indicates to reduce the number of UEs corresponding to the network slice identified by the S-NSSAI, for example, the number of UEs is reduced by 1. It can be understood that if the result returned by NSACF-2 is that the counting of the number of sessions fails, it means that the current network resources do not allow the UE to establish a PDN connection on the network slice. into the network slice. At this time, the ninth request message_1 may correspond to the first request message in FIG. 4 above.

Step 815, NSACF_1 determines whether to store information related to session_1 according to the ninth request message_1.

In a possible implementation, if the ninth request message_1 contains information related to session_1, NSACF_1 can maintain the number of UEs corresponding to the network slice identified by S-NSSAI, and save information related to session_1 . If the first indication information in the ninth request message_1 indicates to reduce the number of UEs, then NSACF_1 judges whether there are other sessions in the current UE, because the context stored in NSACF_1 only contains _1), NSACF_1 may reduce the number of UEs corresponding to the network slice identified by the S-NSSAI, and at the same time, NSACF_1 deletes information related to session_1.

Step 816, NSACF_1 sends a ninth response message_1 to SMF+PGW-C_1.

Wherein, if the ninth request message_1 contains information related to session_1, then the ninth response message_1 is used to indicate that the session information is stored successfully; if the ninth request message_1 is used to request the access network slice The number of UEs performing admission control (for example, indicating to reduce the number of UEs corresponding to the network slice identified by S-NSSAI), then the ninth response message_1 is used to indicate the result of performing admission control on the number of UEs in the network slice.

It should be noted that, if in step 807, NSACF_1 saves the information related to session_1, when the sixth response message_1 indicates that the counting of the number of sessions is successful, steps 814-816 may not be executed.

Step 817, execute the rest of the process of establishing the PDN connection.

Since Example 3 takes the establishment of two PDN connections as an example, the first PDN connection is established at this time, so NSACF_1 will increase the number of UEs corresponding to the network slice, and save UE ID, S-NSSAI and session_1 related information. Corresponding relationship, NSACF_2 will increase the number of sessions corresponding to the network slice and save the corresponding relationship between S-NSSAI and session_1 related information. If the UE ID is carried in the sixth request message_1, NSACF_2 may save the correspondence between the UE ID, S-NSSAI and session_1-related information.

So far, the establishment of PDN connection_1 is completed, and NSACF_1 saves the correspondence between UE ID, S-NSSAI, and information related to session_1.

Fig. 9 is another example of the network slice admission control method provided by the present application. SMF+PGW-C_1 in Figure 9 may correspond to the second network element above, NSACF_1 may correspond to the first network element in Figure 4 above, and NSACF_2 may correspond to the third network involved in steps 402-403 above Yuan.

According to the process shown in Figure 8, the UE has successfully established PDN connection_1, and PDN connection_1 is served by SMF+PGW-C_1, and the UE can continue to initiate the PDN connection establishment process to the network. For the convenience of description, the following will serve PDN The SMF+PGW-C for connection_2 is called SMF+PGW-C_2.

In step 901, the UE initiates a PDN connection establishment procedure.

Step 902, SMF+PGW-C_2 determines the network slice associated with the PDN connection.

In step 903, SMF+PGW-C_2 determines whether the network slice needs to execute the NSAC process according to the configuration information.

The implementation manner of steps 901-903 is the same as that of steps 601-603, and reference may be made to the description of steps 601-603, which will not be repeated here.

If SMF+PGW-C_2 determines that the network slice needs to execute the NSAC process, it may continue to execute steps 904-916. If SMF+PGW-C_2 determines that the network slice does not need to execute the NSAC process, steps 904-916 may be skipped, and step 917 may be directly executed.

Step 904, SMF+PGW-C_2 sends a seventh request message_2 to NRF.

Wherein, the seventh request message_2 is used to request the NSACF serving the network slice associated with the PDN connection_2 and supporting the control of the number of UEs accessing the network slice. As an example, the seventh request message_2 may carry S-NSSAI and NSACF service capability indication information used to identify the network slice, and the NSACF service capability indication information is used to indicate that the NSACF requested by SMF+PGW-C_2 supports interconnection The number of UEs entering the network slice is controlled. For convenience of description, the NSACF is referred to as NSACF_1 hereinafter.

In step 905, the NRF sends a seventh response message_2 to the SMF+PGW-C_2 according to the seventh request message_2.

Wherein, the seventh response message_2 carries relevant information of NSACF_1. The NSACF_1 is the NSACF serving the network slice identified by the S-NSSAI carried in the seventh request message_2, and the NSACF_1 supports the control of the number of UEs accessing the network slice identified by the S-NSSAI. The NSACF in step 905 is the same as the NSACF in step 805 .

Optionally, SMF+PGW-C_2 saves the information of NSACF_1 returned by NRF in the context.

Step 906, SMF+PGW-C_2 determines NSACF_1 according to the seventh response message_2, and sends the eighth request message_2 to the NSACF_1.

Wherein, the eighth request message_2 may carry UE ID, update flag_1, and S-NSSAI. The UE ID may be determined by SMF+PGW-C_2 according to the session creation request message. For example, the session creation request message carries the UE ID. Exemplarily, the UE ID may be the IMSI of the UE. The update flag_1 is used to indicate to increase the number of UEs corresponding to the network slice identified by the S-NSSAI, for example, add 1 to the number of UEs.

Optionally, the eighth request message_2 may also carry information related to session_2. The information related to session_2 may include the identifier of SMF+PGW-C_2 and/or the identifier of session_2, the identifier of SMF+PGW-C_2 may be the ID of SMF+PGW-C_2, and the identifier of session_2 is used to identify the Session_2, such as PDU session ID_2, where PDU session ID_2 may be included in the create session request message.

A possible implementation, SMF+PGW-C_2 sends Nnsacf_NumberOfUEsPerSliceAvailabilityCheckAndUpdate request to NSACF_1.

A possible implementation, optional, when SMF+PGW-C_2 judges that PDN connection_2 is the first PDN connection associated with S-NSSAI served by SMF+PGW-C_2 for the UE, then SMF+PGW- C_2 performs steps 906-908. Specifically, SMF+PGW-C_2 can judge whether PDN connection_2 is the first PDN connection established by the UE and associated with the network slice according to the context information stored by SMF+PGW-C_2, for example, SMF+PGW-C_2 saves The context information of all PDN connections currently established by the UE, if there are other PDN connections in the context with the same network slice associated with the PDN connection_2, it means that the PDN connection_2 is not the first one initiated by the UE to be established with the network slice The PDN connection associated with the network slice. For example, the UE has currently established PDN Connection_2', which is also served by SMF+PGW-C_2, and the network slice associated with PDN Connection_2' is the same as the network slice associated with PDN Connection_2. It should be noted that the APN corresponding to the PDN connection_2' may be different from the APN corresponding to the PDN connection_2. If there is no other PDN connection in the context stored by SMF+PGW-C_2 that is the same as the network slice associated with the PDN connection_2, it means that the PDN connection_2 is the first network slice associated with the network slice initiated by the UE. And the PDN connection served by SMF+PGW-C_2.

If SMF+PGW-C_2 judges that PDN connection_2 is not the first PDN connection associated with S-NSSAI served by SMF+PGW-C_2 for the UE according to the above description, for example, the UE has currently established PDN connection_2' And the PDN connection_2' is associated with the same S-NSSAI, then the execution control process of the number of UEs corresponding to the network slice identified by the S-NSSAI has been executed in the establishment process of the PDN connection_2', because the current PDN connection_2 If it is established by the same UE and associated with the same network slice, SMF+PGW-C_2 does not need to request NSACF_1 to control the number of users of the network slice, that is, steps 906-908 may not be executed.

It should be noted that during the process of establishing the PDN connection, the SMF+PGW-C_2 can store the information of the PDN connection in the local context. During the process of releasing the PDN connection, SMF+PGW-C_2 can delete the information of the PDN connection in the local context.

Step 907, NSACF_1 performs admission control on the network slice according to the eighth request message_2.

In the process shown in Figure 9, NSACF_1 judges that the UE has accessed the network slice identified by the S-NSSAI according to the correspondence between the UE ID and the S-NSSAI stored in the context information. In this case, NSACF_1 does not need to The number of UEs corresponding to the network slice is counted, that is, the number of UEs in the network slice remains unchanged.

Optionally, if the information related to session_2 is carried in the eighth request message_2, NSACF_1 may also save the information related to session_2. For example, configuration information or policy information is stored on NSACF_1: the configuration information or policy information is used to instruct NSACF_1 to store information related to session_2.

Step 908, NSACF_1 sends an eighth response message_2 to SMF+PGW-C_2.

Wherein, the eighth response message_2 is used to indicate the result of performing admission control on the network slice. The result may include: performing admission control on the network slice successfully or failing to perform admission control on the network slice. If the execution of admission control on the network slice is successful, it means that the counting of the number of UEs is performed successfully, and if the execution of admission control on the network slice fails, it means that the counting of the number of UEs is failed, then the eighth response message_2 can also carry the failure reason value , the failure cause value is used to indicate that the number of UEs connected to the network slice has reached the maximum value. In this example, the eighth response message_2 may indicate that admission control on the network slice is performed successfully.

In a possible implementation manner, NSACF_1 sends Nnsacf_NumberOfUEsPerSliceAvailabilityCheckAndUpdate response to SMF+PGW-C_2, and NSACF_1 carries the result of performing admission control on network slices in the sent message.

Step 909, if the eighth response message_2 indicates that the counting of the number of UEs is successful, SMF+PGW-C_2 sends a fifth request message_2 to the NRF.

Wherein, the fifth request message_2 is used to request the NSACF serving the network slice associated with the PDN connection_2 and supporting the control of the number of sessions established on the network slice. As an example, the fifth request message_2 may carry NS-NSSAI and NSACF service capability indication information used to identify the network slice, and the NSACF service capability indication information is used to indicate that the NSACF requested by SMF+PGW-C_2 supports support for The number of sessions established on the network slice identified by the S-NSSAI is controlled. For convenience of description, the NSACF is referred to as NSACF_2 hereinafter.

Step 910, the NRF sends a fifth response message_2 to the SMF+PGW-C_2 according to the fifth request message_2.

Wherein, the fifth response message_2 carries relevant information of NSACF_2. The related information of NSACF_2 may include the address of NSACF_2. The NSACF_2 is the NSACF serving the network slice identified by the S-NSSAI carried in the fifth request message_2, and the NSACF_2 supports the control of the number of sessions established on the network slice identified by the S-NSSAI. The NSACF in step 910 is the same as the NSACF in step 810.

In a possible implementation manner, NRF returns Nnrf_NFDiscovery response to SMF+PGW-C_2, carrying information of NSACF_2, such as address information of NSACF_2.

Optionally, SMF+PGW-C_2 saves the information of NSACF_2 returned by NRF in the context.

It should be noted that this application does not limit the order in which SMF+PGW-C_2 requests NRF to discover NSACF_1 and NSACF_2. A possible implementation, as shown in Figure 9, SMF+PGW-C_2 can first request the NRF to discover NSACF_1 and after determining that the count of the number of UEs is successful, then request the NRF to discover NSACF_2, that is, SMF+PGW-C_2 respectively send NRF sends two request messages to obtain the information of NSACF_1 and the information of NSACF_2. In another possible implementation, SMF+PGW-C_2 triggers NRF to discover NSACF_1 and NSACF_2 through a request message, and NRF returns the information of NSACF_1 and NSACF_2 in a response message at the same time.

Step 911, SMF+PGW-C_2 determines NSACF_2 according to the fifth response message_2, and sends a sixth request message_2 to the NSACF_2.

Wherein, the sixth request message_2 may carry update flag_2, S-NSSAI, and information related to session_2. The update flag_2 is used to indicate to increase the number of sessions corresponding to the network slice identified by the S-NSSAI, for example, add 1 to the number of sessions. The information related to session_2 may include the identifier of SMF+PGW-C_2 and/or the identifier of session_2, the identifier of SMF+PGW-C_2 may be the ID of SMF+PGW-C_2, and the identifier of session_2 is used to identify the Session_2, such as PDU session ID_2, where PDU session ID_2 may be included in the create session request message.

Optionally, the sixth request message_2 may also carry a UE ID, where the UE ID may be determined by SMF+PGW-C_2 according to the session creation request message or context.

A possible implementation, SMF+PGW-C_2 sends Nnsacf_NumberOfPDUsPerSliceAvailabilityCheckAndUpdate request to NSACF_2.

Step 912, NSACF_2 performs admission control on the network slice according to the sixth request message_2.

In the process shown in FIG. 9 , NSACF_2 will increase the number of sessions of the network slice, and save the corresponding relationship between session_2 related information and S-NSSAI. If the UE ID is carried in the sixth request message_2, NSACF_2 may save the correspondence between the UE ID, S-NSSAI and session_2 related information.

Step 913, NSACF_2 sends a sixth response message_2 to SMF+PGW-C_2.

Wherein, the sixth response message_2 is used to indicate the result of performing admission control on the network slice. The result may include: performing admission control on the network slice successfully or failing to perform admission control on the network slice. If the execution of admission control on the network slice is successful, it means that the counting of the number of execution sessions is successful; if the execution of admission control on the network slice fails, it means that the counting of the number of execution sessions fails, then the sixth response message_2 can also carry the failure reason value , the failure reason value is used to indicate that the number of sessions established on the network slice has reached the maximum value. In the process shown in FIG. 9 , the sixth response message_2 may indicate that the admission control on the network slice is successfully performed.

In a possible implementation manner, NSACF_2 sends Nnsacf_NumberOfPDUsPerSliceAvailabilityCheckAndUpdate response to SMF+PGW-C_2, and NSACF_2 carries the result of performing admission control on network slices in the sent message.

Step 914, SMF+PGW-C_2 sends a ninth request message_2 to NSACF_1.

Similarly, the reason for SMF+PGW-C_2 to execute step 914 may be any of the following:

1) The eighth request message_2 does not carry information related to session_2;

2) The eighth request message_2 carries information related to session_2, but the sixth response message_2 indicates that counting the number of sessions fails.

If the reason why SMF+PGW-C_2 executes step 914 is the above reason 1), the ninth request message_2 may have the following two situations:

a) If the sixth response message_2 indicates that the counting of the number of sessions is successful, then the ninth request message_2 may carry information related to UE ID, S-NSSAI, and session_2. The UE ID may be contextually determined. Optionally, the ninth request message_2 may also carry first indication information, which is used to instruct NSACF_1 to store information related to session_2, that is, NSACF_1 stores information related to session_2; it can be understood that if NSACF-2 returns The result is that the number of sessions is successfully counted, indicating that the current network resources allow the UE to establish a PDN connection on the network slice, and then NSACF_1 needs to store information related to the session_2. At this time, the ninth request message_2 may correspond to the second request message involved in step 402 above.

b) If the sixth response message_2 indicates that the counting of the number of sessions fails, then the ninth request message_2 may carry UE ID, S-NSSAI, and first indication information (such as update flag_1). The UE ID may be contextually determined. The first indication information indicates to reduce the number of UEs corresponding to the network slice identified by the S-NSSAI, for example, the number of UEs is reduced by 1.

If the reason why SMF+PGW-C_2 performs step 914 is the above-mentioned reason 2), then the ninth request message_2 may carry UE ID, S-NSSAI, and first indication information (such as update flag_1). The UE ID may be contextually determined. The first indication information indicates to reduce the number of UEs corresponding to the network slice identified by the S-NSSAI, for example, the number of UEs is reduced by 1. It can be understood that if the result returned by NSACF-2 is that the counting of the number of sessions fails, it means that the current network resources do not allow the UE to establish a PDN connection on the network slice. into the network slice. At this time, the ninth request message_2 may correspond to the first request message in FIG. 4 above.

Step 915, NSACF_1 determines whether to store information related to session_2 according to the ninth request message_2.

In a possible implementation, if the ninth request message_2 contains information related to session_2, NSACF_1 can maintain the number of UEs corresponding to the network slice identified by S-NSSAI, and save information related to session_2 . If the first indication information in the ninth request message_2 indicates to reduce the number of UEs, then NSACF_1 judges whether there are other sessions in the current UE. Since the context stored by NSACF_1 includes information related to session_1 and session_2, Then NSACF_1 cannot reduce the number of UEs corresponding to the network slice identified by the S-NSSAI. At the same time, NSACF_1 deletes the information related to session_2, that is, deletes the information related to session_2 and retains the information related to session_1.

In the process shown in FIG. 9 , NSACF_1 maintains the number of UEs corresponding to the network slice identified by S-NSSAI, and decides whether to save session_2-related information according to the parameters carried in the ninth request message_2.

Step 916, NSACF_1 sends a ninth response message_2 to SMF+PGW-C_2.

Wherein, if the ninth request message_2 contains UE session-related information, the ninth response message_2 is used to indicate that the session information is stored successfully, and if the ninth request message_2 is used to execute admission control, then the ninth response message_2 is used to indicate the result of performing admission control on the number of UEs in the network slice.

It should be noted that, if in step 907, NSACF_1 saves information related to session_2, and when the sixth response message_2 indicates that the counting of the number of sessions is successful, steps 914-916 may not be executed.

Step 917, execute the remaining procedures of PDN connection establishment.

So far, the establishment of PDN connection_2 is completed, and NSACF_1 saves the corresponding relationship between UE ID, S-NSSAI, information related to session_1 and information related to session_2.

It can be seen from the above that for the determination process of the number of UEs and the number of sessions triggered by the establishment of a PDN connection, in Example 3, SMF+PGW-C first interacts with NSACF_1 (NSACF responsible for controlling the number of UEs) to trigger the update of the number of UEs, if If the number of UEs is not exceeded, SMF+PGW-C interacts with NSACF_2 (NSACF responsible for controlling the number of sessions) to trigger an update of the number of sessions. When the number of sessions is successfully updated, SMF+PGW-C needs to interact with NSACF_1 again to trigger NSACF_1 to maintain the number of sessions so that NSACF_1 can subsequently determine whether to reduce the number of UEs. In this way, network slice admission control in interworking scenarios can be realized.

It should be noted that both Figure 8 and Figure 9 take SMF+PGW-C as an example to first interact with the NSACF responsible for controlling the number of UEs, then interact with the NSACF responsible for controlling the number of sessions, and finally interact with the NSACF responsible for controlling the number of UEs. However, the embodiments of the present application are not limited thereto. For example, SMF+PGW-C may first interact with the NSACF responsible for controlling the number of sessions, then interact with the NSACF responsible for controlling the number of UEs, and finally interact with the NSACF responsible for controlling the number of sessions .

Example 4

In Example 4, the UE initiates the release process of multiple PDN connections respectively, and multiple PDN connections are associated with the same network slice. The NSACF responsible for the quota management of the number of UEs in the network slice and the quota management of the number of sessions in the network slice The NSACF is different. FIG. 10 takes the UE establishing two PDN connections as an example. Assuming that according to example 3, the UE has established two PDN connections (PDN connection_1 and PDN connection_2) for the same network slice, at a certain moment, the UE initiates a PDN connection release procedure to the network.

Fig. 10 is another example of the network slice admission control method provided by this application. SMF+PGW-C_1 and SMF+PGW-C_2 in Figure 10 may correspond to the second network element in Figure 4 above, NSACF_1 may correspond to the first network element in Figure 4 above, and NSACF_2 may correspond to the above The third network element involved in steps 402-403.

In step 1001, the UE initiates a PDN connection_1 release procedure.

The implementation manner of step 1001 is the same as that of step 701, and reference may be made to the description of step 701, which will not be repeated here.

Step 1002, SMF+PGW-C_1 sends a sixth request message_3 to NSACF_2.

Wherein, the sixth request message_3 may carry information related to S-NSSAI, update flag_2, and session_1. The update flag_2 is used to indicate that the number of sessions corresponding to the network slice identified by the S-NSSAI is reduced, for example, the number of sessions is reduced by 1. The information related to session_1 may include the identifier of SMF+PGW-C_1 and/or the identifier of session_1, the identifier of SMF+PGW-C_1 may be the ID of SMF+PGW-C_1, and the identifier of session_1 is used to identify the Session_1, such as PDU session ID_1, where PDU session ID_1 may be included in the create session request message.

Optionally, the sixth request message_3 may also carry a UE ID, where the UE ID may be determined by SMF+PGW-C_1 according to the delete session request message, for example, the UE ID may be the IMSI of the UE.

In a possible implementation manner, if SMF+PGW-C_1 saves the information of NSACF_2 in the context, then SMF+PGW-C_1 can directly determine NSACF_2 according to the information of NSACF_2.

As another implementation, if SMF+PGW-C_1 does not save the information of NSACF_2 in the context, then SMF+PGW-C_1 may request NRF to discover NSACF_2. For this method, reference may be made to the above-mentioned step 809 and step 810 .

Step 1003, NSACF_2 performs admission control on the network slice according to the sixth request message_3.

In a possible implementation manner, NSACF_2 performing admission control on the network slice includes performing admission control on the number of sessions on the network slice, which may also be referred to as counting the number of sessions performed. Specifically, NSACF_2 reduces the number of sessions corresponding to the network slice identified by S-NSSAI (for example, NSACF_2 reduces the number of sessions established in the network slice identified by S-NSSAI by 1), and deletes the SMF+PGW- Identification of C ID_1.

Step 1004, NSACF_2 sends a sixth response message_3 to SMF+PGW-C_1.

Wherein, the sixth response message_3 is used to indicate the result of performing admission control on the network slice. The result may include: performing admission control on the network slice successfully or failing to perform admission control on the network slice. If the admission control is successfully performed on the network slice, it means that the counting of the number of sessions is performed successfully, and if the admission control on the network slice fails, it means that the counting of the number of sessions is executed failed. In step 1004, the sixth response message_3 may indicate that admission control on the network slice is performed successfully.

Step 1005, SMF+PGW-C_1 sends a first request message_1 to NSACF_1.

Wherein, the first request message_1 may carry information related to UE ID, S-NSSAI, update flag_1, and session_1. The UE ID can be determined by SMF+PGW-C_1 according to the delete session request message or context. The update flag_1 is used to indicate to reduce the number of UEs corresponding to the network slice identified by the S-NSSAI, for example, the number of UEs is reduced by 1. The information related to session_1 may include the identifier of SMF+PGW-C_1 and/or the identifier of session_1, the identifier of SMF+PGW-C_1 may be the ID of SMF+PGW-C_1, and the identifier of session_1 is used to identify the Session_1, such as PDU session ID_1, where PDU session ID_1 may be included in the create session request message.

In a possible implementation manner, if SMF+PGW-C_1 saves the information of NSACF_1 in the context, then SMF+PGW-C_1 can directly determine NSACF_1 according to the information of NSACF_1.

As another implementation, if SMF+PGW-C_1 does not save the information of NSACF_1 in the context, then SMF+PGW-C_1 may request NRF to discover NSACF_1. For this method, reference may be made to the above step 804 and step 805 .

A possible implementation, SMF+PGW-C_1 sends Nnsacf_NumberOfPDUsPerSliceAvailabilityCheckAndUpdate request to NSACF_1.

A possible implementation, optional, when SMF+PGW-C_1 determines that PDN connection_1 is the only PDN connection associated with S-NSSAI that SMF+PGW-C_1 serves for the UE, then SMF+PGW-C_1 Execute steps 1005-1007. Specifically, SMF+PGW-C_1 can judge whether PDN connection_1 is the only PDN connection associated with S-NSSAI according to the context information, for example, SMF+PGW-C_1 saves the context information of all PDN connections currently established by the UE , if there is another PDN connection in the context that is the same as the network slice associated with the PDN connection_1, it means that after the PDN connection_1 is released, there are other PDN connections. For example, the UE currently has PDN connection_1', which is also served by SMF+PGW-C_1, and the network slice associated with PDN connection_1' is the same as the network slice associated with PDN connection_1. It should be noted that the APN corresponding to the PDN connection_1' may be different from the APN corresponding to the PDN connection_1. If there is no other PDN connection in the context that is the same as the network slice associated with the PDN connection_1, it means that the PDN connection_1 is the only one associated with the network slice initiated by the UE and served by SMF+PGW-C_1 PDN connections.

If SMF+PGW-C_1 judges that PDN connection_1 is not the only PDN connection associated with S-NSSAI released by the UE according to the above description, for example, the UE has currently established PDN connection_1' and the PDN connection_1' Associated with the same S-NSSAI, then the number of UEs corresponding to the network slice identified by the S-NSSAI does not need to be executed. Since the current UE still has other PDN connections associated with the same network slice, SMF+PGW-C_1 does not need to request NSACF_1 controls the number of users of the network slice, that is, steps 1005-1007 may not be executed.

Step 1006, NSACF_1 performs admission control on the network slice according to the first request message_1.

In a possible implementation manner, performing admission control on the network slice by NSACF_1 includes performing admission control on the number of UEs on the network slice, which may also be referred to as performing counting on the number of UEs. Specifically, NSACF_1 judges whether the current UE has a session other than session_1, if the session information related to the UE in the context stored by NSACF_1 only contains information related to session_1 (that is, NSACF_1 only stores the information of PDN connection_1 information), then NSACF_1 may reduce the number of UEs corresponding to the network slice identified by the S-NSSAI, and at the same time, NSACF_1 deletes information related to session_1. If the session information related to the UE in the context stored by NSACF_1 also includes session-related information other than session-1-related information (for example, session-2-related information), then NSACF_1 deletes session-1-related information, However, the number of UEs corresponding to the network slice identified by the S-NSSAI is not reduced.

In another possible implementation manner, NSACF_1 first deletes information related to session_1 from the stored context, and then NSACF_1 judges whether there is information about other sessions in the current UE. If the current UE does not have other session information, that is, after the information related to session_1 is deleted from the session information related to the UE, the session information related to the UE is empty, then NSACF_1 can reduce the network identified by S-NSSAI The number of UEs corresponding to the slice. If the current UE still has other session information, that is, after the session information related to session_1 is deleted from the session information related to the UE, the session information related to the UE is not empty, then NSACF_1 does not need to reduce the information identified by S-NSSAI The number of UEs corresponding to the network slice.

In this example, since NSACF_1 stores information related to session_1 and information related to session_2 for the UE ID at the same time, and the UE currently only releases the PDN connection_1 corresponding to the information related to session_1, NSACF_1 judges that the The UE still has other sessions, and there is no need to reduce the number of UEs accessing the network slice identified by S-NSSAI. NSACF_1 deletes the information related to UE session 1, and continues to save the UE ID, the corresponding relationship between S-NSSAI and the information related to UE session 2 corresponding relationship. That is, the UE ID will continue to be stored in the UE ID list that the network slice identified by the S-NSSAI has already accessed.

Step 1007, NSACF_1 sends a first response message_1 to SMF+PGW-C_1.

Wherein, the first response message_1 is used to indicate the result of performing admission control on the network slice. The result may include: performing admission control on the network slice successfully or failing to perform admission control on the network slice. If the execution of admission control on the network slice is successful, it means that the counting of the number of UEs is successful, and if the execution of admission control on the network slice fails, it means that the counting of the number of UEs is failed, then the first response message_1 can also carry the failure reason value , the failure cause value is used to indicate that the UE still has other sessions. In step 1007, the first response message_1 may indicate that admission control on the network slice fails, and the reason for the failure is that the UE still has other sessions.

In a possible implementation manner, NSACF_1 sends Nnsacf_NumberOfPDUsPerSliceAvailabilityCheckAndUpdate response to SMF+PGW-C_1, and NSACF_1 carries the result of performing admission control on network slices in the sent message.

Step 1008, execute the remaining procedures of PDN connection release.

So far, the release of the PDN connection_1 is completed.

In step 1009, the UE initiates the release procedure of the PDN connection_2 again.

The implementation manner of step 1009 is the same as that of step 701, and reference may be made to the description of step 701, which will not be repeated here.

Step 1010, SMF+PGW-C_2 sends a sixth request message_4 to NSACF_2.

Wherein, the sixth request message_4 may carry information related to S-NSSAI, update flag_2, and session_2. The update flag_2 is used to indicate that the number of sessions corresponding to the network slice identified by the S-NSSAI is reduced, for example, the number of sessions is reduced by 1. The information related to session_2 may include the identifier of SMF+PGW-C_2 and/or the identifier of session_2, the identifier of SMF+PGW-C_2 may be the ID of SMF+PGW-C_2, and the identifier of session_2 is used to identify the Session_2, such as PDU session ID_2, where PDU session ID_2 may be included in the create session request message.

Optionally, the sixth request message_4 may also carry a UE ID, where the UE ID may be determined by SMF+PGW-C_1 according to the delete session request message. Exemplarily, the UE ID may be the IMSI of the UE.

In a possible implementation manner, if SMF+PGW-C_2 saves the information of NSACF_2 in the context, then SMF+PGW-C_2 can directly determine NSACF_2 according to the information of NSACF_2.

As another implementation, if SMF+PGW-C_2 does not save the information of NSACF_2 in the context, then SMF+PGW-C_2 may request NRF to discover NSACF_2. For this method, reference may be made to the above-mentioned step 809 and step 810 .

Step 1011, NSACF_2 performs admission control on the network slice according to the sixth request message_4.

In a possible implementation manner, NSACF_2 performing admission control on the network slice includes performing admission control on the number of sessions on the network slice, which may also be referred to as counting the number of sessions performed. Specifically, NSACF_2 reduces the number of sessions corresponding to the network slice identified by S-NSSAI (for example, NSACF_2 reduces the number of sessions established in the network slice identified by S-NSSAI by 1), and deletes the SMF+PGW- Identification of C ID_2.

Step 1012, NSACF_2 sends a sixth response message_4 to SMF+PGW-C_2.

Wherein, the sixth response message_4 is used to indicate the result of performing admission control on the network slice. The result may include: performing admission control on the network slice successfully or failing to perform admission control on the network slice. If the admission control on the network slice is successfully performed, it means that the counting of the number of sessions is performed successfully, and if the admission control on the network slice fails, it means that the counting of the number of sessions is executed failed. In step 1012, the sixth response message_4 may indicate that admission control on the network slice is performed successfully.

Step 1013, SMF+PGW-C_2 sends a first request message_2 to NSACF_1.

Wherein, the first request message_2 may carry information related to UE ID, S-NSSAI, update flag_1, and session_2. The UE ID can be determined by SMF+PGW-C_2 according to the delete session request message or context. The update flag_1 is used to indicate to reduce the number of UEs corresponding to the network slice identified by the S-NSSAI, for example, the number of UEs is reduced by 1. The information related to session_2 may include the identifier of SMF+PGW-C_2 and/or the identifier of session_2, the identifier of SMF+PGW-C_2 may be the ID of SMF+PGW-C_2, and the identifier of session_2 is used to identify the Session_2, such as PDU session ID_2, where PDU session ID_2 may be included in the create session request message.

In a possible implementation manner, if SMF+PGW-C_2 saves the information of NSACF_1 in the context, then SMF+PGW-C_2 can directly determine NSACF_1 according to the information of NSACF_1.

As another implementation, if SMF+PGW-C_2 does not save the information of NSACF_1 in the context, then SMF+PGW-C_2 may request NRF to discover NSACF_1. For this method, reference may be made to the above step 804 and step 805 .

A possible implementation, SMF+PGW-C_2 sends Nnsacf_NumberOfPDUsPerSliceAvailabilityCheckAndUpdate request to NSACF_1.

A possible implementation, optional, when SMF+PGW-C_2 determines that PDN connection_2 is the only PDN connection associated with S-NSSAI that SMF+PGW-C_2 serves for the UE, then SMF+PGW-C_2 Execute steps 1013-1015. Specifically, SMF+PGW-C_2 can judge whether PDN connection_2 is the only PDN connection associated with S-NSSAI according to the context information. For example, SMF+PGW-C_2 saves the context information of all PDN connections currently established by the UE , if there is another PDN connection in the context that is the same as the network slice associated with the PDN connection_2, it means that after the PDN connection_2 is released, there are other PDN connections. For example, the UE currently has PDN connection_2', which is also served by SMF+PGW-C_2, and the network slice associated with PDN connection_2' is the same as the network slice associated with PDN connection_2. It should be noted that the APN corresponding to the PDN connection_2' may be different from the APN corresponding to the PDN connection_2. If there is no other PDN connection in the context that is the same as the network slice associated with the PDN connection_2, it means that the PDN connection_2 is the only one associated with the network slice initiated by the UE and served by SMF+PGW-C_2 PDN connections.

If SMF+PGW-C_2 judges that PDN connection_2 is not the only PDN connection associated with S-NSSAI released by the UE according to the above description, for example, the UE has currently established PDN connection_2' and the PDN connection_2' Associated with the same S-NSSAI, then the number of UEs corresponding to the network slice identified by the S-NSSAI does not need to be executed. Since the current UE still has other PDN connections associated with the same network slice, SMF+PGW-C_2 does not need to request NSACF_1 controls the number of users of the network slice, that is, steps 1013-1015 may not be executed.

Step 1014, NSACF_1 performs admission control on the network slice according to the first request message_2.

In a possible implementation manner, performing admission control on the network slice by the NSACF includes performing admission control on the number of UEs on the network slice, which may also be referred to as performing counting on the number of UEs. Specifically, NSACF_1 judges whether the current UE has a session other than session_2, and if the context stored by NSACF_1 only contains information related to session_2 (that is, NSACF_1 only stores information about PDN connection_2), then NSACF_1 can reduce the The number of UEs corresponding to the network slice identified by the S-NSSAI, and at the same time, NSACF_1 deletes information related to session_2. If the context stored by NSACF_1 also includes session-related information other than session-2-related information, NSACF_1 deletes session-2-related information, but does not reduce the number of UEs corresponding to the network slice identified by the S-NSSAI.

In another possible implementation manner, NSACF_1 first deletes information related to session_2 from the stored context, and then NSACF_1 judges whether there is information about other sessions in the current UE. If there is no other session information for the current UE, that is, after the information related to session_2 is deleted from the session information related to the UE, the session information related to the UE is empty, then NSACF_1 can reduce the network identified by S-NSSAI The number of UEs corresponding to the slice. If the current UE still has other session information, that is, after the session information related to session_2 is deleted from the session information related to the UE, the session information related to the UE is not empty, then NSACF_1 does not need to reduce the information identified by the S-NSSAI The number of UEs corresponding to the network slice.

In this example, since the current NSACF_1 only stores session_2 related information for the UE ID, after deleting the session_2 related information, there are no other established sessions for the UE, so NSACF_1 can count the UE ( That is, NSACF_1 reduces the number of UEs that access the network slice identified by the S-NSSAI), and deletes the UE ID from the list of UE identifiers that have been accessed by the network slice in the context information.

Step 1015, NSACF_1 sends a first response message_2 to SMF+PGW-C_2.

Wherein, the first response message_2 is used to indicate the result of performing admission control on the network slice. The result may include: performing admission control on the network slice successfully or failing to perform admission control on the network slice. If the execution of admission control on the network slice is successful, it means that the counting of the number of UEs is successful, and if the execution of admission control on the network slice fails, it means that the counting of the number of UEs is failed, then the first response message_2 can also carry the failure reason value , the failure cause value is used to indicate that the UE still has other sessions. In step 1015, the first response message_2 may indicate that admission control on the network slice is performed successfully.

In a possible implementation manner, NSACF_1 sends Nnsacf_NumberOfPDUsPerSliceAvailabilityCheckAndUpdate response to SMF+PGW-C_2, and NSACF_1 carries the result of performing admission control on network slices in the sent message.

Step 1016, execute the remaining procedures of PDN connection release.

It can be seen from the above that for the determination process of the number of UEs and the number of sessions triggered by the release of the PDN connection, in Example 4, the NSACF responsible for controlling the number of UEs will also determine the PDN connection of the UE when determining the number of UEs corresponding to the network slice. Whether all should be released, when the UE has no established session, NSACF reduces the number of UEs accessing the network slice identified by S-NSSAI, and deletes the UE ID in the context information. In this way, network slice admission control in interworking scenarios can be realized.

It should be noted that in Figure 10, SMF+PGW-C first interacts with the NSACF responsible for controlling the number of UEs, and then interacts with the NSACF responsible for controlling the number of sessions as an example, but the embodiments of the present application are not limited thereto, for example, SMF+ The PGW-C may also first interact with the NSACF responsible for controlling the number of sessions, and then interact with the NSACF responsible for controlling the number of UEs.

The method embodiment provided by the present application is described in detail above with reference to FIG. 4 to FIG. 10 , and the device embodiment of the present application will be described in detail below in conjunction with FIG. 11 and FIG. 12 . It can be understood that, in order to implement the functions in the foregoing embodiments, the apparatus in FIG. 11 or FIG. 12 includes corresponding hardware structures and/or software modules for performing various functions. 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 each example 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.

FIG. 11 and FIG. 12 are schematic structural diagrams of possible devices provided by the embodiments of the present application. These devices can be used to implement the functions of the first network element, the second network element, the fourth network element, and the NRF in the above method embodiments, and thus can also realize the beneficial effects of the above method embodiments.

As shown in FIG. 11 , an apparatus 1100 includes a transceiver unit 1110 and a processing unit 1120 .

When the device 1100 is used to realize the function of the first network element in the method embodiment:

The transceiver unit 1120 is configured to acquire first information from a second network element, the first information is used to associate the first session of the user equipment, and the first network element supports performing control on the number of users accessing the network slice, so The first session is associated with the network slice, the second network element serves the first session; and receiving a first request message from the second network element, the first request message is used to indicate Reduce the number of users who have access to the network slice. The processing unit 1110 is configured to determine whether to reduce the number of users who have accessed the network slice according to the first information.

Optionally, after acquiring the first information, the processing unit 1110 may also save the first information, the network slice, and the corresponding relationship between the user equipment.

Optionally, the transceiving unit is specifically configured to: obtain the first information when the second network element requests to increase the number of users who have accessed the network slice.

Optionally, the transceiver unit is specifically configured to: receive a message from the second network element when the number of established sessions on the network slice does not exceed the maximum number of sessions allowed by the network slice. A second request message, where the second request message includes the first information.

Optionally, the processing unit is specifically configured to: if the user equipment has established a session other than the first session on the network slice, determine and maintain the number of users who have accessed the network slice; if The user equipment establishes only the first session on the network slice, and then determines to reduce the number of users who have accessed the network slice.

Optionally, the processing unit is further configured to: delete the first information after determining whether to reduce the number of users who have accessed the network slice.

Optionally, the first session is a packet data network (PDN) connection established by the user equipment in an Evolved Packet Core Network (EPC) network.

When the device 1100 is used to realize the function of the second network element in the method embodiment:

In some implementations, the processing unit 1110 is configured to determine the network slice associated with the first session of the user equipment; the transceiver unit 1120 is configured to send first information to the first network element, the first information is used to associate the A first session, where the first network element supports performing control on the number of users accessing the network slice, and the second network element serves the first session; and sending a first request to the first network element message, the first request message is used to indicate to reduce the number of users who have accessed the network slice; wherein the first information is used to determine whether to reduce the number of users who have accessed the network slice.

Optionally, the transceiving unit 1120 is specifically configured to: send the first information to the first network element during a process of requesting to increase the number of users who have accessed the network slice.

Optionally, the transceiving unit 1120 is specifically configured to: send a second A request message, the second request message includes the first information.

Optionally, the transceiver unit 1120 is specifically configured to: learn from a third network element that the number of established sessions on the network slice has reached the maximum number of sessions allowed by the network slice, and that the third network element supports Execute control on the number of sessions established on the network slice; after the second network element learns that the number of established sessions on the network slice has reached the maximum number of sessions allowed to be established on the network slice, report to the first network element The element sends the first request message.

Optionally, the transceiving unit 1120 is specifically configured to: when the first session is released, the second network element sends the first request message to the first network element.

In some other implementation manners, the processing unit 1110 is configured to determine a network slice associated with the first session of the user equipment; the transceiver unit 1120 is configured to send a third request message to a network element with a network storage function, and the third request message uses For requesting information of the fourth network element, the third request message includes the identifier of the network slice and second information, and the second information is used to indicate that the fourth network element supports access to the network slice performing control on the number of users, and supporting performing control on the number of sessions established on the network slice; receiving a third response message from the network storage function network element, where the third response message includes information on the fourth network element; and sending a fourth request message to the fourth network element, where the fourth request message is used to request the fourth network element to perform control on the number of users accessing the network slice, and to control the number of users connected to the network slice. Session count execution control.

Optionally, the fourth request message includes an identifier of the user equipment, first information, third information, fourth information, and an identifier of the network slice, the first information is used to associate the first session, Wherein: when the user equipment requests to establish the first session, the third information is used to indicate to increase the number of users who have accessed the network slice, and the fourth information is used to indicate to increase the number of users in the network slice The number of established sessions; when the user equipment requests to release the first session, the third information is used to indicate to reduce the number of users who have accessed the network slice, and the fourth information is used to indicate to reduce the number of users in the network slice. The number of sessions established for the network slice.

Optionally, the first information includes at least one of an identifier of the second network element or an identifier of the session with the first network element.

When the device 1100 is used to realize the function of NRF in the method embodiment:

The transceiver unit 1120 is configured to receive a third request message from the second network element, where the third request message is used to request information of the fourth network element, where the third request message includes the identifier of the network slice and the second Information, the second information is used to indicate that the fourth network element supports the control of the number of users accessing the network slice, and supports the control of the number of sessions established on the network slice; The second network element sends a third response message, where the third response message includes the information of the fourth network element.

When the device 1100 is used to realize the function of the fourth network element in the method embodiment:

The transceiver unit 1120 is configured to receive a fourth request message from a second network element, where the fourth network element supports controlling the number of users accessing the network slice and supporting controlling the number of sessions established on the network slice , the second network element serves the first session of the user equipment, and the first session is associated with the network slice; the processing unit 1110 is configured to, according to the fourth request message, process the The number of users and the number of sessions established in the network slice perform control; the transceiver unit 1120 is further configured to send a fourth response message to the second network element, and the fourth response message is used to indicate the received A result of performing control on the number of users entering the network slice and a result of performing control on the number of sessions established in the network slice.

More detailed descriptions about the processing unit 1110 and the transceiver unit 1120 can be directly obtained by referring to related descriptions in the above method embodiments, and details are not repeated here.

As shown in FIG. 12 , the device 1200 includes a processor 1210 and an interface circuit 1220 . The processor 1210 and the interface circuit 1220 are coupled to each other. It can be understood that the interface circuit 1220 may be a transceiver or an input/output interface. In one implementation manner, the apparatus 1200 may further include a memory 1230 for storing instructions executed by the processor 1210 or storing input data required by the processor 1210 to execute the instructions or storing data generated by the processor 1210 after executing the instructions.

When the apparatus 1200 is used to implement the method described above, the processor 1210 is used to implement the functions of the processing unit 1120 described above, and the interface circuit 1220 is configured to implement the functions of the transceiver unit 1110 described above.

When the above communication device is a chip applied to the first network element, the chip implements the functions of the first network element in the above method embodiment. The chip receives information from other modules (such as radio frequency modules or antennas) in the first network element, and the information is sent to the first network element by other devices; or, the chip sends information to other modules (such as radio frequency modules) in the first network element. module or antenna) to send information, the information is sent by the first network element to other devices.

When the above communication device is a chip applied to the second network element, the chip implements the functions of the second network element in the above method embodiment. The chip receives information from other modules (such as radio frequency modules or antennas) in the second network element, and the information is sent to the second network element by other devices; or, the chip sends information to other modules (such as radio frequency modules) in the second network element. module or antenna) to send information, which is sent by the second network element to other devices.

When the communication device is a chip using the fourth network element, the chip implements the function of the fourth network element in the above method embodiment. The chip receives information from other modules (such as radio frequency modules or antennas) in the fourth network element, and the information is sent to the fourth network element by other devices; or, the chip sends information to other modules (such as radio frequency modules) in the fourth network element. module or antenna) to send information, and the information is sent by the fourth network element to other devices.

When the above-mentioned communication device is a chip using NRF, the chip implements the function of NRF in the above-mentioned method embodiment. The chip receives information from other modules in the NRF (such as radio frequency modules or antennas), and the information is sent to the NRF by other devices; or, the chip sends information to other modules in the NRF (such as radio frequency modules or antennas), and the information It is sent by NRF to other devices.

The embodiment of the present application also provides a chip, which acquires an instruction and executes the instruction to implement the above method.

Optionally, as an implementation manner, the chip includes a processor and a data interface, and the processor reads instructions stored in the memory through the data interface to execute the above method.

Optionally, as an implementation manner, the chip may further include a memory, the memory stores instructions, the processor is configured to execute the instructions stored in the memory, and when the instructions are executed, the processor is configured to execute the above method .

An embodiment of the present application further provides a communication system, including any one of the above-mentioned communication devices, or including any one of the above-mentioned chips.

The embodiment of the present application also provides a computer-readable storage medium, where instructions are stored in the computer-readable storage medium, and the instructions are used in the methods in the foregoing method embodiments.

The embodiment of the present application also provides a computer program product including instructions, where the instructions are used to implement the methods in the above method embodiments.

It can be understood that the processor in the embodiments of the present application may be a central processing unit (central processing unit, CPU), and may also be other general processors, digital signal processors (digital signal processor, DSP), application specific integrated circuits (application specific integrated circuit, ASIC), field programmable gate array (field programmable gate array, FPGA) or other programmable logic devices, transistor logic devices, hardware components or any combination thereof. A general-purpose processor can be a microprocessor, or any conventional processor.

Memory in embodiments of the present application may be volatile memory or nonvolatile memory, or may include both volatile and nonvolatile memory. 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 random access memory (RAM) are available, such as static random access memory (static RAM, SRAM), dynamic random access memory (DRAM), synchronous dynamic random access memory 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 Access memory (synchlink DRAM, SLDRAM) and direct memory bus random access memory (direct rambus RAM, DR RAM).

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

In each embodiment of the present application, if there is no special explanation and logical conflict, the terms and/or descriptions between different embodiments are consistent and can be referred to each other, and the technical features in different embodiments are based on their inherent Logical relationships can be combined to form new embodiments.

In this application, "at least one" means one or more, and "multiple" means two or more. "And/or" describes the association relationship of associated objects, indicating that there may be three types of relationships, for example, A and/or B, which can mean: A exists alone, A and B exist simultaneously, and B exists alone, where A, B can be singular or plural. In the text description of this application, the character "/" generally indicates that the contextual objects are an "or" relationship; in the formulas of this application, the character "/" indicates that the contextual objects are a "division" Relationship.

It can be understood that the various numbers involved in the embodiments of the present application are only for convenience of description, and are not used to limit the scope of the embodiments of the present application. The size of the serial numbers of the above-mentioned processes does not mean the order of execution, and the execution order of each process should be determined by its functions and internal logic.

Unless otherwise specified, all technical and scientific terms used in the embodiments of the present application have the same meaning as commonly understood by those skilled in the technical field of the present application. The terms used in the present application are only for the purpose of describing specific embodiments, and are not intended to limit the scope of the present application. It should be understood that the foregoing is an illustration, and the foregoing examples are only intended to help those skilled in the art understand the embodiments of the present application, and are not intended to limit the embodiments of the present application to the illustrated specific values or specific scenarios. Those skilled in the art can obviously make various equivalent modifications or changes based on the examples given above, and such modifications and changes also fall within the scope of the embodiments of the present application.

In the several embodiments provided in this application, it should be understood that the disclosed systems, devices and methods may be implemented in other ways. For example, the device embodiments described above are only illustrative. For example, the division of the units is only a logical function division. In actual implementation, there may be other division methods. For example, multiple units or components can be combined or May be integrated into another system, or some features may be ignored, or not implemented. In another point, the mutual coupling or direct coupling or communication connection shown or discussed may be through some interfaces, and the indirect coupling or communication connection of devices or units may be in electrical, mechanical or other forms.

The units described as separate components may or may not be physically separated, and the components shown as units may or may not be physical units, that is, they may be located in one place, or may be distributed to multiple network units. Part or all of the units can be selected according to actual needs to achieve the purpose of the solution of this embodiment.

In addition, each functional unit in each embodiment of the present application may be integrated into one processing unit, each unit may exist separately physically, or two or more units may be integrated into one unit.

If the functions described above are realized in the form of software function units and sold or used as independent products, they can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of the present application is essentially or the part that contributes to the prior art or the part of the technical solution can be embodied in the form of a software product, and the computer software product is stored in a storage medium, including Several instructions are used to make a computer device (which may be a personal computer, a server, or a network device) execute all or part of the steps of the methods described in the various embodiments of the present application. The aforementioned storage media include: U disk, mobile hard disk, read-only memory (Read-Only Memory, ROM), random access memory (Random Access Memory, RAM), magnetic disk or optical disc and other media that can store program codes. .

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 admission control method, characterized in that the method comprises:

The first network element acquires first information from the second network element, the first information is used to associate the first session of the user equipment, the first network element supports the control of the number of users accessing the network slice, the first network element a session is associated with the network slice, the second network element serving the first session;

The first network element receives a first request message from the second network element, where the first request message is used to indicate to reduce the number of users who have accessed the network slice;

The first network element determines whether to reduce the number of users who have accessed the network slice according to the first information.
The method according to claim 1, wherein the first network element obtaining the first information from the second network element comprises:

During the process of the second network element requesting to increase the number of users who have accessed the network slice, the first network element acquires the first information.
The method according to claim 1, wherein the first network element obtaining the first information from the second network element comprises:

When the number of established sessions on the network slice does not exceed the maximum number of sessions allowed by the network slice, the first network element receives a second request message from the second network element, and The second request message includes the first information.
The method according to any one of claims 1 to 3, wherein the method further comprises:

The first network element stores the first information.
The method according to any one of claims 1 to 4, wherein the first network element determines whether to reduce the number of users who have accessed the network slice according to the first information, including:

If the user equipment has established a session other than the first session on the network slice, the first network element determines to maintain the number of users who have accessed the network slice;

If the user equipment has only established the first session on the network slice, the first network element determines to reduce the number of users who have accessed the network slice.
The method according to claim 5, wherein the method further comprises:

After the first network element determines whether to reduce the number of users who have accessed the network slice, the first network element deletes the first information.
The method according to any one of claims 1 to 6, wherein the first information includes at least one of an identifier of the second network element or an identifier of the session with the first network element.
A method according to any one of claims 1 to 7, characterized in that

The first session is a PDN connection established by the user equipment in an Evolved Packet Core Network (EPC) network.
A network slice admission control method, characterized in that the method comprises:

The second network element determines a network slice associated with the first session of the user equipment;

The second network element sends first information to the first network element, the first information is used to associate the first session, and the first network element supports performing control on the number of users accessing the network slice, the second network element serves the first session;

The second network element sends a first request message to the first network element, where the first request message is used to indicate to reduce the number of users who have accessed the network slice;

Wherein, the first information is used to determine whether to reduce the number of users who have accessed the network slice.
The method according to claim 9, wherein the sending of the first information by the second network element to the first network element comprises:

In a process of requesting to increase the number of users who have accessed the network slice, the second network element sends the first information to the first network element.
The method according to claim 9, wherein the sending of the first information by the second network element to the first network element comprises:

When the number of established sessions on the network slice does not exceed the maximum number of sessions allowed by the network slice, the second network element sends a second request message to the first network element, and the second The request message includes the first information.
The method according to claim 10, characterized in that,

The method also includes:

The second network element learns from the third network element that the number of established sessions on the network slice has reached the maximum number of sessions allowed by the network slice, and the third network element supports the session establishment on the network slice number execution control;

The second network element sends a first request message to the first network element, including:

After the second network element learns that the number of established sessions on the network slice has reached the maximum number of sessions allowed by the network slice, the second network element sends the first network element to the first network element A request message.
The method according to any one of claims 9 to 11, wherein the second network element sends a first request message to the first network element, comprising:

When releasing the first session, the second network element sends the first request message to the first network element.
The method according to any one of claims 9 to 13, wherein the first information includes at least one of an identifier of the second network element or an identifier of the session with the first network element.
A method according to any one of claims 9 to 14, wherein

The first session is a PDN connection established by the user equipment in an Evolved Packet Core Network (EPC) network.
A network slice admission control method, characterized in that the method comprises:

The second network element determines a network slice associated with the first session of the user equipment;

The second network element sends a third request message to the network storage function network element, the third request message is used to request information of the fourth network element, and the third request message includes the identifier of the network slice and the second information, where the second information is used to indicate that the fourth network element supports controlling the number of users accessing the network slice, and supports controlling the number of sessions established on the network slice;

The second network element receives a third response message from the network storage function network element, where the third response message includes information of the fourth network element;

The second network element sends a fourth request message to the fourth network element, where the fourth request message is used to request the fourth network element to perform control on the number of users accessing the network slice, and to control the number of users connected to the network slice. The number of sessions established by the above network slices is controlled.
The method according to claim 16, characterized in that,

The first session is a PDN connection established by the user equipment in an Evolved Packet Core Network (EPC) network.
A network slice admission control method, characterized in that the method comprises:

The network storage function network element receives a third request message from the second network element, the third request message is used to request the information of the fourth network element, and the third request message includes the identifier of the network slice and the second information The second information is used to indicate that the fourth network element supports controlling the number of users accessing the network slice, and supports controlling the number of sessions established on the network slice;

The network element with the network storage function sends a third response message to the second network element, where the third response message includes information of the fourth network element.
A communication device, characterized by comprising:

A processor configured to execute computer instructions stored in a memory, so that the device performs the method according to any one of claims 1 to 8, or performs the method according to any one of claims 9 to 17 , or perform the method as claimed in claim 18.
The apparatus of claim 19, further comprising the memory for storing the computer instructions.
A computer-readable storage medium, characterized in that, the computer-readable medium stores a computer program, and when the computer program is executed by one or more processors, the device comprising the processor performs the process described in claim 1. The method according to any one of claims 9 to 17, or the method according to claim 18.
A computer program product, characterized in that the computer program product comprises computer program code, and when the computer program code is run on a computer, the method according to any one of claims 1 to 8 is realized, or the method according to any one of claims 1 to 8 is realized, or A method as claimed in any one of claims 9 to 17, or implementing a method as claimed in claim 18.
A communication system, characterized by comprising the communication device according to claim 19 or 20.