CN113596886B

CN113596886B - Method, apparatus and readable storage medium for controlling slice flow

Info

Publication number: CN113596886B
Application number: CN202010361410.4A
Authority: CN
Inventors: 侯云静
Original assignee: Datang Mobile Communications Equipment Co Ltd
Current assignee: Datang Mobile Communications Equipment Co Ltd
Priority date: 2020-04-30
Filing date: 2020-04-30
Publication date: 2024-01-26
Anticipated expiration: 2040-04-30
Also published as: CN113596886A

Abstract

The embodiment of the application provides a method, equipment and readable storage medium for controlling slice flow, which relate to the technical field of communication and comprise the following steps: the AMF receives a first message sent by the RAN, wherein the first message comprises first indication information and a slice identifier, and the first indication information is used for indicating that the slice rate of the UE is lower than, reaches or exceeds the maximum value; the AMF sends a second message to one of the UE, SMF, PCF or NWDAF, the second message including the first indication information and the slice identifier. And the UE receives the PDU session command sent by the SMF and dredges the slice traffic to the non-3 GPP access. In the embodiment of the application, when the slicing rate of the UE reaches/exceeds the maximum value, the slicing flow is moved to the non-3 GPP access to reduce the slicing rate of the UE and avoid the packet loss of the RAN.

Description

Method, apparatus and readable storage medium for controlling slice flow

Technical Field

The embodiment of the application relates to the technical field of communication, in particular to a method and equipment for controlling slice flow and a readable storage medium.

Background

The 5G network proposes the concept of network slicing, i.e. a logical network supporting a certain service, four types of slices, such as eMBB (Enhanced Mobile Broadband ), URLLC (Ultra-Reliable and Low Latency Communications, ultra-reliable and low-latency communication), mIoT (Massive IoT), and V2X (Vihicle to everything, vehicle-to-outside information exchange), are currently defined. The identification of the network slice is S-nsai (Single Network Slice Selection Assistance Information ).

The UE's slice rate is the maximum uplink and downlink bit rates of the UE within the slice, which only limits the traffic of the UE's slice for third generation partnership project (3rd Generation Partnership Project,3GPP) access transmissions, and not the traffic of the UE's slice for non-3 GPP access transmissions. When the slicing rate of the UE reaches a maximum value or when the slicing rate of the UE cannot be guaranteed due to limited Radio Access Network (RAN) resources, the RAN will discard the data packet.

Disclosure of Invention

The embodiment of the invention provides a method, equipment and readable storage medium for controlling slicing flow, which can solve the problem that RAN discards data packets when the slicing rate of UE cannot be ensured due to limited RAN resources in the prior art.

In a first aspect, an embodiment of the present application provides a method for controlling slice traffic, applied to an access and mobility management function AMF, the method including:

receiving a first message sent by a Radio Access Network (RAN), wherein the first message comprises first indication information and a slice identifier, and the first indication information is used for indicating that the slice rate of a terminal UE is lower than, reaches or exceeds a maximum value;

and sending a second message to any one of the UE, a session management function SMF, a policy control function PCF or a network data analysis function NWDAF, wherein the second message comprises the first indication information and the slice identifier.

Further, the first indication information is used for indicating that the slicing rate of the UE reaches the maximum value;

before sending the second message to the UE, the method further comprises:

determining an allowed slice identity of a non-3 GPP access of the UE includes the slice identity.

In a second aspect, an embodiment of the present application provides a method for controlling slice traffic, applied to a UE, where the method includes:

receiving a second message sent by the AMF, wherein the second message comprises first indication information and a slice identifier, and the first indication information is used for indicating that the slice rate of the UE reaches or exceeds a maximum value;

when the UE supports a multi-access MA PDU session and the MA PDU session is established, a third message is sent to a user plane function UPF, the UPF sends a fourth message to an SMF, the third message and the fourth message comprise second indication information, and the second indication information is used for indicating that the 3GPP access rate reaches the maximum value;

receiving an access traffic grooming, switching and separating ATSSS rule sent by the SMF;

and according to the ATSSS rule, the slice traffic is led to the non-3 GPP access.

Further, after receiving the second message sent by the AMF, the method further includes:

When the UE supports MA PDU session and does not establish MA PDU, sending PDU session establishment request to the SMF, wherein the PDU session establishment request comprises the second indication information;

receiving an ATSSS rule sent by the SMF;

and when the UE does not support MA PDU session and new traffic needs to be sent to the slice, the slice traffic is led to the non-3 GPP access.

In a third aspect, an embodiment of the present application provides a method for controlling slice flow, applied to SMF, the method including:

receiving a third message sent by UPF, wherein the third message comprises second indication information which is used for indicating that the 3GPP access rate reaches the maximum value;

and sending the second indication information to the PCF.

Further, the method further comprises:

receiving an updated MA PDU session policy sent by the PCF;

an ats rule is sent to the UE and an N4 rule is sent to the UPF.

In a fourth aspect, an embodiment of the present application provides a method for controlling slice flow, applied to a PCF, where the method includes:

Receiving second indication information sent by SMF, wherein the second indication information is used for indicating that the 3GPP access rate reaches the maximum value;

updating MA PDU session strategy;

and sending the updated MA PDU session policy to the SMF.

Further, the updating MA PDU session policy includes:

setting a grooming mode to be based on priority-based, and setting the priority of non-3 GPP access to be highest;

alternatively, the grooming mode is set to active-standby and the active access is set to non-3 GPP access.

In a fifth aspect, an embodiment of the present application provides a method for controlling slice flow, applied to SMF, the method including:

receiving a second message sent by the AMF, wherein the second message comprises first indication information and a slice identifier, and the first indication information is used for indicating that the slice rate of the UE reaches the maximum value;

and sending the first indication information and the slice identifier to the PCF.

Further, the method further comprises:

receiving an updated PDU session policy sent by the PCF;

and initiating a PDU session modification process according to the updated PDU session strategy.

In a sixth aspect, an embodiment of the present application provides a method for controlling slice flow, applied to a PCF, where the method includes:

Receiving first indication information and a slice identifier sent by SMF, wherein the first indication information is used for indicating that the slice rate of UE reaches the maximum value;

updating PDU session policy;

the updated PDU session policy is sent to the SMF.

Further, the updating the PDU session policy includes:

updating MA PDU session policy associated with the slice identifier;

and/or adjusting a guaranteed bit rate GFBR of the guaranteed bit rate quality flow GBR QoS flow;

and/or releasing QoS flow;

and/or modifying the QoS of the PDU session.

Further, the sending the updated PDU session policy to the SMF includes:

transmitting the updated PDU session policy to a target SMF of the plurality of SMFs;

the UE establishes a plurality of PDU sessions related to the slice identifier, and a plurality of SMFs associated with the plurality of PDU sessions are different, wherein the target SMF is any one SMF in the plurality of SMFs, or the target SMF is one SMF with the largest associated PDU session, or the target SMF is one SMF with the largest GBR QoS flow.

In a seventh aspect, an embodiment of the present application provides a method for controlling a slice flow, applied to a PCF, where the PCF includes a PCF-AM and a PCF-SM, the method includes:

The PCF-AM receives first indication information and a slice identifier sent by an AMF, wherein the first indication information is used for indicating that the slice rate of the UE is lower than, reaches or exceeds a maximum value;

the PCF-AM sends the first indication information and the slice identifier to the PCF-SM;

the PCF-SM sends PDU session policy to SMF.

Further, the PCF-AM sends a fifth message to the AMF, where the fifth message includes a UE policy, where the UE policy is used to groom traffic related to the slice identifier to a non-3 GPP access.

In an eighth aspect, an embodiment of the present application provides an AMF entity, including:

