WO2024000445A1 - Procédé et appareil de commande de flux de qualité de service, et support de stockage informatique - Google Patents

Procédé et appareil de commande de flux de qualité de service, et support de stockage informatique Download PDF

Info

Publication number
WO2024000445A1
WO2024000445A1 PCT/CN2022/102934 CN2022102934W WO2024000445A1 WO 2024000445 A1 WO2024000445 A1 WO 2024000445A1 CN 2022102934 W CN2022102934 W CN 2022102934W WO 2024000445 A1 WO2024000445 A1 WO 2024000445A1
Authority
WO
WIPO (PCT)
Prior art keywords
status information
entity
terminal
core network
terminal status
Prior art date
Application number
PCT/CN2022/102934
Other languages
English (en)
Chinese (zh)
Inventor
吴锦花
沈洋
王德乾
刘建宁
毛玉欣
Original Assignee
北京小米移动软件有限公司
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 北京小米移动软件有限公司 filed Critical 北京小米移动软件有限公司
Priority to CN202280002504.XA priority Critical patent/CN117643100A/zh
Priority to PCT/CN2022/102934 priority patent/WO2024000445A1/fr
Publication of WO2024000445A1 publication Critical patent/WO2024000445A1/fr

Links

Images

Classifications

    • 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]

Definitions

  • the present disclosure relates to the field of wireless communication technology, and in particular, to a QoS flow control method, device and computer storage medium.
  • XR and media services have the characteristics of high throughput, low latency, and high reliability requirements, they require high power consumption on the terminal side, and the battery power of the terminal may affect the user experience.
  • the present disclosure provides a QoS flow control method, device and computer storage medium to match business traffic characteristics and terminal energy consumption management, thereby ensuring business requirements and user experience.
  • a quality of service (QoS) flow control method is provided, which can be applied to the first core network functional entity in the communication system, such as policy control function (PCF) entity.
  • the method may include: the first core network functional entity receives terminal status information (UE status information) from an application function (AF) entity, and the terminal status information is used to represent the power consumption status of the terminal; the first core network functional entity Perform one of the following: perform QoS update on the QoS flow associated with the terminal according to the terminal status information; send the terminal status information to the second core network functional entity, and the terminal status information is used by the second core network functional entity to perform QoS update on the QoS flow.
  • UE status information terminal status information
  • AF application function
  • AF application function
  • the terminal status information is used to represent the power consumption status of the terminal
  • the first core network functional entity Perform one of the following: perform QoS update on the QoS flow associated with the terminal according to the terminal status information; send the terminal status information to the second core network functional entity, and
  • the first core network functional entity may be a PCF entity (can also be described as a first PCF entity), and the second core network functional entity may be other PCF entities (can also be described as a second PCF entity).
  • the second PCF entity can be understood as one or more PCF entities.
  • the QoS flow includes at least one of the following: session QoS flow; service data flow QoS flow.
  • the terminal status information includes at least one of the following: battery power; battery life; power supply mode; CPU load; and terminal overheating status.
  • the QoS flow is a guaranteed bit rate (guaranteed bit rate, GBR) QoS flow
  • the QoS parameters of the QoS flow include: guaranteed flow bit rate (guaranteed flow bit rate, GFBR) and/or maximum flow bit rate (maximum flow bit rate, MFBR).
  • the first core network functional entity performs QoS updates on the QoS flow based on the terminal status information, including: the first core network functional entity lowers or increases the GFBR based on the terminal status information.
  • the above method also includes: the first core network functional entity sends MFBR to the third core network functional entity, and the MFBR is used by the third core network functional entity to perform QoS update on the downlink GBR QoS flow; and/or , the first core network functional entity sends the MFBR to the access network functional entity, and the MFBR is used by the access network functional entity to perform QoS updates on the uplink and/or downlink GBR QoS flows.
  • the third core network function entity may be a user plan function (UPF) entity.
  • UPF user plan function
  • the QoS flow is a non-GBR QoS flow
  • the QoS parameters of the QoS flow include: aggregate maximum bit rate (aggregate maximum bit rate, AMBR).
  • the first core network functional entity performs QoS updates on the QoS flow based on the terminal status information, including: the first core network functional entity reduces or increases AMBR based on the terminal status information.
  • AMBR includes at least one of the following: AMBR per terminal, AMBR per session.
  • the above method further includes: the first core network functional entity sends the per-session AMBR to the third core network functional entity, and the per-session AMBR is used for the third core network functional entity.
  • the core network functional entity performs QoS updates on the uplink and/or downlink session QoS flows; or, the first core network functional entity sends the AMBR of each session to the terminal, and the AMBR of each session is used by the terminal to perform protocol data based on the non-GBR QoS flow.
  • PDU protocol data unit
  • the above method in response to the AMBR including the AMBR of each terminal, the above method further includes: the first core network functional entity sends the AMBR of each terminal to the access network functional entity, and the AMBR of each terminal is used for the access network function.
  • the entity performs QoS updates for each terminal's upstream and/or downstream non-GBR QoS flows.
  • the QoS flow is a GBR QoS flow or a non-GBR QoS flow
  • the QoS parameters of the QoS flow include: maximum bit rate (maximum bit rate, MBR) per slice per terminal.
  • the application function entity is a trusted application function entity; the first core network function entity receives terminal status information from the application function entity, including one of the following: the first core network function entity receives the terminal status information sent by the application function entity The terminal status information; the first core network functional entity receives the terminal status information sent by the time sensitive communication and time synchronization function (TSCTSF) entity, and the terminal status information is sent by the application function entity to the TSCTSF entity.
  • TSCTSF time sensitive communication and time synchronization function
  • the application function entity is an untrusted application function entity; the first core network function entity receives terminal status information from the application function entity, including one of the following: the first core network function entity receives the network opening function The terminal status information sent by the (network exposure function, NEF) entity, the terminal status information is sent to the NEF entity by the application function entity; the first core network function entity receives the terminal status information sent by the TSCTSF entity, the terminal status information is sent by the application function entity Sent to the TSCTSF entity through the NEF entity.
  • NEF network exposure function
  • the first core network functional entity sends the terminal status information to the second core network functional entity, including: the first core network functional entity queries the subscription event and determines the first event associated with the terminal status information; When an event satisfies event reporting conditions, the first core network functional entity sends terminal status information to the second core network functional entity.
  • a QoS flow control method which method can be applied to an application function entity in a communication system.
  • the method includes: an application function entity receives terminal status information sent by a terminal, and the terminal status information is used to represent the power consumption status of the terminal; the application function entity sends terminal status information to a first core network functional entity, and the terminal status information is also used for the first
  • the core network functional entity performs QoS updates on the QoS flows associated with the terminal.
  • the QoS flow includes at least one of the following: QoS flow of the session; QoS flow of the service data flow.
  • the application function entity is a trusted application function entity; the application function entity sends terminal status information to the first core network function entity, including one of the following: the application function entity sends terminal status information to the first core network function entity Status information: the application function entity sends terminal status information to the TSCTSF entity, and the terminal status information is also used by the TSCTSF entity to send to the first core network function entity.
  • the application function entity is an untrusted application function entity; the application function entity sends terminal status information to the first core network function entity, including: terminal status information sent by the application function entity to the NEF entity, terminal status The information is also used by the NEF entity to send to the first core network functional entity, or the terminal status information is also used by the NEF entity to send to the first core network functional entity through the TSCTSF entity.
  • a QoS flow control device may be the first core network functional entity in the communication system or the chip or system-on-chip of the first core network functional entity. It may also be the first core network functional entity.
  • the functional modules in the network functional entity are used to implement the methods described in the above embodiments.
  • the control device can realize the functions performed by the first core network functional entity in the above embodiments, and these functions can be realized by hardware executing corresponding software. These hardware or software include one or more modules corresponding to the above functions.
  • the device may include: a receiving module configured to receive terminal status information (UE status information) from the application function entity, where the terminal status information is used to represent the power consumption status of the terminal; a processing module configured to, based on the terminal status information, The QoS flow associated with the terminal performs QoS update; the sending module is configured to send terminal status information to the second core network functional entity, and the terminal status information is used by the second core network functional entity to perform QoS update on the QoS flow.
  • UE status information terminal status information
  • the QoS flow associated with the terminal performs QoS update
  • the sending module is configured to send terminal status information to the second core network functional entity, and the terminal status information is used by the second core network functional entity to perform QoS update on the QoS flow.
  • the first core network functional entity may be a PCF entity
  • the second core network functional entity may be other PCF entities.
  • the QoS flow includes at least one of the following: session QoS flow; service data flow QoS flow.
  • the terminal status information includes at least one of the following: battery power; battery life; power supply mode; CPU load; and terminal overheating status.
  • the QoS flow is a GBR QoS flow
  • the QoS parameters of the QoS flow include: GFBR and/or MFBR.
  • the processing module is configured to reduce or increase the GFBR according to the terminal status information.
  • the sending module is configured to send the MFBR to the third core network functional entity.
  • the MFBR is used by the third core network functional entity to perform QoS updates on the downlink GBR QoS flow; and/or to the access network function.
  • the entity sends MFBR, which is used by the access network functional entity to perform QoS updates on the uplink and/or downlink GBR QoS flows.
  • the third core network functional entity may be a UPF entity.
  • the processing module is configured to reduce or increase the AMBR according to the terminal status information.
  • AMBR includes at least one of the following: AMBR per terminal, AMBR per session.
  • the sending module in response to the AMBR including a per-session AMBR, is configured to send the per-session AMBR to the third core network functional entity, and the per-session AMBR is used for the third core network functional entity pair Perform QoS updates for upstream and/or downlink session QoS flows; or, send per-session AMBR to the terminal, and the per-session AMBR is used by the terminal to perform PDU session-based upstream rate limiting on non-GBR QoS flows.
  • the QoS flow is a GBR QoS flow or a non-GBR QoS flow
  • the QoS parameters of the QoS flow include: MBR per terminal per slice.
  • the sending module in response to the QoS parameter including the MBR per terminal per slice, is configured to send the MBR per terminal per slice to the access network functional entity, and the MBR per terminal per slice is used for access.
  • the network function entity performs QoS updates on the PDU session QoS flow corresponding to the terminal's single network slice selection auxiliary information S-NSSAI.
  • the application function entity is a trusted application function entity; the receiving module is configured to perform one of the following: receiving terminal status information sent by the application function entity; receiving terminal status information sent by the TSCTSF entity, terminal status The information is sent by the application function entity to the TSCTSF entity.
  • the processing module is configured to query the subscription event and determine the first event associated with the terminal status information; the sending module is configured to send the message to the second core when the first event satisfies the event reporting condition.
  • the network function entity sends terminal status information.
  • a QoS flow control device can be an application function entity in a communication system or a chip or system-on-chip of an application function entity. It can also be an application function entity used to implement each of the above. Functional module of the method described in the embodiment.
  • the control device can realize the functions performed by the application function entities in the above embodiments, and these functions can be realized by hardware executing corresponding software. These hardware or software include one or more modules corresponding to the above functions.
  • the control device may include: a receiving module configured to receive terminal status information sent by the terminal, where the terminal status information is used to represent the power consumption status of the terminal; a sending module configured to send the terminal status information to the first core network functional entity, The terminal status information is also used by the first core network functional entity to perform QoS update on the QoS flow associated with the terminal.
  • the QoS flow includes at least one of the following: QoS flow of the session; QoS flow of the service data flow.
  • the application function entity is a trusted application function entity; the sending module is configured to perform one of the following: sending terminal status information to the first core network functional entity; sending terminal status information to the TSCTSF entity. The status information is also used by the TSCTSF entity to send to the first core network functional entity.
  • the application function entity is an untrusted application function entity; the sending module is configured to send terminal status information to the NEF entity, and the terminal status information is also used by the NEF entity to send to the first core network function entity , or, the terminal status information is also used by the NEF entity to send to the first core network function entity through the TSCTSF entity.
  • Figure 3 is a schematic flowchart of an implementation process for performing QoS updates on GBR QoS flows in an embodiment of the present disclosure
  • Figure 4 is a schematic flowchart of an implementation process for performing QoS updates on non-GBR QoS flows in an embodiment of the present disclosure
  • Figure 6 is a schematic structural diagram of a QoS flow control device in an embodiment of the present disclosure.
  • Figure 8 is a schematic structural diagram of a network functional entity in an embodiment of the present disclosure.
  • first, second, third, etc. may be used to describe various information in the embodiments of the present disclosure, the information should not be limited to these terms. These terms are only used to distinguish information of the same type from each other. For example, without departing from the scope of the embodiments of the present disclosure, “first information” may also be called “second information”, and similarly, “second information” may also be called “first information”. Depending on the context, the word “if” as used herein may be interpreted as “when” or “when” or “in response to determining.”
  • the technical solution of the embodiment of the present disclosure relates to the architecture of a communication system.
  • the communication system may be a 5G communication system or a future evolution communication system.
  • access network functional entities which can also be described as access network functional entities, access network elements, access network functional components, access network functional modules, etc.
  • core Network function (NF) entity can also be described as core network equipment, core network element, core network functional component, core network functional module, etc.
  • At least one core network functional entity is located in the core network (ie 5GC).
  • the terminal is used to report terminal status information (UE status information) used to indicate its own power consumption status to the first core network side; at least one core network functional entity has at least the following functions: according to the received terminal status information, the terminal associated The QoS flow performs QoS update; and, the terminal status information is sent to the next-level core network functional entity for the second core network functional entity to perform QoS update on the QoS flow.
  • the above QoS flow is the QoS flow of the first service of the terminal.
  • the first service may include XR service, mobile media service, etc., wherein XR service and mobile media service may also be called XRM service, or may be described as XR ⁇ M service.
  • FIG. 1 is an architectural schematic diagram of a 5G communication system in an embodiment of the present disclosure.
  • the above-mentioned 5G communication system 100 may include a 5G Radio Access Network (RAN) and a 5G Core Network (5GC).
  • the 5G wireless access network may include next generation radio access network (NG RAN).
  • NG RAN 101 communicates with the terminal (or terminal device) 102 through the Uu interface.
  • the 5G core network may include: at least one core network functional entity mentioned above, such as access and mobility management function (AMF) entity 1031, SMF entity 1032, PCF entity 1033, UPF entity 1034, AF entity 1035, NEF entity 1036, TSCTSF entity 1037, etc.
  • AMF access and mobility management function
  • the above communication system may also include other network functional entities (which may also be called network elements, network devices, etc.), which are not specifically limited in the embodiment of the present disclosure.
  • both the third-party (3rd) AF entity and the operator (operator) AF entity belong to AF entities.
  • third-party AF entities such as instant messaging service servers, electronic payment service servers, etc.
  • operator AF entities such as the agent-call session control function in the IP multimedia system) proxy-call session control function, P-CSCF) entity
  • third-party AF entities need to pass NEF entities when interacting with PCF entities.
  • the above operator AF entity can also be described as a trusted or trusted AF entity, and the above third party AF can also be described as an untrusted or untrusted AF entity.
  • PCF PCF
  • SMF SMF
  • Other entities are similar and will not be listed one by one.
  • N2 The interface between AMF 1031 and NG RAN 101, used to transmit wireless bearer control information from the core network side to NG RAN 101, etc.
  • N1 The interface between AMF 1031 and terminal 102, has nothing to do with access, and is used to transmit QoS control rules to terminal 102, etc.
  • the communication between any two entities can use service-oriented communication.
  • the interfaces Nnef and Npcf used for communication between NEF and PCF are both service-oriented interfaces.
  • the interfaces Naf, Ntsctsf, Namf and Nsmf are all service-oriented interfaces.
  • the above-mentioned terminal may be a terminal device with a wireless communication function and a wireless sensing function, and may also be called user equipment (UE).
  • Terminals can be deployed on land, including indoors or outdoors, handheld, wearable or vehicle-mounted; they can also be deployed on water (such as ships, etc.); they can also be deployed in the air (such as aircraft, balloons, satellites, etc.).
  • the terminal can be a mobile phone, a tablet computer, a computer with wireless transceiver functions, a virtual reality (VR) terminal device, an augmented reality (AR) terminal device, or an industrial control (industrial control) ), wireless terminals in self-driving, wireless terminals in remote medical, wireless terminals in smart grid, wireless terminals in transportation safety Terminals, wireless terminals in smart cities, wireless terminals in smart homes, etc.
  • the terminal may also be a handheld device, a vehicle-mounted device, a wearable device, a computing device, or other processing device connected to a wireless modem with wireless communication functions and wireless sensing functions.
  • the terminal device can also be called by different names in different networks, for example: terminal device, access terminal, subscriber unit, subscriber station, mobile station, mobile station, remote station, remote terminal, mobile equipment, user terminal , terminal, wireless communication equipment, user agent or user device, cellular phone, cordless phone, session initiation protocol (session initiation protocol, SIP) phone, wireless local loop (wireless local loop, WLL) station, personal digital processing (personal digital) assistant, PDA), 5G communication system or terminals in future evolution communication systems, etc.
  • terminal device access terminal, subscriber unit, subscriber station, mobile station, mobile station, remote station, remote terminal, mobile equipment, user terminal , terminal, wireless communication equipment, user agent or user device, cellular phone, cordless phone, session initiation protocol (session initiation protocol, SIP) phone, wireless local loop (wireless local loop, WLL) station, personal digital processing (personal digital) assistant, PDA), 5G communication system or terminals in future evolution communication systems, etc.
  • SIP session initiation protocol
  • WLL wireless local loop
  • the above-mentioned access network functional entity may be a functional entity used by the access network side to support communication terminals to access the wireless communication system.
  • it can be the next generation base station (next generation NodeB, gNB), transmission reception point (TRP), relay node (relay node), access point (AP), etc. in the 5G communication system.
  • next generation base station next generation NodeB, gNB
  • TRP transmission reception point
  • relay node relay node
  • AP access point
  • each functional entity and interface are only exemplary, and not all functions of each functional entity are necessary when applied in the embodiments of the present disclosure.
  • the functional entities of the access network and the core network may be physical physical devices or virtualized devices, which are not limited here.
  • the communication system in the embodiment of the present disclosure may also include other devices not shown in Figure 1, which are not limited here.
  • XR and media (extend reality and media, XRM) business In 5G networks, mobile media services, XR, cloud games, video-based machine or drone remote control, etc. are expected to contribute more and more traffic to 5G networks.
  • XR and media (extend reality and media, XRM) business Especially XR and media (extend reality and media, XRM) business.
  • XRM business has the characteristics of high throughput, low latency, and high reliability requirements, and requires high power consumption on the terminal side. The battery power of the terminal may affect the user experience.
  • connection management connection management
  • CM connection management
  • MICO mobile initiated connection only
  • extended DRX extended discontinuous reception
  • eDRX extended discontinuous reception
  • embodiments of the present disclosure provide a QoS flow control method.
  • FIG 2 is a schematic flowchart of the implementation of the first QoS flow control method in an embodiment of the present disclosure.
  • the QoS flow control method is applied to the first core network functional entity (such as PCF ) side, the QoS flow control method may include S201 to S204.
  • PCF receives terminal status information (UE status information) sent from the application function entity (such as AF).
  • UE status information UE status information
  • the application function entity such as AF
  • the terminal status information is used to indicate the power consumption status of the UE.
  • the terminal status information includes one or more parameters related to the UE performance.
  • the UE status information may include at least one of the following: UE battery level, UE battery life, UE's power supply mode (powered mode), UE's CPU load, UE overheating status (UE overheating status).
  • parameters related to UE power consumption may include other parameters.
  • the power supply mode of the UE may include: battery-powered mode (battery-powered) and power supply mode (mains/wall-powered).
  • the battery power supply mode refers to using the built-in battery of the UE to provide power
  • the power supply mode refers to using a power adapter to connect to a power source such as a wall socket, a mobile socket, etc., to power the UE.
  • the registered UE can report its own terminal status information to the AF through the application layer, and then the AF reports it to the PCF.
  • the AF may, but is not limited to, send terminal status information to the PCF through the following paths.
  • AF directly sends terminal status information to PCF. It can be understood that AF sends terminal status information to PCF through Naf and Npcf. At this time, AF is trusted AF.
  • AF sends terminal status information to PCF through NEF. It can be understood that AF sends terminal status information to NEF through Naf and Nnef, and NEF sends terminal status information to PCF through Nnef and Npcf. At this time, AF is an untrusted AF.
  • AF sends terminal status information to PCF through TSCTSF. It is understandable that AF sends terminal status information to TSCTSF through Naf and Ntsctsf, and TSCTSF sends terminal status information to PCF through Ntsctsf and Npcf.
  • AF is a trusted AF
  • the first service is a time-sensitive service.
  • AF sends terminal status information to PCF through NEF and TSCTSF. It can be understood that AF sends the terminal status information to NEF through Naf and Nnef, and NEF sends the terminal status information to TSCTSF through Nnef and Ntsctsf. TSCTSF then sends the terminal status information to PCF through Ntsctsf and Npcf. At this time, AF is not Trusted AF, the first service is time-sensitive service.
  • one or more NFs can be set between the AF and the PCF, such as the above-mentioned NEF, TSCTSF, etc.
  • different transmission paths may exist for terminal status information. It should be noted that the above is only an example of the transmission path of the terminal status information, and does not limit the transmission method and transmission path of the terminal status information.
  • the terminal status information can also be transmitted from the AF to the PCF using other paths.
  • the AF when the AF is an untrusted AF, the AF can provide terminal status information to the NEF, and the terminal status information is carried in the AF request message.
  • the AF request message may include: NEF parameter creation request message (such as Nnef_ParameterProvision_Create Request), NEF parameter update request message (such as Nnef_ParameterProvision_Update Request), AF session resource request message (such as Nnef_AFsessionWithQoS_Create request), etc.
  • NEF authorizes AF's request and performs related mapping. NEF then provides terminal status information to PCF.
  • NEF can also provide terminal status information to one or more PCFs corresponding to the multi-UEs.
  • NEF may send terminal status information to the corresponding PCF according to the UE's identity or group identity.
  • NEF after receiving the terminal status information sent by the AF, NEF can also send the terminal status information to the user data register (user data repository, UDR) functional entity or unified data management (unified data management, UDM) ) functional entity, used as AMF associated parameter storage, SMF associated parameter storage or business characteristic parameter storage of application data.
  • user data register user data repository, UDR
  • unified data management unified data management
  • the PCF may perform at least one of S202 to S203.
  • the above-mentioned QoS flows may be of different granularities, for example, they may be session-specific (ie, session QoS flow) or service-oriented (eg, business data flow QoS flow). This is not the case in the embodiments of the present disclosure. Specific limitations.
  • the PCF can determine corresponding QoS parameters for one or more sessions of a service (ie, the first service) of the UE according to the terminal status information.
  • the PCF may determine corresponding QoS parameters for a service of the UE (ie, the first service) based on the terminal status information.
  • "OK” can be described as “setting”, “generating”, “updating”, etc.
  • S203 The PCF sends terminal status information to other PCFs, and the terminal status information is used by other PCFs to perform QoS updates on the QoS flow.
  • PCF can be recorded as PCF0
  • PCF 1 PCF 2, PCF 3,
  • PCF 3 PCF 1, PCF 2, PCF 3,
  • PCF 0 after receiving the terminal status information, PCF 0 can directly send it to other PCFs such as PCF 1, PCF 2, PCF 3, etc.
  • other PCFs such as PCF 1, PCF 2, PCF 3, etc. can also subscribe to PCF 0 for events associated with the terminal status information (i.e., the first event).
  • PCF 0 sends terminal status information to other PCFs such as PCF 1, PCF 2, PCF 3, etc.
  • all PCFs subscribe to NEF for events related to terminal status information.
  • NEF sends terminal status information to all PCFs.
  • multiple PCFs can also obtain terminal status information through other methods, which are not specifically limited in the embodiments of the present disclosure.
  • the above-mentioned QoS flows may be GBR QoS flows and non-GBR QoS flows.
  • the corresponding QoS parameters are also different.
  • the QoS parameters of the QoS flow may include: GFBR and/or MFBR.
  • the QoS parameters of the QoS flow can include: AMBR.
  • AMBR can be divided into: AMBR per terminal (UE-AMBR) and AMBR per session (session-AMBR) according to different granularities.
  • S202 may include: the PCF decreases or increases one or more of the GFBR and MFBR according to the terminal status information, so as to GBR QoS flow performs QoS updates.
  • Figure 3 is a schematic flowchart of an implementation of performing QoS updates on GBR QoS flows in an embodiment of the present disclosure.
  • the PCF can also perform at least the following: One: S301 and S302.
  • PCF sends QoS parameters (such as GFBR and/or MFBR) to the UPF entity.
  • QoS parameters are used by UPF to perform QoS updates on the downlink GBR QoS flow.
  • PCF can send QoS parameters to SMF through Npcf and Nsmf, and then SMF sends it to UPF. After UPF receives the QoS parameters, it uses the QoS parameters to perform QoS updates on the downstream GBR QoS flow.
  • the PCF sends QoS parameters to the base station.
  • the QoS parameters are used by the base station to perform QoS updates on the uplink and/or downlink GBR QoS flows.
  • the PCF can send the QoS parameters to the AMF through Npcf and Namf, and then the AMF sends it to the base station. After receiving the QoS parameters, the base station uses the QoS parameters to perform QoS updates on the uplink and/or downlink GBR QoS flows.
  • AMF and SMF can also obtain the QoS parameters sent by PCF by subscribing to events.
  • AMF can subscribe to PCF for events related to QoS parameters. After the QoS parameters, PCF queries the subscription events and confirms the events associated with the QoS parameters. When the event meets the reporting conditions, PCF sends QoS parameters to AMF.
  • SMF can also subscribe to PCF for events related to QoS parameters. After the QoS parameters, PCF queries the subscription events and confirms the events associated with the QoS parameters. When the event meets the reporting conditions, PCF sends QoS parameters to SMF.
  • AMF and SMF can also use other methods to obtain QoS parameters from PCF, and this is not specifically limited in the embodiments of the present disclosure.
  • Figure 4 is a schematic flowchart of an implementation of QoS update for non-GBR QoS flows in an embodiment of the present disclosure.
  • the PCF can also Perform at least one of the following: S401 to S403.
  • PCF sends session-AMBR to UPF, so that UPF uses session-AMBR to perform QoS updates on the uplink and/or downlink session QoS flows.
  • PCF first sends session-AMBR to SMF, and then SMF sends it to UPF.
  • the PCF sends session-AMBR to the UE, causing the UE to perform PDU session-based uplink rate limitation on non-GBR QoS flows.
  • the PCF sends the UE-AMBR to the base station, so that the base station performs QoS updates on the uplink and/or downlink non-GBR QoS flows of each UE.
  • PCF can also perform other QoS updates for the GBR QoS flow, which is not specifically limited in this embodiment of the disclosure.
  • the QoS flow is a GBR QoS flow or a non-GBR QoS flow
  • the QoS parameters of the QoS flow include: MBR per terminal per slice (UE-slice-MBR).
  • the above method includes: the PCF sends the UE-slice-MBR to the base station, so that the base station performs QoS update on the PDU session QoS flow corresponding to the S-NSSAI of the UE.
  • S-NSSAI is used to represent a network slice (slice)
  • the UE can correspond to one or more PDU sessions on one slice, and the one or more PDU sessions are sessions of the first service. Then, after receiving the UE-slice-MBR, the base station uses the UE-slice-MBR to perform QoS updates for the QoS flows of all sessions of the first service on the slice corresponding to the S-NSSAI.
  • the base station admission control should ensure that the sum of the GFBR values of the admitted GBR QoS flow does not exceed the UE-Slice-MBR. If the QoS flow cannot be Accepted, the base station shall reject the establishment or modification of the QoS flow. And, the base station should ensure that the aggregate bit rate of all GBR and non-GBR QoS flows belonging to the PDU sessions corresponding to the UE's S-NSSAI does not exceed the UE-Slice-MBR, while always ensuring the GFBR of each GBR QoS flow of these PDU sessions.
  • PCF performs QoS update, and the QoS parameters sent by PCF are updated QoS parameters.
  • PCF completes the process of performing QoS update based on terminal status information.
  • the above QoS control process can be reused with the service specific information provisioning procedure (Service specific information provisioning procedure), AF session establishment procedure (Setting up an AF session with required QoS procedure), etc.
  • service specific information provisioning procedure Service specific information provisioning procedure
  • AF session establishment procedure Setting up an AF session with required QoS procedure
  • it can also be reused in other processes, which is not specifically limited in the embodiments of the present disclosure.
  • the AF provides the terminal status information of the UE to the PCF, so that the PCF can match the service traffic characteristics and terminal energy consumption management according to the terminal status information, that is, control the QoS flow according to the power consumption status of the UE to ensure Business needs and user experience.
  • the terminal status information provided by the AF is used as additional information for policy determination, which can reduce the use of wireless interface network resources, especially when resources are limited.
  • the AF provides the PCF with the terminal status information of the UE, which can support the use of network resources according to the UE's capabilities.
  • U's terminal status information is provided to the PCF through AF, allowing the user's critical applications to be run in the power saving mode, thereby improving the user experience and extending battery life, rather than shutting down completely.
  • embodiments of the present disclosure also provide a QoS flow control method.
  • Figure 5 is a schematic flowchart of the implementation of the second QoS flow control method in the embodiment of the present disclosure. Referring to Figure 5, the QoS flow control method can be applied to the application function entity (such as AF) side.
  • the QoS flow control method can Including S501 to S502.
  • the AF receives the terminal status information sent by the UE.
  • the terminal status information is used to indicate the power consumption status of the UE.
  • the UE After the UE registers with the network, it selects PCF to complete AM session association. The UE sends terminal status information to the AF.
  • the AF sends terminal status information to the PCF.
  • the terminal status information is also used by the PCF to perform QoS updates on the QoS flow associated with the UE.
  • the AF may, but is not limited to, send terminal status information to the PCF through the following paths.
  • AF directly sends terminal status information to PCF. It can be understood that AF sends terminal status information to PCF through Naf and Npcf. At this time, AF is trusted AF.
  • AF sends terminal status information to PCF through NEF. It can be understood that AF sends terminal status information to NEF through Naf and Nnef, and NEF sends terminal status information to PCF through Nnef and Npcf. At this time, AF is an untrusted AF.
  • AF sends terminal status information to PCF through TSCTSF. It is understandable that AF sends terminal status information to TSCTSF through Naf and Ntsctsf, and TSCTSF sends terminal status information to PCF through Ntsctsf and Npcf.
  • AF is a trusted AF
  • the first service is a time-sensitive service.
  • AF sends terminal status information to PCF through NEF and TSCTSF. It can be understood that AF sends the terminal status information to NEF through Naf and Nnef, and NEF sends the terminal status information to TSCTSF through Nnef and Ntsctsf. TSCTSF then sends the terminal status information to PCF through Ntsctsf and Npcf. At this time, AF is not Trusted AF, the first service is time-sensitive service.
  • one or more NFs can be set between the AF and the PCF, such as the above-mentioned NEF, TSCTSF, etc.
  • different transmission paths may exist for terminal status information. It should be noted that the above is only an example of the transmission path of the terminal status information, and does not limit the transmission method and transmission path of the terminal status information.
  • the terminal status information can also be transmitted from the AF to the PCF using other paths.
  • the execution process of AF can be referred to the description of the AF execution process in the above-mentioned embodiments of FIGS. 2 to 4. For the sake of simplicity of the description, no further description is given here.
  • FIG. 6 is a schematic structural diagram of a QoS flow control device in the embodiment of the present disclosure.
  • the control device 600 can It includes: processing module 601, receiving module 602 and sending module 603.
  • control device may be the first core network functional entity in the communication system or a chip or system-on-chip of the first core network functional entity. It may also be the first core network functional entity used to implement the above.
  • the control device can realize the functions performed by the first core network functional entity in the above embodiments, and these functions can be realized by hardware executing corresponding software. These hardware or software include one or more modules corresponding to the above functions.
  • the device may include: a receiving module 602, configured to receive terminal status information from the application function entity, where the terminal status information is used to represent the power consumption status of the terminal; a processing module 601, configured to, based on the terminal status information, perform a The QoS flow performs QoS update; the sending module 603 is configured to send terminal status information to the second core network functional entity, and the terminal status information is used by the second core network functional entity to perform QoS update on the QoS flow.
  • the first core network functional entity may be a PCF entity
  • the second core network functional entity may be other PCF entities.
  • the QoS flow includes at least one of the following: session QoS flow; service data flow QoS flow.
  • the terminal status information includes at least one of the following: battery power; battery life; power supply mode; CPU load; and terminal overheating status.
  • the QoS flow is a GBR QoS flow
  • the QoS parameters of the QoS flow include: GFBR and/or MFBR.
  • the processing module 601 is configured to reduce or increase the GFBR according to the terminal status information.
  • the sending module 603 is configured to send the MFBR to the third core network functional entity.
  • the MFBR is used by the third core network functional entity to perform QoS updates on the downlink GBR QoS flow; and/or to the access network.
  • the functional entity sends MFBR, which is used by the access network functional entity to perform QoS updates on the uplink and/or downlink GBR QoS flows.
  • the third core network functional entity may be a UPF entity.
  • the QoS flow is a non-GBR QoS flow
  • the QoS parameters of the QoS flow include: AMBR.
  • the processing module 601 is configured to reduce or increase the AMBR according to the terminal status information.
  • AMBR includes at least one of the following: AMBR per terminal, AMBR per session.
  • the sending module 603 in response to the AMBR including the AMBR per session, is configured to send the AMBR per session to the third core network functional entity, and the AMBR per session is used for the third core network functional entity. Perform QoS updates on upstream and/or downstream session QoS flows; or, send per-session AMBR to the terminal, and the per-session AMBR is used by the terminal to perform PDU session-based upstream rate limiting on non-GBR QoS flows.
  • the sending module 603 in response to the AMBR including the AMBR of each terminal, is configured to send the AMBR of each terminal to the access network functional entity, and the AMBR of each terminal is used by the access network functional entity for each QoS updates are performed on the terminal's upstream and/or downstream non-GBR QoS flows.
  • the QoS flow is a GBR QoS flow or a non-GBR QoS flow
  • the QoS parameters of the QoS flow include: MBR per terminal per slice.
  • the sending module 603 in response to the QoS parameters including the MBR per terminal per slice, is configured to send the MBR per terminal per slice to the access network functional entity, and the MBR per terminal per slice is used for access.
  • the network access functional entity performs QoS updates on the PDU session QoS flow corresponding to the terminal's S-NSSAI.
  • the application function entity is a trusted application function entity; the receiving module 602 is configured to perform one of the following: receiving terminal status information sent by the application function entity; receiving terminal status information sent by the TSCTSF entity. Status information is sent by the application function entity to the TSCTSF entity.
  • the application function entity is an untrusted application function entity; the receiving module 602 is configured to perform one of the following: receiving terminal status information sent by the NEF entity, and the terminal status information is sent to the NEF by the application function entity Entity; receives the terminal status information sent by the TSCTSF entity. The terminal status information is sent by the application function entity to the TSCTSF entity through the NEF entity.
  • the processing module 601 is configured to query subscription events and determine the first event associated with the terminal status information; the sending module 603 is configured to send the first event to the third event if the first event satisfies the event reporting condition.
  • the second core network functional entity sends terminal status information.
  • control device may also be an application function entity in the communication system or a chip or system-on-chip of the application function entity, or may be an application function entity used to implement the methods described in the above embodiments.
  • functional module The control device can realize the functions performed by the application function entities in the above embodiments, and these functions can be realized by hardware executing corresponding software. These hardware or software include one or more modules corresponding to the above functions.
  • the receiving module 602 is configured to receive terminal status information sent by the terminal, and the terminal status information is used to represent the power consumption status of the terminal; the sending module 603 is configured to send the terminal status information to the first core network functional entity, and the terminal The status information is also used by the first core network functional entity to perform QoS update on the QoS flow associated with the terminal.
  • the QoS flow includes at least one of the following: QoS flow of the session; QoS flow of the service data flow.
  • the terminal status information includes at least one of the following: battery power; battery life; power supply mode; CPU load; and terminal overheating status.
  • the application function entity is a trusted application function entity; the sending module 603 is configured to perform one of the following: sending terminal status information to the first core network functional entity; sending terminal status information to the TSCTSF entity, The terminal status information is also used by the TSCTSF entity to send to the first core network functional entity.
  • the application function entity is an untrusted application function entity; the sending module 603 is configured to send terminal status information to the NEF entity.
  • the terminal status information is also used by the NEF entity to send the first core network function entity to the NEF entity.
  • Send, or the terminal status information is also used by the NEF entity to send to the first core network function entity through the TSCTSF entity.
  • the receiving module 602 mentioned in the embodiment of the present disclosure may be a receiving interface, a receiving circuit or a receiver, etc.; the sending module 603 may be a sending interface, a sending circuit or a transmitter, etc.; and the processing module 601 may be one or more processors.
  • FIG. 7 is a schematic structural diagram of a communication device in an embodiment of the present disclosure.
  • the communication device 700 uses general computer hardware, including a processor 701, a memory 702, a bus 703, an input device 704 and an output device.
  • memory 702 may include computer storage media in the form of volatile and/or non-volatile memory, such as read-only memory and/or random access memory.
  • Memory 702 may store an operating system, application programs, other program modules, executable code, program data, user data, and the like.
  • Input device 704 may be used to enter commands and information to a communication device, such as a keyboard or pointing device such as a mouse, trackball, touch pad, microphone, joystick, game pad, satellite television dish, scanner, or similar device. These input devices may be connected to processor 701 via bus 703 .
  • the output device 705 can be used for communication devices to output information.
  • the output device 705 can also be other peripheral output devices, such as speakers and/or printing devices. These output devices can also be connected to the processor 701 through the bus 703. .
  • the communication device may be connected to a network through the antenna 706, such as a local area network (LAN).
  • LAN local area network
  • the computer execution instructions stored in the control device can be stored in a remote storage device and are not limited to local storage.
  • the communication device executes the relay communication method on the UE side or the network device side in the above embodiments.
  • the specific execution process refer to the above embodiments. , which will not be described in detail here.
  • the above-mentioned memory 702 stores computer execution instructions for realizing the functions of the processing module 601, the receiving module 602 and the sending module 603 in FIG. 6 .
  • the functions/implementation processes of the processing module 601, the receiving module 602 and the sending module 603 in Figure 6 can all be implemented by the processor 701 in Figure 7 calling the computer execution instructions stored in the memory 702.
  • the processor 701 in Figure 7 calling the computer execution instructions stored in the memory 702.
  • embodiments of the present disclosure provide a network functional entity, such as a first core network functional entity or an application functional entity.
  • FIG 8 is a schematic structural diagram of a network functional entity in an embodiment of the present disclosure.
  • the network functional entity 800 may include a processing component 801, which further includes one or more processors, and is represented by a memory 802 A memory resource used to store instructions, such as application programs, that can be executed by processing component 801.
  • the application program stored in memory 802 may include one or more modules, each corresponding to a set of instructions.
  • the processing component 801 is configured to execute instructions to perform any of the foregoing methods applied to the network device.
  • the network function entity 800 may also include a power supply component 803 configured to perform power management of the network function entity 800, a wired or wireless network interface 804 configured to connect the network function entity 800 to the network, and an input/output (I/O ) interface 805.
  • the network function entity 800 may operate based on an operating system stored in the memory 802, such as Windows ServerTM, Mac OS XTM, UnixTM, LinuxTM, FreeBSDTM or the like.
  • an embodiment of the present disclosure also provides a communication device, such as a first core network functional entity, including: a memory and a processor; the processor is connected to the memory and is configured to execute computer executable data stored on the memory. Instructions are provided to implement the QoS flow control method on the first core network functional entity side as described in one or more of the above embodiments.
  • embodiments of the present disclosure also provide a computer-readable storage medium. Instructions are stored in the computer-readable storage medium; when the instructions are run on the computer, they are used to execute the network in one or more of the above embodiments. QoS flow control method on the functional entity side.
  • the network functional entity may include: a first core network functional entity or an application functional entity.
  • embodiments of the present disclosure also provide a computer program or computer program product.
  • the computer program product When the computer program product is executed on a computer, it causes the computer to implement QoS on the entity side of the network function in one or more of the above embodiments.
  • the network functional entity may include: a first core network functional entity or an application functional entity.

