CN115707062A - Network slice admission control method and device - Google Patents

Network slice admission control method and device Download PDF

Info

Publication number
CN115707062A
CN115707062A CN202110908693.4A CN202110908693A CN115707062A CN 115707062 A CN115707062 A CN 115707062A CN 202110908693 A CN202110908693 A CN 202110908693A CN 115707062 A CN115707062 A CN 115707062A
Authority
CN
China
Prior art keywords
network slice
network element
network
session
information
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Pending
Application number
CN202110908693.4A
Other languages
Chinese (zh)
Inventor
朱方园
米而科·施拉姆
孙海洋
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Huawei Technologies Co Ltd
Original Assignee
Huawei Technologies Co Ltd
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Huawei Technologies Co Ltd filed Critical Huawei Technologies Co Ltd
Priority to CN202110908693.4A priority Critical patent/CN115707062A/en
Priority to PCT/CN2022/090973 priority patent/WO2023015973A1/en
Publication of CN115707062A publication Critical patent/CN115707062A/en
Pending legal-status Critical Current

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W48/00—Access restriction; Network selection; Access point selection
    • H04W48/02—Access restriction performed under specific conditions
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W48/00—Access restriction; Network selection; Access point selection
    • H04W48/08—Access restriction or access information delivery, e.g. discovery data delivery
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W48/00—Access restriction; Network selection; Access point selection
    • H04W48/16—Discovering, processing access restriction or access information
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W60/00—Affiliation to network, e.g. registration; Terminating affiliation with the network, e.g. de-registration
    • H04W60/06—De-registration or detaching

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Computer Security & Cryptography (AREA)
  • Data Exchanges In Wide-Area Networks (AREA)

Abstract

The application provides a network slice admission control method and a device, wherein the method comprises the following steps: a first network element acquires first information from a second network element, wherein the first information is used for associating a first session of user equipment, the first network element supports the execution of control on 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, wherein the first request message is used for indicating that the number of users accessing the network slice is reduced; and the first network element determines whether to reduce the number of users accessed to the network slice or not according to the first information. The method can realize the control of the number of users accessing the network slice and the number of sessions established in the network slice, and is beneficial to the admission control of the network slice.

Description