a first receiving module, configured to receive a first message sent by a RAN, where the first message includes first indication information and a slice identifier, where the first indication information is used to indicate that a slice rate of a UE is lower than, reaches or exceeds a maximum value;

and the first sending module is used for sending a second message to any one of UE, SMF, PCF or NWDAF, wherein the second message comprises the first indication information and the slice identifier.

In a ninth aspect, embodiments of the present application provide a UE, including:

the second receiving module is used for receiving a second message sent by the AMF, wherein the second message comprises first indication information and a slice identifier, and the first indication information is used for indicating that the slice rate of the UE reaches or exceeds a maximum value;

A second sending module, configured to send a third message to a user plane function UPF when the UE supports a multi-access MA PDU session and a MA PDU is established, where the UPF sends a fourth message to the SMF, and the third message and the fourth message include second indication information, where the second indication information is used to indicate that a 3GPP access rate reaches a maximum value;

a third receiving module, configured to receive an ats ss rule sent by the SMF;

and the first control module is used for leading the slice traffic to the non-3 GPP access according to the ATSSS rule.

In a tenth aspect, embodiments of the present application provide an SMF entity, including:

a fourth receiving module, configured to receive a third message sent by the UPF, where the third message includes second indication information, where the second indication information is used to indicate that a 3GPP access rate reaches a maximum value;

and the third sending module is used for sending the second indication information to the PCF.

In an eleventh aspect, an embodiment of the present application provides a PCF entity, including:

a fifth receiving module, configured to receive second indication information sent by the SMF, where the second indication information is used to indicate that a 3GPP access rate reaches a maximum value;

a first updating module, configured to update MA PDU session policy;

And a fourth sending module, configured to send an updated MA PDU session policy to the SMF.

In a twelfth aspect, embodiments of the present application provide an SMF entity, including:

a sixth receiving module, configured to receive a second message sent by the AMF, where the second message includes first indication information and a slice identifier, and the first indication information is used to indicate that a slice rate of the UE reaches a maximum value;

and a fifth sending module, configured to send the first indication information and the slice identifier to the PCF.

In a thirteenth aspect, embodiments of the present application provide a PCF entity, including:

a seventh receiving module, configured to receive first indication information and a slice identifier sent by an SMF, where the first indication information is used to indicate that a slice rate of the UE reaches a maximum value;

a second updating module, configured to update a PDU session policy;

and a sixth sending module, configured to send the updated PDU session policy to the SMF.

In a fourteenth aspect, an embodiment of the present application provides a PCF entity, where the PCF entity includes a PCF-AM and a PCF-SM, and the PCF entity further includes:

a seventh sending module, configured to receive, by using the PCF-AM, first indication information and a slice identifier sent by the AMF, where the first indication information is used to indicate that a slice rate of the UE is lower than, reaches or exceeds a maximum value;

An eighth sending module, configured to send, by the PCF-AM, the first indication information and the slice identifier to the PCF-SM;

and a ninth sending module, configured to send a PDU session policy to the SMF by using the PCF-SM.

In a fifteenth aspect, an embodiment of the present application provides an AMF entity, including a processor, a memory, and a program stored on the memory and executable on the processor, the program when executed by the processor implementing the steps of the method for controlling slice flow according to the first aspect.

In a sixteenth aspect, an embodiment of the present application provides a UE, including a processor, a memory, and a program stored on the memory and executable on the processor, the program implementing the steps of the method for controlling slice flow according to the second aspect when executed by the processor.

In a seventeenth aspect, an embodiment of the present application provides an SMF entity, including a processor, a memory, and a program stored on the memory and executable on the processor, where the program when executed by the processor implements the steps of the method for controlling slice traffic according to the third aspect, or the steps of the method for controlling slice traffic according to the fifth aspect.

In an eighteenth aspect, an embodiment of the present application provides a PCF entity, including a processor, a memory, and a program stored on the memory and executable on the processor, where the program is executed by the processor to implement the steps of the method for controlling slice traffic as described in the fourth aspect, or the steps of the method for controlling slice traffic as described in the sixth aspect, or the steps of the method for controlling slice traffic as described in the seventh aspect.

In a nineteenth aspect, an embodiment of the present application provides a readable storage medium, on which a program is stored, which when executed by a processor, implements the steps of the method for controlling slice flow according to the first aspect, or the steps of the method for controlling slice flow according to the second aspect, or the steps of the method for controlling slice flow according to the third aspect, or the steps of the method for controlling slice flow according to the fourth aspect, or the steps of the method for controlling slice flow according to the fifth aspect, or the steps of the method for controlling slice flow according to the sixth aspect, or the steps of the method for controlling slice flow according to the seventh aspect.

In the embodiment of the application, when the slicing rate of the UE reaches/exceeds the maximum value, the slicing flow is moved to the non-3 GPP access to reduce the slicing rate of the UE and avoid the packet loss of the RAN.

Drawings

In order to more clearly illustrate the technical solutions of the embodiments of the present application, the drawings that are needed in the description of the embodiments of the present application will be briefly described below, and it is obvious that the drawings in the following description are only some embodiments of the present invention, and other drawings may be obtained according to these drawings without inventive effort for a person skilled in the art.

Fig. 1 is a flow chart of a PDU session modification procedure according to an embodiment of the present application;

FIG. 2 is a schematic flow chart of a method for controlling slice flow according to an embodiment of the present disclosure;

FIG. 3 is a second flow chart of a method for controlling slice flow according to an embodiment of the present disclosure;

FIG. 4 is a third flow chart of a method for controlling slice flow according to an embodiment of the present disclosure;

FIG. 5 is a flow chart of a method for controlling slice flow according to an embodiment of the present disclosure;

FIG. 6 is a fifth flow chart of a method for controlling slice flow according to an embodiment of the present disclosure;

FIG. 7 is a flowchart illustrating a method for controlling slice flow according to an embodiment of the present disclosure;

FIG. 8 is a flow chart of a method for controlling slice flow according to an embodiment of the present disclosure;

fig. 9 is one of flow diagrams of an application scenario provided in an embodiment of the present application;

FIG. 10 is a second flowchart of an application scenario provided in the embodiment of the present application;

FIG. 11a is a third flow chart of an application scenario provided in the embodiment of the present application;

FIG. 11b is a flowchart of an application scenario provided in an embodiment of the present application;

FIG. 11c is a fifth flowchart of an application scenario provided in an embodiment of the present application;

FIG. 11d is a flowchart of an application scenario provided in an embodiment of the present application;

fig. 12 is a seventh flowchart of an application scenario provided in the embodiment of the present application;

fig. 13 is a flowchart illustrating an application scenario provided in an embodiment of the present application;

fig. 14 is one of schematic structural diagrams of an AMF entity according to an embodiment of the present application;

fig. 15 is one of schematic structural diagrams of a UE according to an embodiment of the present application;

fig. 16 is one of schematic structural diagrams of an SMF entity according to an embodiment of the present application;

fig. 17 is a schematic structural diagram of a PCF entity according to an embodiment of the present disclosure;

Fig. 18 is a second schematic structural diagram of an SMF entity according to an embodiment of the present disclosure;

FIG. 19 is a second schematic diagram of a PCF entity according to an embodiment of the present disclosure;

fig. 20 is a third schematic structural diagram of a PCF entity according to an embodiment of the present disclosure;

FIG. 21 is a second schematic diagram of an AMF entity according to an embodiment of the present disclosure;

fig. 22 is a second schematic structural diagram of a UE according to an embodiment of the present disclosure;

fig. 23 is a third schematic structural diagram of an SMF entity according to an embodiment of the present disclosure;