Landscapes

  • Engineering & Computer Science (AREA)
  • Quality & Reliability (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Mobile Radio Communication Systems (AREA)
  • Power Sources (AREA)

Abstract

La présente divulgation concerne un procédé et un appareil de commande de flux de qualité de service, et un support de stockage informatique. Le procédé de commande peut être appliqué à un système 5G. Le procédé peut comprendre : la réception, par une première entité de fonction de réseau central, d'informations d'état de terminal en provenance d'une entité de fonction d'application (S201), les informations d'état de terminal étant utilisées pour représenter l'état de consommation d'énergie d'un terminal; et l'exécution; par la première entité de fonction de réseau central, de ce qui suit : l'exécution, selon les informations d'état de terminal, d'une mise à jour de qualité de service, QoS, sur un flux de QoS associé au terminal (S202) et/ou l'envoi des informations d'état de terminal à une seconde entité de fonction de réseau central, les informations d'état de terminal étant utilisées pour que la seconde entité de fonction de réseau central exécute une mise à jour de QoS sur un flux de QoS (S203). Dans la présente divulgation, une entité de fonction d'application fournit des informations d'état de terminal d'un terminal à une première entité de fonction de réseau central, de sorte que la première entité de fonction de réseau central peut commander un flux de QoS selon l'état de consommation d'énergie du terminal de façon à garantir une exigence de service et la convivialité d'utilisation.
PCT/CN2022/102934 2022-06-30 2022-06-30 Procédé et appareil de commande de flux de qualité de service, et support de stockage informatique WO2024000445A1 (fr)

Priority Applications (2)

Application Number Priority Date Filing Date Title
CN202280002504.XA CN117643100A (zh) 2022-06-30 2022-06-30 一种QoS流的控制方法、装置及计算机存储介质
PCT/CN2022/102934 WO2024000445A1 (fr) 2022-06-30 2022-06-30 Procédé et appareil de commande de flux de qualité de service, et support de stockage informatique

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/CN2022/102934 WO2024000445A1 (fr) 2022-06-30 2022-06-30 Procédé et appareil de commande de flux de qualité de service, et support de stockage informatique

Publications (1)

Publication Number Publication Date
WO2024000445A1 true WO2024000445A1 (fr) 2024-01-04

Family

ID=89383817

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2022/102934 WO2024000445A1 (fr) 2022-06-30 2022-06-30 Procédé et appareil de commande de flux de qualité de service, et support de stockage informatique

Country Status (2)

Country Link
CN (1) CN117643100A (fr)
WO (1) WO2024000445A1 (fr)

Citations (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101242576A (zh) * 2007-02-06 2008-08-13 Lg电子株式会社 无线通信系统及其终端装置和基站及它们的信道调度方法
CN102158871A (zh) * 2010-02-12 2011-08-17 中兴通讯股份有限公司 一种适应终端差异化的通信方法、系统、控制站及终端
US20110268000A1 (en) * 2010-05-03 2011-11-03 Palm, Inc. Apparatus and methods for power management on mobile devices
CN109121187A (zh) * 2017-06-22 2019-01-01 中国移动通信有限公司研究院 一种业务传输方法、设备及计算机可读存储介质
CN110166377A (zh) * 2018-02-14 2019-08-23 华为技术有限公司 一种资源分配方法和装置
CN110475270A (zh) * 2019-07-18 2019-11-19 中国联合网络通信集团有限公司 一种终端参数配置方法及装置

Patent Citations (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101242576A (zh) * 2007-02-06 2008-08-13 Lg电子株式会社 无线通信系统及其终端装置和基站及它们的信道调度方法
CN102158871A (zh) * 2010-02-12 2011-08-17 中兴通讯股份有限公司 一种适应终端差异化的通信方法、系统、控制站及终端
US20110268000A1 (en) * 2010-05-03 2011-11-03 Palm, Inc. Apparatus and methods for power management on mobile devices
CN109121187A (zh) * 2017-06-22 2019-01-01 中国移动通信有限公司研究院 一种业务传输方法、设备及计算机可读存储介质
CN110166377A (zh) * 2018-02-14 2019-08-23 华为技术有限公司 一种资源分配方法和装置
CN110475270A (zh) * 2019-07-18 2019-11-19 中国联合网络通信集团有限公司 一种终端参数配置方法及装置

Also Published As

Publication number Publication date
CN117643100A (zh) 2024-03-01

Similar Documents

Publication Publication Date Title
US11611949B2 (en) Keeping the UE awake
US11778493B2 (en) Data collection method, device, and system
US20220060935A1 (en) Communications Method and Apparatus
EP3713372A1 (fr) Procédé et dispositif de création de groupe d'utilisateurs
WO2021018200A1 (fr) Procédé et appareil de gestion de session
US11848963B2 (en) Method for providing restricted service, and communications device
WO2021036925A1 (fr) Appareil et procédé de communication
US11310658B2 (en) Method and apparatus for determining status of terminal device, and device
WO2021081875A1 (fr) Procédé et dispositif de commande d'état de connexion rrc, et support de stockage
US20230354237A1 (en) Method and apparatus for determining transmission delay, device, and storage medium
WO2024000445A1 (fr) Procédé et appareil de commande de flux de qualité de service, et support de stockage informatique
WO2024020759A1 (fr) Procédé de commande de flux de qos, appareil, et support de stockage informatique
WO2024000450A1 (fr) Procédé et appareil de commande de flux de qualité de service et support de stockage informatique
WO2024020760A1 (fr) Procédé et appareil de commande de flux de qos, et support de stockage informatique
WO2023245458A1 (fr) Procédé et appareil de transmission d'information et support de stockage informatique
WO2021004534A1 (fr) Procédé, dispositif et système de transmission de données d'utilisateur de liaison montante
WO2022016338A1 (fr) Procédé et appareil de communication
WO2022160275A1 (fr) Procédé de communication sans fil, et dispositifs et support de stockage
WO2022178682A1 (fr) Procédé et appareil de transmission de données
WO2024007271A1 (fr) Procédé et appareil de commutation de service de détection, dispositif électronique et support de stockage
WO2024050838A1 (fr) Procédé et appareil de communication
WO2024000435A1 (fr) Procédé et appareil de gestion de dispositif de l'internet des objets, et dispositif et support de stockage
WO2023197320A1 (fr) Procédé et appareil de configuration de signal de référence de positionnement de liaison montante, et dispositif et support de stockage
WO2024032552A1 (fr) Procédé et appareil de communication, et support de stockage
WO2024077546A1 (fr) Procédé d'appel de capacité et appareil de communication

Legal Events

Date Code Title Description
WWE Wipo information: entry into national phase

Ref document number: 202280002504.X

Country of ref document: CN

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

Ref document number: 22948549

Country of ref document: EP

Kind code of ref document: A1