Network slice admission control method and device
Technical Field
The present application relates to the field of communications, and in particular, to a method and an apparatus for network slice admission control.
Background
With the development of communication technology, billions of internet of things devices are accessed into a network, and the demands of different types of application scenarios on the network are differentiated, and some applications are even mutually conflicting. Providing services for different types of application scenarios through a single network at the same time can lead to an abnormally complex network architecture, low network management efficiency and low resource utilization efficiency. The network slicing technology provides mutually isolated network environments for different application scenes in a mode of virtualizing an independent logic network on the same network infrastructure, so that different application scenes can customize network functions and characteristics according to respective requirements, and quality of service (QoS) requirements of different services can be practically guaranteed.
In the actual deployment scenario of network slices, the number of users that can accommodate access and the number of sessions that are allowed to be established per network slice is limited due to network resource limitations. How to control the number of users accessing a network slice and the number of sessions established on the network slice becomes an urgent problem to be solved.
Disclosure of Invention
The application provides a network slice admission control method and a network slice admission control device, which can realize the control of the number of users accessing a network slice and the number of sessions established in the network slice and are beneficial to the admission control of the network slice.
In a first aspect, the present application provides a method for controlling network slice admission, where the method includes: a first network element acquires first information from a second network element, wherein the first information is used for associating a first session of user equipment, the first network element supports the execution of control on 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, wherein the first request message is used for indicating that the number of users accessing the network slice is reduced; and the first network element determines whether to reduce the number of users accessed to the network slice or not according to the first information.
The first network element supports controlling the number of users accessing the network slice, which can also be described as the first network element supporting counting (number of UEs counting) of the number of users accessing the network slice or the first network element having the capability of controlling the number of users accessing the network slice.
The first information is used for associating with the first session of the user equipment, and may also be described as the first information being information related to the first session of the user equipment. As one example, the first information is used to identify the first session, e.g., the first information may include at least one of an identification of the first session or an identification of the second network element. The identifier of the second network element may be an ID (identity) 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 (PDU) session ID (PDU session ID).
Alternatively, the first network element may be a Network Slice Admission Control Function (NSACF) network element, and the second network element may be a Session Management Function (SMF) + Packet Data Network (PDN) gateway-control plane (PGW-C) network element, that is, SMF + PGW-C.
In a possible implementation manner, after the first network element obtains the first information, the network slice, and the corresponding relationship of the user equipment may also be stored.
In the above technical solution, the second network element may send the information related to the session to the first network element, so that the first network element stores a corresponding relationship between the user equipment, the network slice, and the information related to the session, and when the first network element receives the instruction to reduce the number of users accessing the network slice, it may be determined whether the number of users accessing the network slice may be reduced according to the corresponding relationship. This may enable network slice admission control.
With reference to the first aspect, in a possible implementation manner, the acquiring, by the first network element, the first information from the second network element includes: and in the process that the second network element requests to increase the number of users accessed to the network slice, the first network element acquires the first information.
For example, when a user equipment establishes a PDN connection in an Evolved Packet Core (EPC) network, a second network element determines a network slice corresponding to the PDN connection, and further triggers user number control of the network slice and session number control of the network slice, the second network element may interact with a first network element that supports control of a number of users accessing the network slice, trigger the first network element to increase a number of users accessing the network slice, and send first information to the first network element in a process of interacting with the first network element; if the number of users accessing the network slice is not excessive, it is indicated that the number of users accessing the network slice does not reach the maximum number (such as a first threshold), the network slice allows new users to access, the second network element interacts with a third network element supporting the execution control of the number of sessions established on the network slice, and the third network element is triggered 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 sessions established by the network slice is not excessive, which indicates that the number of sessions established by the network slice does not reach the maximum number (e.g., a second threshold), the network slice allows a new session to be established, or it can be understood that the second network element learns from the third network element that the session number control is successful, the second network element may not interact with the first network element any more, and continue to perform other steps of the PDN connection establishment procedure; if the second network element learns from the third network element that the number of sessions established by the network slice is excessive, which indicates that the number of sessions established by the network slice reaches the maximum number (e.g., the second threshold), the network slice does not allow new sessions to be established, or it can be understood that the second network element learns from the third network element that the session number control fails, the second network element may interact with the first network element again, and trigger the first network element to control the number of users accessing the network slice, for example, trigger the first network element to reduce the number of users accessing the network slice.
In the above technical solution, the first network element obtains the first information in the process that the second network element requests to increase the number of users that have access to the network slice, so that the second network element does not need to interact with the first network element any more when knowing that the session number control is successful from the third network element, which is helpful for reducing signaling overhead.
With reference to the first aspect or any one implementation manner of the first aspect, in another possible implementation manner, the acquiring, by the first network element, the first information from the second network element includes: the first network element receives a second request 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 to be established by the network slice, wherein the second request message comprises the first information.
For example, when a user equipment establishes a PDN connection in an EPC network, a second network element determines a network slice corresponding to the PDN connection, and further triggers user number control of the network slice and session number control of the network slice, the second network element may interact with a first network element that supports 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 excessive, it is indicated that the number of users accessing the network slice does not reach the maximum number (such as a first threshold), the network slice allows new users to access, the second network element interacts with a third network element supporting the execution control of the number of sessions established on the network slice, and the third network element is triggered 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 sessions established by the network slice is not excessive, which indicates that the number of sessions established by the network slice does not reach the maximum number (e.g., a second threshold), the network slice allows new sessions to be established, or it can be understood that the second network element learns from the third network element that the session number control is successful, the second network element may send a second request message to the first network element, and carry the first information in the second request message, so that the first network element stores the first information and continues to perform other steps of the PDN connection establishment procedure; if the second network element learns from the third network element that the number of sessions established by the network slice is excessive, which indicates that the number of sessions established by the network slice reaches the maximum number (e.g., the second threshold), the network slice does not allow new sessions to be established, or it can be understood that the second network element learns from the third network element that the session number control fails, the second network element may interact with the first network element again, and trigger the first network element to control the number of users accessing the network slice, for example, trigger the first network element to reduce the number of users accessing the network slice.
In the above technical solution, the first network element obtains the first information when the number of sessions established on the network slice does not exceed the maximum number of sessions allowed to be established by the network slice, so that it is not necessary to instruct the first network element to delete the first information when the second network element learns from the third network element that the session number control fails, which can simplify the processing.
With reference to the first aspect or any implementation manner of the first aspect, in another possible implementation manner, the determining, by the first network element, whether to reduce the number of users having access to the network slice according to the first information includes: if the user equipment establishes a session on the network slice except the first session, the first network element determines to maintain the number of users accessing the network slice; if the user equipment only establishes the first session on the network slice, the first network element determines to reduce the number of users having access to the network slice. This allows a more accurate control of the number of users that have access to the network slice.
With reference to the first aspect or any one of implementation manners thereof, in another possible implementation manner, the method further includes: and after the first network element determines whether the number of users accessing the network slice is reduced, deleting the first information by the first network element.
With reference to the first aspect or any implementation manner of the first aspect, in another possible implementation manner, the first session is a PDN connection established by the ue in an EPC network, or may also be described as a session corresponding to the PDN connection established by the ue in the EPC.
In a second aspect, the present application provides a method for controlling network slice admission, where the method includes: 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 a first network element, the first information is used for associating the first session, the first network element supports to execute control on 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, wherein the first request message is used for indicating that the number of users accessing the network slice is reduced; wherein the first information is used to determine whether to reduce a number of users that have access to the network slice.
Wherein the second network element serves the first session. The second network element serves the first session, which may be understood as associating the first session to the second network element when establishing the first session, or establishing the first session through a network slice resource 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 control over the number of users accessing the network slice, which can also be described as the first network element supports counting over the number of users accessing the network slice or the first network element has the capability of controlling over the number of users accessing the network slice.
The first information is used for associating with the first session of the user equipment, and may also be described as the first information being information related to the first session of the user equipment. As an example, the first information is used to identify the first session, e.g., the first information may include at least one of an identification of the first session or an identification of the second network element. The identifier of the second network element may be an 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.
Alternatively, the first network element may be an NSACF, and the second network element may be an SMF + PGW-C.
In the above technical solution, the second network element sends the information related to the session to the first network element, so that the first network element stores a corresponding relationship between the user equipment, the network slice, and the information related to the session, and thus when the first network element receives an instruction to reduce the number of users accessing the network slice, it can determine whether the number of users accessing the network slice can be reduced according to the corresponding relationship. This may enable network slice admission control.
With reference to the second aspect, in a possible implementation manner, the sending, by the second network element, the first information to the first network element includes: and in the process of requesting to increase the number of users accessing the network slice, the second network element sends the first information to the first network element.
For example, when a user equipment establishes a PDN connection in an EPC network, a second network element determines a network slice corresponding to the PDN connection, and further triggers user number control of the network slice and session number control of the network slice, the second network element may interact with a first network element that supports 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 send first information to the first network element in a process of interacting with the first network element; if the number of users accessing the network slice is not excessive, it is indicated that the number of users accessing the network slice does not reach the maximum number (such as a first threshold), the network slice allows new users to access, the second network element interacts with a third network element supporting the execution control of the number of sessions established on the network slice, and the third network element is triggered 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 sessions established by the network slice is not excessive, which indicates that the number of sessions established by the network slice does not reach the maximum number (e.g., a second threshold), the network slice allows a new session to be established, or it can be understood that the second network element learns from the third network element that the session number control is successful, the second network element may not interact with the first network element any more, and continue to perform other steps of the PDN connection establishment procedure; if the second network element learns from the third network element that the number of sessions established by the network slice is excessive, which indicates that the number of sessions established by the network slice reaches the maximum number (e.g., the second threshold), the network slice does not allow new sessions to be established, or it can be understood that the second network element learns from the third network element that the session number control fails, the second network element may interact with the first network element again, and trigger the first network element to control the number of users accessing the network slice, for example, trigger the first network element to reduce the number of users accessing the network slice.
In the above technical solution, the first network element obtains the first information in the process that the second network element requests to increase the number of users that have access to the network slice, so that the second network element does not need to interact with the first network element any more when knowing that the session number control is successful from the third network element, which is helpful for reducing signaling overhead.
With reference to the second aspect or any implementation manner of the second aspect, in another possible implementation manner, the sending, by the second network element, the first information to the first network element includes: and when the number of established sessions on the network slice does not exceed the maximum number of sessions allowed to be established by the network slice, the second network element sends a second request message to the first network element, wherein the second request message comprises the first information.
For example, when a user equipment establishes a PDN connection in an EPC network, a second network element determines a network slice corresponding to the PDN connection, and further triggers user number control of the network slice and session number control of the network slice, the second network element may interact with a first network element that supports 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 excessive, it is indicated that the number of users accessing the network slice does not reach the maximum number (such as a first threshold), the network slice allows new users to access, the second network element interacts with a third network element supporting the execution control of the number of sessions established on the network slice, and the third network element is triggered 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 sessions established by the network slice is not excessive, which indicates that the number of sessions established by the network slice does not reach the maximum number (e.g., a second threshold), the network slice allows new sessions to be established, or it can be understood that the second network element learns from the third network element that the session number control is successful, the second network element may send a second request message to the first network element, and carry the first information in the second request message, so that the first network element stores the first information and continues to perform other steps of the PDN connection establishment procedure; if the second network element learns from the third network element that the number of sessions established by the network slice is excessive, which indicates that the number of sessions established by the network slice reaches the maximum number (e.g., the second threshold), the network slice does not allow new sessions to be established, or it can be understood that the second network element learns from the third network element that the session number control fails, the second network element may interact with the first network element again, and trigger the first network element to control the number of users accessing the network slice, for example, trigger the first network element to reduce the number of users accessing the network slice.
In the above technical solution, the first network element obtains the first information when the number of sessions established on the network slice does not exceed the maximum number of sessions allowed to be established by the network slice, so that it is not necessary to instruct the first network element to delete the first information when the second network element knows that the session number control from the third network element fails, which can simplify the processing.
With reference to the second aspect or any implementation manner thereof, in another possible implementation manner, the method further includes: the second network element learns from a third network element that the number of sessions established on the network slice reaches the maximum value of the number of sessions allowed to be established by the network slice, and the third network element supports control over the number of sessions established on the network slice; the second network element sending a first request message to the first network element, including: and after the second network element learns that the number of the established sessions on the network slice reaches the maximum value of the number of the sessions allowed to be established by the network slice, the second network element sends the first request message to the first network element.
With reference to the second aspect or any implementation manner of the second aspect, in another possible implementation manner, the sending, by the second network element, a first request message to the first network element includes: and when the first session is released, the second network element sends the first request message to the first network element.
With reference to the second aspect or any implementation manner of the second aspect, in another possible implementation manner, the first session is a PDN connection established by the ue in an EPC network, or may also be described as a session corresponding to the PDN connection established by the ue in the EPC.
In a third aspect, the present application provides a method for controlling network slice admission, where the method includes: 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 a network storage function network element, the third request message is used for requesting information of a fourth network element, the third request message comprises an identifier of the network slice and second information, and the second information is used for indicating that the fourth network element supports control over the number of users accessing the network slice and control over the number of sessions established on the network slice; the second network element receives a third response message of the network storage function network element, where the third response message includes information of the fourth network element; and 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 control the number of users accessing 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 controlling the number of users accessing the network slice and controlling the number of sessions established on the control network slice, so that when determining the number of users and the number of sessions corresponding to the network slice, the fourth network element can determine whether the user equipment has accessed the network slice or whether the sessions of the user equipment should be released, thereby accurately controlling the number of users accessing the network slice and the number of sessions established on the network slice. This may enable network slice admission control.
With reference to the third aspect, in a possible implementation manner, the fourth request message includes an identifier of a user equipment, first information, third information, fourth information, and an identifier of the network slice, where the first information is used to associate with the first session, where: when the user equipment requests to establish the first session, the third information is used for indicating the increase of the number of users accessing the network slice, and the fourth information is used for indicating the increase of the number of sessions established in the network slice; when the user equipment requests to release the first session, the third information is used for indicating to reduce the number of users having access to the network slice, and the fourth information is used for indicating to reduce the number of sessions established in the network slice.
With reference to the third aspect or any implementation manner of the third aspect, in another possible implementation manner, the first information includes at least one of an identification of the second network element or an identification of the first session.
With reference to the third aspect or any implementation manner of the third aspect, in another possible implementation manner, the first session is a PDN connection established by the user equipment in an EPC network, or may also be described as a session corresponding to the PDN connection established by the user equipment in an EPC.
In a fourth aspect, the present application provides a method for controlling network slice admission, where the method includes: a network storage function network element receives a third request message from a second network element, where the third request message is used to request information of a fourth network element, the third request message includes an identifier of the network slice and second information, and the second information is used to indicate that the fourth network element supports controlling the number of users accessing the network slice and controlling the number of sessions established on the network slice; and the network storage function network element sends a third response message to the second network element, where the third response message includes information of the fourth network element.
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 controlling the number of users accessing the network slice and controlling the number of sessions established on the control network slice, so that when determining the number of users and the number of sessions corresponding to the network slice, the fourth network element can determine whether the user equipment has accessed the network slice or whether the sessions of the user equipment should be released, thereby accurately controlling the number of users accessing the network slice and the number of sessions established on the network slice. This may enable network slice admission control.
In a fifth aspect, the present application provides a method for controlling network slice admission, where the method includes: a fourth network element receives a fourth request message from a second network element, the fourth network element supporting control over the number of users accessing a network slice and control over the number of sessions established on the network slice, the second network element serving a first session of a user equipment, the first session being associated with the network slice; the fourth network element performs control on the number of users having access to the network slice and the number of sessions established in the network slice according to the fourth request message; and the fourth network element sends a fourth response message to the second network element, where the fourth response message is used to indicate a result of controlling the number of users who have access to the network slice and a result of controlling the number of sessions established in 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 controlling the number of users accessing the network slice and controlling the number of sessions established on the control network slice, so that when determining the number of users and the number of sessions corresponding to the network slice, the fourth network element can determine whether the user equipment has accessed the network slice or whether the sessions of the user equipment should be released, thereby accurately controlling the number of users accessing the network slice and the number of sessions established on the network slice. This may enable network slice admission control.
With reference to the fifth aspect, in a possible implementation manner, the fourth request message includes an identifier of a user equipment, first information, third information, fourth information, and an identifier of the network slice, where the first information is used to associate with the first session, where: when the user equipment requests to establish the first session, the third information is used for indicating the number of users who have access to the network slice to be increased, and the fourth information is used for indicating the number of sessions established in the network slice to be increased; when the user equipment requests to release the first session, the third information is used for indicating to reduce the number of users having access to the network slice, and the fourth information is used for indicating to reduce the number of sessions established in the network slice.
In a sixth aspect, the present application provides a communication device, comprising:
a transceiver unit, configured to acquire first information from a second network element, where the first information is used to associate a first session of a user equipment, the first network element supports controlling a 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; receiving a first request message from the second network element, wherein the first request message is used for indicating that the number of users accessing the network slice is reduced;
and the processing unit is used for determining whether the number of users accessing the network slice is reduced or not according to the first information.
In a possible implementation manner, after the first information is obtained, the apparatus may further store 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 transceiver unit is specifically configured to: and acquiring the first information in the process that the second network element requests to increase the number of users accessed to the network slice.
With reference to the sixth aspect or any implementation manner of the sixth aspect, in another possible implementation manner, the transceiver unit is specifically configured to: receiving a second request message from the second network element in a case that the number of established sessions on the network slice does not exceed a maximum value of the number of sessions allowed to be established by the network slice, the second request message including the first information.
With reference to the sixth aspect or any implementation manner of the sixth aspect, in another possible implementation manner, the processing unit is specifically configured to: determining to maintain the number of users having accessed the network slice if the user equipment establishes a session on the network slice other than the first session; and if the user equipment only establishes the first session on the network slice, determining to reduce the number of users having access to the network slice.
With reference to the sixth aspect or any implementation manner thereof, in another possible implementation manner, the processing unit is further configured to: deleting the first information after determining whether to reduce the number of users having access to the network slice.
With reference to the sixth aspect or any implementation manner of the sixth aspect, in another possible implementation manner, the first session is a PDN connection established by the user equipment in an EPC network.
In a seventh aspect, the present application provides a communications apparatus, comprising:
a processing unit to determine a network slice associated with a first session of a user equipment;
a transceiver unit, configured to send first information to a first network element, where the first information is used to associate with the first session, the first network element supports controlling a number of users accessing the network slice, and the second network element serves the first session; sending a first request message to the first network element, wherein the first request message is used for indicating that the number of users accessing the network slice is reduced; wherein the first information is used to determine whether to reduce a number of users that have access to the network slice.
With reference to the seventh aspect, in a possible implementation manner, the transceiver unit is specifically configured to: and in the process of requesting to increase the number of users accessing the network slice, sending the first information to the first network element.
With reference to the seventh aspect or any implementation manner of the seventh aspect, in another possible implementation manner, the transceiver unit is specifically configured to: and when the number of established sessions on the network slice does not exceed the maximum number of sessions allowed to be established by the network slice, sending a second request message to the first network element, wherein the second request message comprises the first information.
With reference to the seventh aspect or any implementation manner of the seventh aspect, in another possible implementation manner, the transceiver unit is specifically configured to: acquiring, from a third network element, that the number of sessions established on the network slice reaches a maximum value of the number of sessions allowed to be established by the network slice, the third network element supporting control over the number of sessions established on the network slice; and after the second network element learns that the number of the established sessions on the network slice reaches the maximum value of the number of the sessions allowed to be established by the network slice, sending the first request message to the first network element.
With reference to the seventh aspect or any implementation manner of the seventh aspect, in another possible implementation manner, the transceiver unit is specifically configured to: and when the first session is released, the second network element sends the first request message to the first network element.
With reference to the seventh aspect or any implementation manner of the seventh aspect, in another possible implementation manner, the first session is a PDN connection established by the user equipment in an EPC network.
In an eighth aspect, the present application provides a communications apparatus, comprising:
a processing unit to determine a network slice associated with a first session of a user equipment;
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, the third request message includes an identifier of the network slice and second information, and the second information is used to indicate that the fourth network element supports controlling the number of users accessing the network slice and controlling the number of sessions established on the network slice; receiving a third response message of the network storage function network element, wherein the third response message comprises information of 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 control on 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 a user equipment, first information, third information, fourth information, and an identifier of the network slice, where the first information is used to associate with the first session, where: when the user equipment requests to establish the first session, the third information is used for indicating the number of users who have access to the network slice to be increased, and the fourth information is used for indicating the number of sessions established in the network slice to be increased; when the user equipment requests to release the first session, the third information is used for indicating to reduce the number of users having access to the network slice, and the fourth information is used for indicating to reduce the number of sessions established in the network slice.
With reference to the eighth aspect or any implementation manner of this aspect, in another possible implementation manner, the first information includes at least one of an identification of the second network element or an identification of the first session.
With reference to the eighth aspect or any implementation manner of the eighth aspect, in another possible implementation manner, the first session is a PDN connection established by the user equipment in an EPC network.
In a ninth aspect, the present application provides a communication apparatus, comprising:
a transceiving 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, the third request message includes an identifier of the network slice and second information, and the second information is used to indicate that the fourth network element supports controlling a number of users accessing the network slice and controlling a number of sessions established on the network slice; and sending a third response message to the second network element, where the third response message includes information of the fourth network element.
In a tenth aspect, the present application provides a communication apparatus, comprising:
a transceiving unit, configured to receive a fourth request message from a second network element, where the fourth network element supports controlling a number of users accessing a network slice and controlling a number of sessions established on the network slice, and the second network element serves a first session of a user equipment, where the first session is associated with the network slice;
a processing unit, configured to perform control on the number of users who have access to 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 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 tenth aspect, in a possible implementation manner, the fourth request message includes an identifier of a user equipment, first information, third information, fourth information, and an identifier of the network slice, where the first information is used to associate with the first session, where: when the user equipment requests to establish the first session, the third information is used for indicating the number of users who have access to the network slice to be increased, and the fourth information is used for indicating the number of sessions established in the network slice to be increased; when the user equipment requests to release the first session, the third information is used for indicating to reduce the number of users having access to the network slice, and the fourth information is used for indicating to reduce the number of sessions established in the network slice.
The sixth aspect to the tenth aspect are device embodiments corresponding to the first aspect to the fifth aspect, and the method according to the first aspect to the fifth aspect and the advantageous effects according to the first aspect to the fifth aspect can be achieved, and for specific description, reference may be made to the first aspect to the fifth aspect, and details are not repeated here.
In an eleventh aspect, the present application provides a communications apparatus comprising a processor. The processor is coupled to the memory and is operable to execute the instructions in the memory to cause the apparatus to perform the method provided by any one of the first to fifth aspects described above, or to perform the method in any one of the possible implementations of the first to fifth aspects. Optionally, the apparatus further comprises a memory. Optionally, the apparatus further comprises an interface circuit, the processor being coupled to the interface circuit.
In a twelfth aspect, the present application provides a processor comprising: input circuit, output circuit and 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 performs the method provided in any one of the first to fifth aspects, or performs the method in any one of the possible implementations of the first to fifth aspects.
In a specific implementation process, the processor may be a chip, the input circuit may be an input pin, the output circuit may be an output pin, and the processing circuit may 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 and without limitation, a receiver, the signal output by the output circuit may be output to and transmitted by a transmitter, for example and without limitation, and the input circuit and the output circuit may be the same circuit that functions as the input circuit and the output circuit, respectively, at different times. The embodiment of the present application does not limit the specific implementation manner of the processor and various circuits.
In a thirteenth aspect, the present application provides a processing apparatus comprising a processor and a memory. The processor is configured to read instructions stored in the memory and may receive signals via the receiver and transmit signals via the transmitter to perform the method provided by any one of the first to fifth aspects or to perform the method of any one of the possible implementations of the first to fifth aspects.
Optionally, the number of the processors is one or more, and the number of the memories is one or more.
Alternatively, the memory may be integral to the processor or provided separately from the processor.
In a specific implementation process, the memory may be a non-transient memory, such as a Read Only Memory (ROM), which may be integrated on the same chip as the processor, or may be separately disposed on different chips.
The processing device in the thirteenth aspect may be a chip, the processor may be implemented by hardware or may be implemented by software, and when implemented by hardware, the processor may be a logic circuit or an integrated circuit; when implemented in software, the processor may be a general-purpose processor implemented by reading software code stored in a memory, which may be integrated with the processor, located external to the processor, or stand-alone.
In a fourteenth aspect, the present application provides a computer program product comprising: a computer program (which may also be referred to as code, or instructions), which when executed, causes a computer to perform the method provided by any of the first to fifth aspects described above, or to perform the method of any of the possible implementations of the first to fifth aspects.
In a fifteenth aspect, the present application provides a computer-readable medium storing a computer program (which may also be referred to as code, or instructions) which, when run on a computer, causes the computer to perform the method provided in any of the first to fifth aspects described above, or in any possible implementation of the first to fifth aspects.
In a sixteenth aspect, the present application provides a communication system including at least one of the apparatuses provided in any of the above aspects or possible implementations thereof.
Drawings
Fig. 1 is a schematic architecture diagram of a communication system to which the present application may be applied.
Fig. 2 is another schematic architecture diagram of a communication system to which the present application may be applied.
Fig. 3 is another schematic architecture diagram of a communication system to which the present application may be applied.
Fig. 4 is a schematic flow chart of a network slice admission control method provided by the present application.
Fig. 5 is a schematic flow chart 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 the present application.
Fig. 7 is another example of a network slice admission control method provided by the present application.
Fig. 8 is another example of a network slice admission control method provided by the present application.
Fig. 9 is another example of a network slice admission control method provided by the present application.
Fig. 10 is another example of a network slice admission control method provided by the present application.
Fig. 11 is a schematic structural diagram of an apparatus provided in an embodiment of the present application.
Fig. 12 is another schematic structural diagram of an apparatus provided in an embodiment of the present application.
Detailed Description
The technical solution in the present application will be described below with reference to the accompanying drawings.
The technical scheme of the embodiment of the application can be applied to various communication systems, for example: a Long Term Evolution (LTE) system, an LTE Frequency Division Duplex (FDD) system, an LTE Time Division Duplex (TDD) system, a Universal Mobile Telecommunications System (UMTS), a Worldwide Interoperability for Microwave Access (WiMAX) communication system, a fifth generation (5 g) communication system, a New Radio (NR) communication system, or a satellite communication system. The communication system may include a non-standalone (NSA) network and/or a Standalone (SA) network, among others.
The technical scheme provided by the application can also be applied to Machine Type Communication (MTC), long Term Evolution-machine (LTE-M) for inter-machine communication, device-to-device (D2D) network, machine-to-machine (M2M) network, internet of things (IoT) network, or other networks. The IoT network may comprise, for example, a car networking network.
The technical solution provided in the present application may also be applied to future mobile communication systems, such as a sixth generation mobile communication system, which is not limited in the present application.
A communication system to which the present application can be applied will be described below with reference to fig. 1 to 3 as an example.
Fig. 1 is a schematic architecture diagram of a communication system to which the present application may be applied. Fig. 1 is a schematic diagram of a 5G network architecture based on a service architecture. The 5G network architecture shown in fig. 1 may include three parts, which are a User Equipment (UE) part, a Data Network (DN) part, and an operator network part. Wherein the operator network may comprise one or more of the following network elements: a (radio) access network (R) AN, a User Plane Function (UPF) network element, AN authentication server function (AUSF) network element, AN NSACF network element, AN access and mobility management function (AMF) network element, AN SMF network element, a Network Slice Selection Function (NSSF) network element, a network open function (NEF) network element, a network function library function (NRF) network element, a Policy Control Function (PCF) network element, a Unified Data Management (UDM) network element, and AN Application Function (AF) network element. In the operator network described above, the parts other than the RAN part may be referred to as core network parts. User equipment, a radio access network, a UPF network element, an AUSF network element, an AMF network element, an SMF network element, a NEF network element, an NRF network element, a PCF network element, a UDM network element, an NSSF network element, an NSACF network element, and an AF network element are hereinafter referred to simply as UE, RAN, UPF, DN, AUSF, AMF, SMF, NEF, NRF, PCF, UDM, NSSF, NSACF, and AF, respectively.
In the network architecture, NSSF is a service-based interface presented by NSSF, nnef is a service-based interface presented by NEF, nrrf is a service-based interface presented by NRF, npcf is a service-based interface presented by PCF, numm is a service-based interface presented by UDM, naf is a service-based interface presented by AF, nausf is a service-based interface presented by AUSF, namf is a service-based interface presented by AMF, nsmf is a service-based interface presented by SMF, and NSACF is a service-based interface presented by NSACF. N1 is an interface between the UE and the AMF, and N2 is an interface between the RAN and the AMF and is used for sending NAS messages; n3 is an interface between RAN and UPF, and is used for transmitting data of a user plane; n4 is an interface between the SMF and the UPF, and is used to transmit tunnel identification information, data cache indication information, and downlink data notification information of the N3 connection, for example; the N6 interface is an interface between UPF and DN, and is used for transmitting data of a user plane; n9 is the interface between the UPF and the UPF.
The network elements involved in fig. 1 are briefly described below.
1、UE
The UE accesses the 5G network and obtains services mainly through a wireless air interface, interacts with the RAN through the air interface, and interacts with the AMF of the core network through non-access stratum signaling (NAS).
A UE in the embodiments of the present application may also be referred to as a terminal device, user, access terminal, subscriber unit, subscriber station, mobile station, remote terminal, mobile device, user terminal, wireless communication device, user agent, or user equipment. The UE may be a cellular phone, a smart watch, a wireless data card, a mobile phone, a tablet, a Personal Digital Assistant (PDA) computer, a wireless modem, a handheld device, a laptop, a Machine Type Communication (MTC) terminal, a computer with wireless transceiving function, a terminal of internet of things, a virtual reality terminal, an augmented reality terminal, a wearable device, a vehicle, a terminal in device-to-device (D2D) communication, a terminal in vehicle to object (V2X) communication, a terminal in machine-type communication (MTC), a terminal in internet of things (IOT), a terminal in smart office, a terminal in industrial control, a terminal in unmanned, a terminal in tele-operation, a terminal in smart grid, a terminal in transportation security, a terminal in smart terminal, a terminal in city, a terminal in satellite communication (e.g., a satellite phone or a satellite phone). The UE may also be a customer-premises equipment (CPE), a telephone, a router, a network switch, a home gateway (RG), a set-top box, a fixed mobile convergence product, a home network adapter, and an internet access gateway. The embodiments of the present application do not limit the specific technology and the specific device form adopted by the UE.
2. Access network device
The access network device in the present application may be a device for communicating with the UE, and is mainly responsible for radio resource management, quality of service management, data compression, and encryption functions on the air interface side. The access network device may be a base station (BTS) in a global system for mobile communications (GSM) system or a Code Division Multiple Access (CDMA) system, a base station (nodeB) in a Wideband Code Division Multiple Access (WCDMA) system, an evolved base station (eNB or eNodeB) in an LTE system, a base station in a Worldwide Interoperability for Microwave Access (WiMAX) communication system, a wireless controller in a cloud wireless access network (CRAN) scenario, a central access point, a relay station, a vehicle-mounted device, or a wearable device in a wireless fidelity (wireless fidelity) system. Or the access network device may be a terminal that assumes the function of a base station in D2D communication or machine communication. Or 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 a unit that performs part of the functions of the base station, for example, a Centralized Unit (CU) or a Distributed Unit (DU). The embodiment of the present application does not limit the specific technology and the specific device form adopted by the access network device.
3、UPF
The UPF is a user plane functional network element and supports all or part of the following functions: interconnecting a Protocol Data Unit (PDU) session with the DN; packet routing and forwarding (e.g., support forwarding traffic to DN after upstream classification (Uplink classifier), support Branching point (Branching point) to support multi-connection (multi-homed) PDU sessions); and detecting the data packet.
4、DN
The DN is the destination of the PDU session access for the user. The DN is an operator network providing a data transmission service for a user, for example, internet Protocol (IP) multimedia service (IMS), internet. The UE may access the DN by establishing a PDU session between the UE to the RAN to the UPF to the DN.
5、AUSF
The AUSF belongs to a core network control plane network element and is mainly responsible for authentication and authorization of a user to ensure that the user is a legal user.
6、AMF
The AMF is a mobility management function network element and is responsible for mobility management of users, including mobility state management, user temporary identity distribution, authentication and user authorization.
7、SMF
The SMF is a session management function network element and 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
The NEF belongs to a core network control plane network element and is responsible for opening the mobile network capability to the outside, and opening the network capability and service to the outside.
9、NRF
The NRF belongs to a core network control plane network element, and is responsible for the registration and discovery functions of the network element and maintains information of the network element, such as an instance identification, type, PLMN, slice-related identification, IP address or FQDN of the network element, capabilities of the network element, supported services.
10、PCF
The PCF comprises a policy control decision and a function based on flow charging control, and comprises a user subscription data management function, a policy control function, a charging policy control function and QoS control, and mainly supports the provision of a unified policy framework to control network behaviors, the provision of policy rules to a control layer network function, and the acquisition of user subscription information related to the policy decision.
11、UDM
The UDM belongs to a core network control plane network element, and the home subscriber server is responsible for managing subscription data and notifying a corresponding network element when the subscription data is modified.
12、NSSF
NSSF is responsible for the selection of network slices.
13、NSACF
The NSACF is responsible for admission control (admission control) of the network slice. For example, when a network slice needs to perform admission control, the NSACF may control the number of users accessed on each network slice. The maximum number of users (max number of UEs per network slice) allowed can be configured on the NSACF. When the number of users currently registered in a network slice is increased, the NSACF first determines whether the number of users currently accessed to the network slice reaches the maximum number of users under the network slice.
The NSACF may also be responsible for controlling the number of established sessions on each network slice. The maximum number of sessions (max number of PDU sessions per network slice) allowed per network slice may be configured on the NSACF. When the current session number of the network slice is increased, the NSACF first determines whether the currently established session number on the network slice reaches the maximum session number under the network slice.
14、AF
The AF is responsible for providing some application layer services to the UE, and when providing services to the UE, the AF has requirements on QoS (policy) and charging policy (charging), and needs to inform the network. Meanwhile, 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 may be applied. Fig. 2 is a schematic diagram of a 5G network architecture based on a point-to-point interface, and a main difference between fig. 2 and fig. 1 is that interfaces between network elements in fig. 2 are point-to-point interfaces, rather than serving interfaces, and descriptions of the network elements may refer to fig. 1, which is not described herein again.
Fig. 3 is another schematic architecture diagram of a communication system to which the present application may be applied. FIG. 3 is for a fifth generation communication system (5) th generation system,5 GS) and EPC/evolved universal terrestrial radio access network (e-UTRAN). Part of network elements of the EPC network and part of network elements of the 5G network may be deployed on the same physical entity, so that the EPS network and the 5G network may interact. For example, as shown in fig. 3, a Home Subscriber Server (HSS) network element and a Unified Data Management (UDM) network element may be deployed in the same physical entity. Control of packet data network gateway (PGW)A policy and provisioning function (PGW-C) and a Session Management Function (SMF) network element may be deployed in the same physical entity. A User plane function (PGW-U) and a User Plane Function (UPF) network element of a packet data network gateway (PGW) may be deployed in the same physical entity. The 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 a Mobility Management Entity (MME) and the 5GS AMF, and is used for implementing the interworking between the EPC and the 5G core network. Supporting the N26 interface is optional for implementing interworking between 5GS and EPC/E-UTRAN. N26 supports a subset of functions supported by S10 (basic functions of the interconnect). The HSS + UDM network element has a function of HSS and a function of UDM network element, and can store the subscription data of the user. 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 referred to as an HSS + UDM device or an HSS + UDM entity or an UDM + HSS network element or an UDM + HSS device or an UDM + HSS entity. The SMF + PGW-C network element has SMF and PGW-C functions, and the UPF + PGW-C network element has UPF network element and PGW-U functions. When establishing a PDN connection, a UE residing in the EPC may obtain a service of the 5G core network or a service of the EPC through SMF + PGW-C. The portion 5G referred to in fig. 3 may be as shown in fig. 1 or fig. 2.
It should be understood that the name of each network element shown in fig. 1 to 3 is only a name, and the name does not limit the function of the network element itself. In different networks, the network elements may also be given other names, and this embodiment of the present application is not limited to this specific name. For example, in a 6G network, some or all of the above network elements may use the terminology in 5G, or may use other nomenclature, and so on, which are described herein in a unified manner and will not be described again below. Similarly, the interfaces between the network elements shown in fig. 1 to 3 are only an example, and in a 5G network and other networks in the future, the interfaces between the network elements may not be the interfaces shown in the figures, which is not limited in this application. It should also be understood that the embodiments of the present application are not limited to the system architectures shown in fig. 1-3. For example, a communication system to which the present application may be applied may comprise more or fewer network elements or devices. The devices or network elements in fig. 1 to 3 may be hardware, or may be functionally divided software, or a combination of the two. The devices or network elements in fig. 1 to 3 may communicate with each other via other devices or network elements.
In 5G communication systems, network slices are introduced. The network slice is based on a logic concept, and is used for recombining resources, so that a plurality of logic subnets with different characteristics and isolated from each other can be virtually simulated on the same set of physical facilities to provide services for users in a targeted manner. Different logical subnets are identified and distinguished by a single network slice selection assistance information (S-NSSAI). In the actual deployment scenario of network slices, the number of users that can accommodate access and the number of sessions that support establishment is limited for one network slice due to network resource limitations.
According to the current 5G standard, if a network slice needs to perform admission control, then admission control can be performed on that network slice through the NSACF. For example, the NSACF performs admission control on the number of UEs accessed by a network slice or on the number of sessions established by a network slice. Specifically, for example, the number of UEs accessed to a network slice by an NSACF is subjected to admission control, a quota (quota) of the network slice and the number of users currently accessed to the network slice can be configured on the NSACF, and the number of UEs accessed to the network slice is controlled in a registration or de-registration process of the UEs. Taking the example of controlling the number of UEs accessing a network slice in a registration procedure, a UE may carry a requested NSSAI (requested NSSAI); the AMF determines whether the requested NSSAI includes a network slice requiring performing Network Slice Admission Control (NSAC), and if the requested NSSAI includes a network slice requiring performing NSAC, the AMF may determine a target NSSAI (target NSSAI), where the target NSSAI is a set of all network slices that the UE requests to access and requires performing NSAC; and the AMF interacts with a NSACF network element, and triggers the NSACF to judge whether the quota of the current network slice can allow the UE to access the network slice. If the current quota of a certain network slice contained in the target nsasi is still available, the UE may access the network slice, and at the same time, the NSACF counts the number of users of the network slice whose quota is available, the NSACF returns indication information of "quota available" to the AMF, and the network slice of the AMF "quota available" is contained in an allowed nsai (allowed nsai); if the current quota of a certain network slice contained in the target NSSAI is not available, the UE may not access the network slice, the NSACF returns an indication message of "no quota available" to the AMF, and the network slice of the AMF "no quota available" is contained in the rejected NSSAI (rejected NSSAI). Similarly, the number of sessions established by a network slice may also be controlled by the NSACF. Specifically, the NSACF may configure a quota of a network slice and store a number of sessions currently established in the network slice, and the NSACF may control the number of sessions established in the network slice in a PDU session management procedure of the UE, where a specific procedure is similar to a procedure for controlling the number of UEs accessed to the network slice, and is not described again.
It is 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 fig. 3, when the UE initiates a PDN connection establishment procedure, the PDN connection may be associated with a core network element of a certain network slice, such as SMF + PGW-C, and it can also be understood that the UE may establish the PDN connection using a network slice resource of SMF + PGW-C; when UE initiates a PDN connection release process, resources of SMF + PGW-C associated with the PDN connection are released. When initiating a PDN connection establishment procedure or a PDN connection release procedure, a UE residing in the EPC may trigger control of the number of UEs accessing the network slice and the number of sessions established for the network slice at the same time. In this case, how to control the number of users accessing 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 method and an apparatus for controlling admission of a network slice, which can implement control over the number of users accessing the network slice and the number of sessions established in the network slice, and facilitate admission control of the network slice.
Before describing the technical solutions of the present application, terms related to the present application will be described first.
The quota of the number of UEs of a network slice shown in this application may also be understood as: the number of UEs accessed by the network slice, or the maximum value of the number of UEs accessed by the network slice, or the number of UEs allowed to be registered by the network slice. The quota of the number of UEs of the network slice is not available, which can also be understood as: the quota of the number of the UEs in the network slice is exceeded, or the number of the UEs accessed to the network slice exceeds the quota, or the number of the UEs accessed to the network slice exceeds the maximum value, or the number of the UEs accessed to the network slice reaches the maximum number of the UEs allowed to be accessed, or the number of the UEs accessed to the network slice is greater than or equal to a preset threshold. The quota of the number of UEs in the network slice is available, which can also be understood as: the number of the UEs accessed to the network slice does not exceed the maximum number, or the number of the UEs accessed to the network slice does not reach the maximum number of UEs allowed to be accessed, or the number of the UEs accessed to the network slice is less than or equal to a preset threshold, or the number of the UEs accessed to the network slice is less than the preset threshold.
Similarly, the quota of the number of sessions of the network slice shown in the present application may also be understood as: the number of sessions that the network slice has established, or the maximum value of the number of sessions that the network slice has established, or the number of sessions that the network slice allows to establish, or the number of PDN connections that the network slice allows to establish. The quota of the number of sessions of the network slice is not available, and can be understood as follows: the quota of the number of sessions of the network slice is exceeded, or the number of sessions allowed to be established by the network slice exceeds the quota, or the number of sessions established on the network slice exceeds the maximum value, or the number of sessions established by the network slice reaches 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 a preset threshold value, or the number of sessions established by the network slice is greater than the preset threshold value. The quota of 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 number of sessions established by the network slice is smaller than a preset threshold, or the number of sessions established by the network slice is smaller than or equal to the preset threshold.
In this application, it may be shown that the number of users accessing the network slice fails to be controlled or counted, or the number of users accessing the network slice does not change, or the number of users accessing the network slice maintains the original value, or the number of users accessing the network slice fails to be updated. Similarly, the failure of controlling or counting the number of sessions established on the network slice may indicate that the number of sessions established on the network slice is not changed, or the number of sessions established on the network slice maintains the original value, or the number of sessions established on the network slice fails to be updated.
It should be noted that, in the present application, the number of users accessed to a network slice may also be described as the number of users already accessed to the network slice or the number of users corresponding to the network slice. The number of sessions established in a network slice may also be described as the number of sessions established in a network slice or the number of sessions corresponding to a network slice. The session of the present application may be a PDU session or a PDN connection. The following describes a network slice admission control method provided by the present application.
Fig. 4 is a schematic flow chart 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, and may also 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 an execution subject as a first network element and a second network element as an example.
In the method shown in fig. 4, a network element that performs control of the number of users accessing a network slice (hereinafter referred to as a first network element, e.g., NSACF _1 that performs control of the number of users accessing a network slice) and a network element that performs control of the number of sessions established on a network slice (hereinafter referred to as a third network element, e.g., NSACF _2 that performs control of the number of sessions established on an access network slice) are different.
In step 401, the second network element determines a 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, which may be understood as associating the first session to the second network element when establishing the first session, or establishing the first session through a network slice resource 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.
In a possible implementation manner, the first session is a PDN connection, and the second network element is SMF + PGW-C. Specifically, the SMF + PGW-C may determine a network slice associated with the PDN connection according to an Access Point Name (APN) carried in a session creation request message received in the PDN connection establishment procedure.
Step 402, the second network element sends the first information to the first network element. Accordingly, the first network element receives the first information from the second network element.
The first network element supports control over the number of users accessing the network slice. The first network element supports controlling the number of users accessing the network slice, which can also be described as that the first network element supports counting the number of UEs accessing the network slice or that the first network element has the capability of controlling the number of users accessing the network slice. The first information is used for associating with the first session of the user equipment, and may also be described as the first information being information related to the first session of the user equipment. As one example, the first information is used to identify the first session, e.g., the first information may include at least one of an identification of the first session or an identification of the second network element. The identifier of the second network element may be an 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.
Alternatively, the first network element may be an NSACF, and the second network element may be an SMF + PGW-C.
The application does not limit the time when the second network element sends the first information.
In some implementations, the second network element may send the first information to the first network element in a process of requesting to increase the number of users having accessed the network slice determined in step 401. For example, in the process of controlling the number of UEs and the number of sessions triggered by the establishment of the PDN connection, the second network element may interact with the first network element that supports controlling the number of users accessing the network slice, trigger the first network element to increase the number of users accessing the network slice, and send the first information to the first network element in the process of interacting with the first network element; and if the number of the users accessing the network slice is not excessive, the second network element interacts with a third network element supporting the execution control of the number of the sessions established on the network slice, and triggers the third network element to increase the number of the sessions established on the network slice. In this example, if the second network element learns from the third network element that the session number control is successful, the second network element may no longer interact with the first network element, which may reduce signaling overhead.
In other implementations, the second network element may send a 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 value of the number of sessions allowed to be established by the network slice, and the second request message carries the first information. For example, in the process of controlling the number of UEs and the number of sessions triggered by the establishment of the PDN connection, the second network element may 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 excessive, the second network element interacts with a third network element supporting the execution control of the number of sessions established on the network slice, and triggers the third network element to increase the number of sessions established on the network slice; if the second network element knows that the session number control is successful from the third network element, the second network element may send a second request message to the first network element, and the second request message carries the first information, so that the first network element stores the first information.
The 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 controlling the number of sessions established on the network slice, which can also be described as that the third network element supports counting the number of sessions established on the network slice or that the third network element has the capability of controlling the number of sessions established on the network slice.
In other implementation manners, after receiving the first information, the first network element may further store the corresponding relationship between the first information, the network slice, and the user equipment.
In step 403, the second network element sends a first request message to the first network element. Accordingly, the first network element receives a first request message from a second network element.
Wherein the first request message is used for indicating to reduce the number of users having access to the network slice.
Alternatively, the first request message may be an nsacf _ numberofuesresviceaavailability check and updated request.
The application does not limit the time when the second network element sends the first request message.
In some implementations, 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 performs control on the number of users having access to the network slice. For example, after the PDN connection is successfully established, the PDN connection is released at a certain time, and in a control process of the number of UEs and the number of sessions triggered by the PDN connection release, the second network element may interact with a third network element that supports performing control on the number of sessions established on the network slice, and trigger the third network element to reduce the number of sessions established on the network slice; the second network element may also send a first request message to a first network element that supports controlling the number of users accessing the network slice, and trigger the first network element to reduce the number of sessions established on the network slice.
In 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 on the network slice fails in the PDN connection establishment procedure, so that the first network element performs control on the number of users having access to the network slice. For example, in the process of controlling the number of UEs and the number of sessions triggered by the establishment of the PDN connection, the second network element may 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 excessive, the second network element interacts with a third network element supporting the execution control of the number of sessions established on the network slice, and triggers 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 session number control fails, the second network element may send a first request message to a first network element that supports controlling the number of users accessing the network slice, and trigger the first network element to reduce the number of users established on the network slice.
And step 404, the first network element determines whether to reduce the number of users having access to the network slice according to the first information.
In some implementations, 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 a correspondence relationship between the user equipment, the network slice, and a session established by the user equipment in the network slice, and the first network element may determine whether the user equipment has a session other than the first session in the network slice according to whether the correspondence relationship exists. If the user equipment establishes a session on the network slice except the first session, the first network element determines to maintain the number of users accessing the network slice, namely the first network element determines not to reduce the number of users accessing the network slice. If the user equipment only establishes the first session on the network slice, the first network element determines that the number of users having access to the network slice can be reduced.
In other implementations, the first network element may further delete the first information after receiving the first request message or after determining whether to reduce the number of users that have accessed the network slice. That is, the first network element may delete the first information regardless of whether the first network element determines to reduce the number of users that have accessed the network slice or to maintain the number of users that have accessed the network slice.
It should be noted that, for the first network element, whether the user equipment establishes a session on the network slice may be understood as whether the first network element stores related information of the session, such as an identifier of the session or an identifier of a session management network element serving the session.
Optionally, the first request message may further carry first information, so that the first network element determines a 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.
In the above technical solution, the second network element sends the information related to the session to the first network element, so that the first network element stores a corresponding relationship between the user equipment, the network slice, and the information related to the session, and when the first network element receives an instruction to decrease the number of users accessing the network slice, it may determine whether the number of users accessing the network slice may be decreased according to the corresponding relationship. This may enable network slice admission control.
Fig. 5 is a schematic flow chart 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 execution subject as the second network element, the fourth network element, and the NRF as an example.
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 a fourth network element. In other words, the fourth network element can control both the number of users accessing the network slice and the number of sessions established on the network slice.
In step 501, a second network element determines a network slice associated with a first session of a user equipment.
Wherein the second network element serves the first session.
The second network element serves the first session, which may be understood as associating the first session to the second network element when establishing the first session, or establishing the first session through a network slice resource of 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.
In a possible implementation manner, the first session is a PDN connection, and the second network element is SMF + PGW-C. Specifically, the SMF + PGW-C may determine a network slice associated with the PDN connection according to an APN carried in a session creation request message received in the PDN connection establishment procedure.
Step 502, the second network element sends a third request message to the NRF. Accordingly, the NRF receives a third request message from the second network element.
Wherein the third request message is used for requesting information of the fourth network element.
Optionally, the third request message comprises an identification of the network slice and the second information. The second information is used for indicating that a fourth network element requested by the second network element supports the execution control of the number of users accessing the network slice and the execution control of the number of sessions established on the network slice. The second information, which may also be referred to as network element capability information, is used to indicate that the second network element requests a fourth network element that has the capability to control the number of users accessing the network slice and to control the number of sessions established on the network slice.
In some implementations, the second network element may send the third request message in the process of establishing the PDN connection.
In one possible implementation, the second network element may invoke a servitization operation nrrf _ NFDiscovery request of the NRF.
Alternatively, 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. Accordingly, the second network element receives a 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 control over the number of users accessing the network slice and control over the number of sessions established on the network slice.
In one possible implementation, the NRF may send an nrrf _ NFDiscovery response to the second network element.
In step 504, the second network element sends a fourth request message to the fourth network element. Accordingly, the fourth network element receives a fourth request message from the second network element.
The fourth request message is used for requesting 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 from the third response message.
In some implementations, the fourth request message includes an identification of the user equipment, the first information, the third information, the fourth information, and an identification of the network slice. The first information is used for associating with the first session of the user equipment, and the detailed description of the first information may refer to step 402, which is not described herein again. When the user equipment requests to establish the first session, the third information is used for indicating the number of users who have access to the network slice, and the fourth information is used for indicating the number of sessions established in the network slice. When the user equipment requests to release the first session, the third information is used for indicating the number of users having access to the network slice to be reduced, and the fourth information is used for indicating the number of sessions established in the network slice to be reduced.
In a possible implementation manner, the second network element sends an nsacf _ numberofuesriservice availabilitycheck andupdate request to the fourth network element, or the second network element sends an nsacf _ numberofpdusperselailabilitycheck andupdate request to the fourth network element.
And 505, the fourth network element performs admission control on the network slice according to the fourth request message.
In some implementations, the performing, by the fourth network element, 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 may also be referred to as performing counting of the number of UEs and counting of the number of sessions, so as to ensure that the total number of UEs currently accessed to the network slice does not exceed the maximum number/number of terminal devices allowed to be accessed by the network slice, and ensure that the total number of sessions currently established on the network slice does not exceed the maximum number/number of sessions allowed to be established by the network slice. The fourth network element may store the number of users currently accessing the network slice, or store a UE identifier list currently accessing the network slice, where an identifier in the UE identifier list is used to identify a UE currently accessing the network slice. The fourth network element may also save the number of sessions that have currently been established in the network slice. The fourth network element may further configure a maximum value of the number of users allowed to be accessed by the network slice and a maximum value of the number of sessions allowed to be established by the network slice, that is, the fourth network element may configure the number of the maximum number of users allowed to be accessed by the network slice and the number of the maximum number of sessions allowed to be established by the network slice.
When the user equipment requests to establish the first session, the third information is used for indicating the number of users having access to the network slice to be increased, and the fourth information is used for indicating the number of sessions established in the network slice to be increased. The fourth network element judges whether the number of users accessing the network slice exceeds the maximum number of users allowed to be accessed by the network slice, and judges whether the number of sessions established on the network slice exceeds the maximum number of sessions allowed to be established 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 be accessed by the network slice, and the ID of the user equipment is not stored in the user equipment identifier list to which the network slice has been accessed, 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 user equipment identifier list to which the network slice has been accessed, thereby saving the correspondence between the ID of the user equipment and the network slice, and meanwhile, the fourth network element determines that the number of sessions corresponding to the network slice does not exceed the maximum number of sessions allowed to be established by the network slice, and the fourth network element may increase the number of sessions corresponding to the network slice according to the fourth information and save the correspondence 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 be accessed by 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 number of users corresponding to the network slice and the number of sessions corresponding to the network slice.
When the user equipment requests to release the first session, the third information is used for indicating the reduction of the number of users accessing the network slice, and the fourth information is used for indicating the reduction of the number of sessions established in 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 a correspondence relationship between the user equipment, the network slice, and a session established by the user equipment in the network slice, and the first network element may determine whether the user equipment has a session other than the first session in the network slice according to whether the correspondence relationship exists. If the user equipment establishes a session on the network slice except the first session, the first network element determines to maintain the number of users accessing the network slice, namely the first network element determines not to reduce the number of users accessing the network slice. If the user equipment only establishes the first session on the network slice, the first network element determines that the number of users having access to the network slice can be reduced.
Step 506, the fourth network element sends a fourth response message to the second network element. Accordingly, the second network element receives a fourth response message from the fourth network element.
Wherein the fourth response message is used to indicate a result of performing admission control on the network slice. The results may include: the admission control performed on the network slice is successful or the admission control performed on the network slice is failed. And if the second network element judges that the number of the users accessing the network slice does not exceed the maximum number of the users allowed to be accessed by the network slice and the number of the sessions established on the network slice does not exceed the maximum number of the sessions allowed to be established by the network slice, the network slice successfully executes the admission control. It can be understood from the above description that if the admission control performed on the network slice is successful, it indicates that the counting of the number of performing UEs and the counting of the number of performing sessions are both successful. If the second network element judges that the number of users accessing the network slice exceeds the maximum number of the users allowed to be accessed by the network slice, but the number of the sessions established on the network slice does not exceed the maximum number of the sessions allowed to be established by the network slice, the network slice fails to execute 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 to be accessed by the network slice, but the number of sessions established on the network slice exceeds the maximum number of sessions allowed to be established by the network slice, the network slice fails to execute admission control; and if the second network element judges that the number of the users accessing the network slice exceeds the maximum number of the users allowed to be accessed by the network slice, but the number of the sessions established on the network slice exceeds the maximum number of the sessions allowed to be established by the network slice, the network slice fails to execute the admission control. It can be understood from the above description that, if performing admission control on a network slice fails, it indicates that performing counting of the number of UEs fails and/or performing counting of the number of sessions fails, then the fourth response message may further carry a failure cause value, if the user equipment requests to establish a first session, the failure cause value may be whether the number of users accessing the network slice exceeds the maximum number of users allowed to access the network slice and/or whether the number of sessions established on the network slice exceeds the maximum number of sessions allowed to be established by the network slice, and 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.
Also, the first session in fig. 5 may also be a PDU session, and the second network element may also be an SMF, i.e. the method shown in fig. 5 is also applicable to a 5G communication system.
In the above technical solution, a process of discovering a fourth network element by a second network element is enhanced, and specifically, the second network element requests an NRF to select the fourth network element for which the NRF simultaneously supports controlling the number of UEs accessing a network slice and controlling the number of sessions established on a control network slice. Secondly, when determining the number of users and the number of sessions corresponding to the network slice, the fourth network element may further determine whether the user equipment has accessed the network slice or whether the sessions of the user equipment should be released. Thus, network slice admission control in an interworking scenario can be achieved.
The technical solution of the present application is described in detail below with reference to specific examples.
Example 1
In example 1, a UE initiates an establishment procedure (PDN connection establishment) for establishing multiple PDN connections, and the multiple PDN connections are associated with a same network slice, and an NSACF responsible for quota management of the number of UEs of the network slice and an NSACF responsible for quota management of the number of sessions of the network slice are the same NSACF. Fig. 6 takes the UE establishing 2 PDN connections as an example.
Fig. 6 is an example of a network slice admission control method provided by the present application. The SMF + PGW-C _1 and SMF + PGW-C _2 in fig. 6 may correspond to the second network element in fig. 5 above, and the NSACF may correspond to the fourth network element in fig. 5 above.
Step 601, UE initiates a PDN connection establishment flow.
In a possible implementation manner, UE sends a PDN connection establishment request message (PDN connectivity request) to MME, where the message may carry an APN; after receiving the PDN connection establishment request message, the MME selects a Serving Gateway (SGW) and an SMF + PGW-C network element according to the APN and the location of the UE carried in the message; the MME sends a create session request message (create session request) to the SGW, and then the SGW sends the create session request message to the selected SMF + PGW-C. For convenience of description, the PDN connection will be referred to as PDN connection _1, and the selected SMF + PGW-C will be 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, the SMF + PGW-C _1 determines a network slice associated with the PDN connection according to the APN carried in the create session request message.
Step 603, SMF + PGW-C _1 determines whether the network slice needs to execute NSAC flow according to the configuration information.
In one possible implementation, the SMF + PGW-C _1 stores configuration information of the network slice that needs to execute NSAC. After the SMF + PGW-C _1 determines the network slice associated with the PDN connection, the SMF + PGW-C _1 determines whether the network slice needs to perform the NSAC procedure according to the configuration information.
If the SMF + PGW-C _1 determines that the network slice needs to perform the NSAC process, then steps 604-608 may be continued. If the SMF + PGW-C _1 determines that the network slice does not need to perform the NSAC procedure, steps 604-608 can be skipped and step 609 can be performed directly.
Step 604, SMF + PGW-C _1 sends a third request message _1 to NRF.
Wherein the third request message _1 is for requesting an NSACF that serves a network slice associated with the PDN connection _1, supports control over the number of UEs accessing the network slice, and supports control over the number of sessions established on the network slice. As an example, the third request message _1 may carry S-nsasi and NSACF service capability indication information (NSACF service capability) for identifying the network slice, where the NSACF service capability indication information is used to indicate that the NSACF + PGW-C _1 requested NSACF supports performing control on the number of UEs accessing the network slice and supports performing control on the number of sessions established on the control network slice, i.e., the second information described in fig. 5.
It should be noted that, the NSACF supports performing control on the number of UEs in the access network slice, which may also be described as the NSACF having the capability of controlling the number of UEs in the access network slice, and the same is described below as the NSACF supporting performing control on the number of UEs in the access network slice. The NSACF supports performing control on the number of sessions established on the control network slice, which may also be described as an NSACF having the capability of controlling the number of sessions established on the network slice, and the same description is hereinafter described as an NSACF supporting performing control on the number of sessions established on the control network slice.
In one possible implementation, the SMF + PGW-C _1 may call a servitization operation nrrf _ NFDiscovery request of the NRF.
In step 605, the nrf sends a third response message _1 to SMF + PGW-C _1 according to the third request message _1.
Wherein, the third response message _1 carries the relevant information of the NSACF. The information related to the NSACF may include an address of the NSACF. The NSACF is an NSACF serving the network slice identified by the S-NSSAI carried in the third request message _1, and the NSACF simultaneously supports control over the number of UEs accessing the network slice identified by the S-NSSAI and supports control over the number of sessions established on the network slice identified by the S-NSSAI.
In one possible implementation, the NRF returns nrrf _ NFDiscovery response to the SMF + PGW-C _1, which carries information of the NSACF, such as address information of the NSACF.
Optionally, SMF + PGW-C _1 holds the information of the NSACF returned by the NRF in context.
Step 606, SMF + PGW-C _1 determines NSACF according to the third response message _1, and sends a fourth request message _1 to the NSACF.
The fourth request message _1 may carry the UE ID, the update flag _1 (update _ flag _ 1), the S-NSSAI, the update flag _2 (update _ flag _ 2), and the session _1 related information. The UE ID may be determined by the SMF + PGW-C _1 according to the create session request message, for example, the create session request message carries the UE ID, and the UE ID may be a permanent identifier of the UE, for example, an International Mobile Subscriber Identity (IMSI). The update flag _1 is used to indicate that the number of UEs corresponding to the network slice identified by the S-NSSAI is increased, e.g., the number of UEs is increased 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 increased, e.g., the number of sessions is increased by 1. The information related to session _1 may include an identifier of SMF + PGW-C _1 and/or an identifier of session _1, where the identifier of SMF + PGW-C _1 may be an 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 manner is that SMF + PGW-C _1 sends an NSACF _ numberofpdusperserviceavailabilitycheckaddupdate request to the NSACF, or SMF + PGW-C _1 sends an NSACF _ numberofuespiesvicesavailackandupdate request to the NSACF, which is not limited in this application.
Step 607, nsacf performs admission control on the network slice according to the fourth request message _1.
In one possible implementation, performing admission control on a network slice by the NSACF includes performing admission control on the number of UEs on the network slice and performing admission control on the number of sessions on the network slice, which may also be referred to as performing counting of the number of UEs (number of UEs counting) and counting of the number of sessions (number of sessions counting), so as to ensure that the sum of the number of UEs currently having access to the network slice does not exceed the maximum number of terminal devices allowed to be accessed by the network slice, and ensure that the sum of the number of sessions currently having been established on the network slice does not exceed the maximum number of sessions allowed to be established by the network slice. The NSACF may store the number of UEs currently accessing the network slice, or store a UE identity list of UEs currently accessing the network slice, where the identity in the UE identity list is used to identify the UE currently accessing the network slice. The NSACF may also keep the number of sessions that have currently been established on a network slice. The NSACF may also configure a maximum value of the number of UEs allowed to be accessed by the network slice and a maximum value of the number of sessions allowed to be established by the network slice, that is, the NSACF may configure the number of the maximum number of users allowed to be accessed by the network slice and the number of the maximum number of sessions allowed to be established by the network slice.
For example, the NSACF determines whether a quota of a corresponding number of UEs for the network slice identified by the S-NSSAI is available (i.e., whether the number of UEs currently accessing the network slice identified by the S-NSSAI exceeds a maximum number), and whether a quota of a corresponding number of sessions for the network slice identified by the S-NSSAI is available (i.e., whether the number of sessions currently established for the network slice identified by the S-NSSAI exceeds a maximum number). If the NSACF determines that the quota of the number of UEs corresponding to the network slice identified by the S-NSSAI is available, and meanwhile the UE ID is not stored in the UE identity list to which the network slice identified by the S-NSSAI has been accessed, the NSACF 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 is increased by 1) according to the update flag _1, and adds the UE ID to the UE identity list to which the network slice has been accessed, thereby saving the corresponding relationship between the UE ID and the S-NSSAI. The NSACF further determines that a quota of the session number of the network slice identified by the S-NSSAI is available, and the NSACF increases the session number corresponding to the network slice according to the update flag _2 (for example, the session number established in the network slice identified by the S-NSSAI is increased by 1), and stores the corresponding relationship between the information related to the session _1 and the S-NSSAI. If the quota of the number of UEs corresponding to the network slice identified by the S-NSSAI is unavailable and/or the quota of the number of sessions is unavailable, 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 of counting the number of UEs executed by the NSACF and counting the number of sessions executed by the NSACF. For example, counting the number of UEs and then counting the number of sessions may be performed, in this case, if the NSACF determines that the quota of the number of sessions is not available after determining that the quota of the number of UEs corresponding to the network slice identified by the S-nsai is available and adds one to the number of UEs, the NSACF updates the number of UEs after determining that the quota of the number of sessions is not available, that is, the NSACF decreases the number of UEs by one and deletes the UE ID from the identification list of the terminal device to which the network slice has access. For another example, the counting of the number of sessions may be performed first and then the counting of the number of UEs may be performed, in which case, if the NSACF determines that the quota of the number of UEs is not available after determining that the quota of the number of sessions corresponding to the network slice identified by the S-nsai is available and adding one to the number of sessions, the NSACF updates the number of sessions after determining that the quota of the UEs is not available, that is, the NSACF decreases the number of sessions by one. For another example, the number of UEs and the number of sessions may be counted at the same time, and in this case, the NSACF may integrate the determination result of the quota of the number of UEs and the determination result of the quota of the number of sessions, and update the number of UEs and the number of sessions collectively.
Since fig. 6 illustrates the establishment of 2 PDN connections, in this case, the 1 st PDN connection is established, so the NSACF increases the number of UEs corresponding to the network slice (for example, the number of UEs accessing the network slice identified by S-NSSAI is added by 1) and increases the number of sessions corresponding to the network slice (for example, the number of sessions established in the network slice identified by S-NSSAI is added by 1), and stores the corresponding relationship of the information related to the UE ID, S-NSSAI, and session _1.
In step 608, the NSACF sends a fourth response message _1 to the 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 results may include: the admission control performed on the network slice is successful or the admission control performed on the network slice is failed. If the admission control performed on the network slice is successful, it indicates that the counting of the number of the executed UEs and the counting of the number of the executed sessions are both successful, and if the admission control performed on the network slice is failed, it indicates that the counting of the number of the executed UEs and/or the counting of the number of the executed sessions are failed, then the fourth response message _1 may further carry a failure cause value, where the failure cause value may be used to indicate that the number of UEs that the network slice has accessed has reached the maximum value and/or indicate that the number of sessions that the network slice has established has reached the maximum value. In this example, the fourth response message _1 may indicate that performing admission control on the network slice was successful.
One possible implementation manner is that the NSACF sends NSACF _ numberofpdusperseliceavailabilitycheckaddupdate response to the SMF + PGW-C _1, or the NSACF sends NSACF _ numberofuesrislaceavailabilitycheckaddupdate response to the SMF + PGW-C _1, which is not limited in this application, and the NSACF carries a result of performing admission control on a network slice in a sent message.
Step 609, execute the rest flows of PDN connection establishment.
Thus, the establishment of PDN connection _1 is completed, and the NSACF stores the correspondence between the UE ID, S-NSSAI, and information related to session _1.
In step 610, the ue initiates the PDN connection establishment procedure.
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 is not described herein again. For convenience of description, the PDN connection is hereinafter referred to as PDN connection _2, and the selected SMF + PGW-C is referred to as SMF + PGW-C _2.
Step 611, SMF + PGW-C _2 determines the network slice associated with the PDN connection.
In a possible implementation manner, the SMF + PGW-C _2 determines a network slice associated with the PDN connection according to the APN carried in the create session request message.
The network slice determined in step 611 is the same as the network slice determined in step 603.
Step 612, SMF + PGW-C _2 determines whether the network slice needs to execute the NSAC process according to the configuration information.
In one possible implementation, the SMF + PGW-C _2 stores configuration information of the network slice that needs to execute NSAC. After the SMF + PGW-C _2 determines the network slice associated with the PDN connection, the SMF + PGW-C _2 determines whether the network slice needs to perform the NSAC procedure according to the configuration information.
If the SMF + PGW-C _2 determines that the network slice needs to perform the NSAC procedure, then steps 613-617 may be continued. If the SMF + PGW-C _2 determines that the network slice does not need to perform the NSAC procedure, step 613-617 may be skipped and step 618 may be performed directly.
Step 613, SMF + PGW-C _2 sends a third request message _2 to NRF.
Wherein the third request message _2 is for requesting an NSACF that serves a network slice associated with the PDN connection _2 and supports control over the number of UEs accessing the network slice and control over the number of sessions established on the network slice. As an example, the third request message _2 may carry S-nsasi and NSACF service capability indication information for identifying the network slice, the NSACF service capability indication information being used to indicate that the SMF + PGW-C _2 requested NSACF supports both control of the number of UEs accessing the network slice identified by the S-nsai and control of the number of sessions established on the network slice identified by the S-nsai.
In one possible implementation, the SMF + PGW-C _2 may call a servitization operation nrrf _ NFDiscovery request of the NRF.
In 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 the relevant information of the NSACF. The information related to the NSACF may include an address of the NSACF. The NSACF is an NSACF serving the network slice identified by the S-NSSAI carried in the third request message _2, and the NSACF simultaneously supports control over the number of UEs accessing the network slice identified by the S-NSSAI and supports control over 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 one possible implementation, the NRF returns nrrf _ NFDiscovery response to the SMF + PGW-C _2, which carries information of the NSACF, such as address information of the NSACF.
Optionally, SMF + PGW-C _2 saves the information of the NSACF returned by the NRF in context.
Step 615, SMF + PGW-C _2 determines NSACF according to the third response message _2, and transmits a fourth request message _2 to the NSACF.
The fourth request message _2 may carry information related to the UE ID, the update flag _1, the S-NSSAI, the update flag _2, and the session _2. The UE ID may be determined by the SMF + PGW-C _2 according to the create session request message, for example, the create session request message carries the UE ID, which may be, for example, the IMSI of the UE. The update flag _1 is used to indicate that the number of UEs corresponding to the network slice identified by the S-NSSAI is increased, e.g., the number of UEs is increased 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 increased, e.g., the number of sessions is increased by 1. The information related to session _2 may include an identifier of SMF + PGW-C _2 and/or an identifier of session _2, where the identifier of SMF + PGW-C _2 may be an 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 manner is that SMF + PGW-C _2 sends an NSACF _ numberofpdusperserviceavailabilitycheckaddupdate request to the NSACF, or SMF + PGW-C _2 sends an NSACF _ numberofuespiesvicesavailackandupdate request to the 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 one possible implementation, performing admission control on a network slice by the NSACF includes performing admission control on the number of UEs on the network slice and performing admission control on the number of sessions on the network slice, which may also be referred to as performing counting of the number of UEs and counting of the number of sessions.
Specifically, the NSACF determines whether a quota of a corresponding number of UEs for the network slice identified by the S-NSSAI is available (i.e., whether the number of UEs currently accessing the network slice identified by the S-NSSAI exceeds a maximum number), and determines whether a quota of a corresponding number of sessions for the network slice identified by the S-NSSAI is available (i.e., whether the number of sessions currently established for the network slice identified by the S-NSSAI exceeds a maximum number). The NSACF determines, according to the correspondence between the UE ID and the S-NSSAI stored in the context information (i.e., the correspondence between the UE ID and the S-NSSAI stored in step 607), that the UE ID is already stored in the UE identity list to which the network slice identified by the S-NSSAI has been accessed, which indicates that the UE has already been accessed to the network slice identified by the S-NSSAI, in this case, the NSACF does not need to count the number of UEs corresponding to the network slice, i.e., the number of UEs of the network slice remains unchanged, and at the same time, the NSACF determines that a quota of the session number of the network slice identified by the S-NSSAI is available, and increases the session number corresponding to the network slice according to the update flag _2 (e.g., the session number established in the network slice identified by the S-NSSAI is incremented by 1), and stores the information related to the session _2 and the correspondence between the S-NSSAI. If the quota of the number of UEs corresponding to the network slice identified by the S-NSSAI is unavailable and/or the quota of the number of sessions is unavailable, the NSACF may not change the number of UEs corresponding to the network slice and the number of sessions corresponding to the network slice.
Also, the present application does not limit the order of the counting of the number of UEs executed by the NSACF and the counting of the number of sessions executed. For specific description, reference may be made to the above description, which is not repeated herein.
Since fig. 6 takes the establishment of 2 PDN connections as an example, in this case, 2 nd PDN connection is established, the NSACF keeps the number of UEs corresponding to the network slice unchanged, increases the number of sessions corresponding to the network slice, and continues to store the corresponding relationship between the UE ID, 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 results may include: the admission control performed on the network slice is successful or the admission control performed on the network slice is failed. If the admission control is successfully executed on the network slice, the counting of the number of the executed UE and the counting of the number of the executed sessions are both successful. If the admission control performed on the network slice fails, which indicates that the counting of the number of UEs performed fails and/or the counting of the number of sessions performed fails, the fourth response message _2 may further carry a failure cause value, for example, the failure cause value is used to indicate that the number of UEs to which the network slice has access has reached the maximum value and/or indicate that the number of sessions to which the network slice has been established has reached the maximum value. In this example, the fourth response message _2 may indicate that performing admission control on the network slice was successful.
A possible implementation manner is that the NSACF sends NSACF _ numberofpdusperseliceavailabilitycheckaddupdate response to the SMF + PGW-C _2, or the NSACF sends NSACF _ numberofuesrislaceavailabilitycheckaddupdate response to the SMF + PGW-C _2, which is not limited in this application, and the NSACF carries a result of performing admission control on a network slice in a sent message.
In step 618, the remaining procedure of PDN connection establishment is performed.
The establishment of PDN connection _1 and PDN connection _2 is completed, and the NSACF stores the correspondence between the UE ID, the S-NSSAI, the information related to session _1, and the information related to session _2.
As can be seen from the above, for the determination procedure of the number of UEs and the number of sessions triggered by the establishment of PDN connection, in example 1, the procedure of discovery of an NSACF by the SMF + PGW-C is first enhanced, specifically, the SMF + PGW-C requests the NRF to select an NSACF for which the control is simultaneously supported for the number of UEs accessing the network slice and for the number of sessions established on the control network slice. Secondly, when the number of UEs and the number of sessions corresponding to the network slice are determined, the NSACF may also determine whether the UE has accessed the network slice, and if the UE has accessed the network slice, the number of UEs may not be increased. Thus, network slice admission control in an interworking scenario can be achieved.
Example 2
In example 2, the UE initiates release procedures of multiple PDN connections, and the multiple PDN connections are associated with the same network slice, and an NSACF responsible for quota management of the number of UEs in the network slice is the same NSACF as an NSACF responsible for quota management of the number of sessions in the network slice. Fig. 7 takes the UE establishing 2 PDN connections as an example. Assuming that according to example 1, the UE has established 2 PDN connections (PDN connection _1 and PDN connection _ 2) for the same network slice, at some point the UE initiates a PDN connection release procedure (PDN connection release) to the network.
Fig. 7 is another example of a network slice admission control method provided by the present application. The SMF + PGW-C _1 and SMF + PGW-C _2 in fig. 7 may correspond to the second network element in fig. 5 above, and the NSACF may correspond to the fourth network element in fig. 5 above.
In step 701, the ue initiates a release procedure of PDN connection _1.
In one possible implementation, the UE sends a PDN connection release message (PDN disconnection request) to the MME; after receiving the message, the MME determines that the UE is to release the PDN connection, the MME sends a delete session request message (delete session request) to the SGW serving the PDN connection, and the SGW sends the 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.
The fourth request message _3 may carry information related to the UE ID, the update flag _1, the S-NSSAI, the update flag _2, and the session _1. The UE ID may be determined by SMF + PGW-C _1 according to the delete session request message, and may be a permanent identity of the UE, such as IMSI. The update flag _1 is used to indicate that the number of UEs corresponding to the network slice identified by the S-NSSAI is reduced, e.g., 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, e.g., the number of sessions is reduced by 1. The information related to session _1 may include an identifier of SMF + PGW-C _1 and/or an identifier of session _1, where the identifier of SMF + PGW-C _1 may be an 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 one possible implementation, if the SMF + PGW-C _1 context holds information of an NSACF, the SMF + PGW-C _1 may determine the NSACF directly from the information of the NSACF.
As another implementation, if SMF + PGW-C _1 does not hold information for the NSACF in context, then SMF + PGW-C _1 may request the NRF to discover the NSACF. The method may refer to steps 604 and 605 described above.
A possible implementation manner is that SMF + PGW-C _1 sends an NSACF _ numberofpdusperserviceavailabilitycheckaddupdate request to the NSACF, or SMF + PGW-C _1 sends an NSACF _ numberofuespiesvicesavailackandupdate request to the NSACF, which is not limited in this application.
In step 703, the nsacf performs admission control on the network slice according to the fourth request message _3.
In one possible implementation manner, performing admission control on a network slice by using an NSACF includes performing admission control on the number of UEs on the network slice and performing admission control on the number of sessions on the network slice, which may also be referred to as performing counting of the number of UEs and counting of the number of sessions, and the present application does not limit the order in which the NSACF performs counting of the number of UEs and performs counting of the number of sessions.
In one possible implementation, the NSACF performs the counting of the number of sessions first, 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 reduces the number of sessions established in the network slice identified by the S-NSSAI by 1), and deletes the identifier of SMF + PGW-C ID _1 in the context information; since the NSACF _1 stores the information related to the session _1 and the information related to the 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 the session _1, the NSACF determines that other sessions exist in the UE, the NSACF deletes the information related to the session _1 and continuously stores the corresponding relationship between the UE ID, the information related to the session _2 and the S-nsai without reducing the number of UEs accessing the network slice identified by the S-nsai. I.e. the UE ID is kept in the UE identity list that the network slice identified by the S-NSSAI has access to.
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 results may include: the admission control performed on the network slice is successful or the admission control performed on the network slice is failed. If the admission control is successfully executed on the network slice, the counting of the number of the executed UE and the counting of the number of the executed sessions are both successful. If the admission control performed on the network slice fails, which indicates that the counting of the number of the UEs performed fails and/or the counting of the number of the sessions performed fails, the fourth response message _3 may further carry a failure cause value, which may indicate that the UE has other sessions on the network slice. In step 704, the fourth response message _3 may indicate that the admission control performed on the network slice fails, and the fourth response message _3 may also carry a failure cause value, for example, that the UE has other sessions on the network slice.
One possible implementation manner is that the NSACF sends NSACF _ numberofpdusperseliceavailabilitycheckaddupdate response to the SMF + PGW-C _1, or the NSACF sends NSACF _ numberofuesrislaceavailabilitycheckaddupdate response to the SMF + PGW-C _1, which is not limited in this application, and the NSACF carries a result of performing admission control on a network slice in a sent message.
Step 705, the remaining procedure of PDN connection release is performed.
At this point, the release of PDN connection _1 is complete.
In step 706, the ue initiates the release procedure of PDN connection _2.
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 is not described herein again.
Step 707, SMF + PGW-C _2 sends a fourth request message _4 to NSACF.
The fourth request message _4 may carry information related to the UE ID, the update flag _1, the S-NSSAI, the update flag _2, and the session _2. The UE ID may be determined by SMF + PGW-C _2 according to the delete session request message, and may be, for example, the IMSI of the UE. The update flag _1 is used to indicate that the number of UEs corresponding to the network slice identified by the S-NSSAI is reduced, e.g., 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, e.g., the number of sessions is reduced by 1. The information related to session _2 may include an identifier of SMF + PGW-C _2 and/or an identifier of session _2, where the identifier of SMF + PGW-C _2 may be an 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 one possible implementation, if the SMF + PGW-C _2 context holds information of an NSACF, the SMF + PGW-C _2 may determine the NSACF directly from the information of the NSACF.
As another implementation, if the SMF + PGW-C _2 does not hold information of the NSACF in context, the SMF + PGW-C _2 may request the NRF to discover the NSACF. The method may refer to steps 613 and 614 described above.
A possible implementation manner is that SMF + PGW-C _2 sends NSACF _ numberofpdusperspeviatilitycheckanddupdate request to NSACF, or SMF + PGW-C _2 sends NSACF _ numberofusesrilactitycheckanddupdate request to NSACF, which is not limited in this application.
In step 708, the nsacf performs admission control on the network slice according to the fourth request message _4.
In one possible implementation manner, performing admission control on a network slice by an NSACF includes performing admission control on the number of UEs on the network slice and performing admission control on the number of sessions on the network slice, which may also be referred to as performing counting of the number of UEs and counting of the number of sessions, and the present application does not limit the order in which the NSACF performs counting of the number of UEs and counting of the number of sessions.
In one possible implementation, the NSACF first performs counting of the number of sessions, and the NSACF decreases the number of sessions corresponding to the network slice identified by the S-nsai according to the update flag _2 (for example, the NSACF decreases the number of sessions established in the network slice identified by the S-nsai by 1), and deletes information related to session _2 in the context information; since only session _2 related information is stored for the UE ID in the context information, when the session _2 related information is deleted, there are no other sessions already established for the UE, so the NSACF can count the UE according to the update flag _1 (i.e., the NSACF reduces the number of UEs accessing the network slice identified by S-NSSAI), and delete the UE ID in the context information. That is, the NSACF deletes the UE ID from the UE identity list that the network slice identified by the S-NSSAI has access to.
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 results may include: the admission control performed on the network slice is successful or the admission control performed on the network slice is failed. If the admission control is successfully executed on the network slice, the counting of the number of the executed UE and the counting of the number of the executed sessions are both successful. If the admission control performed on the network slice fails, which indicates that the counting of the number of the UEs performed fails and/or the counting of the number of the sessions performed fails, the fourth response message _4 may also carry a failure cause value. In step 709, a fourth response message _4 may indicate that performing admission control on the network slice was successful.
One possible implementation manner is that the NSACF sends NSACF _ numberofpdusperseliceavailabilitycheckaddupdate response to the SMF + PGW-C _2, or the NSACF sends NSACF _ numberofuesrislaceavailabilitycheckaddupdate response to the SMF + PGW-C _1, which is not limited in this application, and the NSACF carries a result of performing admission control on a network slice in a sent message.
Step 710, execute the remaining procedure of PDN connection release.
At this point, the release of PDN connections _1 and _2 is completed.
As can be seen from the above, for the determination process of the number of UEs and the number of sessions triggered by the release of PDN connection, in example 2, the NSACF further determines whether the PDN connections of the UE should be released when determining the number of UEs and the number of sessions corresponding to the network slice, and when the UE has no established session, the NSACF reduces the number of UEs accessing the network slice identified by S-NSSAI, and deletes the UE ID in the context information. Thus, network slice admission control in an interworking scenario can be achieved.
Example 3
In example 3, the UE initiates an establishment procedure for establishing a plurality of PDN connections, and the PDN connections are associated with the same network slice, and an NSACF responsible for quota management of the number of UEs of the network slice is different from an NSACF responsible for quota management of the number of sessions of the network slice. Fig. 8 and 9 take the UE as an example to establish 2 PDN connections, where fig. 8 shows the establishment procedure of the 1 st PDN connection (hereinafter referred to as PDN connection _ 1) and fig. 9 shows the establishment procedure of the 2 nd PDN connection (hereinafter referred to as PDN connection _ 2).
Fig. 8 is another example of a network slice admission control method provided by the present application. SMF + PGW-C _1 in fig. 8 may correspond to the second network element in fig. 4 above, NSACF _1 may correspond to the first network element in fig. 4 above, and NSACF _2 may correspond to the third network element referred to in steps 402-403 above.
Step 801, UE initiates a PDN connection establishment flow.
Step 802, SMF + PGW-C _1 determines the network slice associated with the PDN connection.
At step 803, SMF + PGW-C _1 determines whether the network slice needs to execute NSAC process according to the configuration information.
The implementation manner of steps 801 to 803 is the same as that of steps 601 to 603, and reference may be made to the description of steps 601 to 603, which is not described herein again. For convenience of description, the selected SMF + PGW-C will be referred to hereinafter as SMF + PGW-C _1.
If the SMF + PGW-C _1 determines that the network slice needs to perform the NSAC procedure, steps 804-816 may be continued. If the SMF + PGW-C _1 determines that the network slice does not need to perform the NSAC procedure, steps 804-816 can be skipped and step 817 can be performed directly.
Step 804, SMF + PGW-C _1 sends a seventh request message _1 to NRF.
Wherein, the seventh request message _1 is used for requesting an NSACF which serves a network slice associated with the PDN connection _1 and supports performing control over the number of UEs accessing the network slice. As an example, the seventh request message _1 may carry S-nsasi and NSACF service capability indication information for identifying the network slice, where the NSACF service capability indication information is used to indicate that the NSACF requested by the SMF + PGW-C _1 supports performing control on the number of UEs accessing the network slice. For convenience of description, this NSACF will be referred to as NSACF _1 hereinafter.
In one possible implementation, the SMF + PGW-C _1 may call a servitization operation nrrf _ NFDiscovery request of the NRF.
In 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 the relevant information of the NSACF _1. The relevant information of NSACF _1 may include an address of NSACF _1. The NSACF _1 is an NSACF serving a network slice identified by the S-NSSAI carried in the seventh request message _1, and the NSACF _1 supports performing control of the number of UEs accessing the network slice identified by the S-NSSAI.
In one possible implementation, the NRF returns nrrf _ NFDiscovery response to the SMF + PGW-C _1, carrying information of the NSACF _1, such as address information of the NSACF _1.
Optionally, SMF + PGW-C _1 holds the information of NSACF _1 returned by the NRF in context.
Step 806, SMF + PGW-C _1 determines NSACF _1 from the seventh response message _1, and transmits an eighth request message _1 to NSACF _1.
The eighth request message _1 may carry the UE ID, the update flag _1, and the S-NSSAI. The UE ID may be determined by the SMF + PGW-C _1 according to the create session request message, for example, the create session request message carries the UE ID, which may be, for example, the IMSI of the UE. The update flag _1 is used to indicate that the number of UEs corresponding to the network slice identified by the S-NSSAI is increased, e.g., the number of UEs is increased by 1.
Optionally, the eighth request message _1 may also carry information related to the session _1. The information related to session _1 may include an identifier of SMF + PGW-C _1 and/or an identifier of session _1, where the identifier of SMF + PGW-C _1 may be an 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 one possible implementation, SMF + PGW-C _1 sends an nsecf _ numberofuserselslaviailabilitycheck addupdate request to NSACF _1.
In a possible implementation manner, optionally, when the SMF + PGW-C _1 determines that the PDN connection _1 is the first PDN connection associated with the S-NSSAI and served by the SMF + PGW-C _1 for the UE, the SMF + PGW-C _1 performs steps 806 to 808. Specifically, the SMF + PGW-C _1 may determine, according to the context information stored in the SMF + PGW-C _1, whether the PDN connection _1 is the first PDN connection established by the UE and associated with the network slice, for example, the SMF + PGW-C _1 stores the context information of all PDN connections currently established by the UE, and if there are other PDN connections in the context that are the same as the network slice associated with the PDN connection _1, it indicates that the PDN connection _1 is not the first PDN connection initiated by the UE and associated with the network slice. For example, the UE has currently established a PDN connection _1', which PDN connection _1' 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 PDN connection _1' may be different from the APN corresponding to PDN connection _1. If no other PDN connection exists in the context that is the same as the network slice associated with PDN connection _1, this indicates that PDN connection _1 is the first PDN connection associated with the network slice and served by SMF + PGW-C _1 that the UE initiates establishment.
If the SMF + PGW-C _1 determines, according to the above description, that the PDN connection _1 is not the first PDN connection associated with the S-NSSAI and served by the SMF + PGW-C _1 for the UE, for example, the UE currently establishes the PDN connection _1' on the SMF + PGW-C _1 and the PDN connection _1' is associated with the same S-NSSAI, the UE number execution control procedure corresponding to the network slice identified by the S-NSSAI is already executed in the establishment procedure of the PDN connection _1', and since the current PDN connection _1 is established by the same UE and is associated with the same network slice, the SMF + PGW-C _1 may not need to request the nsecf _1 to perform user number control on the network slice, that is, steps 806 to 808 may not be executed.
It should be noted that, in the process of establishing a PDN connection, the SMF + PGW-C _1 may store information of the PDN connection in a local context. In the process of releasing the PDN connection, the SMF + PGW-C _1 may delete the information of the PDN connection in the local context.
Step 807, nsacf _1performs admission control on the network slice according to the eighth request message _1.
In one possible implementation, performing admission control on a 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 counting the number of UEs performed, so as to ensure that the sum of the number of UEs currently accessing the network slice does not exceed the maximum number/number of terminal devices allowed to be accessed by the network slice. NSACF _1 may hold the number of UEs that have currently accessed a network slice, with the identities in the UE identity list used to identify the UEs that have currently accessed a network slice. NSACF _1 may also configure the maximum number of UEs that the network slice allows access to, i.e., NSACF _1 may configure the number of the maximum number of users that the network slice allows access to.
Specifically, if the current quota of the network slice identified by the S-NSSAI is still available (i.e., 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 UE identification list already accessed by the network slice identified by the S-NSSAI, the UE may access the network slice identified by the S-NSSAI, in which case, the NSACF _1 increases the number of UEs of the network slice (e.g., the number of UEs accessing the network slice identified by the S-NSSAI is added by 1), and adds the UE ID to the UE identification list already accessed by the network slice, 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 is already stored in the UE identity list to which the network slice identified by the S-NSSAI has access, it indicates that the UE has access to the network slice identified by the S-NSSAI, in this case, the number of UEs in the network slice is not changed by NSACF _1. If the current quota of the network slice identified by the S-NSSAI is not available (i.e., the number of UEs currently accessing the network slice identified by the S-NSSAI exceeds the maximum number), the UE may not access the network slice identified by the S-NSSAI, in which case, NSACF _1 also does not change the number of UEs of the network slice.
In the process shown in fig. 8, NSACF _1 increases the number of UEs in a network slice, and adds a UE ID to a UE identity list that the network slice has access to, thereby saving the corresponding relationship between the UE ID and the S-NSSAI.
Optionally, if the eighth request message _1 carries session _1 related information, the NSACF _1 may also store the session _1 related information. For example, the NSACF _1 stores configuration information or policy information thereon: the configuration information or policy information is used to indicate that NSACF _1 stores session _1 related information.
Step 808, NSACF _1sends an eighth response message _1 to SMF + PGW-C _1.
Wherein the eighth response message _1 is used to indicate a result of performing admission control on the network slice. The results may include: the admission control performed on the network slice is successful or the admission control performed on the network slice is failed. If the admission control performed on the network slice is successful, it indicates that the counting of the number of the UEs performed is successful, and if the admission control performed on the network slice is failed, it indicates that the counting of the number of the UEs performed is failed, then the eighth response message _1 may further carry a failure cause value, where the failure cause value is used to indicate that the number of the UEs that the network slice has accessed has reached the maximum value. In this example, the eighth response message _1 may indicate that performing admission control on the network slice is successful.
One possible implementation is that NSACF _1 sends NSACF _ numberofuesrisvicavailabilitycheckandopate response to SMF + PGW-C _1, and NSACF _1 carries the result of performing admission control on the network slice 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 for requesting an NSACF that serves the network slice associated with PDN connection _1 and supports performing control over 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 for identifying the network slice, the NSACF service capability indication information being used to indicate that the smaf + PGW-C _1 requested NSACF supports performing control on the number of sessions established on the network slice identified by the S-NSSAI. For convenience of description, this NSACF will be referred to as NSACF _2 hereinafter.
In one possible implementation, the SMF + PGW-C _1 may call a service operation NRF _ NFDiscovery request of the NRF.
And 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 the relevant information of the NSACF _2. The information related to NSACF _2 may include an address of NSACF _2. The NSACF _2 is an NSACF serving the network slice identified by the S-NSSAI carried in the fifth request message _1, and the NSACF _2 supports performing control over the number of sessions established on the network slice identified by the S-NSSAI.
In one possible implementation, the NRF returns nrrf _ NFDiscovery response to the SMF + PGW-C _1, which carries information of the NSACF _2, such as address information of the NSACF _2.
Optionally, SMF + PGW-C _1 holds the information of NSACF _2 returned by the NRF in context.
It should be noted that, the present application does not limit the sequence of the SMF + PGW-C _1 requesting to find NSACF _1 and NSACF _2 from the NRF. As shown in fig. 8, the SMF + PGW-C _1 may first request the NRF to find the NSACF _1 and then request the NRF to find the NSACF _2 after determining that the counting of the number of UEs is successful, that is, the SMF + PGW-C _1 sends two request messages to the NRF to obtain the information of the NSACF _1 and the information of the NSACF _2, respectively. In another possible implementation, the SMF + PGW-C _1 triggers the NRF to discover NSACF _1 and NSACF _2 through a request message, and the NRF returns the information of NSACF _1 and the information of NSACF _2 in a response message.
Step 811, SMF + PGW-C _1 determines NSACF _2 from the fifth response message _1, and transmits a sixth request message _1 to NSACF _2.
Wherein, the sixth request message _1 may carry the update flag _2, the S-NSSAI, and the session _1 related information. The update flag _2 is used to indicate that the number of sessions corresponding to the network slice identified by the S-NSSAI is increased, e.g., the number of sessions is increased by 1. The information related to session _1 may include an identifier of SMF + PGW-C _1 and/or an identifier of session _1, where the identifier of SMF + PGW-C _1 may be an 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 further carry a UE ID, where the UE ID may be determined by the SMF + PGW-C _1 according to the create session request message or the context.
One possible implementation is that SMF + PGW-C _1 sends a NSACF _ numberofpdusperslicieavailabilitycheck addupdate request to NSACF _2.
In step 812, nsacf _2performs admission control on the network slice according to the sixth request message _1.
In one possible implementation, performing admission control on a network slice by NSACF _2 includes performing admission control on the network slice for the number of sessions, which may also be referred to as counting the number of sessions, so as to ensure that the sum of the number of sessions that have currently been established on the network slice does not exceed the maximum number/number of sessions that the network slice is allowed to establish. NSACF _2 may hold the number of sessions that have currently been established on a network slice. NSACF _2 may also configure the maximum number of sessions that a network slice allows to establish, i.e., NSACF _2 may configure the number of maximum number of users that a network slice allows to access and the number of maximum number of sessions that a network slice allows to establish.
Specifically, if the current quota of the network slice identified by the S-NSSAI is still available (i.e., the number of sessions currently established by the network slice identified by the S-NSSAI does not exceed the maximum number), the UE may establish a new session within the network slice identified by the S-NSSAI, in which case NSACF _2 increases the number of sessions of the network slice (e.g., adds 1 to the number of sessions accessing the network slice identified by the S-NSSAI), and saves the correspondence between the information related to session _1 and the S-NSSAI. If the current quota of the network slice identified by the S-NSSAI is not available (i.e., the number of sessions currently established by the network slice identified by the S-NSSAI exceeds the maximum number), the UE may not establish a new session within the network slice identified by the S-NSSAI, in which case NSACF _2 does not change the number of sessions of the network slice for which the quota is available.
In the process shown in fig. 8, NSACF _2 increases the number of sessions of the network slice, and stores the corresponding relationship between the information related to session _1 and S-NSSAI. If the sixth request message _1 carries the UE ID, the NSACF _2 may store the corresponding relationship between the UE ID, the S-NSSAI, and the information related to the session _1
Step 813, nsacf _2sends a sixth response message _1 to SMF + PGW-C _1.
Wherein the sixth response message _1 is used for a result of performing admission control on the network slice. The results may include: the admission control performed on the network slice is successful or the admission control performed on the network slice is failed. If the admission control performed on the network slice is successful, which indicates that the counting of the number of sessions performed is successful, and if the admission control performed on the network slice is failed, which indicates that the counting of the number of sessions performed is failed, the sixth response message _1 may further carry a failure cause value, where the failure cause value is used to indicate that the number of sessions established on the network slice has reached the maximum value. In the flow shown in fig. 8, the sixth response message _1 may indicate that performing admission control on the network slice is successful.
One possible implementation manner is that NSACF _2 sends NSACF _ numberofpduspersliceavailabilitychecandaddupdate response to SMF + PGW _ C _1, and NSACF _2 carries the result of performing admission control on a network slice in the sent message.
Step 814, SMF + PGW-C _1 sends a ninth request message _1 to NSACF _1.
The reason why the SMF + PGW-C _1 performs step 814 may be any one of the following reasons:
1) The eighth request message _1 does not carry information related to the session _ 1;
2) The eighth request message _1 carries information related to the session _1, but the sixth response message _1 indicates that the counting of the number of sessions fails.
If the SMF + PGW-C _1 performs step 814 for the reason 1), the ninth request message _1 may have the following 2 cases:
a) If the sixth response message _1 indicates that the counting of the session number is successful, the ninth request message _1 may carry information related to the UE ID, the S-NSSAI, and the session _1. The UE ID may be determined according to the context. Optionally, the ninth request message _1 may further carry first indication information, which is used to indicate that the NSACF _1 stores the information related to the session _1, that is, the NSACF _1 stores the information related to the session _ 1; it is understood that if the result returned by NSACF-2 is a successful counting of the number of sessions, indicating that the current network resources allow the UE to establish a PDN connection on the network slice, then NSACF _1 needs to store information related to this session _1. The ninth request message _1 may then correspond to the second request message referred to in step 402 above.
b) If the sixth response message _1 indicates that the counting of the session number fails, the ninth request message _1 may carry the UE ID, the S-NSSAI, and the first indication information (e.g., the update flag _ 1). The UE ID may be determined according to the context. The first indication information indicates to reduce the number of UEs corresponding to the network slice identified by the S-NSSAI, such as the number of UEs minus 1.
If the SMF + PGW-C _1 performed step 814 is for the reason 2), the ninth request message _1 may carry the UE ID, the S-NSSAI, and the first indication information (e.g., the update flag _ 1). The UE ID may be determined according to the context. The first indication information indicates to reduce the number of UEs corresponding to the network slice identified by the S-NSSAI, such as the number of UEs minus 1. It is to be understood that if the NSACF-2 returns a failure of counting the number of sessions, indicating that the current network resources do not allow the UE to establish a PDN connection on the network slice, it is further understood that the session establishment fails and the UE no longer accesses the network slice. The ninth request message _1 at this time may correspond to the first request message in fig. 4 above.
One possible implementation is that SMF + PGW-C _1 sends an NSACF _ numberofuesrisliceavailabilitycheckandupdate request to NSACF _1.
In step 815, the nsacf _1determines whether to store the information related to the session _1 according to the ninth request message _1.
In one possible implementation manner, if the ninth request message _1 includes the information related to the session _1, the NSACF _1 may maintain the number of UEs corresponding to the network slice identified by the S-NSSAI, and store the information related to the session _1. If the first indication information in the ninth request message _1 indicates to reduce the number of UEs, the NSACF _1 determines whether there are other sessions for the current UE, and since the context stored in the NSACF _1 only includes information related to the session _1 (i.e., the NSACF _1 only stores information of the PDN connection _ 1), the NSACF _1 may reduce the number of UEs corresponding to the network slice identified by the S-NSSAI, and meanwhile, the NSACF _1 deletes the information related to the session _1.
Step 816, nsacf _1sends a ninth response message _1 to SMF + PGW-C _1.
If the ninth request message _1 contains the information related to the session _1, the ninth response message _1 is used to indicate that the session information is successfully stored; if the ninth request message _1 is used to request that admission control be performed on the number of UEs accessing the network slice (e.g., indicating that the number of UEs corresponding to the network slice identified by the S-NSSAI is decreased), the ninth response message _1 is used to indicate the result of performing admission control on the number of UEs accessing the network slice.
Note that, if the NSACF _1 stores the information about the session _1 in step 807, when the sixth response message _1 indicates that the counting of the number of sessions is successful, steps 814 to 816 may not be executed.
Step 817, the remaining procedures of PDN connection establishment are performed.
Since example 3 takes 2 PDN connections as an example, and at this time, the 1 st PDN connection is established, so NSACF _1 increases the number of UEs corresponding to the network slice, and stores the corresponding relationship between the UE ID, S-NSSAI, and information related to session _1, and NSACF _2 increases the number of sessions corresponding to the network slice, and stores the corresponding relationship between S-NSSAI and information related to session _1. If the sixth request message _1 carries the UE ID, the NSACF _2 may store the corresponding relationship between the UE ID, the S-NSSAI, and the information related to the session _1.
Thus, the establishment of PDN connection _1 is completed, and the NSACF _1 stores the correspondence between the UE ID, S-NSSAI, and information related to session _1.
Fig. 9 is another example of a network slice admission control method provided by the present application. SMF + PGW-C _1 in fig. 9 may correspond to the second network element above, NSACF _1 may correspond to the first network element in fig. 4 above, and NSACF _2 may correspond to the third network element referred to in steps 402-403 above.
According to the procedure shown in fig. 8, the UE has successfully established PDN connection _1, PDN connection _1 is served by SMF + PGW-C _1, and the UE may continue to initiate a PDN connection establishment procedure to the network, where, for convenience of description, SMF + PGW-C serving PDN connection _2 is hereinafter referred to as 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.
Step 903, SMF + PGW-C _2 determines whether the network slice needs to execute NSAC flow 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 is not described herein again.
If the SMF + PGW-C _2 determines that the network slice needs to perform the NSAC flow, then steps 904-916 may continue. If the SMF + PGW-C _2 determines that the network slice does not need to perform the NSAC procedure, steps 904-916 can be skipped and step 917 can be performed directly.
Step 904, SMF + PGW-C _2 sends a seventh request message _2 to NRF.
Wherein the seventh request message _2 is for requesting an NSACF that serves a network slice associated with the PDN connection _2 and supports performing control over the number of UEs accessing the network slice. As an example, the seventh request message _2 may carry S-nsasi and NSACF service capability indication information for identifying the network slice, where the NSACF service capability indication information is used to indicate that the NSACF requested by the SMF + PGW-C _2 supports performing control on the number of UEs accessing the network slice. For convenience of description, this NSACF will be referred to as NSACF _1 hereinafter.
In one possible implementation, the SMF + PGW-C _2 may call a servitization operation nrrf _ NFDiscovery request of the NRF.
And 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 the relevant information of the NSACF _1. The NSACF _1 is an NSACF serving the network slice identified by the S-NSSAI carried in the seventh request message _2, and the NSACF _1 supports performing 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 holds the information of NSACF _1 returned by the NRF in context.
Step 906, smf + pgw-C _2 determines NSACF _1 according to the seventh response message _2 and transmits an eighth request message _2 to the NSACF _1.
The eighth request message _2 may carry the UE ID, the update flag _1, and the S-NSSAI. The UE ID may be determined by the SMF + PGW-C _2 according to the create session request message, for example, the create session request message carries the UE ID, which may be, for example, the IMSI of the UE. The update flag _1 is used to indicate that the number of UEs corresponding to the network slice identified by the S-NSSAI is increased, e.g., the number of UEs is increased by 1.
Optionally, the eighth request message _2 may also carry information related to the session _2. The information related to session _2 may include an identifier of SMF + PGW-C _2 and/or an identifier of session _2, where the identifier of SMF + PGW-C _2 may be an 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 one possible implementation, SMF + PGW-C _2 sends an nsecf _ numberofuserselslaviailabilitycheck addupdate request to NSACF _1.
In a possible implementation manner, optionally, when the SMF + PGW-C _2 determines that the PDN connection _2 is the first PDN connection associated with the S-NSSAI and served by the SMF + PGW-C _2 for the UE, the SMF + PGW-C _2 performs steps 906 to 908. Specifically, the SMF + PGW-C _2 may determine, according to the context information stored in the SMF + PGW-C _2, whether the PDN connection _2 is the first PDN connection established by the UE and associated with the network slice, for example, the SMF + PGW-C _2 stores context information of all PDN connections currently established by the UE, and if there is another PDN connection in the context that is the same as the network slice associated with the PDN connection _2, it indicates that the PDN connection _2 is not the first PDN connection initiated by the UE and associated with the network slice. For example, the UE has currently established a PDN connection _2', which PDN connection _2' 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 PDN connection _2' may be different from the APN corresponding to PDN connection _2. If no other PDN connection exists 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 PDN connection _2 is the first PDN connection that the UE initiates establishment and is associated with the network slice and served by SMF + PGW-C _2.
If the SMF + PGW-C _2 determines that the PDN connection _2 is not the first PDN connection associated with the S-NSSAI, which is served by the SMF + PGW-C _2 for the UE, according to the above description, for example, the UE has currently established the PDN connection _2' and the PDN connection _2' is associated with the same S-NSSAI, then the UE number execution control procedure corresponding to the network slice identified by the S-NSSAI is already executed in the establishment procedure of the PDN connection _2', and since the current PDN connection _2 is established by the same UE and is associated with the same network slice, the SMF + PGW-C _2 may not need to request the NSACF _1 to control the number of users of the network slice, that is, steps 906 to 908 may not be executed.
It should be noted that, in the process of establishing a PDN connection, the SMF + PGW-C _2 may store information of the PDN connection in a local context. In the process of releasing the PDN connection, the SMF + PGW-C _2 may delete the information of the PDN connection in the local context.
In step 907, the nsacf _1performs admission control on the network slice according to the eighth request message _2.
In one possible implementation, performing admission control on a 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 of the number of UEs, so as to ensure that the sum of the number of UEs currently accessing the network slice does not exceed the maximum number/number of terminal devices allowed to be accessed by the network slice. NSACF _1 may maintain the number of UEs that have currently accessed a network slice, and the identities in the UE identity list are used to identify the UEs that have currently accessed a network slice. NSACF _1 may also configure the maximum number of UEs that the network slice allows access to, i.e., NSACF _1 may configure the number of maximum number of users that the network slice allows access to.
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 UE identification list to which the network slice identified by the S-NSSAI has been accessed, the UE may access the network slice identified by the S-NSSAI, in which case, the NSACF _1 increases the number of UEs of the network slice (for example, the number of UEs accessing the network slice identified by the S-NSSAI is added by 1), and adds the UE ID to the UE identification list to which the network slice has been accessed, thereby saving 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 meanwhile, the UE ID is already stored in the UE identity list to which the network slice identified by the S-NSSAI has access, it indicates that the UE has access to the network slice identified by the S-NSSAI, in this case, nsecf _1 does not change the number of UEs in the network slice. If the current quota of the network slice identified by the S-NSSAI is not available (i.e., the number of UEs currently accessing the network slice identified by the S-NSSAI exceeds the maximum number), the UE may not access the network slice identified by the S-NSSAI, in which case, NSACF _1 also does not change the number of UEs of the network slice.
In the process shown in fig. 9, NSACF _1 determines that the UE has accessed the network slice identified by S-NSSAI according to the correspondence between the UE ID and S-NSSAI stored in the context information, in this case, NSACF _1 does not need to count the number of UEs corresponding to the network slice, that is, the number of UEs in the network slice remains unchanged.
Optionally, if the eighth request message _2 carries the information related to the session _2, the NSACF _1 may also store the information related to the session _2. For example, the NSACF _1 stores thereon configuration information or policy information: the configuration information or policy information is used to indicate that NSACF _1 stores session _2 related information.
Step 908, nsacf _1sends an eighth response message _2 to SMF + PGW-C _2.
Wherein the eighth response message _2 is used to indicate a result of performing admission control on the network slice. The results may include: the admission control performed on the network slice is successful or the admission control performed on the network slice is failed. If the admission control performed on the network slice is successful, it indicates that the counting of the number of the executed UEs is successful, and if the admission control performed on the network slice is failed, it indicates that the counting of the number of the executed UEs is failed, then the eighth response message _2 may further carry a failure cause value, where the failure cause value is used to indicate that the number of the UEs that the network slice has accessed has reached the maximum value. In this example, the eighth response message _2 may indicate that performing admission control on the network slice was successful.
One possible implementation is that NSACF _1 sends NSACF _ numberofuesrisvicavailabilitycheckandopate response to SMF + PGW-C _2, and NSACF _1 carries the result of performing admission control on the network slice in the sent message.
In step 909, if the eighth response message _2 indicates that the counting of the UE count is successful, the SMF + PGW-C _2 sends a fifth request message _2 to the NRF.
Wherein the fifth request message _2 is for requesting an NSACF that serves a network slice associated with the PDN connection _2 and supports performing control over 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 for identifying the network slice, the NSACF service capability indication information being used to indicate that the smaf + PGW-C _2 requested NSACF supports performing control over the number of sessions established on the network slice identified by the S-NSSAI. For convenience of description, the NSACF will be hereinafter referred to as NSACF _2.
In one possible implementation, the SMF + PGW-C _1 may call a servitization operation nrrf _ NFDiscovery request of the NRF.
In 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 the relevant information of the NSACF _2. The information related to NSACF _2 may include an address of NSACF _2. The NSACF _2 is an NSACF serving the network slice identified by the S-NSSAI carried in the fifth request message _2, and the NSACF _2 supports performing control over 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 one possible implementation, the NRF returns nrrf _ NFDiscovery response to the SMF + PGW-C _2, carrying information of the NSACF _2, such as address information of the NSACF _2.
Optionally, the SMF + PGW-C _2 context holds the NSACF _2 information returned by the NRF.
It should be noted that, the present application does not limit the sequence of the SMF + PGW-C _2 requesting the NRF to find NSACF _1 and NSACF _2. As shown in fig. 9, the SMF + PGW-C _2 may first request the NRF to find the NSACF _1 and then request the NRF to find the NSACF _2 after determining that the counting of the number of UEs is successful, that is, the SMF + PGW-C _2 sends two request messages to the NRF to obtain the information of the NSACF _1 and the information of the NSACF _2, respectively. In another possible implementation, the SMF + PGW-C _2 triggers the NRF to discover NSACF _1 and NSACF _2 through a request message, and the NRF returns the information of NSACF _1 and the information of NSACF _2 in a response message.
Step 911, smf + pgw-C _2 determines NSACF _2 from the fifth response message _2 and transmits a sixth request message _2 to the NSACF _2.
Wherein, the sixth request message _2 may carry the update flag _2, the S-NSSAI, and the session _2 related information. The update flag _2 is used to indicate that the session number corresponding to the network slice identified by the S-NSSAI is increased, e.g., the session number is increased by 1. The information related to session _2 may include an identifier of SMF + PGW-C _2 and/or an identifier of session _2, where the identifier of SMF + PGW-C _2 may be an 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 further carry a UE ID, where the UE ID may be determined by the SMF + PGW-C _2 according to the create session request message or the context.
One possible implementation is that SMF + PGW-C _2 sends NSACF _ numberofpdusperslicieavailabilitycheck addupdate request to NSACF _2.
In step 912, nsacf _2performs admission control on the network slice according to the sixth request message _2.
In one possible implementation, performing admission control on a network slice by NSACF _2 includes performing admission control on the network slice for the number of sessions, which may also be referred to as counting the number of sessions, so as to ensure that the sum of the number of sessions that have currently been established on the network slice does not exceed the maximum number/number of sessions that the network slice is allowed to establish. NSACF _2 may hold the number of sessions that have currently been established on a network slice. NSACF _2 may also configure the maximum number of sessions that a network slice allows to establish, i.e., NSACF _2 may configure the number of maximum number of users a network slice allows to access and the number of maximum number of sessions a network slice allows to establish.
Specifically, if the current quota of the network slice identified by the S-NSSAI is still available (i.e., the number of sessions currently established by the network slice identified by the S-NSSAI does not exceed the maximum number), the UE may establish a new session within the network slice identified by the S-NSSAI, in which case NSACF _2 increases the number of sessions of the network slice (e.g., adds 1 to the number of sessions accessing the network slice identified by the S-NSSAI), and stores the corresponding relationship between the information related to session _1 and the S-NSSAI. If the current quota of the network slice identified by the S-NSSAI is not available (i.e., the number of sessions currently established by the network slice identified by the S-NSSAI exceeds the maximum number), the UE may not establish a new session within the network slice identified by the S-NSSAI, in which case NSACF _2 does not change the number of sessions of the network slice for which the quota is available.
In the process shown in fig. 9, NSACF _2 increases the number of sessions of a network slice, and stores the corresponding relationship between information related to session _2 and S-NSSAI. If the sixth request message _2 carries the UE ID, the NSACF _2 may store the corresponding relationship between the UE ID, the S-NSSAI, and the session _2 related information.
Step 913, NSACF _2sends 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 results may include: the admission control performed on the network slice is successful or the admission control performed on the network slice is failed. If the admission control performed on the network slice is successful, it indicates that the counting of the number of sessions performed is successful, and if the admission control performed on the network slice is failed, it indicates that the counting of the number of sessions performed is failed, then the sixth response message _2 may further carry a failure cause value, where the failure cause value is used to indicate that the number of sessions established on the network slice has reached the maximum value. In the flow shown in fig. 9, the sixth response message _2 may indicate that performing admission control on the network slice is successful.
One possible implementation manner is that NSACF _2 sends NSACF _ numberofpduspersliceavailabilitychecandaddupdate response to SMF + PGW-C _2, and NSACF _2 carries the result of performing admission control on a network slice in the sent message.
Step 914, SMF + PGW-C _2 sends a ninth request message _2 to NSACF _1.
Also, the reason why the SMF + PGW-C _2 performs step 914 may be any of the following:
1) The eighth request message _2 does not carry information related to the session _ 2;
2) The eighth request message _2 carries information related to the session _2, but the sixth response message _2 indicates that the counting of the number of sessions fails.
If the reason for performing step 914 by the SMF + PGW-C _2 is the above reason 1), the ninth request message _2 may have the following 2 cases:
a) If the sixth response message _2 indicates that the counting of the session number is successful, the ninth request message _2 may carry information related to the UE ID, the S-NSSAI, and the session _2. The UE ID may be determined according to context. Optionally, the ninth request message _2 may further carry first indication information, which is used to indicate that the NSACF _1 stores the information related to the session _2, that is, the NSACF _1 stores the information related to the session _ 2; it can be understood that if the result returned by nsecf-2 is that the counting of the number of sessions is successful, which indicates that the current network resources allow the UE to establish PDN connection on the network slice, then the information related to the session _2 needs to be stored by nsecf _1. The ninth request message _2 may then correspond to the second request message referred to above in step 402.
b) If the sixth response message _2 indicates that the counting of the session number fails, the ninth request message _2 may carry the UE ID, the S-NSSAI, and the first indication information (e.g., the update flag _ 1). The UE ID may be determined according to the context. The first indication information indicates to reduce the number of UEs corresponding to the network slice identified by the S-NSSAI, such as the number of UEs minus 1.
If the reason for the SMF + PGW-C _2 performing step 914 is the reason 2), the ninth request message _2 may carry the UE ID, the S-NSSAI, and the first indication information (e.g., update flag _ 1). The UE ID may be determined according to the context. The first indication information indicates to reduce the number of UEs corresponding to the network slice identified by the S-NSSAI, such as the number of UEs minus 1. It is to be understood that if the NSACF-2 returns that the counting of the number of sessions fails, which means that the current network resources do not allow the UE to establish the PDN connection on the network slice, it is further understood that the session establishment fails and the UE no longer accesses the network slice. The ninth request message _2 at this time may correspond to the first request message in fig. 4 above.
In one possible implementation, SMF + PGW-C _2 sends an nsecf _ numberofuserselslaviailabilitycheck addupdate request to NSACF _1.
In step 915, the nsacf _1determines whether to store the information related to the session _2 according to the ninth request message _2.
In one possible implementation, if the ninth request message _2 includes information related to session _2, the NSACF _1 may maintain the number of UEs corresponding to the network slice identified by the S-NSSAI, and store the information related to session _2. If the first indication information in the ninth request message _2 indicates to reduce the number of UEs, the NSACF _1 determines whether there are other sessions for the current UE, and since the context stored in the NSACF _1 includes the session _1 related information and the session _2 related information, the NSACF _1 cannot reduce the number of UEs corresponding to the network slice identified by the S-NSSAI. Meanwhile, the NSACF _1 deletes the session _ 2-related information, i.e., deletes the session _ 2-related information, and retains the session _ 1-related information.
In the process shown in fig. 9, NSACF _1 maintains the number of UEs corresponding to the network slice identified by S-NSSAI, and determines whether to store the session _2 related information according to the parameters carried in the ninth request message _2.
In step 916, NSACF _1sends a ninth response message _2 to SMF + PGW-C _2.
If the ninth request message _2 includes information related to UE sessions, the ninth response message _2 is used to indicate that the session information is successfully stored, and if the ninth request message _2 is used to perform admission control on the number of UEs in the network slice, the ninth response message _2 is used to indicate a result of performing admission control on the number of UEs in the network slice.
It should be noted that, if the NSACF _1 stores the information related to the session _2 in step 907, when the sixth response message _2 indicates that the counting of the number of sessions is successful, steps 914 to 916 may not be executed.
Step 917, perform the remaining procedure of PDN connection establishment.
The establishment of PDN connection _2 is completed so far, and NSACF _1 stores the correspondence between the UE ID, S-NSSAI, information related to session _1, and information related to session _2.
As can be seen from the above, for the determination process of the number of UEs and the number of sessions triggered by establishing the PDN connection, in example 3, the SMF + PGW-C interacts with the NSACF _1 (NSACF responsible for controlling the number of UEs) first to trigger updating the number of UEs, if the number of UEs is not excessive, the SMF + PGW-C interacts with the NSACF _2 (NSACF responsible for controlling the number of sessions) again to trigger updating the number of sessions, and when the number of sessions is updated successfully, the SMF + PGW-C needs to interact with the NSACF _1 again to trigger the NSACF _1 to maintain the state of the number of sessions, so that the NSACF _1 subsequently determines whether to reduce the number of UEs. Thus, network slice admission control in an interworking scenario can be achieved.
It should be noted that, fig. 8 and 9 both illustrate the case where the SMF + PGW-C interacts with the NSACF responsible for UE count control first, then interacts with the NSACF responsible for session count control, and finally interacts with the NSACF responsible for UE count control, but the embodiment of the present application is not limited to this, for example, the SMF + PGW-C may also interact with the NSACF responsible for session count control first, then interacts with the NSACF responsible for UE count control, and finally interacts with the NSACF responsible for session count control.
Example 4
In example 4, the UE initiates release procedures of multiple PDN connections, and the multiple PDN connections are associated with the same network slice, and an NSACF responsible for quota management of the number of UEs of the network slice is different from an NSACF responsible for quota management of the number of sessions of the network slice. Fig. 10 takes the example where the UE has established 2 PDN connections. Assuming that according to example 3, the UE has established 2 PDN connections (PDN connection _1 and PDN connection _ 2) for the same network slice, at some point the UE initiates a PDN connection release procedure to the network.
Fig. 10 is another example of a network slice admission control method provided by the present application. SMF + PGW-C _1 and SMF + PGW-C _2 in fig. 10 may correspond to the second network element in fig. 4 above, NSACF _1 may correspond to the first network element in fig. 4 above, and NSACF _2 may correspond to the third network element involved in steps 402-403 above.
Step 1001, the ue initiates a release procedure of PDN connection _1.
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 is not described herein again.
Step 1002, SMF + PGW-C _1 sends a sixth request message _3 to NSACF _2.
The sixth request message _3 may carry S-NSSAI, update flag _2, and session _1 related information. 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, e.g., the number of sessions is reduced by 1. The information related to session _1 may include an identifier of SMF + PGW-C _1 and/or an identifier of session _1, where the identifier of SMF + PGW-C _1 may be an 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 further carry a UE ID, where the UE ID may be determined by the SMF + PGW-C _1 according to the delete session request message, and for example, the UE ID may be an IMSI of the UE.
In one possible implementation, if the SMF + PGW-C _1 holds the information of NSACF _2 in the context, the SMF + PGW-C _1 may determine NSACF _2 directly from the information of NSACF _2.
As another implementation, if the SMF + PGW-C _1 does not hold information of the NSACF _2 in the context, the SMF + PGW-C _1 may request discovery of the NSACF _2 from the NRF. The method can refer to steps 809 and 810 described above.
One possible implementation is that SMF + PGW-C _1 sends an NSACF _ numberofpduspersliceavailabilitycheckandopate request to NSACF _2.
In step 1003, nsacf _2performs admission control on the network slice according to the sixth request message _3.
In one possible implementation, performing admission control on a network slice by NSACF _2 includes performing admission control of the number of sessions, which may also be referred to as performing counting of the number of sessions, on the network slice. Specifically, NSACF _2 reduces the number of sessions corresponding to the network slice identified by the S-NSSAI (e.g., NSACF _2 reduces the number of sessions established within the network slice identified by the S-NSSAI by 1), and deletes the identification of SMF + PGW-C ID _1 in the context information.
Step 1004, NSACF _2sends 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 results may include: the admission control performed on the network slice is successful or the admission control performed on the network slice is failed. If the admission control is successfully executed on the network slice, the counting of the number of the executed sessions is successful, and if the admission control is failed, the counting of the number of the executed sessions is failed. In step 1004, a sixth response message _3 may indicate that performing admission control on the network slice was successful.
One possible implementation manner is that NSACF _2 sends NSACF _ numberofpduspersliceavailabilitychecandaddupdate response to SMF + PGW _ C _1, and NSACF _2 carries the result of performing admission control on a network slice in the sent message.
Step 1005, SMF + PGW-C _1 sends a first request message _1 to NSACF _1.
The first request message _1 may carry UE ID, S-NSSAI, update flag _1, and session _1 related information. The UE ID may be determined by SMF + PGW-C _1 from the delete session request message or context. The update flag _1 is used to indicate that the number of UEs corresponding to the network slice identified by the S-NSSAI is reduced, e.g., the number of UEs is reduced by 1. The information related to session _1 may include an identifier of SMF + PGW-C _1 and/or an identifier of session _1, where the identifier of SMF + PGW-C _1 may be an 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 one possible implementation, if the SMF + PGW-C _1 context holds information of NSACF _1, then SMF + PGW-C _1 may determine NSACF _1 directly from the information of NSACF _1.
As another implementation, if the SMF + PGW-C _1 does not hold information for NSACF _1 in the context, then the SMF + PGW-C _1 may request the NRF to discover NSACF _1. The method may refer to steps 804 and 805 described above.
One possible implementation is that SMF + PGW-C _1 sends an NSACF _ numberofpduspersliceavailabilitycheckandopate request to NSACF _1.
In a possible implementation manner, optionally, when the SMF + PGW-C _1 determines that the PDN connection _1 is the only PDN connection associated with the S-NSSAI and served by the SMF + PGW-C _1 for the UE, the SMF + PGW-C _1 performs steps 1005 to 1007. Specifically, the SMF + PGW-C _1 may determine, according to the context information, whether the PDN connection _1 is only one PDN connection associated with the S-NSSAI, for example, the SMF + PGW-C _1 stores context information of all PDN connections currently established by the UE, and if there is another PDN connection in the context that is the same as a network slice associated with the PDN connection _1, it indicates that another PDN connection exists after the PDN connection _1 is released. For example, the UE currently has a PDN connection _1', which PDN connection _1' 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 PDN connection _1' may be different from the APN corresponding to PDN connection _1. If no other PDN connection exists in the context that is the same as the network slice associated with PDN connection _1, then PDN connection _1 is the only one PDN connection associated with the network slice and served by SMF + PGW-C _1 that the UE initiates the release.
If the SMF + PGW-C _1 determines that the PDN connection _1 is not the only PDN connection associated with the S-NSSAI released by the UE according to the above description, for example, the UE has currently established the PDN connection _1 'and the PDN connection _1' is associated with the same S-NSSAI, then the UE number execution control flow corresponding to the network slice identified by the S-NSSAI does not need to be executed, because there are other PDN connections associated with the same network slice in the current UE, the SMF + PGW-C _1 does not need to request the NSACF _1 to perform user number control on the network slice, that is, steps 1005-1007 may not be executed.
In step 1006, nsacf _1performs admission control on the network slice according to the first request message _1.
In one possible implementation, performing admission control on a 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 of the number of UEs. Specifically, NSACF _1 determines whether a session other than session _1 exists in the current UE, and if only session information related to session _1 is included in the session information related to the UE in the context stored in NSACF _1 (i.e., only information of PDN connection _1 is stored in NSACF _ 1), NSACF _1 may reduce the number of UEs corresponding to the network slice identified by S-NSSAI, and at the same time, NSACF _1 deletes the session _1 related information. If the session information related to the UE in the context stored by NSACF _1 includes session related information (e.g., session _2 related information) other than the session _1 related information, the NSACF _1 deletes the session _1 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, the NSACF _1 deletes the information related to the session _1 from the stored context, and then the NSACF _1 determines whether there is information of another session in the current UE. If the current UE does not have information about other sessions, i.e., after the information about session _1 is deleted from the session information about the UE, the session information about the UE is empty, then NSACF _1 may reduce the number of UEs corresponding to the network slice identified by S-NSSAI. If the current UE has information of other sessions, 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 not null, then NSACF _1 does not need to reduce the number of UEs corresponding to the network slice identified by S-NSSAI.
In this example, since the NSACF _1 stores the information related to the session _1 and the information related to the session _2 for the UE ID at the same time, and the UE currently releases only the PDN connection _1 corresponding to the information related to the session _1, and the NSACF_1 determines that other sessions exist in the UE, the NSACF _1 deletes the information related to the UE session 1 and continues to store the corresponding relationship between the UE ID and the S-nsai and the information related to the UE session 2 without reducing the number of UEs accessing the network slice identified by the S-nsai. Namely, the UE ID is continuously stored in the UE identity list to which the network slice identified by the S-NSSAI has access.
Step 1007, NSACF _1sends a first response message _1 to SMF + PGW-C _1.
Wherein the first response message _1 is used to indicate a result of performing admission control on the network slice. The results may include: the admission control performed on the network slice is successful or the admission control performed on the network slice is failed. If the admission control performed on the network slice is successful, it indicates that the counting of the number of the executed UEs is successful, and if the admission control performed on the network slice is failed, it indicates that the counting of the number of the executed UEs is failed, then the first response message _1 may also carry a failure cause value, where the failure cause value is used to indicate that other sessions also exist in the UE. In step 1007, the first response message _1 may indicate that admission control on the network slice failed because there are other sessions for the UE.
One possible implementation manner is that NSACF _1 sends NSACF _ numberofpduspersliceavailabilitychecandaddupdate response to SMF + PGW _ C _1, and NSACF _1 carries the result of performing admission control on a network slice in the sent message.
Step 1008, perform the remaining procedures of PDN connection release.
At this point, the release of PDN connection _1 is complete.
In step 1009, the ue initiates the release procedure of 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 is not described herein again.
Step 1010, SMF + PGW-C _2 sends a sixth request message _4 to NSACF _2.
The sixth request message _4 may carry information related to S-NSSAI, the update flag _2, and the 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, e.g., the number of sessions is reduced by 1. The information related to session _2 may include an identifier of SMF + PGW-C _2 and/or an identifier of session _2, where the identifier of SMF + PGW-C _2 may be an 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 further carry a UE ID, where the UE ID may be determined by the SMF + PGW-C _1 according to the delete session request message, and for example, the UE ID may be an IMSI of the UE.
In one possible implementation, if the SMF + PGW-C _2 context holds the information of NSACF _2, then the SMF + PGW-C _2 may determine NSACF _2 directly from the information of NSACF _2.
As another implementation, if the SMF + PGW-C _2 does not hold information for NSACF _2 in the context, then the SMF + PGW-C _2 may request the NRF to discover NSACF _2. The method can refer to steps 809 and 810 described above.
One possible implementation is that SMF + PGW-C _2 sends NSACF _ numberofpdusperslicieavailabilitycheck addupdate request to NSACF _2.
Step 1011, nsacf _2performs admission control on the network slice according to the sixth request message _4.
In one possible implementation, performing admission control on a network slice by NSACF _2 includes performing admission control of the number of sessions on the network slice, which may also be referred to as performing counting of the number of sessions. Specifically, NSACF _2 reduces the number of sessions corresponding to the network slice identified by the S-NSSAI (e.g., NSACF _2 reduces the number of sessions established within the network slice identified by the S-NSSAI by 1), and deletes the identification of SMF + PGW-C ID _2 in the context information.
Step 1012, NSACF _2sends 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 results may include: the admission control performed on the network slice is successful or the admission control performed on the network slice is failed. If the admission control is successfully executed on the network slice, the counting of the number of the executed sessions is successful, and if the admission control is failed, the counting of the number of the executed sessions is failed. In step 1012, the sixth response message _4 may indicate that performing admission control on the network slice was successful.
One possible implementation manner is that NSACF _2 sends NSACF _ numberofpduspersliceavailabilitychecandaddupdate response to SMF + PGW-C _2, and NSACF _2 carries the result of performing admission control on a network slice in the sent message.
Step 1013, SMF + PGW-C _2 sends a first request message _2 to NSACF _1.
The first request message _2 may carry UE ID, S-NSSAI, update flag _1, and session _2 related information. The UE ID may be determined by SMF + PGW-C2 from the delete session request message or context. The update flag _1 is used to indicate that the number of UEs corresponding to the network slice identified by the S-NSSAI is reduced, e.g., the number of UEs is reduced by 1. The information related to session _2 may include an identifier of SMF + PGW-C _2 and/or an identifier of session _2, where the identifier of SMF + PGW-C _2 may be an 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 one possible implementation, if the SMF + PGW-C _2 context holds the information of NSACF _1, then the SMF + PGW-C _2 may determine NSACF _1 directly from the information of NSACF _1.
As another implementation, if the SMF + PGW-C _2 does not hold information of the NSACF _1 in the context, the SMF + PGW-C _2 may request discovery of the NSACF _1 from the NRF. The method may refer to steps 804 and 805 described above.
One possible implementation is that SMF + PGW-C _2 sends an NSACF _ NumberOfPDUsPerSliceAvailabilityCheckAndUpdate request to NSACF _1.
In a possible implementation manner, optionally, when the SMF + PGW-C _2 determines that the PDN connection _2 is the only PDN connection associated with the S-NSSAI and served by the SMF + PGW-C _2 for the UE, the SMF + PGW-C _2 performs steps 1013-1015. Specifically, the SMF + PGW-C _2 may determine, according to the context information, whether the PDN connection _2 is only one PDN connection associated with the S-NSSAI, for example, the SMF + PGW-C _2 stores context information of all PDN connections currently established by the UE, and if there is another PDN connection in the context that is the same as a network slice associated with the PDN connection _2, it indicates that another PDN connection exists after the PDN connection _2 is released. For example, the UE currently has a PDN connection _2', which PDN connection _2' 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 PDN connection _2' may be different from the APN corresponding to PDN connection _2. If no other PDN connection exists in the context that is the same as the network slice associated with PDN connection _2, then PDN connection _2 is the only one PDN connection associated with the network slice and served by SMF + PGW-C _2 that the UE initiates the release.
If the SMF + PGW-C _2 determines that the PDN connection _2 is not the only PDN connection associated with the S-NSSAI released by the UE according to the above description, for example, the UE has currently established the PDN connection _2 'and the PDN connection _2' is associated with the same S-NSSAI, then the UE number execution control flow corresponding to the network slice identified by the S-NSSAI does not need to be executed, and since there are other PDN connections associated with the same network slice in the current UE, the SMF + PGW-C _2 does not need to request the NSACF _1 to perform user number control on the network slice, that is, steps 1013-1015 may not be executed.
Step 1014, nsacf _1performs admission control on the network slice according to the first request message _2.
In one possible implementation, performing admission control on a 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 of the number of UEs. Specifically, NSACF _1 determines whether a session other than session _2 exists in the current UE, and if the context stored in NSACF _1 only includes information related to session _2 (i.e., NSACF _1 only stores information of PDN connection _ 2), NSACF _1 may reduce the number of UEs corresponding to the network slice identified by 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 S-NSSAI.
In another possible implementation manner, the NSACF _1 deletes the information related to the session _2 from the stored context, and then the NSACF _1 determines whether there is information of another session in the current UE. NSACF _1 may reduce the number of UEs corresponding to the network slice identified by the S-NSSAI if the current UE does not have information of other sessions, i.e., the session information related to the UE is empty after the information related to session _2 is deleted from the session information related to the UE. If the current UE has information of other sessions, i.e. 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 not null, then NSACF _1 does not need to reduce the number of UEs corresponding to the network slice identified by S-NSSAI.
In this example, since the current NSACF _1 stores only session _2 related information for this UE ID, when session _2 related information is deleted, there are no other already established sessions for this UE, so NSACF _1 may count the UE (i.e., NSACF _1 reduces the number of UEs accessing the network slice identified by S-NSSAI), and delete the UE ID from the list of UE identities that the network slice has accessed in context information.
Step 1015, nsacf _1sends a first response message _2 to SMF + PGW-C _2.
Wherein the first response message _2 is used to indicate a result of performing admission control on the network slice. The results may include: the admission control performed on the network slice is successful or the admission control performed on the network slice is failed. If the admission control performed on the network slice is successful, it indicates that the counting of the number of the executed UEs is successful, and if the admission control performed on the network slice is failed, it indicates that the counting of the number of the executed UEs is failed, then the first response message _2 may further carry a failure cause value, where the failure cause value is used to indicate that other sessions also exist in the UE. In step 1015, the first response message _2 may indicate that performing admission control on the network slice was successful.
One possible implementation manner is that NSACF _1 sends NSACF _ numberofpduspersliceavailabilitychecandaddupdate response to SMF + PGW-C _2, and NSACF _1 carries the result of performing admission control on a network slice in the sent message.
In step 1016, the remaining procedures of PDN connection release are performed.
So far, the release of PDN connections _1 and _2 is completed.
As can be seen from the above, for the process of determining the number of UEs and the number of sessions triggered by releasing PDN connection, in example 4, the NSACF responsible for controlling the number of UEs also determines whether all PDN connections of the UE should be released when determining the number of UEs corresponding to a network slice, and when the UE has no established session, the NSACF reduces the number of UEs accessing the network slice identified by S-nsai, and deletes the UE ID in the context information. Thus, network slice admission control in an interworking scenario can be achieved.
It should be noted that, in fig. 10, the SMF + PGW-C interacts with the NSACF responsible for UE count control first and then interacts with the NSACF responsible for session count control, but the embodiment of the present application is not limited thereto, for example, the SMF + PGW-C may also interact with the NSACF responsible for session count control first and then interacts with the NSACF responsible for UE count control.
The method embodiment provided by the present application is described in detail above with reference to fig. 4 to 10, and the apparatus embodiment of the present application is described in detail below with reference to fig. 11 and 12. It is to be understood that, in order to implement the functions of the above-described embodiments, the apparatus in fig. 11 or fig. 12 includes a corresponding hardware structure and/or software module for performing each function. Those of skill in the art will readily appreciate that the various illustrative elements and method steps described in connection with the embodiments disclosed herein may be implemented as hardware or combinations of hardware and computer software. Whether a function is performed as hardware or computer software driven hardware depends on the particular application scenario and design constraints imposed on the solution.
Fig. 11 and 12 are schematic structural diagrams of possible devices provided by embodiments of the present application. The apparatuses may be configured to implement the functions of the first network element, the second network element, the fourth network element, and the NRF in the foregoing method embodiment, so that the advantageous effects of the foregoing method embodiment can also be achieved.
As shown in fig. 11, the apparatus 1100 includes a transceiving unit 1110 and a processing unit 1120.
When the apparatus 1100 is used to implement the functionality of the first network element in the method embodiment:
a transceiver 1120, configured to obtain first information from a second network element, where the first information is used to associate a first session of a user equipment, the first network element supports performing control on a 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; and receiving a first request message from the second network element, wherein the first request message is used for indicating that the number of users accessing the network slice is reduced. A processing unit 1110, configured to determine whether to reduce the number of users having access to the network slice according to the first information.
Optionally, after acquiring the first information, the processing unit 1110 may further store the first information, the network slice, and the corresponding relationship of the user equipment.
Optionally, the transceiver unit is specifically configured to: and acquiring the first information in the process that the second network element requests to increase the number of users accessed to the network slice.
Optionally, the transceiver unit is specifically configured to: receiving a second request message from the second network element in a case that the number of established sessions on the network slice does not exceed a maximum value of the number of sessions allowed to be established by the network slice, the second request message including the first information.
Optionally, the processing unit is specifically configured to: determining to maintain a number of users that have accessed the network slice if the user equipment establishes a session on the network slice other than the first session; and if the user equipment only establishes the first session on the network slice, determining to reduce the number of users having access to the network slice.
Optionally, the processing unit is further configured to: deleting the first information after determining whether to reduce the number of users having access to the network slice.
Optionally, the first session is a packet data network PDN connection established by the ue in an evolved packet core EPC network.
When the apparatus 1100 is used to implement the functionality of the second network element in the method embodiment:
in some implementations, a processing unit 1110 to determine a network slice associated with a first session of a user device; a transceiver 1120, configured to send first information to a first network element, where the first information is used to associate with the first session, 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; sending a first request message to the first network element, wherein the first request message is used for indicating to reduce the number of users accessing the network slice; wherein the first information is used to determine whether to reduce a number of users that have access to the network slice.
Optionally, the transceiver 1120 is specifically configured to: and in the process of requesting to increase the number of users accessing the network slice, sending the first information to the first network element.
Optionally, the transceiver 1120 is specifically configured to: and when the number of established sessions on the network slice does not exceed the maximum number of sessions allowed to be established by the network slice, sending a second request message to the first network element, wherein the second request message comprises the first information.
Optionally, the transceiver 1120 is specifically configured to: acquiring, from a third network element, that the number of sessions established on the network slice reaches a maximum value of the number of sessions allowed to be established by the network slice, the third network element supporting control over the number of sessions established on the network slice; and after the second network element learns that the number of the established sessions on the network slice reaches the maximum value of the number of the sessions allowed to be established by the network slice, the first request message is sent to the first network element.
Optionally, the transceiver 1120 is specifically configured to: and when the first session is released, the second network element sends the first request message to the first network element.
Optionally, the first session is a packet data network PDN connection established by the user equipment in an evolved packet core, EPC, network.
In other implementations, the processing unit 1110 is configured to determine a network slice associated with a first session of a user equipment; a transceiver 1120, 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, the third request message includes an identifier of the network slice and second information, and the second information is used to indicate that the fourth network element supports controlling a number of users accessing the network slice and controlling a number of sessions established on the network slice; receiving a third response message of the network storage function network element, wherein the third response message comprises information of 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 control on the number of sessions established by the network slice.
Optionally, the fourth request message includes an identifier of a user equipment, first information, third information, fourth information, and an identifier of the network slice, where the first information is used to associate with the first session, where: when the user equipment requests to establish the first session, the third information is used for indicating the number of users who have access to the network slice to be increased, and the fourth information is used for indicating the number of sessions established in the network slice to be increased; when the user equipment requests to release the first session, the third information is used for indicating to reduce the number of users having access to the network slice, and the fourth information is used for indicating to reduce the number of sessions established in the network slice.
Optionally, the first information includes at least one of an identification of the second network element or an identification of the first session.
Optionally, the first session is a packet data network PDN connection established by the ue in an evolved packet core EPC network.
When the apparatus 1100 is used to implement the functionality of the NRF in method embodiments:
a transceiver 1120, 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, the third request message includes an identifier of the network slice and second information, and the second information is used to indicate that the fourth network element supports performing control on the number of users accessing the network slice and supporting performing control on the number of sessions established on the network slice; and sending a third response message to the second network element, where the third response message includes information of the fourth network element.
When the apparatus 1100 is used to implement the functionality of the fourth network element in the method embodiment:
a transceiver 1120, configured to receive a fourth request message from a second network element, the fourth network element supporting control over a number of users accessing a network slice and control over a number of sessions established on the network slice, the second network element serving a first session of a user equipment, the first session being associated with the network slice; a processing unit 1110, configured to 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 transceiving unit 1120 is further configured to send a fourth response message to the second network element, where the fourth response message is used to indicate a result of performing control on the number of users who have accessed the network slice and a result of performing control on the number of sessions that have been established in the network slice.
Optionally, the fourth request message includes an identifier of a user equipment, first information, third information, fourth information, and an identifier of the network slice, the first information is used for associating the first session, where: when the user equipment requests to establish the first session, the third information is used for indicating the number of users who have access to the network slice to be increased, and the fourth information is used for indicating the number of sessions established in the network slice to be increased; when the user equipment requests to release the first session, the third information is used for indicating to reduce the number of users having access to the network slice, and the fourth information is used for indicating to reduce the number of sessions established in the network slice.
The more detailed description about the processing unit 1110 and the transceiver 1120 can be directly obtained by referring to the related description in the above method embodiments, and will not be repeated herein.
As shown in fig. 12, the apparatus 1200 includes a processor 1210 and an interface circuit 1220. The processor 1210 and the interface circuit 1220 are coupled to each other. It is understood that the interface circuit 1220 may be a transceiver or an input-output interface. In one implementation, the apparatus 1200 may further include a memory 1230 for storing instructions to be 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 configured to implement the functions of the processing unit 1120, and the interface circuit 1220 is configured to implement the functions of the transceiving unit 1110.
When the communication device is a chip applied to the first network element, the chip implements the function of the first network element in the embodiment of the method. The chip receives information from other modules (such as a radio frequency module or an antenna) in the first network element, wherein the information is sent to the first network element by other equipment; or, the chip sends information to other modules (such as a radio frequency module or an antenna) in the first network element, where the information is sent by the first network element to other devices.
When the communication device is a chip applied to a second network element, the chip implements the function of the second network element in the above method embodiment. The chip receives information from other modules (such as a radio frequency module or an antenna) in the second network element, and the information is sent to the second network element by other equipment; or, the chip sends information to other modules (such as a radio frequency module or an antenna) in the second network element, where the information is sent by the second network element to other devices.
When the communication device is a chip using a 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 a radio frequency module or an antenna) in the fourth network element, and the information is sent to the fourth network element by other equipment; or, the chip sends information to other modules (such as a radio frequency module or an antenna) in the fourth network element, where the information is sent by the fourth network element to other devices.
When the communication device is a chip to which NRF is applied, the chip realizes the function of NRF in the above method embodiment. The chip receives information from other modules in the NRF (e.g., radio frequency modules or antennas) that other devices send to the NRF; alternatively, the chip sends information to other modules in the NRF (such as a radio frequency module or an antenna), which the NRF sends to other devices.
The embodiment of the application also provides a chip, and the chip acquires the instruction and executes the instruction to realize the method.
Optionally, as an implementation manner, the chip includes a processor and a data interface, and the processor reads instructions stored on the memory through the data interface to execute the method.
Optionally, as an implementation manner, the chip may further include a memory, where the memory stores instructions, and the processor is configured to execute the instructions stored on the memory, and when the instructions are executed, the processor is configured to execute the method.
The embodiment of the present application further provides a communication system, which includes any one of the above communication devices, or includes any one of the above chips.
Embodiments of the present application further provide a computer-readable storage medium, where the computer-readable storage medium stores instructions for the method in the foregoing method embodiments.
The embodiment of the present application further provides a computer program product containing instructions for implementing the method in the above method embodiment.
It is understood that the processor in the embodiments of the present application may be a Central Processing Unit (CPU), other general purpose processor, a Digital Signal Processor (DSP), an Application Specific Integrated Circuit (ASIC), a Field Programmable Gate Array (FPGA) or other programmable logic device, a transistor logic device, a hardware component, or any combination thereof. The general purpose processor may be a microprocessor, but may be any conventional processor.
The memory in embodiments of the present application may be either volatile memory or nonvolatile memory, or may include both volatile and nonvolatile memory. The non-volatile memory may be a read-only memory (ROM), a Programmable ROM (PROM), an Erasable PROM (EPROM), an electrically Erasable EPROM (EEPROM), or a flash memory. Volatile memory can be Random Access Memory (RAM), which acts as external cache memory. By way of example, but not limitation, many forms of Random Access Memory (RAM) are available, such as Static RAM (SRAM), dynamic RAM (DRAM), synchronous DRAM (SDRAM), double data rate SDRAM (DDR SDRAM), enhanced SDRAM (ESDRAM), synchlink DRAM (SLDRAM), and direct bus RAM (DR RAM).
It is clear to those skilled in the art that, for convenience and brevity of description, the specific working processes of the above-described systems, apparatuses and units may refer to the corresponding processes in the foregoing method embodiments, and are not described herein again.
In various embodiments of the present application, unless otherwise specified or conflicting, terms and/or descriptions between different embodiments have consistency and may be mutually referenced, and technical features in different embodiments may be combined to form a new embodiment according to their inherent logical relationships.
In the present application, "at least one" means one or more, "a plurality" means two or more. "and/or" describes the association relationship of the associated objects, meaning that there may be three relationships, e.g., a and/or B, which may mean: a alone, A and B together, and B alone, wherein A and B may be singular or plural. In the description of the text of the present application, the character "/" generally indicates that the former and latter associated objects are in an "or" relationship; in the formula of the present application, the character "/" indicates that the preceding and following associated objects are in a "division" relationship.
It is to be understood that the various numerical references referred to in the embodiments of the present application are merely for descriptive convenience and are not intended to limit the scope of the embodiments of the present application. The sequence numbers of the above-mentioned processes do not mean the execution sequence, and the execution sequence of the processes should be determined by their functions and inherent logic.
Unless otherwise defined, all technical and scientific terms used in the examples of this application have the same meaning as commonly understood by one of ordinary skill in the art to which this application belongs. The terminology used in the present application is for the purpose of describing particular embodiments only and is not intended to limit the scope of the present application. It should be understood that the above examples are for illustrative purposes only and are not intended to limit the claimed embodiments to the particular values or particular scenarios illustrated to assist those skilled in the art in understanding the claimed embodiments. It will be apparent to those skilled in the art from the examples given above that various equivalent modifications or variations can be made, and such modifications and variations also fall within the scope of the embodiments of the present application.
In the several embodiments provided in the present application, it should be understood that the disclosed system, apparatus and method may be implemented in other ways. For example, the above-described apparatus embodiments are merely illustrative, and for example, the division of the units is only one type of logical functional division, and other divisions may be realized in practice, for example, multiple units or components may be combined or integrated into another system, or some features may be omitted, or not executed. In addition, the shown or discussed mutual coupling or direct coupling or communication connection may be an indirect coupling or communication connection through some interfaces, devices or units, and may be in an electrical, mechanical or other form.
The units described as separate parts may or may not be physically separate, and parts displayed as units may or may not be physical units, may be located in one position, or may be distributed on multiple network units. Some or all of the units can be selected according to actual needs to achieve the purpose of the solution of the embodiment.
In addition, functional units in the embodiments of the present application may be integrated into one processing unit, or each unit may exist alone physically, or two or more units are integrated into one unit.
The functions, if implemented in the form of software functional units and sold or used as a stand-alone product, may be stored in a computer readable storage medium. Based on such understanding, the technical solution of the present application or portions thereof that substantially contribute to the prior art may be embodied in the form of a software product stored in a storage medium and including instructions for causing a computer device (which may be a personal computer, a server, or a network device) to execute all or part of the steps of the method according to the embodiments of the present application. And the aforementioned storage medium includes: a U-disk, a removable hard disk, a Read-Only Memory (ROM), a Random Access Memory (RAM), a magnetic disk, an optical disk, or other various media capable of storing program codes.
The above description is only for the specific embodiments of the present application, but the scope of the present application is not limited thereto, and any person skilled in the art can easily conceive of the changes or substitutions within the technical scope of the present application, and shall be covered by the scope of the present application. Therefore, the protection scope of the present application shall be subject to the protection scope of the claims.