fig. 24 is a schematic structural diagram of a PCF entity according to an embodiment of the present disclosure;

Detailed Description

The following description of the technical solutions in the embodiments of the present application will be made clearly and completely with reference to the drawings in the embodiments of the present application, and it is apparent that the described embodiments are some embodiments of the present invention, not all embodiments. All other embodiments, which can be made by those skilled in the art based on the embodiments of the invention without making any inventive effort, are intended to be within the scope of the invention.

In the embodiments of the present application, words such as "exemplary" or "such as" are used to mean serving as examples, illustrations, or descriptions. Any embodiment or design described herein as "exemplary" or "for example" should not be construed as preferred or advantageous over other embodiments or designs. Rather, the use of words such as "exemplary" or "such as" is intended to present related concepts in a concrete fashion.

Relational terms such as "first" and "second", and the like, are used solely to distinguish one from another, and do not necessarily imply a relationship or order between such names.

The techniques described herein are not limited to fifth generation mobile communication (5 th-generation, 5G) systems and subsequent evolution communication systems, and are not limited to LTE/LTE evolution (LTE-Advanced, LTE-a) systems, and may also be used for various wireless communication systems such as code division multiple access (Code Division Multiple Access, CDMA), time division multiple access (Time Division Multiple Access, TDMA), frequency division multiple access (Frequency Division Multiple Access, FDMA), orthogonal frequency division multiple access (Orthogonal Frequency Division Multiple Access, OFDMA), single-carrier frequency division multiple access (Single-carrier Frequency-Division Multiple Access, SC-FDMA), and other systems.

The terms "system" and "network" are often used interchangeably. A CDMA system may implement radio technologies such as CDMA2000, universal terrestrial radio access (Universal Terrestrial Radio Access, UTRA), and the like. UTRA includes wideband CDMA (Wideband Code Division Multiple Access, WCDMA) and other CDMA variants. TDMA systems may implement radio technologies such as the global system for mobile communications (Global System for Mobile Communication, GSM). OFDMA systems may implement radio technologies such as ultra mobile broadband (Ultra Mobile Broadband, UMB), evolved UTRA (E-UTRA), IEEE 802.11 ((Wi-Fi)), IEEE802.16 ((WiMAX)), IEEE 802.20, flash-OFDM, etc. UTRA and E-UTRA are parts of the universal mobile telecommunications system (Universal Mobile Telecommunications System, UMTS). LTE and higher LTE (e.g., LTE-a) are new UMTS releases that use E-UTRA. UTRA, E-UTRA, UMTS, LTE, LTE-a and GSM are described in the literature from an organization named "third generation partnership project" (3rd Generation Partnership Project,3GPP). CDMA2000 and UMB are described in the literature from an organization named "third generation partnership project 2" (3 GPP 2). The techniques described herein may be used for the systems and radio technologies mentioned above as well as for other systems and radio technologies.

For a better understanding of the method according to the embodiments of the present application, the following technical matters are first described:

UE slicing rate

The UE's slice rate includes guaranteed bit rate (Guaranteed Bit Rate, GBR) and non-GBR streaming data associated with a particular slice that is transmitted over a 3GPP access, excluding data associated with the slice that is transmitted over a non-3 GPP access.

GBR flows require guaranteed flow bit rates, and non-GBR flows do not require guaranteed flow bit rates.

(II) policy control

In a 5G system, a policy control function (Policy Control Function, PCF) may decide on access and mobility management (Access and Mobility Management, AM) policies, UE policies and session management (Session Management, SM) policies. The AM policies include access and mobility management related policies, the UE policies include access discovery and selection policies and UE path selection policies, and the SM policies include session management related policies. Wherein the AM policy and the UE policy are determined by the PCF (denoted PCF-AM) selected by the access and mobility management function (Access and Mobility Management Function, AMF), and the SM policy is determined by the PCF (denoted PCF-SM) selected by the SMF. The PCF-AM and PCF-SM may be different PCFs.

(III) PDU session modification procedure

Referring to fig. 1, a PDU session modification procedure is shown.

1. The flow may be triggered by the following events:

(UE initiated modification) the UE initiates the PDU session modification procedure by sending a Non-Access Stratum (NAS) message (N1 SM message packet (PDU session modification request (protocol data unit (Protocol Data Unit, PDU) session ID, packet filter, operation, requested quality of service (Quality of Service, qoS), quarantine (establishment), 5GSM core network capability, packet filter number, [ Always-on PDU Session Requested ])), PDU session ID, UE integrity protection maximum data rate). According to the access type, if the UE is in a Continuity Mode-IDLE (CM-IDLE) state, a service request procedure is initiated before the SM-NAS message. The NAS message is forwarded by the RAN to the AMF and specifies the user location information. AMF calls Nsmf_PDUSion_UpdateSMContex (SM context ID, N1 SM container (PDU session modification request)).

When the UE requests a specific QoS treatment for a service data flow (Service Data Flow, SDF), it carries in the PDU session modification request a packet filter describing the SDF, the requested packet filter operation (add, modify, delete), the requested QoS, and optionally a aggregation indication. The UE provides a setup indication when the UE suggests that the network bind SDFs to one dedicated QoS flow (e.g., even though the existing QoS flow may support the requested QoS). The network should adhere to the UE's request, but the network can still bind the SDF to the existing QoS flow.

(modification of SMF request) PCF performs PCF initiated session management policy modification procedure to inform SMF about policy modification. Such as by policy decisions or AMF requirements.

(modification of SMF request) the unified data management entity (Unified Data Management, UDM) updates the subscription data of the SMF by means of nudm_SDM_notification (subscription permanent identity (Subscription Permanent Identifier, SUPI), session management subscription data). The SMF updates the subscription data and acknowledges to the UDM by returning SUPI.

(modification of SMF request) SMF may decide to modify PDU session. This procedure may also be triggered based on a local policy or by the (R) AN. It may also be triggered if a User Plane (UP) connection is active (as described in the service request flow) and the SMF has identified the state of one or more QoS flows to be deleted in the 5G core network (5G core,5 gc) but not yet synchronized with the UE.

If SMF is in stepUpon receiving one of the triggers, the SMF initiates the PDU session modification procedure requested by the SMF.

(AN initiated modification) when AN resource of QoS Flow is released, the (R) AN should notify SMF whether or not the (R) AN is configured with notification control. The (R) AN sends AN N2 message (PDU session ID, N2 SM information) to the AMF. The N2 SM information includes QoS Flow ID (QFI), user location information, and an indication that QoS flow is released. AMF calls NsppdessionUpdateSMContext (SM context ID, N2 SM information).

(AN-initiated notification control) if notification control is configured in the (R) AN for a certain GBR Flow, the (R) AN sends AN N2 message (PDU session ID, N2 SM information) to the SMF when the (R) AN decides that the QoS target of the QoS Flow cannot be met or that the target can be met again. The N2 SM information includes an indication that the QoS target of the QFI and QoS Flow cannot be met or can be met again. AMF calls NsppdessionUpdateSMContext (SM context ID, N2 SM information). If the PCF subscribes to related events, for PCC rules set to notification control, the SMF reports the related events to the PCF for those rules. If the data network name (Data Network Name, DNN) does not support dynamic policy control and charging (Policy Control and Charging, PCC), the SMF may initiate the PDU session modification procedure requested by the SMF according to the local policy, see step 3b.

2. The SMF may need to report some subscription events to the PCF by performing an SMF initiated session management policy association modification procedure. This step may be skipped if the PDU session modification procedure is triggered by step 1b or 1 d. If dynamic PCC is not deployed, SMF may decide whether to change QoS profiles through local policy.

