WO2021159884A1 - METHOD AND NETWORK NODE FOR QoS NOTIFICATION - Google Patents

METHOD AND NETWORK NODE FOR QoS NOTIFICATION Download PDF

Info

Publication number
WO2021159884A1
WO2021159884A1 PCT/CN2020/141702 CN2020141702W WO2021159884A1 WO 2021159884 A1 WO2021159884 A1 WO 2021159884A1 CN 2020141702 W CN2020141702 W CN 2020141702W WO 2021159884 A1 WO2021159884 A1 WO 2021159884A1
Authority
WO
WIPO (PCT)
Prior art keywords
qos
guaranteed
notification
requested
network node
Prior art date
Application number
PCT/CN2020/141702
Other languages
English (en)
French (fr)
Other versions
WO2021159884A8 (en
Inventor
Wenliang Xu
Original Assignee
Telefonaktiebolaget Lm Ericsson (Publ)
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 Telefonaktiebolaget Lm Ericsson (Publ) filed Critical Telefonaktiebolaget Lm Ericsson (Publ)
Priority to EP20918461.3A priority Critical patent/EP4104507A4/en
Priority to JP2022547774A priority patent/JP7408824B2/ja
Priority to KR1020227029402A priority patent/KR20220133250A/ko
Priority to CN202080096242.9A priority patent/CN115299097A/zh
Priority to CN202310365322.5A priority patent/CN116455771A/zh
Priority to US17/799,151 priority patent/US20230081774A1/en
Priority to TW110102632A priority patent/TW202137796A/zh
Publication of WO2021159884A1 publication Critical patent/WO2021159884A1/en
Publication of WO2021159884A8 publication Critical patent/WO2021159884A8/en
Priority to CONC2022/0011769A priority patent/CO2022011769A2/es

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/34—Signalling channels for network management communication
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W28/00—Network traffic management; Network resource management
    • H04W28/02—Traffic management, e.g. flow control or congestion control
    • H04W28/0268—Traffic management, e.g. flow control or congestion control using specific QoS parameters for wireless networks, e.g. QoS class identifier [QCI] or guaranteed bit rate [GBR]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W28/00—Network traffic management; Network resource management
    • H04W28/16—Central resource management; Negotiation of resources or communication parameters, e.g. negotiating bandwidth or QoS [Quality of Service]
    • H04W28/24—Negotiating SLA [Service Level Agreement]; Negotiating QoS [Quality of Service]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/50—Network service management, e.g. ensuring proper service fulfilment according to agreements
    • H04L41/5003—Managing SLA; Interaction between SLA and QoS
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/50—Network service management, e.g. ensuring proper service fulfilment according to agreements
    • H04L41/5003—Managing SLA; Interaction between SLA and QoS
    • H04L41/5019—Ensuring fulfilment of SLA
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/50—Network service management, e.g. ensuring proper service fulfilment according to agreements
    • H04L41/5041—Network service management, e.g. ensuring proper service fulfilment according to agreements characterised by the time relationship between creation and deployment of a service
    • H04L41/5051—Service on demand, e.g. definition and deployment of services in real time
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W28/00—Network traffic management; Network resource management
    • H04W28/02—Traffic management, e.g. flow control or congestion control
    • H04W28/0215—Traffic management, e.g. flow control or congestion control based on user or device properties, e.g. MTC-capable devices

Definitions

  • the present disclosure relates to wireless communication, and more particularly, to a method and a network node for Quality of Service (QoS) notification.
  • QoS Quality of Service
  • the Network Exposure Function supports external exposure of capabilities of network functions.
  • the external exposure can be categorized as Monitoring capability, Provisioning capability, Policy/Charging capability and Analytics reporting capability.
  • the Monitoring capability is for monitoring of specific events for terminal devices (or referred to as User Equipments or UEs) in the 5 th Generation (5G) system and making such monitoring events information available for external exposure via the NEF.
  • the Provisioning capability is for allowing provision of information by external parties for use by UEs in the 5G system.
  • the Policy/Charging capability is for handling QoS and charging policy for UEs based on requests from external parties.
  • the Policy/Charging capability involves means that allow requesting for session and charging policy, enforcing QoS policy, and applying accounting functionality, and can be used for QoS/priority handling for sessions of UEs, and for setting applicable charging parties or charging rates.
  • the Analytics reporting capability is for allowing external parties to fetch or subscribe/unsubscribe to analytics information generated by the 5G system.
  • the NEF Application Programing Interface can allow an Application Function (AF) to set up an AF session with a requested QoS.
  • Fig. 1 shows a sequence flow for such procedure.
  • an AF sends a request to reserve resources for an AF session using Nnef_AFsessionWithQoS_Create request message (containing UE address, AF Identifier, Flow description (s) , QoS reference (or referred to as “requested QoS” or “required QoS” hereinafter) , and optionally Alternative Service Requirements (or referred to as “Alternative QoS requirements” hereinafter) ) to an NEF.
  • a period of time or a traffic volume for the requested QoS can be included in the AF request.
  • the NEF assigns a Transaction Reference ID to the Nnef_AFsessionWithQoS_Create request.
  • the NEF authorizes the AF request and may apply policies to control the overall amount of pre-defined QoS authorized for the AF. If the authorization is not granted, steps 1.3 and 1.4 are skipped and the NEF replies to the AF with a Result value indicating that the authorization failed.
  • the NEF interacts with a Policy Control Function (PCF) by triggering a Npcf_PolicyAuthorization_Create request and provides UE address, AF Identifier, Flow description (s) and the QoS reference including the optionally received period of time or traffic volume which is mapped to sponsored data connectivity information.
  • PCF Policy Control Function
  • the PCF derives the required QoS parameters based on the information provided by the NEF and determines whether this QoS is allowed (according to the PCF configuration for this AF) , and notifies the result to the NEF.
  • the PCF derives the Alternative QoS parameter set (s) from the one or more QoS reference parameters in the same prioritized order.
  • the PCF notifies the NEF whether the transmission resources corresponding to the QoS request are established or not.
  • the PCF determines whether the request is allowed and notifies the NEF if the request is not authorized. If the request is not authorized, the NEF responds to the AF in step 1.5 with a Result value indicating that the authorization failed.
  • the NEF sends a Nnef_AFsessionWithQoS_Create response message (containing Transaction Reference ID and Result) to the AF.
  • the Result indicates whether the request is granted or not.
  • the NEF shall send a Npcf_PolicyAuthorization_Subscribe message to the PCF to subscribe to notifications of Resource allocation status and may subscribe to other events.
  • the PCF sends a Npcf_PolicyAuthorization_Notify message to the NEF notifying about the event.
  • the NEF sends a Nnef_AFsessionWithQoS_Notify message with the event reported by the PCF to the AF.
  • the NEF when the AF includes alternative QoS requirements in the Nnef_AFsessionWithQoS_Create request at 1.1, the NEF will act as an internal AF to interact with the PCF, and in this case, the NEF shall also subscribe to notifications when the requested QoS can no longer (or can again) be fulfilled from the PCF, as described in Section 6.1.3.22 of TS 23.503, V16.3.0, and Section 5.6.2.15 of TS 29.514, V16.3.0, each of which is incorporated herein by reference in its entirety.
  • the requested QoS may be mapped to a bandwidth for a Service Data Flow (SDF) requiring a Guaranteed Bit Rate (GBR) .
  • SDF Service Data Flow
  • GRR Guaranteed Bit Rate
  • the PCF can report to the NEF (based on subscription) about the current situation of the QoS satisfaction and also a currently applied QoS reference.
  • SMF Session Management Function
  • a method in an NEF includes: receiving, from an AF, a request to create a session with a requested QoS.
  • the method further includes: subscribing to a first QoS notification from a PCF.
  • the method further includes: receiving, from the PCF, the first QoS notification indicating that the requested QoS is not guaranteed or the requested QoS is guaranteed.
  • the method further includes: transmitting, in response to receiving the first QoS notification, a second QoS notification indicating that the requested QoS is not guaranteed or the requested QoS is guaranteed to the AF.
  • the request may contain one or more alternative QoS requirements.
  • each of the first QoS notification and the second QoS notification when indicating that the requested QoS is not guaranteed, may further indicate one of the one or more alternative QoS requirements that can be guaranteed or is currently applied.
  • the method may further include: performing a mapping between a QoS reference used at the AF and a QoS reference used at the PCF.
  • the operation of mapping may include: mapping a QoS reference associated with the one alternative QoS requirement that can be guaranteed or is currently applied, as indicated in the first QoS notification, to a QoS reference associated with the one alternative QoS requirement that can be guaranteed or is currently applied in the second QoS notification.
  • the request may contain an indication that a QoS notification feature is supported at the AF.
  • the QoS notification feature may be an AlternativeQoS_5G feature.
  • the operations of subscribing and transmitting may be performed in response to determining that the request contains the indication.
  • a network node includes a processor and a memory.
  • the memory stores instructions enabling the network node to implement an NEF.
  • the network node is configured to, when implementing the NEF, perform the method according to the above first aspect.
  • a computer-readable storage medium has computer-readable instructions embodied therein.
  • the computer-readable instructions When executed by a processor of a network node, the computer-readable instructions configure the network node to perform the method according to the above first aspect.
  • a method in an AF includes: transmitting, to an NEF, a request to create a session with a requested QoS.
  • the method further includes: receiving, from the NEF, a QoS notification indicating that the requested QoS is not guaranteed or the requested QoS is guaranteed.
  • the method may further include: applying a rate adaptation to the session based on the QoS notification.
  • the method may further include: updating the requested QoS based on the QoS notification.
  • the request may contain one or more alternative QoS requirements.
  • the QoS notification when indicating that the requested QoS is not guaranteed, may further indicate one of the one or more alternative QoS requirements that can be guaranteed or is currently applied.
  • the method may further include: applying a rate adaptation to the session based on the one alternative QoS requirement that can be guaranteed or is currently applied.
  • the method may further include: updating the requested QoS based on the one alternative QoS requirement that can be guaranteed or is currently applied.
  • the request may contain an indication that a QoS notification feature is supported at the AF.
  • the QoS notification feature may be an AlternativeQoS_5G feature.
  • a network node includes a processor and a memory.
  • the memory stores instructions enabling the network node to implement an AF.
  • the network node is configured to, when implementing the AF, perform the method according to the above fourth aspect.
  • a computer-readable storage medium has computer-readable instructions embodied therein.
  • the computer-readable instructions When executed by a processor of a network node, the computer-readable instructions configure the network node to perform the method according to the above fourth aspect.
  • an NEF upon receiving a request to create a session with a requested QoS from an AF, an NEF can subscribe to a first QoS notification from a PCF, the first QoS notification indicating that the requested QoS is not guaranteed or the requested QoS is guaranteed.
  • the NEF can transmit a second QoS notification indicating that the requested QoS is not guaranteed or the requested QoS is guaranteed to the AF.
  • the NEF can notify the AF that the requested QoS is not guaranteed or the requested QoS is guaranteed.
  • the AF may apply a rate adaptation or update the requested QoS based on the notification.
  • Fig. 1 is sequence diagram showing a procedure for setting up an AF session with a requested QoS
  • Fig. 2 is a flowchart illustrating a method in an NEF according to an embodiment of the present disclosure
  • Fig. 3 is a flowchart illustrating a method in an AF according to another embodiment of the present disclosure
  • Fig. 4 is a block diagram of a network node for implementing an NEF according to an embodiment of the present disclosure
  • Fig. 5 is a block diagram of a network node for implementing an NEF according to another embodiment of the present disclosure
  • Fig. 6 is a block diagram of a network node for implementing an AF according to an embodiment of the present disclosure.
  • Fig. 7 is a block diagram of a network node for implementing an AF according to another embodiment of the present disclosure.
  • references in the specification to ′′one embodiment, ′′ ′′an embodiment, ′′ ′′an example embodiment, ′′ and the like indicate that the embodiment described may include a particular feature, structure, or characteristic, but it is not necessary that every embodiment includes the particular feature, structure, or characteristic. Moreover, such phrases are not necessarily referring to the same embodiment. Further, when a particular feature, structure, or characteristic is described in connection with an embodiment, it is submitted that it is within the knowledge of one skilled in the art to affect such feature, structure, or characteristic in connection with other embodiments whether or not explicitly described.
  • terminal device encompasses a device which is able to communicate with a network node, such as a base station, or with another wireless device by transmitting and/or receiving wireless signals.
  • a network node such as a base station
  • UE encompasses, but is not limited to: a mobile phone, a stationary or mobile wireless device for machine-to-machine communication, an integrated or embedded wireless card, an externally plugged in wireless card, etc.
  • a “network node” or a “network function” can be implemented in a physical node or a virtualized environment, e.g., a cloud environment.
  • Fig. 2 is a flowchart illustrating a method 200 in an NEF according to an embodiment of the present disclosure.
  • the NEF receives from an AF a request to create a session with a requested QoS.
  • the request may be a
  • Nnef_AFsessionWithQoS_Create request as described above in connection with step 1.1 in Fig. 1.
  • the request may contain one or more alternative QoS requirements, as described above in connection with step 1.1 in Fig. 1.
  • the NEF subscribes to a first QoS notification from a PCF.
  • the first QoS notification indicates that the requested QoS is not guaranteed (e.g., changed from being guaranteed to not being guaranteed) or the requested QoS is guaranteed (e.g., changed from not being guaranteed to being guaranteed) .
  • This subscription may use a Npcf_PolicyAuthorization_Subscribe message as described in step 1.6 in Fig. 1.
  • the first QoS notification may use e.g., a QOS_NOTIF event as specified in Section 5.6.3.9 of TS 29.514, which has two values “GUARANTEED” and “NOT_GUARANTEED” as defined in Table 5.6.3.9-1 of TS 29.514, as reproduced as Table 1 below:
  • Enumeration value Description Applicability GUARANTEED The QoS targets of one or more SDFs are guaranteed again. NOT_GUARANTEED The QoS targets of one or more SDFs are notbeing guaranteed.
  • the request received in the block 210 may contain one or more alternative QoS requirements.
  • the first QoS notification when indicating that the requested QoS is not guaranteed, may further indicate one of the one or more alternative QoS requirements that can be guaranteed or is currently applied.
  • the first QoS notification may use a data type “QosNotificationControllnfo” as specified in Section 5.6.2.15 of TS 29.514.
  • the first QoS notification is received from the PCF (e.g., in a Npcf_PolicyAuthorization_Notify message as described in step 1.7 in Fig. 1) .
  • the NEF transmits a second QoS notification indicating that the requested QoS is not guaranteed or the requested QoS is guaranteed to the AF.
  • a data type “UserPlaneNotificationData” and a data type “UserPlaneEventReport” can be defined, as shown in Table 2 and Table 3 below:
  • the “UserPlaneEvent” in Table 3 may have at least two values, “QOS_GUARANTEED” or “QOS_NOT_GUARANTEED” , as defined in Table 4 below:
  • the second QoS notification may also indicate the one alternative QoS requirement that can be guaranteed or is currently applied, e.g., referring to “appliedQosRef” in Table 3.
  • the second QoS notification transmitted in the block 230 can use a Nnef_AFsessionWithQoS_Notify message, as described in step 1.8 in Fig. 1, which can be enhanced to carry the UserPlaneEvent (e.g., “QOS_GUARANTEED” or “QOS_NOT_GUARANTEED” ) , and optionally “appliedQosRef” in case of “QOS_NOT_GUARANTEED” .
  • the UserPlaneEvent e.g., “QOS_GUARANTEED” or “QOS_NOT_GUARANTEED”
  • QoS references used at the AF may be the same as or different from those used at the PCF.
  • the NEF can perform mapping operations between the QoS references used at the AF and the QoS references used at the PCF. For example, the NEF can map a QoS reference associated with the one alternative QoS requirement that can be guaranteed or is currently applied, as indicated in the first QoS notification, to a QoS reference associated with the one alternative QoS requirement that can be guaranteed or is currently applied in the second QoS notification.
  • the request received in the block 210 may contain an indication that a QoS notification feature is supported at the AF.
  • the operations of subscribing in the block 220 and transmitting in the block 240 may be performed in response to determining that the request contains the indication.
  • the feature can be e.g., “AlternativeQoS_5G” as shown in Table 4, indicating the support of alternative QoS requirements and/or QoS notification (i.e., “QOS_GUARANTEED” or “QOS_NOT_GUARANTEED” ) .
  • Fig. 3 is a flowchart illustrating a method 300 in an AF according to an embodiment of the present disclosure.
  • the AF transmits, to an NEF, a request to create a session with a requested QoS.
  • the request here corresponds to the request as described above in connection with the block 210 in Fig. 1, and details thereof will thus be omitted here.
  • the AF receives, from the NEF, a QoS notification indicating that the requested QoS is not guaranteed (e.g., changed from being guaranteed to not being guaranteed) or the requested QoS is guaranteed (e.g., changed from not being guaranteed to being guaranteed) .
  • the QoS notification here corresponds to the second QoS notification as described above in connection with the block 240 in Fig. 1, and details thereof will thus be omitted here.
  • the AF can apply a rate adaptation to the session based on the QoS notification.
  • the AF can update the requested QoS based on the QoS notification.
  • the requested QoS may be a bandwidth of 50Mbps (Million bits per second) for a video streaming service.
  • the AF can apply a rate adaptation at an application level, e.g., to reduce a resolution or frame rate for the video streaming service (e.g., from 4K to 720p) , or can reduce the requested QoS (e.g., to a bandwidth of 30Mbps) by updating the QoS reference associated with the requested QoS using Hyper Text Transfer Protocol (HTTP) PUT or PATCH as specified in Section 4.4.13 of TS 29.122, V16.4.0.
  • HTTP Hyper Text Transfer Protocol
  • the request transmitted in the block 310 contains one or more alternative QoS requirements.
  • the QoS notification when indicating that the requested QoS is not guaranteed, may further indicate one of the one or more alternative QoS requirements that can be guaranteed or is currently applied.
  • the AF may apply a rate adaptation to the session or update the requested QoS based on the one alternative QoS requirement that can be guaranteed or is currently applied.
  • the requested QoS may be a bandwidth of 50Mbps for a video streaming service.
  • the AF can apply a rate adaptation at an application level based on the bandwidth of 30Mbps, e.g., to reduce a resolution or frame rate for the video streaming service (e.g., from 4K to 720p) , or can reduce the requested QoS (e.g., to a bandwidth of 30Mbps) by updating the QoS reference associated with the requested QoS using Hyper Text Transfer Protocol (HTTP) PUT or PATCH as specified in Section 4.4.13 of TS 29.122.
  • HTTP Hyper Text Transfer Protocol
  • the request transmitted in the block 310 may contain an indication that a QoS notification feature is supported at the AF.
  • the feature can be e.g., “AlternativeQoS_5G” as shown in Table 4, indicating the support of alternative QoS requirements and/or QoS notification (i.e., “QOS_GUARANTEED” or “QOS_NOT_GUARANTEED” ) .
  • Fig. 4 is a block diagram of a network node 400 for implementing an NEF according to an embodiment of the present disclosure.
  • the network node 400 can be operative to, when implementing an NEF, perform the method 200 as shown in Fig. 2.
  • the network node 400 includes a receiving unit 410 configured to receive, from an AF, a request to create a session with a requested QoS.
  • the network node 400 further includes a subscribing unit 420 configured to subscribe to a first QoS notification from a PCF.
  • the receiving unit 410 is further configured to receive, from the PCF, the first QoS notification indicating that the requested QoS is not guaranteed or the requested QoS is guaranteed.
  • the network node 400 further includes a transmitting unit 430 configured to transmit, in response to receiving the first QoS notification, a second QoS notification indicating that the requested QoS is not guaranteed or the requested QoS is guaranteed to the AF.
  • the request may contain one or more alternative QoS requirements.
  • each of the first QoS notification and the second QoS notification when indicating that the requested QoS is not guaranteed, may further indicate one of the one or more alternative QoS requirements that can be guaranteed or is currently applied.
  • the network node 400 may further include a mapping unit configured to perform a mapping between a QoS reference used at the AF and a QoS reference used at the PCF.
  • mapping may include: mapping a QoS reference associated with the one alternative QoS requirement that can be guaranteed or is currently applied, as indicated in the first QoS notification, to a QoS reference associated with the one alternative QoS requirement that can be guaranteed or is currently applied in the second QoS notification.
  • the request may contain an indication that a QoS notification feature is supported at the AF.
  • the QoS notification feature may be an AlternativeQoS_5G feature.
  • the operation performed by the subscribing unit 420 and the operation performed by the transmitting unit 430 may be performed in response to determining that the request contains the indication.
  • the units 410, 420, and 430 can be implemented as a pure hardware solution or as a combination of software and hardware, e.g., by one or more of: a processor or a micro-processor and adequate software and memory for storing of the software, a Programmable Logic Device (PLD) or other electronic component (s) or processing circuitry configured to perform the actions described above, and illustrated, e.g., in Fig. 2.
  • a processor or a micro-processor and adequate software and memory for storing of the software e.g., a Programmable Logic Device (PLD) or other electronic component (s) or processing circuitry configured to perform the actions described above, and illustrated, e.g., in Fig. 2.
  • PLD Programmable Logic Device
  • Fig. 5 is a block diagram of a network node 500 for implementing an NEF according to another embodiment of the present disclosure.
  • the network node 500 includes a processor 510 and a memory 520.
  • the memory 520 may contain instructions executable by the processor 510 whereby the network node 500 is operative to, when implementing the NEF, perform the actions, e.g., of the procedure described earlier in conjunction with Fig. 2.
  • the memory 520 contains instructions executable by the processor 510 whereby the network node 500 is operative to, when implementing the NEF: receive, from an AF, a request to create a session with a requested QoS; subscribe to a first QoS notification from a PCF; receive, from the PCF, the first QoS notification indicating that the requested QoS is not guaranteed or the requested QoS is guaranteed; and transmit, in response to receiving the first QoS notification, a second QoS notification indicating that the requested QoS is not guaranteed or the requested QoS is guaranteed to the AF.
  • the request may contain one or more alternative QoS requirements.
  • each of the first QoS notification and the second QoS notification when indicating that the requested QoS is not guaranteed, may further indicate one of the one or more alternative QoS requirements that can be guaranteed or is currently applied.
  • the memory 520 may further contain instructions executable by the processor 510 whereby the network node 500 is operative to, when implementing the NEF: perform a mapping between a QoS reference used at the AF and a QoS reference used at the PCF.
  • mapping may include: mapping a QoS reference associated with the one alternative QoS requirement that can be guaranteed or is currently applied, as indicated in the first QoS notification, to a QoS reference associated with the one alternative QoS requirement that can be guaranteed or is currently applied in the second QoS notification.
  • the request may contain an indication that a QoS notification feature is supported at the AF.
  • the QoS notification feature may be an AlternativeQoS_5G feature.
  • the operations of subscribing and transmitting may be performed in response to determining that the request contains the indication.
  • Fig. 6 is a block diagram of a network node 600 for implementing an AF according to an embodiment of the present disclosure.
  • the network node 600 can be operative to, when implementing an AF, perform the method 300 as shown in Fig. 3.
  • the network node 600 includes a transmitting unit 610 configured to transmit, to an NEF, a request to create a session with a requested QoS.
  • the network node 600 further includes a receiving unit 620 configured to receive, from the NEF, a QoS notification indicating that the requested QoS is not guaranteed or the requested QoS is guaranteed.
  • the network node 600 may further include a rate adaptation unit configured to apply a rate adaptation to the session based on the QoS notification.
  • the network node 600 may further include an updating unit configured to update the requested QoS based on the QoS notification.
  • the request may contain one or more alternative QoS requirements.
  • the QoS notification when indicating that the requested QoS is not guaranteed, may further indicate one of the one or more alternative QoS requirements that can be guaranteed or is currently applied.
  • the network node 600 may further include a rate adaptation unit configured to apply a rate adaptation to the session based on the one alternative QoS requirement that can be guaranteed or is currently applied.
  • the network node 600 may further include an updating unit configured to update the requested QoS based on the one alternative QoS requirement that can be guaranteed or is currently applied.
  • the request may contain an indication that a QoS notification feature is supported at the AF.
  • the QoS notification feature may be an AlternativeQoS_5G feature.
  • the units 610 and 620 can be implemented as a pure hardware solution or as a combination of software and hardware, e.g., by one or more of: a processor or a micro-processor and adequate software and memory for storing of the software, a Programmable Logic Device (PLD) or other electronic component (s) or processing circuitry configured to perform the actions described above, and illustrated, e.g., in Fig. 3.
  • a processor or a micro-processor and adequate software and memory for storing of the software e.g., a Programmable Logic Device (PLD) or other electronic component (s) or processing circuitry configured to perform the actions described above, and illustrated, e.g., in Fig. 3.
  • PLD Programmable Logic Device
  • Fig. 7 is a block diagram of a network node 700 for implementing an AF according to another embodiment of the present disclosure.
  • the network node 700 includes a processor 710 and a memory 720.
  • the memory 720 may contain instructions executable by the processor 710 whereby the network node 700 is operative to, when implementing the AF, perform the actions, e.g., of the procedure described earlier in conjunction with Fig. 3.
  • the memory 720 contains instructions executable by the processor 710 whereby the network node 700 is operative to, when implementing the AF: transmit, to an NEF, a request to create a session with a requested QoS; and receive, from the NEF, a QoS notification indicating that the requested QoS is not guaranteed or the requested QoS is guaranteed.
  • the memory 720 may further contain instructions executable by the processor 710 whereby the network node 700 is operative to, when implementing the AF: apply a rate adaptation to the session based on the QoS notification.
  • the memory 720 may further contain instructions executable by the processor 710 whereby the network node 700 is operative to, when implementing the AF: update the requested QoS based on the QoS notification.
  • the request may contain one or more alternative QoS requirements.
  • the QoS notification when indicating that the requested QoS is not guaranteed, may further indicate one of the one or more alternative QoS requirements that can be guaranteed or is currently applied.
  • the memory 720 may further contain instructions executable by the processor 710 whereby the network node 700 is operative to, when implementing the AF: apply a rate adaptation to the session based on the one alternative QoS requirement that can be guaranteed or is currently applied.
  • the memory 720 may further contain instructions executable by the processor 710 whereby the network node 700 is operative to, when implementing the AF: update the requested QoS based on the one alternative QoS requirement that can be guaranteed or is currently applied.
  • the request may contain an indication that a QoS notification feature is supported at the AF.
  • the QoS notification feature may be an AlternativeQoS_5G feature.
  • the present disclosure also provides at least one computer program product in the form of a non-volatile or volatile memory, e.g., a non-transitory computer readable storage medium, an Electrically Erasable Programmable Read-Only Memory (EEPROM) , a flash memory and a hard drive.
  • the computer program product includes a computer program.
  • the computer program includes: code/computer readable instructions, which when executed by the processor 510 causes the network node 500 to perform the actions, e.g., of the procedure described earlier in conjunction with Fig. 2, or code/computer readable instructions, which when executed by the processor 710 causes the network node 700 to perform the actions, e.g., of the procedure described earlier in conjunction with Fig. 3.
  • the computer program product may be configured as a computer program code structured in computer program modules.
  • the computer program modules could essentially perform the actions of the flow illustrated in Fig. 2 or 3.
  • the processor may be a single CPU (Central Processing Unit) , but could also comprise two or more processing units.
  • the processor may include general purpose microprocessors; instruction set processors and/or related chips sets and/or special purpose microprocessors such as Application Specific Integrated Circuits (ASICs) .
  • the processor may also comprise board memory for caching purposes.
  • the computer program may be carried by a computer program product connected to the processor.
  • the computer program product may comprise a non-transitory computer readable storage medium on which the computer program is stored.
  • the computer program product may be a flash memory, a Random Access Memory (RAM) , a Read-Only Memory (ROM) , or an EEPROM, and the computer program modules described above could in alternative embodiments be distributed on different computer program products in the form of memories.
  • RAM Random Access Memory
  • ROM Read-Only Memory
  • EEPROM Electrically Erasable programmable read-only memory

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Quality & Reliability (AREA)
  • Data Exchanges In Wide-Area Networks (AREA)
  • Computer And Data Communications (AREA)
  • Mobile Radio Communication Systems (AREA)
  • Telephonic Communication Services (AREA)
PCT/CN2020/141702 2020-02-14 2020-12-30 METHOD AND NETWORK NODE FOR QoS NOTIFICATION WO2021159884A1 (en)

Priority Applications (8)

Application Number Priority Date Filing Date Title
EP20918461.3A EP4104507A4 (en) 2020-02-14 2020-12-30 METHOD AND NETWORK NODE FOR QOS NOTIFICATION
JP2022547774A JP7408824B2 (ja) 2020-02-14 2020-12-30 ＱｏＳ通知のための方法及びネットワークノード
KR1020227029402A KR20220133250A (ko) 2020-02-14 2020-12-30 QoS 통지를 위한 방법 및 네트워크 노드
CN202080096242.9A CN115299097A (zh) 2020-02-14 2020-12-30 用于qos通知的方法和网络节点
CN202310365322.5A CN116455771A (zh) 2020-02-14 2020-12-30 用于QoS通知的方法和网络节点
US17/799,151 US20230081774A1 (en) 2020-02-14 2020-12-30 Method and Network Node for QoS Notification
TW110102632A TW202137796A (zh) 2020-02-14 2021-01-25 用於服務品質通知的方法和網路節點
CONC2022/0011769A CO2022011769A2 (es) 2020-02-14 2022-08-19 Método y nodo de red para la notificación de la qos

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN2020075383 2020-02-14
CNPCT/CN2020/075383 2020-02-14

Publications (2)

Publication Number Publication Date
WO2021159884A1 true WO2021159884A1 (en) 2021-08-19
WO2021159884A8 WO2021159884A8 (en) 2022-08-18

Family

ID=77291665

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2020/141702 WO2021159884A1 (en) 2020-02-14 2020-12-30 METHOD AND NETWORK NODE FOR QoS NOTIFICATION

Country Status (8)

Country Link
US (1) US20230081774A1 (ja)
EP (1) EP4104507A4 (ja)
JP (1) JP7408824B2 (ja)
KR (1) KR20220133250A (ja)
CN (2) CN116455771A (ja)
CO (1) CO2022011769A2 (ja)
TW (1) TW202137796A (ja)
WO (1) WO2021159884A1 (ja)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2024044995A1 (en) * 2022-08-30 2024-03-07 Huawei Technologies Co., Ltd. Enhanced alternative quality-of-service profile handling for an application function session

Citations (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2019228214A1 (zh) * 2018-05-31 2019-12-05 华为技术有限公司 一种无线承载建立、业务流的监测方法及装置

Patent Citations (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2019228214A1 (zh) * 2018-05-31 2019-12-05 华为技术有限公司 一种无线承载建立、业务流的监测方法及装置

Non-Patent Citations (7)

* Cited by examiner, † Cited by third party
Title
"3rd Generation Partnership Project; Technical Specification Group Core Network and Terminals; 5G System; Policy Authorization Service; Stage 3 (Release 16)", 3GPP STANDARD; TECHNICAL SPECIFICATION; 3GPP TS 29.514, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE, vol. CT WG3, no. V16.3.0, 23 December 2019 (2019-12-23), Mobile Competence Centre ; 650, route des Lucioles ; F-06921 Sophia-Antipolis Cedex ; France, pages 1 - 143, XP051840978 *
"3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; Policy and charging control framework for the 5G System (5GS); Stage 2 (Release 16)", 3GPP STANDARD; TECHNICAL SPECIFICATION; 3GPP TS 23.503, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE, vol. SA WG2, no. V16.3.0, 22 December 2019 (2019-12-22), Mobile Competence Centre ; 650, route des Lucioles ; F-06921 Sophia-Antipolis Cedex ; France, pages 1 - 112, XP051840934 *
ANONYMOUS: "3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; Procedures for the 5G System (5GS); Stage 2 (Release 16)", 3GPP STANDARD; TECHNICAL SPECIFICATION; 3GPP TS 23.502, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE, vol. SA WG2, no. V16.3.0, 22 December 2019 (2019-12-22), Mobile Competence Centre ; 650, route des Lucioles ; F-06921 Sophia-Antipolis Cedex ; France, pages 1 - 558, XP051840932 *
SAMSUNG: "Revoke Alternative Service Requirement request", 3GPP DRAFT; S2-1911616, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE, vol. SA WG2, no. Reno, Nevada, USA; 20191118 - 20191122, 8 November 2019 (2019-11-08), Mobile Competence Centre ; 650, route des Lucioles ; F-06921 Sophia-Antipolis Cedex ; France, XP051821696 *
SAMSUNG: "Revoke Alternative Service Requirement request", 3GPP DRAFT; S2-1911986, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE, vol. SA WG2, no. Reno, Nevada, USA; 20191118 - 20191122, 21 November 2019 (2019-11-21), Mobile Competence Centre ; 650, route des Lucioles ; F-06921 Sophia-Antipolis Cedex ; France, XP051827232 *
SAMSUNG: "Revoke Alternative Service Requirement request", 3GPP DRAFT; S2-1912007, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE, vol. SA WG2, no. Reno, Nevada, USA; 20191118 - 20191122, 22 November 2019 (2019-11-22), Mobile Competence Centre ; 650, route des Lucioles ; F-06921 Sophia-Antipolis Cedex ; France, XP051828210 *
See also references of EP4104507A4 *

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2024044995A1 (en) * 2022-08-30 2024-03-07 Huawei Technologies Co., Ltd. Enhanced alternative quality-of-service profile handling for an application function session

Also Published As

Publication number Publication date
EP4104507A4 (en) 2024-02-28
JP7408824B2 (ja) 2024-01-05
US20230081774A1 (en) 2023-03-16
CO2022011769A2 (es) 2022-08-30
EP4104507A1 (en) 2022-12-21
JP2023514142A (ja) 2023-04-05
KR20220133250A (ko) 2022-10-04
WO2021159884A8 (en) 2022-08-18
TW202137796A (zh) 2021-10-01
CN115299097A (zh) 2022-11-04
CN116455771A (zh) 2023-07-18

Similar Documents

Publication Publication Date Title
US11317451B2 (en) Session activation method, device, and system
US11075841B2 (en) Network congestion control method, device, and system
US11089520B2 (en) Session migration method and device
CA3112926A1 (en) Slice information processing method and apparatus
CN110351828B (zh) 一种定位方法及装置
US20200015117A1 (en) Ambr determining method and communications entity
US11057309B2 (en) Management method, management unit, and system
US10848366B2 (en) Network function management method, management unit, and system
US20140136709A1 (en) System and Method for Resource Management in a Wireless Network
US20220405153A1 (en) Report application programming interface (api) capability change based on api filter
CN108011899B (zh) 一种会话建立优化方法、装置和系统
US11044729B2 (en) Function scheduling method, device, and system
US11082893B2 (en) Session migration method and device applied to a UE tracking area update
CN108141796A (zh) 协作ran和传输网络利用
CN106792923B (zh) 一种配置QoS策略的方法及装置
WO2021159884A1 (en) METHOD AND NETWORK NODE FOR QoS NOTIFICATION
WO2021227600A1 (zh) 一种网络切片控制方法及通信装置
AU2021253086B2 (en) Alternative charging handling based on QoS
WO2023279977A1 (en) Network nodes and methods therein for event monitoring
US20240214845A1 (en) Network Nodes and Methods Therein for Event Monitoring
WO2024027484A1 (en) Method and apparatus for service management
US20220353340A1 (en) Communication Method and Communication Apparatus
JP2024522518A (ja) ネットワークノードおよびその中のイベント監視方法
CN115413063A (zh) 建立连接的方法、装置和系统

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 20918461

Country of ref document: EP

Kind code of ref document: A1

DPE1 Request for preliminary examination filed after expiration of 19th month from priority date (pct application filed from 20040101)
ENP Entry into the national phase

Ref document number: 2022547774

Country of ref document: JP

Kind code of ref document: A

ENP Entry into the national phase

Ref document number: 20227029402

Country of ref document: KR

Kind code of ref document: A

NENP Non-entry into the national phase

Ref country code: DE

ENP Entry into the national phase

Ref document number: 2020918461

Country of ref document: EP

Effective date: 20220914