Claims (23)

1. A method for controlling admission to a network slice, 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 user equipment, the first network element supports the execution control of 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, wherein the first request message is used for indicating that the number of users accessing the network slice is reduced;
and the first network element determines whether to reduce the number of users accessed to the network slice or not according to the first information.
2. The method of claim 1, wherein the first network element obtaining the first information from the second network element comprises:
and the first network element acquires the first information in the process that the second network element requests to increase the number of users accessed to the network slice.
3. The method of claim 1, wherein the first network element obtains the first information from the second network element, and wherein the obtaining the first information comprises:
the first network element receives a second request 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 to be established by the network slice, wherein the second request message comprises the first information.
4. The method according to any one of claims 1 to 3, further comprising:
the first network element stores the first information.
5. The method of any of claims 1 to 4, wherein the determining, by the first network element, whether to reduce the number of users having access to the network slice according to the first information comprises:
if the user equipment establishes a session on the network slice except the first session, the first network element determines to maintain the number of users accessing the network slice;
if the user equipment only establishes the first session on the network slice, the first network element determines to reduce the number of users having access to the network slice.
6. The method of claim 5, further comprising:
and after the first network element determines whether the number of users accessing the network slice is reduced or not, deleting the first information by the first network element.
7. The method of any of claims 1 to 6, wherein the first information comprises at least one of an identification of the second network element or an identification of the first session.
8. The method according to any one of claims 1 to 7,
the first session is a Packet Data Network (PDN) connection established by the user equipment in an Evolved Packet Core (EPC) network.
9. A method for controlling admission to a network slice, the method comprising:
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 a first network element, the first information is used for associating the first session, the first network element supports to control 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, wherein the first request message is used for indicating that the number of users accessing the network slice is reduced;
wherein the first information is used to determine whether to reduce a number of users that have access to the network slice.
10. The method of claim 9, wherein the second network element sends the first information to the first network element, and wherein the sending the first information comprises:
and in the process of requesting to increase the number of users accessing the network slice, the second network element sends the first information to the first network element.
11. The method of claim 9, wherein the second network element sends the first information to the first network element, and wherein the sending the first information comprises:
and when the number of established sessions on the network slice does not exceed the maximum number of sessions allowed to be established by the network slice, the second network element sends a second request message to the first network element, wherein the second request message comprises the first information.
12. The method of claim 10,
the method further comprises the following steps:
the second network element learns from a third network element that the number of sessions established on the network slice reaches the maximum value of the number of sessions allowed to be established by the network slice, and the third network element supports control over the number of sessions established on the network slice;
the second network element sending a first request message to the first network element, including:
and after the second network element learns that the number of the established sessions on the network slice reaches the maximum value of the number of the sessions allowed to be established by the network slice, the second network element sends the first request message to the first network element.
13. The method according to any of claims 9 to 11, wherein the second network element sending a first request message to the first network element comprises:
and when the first session is released, the second network element sends the first request message to the first network element.
14. The method according to any of claims 9 to 13, wherein the first information comprises at least one of an identification of the second network element or an identification with the first session.
15. The method according to any one of claims 9 to 14,
the first session is a Packet Data Network (PDN) connection established by the user equipment in an Evolved Packet Core (EPC) network.
16. A method for network slice admission control, the method comprising:
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 a network storage function network element, the third request message is used for requesting information of a fourth network element, the third request message includes an identifier of the network slice and second information, and the second information is used for indicating that the fourth network element supports control over the number of users accessing the network slice and control over the number of sessions established on the network slice;
the second network element receives a third response message of the network storage function network element, where the third response message includes information of the fourth network element;
and 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 control the number of users accessing the network slice and control the number of sessions established by the network slice.
17. The method of claim 16,
the first session is a Packet Data Network (PDN) connection established by the user equipment in an Evolved Packet Core (EPC) network.
18. A method for controlling admission to a network slice, the method comprising:
a network storage function network element receives a third request message from a second network element, where the third request message is used to request information of a fourth network element, the third request message includes an identifier of the network slice and second information, and the second information is used to indicate that the fourth network element supports controlling the number of users accessing the network slice and controlling the number of sessions established on the network slice;
and the network storage function network element sends a third response message to the second network element, where the third response message includes information of the fourth network element.
19. A communications apparatus, comprising:
a processor for executing computer instructions stored in a memory to cause the apparatus to perform the method of any of claims 1 to 8, or to perform the method of any of claims 9 to 17, or to perform the method of claim 18.
20. The apparatus of claim 19, further comprising the memory to store the computer instructions.
21. A computer-readable storage medium, in which a computer program is stored, which, when executed by one or more processors, causes an apparatus comprising the processors to perform performing the method of any of claims 1-8, or performing the method of any of claims 9-17, or performing the method of claim 18.
22. A computer program product, characterized in that it comprises computer program code for implementing the method according to any one of claims 1 to 8, or for implementing the method according to any one of claims 9 to 17, or for implementing the method according to claim 18, when said computer program code is run on a computer.
23. A communication system comprising a communication device according to claim 19 or 20.
CN202110908693.4A 2021-08-09 2021-08-09 Network slice admission control method and device Pending CN115707062A (en)