For UE or AN initiated modification, SMF responds to AMF with nsmf_pduse_update smcontext (N2 SM information (PDU session ID, QFI, qoS profile, session AMBR)), N1 SM container (PDU session modification command (PDU session ID, qoS rules, qoS rule operation, qoS parameters of QoS flow level (if these parameters are needed for QoS flows associated with QoS rules), session aggregate maximum bit rate (Aggregate Maximum Bit Rate, AMBR))).

The N2 SM information carries information that the AMF should provide to the (R) AN, which includes QoS profiles and associated QFI to inform the (R) AN of the QoS flows that need to be added or modified. It may also include only QoS flows that require benefits. If the PDU session modification is triggered by the (R) AN release in step 1e, the N2 SM information carries acknowledgement information of the (R) AN release. If the PDU session modification is requested by the UE and the PDU session for which the modification is requested does not have established user plane resources, the N2 SM information provided to the (R) AN includes information required for establishing the user plane resources.

The N1 SM content packet carries PDU session modification commands provided by the AMF to the UE, the message including QoS rules, qoS parameters at QoS flow level (if these parameters are required for QoS flows associated with QoS rules), qoS rule operation and QoS parameter operation at QoS flow level to inform the UE that one or more QoS rules are added, deleted or modified.

For the modification of the SMF request, the SMF invokes namf_communication_n1n2messagetransfer (N2 SM information (PDU session ID, QFI, qoS profile, session AMBR)), N1 SM container (PDU session modification command (PDU session ID, qoS rule, qoS parameters of QoS flow level (if these parameters are needed for QoS flows associated with QoS rule), qoS rule operation and QoS parameter operation of QoS flow level, session AMBR)).

If the UE is in the CM-IDLE state and ATC is activated, the AMF updates and stores the UE context based on Namf_Communication_N1N2MessageTransferand skips steps 4,5,6 and 7. When the UE is reachable, e.g., when the UE enters the CM-CONNECTED state, the AMF forwards the N1 message to the UE to synchronize the context.

3c, the SMF may request to modify the PDU session as the UDM updates parameters related to the SMF.

4. The AMF may send AN N2 PDU session request (N2 SM information received from the SMF, NAS message (PDU session ID, N1 SM container (PDU session modification command)) message to the (R) AN.

5. The (R) AN may send out UE interaction signaling related to information the UE receives from the SMF. For example, in the case of NG-RAN, RRC connection reconfiguration may be performed when the UE modifies the necessary RAN resources related to the PDU session.

6. The (R) AN can acknowledge the N2 PDU session request by sending AN N2 PDU session acknowledgement (N2 SM information (QFI(s) list accepted/rejected, AN tunnel information, PDU session ID, second radio access type (Radio Access Type, RAT) use data), user location information) message to the AMF. In the case of dual connectivity, if one or more QFI are added to the PDU session, the master RAN node may assign one or more of these QFI to a RAN node that has not previously transmitted PDU session data. In this case, the AN tunnel information contains new N3 tunnel endpoint information of QFI assigned to the new RAN node. Accordingly, if one or more QFI are removed from the PDU session, resulting in the PDU session no longer including the RAN node, the corresponding tunnel endpoint is removed from the AN tunnel. The NG-RAN may reject QFI that fails to satisfy the user plane security enforcement information, e.g., exceeds the UE integrity protection maximum data rate.

7. The AMF forwards the N2 SM information and the user location information received from the AN to the SMF through AN nsmf_pduse_updatsmcontext service operation. If (R) AN refuses QFI, SMF is responsible for updating QoS rules in UE, qoS parameters of QoS flow class (if QoS flows associated with QoS rules require these parameters). The N2 SM information may include second RAT usage data.

8. For the user plane functions (User plane Function, UPF) affected by the PDU session modification, the SMF sends an N4 session modification request message to these UPFs, updating the N4 session.

If a QoS flow is to be created, the SMF updates the UPF with the upstream packet detection rules of the new QoS flow.

Note that: this allows the uplink packets of the QFI with the new QoS flow to be forwarded.

9. The UE transmits a NAS message (PDU session ID, N1 SM container (PDU session modification command acknowledgement)) message to acknowledge the PDU session modification command.

10. The (R) AN forwards the NAS message to the AMF.

11. The AMF transmits the N1 SM container and the user location information received from the AN to the SMF. The SMF replies to the NspPDUSion UpdateSMContext reply.

If the SMF initiated modification deletes the QoS flow (e.g., PCF triggered), wherein the QoS flow associated with the default QoS rule is not included, and the SMF does not receive a response from the UE, the SMF identifies the state of the QoS flow to be synchronized with the UE.

12. The SMF may update the N4 session of the UPF included in the PDU session, and the SMF transmits an N4 session modification request (N4 session ID) to the UPF. For the PDU session of Ethernet PDU Session Type, the SMF may inform the UPF to add or delete Ethernet packet filter sets and forwarding rules.

13. If the SMF interacts with the PCF in step 1b or 2, the SMF informs the PCF whether the PCC decision can be performed by performing an SMF initiated session management policy association modification procedure.

(IV) ATSSS

The PDU session may support the following services:

(1) Single access PDU connection service: PDU sessions are related to one access type at a particular time, i.e. 3GPP access or non-3 GPP access, or

(2) Multi-access PDU connection service: the PDU session is associated with both 3GPP access and non-3 GPP access.

A PDU session supporting a single access PDU connection service is called a single access PDU session, and a PDU session supporting a multiple access PDU connection service is called a multiple access PDU (MA PDU) session, which is used to support the ats characteristics.

Access traffic grooming, switching and Splitting (Access Traffic Steering, ats) techniques may enable a UE or network to select an access network for new and existing data flows and to transmit data for one data flow over a different access network.

In the process of establishing MA PDU session, PCF formulates MA PDU session control strategy and sends it to SMF. The SMF decides an N4 rule and an ATSSS rule according to the MA PDU session control strategy, and sends the rules to the UPF and the UE respectively.

These rules include traffic matching information, grooming functions and grooming patterns. When the UPF/UE finds traffic matching the traffic matching information, the matched traffic is transmitted to a specific access using a grooming function and a grooming mode corresponding thereto.

A UE supporting ats may support one or more of the following grooming functions:

(1) A high-layer grooming function, working above the IP layer;

rel-16 defines only one high-level grooming function based on the MPTCP protocol, referred to as the "MPTCP function", which can groom, exchange, and separate TCP traffic generated by applications using MPTCP. The MPTCP function in the UE communicates with the MPTCP proxy function in the UPF over the 3GPP and/or non-3 GPP user plane using the MPTCP protocol.

(2) A lower layer grooming function, working below the IP layer;

rel-16 defines a lower Layer grooming function called "ATSSS Low-Layer (ATSSS-LL) function". The grooming function can groom, exchange and separate all types of traffic, including TCP traffic, UDP traffic, ethernet traffic, etc. UPF also needs to support ATSSS-LL functionality.

The currently supported grooming modes are as follows:

(1) Active-Standby: when a certain access is available, the SDF is dredged to that access (Active access), and when the Active access becomes unavailable, the SDF is dredged to other accesses (Standby access). When an active access becomes available again, the SDF will be dredged back to the access. If no backup access is specified, the SDF can only be transmitted at the active access.

(2) Smallest Delay: the SDF is groomed to the access with the smallest Round Trip Time (RTT). The UE and UPF may decide RTTs for 3GPP access and non-3 GPP access according to the measurement information. When one access becomes unavailable, all traffic of the traffic data flows are switched to the other available access if the PCC rules allow.

(3) Load-Balancing: traffic data flows are split between 3GPP access and non-3 GPP access. The pattern includes the percentage of SDF traffic sent at 3GPP access and non-3 GPP access. This mode is only applicable to non-GBR QoS flows. When one access becomes unavailable, all traffic data flows are switched to the available access if 100% of the traffic data flows can be transmitted over the available access.

(4) Priority-based: all traffic of the traffic data flows is led to the high priority access until the access is congested. At this time, the traffic of the service data flow may also be sent through low priority access, i.e. the traffic of the service data flow is split into 2 access transmissions. In addition, when high priority access becomes unavailable, all traffic of the SDF is sent over low priority access. How the UE and UPF decide on access congestion depends on implementation.

Referring to fig. 2, an embodiment of the present application provides a method for controlling slice flow, where an execution body of the method is an AMF, and the method includes the following steps:

step 201: receiving a first message sent by the RAN, wherein the first message comprises first indication information and a slice identifier;

in the embodiment of the present application, the first indication information is used to indicate that the slicing rate of the UE is lower than, reaches or exceeds the maximum value.

Specifically, when the RAN detects that the slice rate of the UE is lower than, reaches or exceeds the maximum value, the RAN sends an N2 message (i.e., a first message) to the AMF, where the message parameter includes the first indication information and the slice identifier (Single Network Slice Selection Assistance Information, S-NSSAI).

Step 202: sending a second message to any one of UE, SMF, PCF or NWDAF, wherein the second message comprises the first indication information and the slice identifier;

in the embodiment of the application, the AMF may choose to send the first indication information and the slice identifier to any one of UE, SMF, PCF or NWDAF to implement modification of the PDU session policy of the UE, so as to move the traffic of the UE to the non-3 GPP access.

In the case that the AMF sends the second message to the UE, the first indication information is used to indicate that the slicing rate of the UE reaches a maximum value, and before the second message is sent to the UE, the method further includes: the allowable slice identifier for determining the non-3 GPP access of the UE includes the slice identifier described above, that is, whether the S-nsai belongs to an Allowed nsai for the non-3 GPP access, and if so, the AMF sends a second message to the UE.

Referring to fig. 3, a method for performing control slice flow for a UE with a body in case the AMF sends a second message to the UE is shown, the method comprising the steps of:

step 301: receiving a second message sent by the AMF, wherein the second message comprises the first indication information and the slice identifier, and then executing step 302, step 303 or step 304;

in the embodiment of the present application, the first indication information is used to indicate that the slicing rate of the UE reaches or exceeds a maximum value;

in the case that the UE supports a Multiple Access (MA) PDU session, it is determined whether to establish a MA PDU in the case that the UE supports the MA PDU session, and a different procedure is performed.

Step 302: when the UE supports the MA PDU session and the MA PDU is established, sending a third message to the UPF, where the UPF sends a fourth message to the SMF, where the third message and the fourth message include the second indication information, and then performing step 3021;

in the embodiment of the application, the second indication information is used for indicating that the 3GPP access rate reaches the maximum value;

step 3021: receiving the ats ss rule sent by the SMF, and then executing step 3022;

step 3022: according to the ATSSS rule, the slice flow is led to the non-3 GPP access;

in the embodiment of the application, the UE supports MA PDU session, and when MA PDU is established, the UE notifies the UPF of the event that the slicing rate reaches the maximum value, the UPF reports the event to the SMF, the SMF reports the event to the PCF, the PCF updates MA PDU session control strategy, and the SMF returns ATSSS rule to the UE, thereby realizing that the UE dredges the slicing flow to the non-3 GPP access according to the ATSSS rule.

Step 303: when the UE supports MA PDU session and does not establish MA PDU, sending a PDU session establishment request to the SMF, where the PDU session establishment request includes second indication information, and then executing step 3031;

step 3031: receiving the ats ss rule sent by the SMF, and then executing step 3032;

step 3032: according to the ATSSS rule, the slice flow is led to the non-3 GPP access;

in the embodiment of the application, the UE supports MA PDU session, and does not establish MA PDU, then the UE requests to establish MA PDU session, the UE can carry the indication that the slicing rate of the UE reaches the maximum value in the request, the SMF sends the indication to the PCF, and the PCF formulates MA PDU session control strategy to dredge the traffic to non-3 GPP access; or the UE notifies the UPF of an event that the slice rate reaches the maximum value after establishing the MA PDU session

Step 304: when the UE does not support MA PDU sessions and there is new traffic to send to the slice, the slice traffic is groomed to the non-3 GPP access.

Referring to fig. 4, there is shown a method of performing control slice traffic with a body of SMF in case the AMF transmits a second message to the UE, the method comprising the steps of:

step 401: receiving a third message sent by the UPF, wherein the third message comprises second indication information;

Step 402: transmitting second indication information to the PCF;

in some embodiments, the method further comprises: receiving updated MA PDU session strategy sent by PCF; the ats rules are sent to the UE and the N4 rules are sent to the UPF.

In the embodiment of the present application, the SMF receives different PDU session commands from the PCF according to whether the UE establishes the MA PDU, specifically, see the above-mentioned UE-side processing flow.

Referring to fig. 5, a method for performing control of slice traffic with PCF as a body is shown in the case where the AMF sends a second message to the UE, the method comprising the steps of:

step 501: receiving second indication information sent by the SMF;

step 502: updating MA PDU session strategy;

step 503: sending updated MA PDU session policy to SMF;

specifically, updating the MA PDU session policy includes:

setting a breakout mode to be based on priority-based, and setting a priority of non-3 GPP access to be highest;

alternatively, the grooming mode is set to active-standby (active-standby) and the active access is set to non-3 GPP access.

Referring to fig. 6, there is shown a method of performing control slice traffic for an SMF having a body in the case where the AMF transmits a second message to the SMF, the method comprising the steps of:

Step 601: receiving a second message sent by the AMF, wherein the second message comprises first indication information and a slice identifier;

in the embodiment of the present application, the first indication information is used to indicate that the slicing rate of the UE reaches a maximum value;

step 602: transmitting first indication information and a slice identifier to the PCF;

in some embodiments, the method further comprises: receiving an updated PDU session policy sent by the PCF; and initiating a PDU session modification process according to the updated PDU session policy.

Referring to fig. 7, there is shown a method of performing control of slice traffic with a PCF as a body in the case where an AMF sends a second message to an SMF, the method comprising the steps of:

step 701: receiving first indication information and a slice identifier sent by SMF;

step 702: updating PDU session policy;

step 703: sending the updated PDU session policy to the SMF;

in some embodiments, updating the PDU session policy includes:

updating MA PDU session policy associated with the slice identifier;

and/or adjusting a guaranteed stream bit rate (GFBR) of the GBR QoS flow;

and/or releasing QoS flow;

and/or modifying the QoS of the PDU session.

Further, if the UE establishes a plurality of PDU sessions related to the S-nsai and the SMFs associated with these PDU sessions are different, the above-mentioned transmitting the updated PDU session policy to the SMFs specifically includes: transmitting the updated PDU session policy to a target SMF of the plurality of SMFs;

the UE establishes a plurality of PDU sessions related to the slice identifier, and a plurality of SMFs associated with the plurality of PDU sessions are different, wherein the target SMF is any one of the plurality of SMFs, or the target SMF is one SMF with the largest associated PDU session, or the target SMF is one SMF with the largest GBR QoS flow.

Referring to fig. 8, there is shown a method of performing control of a slice traffic for a PCF including PCF-AM and PCF-SM by a body in case an AMF sends a second message to the PCF, the method comprising the steps of:

step 801: the PCF-AM receives first indication information and a slice identifier sent by the AMF;

Step 802: the PCF-AM sends first indication information and a slice identifier to the PCF-SM;

step 803: the PCF-SM sends PDU session policy to the SMF.

In the embodiment of the application, PCF-SM updates the strategy of PDU session, MA PDU session strategy and the like to SMF, and the SMF initiates PDU session modification process.

In some embodiments, after the SMF initiates the PDU session modification procedure, the method further comprises: the PCF-AM sends a fifth message to the AMF, the fifth message including a UE policy for grooming traffic associated with the slice identity to the non-3 GPP access.

In some embodiments, for the case that the AMF sends the second message to the NWDAF, the AMF may further provide the NWDAF with the slice rate of the UE, the NWDAF stores and analyzes the historical data, the NWDAF determines to offload a part of the traffic of the UE to the non-3 GPP access according to the slice rate trend of the UE and the traffic behavior of the UE (SMF provision), and the NWDAF provides the PCF with the traffic information and the target access.

The invention will now be described with reference to specific examples.

Embodiment one:

the present embodiment introduces that the AMF sends an indication to the UE that the UE's slicing rate reaches a maximum, and the UE uses the MA PDU session to groom the 3GPP access traffic to the non-3 GPP access. The specific process is as shown in fig. 9:

1. the RAN monitors that the UE 'S slicing rate reaches a maximum value, and the RAN sends an N2 message to the AMF, the parameters including S-NSSAI and an indication that the UE' S slicing rate reaches a maximum value.

2. The AMF sends a NAS message to the UE, the parameters including S-NSSAI and an indication that the UE' S slice rate reaches a maximum.

If the UE has established a MA PDU session, the following steps are performed:

3. the UE sends an access report to the UPF, the parameters including an indication that the 3GPP access rate reaches a maximum.

4. The UPF sends an N4 report to the SMF, the parameters including an indication that the 3GPP access rate reaches a maximum.

5. The SMF sends an npcf_smpolicy control_update request (an indication that the 3GPP access rate reaches a maximum value) to the PCF.

6. The PCF updates the MA PDU session control policy, e.g., sets the breakout mode to priority-based and the priority of non-3GPP access to highest, or sets the breakout mode to active-standby and the active access to non-3GPP access.

7. The SMF sends PDU session modification command to the UE and updated ATSSS rule to the UE.

8. The SMF sends an N4 session modification request to the UPF and sends updated N4 rules to the UPF.

If the UE does not establish the MA PDU session, the following steps are performed:

3. the UE sends PDU session establishment request to SMF, and the message carries the indication that the 3GPP access rate reaches the maximum value.

Step 4-7, as in step 5-8 in the scenario of "UE has established MA PDU session" described above.

Alternatively, the UE may first add a non-3GPP access to the MA PDU session and then perform steps 3-8 in accordance with the scenario "UE has established MA PDU session".

Embodiment two:

the present embodiment describes an event that the AMF notifies the PCF of the maximum slice rate via the SMF, and the PCF performs rate control. As particularly shown in fig. 10.

2. The AMF sends a notification to SMF1 (S-nsai, UE slicing rate reaches maximum). If the UE establishes a plurality of PDU sessions associated with the S-nsai and the SMFs associated with the PDU sessions are different, the AMF selects one of the SMFs to send a notification message, such as a random selection, or the SMF associated with the most PDU sessions.

3. The SMF1 sends a notification message to the PCF that the parameters including S-NSSAI and the UE' S slice rate reach a maximum. SMF1 may also send an npcf_smpolicicontrol_update request message to the PCF at this step, the message including that the UE's slicing rate reaches a maximum.

4. The PCF makes policy decisions, such as updating the MA PDU session policy for the MA PDU session associated with the S-nsai, and adjusts the GFBR for GBR QoS flows. And then sending an npcf_smpolicy control_update notification message to the SMF, the message including the updated PCC rule. If the UE establishes multiple PDU sessions associated with S-NSSAI and the SMFs associated with these PDU sessions are different, the PCF selects one or more SMFs from among them for policy adjustment, such as random selection, or SMFs associated with the most PDU sessions, or SMFs with the most GBR QoS flows.

5. The SMF initiates a PDU session modification procedure.

Embodiment III:

the present embodiment describes the case where the AMF directly sends the PCF an event that the UE's slice rate reaches/exceeds the maximum value, as shown in fig. 11 a.

1. The RAN sends an N2 message to the AMF, and the parameters include S-NSSAI and the UE' S slice rate reaching/exceeding the maximum value.

2. The AMF sends an Npcf_AMPolicControl_Update Request to the PCF-AM, and the message includes the S-NSSAI and the UE' S slice rate up to/exceeding the maximum.

3. The PCF-AM sends the Npcf-UEPolicyControl_UpdateNotify or the Npcf-EventExposure_Notify to the PCF-SM, and the message includes the S-NSSAI and the slice rate of the UE reaching/exceeding the maximum value.

4. The PCF-SM sends an npcf_smpolicy control_update notification message to the SMF, updates the PDU session policy, MA PDU session policy, etc.

5. The SMF initiates a PDU session modification procedure.

6. PCF-AM sends to AMF an npcf_uepolicy control_ UpdateNotify Request message including the UE policy. PCF-AM may groom traffic related to S-NSSAI to non-3 GPP access in UE policy. There is no restriction of the order of steps 6 and 3.

7. The AMF sends a UE configuration update command to the UE, and the parameters are UE strategies.

When the RAN finds that the UE's slice rate is below the maximum value, the RAN reports the event to the AMF, which informs the PCF of the event. The specific process is shown in fig. 11 b.

1. The RAN sends an N2 message to the AMF, the parameters including S-NSSAI and the UE' S slice rate being below a maximum value.

2. The AMF sends an Npcf_AMPolicControl_Update Request to the PCF-AM, the message includes S-NSSAI and the UE' S slice rate is below the maximum.

3. The PCF-AM sends the Npcf-UEPolicyControl_UpdateNotify or the Npcf-EventExposure_Notify to the PCF-SM, and the message includes that the S-NSSAI and the slicing rate of the UE are below the maximum.

The PCF may make new policy decisions based on the direction of the RAN, i.e. perform steps 4 and 6 in fig. 11 a.

In this embodiment, the PCF-AM and PCF-SM may be the same PCF, and step 3 need not be performed. If the PCF-AM and the PCF-SM are different PCFs, the method by which the PCF-AM obtains the information of the PCF-SM is described below.

The method is as shown in FIG. 11 c:

1. the AMF sends a request message to the SMF, the message including a PDU session ID or S-NSSAI, possibly carrying an indication of the request PCF-SM information.

2. The SMF replies to the AMF with the identity of the PCF-SM it selected for the PDU session.

3. The AMF sends an Npcf_AMPolicControl_Update request to the PCF-AM, the message includes S-NSSAI, the UE' S slice rate reaches/exceeds/falls below a maximum value, PCF-SM ID.

The second method is as shown in FIG. 11 d:

1. the AMF sends Nsmf_PDUSion_ CreateSMContext Request to the SMF, and the parameters include PCF-AM.

2. The SMF selects PCF-SM, if it is different from PCF-AM provided by AMF, then the SMF sends to PCF-SM the PCF-SMPolicyControl_Create Request message carrying PCF-AM ID.

3. The PCF-SM sends to the PCF-AM an Npcf_EventExposure_Subscribe message including the UE ID and S-NSSAI.

4. When the PCF-AM receives an event related to the S-NSSAI, the PCF-AM sends an Npcf_EventExponsure_Notif to the PCF-SM, the message includes the UE ID, the S-NSSAI, and the slicing rate of the UE reaches/exceeds/falls below a maximum value.

Embodiment four:

this embodiment describes a procedure in which the RAN informs the SMF when the RAN finds that the UE's slicing rate reaches/exceeds a maximum value. As particularly shown in fig. 12.

1. The RAN sends an N2 message to the AMF, the message including N2 SM information (the UE's slice rate reaches a maximum value) and PDU session ID.

2. AMF sends Nsmf_PDUSion_UpdateSMContext (N2 SM information) to SMF.

3. The SMF sends either an npcf_smplicycontrol_update request to the PCF (UE 'S slice rate exceeds/reaches a maximum value) or a notification message to the PCF (S-NSSAI, UE' S slice rate exceeds/reaches a maximum value).

4. The PCF sends an NPcf_SMPolicyControl_update reply/notification to the SMF, updating the PCC rules of the UE.

5. The SMF initiates a PDU session modification procedure. If the RAN sends an indication to the SMF that the UE's slice rate reaches/exceeds a maximum value, caused by a PDU session modification procedure, e.g., the UE or PCF requests to establish a new GBR QoS flow, if it cannot be established, the SMF denies the PDU session modification procedure.

Note that the SMF in step 4 may be different from the SMF in step 2.

After the PCF receives step 3, the policy rules for the PDU session related to S-nsai established by the UE may be adjusted, for example GFBR to reduce GBR QoS flow, or trigger release of PDU session and reestablishment within the non-3 GPP access, or update MA PDU session policy to move traffic to the non-3 GPP access.

Fifth embodiment:

this embodiment describes the NWDAF decision splitting process. As shown in particular in fig. 13.

1. The AMF sends an event notification to the NWDAF, the message including S-nsai, the slice rate/the slice rate of the UE, which is the average or peak rate of data transmitted by the slice/UE over a period of time.

2. The NWDAF stores the data provided by the AMF, analyzes the historical data, and obtains the change trend of the slice rate of the slice/UE. When NWDAF finds that the slice rate of slice/UE reaches/exceeds the maximum slice rate of slice or UE, NWDAF analyzes the traffic behavior of UE (e.g. UE typically uses traffic of non-3 GPP access transmission, different traffic occupies proportion of slice rate), and sends analysis notification to PCF-SMF, including UE identification, traffic description, access technology in the message. The PCF-SM updates the UE strategy or the strategy of the PDU session according to the information provided by the NWDAF.

Referring to fig. 14, an embodiment of the present application provides an AMF entity 1400, including:

a first receiving module 1401, configured to receive a first message sent by the RAN, where the first message includes first indication information and a slice identifier, where the first indication information is used to indicate that a slice rate of the UE is lower than, reaches or exceeds a maximum value;

a first sending module 1402, configured to send a second message to any one of the UE, SMF, PCF or NWDAF, where the second message includes the first indication information and the slice identifier.

before sending the second message to the UE, the first sending module 1402 further includes:

a determining unit, configured to determine that an allowed slice identifier of a non-3 GPP access of the UE includes the slice identifier.

Referring to fig. 15, an embodiment of the present application provides a UE 1500, including:

a second receiving module 1501, configured to receive a second message sent by the AMF, where the second message includes first indication information and a slice identifier, where the first indication information is used to indicate that a slice rate of the UE reaches or exceeds a maximum value;

a second sending module 1502, configured to send a third message to a user plane function UPF when the UE supports a multi-access MA PDU session and a MA PDU is established, where the UPF sends a fourth message to the SMF, and the third message and the fourth message include second indication information, where the second indication information is used to indicate that a 3GPP access rate reaches a maximum value;

A third receiving module 1503, configured to receive an ats ss rule sent by the SMF;

a first control module 1504 is configured to groom slice traffic to a non-3 GPP access according to the ats rules.

Further, the second sending module 1502 is further configured to send a PDU session establishment request to the SMF when the UE supports a MA PDU session and no MA PDU is established, where the PDU session establishment request includes the second indication information;

the third receiving module 1503 is further configured to receive an ats ss rule sent by the SMF;

the first control module 1504 is further configured to groom the slice traffic to a non-3 GPP access according to the ats ss rule.

Further, the first control module 1504 is further configured to, when the UE does not support the MA PDU session and there is new traffic to send to the slice, drain the slice traffic to the non-3 GPP access.

Referring to fig. 16, an embodiment of the present application provides an SMF entity 1600, including:

a fourth receiving module 1601, configured to receive a third message sent by the UPF, where the third message includes second indication information, where the second indication information is used to indicate that a 3GPP access rate reaches a maximum value;

and a third sending module 1602, configured to send the second indication information to the PCF.

Further, the fourth receiving module 1501 is further configured to receive an updated MA PDU session policy sent by the PCF;

the third sending module 1602 is further configured to send an ats rule to the UE and send an N4 rule to the UPF.

Referring to fig. 17, an embodiment of the present application provides a PCF entity 1700, including:

a fifth receiving module 1701, configured to receive second indication information sent by the SMF, where the second indication information is used to indicate that the 3GPP access rate reaches a maximum value;

a first updating module 1702 configured to update MA PDU session policies;

a fourth sending module 1703, configured to send an updated MA PDU session policy to the SMF.

Further, a first updating module 1702 configured to set a grooming mode to be based on priority-based, and set a priority of the non-3 GPP access to be highest;

Referring to fig. 18, an embodiment of the present application provides an SMF entity 1800, including:

a sixth receiving module 1801, configured to receive a second message sent by the AMF, where the second message includes first indication information and a slice identifier, and the first indication information is used to indicate that a slice rate of the UE reaches a maximum value;

A fifth sending module 1802, configured to send the first indication information and the slice identifier to a PCF.

Further, a sixth receiving module 1801 is configured to receive an updated PDU session policy sent by the PCF;

a fifth sending module 1802, configured to initiate a PDU session modification procedure according to the updated PDU session policy.

Referring to fig. 19, an embodiment of the present application provides a PCF entity 1900, including:

a seventh receiving module 1901, configured to receive first indication information and a slice identifier sent by an SMF, where the first indication information is used to indicate that a slice rate of the UE reaches a maximum value;

a second updating module 1902, configured to update a PDU session policy;

a sixth sending module 1903 is configured to send the updated PDU session policy to the SMF.

Further, a second updating module 1902 is configured to update a MA PDU session policy associated with the slice identifier; and/or, adjusting a guaranteed bit rate GFBR of the guaranteed bit rate quality stream GBR QoS flow and/or releasing the QoS flow; and/or modifying the QoS of the PDU session.

Further, a sixth sending module 1903, configured to send the updated PDU session policy to a target SMF of the plurality of SMFs;

Referring to fig. 20, an embodiment of the present application provides a PCF entity 2000, where the PCF entity includes a PCF-AM and a PCF-SM, and the PCF entity 2000 further includes:

a seventh sending module 2001, configured to receive, by using the PCF-AM, first indication information and a slice identifier sent by the AMF, where the first indication information is used to indicate that a slice rate of the UE is lower than, reaches or exceeds a maximum value;

an eighth sending module 2002, configured to send, by the PCF-AM, the first indication information and the slice identifier to the PCF-SM;

a ninth sending module 2003, configured to send a PDU session policy to the SMF by the PCF-SM.

Further, a ninth sending module 2003 is configured to send a fifth message to the AMF by the PCF-AM, where the fifth message includes a UE policy, where the UE policy is used to dredge traffic related to the slice identifier to a non-3 GPP access.

Referring to fig. 21, an embodiment of the present invention provides an AMF entity 2100, including: the processor 2101, the transceiver 2102, the memory 2103, and the bus interface.

The processor 2101 may be responsible for managing the bus architecture and general processing, among other things. The memory 2103 may store data used by the processor 2101 in performing operations.

In an embodiment of the present invention, the AMF entity 2100 may further include: a program stored on the memory 2103 and executable on the processor 2101, which when executed by the processor 2101 performs the steps of the method provided by an embodiment of the present invention.

In fig. 21, a bus architecture may comprise any number of interconnected buses and bridges, with various circuits of one or more processors, as represented by the processor 2101, and memory, as represented by the memory 2103, linked together. The bus architecture may also link together various other circuits such as peripheral devices, voltage regulators, power management circuits, etc., all as are well known in the art and, therefore, further description of embodiments of the present invention will not be provided. The bus interface provides an interface. The transceiver 2102 may be a number of elements, i.e., including a transmitter and a receiver, providing a means for communicating with various other apparatus over a transmission medium.

Referring to fig. 22, an embodiment of the present invention provides a UE 2200 comprising: a processor 2201, a transceiver 2202, a memory 2203, and a bus interface.

Referring to fig. 23, an embodiment of the present invention provides an SMF entity 2300, including: a processor 2301, a transceiver 2302, a memory 2303 and a bus interface.

Referring to fig. 24, an embodiment of the present invention provides a PCF entity 2400, including: processor 2401, transceiver 2402, memory 2403, and bus interfaces.

The above-described structure descriptions of the UE 2200, the SMF entity 2300 and the PCF entity 2400 may refer to the corresponding descriptions of the AMF entity 2100 in fig. 21, and are not repeated herein.

The embodiment of the invention also provides a computer readable storage medium, on which a computer program is stored, which when executed by a processor, implements the processes of the above method embodiment, and can achieve the same technical effects, and in order to avoid repetition, the description is omitted here. Wherein the computer readable storage medium is selected from Read-Only Memory (ROM), random access Memory (Random Access Memory, RAM), magnetic disk or optical disk.

It should be noted that, in this document, the terms "comprises," "comprising," or any other variation thereof, are intended to cover a non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements does not include only those elements but may include other elements not expressly listed or inherent to such process, method, article, or apparatus. Without further limitation, an element defined by the phrase "comprising one … …" does not exclude the presence of other like elements in a process, method, article, or apparatus that comprises the element.

Claims

1. A method for controlling slice traffic for a UE, the method comprising:

when the UE supports a multi-access MAPDU session and the MAPDU session is established, a third message is sent to a user plane function UPF, the UPF sends a fourth message to an SMF, the third message and the fourth message comprise second indication information, and the second indication information is used for indicating that the 3GPP access rate reaches the maximum value;

2. The method of claim 1, wherein after receiving the second message sent by the AMF, the method further comprises:

receiving an ATSSS rule sent by the SMF;

3. The method of claim 1, wherein after receiving the second message sent by the AMF, the method further comprises:

4. A method of controlling slice flow, for use in SMF, the method comprising:

and sending the second indication information to the PCF, wherein the second indication information is used for leading the slice traffic of the UE to the non-3 GPP access.

5. The method according to claim 4, wherein the method further comprises:

receiving an updated MA PDU session policy sent by the PCF;

an ats rule is sent to the UE and an N4 rule is sent to the UPF.

6. A method of controlling slice flow for a PCF, the method comprising:

updating MA PDU session strategy;

and sending updated MA PDU session policy to the SMF for grooming the slice traffic of the UE to the non-3 GPP access.

7. The method of claim 6, wherein updating the MA PDU session policy comprises:

8. A method of controlling slice flow, for use in SMF, the method comprising:

and sending the first indication information and the slice identifier to PCF, wherein the first indication information and the slice identifier are used for leading the slice traffic of the UE to the non-3 GPP access.

9. The method of claim 8, wherein the method further comprises:

receiving an updated PDU session policy sent by the PCF;

10. A method of controlling slice flow for a PCF, the method comprising:

Updating PDU session policy;

and sending the updated PDU session policy to the SMF for grooming the slice traffic of the UE to the non-3 GPP access.

11. The method of claim 10, wherein updating the PDU session policy comprises:

updating MA PDU session policies associated with the slice identity.

12. The method of claim 10, wherein the sending the updated PDU session policy to the SMF comprises:

13. A method of controlling slice traffic for a PCF, the PCF comprising a PCF-AM and a PCF-SM, the method comprising:

the PCF-AM receives first indication information and a slice identifier sent by an AMF, wherein the first indication information is used for indicating that the slice rate of UE reaches or exceeds a maximum value;

and the PCF-SM sends PDU session policy to the SMF for guiding the slice traffic of the UE to the non-3 GPP access.

14. The method of claim 13, wherein the step of determining the position of the probe is performed,

the PCF-AM sends a fifth message to the AMF, wherein the fifth message comprises a UE strategy which is used for leading the traffic related to the slice identifier to a non-3 GPP access.

15. The method of claim 14, wherein the method further comprises:

the PCF-AM receives indication information and the slice identification from the AMF, wherein the indication information is used for indicating that the slice rate of the UE is lower than the maximum value;

and the PCF-AM sends the indication information for indicating that the slice rate of the UE is lower than the maximum value and the slice identification to the PCF-SM.

16. A UE, comprising:

A third receiving module, configured to receive an ats ss rule sent by the SMF;

17. An SMF entity, comprising:

and a third sending module, configured to send the second indication information to the PCF, where the second indication information is used for slice traffic grooming of the UE to a non-3 GPP access.

18. A PCF entity, comprising:

a first updating module, configured to update MA PDU session policy;

and a fourth sending module, configured to send an updated mappdu session policy to the SMF, configured to groom slice traffic of the UE to a non-3 GPP access.

19. An SMF entity, comprising:

And a fifth sending module, configured to send the first indication information and the slice identifier to a PCF, and configured to dredge slice traffic of the UE to a non-3 GPP access.

20. A PCF entity, comprising:

a second updating module, configured to update a PDU session policy;

and a sixth sending module, configured to send an updated PDU session policy to the SMF, configured to groom the slice traffic of the UE to a non-3 GPP access.

21. A PCF entity comprising a PCF-AM and a PCF-SM, the PCF entity further comprising:

a seventh sending module, configured to receive, by using the PCF-AM, first indication information and a slice identifier sent by the AMF, where the first indication information is used to indicate that a slice rate of the UE reaches or exceeds a maximum value;

and a ninth sending module, configured to send a PDU session policy to the SMF by using the PCF-SM, and configured to dredge the slice traffic of the UE to a non-3 GPP access.

22. A UE comprising a processor, a memory and a program stored on the memory and executable on the processor, which when executed by the processor, implements the steps of the method of controlling slice flow of any one of claims 1 to 3.

23. An SMF entity comprising a processor, a memory and a program stored on said memory and executable on said processor, said program when executed by said processor implementing the steps of the method of controlling slice traffic as claimed in claim 4 or 5 or the steps of the method of controlling slice traffic as claimed in claim 8 or 9.

24. PCF entity comprising a processor, a memory and a program stored on the memory and executable on the processor, which program, when executed by the processor, implements the steps of the method of controlling slice traffic of claim 6 or 7, or the steps of the method of controlling slice traffic of any of claims 10 to 12, or the steps of the method of controlling slice traffic of any of claims 13 to 15.

25. A readable storage medium, wherein the readable storage medium has stored thereon a program which, when executed by a processor, implements the steps of the method of controlling a slice flow as claimed in any one of claims 1 to 3, or the steps of the method of controlling a slice flow as claimed in claim 4 or 5, or the steps of the method of controlling a slice flow as claimed in claim 6 or 7, or the steps of the method of controlling a slice flow as claimed in claim 8 or 9, or the steps of the method of controlling a slice flow as claimed in any one of claims 10 to 12, or the steps of the method of controlling a slice flow as claimed in any one of claims 13 to 15.