Priority Applications (2)

Application Number Priority Date Filing Date Title
CN202110908693.4A CN115707062A (en) 2021-08-09 2021-08-09 Network slice admission control method and device
PCT/CN2022/090973 WO2023015973A1 (en) 2021-08-09 2022-05-05 Network slice admission control method and apparatus

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
CN202110908693.4A CN115707062A (en) 2021-08-09 2021-08-09 Network slice admission control method and device

Publications (1)

Publication Number Publication Date
CN115707062A true CN115707062A (en) 2023-02-17

Family

ID=85179254

Family Applications (1)

Application Number Title Priority Date Filing Date
CN202110908693.4A Pending CN115707062A (en) 2021-08-09 2021-08-09 Network slice admission control method and device

Country Status (2)

Country Link
CN (1) CN115707062A (en)
WO (1) WO2023015973A1 (en)

Family Cites Families (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20220377655A1 (en) * 2019-10-08 2022-11-24 Telefonaktiebolaget Lm Ericsson (Publ) Network Slicing Scalability Attributes
WO2021119627A1 (en) * 2019-12-13 2021-06-17 Ofinno, Llc Control of network slice
US11510138B2 (en) * 2020-01-03 2022-11-22 Apple Inc. Network slice quota management

Also Published As

Publication number Publication date
WO2023015973A1 (en) 2023-02-16

Similar Documents

Publication Publication Date Title
US11606734B2 (en) Handover method in wireless communication system and apparatus therefor
CN110999431B (en) Method for registering terminal in wireless communication system and apparatus therefor
KR102436804B1 (en) Session management methods, devices and systems
US11246172B2 (en) Method for selecting session and service continuity mode in wireless communication system and device therefor
US10609608B2 (en) Method for changing connection mode in base station, and base station therefor, and method for changing connection mode in user equipment, and user equipment thereof
US20200413241A1 (en) Method for terminal setting update in wireless communication system and apparatus therefor
WO2020164763A1 (en) Methods and apparatuses for alternative data over non-access stratum, donas, data delivery in a roaming scenario
CN113630749B (en) Method and device for acquiring edge service
CN114143871B (en) Network connection method, network disconnection method and communication device
US20230029714A1 (en) Authorization method, policy control function device, and access and mobility management function device
CN113785552B (en) Session management function selection
US20230132454A1 (en) Method and apparatus for supporting edge computing service for roaming ue in wireless communication system
CN113891427B (en) Communication method and device
WO2019196680A1 (en) Communication method and communication apparatus
CN113795019B (en) Communication control method and communication equipment
WO2022170798A1 (en) Strategy determining method and communication apparatus
US20240224147A1 (en) Apparatus and method for inter-plmn handover of home routed session in wireless communication system
WO2022219478A1 (en) Handling of heterogeneous support for user equipment slice maximum bit rate (s-mbr)
US20240155418A1 (en) Method and apparatus for connecting qos flow based terminal in wireless communication system
KR20200116852A (en) Apparatus and method for handling service policy in wireless communication system
WO2023015973A1 (en) Network slice admission control method and apparatus
WO2024114288A1 (en) Network access method and communication apparatus
US20240244477A1 (en) Apparatus and method for routing dns traffic of home routed session breakout session in wireless communication system
WO2023087988A1 (en) Communication method and apparatus, and device
US20240196222A1 (en) Terminal operation method and device in wireless communication system

Legal Events

Date Code Title Description
PB01 Publication
PB01 Publication
SE01 Entry into force of request for substantive examination
SE01 Entry into force of request for substantive examination