WO2024152162A1 - 多模态业务数据流的管理方法和装置 - Google Patents

多模态业务数据流的管理方法和装置 Download PDF

Info

Publication number
WO2024152162A1
WO2024152162A1 PCT/CN2023/072422 CN2023072422W WO2024152162A1 WO 2024152162 A1 WO2024152162 A1 WO 2024152162A1 CN 2023072422 W CN2023072422 W CN 2023072422W WO 2024152162 A1 WO2024152162 A1 WO 2024152162A1
Authority
WO
WIPO (PCT)
Prior art keywords
data flow
request message
service data
group
pcf
Prior art date
Application number
PCT/CN2023/072422
Other languages
English (en)
French (fr)
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 PCT/CN2023/072422 priority Critical patent/WO2024152162A1/zh
Publication of WO2024152162A1 publication Critical patent/WO2024152162A1/zh

Links

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/08—Configuration management of networks or network elements
    • H04L41/0894—Policy-based network configuration management
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L47/00—Traffic control in data switching networks
    • H04L47/10—Flow control; Congestion control
    • H04L47/24—Traffic characterised by specific attributes, e.g. priority or QoS
    • H04L47/2483—Traffic characterised by specific attributes, e.g. priority or QoS involving identification of individual flows

Definitions

  • the present disclosure relates to the field of communication technology, and in particular to a method and device for managing multimodal service data streams.
  • XR services also involve multimodal data streams, which can be data input from the same device or different devices (including sensors) to describe the same service or application, and these data may be output to one or more destination device terminals.
  • the data streams in multimodal data are often related, such as the synchronization of audio and video streams, and the synchronization of touch and vision.
  • the disclosed embodiments provide a method and device for managing a multimodal business data flow.
  • the PCF can determine the business data flow group to which the business data flow belongs, and generate or update the corresponding PCC rules. It can make policy decisions and resource authorizations for the business data flow more reasonably, and ensure the consistency of policy decisions for business data flows belonging to the same business data flow group.
  • an embodiment of the present disclosure provides a method for managing a multimodal service data flow, which is executed by a PCF, including: the PCF receives a request message sent by an AF, and generates or updates a policy and charging control PCC rule according to the request message.
  • PCF receives the request message sent by AF, and generates or updates the policy and charging control PCC rules according to the request message.
  • PCF can determine the service data flow group to which the service data flow belongs, and generate or update the corresponding PCC rules, so that policy decisions and resource authorization can be made more reasonably for the service data flow, and the consistency of policy decisions for the service data flows belonging to the same service data flow group can be ensured.
  • an embodiment of the present disclosure provides another method for managing multimodal service data flows, which is executed by AF and includes: sending a request message to PCF, wherein the request message is used to indicate adding the service data flow to a first service data flow group and/or removing the service data flow from a second service data flow group.
  • an embodiment of the present disclosure provides a communication device, which has some or all of the functions of the PCF in the method described in the first aspect above.
  • the functions of the communication device may have some or all of the functions in the embodiments of the present disclosure, or may have the functions of implementing any one of the embodiments of the present disclosure alone.
  • the functions may be implemented by hardware, or by hardware executing corresponding software.
  • the hardware or software includes one or more units or modules corresponding to the above functions.
  • the communication device includes: a transceiver module configured to receive a request message sent by an AF, and a processing module configured to generate or update a policy and charging control PCC rule according to the request message.
  • an embodiment of the present disclosure provides another communication device, which has some or all of the functions of AF in the method example described in the second aspect above.
  • the functions of the communication device may have some or all of the functions in the embodiments of the present disclosure, or may have the functions of implementing any one of the embodiments of the present disclosure alone.
  • the functions may be implemented by hardware, or by hardware executing corresponding software.
  • the hardware or software includes one or more units or modules corresponding to the above functions.
  • the communication device includes: a transceiver module configured to send a request message to the PCF, wherein the request message is used to instruct to add a service data flow to a first service data flow group and/or remove a service data flow from a second service data flow group.
  • an embodiment of the present disclosure provides a communication device, which includes a processor.
  • the processor calls a computer program in a memory, the method described in the first aspect is executed.
  • an embodiment of the present disclosure provides a communication device, which includes a processor.
  • the processor calls a computer program in a memory, the method described in the second aspect is executed.
  • an embodiment of the present disclosure provides a communication device, which includes a processor and a memory, in which a computer program is stored; the processor executes the computer program stored in the memory so that the communication device executes the method described in the first aspect above.
  • an embodiment of the present disclosure provides a communication device, which includes a processor and a memory, in which a computer program is stored; the processor executes the computer program stored in the memory so that the communication device executes the method described in the second aspect above.
  • an embodiment of the present disclosure provides a communication device, which includes a processor and an interface circuit, wherein the interface circuit is used to receive code instructions and transmit them to the processor, and the processor is used to run the code instructions to enable the device to execute the method described in the first aspect above.
  • an embodiment of the present disclosure provides a communication device, which includes a processor and an interface circuit, wherein the interface circuit is used to receive code instructions and transmit them to the processor, and the processor is used to run the code instructions to enable the device to execute the method described in the second aspect above.
  • an embodiment of the present disclosure provides a communication system, the system comprising the communication device described in the third aspect and the communication device described in the fourth aspect, or the system comprising the communication device described in the fifth aspect and the communication device described in the sixth aspect, or the system comprising the communication device described in the seventh aspect and the communication device described in the eighth aspect, or the system comprising the communication device described in the ninth aspect and the communication device described in the tenth aspect.
  • an embodiment of the present invention provides a computer-readable storage medium for storing instructions used by the above-mentioned PCF. When the instructions are executed, the PCF executes the method described in the first aspect.
  • an embodiment of the present invention provides a readable storage medium for storing instructions used by the above-mentioned AF, and when the instructions are executed, the AF executes the method described in the above-mentioned second aspect.
  • the present disclosure further provides a computer program product comprising a computer program, which, when executed on a computer, enables the computer to execute the method described in the first aspect above.
  • the present disclosure further provides a computer program product comprising a computer program, which, when executed on a computer, enables the computer to execute the method described in the second aspect above.
  • the present disclosure provides a chip system, which includes at least one processor and an interface, for supporting the PCF to implement the functions involved in the first aspect, for example, determining or processing at least one of the data and information involved in the above method.
  • the chip system also includes a memory, which is used to store computer programs and data necessary for the PCF.
  • the chip system can be composed of chips, or it can include chips and other discrete devices.
  • the present disclosure provides a chip system, which includes at least one processor and an interface, and is used to support AF to implement the functions involved in the second aspect, for example, determining or processing at least one of the data and information involved in the above method.
  • the chip system also includes a memory, and the memory is used to store computer programs and data necessary for AF.
  • the chip system can be composed of a chip, or it can include a chip and other discrete devices.
  • the present disclosure provides a computer program, which, when executed on a computer, enables the computer to execute the method described in the first aspect.
  • the present disclosure provides a computer program which, when executed on a computer, enables the computer to execute the method described in the second aspect.
  • FIG1 is a schematic diagram of a communication network architecture provided by an embodiment of the present disclosure.
  • FIG2 is a schematic diagram of another communication network architecture provided by an embodiment of the present disclosure.
  • FIG3 is a flow chart of a method for managing a multimodal service data stream provided in an embodiment of the present disclosure
  • FIG4 is a flowchart of another method for managing multimodal service data flows provided in an embodiment of the present disclosure.
  • FIG5 is a flowchart of another method for managing multimodal service data flows provided in an embodiment of the present disclosure.
  • FIG6 is a flowchart of another method for managing multimodal service data flows provided in an embodiment of the present disclosure.
  • FIG. 7 is a flowchart of another method for managing multimodal service data flows provided in an embodiment of the present disclosure.
  • FIG8 is a flowchart of another method for managing multimodal service data flows provided in an embodiment of the present disclosure.
  • FIG. 9 is a flowchart of another method for managing multimodal service data flows provided in an embodiment of the present disclosure.
  • FIG10 is a flowchart of another method for managing multimodal service data flows provided in an embodiment of the present disclosure.
  • FIG11 is a structural diagram of a communication device provided in an embodiment of the present disclosure.
  • FIG12 is a structural diagram of another communication device provided in an embodiment of the present disclosure.
  • FIG. 13 is a structural diagram of a chip provided in an embodiment of the present disclosure.
  • first, second, third, etc. may be used in the present disclosure to describe various information, such information should not be limited to these terms. These terms are only used to distinguish the same type of information from each other.
  • first information may also be referred to as the second information, and similarly, the second information may also be referred to as the first information.
  • word “if” used herein may be interpreted as "at the time of” or "when” or "in response to determining”.
  • the information including but not limited to user device information, user personal information, etc.
  • data including but not limited to data used for analysis, stored data, displayed data, etc.
  • signals involved in this disclosure are all authorized by the user or fully authorized by all parties, and the collection, use and processing of relevant data need to comply with relevant laws, regulations and standards of relevant countries and regions.
  • GSM Global System of Mobile communication
  • CDMA Code Division Multiple Access
  • WCDMA Wideband Code Division Multiple Access
  • GPRS General Packet Radio Service
  • LTE Long Term Evolution
  • FDD Frequency Division Duplex
  • TDD Time Division Duplex
  • UMTS Universal Mobile Telecommunication System
  • the communication network architecture may include three parts, namely, a terminal device part, a data network (DN), and an operator network part.
  • UE user equipment
  • Terminal equipment can also be called terminal equipment (terminal), user equipment, mobile station (MS), mobile terminal equipment (MT), etc.
  • Terminal equipment can be a car with communication function, a smart car, a mobile phone (mobile phone), a wearable device, a tablet computer (Pad), a computer with wireless transceiver function, a virtual reality (VR) terminal device, an augmented reality (AR) terminal device, a wireless terminal device in industrial control (industrial control), a wireless terminal device in self-driving, a wireless terminal device in remote medical surgery, a wireless terminal device in smart grid (smart grid), a wireless terminal device in transportation safety (transportation safety), a wireless terminal device in a smart city (smart city), a wireless terminal device in a smart home (smart home), etc.
  • the embodiments of the present disclosure do not limit the specific technology and specific device form adopted by the terminal device.
  • (Radio) access network ((radio) access network, (R)AN) is used to provide network access functions for authorized terminal devices in a specific area, and can use transmission tunnels of different qualities according to the level of the terminal device, business requirements, etc.
  • (R)AN can manage wireless resources, provide access services for terminal devices, and then complete the forwarding of control information and/or data information between terminal devices and the core network (CN).
  • the access network device in the embodiment of the present disclosure is a device that provides wireless communication functions for terminal devices, and can also be called a network device.
  • the access network equipment may include: the next generation node basestation (gNB) in the 5G system, the evolved node B (eNB) in the long term evolution (LTE), the radio network controller (RNC), the node B (NB), the base station controller (BSC), the base transceiver station (BTS), the home base station (e.g., home evolved node B, or home node B, HNB), the base band unit (BBU), the transmission point (TRP), the transmitting point (TP), the small base station equipment (pico), the mobile switching center, or the network equipment in the future network.
  • the embodiments of the present disclosure do not limit the specific types of access network equipment. In systems with different wireless access technologies, the names of devices with access network equipment functions may be different.
  • the operator network may include one or more of the following network functions: authentication server function (AUSF), network exposure function (NEF), policy control function (PCF), unified data management (UDM), unified data repository (UDR), network repository function (NRF), application function (AF), access and mobility management function (AMF), session management function (SMF), RAN and user plane function (UPF), unified data repository function (UDR), network data analytics function (NWDAF), etc.
  • AUSF authentication server function
  • NEF network exposure function
  • PCF policy control function
  • UDM unified data management
  • UDR unified data repository
  • NRF network repository function
  • AMF application function
  • SMF session management function
  • UPF user plane function
  • UDF unified data repository function
  • NWDAF network data analytics function
  • AMF is responsible for user mobility management, including mobile state management, allocating temporary user identities, and authenticating and authorizing users.
  • SMF is responsible for UPF selection, UPF reselection, Internet Protocol (IP) address allocation, bearer establishment, modification and release, and QoS control.
  • IP Internet Protocol
  • PCF includes policy control decision-making and flow-based charging control functions, including user subscription data management functions, policy control functions, charging policy control functions, QoS control, etc.
  • UDM is responsible for managing contract data and notifying corresponding network functions when contract data is modified.
  • UDR is responsible for storing and retrieving contract data, policy data, and public architecture data, etc.; it provides UDM, PCF, and NEF with relevant data. UDR should be able to have different data access authentication mechanisms for different types of data, such as contract data and policy data, to ensure the security of data access; UDR should be able to return a failure response with an appropriate reason value for illegal service operations or data access requests.
  • AF is used to provide some application layer services to UE.
  • AF has requirements for QoS policy and charging policy, and needs to notify the network.
  • AF also needs application-related information fed back by other network functions of the core network.
  • NEF mainly supports network capability exposure functions, opening network capabilities and services to the outside world; the 3rd generation partnership project (3GPP) network function (NF) publishes functions and events to other NFs through NEF.
  • 3GPP 3rd generation partnership project
  • NF network function
  • the capabilities and events opened by NF can be securely opened to third-party applications.
  • NEF uses the standardized interface (Nudr) of UDR to store/retrieve structured data.
  • the exchange information of AF is translated with the exchange information of internal network functions. For example, conversion is performed between AF-Service-Identifier and internal 5G core information.
  • Internal 5G core information for example, can be data network name (data network name, DNN) or single network slice selection assistance information (single network slice selection assistance information, S-NSSAI).
  • UPF supports all or part of the following functions: interconnecting protocol data unit (PDU) sessions with data networks; packet routing and forwarding functions, for example, supporting downlink diversion (uplink classifier) of traffic and forwarding it to the data network, supporting branching point function to support multi-homed PDU sessions; and data packet detection function.
  • PDU protocol data unit
  • packet routing and forwarding functions for example, supporting downlink diversion (uplink classifier) of traffic and forwarding it to the data network, supporting branching point function to support multi-homed PDU sessions; and data packet detection function.
  • AUSF is responsible for the authentication function and for executing the network slice specific authentication and authorization (NSSAA) process.
  • NSSAA network slice specific authentication and authorization
  • NWDAF is used to perform signaling interaction with other core networks to understand the network status.
  • the core network can subscribe to NWDAF to understand the network status.
  • the UE radio capability management function is used to store dictionary entries corresponding to the UE radio capability IDs assigned by the public land mobile network (PLMN) or the manufacturer.
  • the AMF can subscribe to the UCMF to obtain new values of the UE radio capability IDs assigned by the UCMF from the UCMF to cache them locally.
  • OAM can cover the network functions of the access network and the core network, and can collect data from these network functions of the access network and the core network.
  • both the third-party (3rd) AF and the operator AF are AFs.
  • the 3rd AF such as WeChat service server and Alipay payment service server
  • the operator AF for example, the proxy-call session control function (P-CSCF) in the IP multimedia system
  • P-CSCF proxy-call session control function
  • Figure 1 shows a schematic diagram of a communication network architecture based on a service-oriented architecture.
  • NEF, NRF, PCF, UDM, AUSF, UDR, AMF and SMF, and any two network functions can communicate in a service-oriented manner.
  • the interfaces Nnef and Nausf used for communication between NEF and AUSF are both service-oriented interfaces.
  • interfaces Nnrf, Npcf, Nudm, Naf, Nudr, Namf and Nsmf are all service-oriented interfaces.
  • AMF can communicate with terminal equipment through the N1 interface
  • AMF can communicate with (R)AN through the N2 interface
  • RAN and UPF can communicate through the N3 interface
  • SMF and UPF can communicate through the N4 interface
  • terminal equipment and RAN can communicate over the air interface
  • UPF and DN can communicate through the N6 interface.
  • FIG2 is a schematic diagram of a communication network architecture based on a point-to-point interface; the main difference between FIG1 and FIG2 is that the interfaces between the various network functions in FIG2 are point-to-point interfaces, rather than service-oriented interfaces.
  • UDSF, NEF, NWDAF and NRF are not described.
  • the core network in FIG2 can interact with UDSF, NEF, NWDAF and NRF as needed.
  • OAM is not reflected in FIG1 and FIG2.
  • OAM can collect data from the access network and the core network.
  • the above network functions or functions can be network elements in hardware devices, software functions running on dedicated hardware, or virtualized functions instantiated on a platform (e.g., a cloud platform).
  • the functions involved in the embodiments of the present disclosure may also be referred to as network elements, functional devices or entities or functional entities.
  • access and mobility management may also be referred to as access and mobility management network elements, access and mobility management functional devices or access and mobility management entities or access and mobility management functional entities.
  • the names of the various functional devices are not limited in the present disclosure. Those skilled in the art may replace the names of the above functional devices with other names and perform the same functions, which all fall within the scope of protection of the present disclosure.
  • the above functional devices may be network elements in hardware devices, software functions running on dedicated hardware, or virtualized functions instantiated on a platform (e.g., a cloud platform).
  • used to indicate may include being used to indicate directly or indirectly.
  • the information may include that the information directly indicates A or indirectly indicates A, but it does not mean that the information must carry A.
  • the information indicated by the information is called the information to be indicated.
  • the information to be indicated there are many ways to indicate the information to be indicated, such as but not limited to, directly indicating the information to be indicated, such as the information to be indicated itself or the index of the information to be indicated.
  • the information to be indicated can also be indirectly indicated by indicating other information, wherein there is an association between the other information and the information to be indicated. It is also possible to indicate only a part of the information to be indicated, while the other parts of the information to be indicated are known or agreed in advance.
  • the indication of specific information can also be achieved by means of the arrangement order of each information agreed in advance (such as specified by the protocol), thereby reducing the indication overhead to a certain extent.
  • the information to be indicated can be sent as a whole or divided into multiple sub-information and sent separately, and the sending period and/or sending time of these sub-information can be the same or different.
  • the specific sending method is not limited in this disclosure. Among them, the sending period and/or sending time of these sub-information can be pre-defined, for example, pre-defined according to a protocol.
  • the embodiments of the present disclosure list multiple implementation methods to clearly illustrate the technical solutions of the embodiments of the present disclosure.
  • the multiple embodiments provided by the embodiments of the present disclosure can be executed separately, or can be executed together with the methods of other embodiments of the embodiments of the present disclosure, or can be executed together with some methods in other related technologies separately or in combination; the embodiments of the present disclosure do not limit this.
  • XR services also involve multimodal data streams, which can be data input from the same device or different devices (including sensors) to describe the same service or application, and these data may be output to one or more destination device terminals.
  • the data streams in multimodal data are often related, such as the synchronization of audio and video streams, and the synchronization of touch and vision.
  • the data streams of such media services, the data streams between them, and the network transmission requirements of these service data streams all have some common characteristics. The effective identification and utilization of these characteristics will be more conducive to the transmission and control of networks and services, as well as to service assurance and user experience.
  • XRM (XR and media) services require the 5th generation system (5GS) to comprehensively consider the quality of service (QoS) characteristics of the relevant data flows of the service, such as whether the parameters such as guaranteed bitrate (GBR) data flow with severe delay, guaranteed flow bitrate (GFBR), packet delay budget (PDB), and maximum data burst volume (MDBV) can be met and coordinated at the same time.
  • QoS quality of service
  • GBR guaranteed bitrate
  • GFBR guaranteed flow bitrate
  • PDB packet delay budget
  • MDBV maximum data burst volume
  • the PCF receives a request message sent by the AF, wherein the request message is used to indicate that the service data flow is added to the first service data flow group and/or the service data flow is removed from the second service data flow group; the PCF can generate or update the Policy and Charging Control (PCC) rules according to the request message.
  • PCC Policy and Charging Control
  • the PCF can determine the service data flow group to which the service data flow belongs, and generate or update the corresponding PCC rules, so as to make policy decisions and resource authorization for the service data flow more reasonably, and ensure the consistency of policy decisions for service data flows belonging to the same service data flow group.
  • Figure 3 is a flow chart of a method for managing multimodal service data flows provided by an embodiment of the present disclosure.
  • the method is executed by the PCF, as shown in Figure 3, and the method may include but is not limited to the following steps:
  • S31 Receive a request message sent by AF.
  • the PCF may receive a request message sent by the AF.
  • the request message is used to indicate at least one of the following:
  • the service data flow is removed from the second service data flow group.
  • the PCF may receive a request message sent by the AF, wherein the request message is used to instruct to add the service data flow to the first service data flow group.
  • the PCF may determine that the service data flow belongs to the first service data flow group.
  • the PCF may receive a request message sent by the AF, wherein the request message is used to instruct to remove the service data flow from the second service data flow group.
  • the PCF may determine that the service data flow does not belong to the second service data flow group.
  • the PCF may receive a request message sent by the AF, wherein the request message is used to indicate that the service data flow is added to the first service data flow group and the service data flow is removed from the second service data flow group.
  • the PCF may determine that the service data flow belongs to the first service data flow group and does not belong to the second service data flow group.
  • the PCF receives the request message sent by the AF, and the request message may indicate to add one or more service data flows to the first service data flow group.
  • the PCF may determine the first service data flow group to which the one or more service data flows belong.
  • the PCF receives the request message sent by the AF, and the request message may indicate to remove one or more service data flows from the second service data flow group.
  • the PCF may determine the second service data flow group to which the one or more service data flows do not belong.
  • the PCF receives the request message sent by the AF, and the request message may indicate that one or more service data flows are added to the first service data flow group and removed from the second service data flow group.
  • the PCF may determine the first service data flow group to which the one or more service data flows belong and the second service data flow group to which the one or more service data flows do not belong.
  • the request message includes a group identifier corresponding to the service data flow, and the group identifier is associated with the first service data flow group or the second service data flow group.
  • the PCF receives a request message sent by the AF, where the request message includes a group identifier corresponding to the service data flow.
  • the group identifier can be a common ID or an XRM service ID (XRM service ID), etc.
  • XRM service ID can indicate different groups through different values, and the embodiments of the present disclosure do not make specific limitations.
  • the group identifier may be associated with the first service data flow group, or the group identifier may also be associated with the second service data flow group.
  • request message is used to instruct to add the service data flow to the first service data flow group and/or to remove the service data flow from the second service data flow group.
  • the request message when the request message includes the group identifier corresponding to the business data flow and the group identifier is associated with the first business data flow group, the request message can be used to indicate adding the business data flow to the first business data flow group and/or removing the business data flow from the second business data flow group.
  • the request message when the request message includes the group identifier corresponding to the business data flow and the group identifier is associated with the second business data flow group, the request message can be used to indicate adding the business data flow to the first business data flow group and/or removing the business data flow from the second business data flow group.
  • the PCF may receive a request message sent by the AF, where the request message includes a group identifier associated with the first service data flow group, and the request message may be used to instruct to add the service data flow to the first service data flow group.
  • the PCF may receive a request message sent by the AF, where the request message includes a group identifier, and the group identifier is associated with a first business data flow group.
  • the request message may be used to indicate that the business data flow is to be added to the first business data flow group.
  • the PCF may receive a request message sent by the AF, where the request message includes a group identifier associated with the second service data flow group, and the request message may be used to indicate that the service data flow is to be removed from the second service data flow group.
  • the PCF may receive a request message sent by the AF, where the request message includes a group identifier, and the group identifier is associated with a first business data flow group.
  • the request message may be used to indicate adding the business data flow to the first business data flow group, and removing the business data flow from the second business data flow group.
  • the service data flow before receiving the request message sent by the AF, the service data flow is located in the second service data flow group, or the service data flow does not belong to any service data flow group.
  • the request message may indicate that the service data flow is removed from the second service data flow group.
  • the request message may also indicate that the service data flow is added to the first service data flow group.
  • the request message may indicate that the service data flow is added to the first service data flow group.
  • the request message includes an action indication corresponding to the service data flow.
  • the request message includes an action indication corresponding to the business data flow.
  • the PCF receives a request message sent by the AF, the request message includes a group identifier, the group identifier is associated with the first service data flow group or the second service data flow group, and the request message also includes an action indication corresponding to the service data flow.
  • the action indication may be used to indicate at least one of the following:
  • the service data flow is removed from the second service data flow group.
  • the PCF receives a request message sent by the AF, the request message includes a group identifier, the group identifier is associated with the first business data flow group, and the request message also includes an action indication corresponding to the business data flow.
  • the action indication can be used to indicate that the business data flow is added to the first business data flow group.
  • the PCF receives the request message sent by the AF, and the request message includes a group identifier corresponding to the business data flow, the group identifier is associated with the first business data flow group, and the request message also includes an action indication corresponding to the business data flow, and the action indication is used to indicate that the business data flow is added to the first business data flow group.
  • the PCF can determine to add the business data flow to the first business data flow group based on the action indication in the request message.
  • the PCF may not update the group information of the service data flow, and may determine that the service data flow belongs to the first service data flow group.
  • the PCF receives a request message sent by the AF, the request message includes a group identifier, the group identifier is associated with the second business data flow group, and the request message also includes an action indication corresponding to the business data flow.
  • the action indication can be used to indicate that the business data flow is removed from the second business data flow group.
  • the PCF may update the group information of the service data flow according to the action indication in the request message, and may determine that the service data flow does not belong to the second service data flow group.
  • the PCF may not update the group information of the service data flow, and may determine that the service data flow does not belong to the second service data flow group.
  • the request message when the PCF receives a request message sent by the AF, the request message includes a group identifier, the group identifier is associated with the first business data flow group, and the request message also includes an action indication corresponding to the business data flow. If the business data flow is in the second business data flow group before the PCF receives the request message sent by the AF, the action indication can be used to indicate that the business data flow is removed from the second business data flow group. In addition, the action indication information can also be used to indicate that the business data flow is added to the first business data flow group.
  • the PCF can update the group information of the business data flow according to the action indication in the request message, remove the business data flow from the second business data flow group and add the business data flow to the first business data flow group, and it can be determined that the business data flow belongs to the first business data flow group and does not belong to the second business data flow group.
  • the PCF receives a request message sent by the AF, the request message includes a group identifier, the group identifier is associated with the first business data flow group, and the request message also includes an action indication corresponding to the business data flow. If the business data flow does not belong to any business data flow group before the PCF receives the request message sent by the AF, the action indication can be used to indicate that the business data flow is added to the first business data flow group.
  • the PCF receives a request message sent by the AF, in which the request message includes a group identifier, the group identifier is associated with the second business data flow group, and the request message also includes an action indication corresponding to the business data flow.
  • the action identifier can be used to indicate that the business data flow is removed from the second business data flow group.
  • the group identifier when the request message includes a group identifier corresponding to a business data flow, the group identifier is associated with a second business data flow group, and the request message also includes an action indication corresponding to the business data flow, the action identifier can be used to indicate that the business data flow is removed from the second business data flow group.
  • the request message when the PCF receives the request message sent by the AF, the request message includes a group identifier corresponding to the business data flow, the group identifier is associated with the second business data flow group, and the request message also includes an action indication corresponding to the business data flow, and the action indication is used to indicate that the business data flow is removed from the second business data flow group. Regardless of which business data flow group the business data flow was previously located in, it can be determined to remove the business data flow from the second business data flow group based on the action indication in the request message.
  • the service data flow may be located in the second service data flow group, or may also be located in other service data flow groups other than the second service data flow group.
  • the PCF receives the request message sent by the AF, and may directly receive the request message sent by the AF, or may indirectly receive the request message sent by the AF.
  • the PCF receives a request message sent by the AF, including:
  • the PCF receives a request message sent by the AF, and may receive a request message sent by the AF through a network exposure function (NEF).
  • NEF network exposure function
  • the PCF receives a request message sent by the AF, and may receive a request message sent by the AF through a time sensitive communication and time synchronization function (TSCTSF).
  • TSCTSF time sensitive communication and time synchronization function
  • the PCF receives the request message sent by the AF, and may receive the request message sent by the AF through the NEF and the TSCTSF.
  • the PCF receives a request message sent by the AF, including: receiving an AF session creation request or an AF session update request sent by the AF, wherein the AF session creation request or the AF session update request includes the request message.
  • the PCF receives the request message sent by the AF, and may receive the AF session creation request sent by the AF, wherein the AF session creation request includes the request message.
  • the PCF receives the request message sent by the AF, and may receive the AF session update request sent by the AF, wherein the AF session update request includes the request message.
  • the PCF receives a request message sent by the AF, including: receiving the request message sent by the AF in at least one of the following processes:
  • the PCF receives the request message sent by the AF, and may receive the request message sent by the AF during the process of the AF session establishment request.
  • the PCF receives the request message sent by the AF, and may receive the request message sent by the AF during the process of establishing an update request for the AF session.
  • the PCF receives the request message sent by the AF, and may receive the request message sent by the AF during the process of providing service-specific parameters.
  • the PCF receives the request message sent by the AF, and may receive the request message sent by the AF in the process of setting a policy for a subsequent AF session.
  • S32 Generate or update policy and charging control PCC rules according to the request message.
  • the PCF can determine the business data flow group to which the business data flow belongs based on the request message, and then generate or update the PCC rules. As a result, it can make policy decisions and resource authorizations for the business data flow more reasonably, and ensure the consistency of policy decisions for business data flows belonging to the same business data flow group.
  • the PCF generates or updates the PCC rules according to the request message, and may further send the generated or updated PCC rules to the SMF for installation and execution.
  • SMF can generate corresponding QoS rules based on the generated or updated PCC rules sent by PCF, and send them to UPF and RAN for installation and execution.
  • the PCF receives the request message sent by the AF, and generates or updates the policy and charging control PCC rule according to the request message.
  • the PCF can determine the service data flow group to which the service data flow belongs, and generate or update the corresponding PCC rule, so that the policy decision and resource authorization for the service data flow can be made more reasonably, and the consistency of the policy decision of the service data flow belonging to the same service data flow group can be ensured.
  • Figure 4 is a flowchart of another method for managing multimodal service data flows provided by an embodiment of the present disclosure.
  • the method is executed by the PCF, as shown in Figure 4, and the method may include but is not limited to the following steps:
  • S41 Receive a request message sent by AF.
  • the request message is used to indicate at least one of the following:
  • the service data flow is removed from the second service data flow group.
  • S42 Update the first service data flow group and/or the second service data flow group according to the request message.
  • the PCF receives a request message sent by the AF, wherein the request message is used to indicate that a service data flow is to be added to the first service data flow group. Based on this, the PCF may update the first service data flow group according to the request message.
  • the PCF receives a request message sent by the AF, wherein the request message is used to indicate that the service data flow is to be removed from the second service data flow group. Based on this, the PCF may update the second service data flow group according to the request message.
  • the PCF receives a request message sent by the AF, wherein the request message is used to indicate adding a service data flow to a first service data flow group and removing a service data flow from a second service data flow group. Based on this, the PCF can update the first service data flow group and the second service data flow group according to the request message.
  • S41 to S42 can be implemented separately or in combination with any other steps in the embodiment of the present disclosure, for example, in combination with S31 to S32 in the embodiment of the present disclosure, and the embodiment of the present disclosure is not limited to this.
  • the PCF receives the request message sent by the AF, and updates the first service data flow group and/or the second service data flow group according to the request message.
  • the PCF can determine the service data flow group to which the service data flow belongs, so as to make policy decisions and resource authorization for the service data flow more reasonably when the PCC rule is generated and updated, and ensure the consistency of policy decisions for the service data flows belonging to the same service data flow group.
  • Figure 5 is a flowchart of another method for managing multimodal service data flows provided by an embodiment of the present disclosure.
  • the method is executed by the PCF, as shown in Figure 5, and the method may include but is not limited to the following steps:
  • S51 Receive a request message sent by AF.
  • the request message is used to indicate at least one of the following:
  • the service data flow is removed from the second service data flow group.
  • S52 Update the first service data flow group and/or the second service data flow group according to the request message.
  • S53 Store the updated first service data flow group and/or the second service data flow group.
  • the PCF receives a request message sent by the AF.
  • the PCF may update the first service data flow group according to the request message and store the updated first service data flow group.
  • the PCF receives a request message sent by the AF.
  • the PCF may update the second service data flow group according to the request message and store the updated second service data flow group.
  • the PCF receives a request message sent by the AF.
  • the request message is used to indicate adding a service data flow to a first service data flow group and removing a service data flow from a second service data flow group
  • the PCF can update the first service data flow group and the second service data flow group according to the request message, and store the updated first service data flow group and the second service data flow group.
  • the PCF stores the updated first service data flow group and/or the second service data flow group in at least one of the following:
  • Unstructured data storage function UDSF Unstructured data storage function
  • the PCF may store the updated first service data flow group and/or the second service data flow group locally.
  • the PCF may store the updated first business data flow group and/or the second business data flow group in a unified database (UDR).
  • UDR unified database
  • PCF may store the updated first business data stream group and/or second business data stream group in an unstructured data storage function (Unstructured Data Storage Function, UDSF).
  • UDSF Unstructured Data Storage Function
  • S51 to S53 can be implemented separately or in combination with any other steps in the embodiments of the present disclosure, for example, in combination with S31 to S32 and/or S41 to S42 in the embodiments of the present disclosure, and the embodiments of the present disclosure are not limited to this.
  • the PCF receives the request message sent by the AF, updates the first service data flow group and/or the second service data flow group according to the request message, and stores the updated first service data flow group and/or the second service data flow group.
  • the PCF can determine the service data flow group to which the service data flow belongs, and update and store the service data flow group, so as to make policy decisions and resource authorization for the service data flow more reasonably when the PCC rules are generated and updated, and ensure the consistency of policy decisions for the service data flows belonging to the same service data flow group.
  • Figure 6 is a flowchart of another method for managing multimodal service data flows provided by an embodiment of the present disclosure.
  • the method is executed by the PCF, as shown in Figure 6, and the method may include but is not limited to the following steps:
  • S61 Receive a request message sent by the AF, where the request message is used to instruct to remove the service data flow from the second service data flow group.
  • the PCF receives a request message sent by the AF, wherein the request message is used to indicate that the service data flow is removed from the second service data flow group.
  • the PCF may continue to retain or release the AF session corresponding to the request message.
  • S51 to S53 can be implemented separately or in combination with any other steps in the embodiments of the present disclosure, for example, in combination with S31 to S32 and/or S41 to S42 and/or S51 to S53 in the embodiments of the present disclosure, and the embodiments of the present disclosure are not limited to this.
  • the PCF receives a request message sent by the AF, wherein the request message is used to instruct to remove the service data flow from the second service data flow group, and to continue to retain or release the AF session corresponding to the request message.
  • the PCF can remove the service data flow from the second service data flow group according to the request message of the AF, and continue to retain or release the AF session corresponding to the request message.
  • Figure 7 is a flow chart of a method for managing multimodal service data flows provided by an embodiment of the present disclosure.
  • the method is executed by the AF, as shown in Figure 7, and the method may include but is not limited to the following steps:
  • the AF may send a request message to the PCF.
  • the request message is used to indicate at least one of the following:
  • the service data flow is removed from the second service data flow group.
  • the AF may send a request message to the PCF, wherein the request message is used to instruct to add the service data flow to the first service data flow group.
  • the AF may send information that the service data flow belongs to the first service data flow group to the PCF.
  • the AF may send a request message to the PCF, wherein the request message is used to instruct to remove the service data flow from the second service data flow group.
  • the AF may send information to the PCF that the service data flow does not belong to the second service data flow group.
  • the AF may send a request message to the PCF, wherein the request message is used to indicate that the service data flow is added to the first service data flow group and the service data flow is removed from the second service data flow group.
  • the AF may send information to the PCF that the service data flow belongs to the first service data flow group and does not belong to the second service data flow group.
  • the AF may send a request message to the PCF, and the request message may indicate to add one or more service data flows to the first service data flow group.
  • the AF may send information about the first service data flow group to which the one or more service data flows belong to the PCF.
  • the AF may send a request message to the PCF, and the request message may indicate to remove one or more service data flows from the second service data flow group.
  • the AF may send information to the PCF that the one or more service data flows do not belong to the second service data flow group.
  • the AF may send a request message to the PCF, and the request message may indicate that one or more service data flows are added to the first service data flow group and removed from the second service data flow group.
  • the AF may send information about the first service data flow group to which the one or more service data flows belong and the second service data flow group to which the one or more service data flows do not belong to to the PCF.
  • the request message includes a group identifier corresponding to the service data flow, and the group identifier is associated with the first service data flow group or the second service data flow group.
  • the AF sends a request message to the PCF, where the request message includes a group identifier corresponding to the service data flow.
  • the group identifier can be a common ID or an XRM service ID (XRM service ID), etc.
  • XRM service ID can indicate different groups through different values, and the embodiments of the present disclosure do not make specific limitations.
  • the group identifier may be associated with the first service data flow group, or the group identifier may also be associated with the second service data flow group.
  • request message is used to instruct to add the service data flow to the first service data flow group and/or to remove the service data flow from the second service data flow group.
  • the request message when the request message includes the group identifier corresponding to the business data flow and the group identifier is associated with the first business data flow group, the request message can be used to indicate adding the business data flow to the first business data flow group and/or removing the business data flow from the second business data flow group.
  • the request message when the request message includes the group identifier corresponding to the business data flow and the group identifier is associated with the second business data flow group, the request message can be used to indicate adding the business data flow to the first business data flow group and/or removing the business data flow from the second business data flow group.
  • the AF may send a request message to the PCF, where the request message includes a group identifier associated with the first service data flow group, and the request message may be used to instruct to add the service data flow to the first service data flow group.
  • the AF may send a request message to the PCF, where the request message includes a group identifier, and the group identifier is associated with the first business data flow group.
  • the request message can be used to indicate that the business data flow is to be added to the first business data flow group.
  • the AF may send a request message to the PCF, where the request message includes a group identifier associated with the second service data flow group, and the request message may be used to instruct to remove the service data flow from the second service data flow group.
  • the AF may send a request message to the PCF, where the request message includes a group identifier, and the group identifier is associated with the first business data flow group.
  • the request message can be used to indicate adding the business data flow to the first business data flow group, and removing the business data flow from the second business data flow group.
  • the service data flow is located in the second service data flow group, or the service data flow does not belong to any service data flow group.
  • the AF sends a request message to the PCF, and the request message includes a group identifier corresponding to the business data flow, and if the group identifier is associated with the first business data flow group, the request message may indicate that the business data flow is removed from the second business data flow group. In addition, the request message may also indicate that the business data flow is added to the first business data flow group.
  • the AF sends a request message to the PCF, and the request message includes a group identifier corresponding to the service data flow, and if the group identifier is associated with the first service data flow group, the request message may indicate that the service data flow is added to the first service data flow group.
  • the request message includes an action indication corresponding to the service data flow.
  • the request message includes an action indication corresponding to the business data flow.
  • the AF sends a request message to the PCF, the request message includes a group identifier, the group identifier is associated with the first service data flow group or the second service data flow group, and the request message also includes an action indication corresponding to the service data flow.
  • the action indication may be used to indicate at least one of the following:
  • the corresponding service data flow is removed from the second service data flow group.
  • the AF sends a request message to the PCF, the request message includes a group identifier, the group identifier is associated with the first business data flow group, and the request message also includes an action indication corresponding to the business data flow.
  • the action indication can be used to indicate that the business data flow is added to the first business data flow group.
  • AF sends a request message to PCF, and the request message includes a group identifier corresponding to the business data flow, the group identifier is associated with the first business data flow group, and the request message also includes an action indication corresponding to the business data flow, and the action indication is used to indicate that the business data flow is added to the first business data flow group.
  • PCF can determine to add the business data flow to the first business data flow group based on the action indication in the request message.
  • the PCF may not update the group information of the service data flow, and may determine that the service data flow belongs to the first service data flow group.
  • the AF sends a request message to the PCF, the request message includes a group identifier, the group identifier is associated with the second business data flow group, and the request message also includes an action indication corresponding to the business data flow.
  • the action indication can be used to indicate that the business data flow is removed from the second business data flow group.
  • the PCF may update the group information of the service data flow according to the action indication in the request message, and may determine that the service data flow does not belong to the second service data flow group.
  • the PCF may not update the group information of the service data flow, and may determine that the service data flow does not belong to the second service data flow group.
  • the AF sends a request message to the PCF
  • the request message includes a group identifier
  • the group identifier is associated with the first business data flow group
  • the request message also includes an action indication corresponding to the business data flow. If the business data flow is in the second business data flow group before the AF sends the request message to the PCF, the action indication can be used to indicate that the business data flow is removed from the second business data flow group. In addition, the action indication information can also be used to indicate that the business data flow is added to the first business data flow group.
  • the PCF can update the group information of the business data flow according to the action indication in the request message, remove the business data flow from the second business data flow group and add the business data flow to the first business data flow group, and it can be determined that the business data flow belongs to the first business data flow group and does not belong to the second business data flow group.
  • the AF sends a request message to the PCF
  • the request message includes a group identifier
  • the group identifier is associated with the first business data flow group
  • the request message also includes an action indication corresponding to the business data flow. If the business data flow does not belong to any business data flow group before the AF sends the request message to the PCF, the action indication can be used to indicate that the business data flow is added to the first business data flow group.
  • the AF sends a request message to the PCF, in which the group identifier is associated with the second business data flow group. If the request message also includes an action indication corresponding to the business data flow, the action identifier can be used to indicate that the business data flow is removed from the second business data flow group.
  • the group identifier when the request message includes a group identifier corresponding to a business data flow, the group identifier is associated with a second business data flow group, and the request message also includes an action indication corresponding to the business data flow, the action identifier can be used to indicate that the business data flow is removed from the second business data flow group.
  • the request message when AF sends a request message to PCF, the request message includes a group identifier corresponding to the business data flow, the group identifier is associated with the second business data flow group, and the request message also includes an action indication corresponding to the business data flow, and the action indication is used to indicate that the business data flow is removed from the second business data flow group.
  • PCF can determine to remove the business data flow from the second business data flow group based on the action indication in the request message.
  • the service data flow may be located in the second service data flow group, or may be located in other service data flow groups other than the second service data flow group.
  • the AF sends a request message to the PCF, and may directly send the request message to the PCF, or may indirectly send the request message to the PCF.
  • the AF sends a request message to the PCF, including:
  • the AF sends a request message to the PCF, and may send the request message to the PCF through the NEF.
  • the AF sends a request message to the PCF, and may send the request message to the PCF via the TSCTSF.
  • the AF sends a request message to the PCF, and may send the request message to the PCF through the NEF and the TSCTSF.
  • the AF sending a request message to the PCF includes: sending an AF session creation request or an AF session update request to the PCF, wherein the AF session creation request or the AF session update request includes the request message. .
  • the AF sends a request message to the PCF, and may send an AF session creation request to the PCF, wherein the AF session creation request includes the request message.
  • the AF sends a request message to the PCF, and may send an AF session update request to the PCF, wherein the AF session update request includes the request message.
  • the AF sends a request message to the PCF, and the request message can be sent to the PCF through the following process:
  • a process such as: The AF provides the RT latency requirement to the PCF during AF session with required QoS procedure.
  • a process such as: AF session with required QoS update procedure.
  • a process such as the Service specific parameter provisioning process.
  • a process such as: Set a policy for a future AF session process.
  • the AF sends a request message to the PCF, including: sending the request message to the PCF in at least one of the following processes:
  • the AF sends a request message to the PCF, and the request message may be sent to the PCF during the process of the AF session establishment request.
  • the AF sends a request message to the PCF, and the request message may be sent to the PCF during the process of establishing an update request for the AF session.
  • the AF sends a request message to the PCF, and the request message may be sent to the PCF during the process of providing service-specific parameters.
  • the AF sends a request message to the PCF, and the request message may be sent to the PCF in the process of setting a policy for a subsequent AF session.
  • the AF sends a request message to the PCF, and the request message is used to instruct to add the service data flow to the first service data flow group and/or remove the service data flow from the second service data flow group.
  • the AF can send information to the PCF to determine the service data flow group to which the service data flow belongs, and the PCF can generate or update the corresponding PCC rules according to the information of the service data flow group to which the service data flow belongs, and can make policy decisions and resource authorization for the service data flow more reasonably, so as to ensure the consistency of policy decisions of the service data flows belonging to the same service data flow group.
  • Figure 8 is a flowchart of another method for managing multimodal service data flows provided by an embodiment of the present disclosure.
  • the method is executed by the AF, as shown in Figure 8, and the method may include but is not limited to the following steps:
  • S81 Send a request message to the PCF, where the request message is used to instruct to remove the service data flow from the second service data flow group.
  • the AF sends a request message to the PCF, wherein the request message is used to indicate that the service data flow is removed from the second service data flow group.
  • the AF may continue to retain or release the AF session corresponding to the request message.
  • S81 to S82 can be implemented separately or in combination with any other steps in the embodiments of the present disclosure, for example, in combination with S71 in the embodiments of the present disclosure, and the embodiments of the present disclosure are not limited to this.
  • the AF sends a request message to the PCF, wherein the request message is used to instruct to remove the service data flow from the second service data flow group, and to continue to retain or release the AF session corresponding to the request message.
  • the AF can send a request message to the PCF, instructing to remove the service data flow from the second service data flow group, and to continue to retain or release the AF session corresponding to the request message.
  • the embodiments of the present disclosure provide the following exemplary embodiments.
  • AF sends an AF session resource request, for example, Nnef_AFsessionWithQoS_Create request can be used to create an AF request.
  • the request message can carry a common ID or an XRM service ID, and can also carry an action indication, which is used to indicate increasing or decreasing the number of SDFs in the group.
  • common ID identifies the XRM service data flow group, and SDFs carrying the same common ID belong to the same XRM service group.
  • it carries UE address/UE identifier (UE address/UE Identifier), AF identifier application ID (AF Identifier Application ID), data network name (data network name, DNN), single network slice selection assistance information (single network slice selection assistance information, S-NSSAI), QoS parameters and other corresponding information.
  • the NEF authorizes the AF request. If it is an untrusted AF, the AF request can be sent to the PCF through the NEF.
  • the NEF can perform relevant mappings, including mapping of the XRM service (AF-Service-Identifier) to the DNN and S-NSSAI, mapping of external applications to core network (CN) application identifiers; and mapping of external UE identifiers to UE identifiers within the CN based on UDM contract information (such as SUPI), and mapping of external to internal XRM service group identifiers based on UDM contract information).
  • XRM service AF-Service-Identifier
  • CN core network
  • UDM contract information such as SUPI
  • UDM contract information such as SUPI
  • the NEF authorizes the AF request and determines whether to invoke the TSCTSF or to directly contact the PCF depending on the parameters provided by the AF. These signaling steps are identical to TS 23.502 clause 4.15.6.6 for setting up an AF session with the required QoS procedures. (These signalling steps are the same as for TS 23.502 clause 4.15.6.6 for setting up an AF session with required QoS procedure.)
  • the PCF receives the AF provided attributes from NEF or from TSCTSF. NEF triggers Npcf_PolicyAuthorization_Create request and sends the AF request to PCF, carrying Common ID (or XRM service ID) and action indication for PCF policy decision reference.
  • the PCF makes a policy decision.
  • the PCF may determine that the updated or new policy information need to be sent to the SMF.
  • the PCF receives the AF session (create/update) request, considering common ID (or XRM service ID) and action indication, and can generate or update the PCC rule;
  • PCF can update the group information associated with the common ID
  • the updated group information is stored locally or in the UDR or UDM or UDSF.
  • the action indication can be carried explicitly, or the original common ID in the corresponding SDF in the AF request can be deleted or replaced with a different common ID to indicate that the SDF is removed from the original group.
  • the corresponding AF session of the SDF removed from the original common ID association group can continue to be retained or released;
  • PCF can send the generated/updated corresponding PCC rules to SMF for installation and execution; SMF can generate corresponding QoS rules and send them to UPF and RAN for installation and execution. This part can refer to the description in the relevant technology).
  • the PCF responds to the NEF a Npcf_Policy Authorization_Create response.
  • the NEF sends a Nnef_AFsessionWithQoS_Create response message to the AF. It carries the result, indicating whether the request is authorized.
  • the PCF initiates SM Policy Association Modification Request (PCC rule (QoS monitoring policy)) to the SMF.
  • PCC rule QoS monitoring policy
  • the SMF Based on the QoS monitoring policy for measurement from the PCF, the SMF generates the QoS Monitoring configuration for UPF (and for RAN, if needed), as described in step 4.
  • the SMF replies SM Policy Association Modification Response to the PCF.
  • the SMF initiates N4 Session Modification Request (QoS Monitoring configuration) to the UPF.
  • the UPF Upon reception of QoS Monitoring configuration, the UPF enables the measurement and report. The UPF(s) respond to the SMF.
  • the SMF invokes Namf_Communication_N1N2MessageTransfer([N2 SM information](PDU Session ID,QFI(s),QoS Profile(s),QoS Monitoring configuration),N1 SM container)).
  • the AMF may send N2([N2 SM information received from SMF],NAS message(PDU Session ID,N1 SM container(PDU Session Modification Command))) Message to the (R)AN.
  • N2 [N2 SM information received from SMF],NAS message(PDU Session ID,N1 SM container(PDU Session Modification Command))
  • the RAN Upon reception of QoS Monitoring configuration, the RAN enables the event measurement and report.
  • the (R)AN may acknowledge N2 PDU Session Request by sending a N2 PDU Session Ack Message to the AMF.
  • the AMF forwards the N2 SM information received from the AN to the SMF via Nsmf_PDUSession_UpdateSMContext service operation.
  • the SMF may update the N4 session of the UPF(s)that are involved by the PDU Session Modification by sending N4 Session Modification Request message to the UPF.
  • the PCF receives the QoS Monitoring report, it will notify the AF.
  • the SMF may update the N4 session of the UPF(s)that are involved by the PDU Session Modification by sending N4 Session Modification Request message to the UPF.
  • the PCF receives the QoS Monitoring report, it will notify the AF.
  • AF provides XRM service request to PCF.
  • This embodiment describes 1) Setting up an AF session with required QoS procedure. It can also be provided through the following process:
  • the embodiment of the present disclosure is that AF provides a common ID (or XRM service ID) to PCF through NEF, and carries an action indication at the same time, wherein the indication indicates increasing or decreasing the number of SDFs in the group, and supports PCF's authorization of related data flows of the XRM service.
  • AF provides a common ID (or XRM service ID) to PCF through NEF, and carries an action indication at the same time, wherein the indication indicates increasing or decreasing the number of SDFs in the group, and supports PCF's authorization of related data flows of the XRM service.
  • step 0 some or all UEs related to the XRM service or multimodal data service have registered with the network and selected PCF to complete the AM session association.
  • PCF can subscribe to the change notification of the contract information related to the XRM service or multimodal data Service from the UDM according to the policy and QoS requirements of the XRM service.
  • AF can trigger Nnef_XRMServiceParameter service and create AF request, which contains XRM service ID, common ID, UE address or ID, etc.
  • AF carries common ID (or XRM service ID) and action indication in the request message, which indicates increasing or decreasing the number of SDFs in the group.
  • AF provides XRM service or multiple data service specific parameters to single or multiple UEs related to the service through Nnef_XRMServiceParameter service.
  • the information sent by AF includes common ID, service parameters, UE/UE group and event subscription (Service Parameters, UE/Group UE, and Subscription to events). Specifically:
  • Service Parameters information on the AF guidance for XRM service or multimodal data Service related Policy and QoS determination. Parameters such as a list of rules that associate XRM service or multiple data Service application traffic, UE policy, common ID or Group ID, or combination of DNN and S-NSSAI, SSC mode, selection priority of corresponding rule (e.g. Alternative QoS parameter priority, corresponding location or Time Window priority, corresponding inclusion type or routing selection priority, etc.).
  • the AF may subscribe to notifications about the outcome of the execution and change of the SM policy, AM policy or UE Policy; or event subscription of media data stream related to XRM service, e.g. Date rate, Latency.
  • NEF can send the request to NEF.
  • NEF authorizes the AF request.
  • NEF performs relevant mappings, including mapping of XRM service or XRM data Service (AF-Service-Identifier) to DNN and S-NSSAI, mapping of external application to CN application identifier; and mapping of external UE identifier to UE identifier within CN (such as SUPI) based on UDM contract information, as well as mapping of external to internal XRM service group identifier according to UDM contract information;
  • NEF can store the requested information in UDR (for example, as business characteristic parameter information storage in Application Data).
  • NEF may improve the corresponding business parameters based on local configuration.
  • NEF can combine the subscription information to confirm whether the requested service features are authorizable for the XRM service or multimodal data Service of a single UE or a group of multiple UEs and store the corresponding parameters in the UDR.
  • the NEF transmits the relevant service parameters to the PCF, and performs the corresponding authorization in each PCF, as well as the decision or update of policies and rules.
  • the PCF stores the corresponding information in the UDR based on the authorization result of the request.
  • the subscription data (Special QoS profile) of UE group members can be associated through XRM service Indication or Group ID/Common ID;
  • Consumers such as AF or PCF can subscribe to related XRM service or multimodal data related event triggers through NEF, such as QoS monitoring report, service QoS update, UE relocation, PCF change, etc.
  • NEF such as QoS monitoring report, service QoS update, UE relocation, PCF change, etc.
  • XRM service or multimodal data related event trigger such as QoS monitoring report, Service QoS update, UE relocation, PCF change, etc.
  • AF or PCF, etc. obtains corresponding notifications by receiving NEF reports; and executes subsequent application requirements or updates of QoS rules.
  • NEF returns a create request response message to AF.
  • step 0 the PCF executes the subscription information update notification after the UE is registered, the subsequent process is executed because the AF requests to update the UDR subscription information
  • PCF receives notification of contract information change from UDR.
  • PCF updates the group information associated with the common ID; optionally, the updated group information is stored locally or in UDR, UDM or UDSF.
  • the action indication can be carried explicitly, or the original common ID in the corresponding SDF in the AF request can be deleted or replaced with a different common ID to indicate that the SDF is removed from the original group.
  • the corresponding AF session of the SDF removed from the original common ID association group can continue to be retained or released;
  • PCF sends UE policy to UE.
  • the PCF sends the relevant execution results to the AF through the NEF.
  • the PCF updates the changes to the UDR, triggering the serving PCF of other UEs related to the XRM service group to execute policy changes and collaboration.
  • NEF After receiving the notification, NEF first performs mapping of internal and external related parameters, and then reports the relevant information to AF.
  • each device includes a hardware structure and/or software module corresponding to the execution of each function.
  • the present disclosure can be implemented in the form of hardware or a combination of hardware and computer software. Whether a function is executed in the form of hardware or computer software driving hardware depends on the specific application and design constraints of the technical solution. Professional and technical personnel can use different methods to implement the described functions for each specific application, but such implementation should not be considered to exceed the scope of the present disclosure.
  • the communication device 1 shown in Figure 11 may include a transceiver module 11 and a processing module 12.
  • the transceiver module may include a sending module and/or a receiving module, the sending module is used to implement a sending function, the receiving module is used to implement a receiving function, and the transceiver module may implement a sending function and/or a receiving function.
  • the communication device 1 is arranged at the PCF side and comprises a transceiver module 11 and a processing module 12 .
  • the transceiver module 11 is configured to receive a request message sent by the application function AF, wherein the request message is used to indicate at least one of the following:
  • the processing module 12 is configured to generate or update a policy and charging control PCC rule according to the request message.
  • the request message includes a group identifier corresponding to the service data flow, and the group identifier is associated with the first service data flow group or the second service data flow group.
  • the request message includes an action indication corresponding to the service data flow.
  • the action indication is used to indicate at least one of the following:
  • the service data flow is removed from the second service data flow group.
  • the service data flow before receiving the request message sent by the AF, is located in the second service data flow group, or does not belong to any service data flow group.
  • the action identifier is used to indicate that the service data flow is removed from the second service data flow group.
  • the processing module 12 is further configured to update the first service data flow group and/or the second service data flow group according to the request message.
  • processing module 12 is further configured to store the updated first service data flow group and/or the second service data flow group in at least one of the following:
  • Unstructured data storage function UDSF Unstructured data storage function
  • the processing module 12 is further configured to, in response to the request message indicating that the service data flow is to be removed from the second service data flow group, continue to reserve or release the AF session corresponding to the request message.
  • the transceiver module 11 is further configured to receive a request message sent by the AF through the network open function NEF; or receive a request message sent by the AF through the time-sensitive communication and time synchronization function TSCTSF; or receive a request message sent by the AF through NEF and TSCTSF.
  • the transceiver module 11 is further configured to receive an AF session creation request or an AF session update request sent by the AF, wherein the AF session creation request or the AF session update request includes a request message.
  • the transceiver module 11 is further configured to receive the request message sent by the AF in at least one of the following processes:
  • the communication device 1 is arranged at the AF side and comprises a transceiver module 11 and a processing module 12 .
  • the transceiver module 11 is configured to send a request message to the PCF, wherein the request message is used to indicate at least one of the following:
  • the service data flow is removed from the second service data flow group.
  • the request message includes a group identifier corresponding to the service data flow, and the group identifier is associated with the first service data flow group or the second service data flow group.
  • the request message includes an action indication corresponding to the service data flow.
  • the action indication is used to indicate at least one of the following:
  • the service data flow is removed from the second service data flow group.
  • the service data flow before sending the request message to the PCF, the service data flow is located in the second service data flow group, or does not belong to any service data flow group.
  • the action identifier is used to indicate that the service data flow is removed from the second service data flow group.
  • the processing module 12 is configured to, in response to a request message for indicating that the service data flow is to be removed from the second service data flow group, continue to reserve or release the AF session corresponding to the request message.
  • the transceiver module 11 is further configured to send a request message to the PCF via the NEF; or send a request message to the PCF via the TSCTSF; or send a request message to the PCF via the NEF and the TSCTSF.
  • the transceiver module 11 is further configured to send an AF session creation request or an AF session update request to the PCF, wherein the AF session creation request or the AF session update request includes a request message.
  • the transceiver module 11 is further configured to send the request message to the PCF in at least one of the following processes:
  • the communication device 1 provided in the above embodiments of the present disclosure achieves the same or similar beneficial effects as the multimodal service data flow management method provided in some of the above embodiments, which will not be described in detail here.
  • FIG 12 is a structural diagram of another communication device 1000 provided in an embodiment of the present disclosure.
  • the communication device 1000 can be a terminal device, an SMF, or a PCF.
  • the device can be used to implement the method described in the above method embodiment, and the details can be referred to the description in the above method embodiment.
  • the communication device 1000 may include one or more processors 1001.
  • the processor 1001 may be a general-purpose processor or a dedicated processor, etc. For example, it may be a baseband processor or a central processing unit.
  • the baseband processor may be used to process the communication protocol and communication data
  • the central processing unit may be used to control the communication device (such as a base station, a baseband chip, a terminal device, a terminal device chip, a DU or a CU, etc.), execute a computer program, and process the data of the computer program.
  • the communication device 1000 may further include one or more memories 1002, on which a computer program 1004 may be stored, and the memory 1002 executes the computer program 1004 so that the communication device 1000 executes the method described in the above method embodiment.
  • data may also be stored in the memory 1002.
  • the communication device 1000 and the memory 1002 may be provided separately or integrated together.
  • the communication device 1000 may further include a transceiver 1005 and an antenna 1006.
  • the transceiver 1005 may be referred to as a transceiver unit, a transceiver, or a transceiver circuit, etc., for implementing a transceiver function.
  • the transceiver 1005 may include a receiver and a transmitter, the receiver may be referred to as a receiver or a receiving circuit, etc., for implementing a receiving function; the transmitter may be referred to as a transmitter or a transmitting circuit, etc., for implementing a transmitting function.
  • the communication device 1000 may further include one or more interface circuits 1007.
  • the interface circuit 1007 is used to receive code instructions and transmit them to the processor 1001.
  • the processor 1001 executes the code instructions to enable the communication device 1000 to execute the method described in the above method embodiment.
  • the communication device 1000 is a PCF
  • the transceiver 1005 is used to execute S31 in Figure 3; S41 in Figure 4; S51 in Figure 5; S61 in Figure 6;
  • the processor 1001 is used to execute S32 in Figure 3; S42 in Figure 4; S52 and S53 in Figure 5; S62 in Figure 6.
  • the communication device 1000 is AF: the transceiver 1005 is used to execute S71 in FIG. 7 ; S81 in FIG. 8 ; and the processor 1001 is used to execute S82 in FIG. 8 .
  • the processor 1001 may include a transceiver for implementing receiving and sending functions.
  • the transceiver may be a transceiver circuit, an interface, or an interface circuit.
  • the transceiver circuit, interface, or interface circuit for implementing the receiving and sending functions may be separate or integrated.
  • the above-mentioned transceiver circuit, interface, or interface circuit may be used for reading and writing code/data, or the above-mentioned transceiver circuit, interface, or interface circuit may be used for transmitting or delivering signals.
  • the processor 1001 may store a computer program 1003, which runs on the processor 1001 and enables the communication device 1000 to perform the method described in the above method embodiment.
  • the computer program 1003 may be fixed in the processor 1001, in which case the processor 1001 may be implemented by hardware.
  • the communication device 1000 may include a circuit that can implement the functions of sending or receiving or communicating in the aforementioned method embodiments.
  • the processor and transceiver described in the present disclosure may be implemented in an integrated circuit (IC), an analog IC, a radio frequency integrated circuit RFIC, a mixed signal IC, an application specific integrated circuit (ASIC), a printed circuit board (PCB), an electronic device, etc.
  • the processor and transceiver may also be manufactured using various IC process technologies, such as complementary metal oxide semiconductor (CMOS), N-type metal oxide semiconductor (NMOS), P-type metal oxide semiconductor (positive channel metal oxide semiconductor, PMOS), bipolar junction transistor (BJT), bipolar CMOS (BiCMOS), silicon germanium (SiGe), gallium arsenide (GaAs), etc.
  • CMOS complementary metal oxide semiconductor
  • NMOS N-type metal oxide semiconductor
  • PMOS P-type metal oxide semiconductor
  • BJT bipolar junction transistor
  • BiCMOS bipolar CMOS
  • SiGe silicon germanium
  • GaAs gallium arsenide
  • the communication device described in the above embodiment may be a terminal device, an SMF, a PCF, or a core network, but the scope of the communication device described in the present disclosure is not limited thereto, and the structure of the communication device may not be limited by FIG. 12.
  • the communication device may be an independent device or may be part of a larger device.
  • the communication device may be:
  • the IC set may also include a storage component for storing data and computer programs;
  • ASIC such as modem
  • FIG. 13 is a structural diagram of a chip provided in an embodiment of the present disclosure.
  • the chip 1100 includes a processor 1101 and an interface 1103.
  • the number of the processor 1101 may be one or more, and the number of the interface 1103 may be multiple.
  • the interface 1103 is used to receive code instructions and transmit them to the processor.
  • the processor 1101 is used to run code instructions to execute the multimodal service data flow management method as described in some of the above embodiments.
  • the interface 1103 is used to receive code instructions and transmit them to the processor.
  • the processor 1101 is used to run code instructions to execute the multimodal service data flow management method as described in some of the above embodiments.
  • the interface 1103 is used to receive code instructions and transmit them to the processor.
  • the processor 1101 is used to run code instructions to execute the multimodal service data flow management method as described in some of the above embodiments.
  • the chip 1100 further includes a memory 1102, and the memory 1102 is used to store necessary computer programs and data.
  • An embodiment of the present disclosure also provides a management system for multimodal service data flows, the system comprising the communication device as a terminal device, the communication device of SMF and the communication device as PCF in the aforementioned embodiment of FIG. 11 , or the system comprising the communication device as a terminal device, the communication device of SMF and the communication device as PCF in the aforementioned embodiment of FIG. 12 .
  • the present disclosure also provides a readable storage medium having instructions stored thereon, which implement the functions of any of the above method embodiments when executed by a computer.
  • the present disclosure also provides a computer program product, which implements the functions of any of the above method embodiments when executed by a computer.
  • the computer program product includes one or more computer programs.
  • the computer can be a general-purpose computer, a special-purpose computer, a computer network, or other programmable device.
  • the computer program can be stored in a computer-readable storage medium, or transmitted from one computer-readable storage medium to another computer-readable storage medium.
  • the computer program can be transmitted from a website site, computer, server or data center by wired (e.g., coaxial cable, optical fiber, digital subscriber line (digital subscriber line, DSL)) or wireless (e.g., infrared, wireless, microwave, etc.) mode to another website site, computer, server or data center.
  • the computer-readable storage medium can be any available medium that can be accessed by a computer or a data storage device such as a server or data center that includes one or more available media integrated.
  • the available medium may be a magnetic medium (e.g., a floppy disk, a hard disk, a magnetic tape), an optical medium (e.g., a high-density digital video disc (DVD)), or a semiconductor medium (e.g., a solid state disk (SSD)), etc.
  • a magnetic medium e.g., a floppy disk, a hard disk, a magnetic tape
  • an optical medium e.g., a high-density digital video disc (DVD)
  • DVD high-density digital video disc
  • SSD solid state disk
  • At least one in the present disclosure can also be described as one or more, and a plurality can be two, three, four or more, which is not limited in the present disclosure.
  • the technical features in the technical feature are distinguished by “first”, “second”, “third”, “A”, “B”, “C” and “D”, etc., and there is no order of precedence or size between the technical features described by the “first”, “second”, “third”, “A”, “B”, “C” and “D”.
  • “A and/or B” includes the following three combinations: only A, only B, and a combination of A and B.

Landscapes

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

Abstract

本公开实施例公开了一种多模态业务数据流的管理方法和装置，该方法包括：PCF接收AF发送的请求消息，根据请求消息，生成或更新策略与计费控制PCC规则。由此，PCF可以确定业务数据流所属的业务数据流组，并生成或更新对应的PCC规则，可以更合理的为业务数据流进行策略决策和资源授权，保证属于同一业务数据流组的业务数据流的策略决策的一致性。

Description

多模态业务数据流的管理方法和装置 技术领域
本公开涉及通信技术领域，尤其涉及一种多模态业务数据流的管理方法和装置。
背景技术
移动媒体类服务、云AR(augmented reality，增强现实)/VR(virtual reality，虚拟现实)等XR(extended reality，扩展现实)业务、云游戏、基于视频的机器或无人机远程控制等业务，预计将为5G网络贡献越来越高的流量。XR业务还涉及多模态数据流，这些多模态数据，可以是描述同一业务或应用的从同一个设备或不同设备(包括传感器)输入的数据，这些数据可能会输出到一个或多个目的设备终端。多模态数据中的各数据流往往具有相关性，比如音频流和视频流的同步，触觉和视觉的同步等。
发明内容
本公开实施例提供一种多模态业务数据流的管理方法和装置，PCF可以确定业务数据流所属的业务数据流组，并生成或更新对应的PCC规则，可以更合理的为业务数据流进行策略决策和资源授权，保证属于同一业务数据流组的业务数据流的策略决策的一致性。
第一方面，本公开实施例提供一种多模态业务数据流的管理方法，由PCF执行，包括：PCF接收AF发送的请求消息，根据请求消息，生成或更新策略与计费控制PCC规则。
在该技术方案中，PCF接收AF发送的请求消息，根据请求消息，生成或更新策略与计费控制PCC规则。由此，PCF可以确定业务数据流所属的业务数据流组，并生成或更新对应的PCC规则，可以更合理的为业务数据流进行策略决策和资源授权，保证属于同一业务数据流组的业务数据流的策略决策的一致性。
第二方面，本公开实施例提供另一种多模态业务数据流的管理方法，由AF执行，包括：向PCF发送请求消息，其中，请求消息用于指示将业务数据流添加至第一业务数据流组和/或将业务数据流从第二业务数据流组中移除。
第三方面，本公开实施例提供一种通信装置，该通信装置具有实现上述第一方面所述的方法中PCF的部分或全部功能，比如通信装置的功能可具备本公开中的部分或全部实施例中的功能，也可以具备单独实施本公开中的任一个实施例的功能。所述功能可以通过硬件实现，也可以通过硬件执行相应的软件实现。所述硬件或软件包括一个或多个与上述功能相对应的单元或模块。
所述通信装置包括：收发模块，被配置为接收AF发送的请求消息，处理模块，被配置为根据请求消息，生成或更新策略与计费控制PCC规则。。
第四方面，本公开实施例提供另一种通信装置，该通信装置具有实现上述第二方面所述的方法示例中AF的部分或全部功能，比如通信装置的功能可具备本公开中的部分或全部实施例中的功能，也可以具备单独实施本公开中的任一个实施例的功能。所述功能可以通过硬件实现，也可以通过硬件执行相应的软件实现。所述硬件或软件包括一个或多个与上述功能相对应的单元或模块。
所述通信装置包括：收发模块，被配置为向PCF发送请求消息，其中，请求消息用于指示将业务数据流添加至第一业务数据流组和/或将业务数据流从第二业务数据流组中移除。
第五方面，本公开实施例提供一种通信装置，该通信装置包括处理器，当该处理器调用存储器中的计算机程序时，执行上述第一方面所述的方法。
第六方面，本公开实施例提供一种通信装置，该通信装置包括处理器，当该处理器调用存储器中的计算机程序时，执行上述第二方面所述的方法。
第七方面，本公开实施例提供一种通信装置，该通信装置包括处理器和存储器，该存储器中存储有计算机程序；所述处理器执行该存储器所存储的计算机程序，以使该通信装置执行上述第一方面所述的方法。
第八方面，本公开实施例提供一种通信装置，该通信装置包括处理器和存储器，该存储器中存储有计算机程序；所述处理器执行该存储器所存储的计算机程序，以使该通信装置执行上述第二方面所述的方法。
第九方面，本公开实施例提供一种通信装置，该装置包括处理器和接口电路，该接口电路用于接收代码指令并传输至该处理器，该处理器用于运行所述代码指令以使该装置执行上述第一方面所述的方法。
第十方面，本公开实施例提供一种通信装置，该装置包括处理器和接口电路，该接口电路用于接收代码指令并传输至该处理器，该处理器用于运行所述代码指令以使该装置执行上述第二方面所述的方法。
第十一方面，本公开实施例提供一种通信系统，该系统包括第三方面所述的通信装置和第四方面所述的通信装置，或者，该系统包括第五方面所述的通信装置和第六方面所述的通信装置，或者，该系统包括第七方面所述的通信装置和第八方面所述的通信装置，或者，该系统包括第九方面所述的通信装置和第十方面所述的通信装置。
第十二方面，本发明实施例提供一种计算机可读存储介质，用于储存为上述PCF所用的指令，当所述指令被执行时，使所述PCF执行上述第一方面所述的方法。
第十三方面，本发明实施例提供一种可读存储介质，用于储存为上述AF所用的指令，当所述指令被执行时，使所述AF执行上述第二方面所述的方法。
第十四方面，本公开还提供一种包括计算机程序的计算机程序产品，当其在计算机上运行时，使得计算机执行上述第一方面所述的方法。
第十五方面，本公开还提供一种包括计算机程序的计算机程序产品，当其在计算机上运行时，使得计算机执行上述第二方面所述的方法。
第十六方面，本公开提供一种芯片系统，该芯片系统包括至少一个处理器和接口，用于支持PCF实现第一方面所涉及的功能，例如，确定或处理上述方法中所涉及的数据和信息中的至少一种。在一种可能的设计中，所述芯片系统还包括存储器，所述存储器，用于保存PCF必要的计算机程序和数据。该芯片系统，可以由芯片构成，也可以包括芯片和其他分立器件。
第十七方面，本公开提供一种芯片系统，该芯片系统包括至少一个处理器和接口，用于支持AF实现第二方面所涉及的功能，例如，确定或处理上述方法中所涉及的数据和信息中的至少一种。在一种可能的设计中，所述芯片系统还包括存储器，所述存储器，用于保存AF必要的计算机程序和数据。该芯片系统，可以由芯片构成，也可以包括芯片和其他分立器件。
第十八方面，本公开提供一种计算机程序，当其在计算机上运行时，使得计算机执行上述第一方面所述的方法。
第十九方面，本公开提供一种计算机程序，当其在计算机上运行时，使得计算机执行上述第二方面所述的方法。
附图说明
为了更清楚地说明本公开实施例或背景技术中的技术方案，下面将对本公开实施例或背景技术中所需要使用的附图进行说明。
图1是本公开实施例提供的一种通信网络架构的示意图；
图2是本公开实施例提供的另一种通信网络架构的示意图；
图3是本公开实施例提供的一种多模态业务数据流的管理方法的流程图；
图4是本公开实施例提供的另一种多模态业务数据流的管理方法的流程图；
图5是本公开实施例提供的又一种多模态业务数据流的管理方法的流程图；
图6是本公开实施例提供的又一种多模态业务数据流的管理方法的流程图；
图7是本公开实施例提供的又一种多模态业务数据流的管理方法的流程图；
图8是本公开实施例提供的又一种多模态业务数据流的管理方法的流程图；
图9是本公开实施例提供的又一种多模态业务数据流的管理方法的流程图；
图10是本公开实施例提供的又一种多模态业务数据流的管理方法的流程图；
图11是本公开实施例提供的一种通信装置的结构图；
图12是本公开实施例提供的另一种通信装置的结构图；
图13是本公开实施例提供的一种芯片的结构图。
具体实施方式
为了更好的理解本公开实施例公开的一种多模态业务数据流的管理方法和装置，下面首先对本公开实施例适用的通信系统进行描述。
这里将详细地对示例性实施例进行说明，其示例表示在附图中。下面的描述涉及附图时除非另有表示，不同附图中的相同数字表示相同或相似的要素。以下示例性实施例中所描述的实施方式并不代表与本公开相一致的所有实施方式。相反，它们仅是与如所附权利要求书中所详述的、本公开的一些方面相一致的装置和方法的例子。
在本公开使用的术语是仅仅出于描述特定实施例的目的，而非旨在限制本公开。在本公开和所附权利要求书中所使用的单数形式的“一种”、“所述”和“该”也是旨在包括多数形式，除非上下文清楚地表示其它含义。还应当理解，本文中使用的术语“和/或”是指并包含一个或多个相关联的列出项目的任何或所有可能组合。
应当理解，尽管在本公开可能采用术语第一、第二、第三等来描述各种信息，但这些信息不应限于这些术语。这些术语仅用来将同一类型的信息彼此区分开。例如，在不脱离本公开范围的情况下，第一信息也可以被称为第二信息，类似地，第二信息也可以被称为第一信息。取决于语境，例如，在此所使用的词语“如果”可以被解释成为“在……时”或“当……时”或“响应于确定”。
需要说明的是，本公开所涉及的信息(包括但不限于用户设备信息、用户个人信息等)、数据(包括但不限于用于分析的数据、存储的数据、展示的数据等)以及信号，均为经用户授权或者经过各方充分授权的，且相关数据的收集、使用和处理需要遵守相关国家和地区的相关法律法规和标准。
应理解，本公开各个实施例的技术方案，按照接入制式来划分可以应用于各种通信系统，例如：全球移动通讯系统(Global System of Mobile communication，GSM)，码分多址(Code Division Multiple Access，CDMA)系统，宽带码分多址(Wideband CodeDivision Multiple Access Wireless，WCDMA)，通用分组无线业务(General PacketRadio Service，GPRS)，长期演进(Long Term Evolution，LTE)，LTE频分双工(FrequencyDivision Duplex，FDD)系统、LTE时分双工(Time Division Duplex，TDD)、通用移动通信系统(Universal Mobile Telecommunication System，UMTS)、无线蜂窝网络系统、5G系统以及未来的通信系统等。
参见图1和图2所示，为本公开实施例中两种可能的通信网络架构的示意图。通信网络架构中可以包括三部分，分别为终端设备部分、数据网络(data network，DN)和运营商网络部分。
其中，UE(user equipment，终端设备)是用户侧的一种用于接收或发射信号的实体，如手机。终端设备也可以称为终端设备(terminal)、用户设备、移动台(mobile station，MS)、移动终端设备(mobile terminal，MT)等。终端设备可以是具备通信功能的汽车、智能汽车、手机(mobile phone)、穿戴式设备、平板电脑(Pad)、带无线收发功能的电脑、虚拟现实(virtual reality，VR)终端设备、增强现实(augmented reality，AR)终端设备、工业控制(industrial control)中的无线终端设备、无人驾驶(self-driving)中的无线终端设备、远程手术(remote medical surgery)中的无线终端设备、智能电网(smart grid)中的无线终端设备、运输安全(transportation safety)中的无线终端设备、智慧城市(smart city)中的无线终端设备、智慧家庭(smart home)中的无线终端设备等等。本公开的实施例对终端设备所采用的具体技术和具体设备形态不做限定。
(无线)接入网络((radio)access network，(R)AN)，用于为特定区域的授权终端设备提供入网功能，并能够根据终端设备的级别，业务的需求等使用不同质量的传输隧道。如(R)AN可管理无线资源，为终端设备提供接入服务，进而完成控制信息和/或数据信息在终端设备和核心网(core network，CN)之间的转发。本公开实施例中的接入网设备是一种为终端设备提供无线通信功能的设备，也可称为网络设备。如该接入网设备可以包括：5G系统中的下一代基站节点(next generation node basestation，gNB)、长期演进(longterm evolution，LTE)中的演进型节点B(evolved node B，eNB)、无线网络控制器(radionetwork controller，RNC)、节点B(node B，NB)、基站控制器(base station controller，BSC)、基站收发台(base transceiver station，BTS)、家庭基站(例如，home evolvednodeB，或home node B，HNB)、基带单元(base band unit，BBU)、传输点(transmitting andreceiving point，TRP)、发射点(transmitting point，TP)、小基站设备(pico)、移动交换中心，或者未来网络中的网络设备等。可理解，本公开实施例对接入网设备的具体类型不作限定。在不同无线接入技术的系统中，具备接入网设备功能的设备的名称可能会有所不同。
下面对其中的部分网络功能的功能进行简单介绍说明。
运营商网络可包括以下网络功能中的一个或多个：鉴权服务器功能(authenticationserver function，AUSF)、网络开放功能(network exposure function，NEF)、策略控制功能(policy control function，PCF)、统一数据管理(unified datamanagement，UDM)、统一数据库(unified data repository，UDR)、网络存储功能(network repository function，NRF)、应用功能(application function，AF)、接入与移动性管理功能(access and mobility management function，AMF)、会话管理功能(session management function，SMF)、RAN以及用户面功能(user planefunction，UPF)、统一的数据存储库功能(unified data repository，UDR)、网络数据分析功能(network data analytics function，NWDAF)等。上述运营商网络中，除无线接入网部分之外的部分也可以称为核心网部分。
下面针对上述各个的功能进行简要说明。
AMF，负责用户的移动性管理，包括移动状态管理，分配用户临时身份标识，认证和授权用户。
SMF，负责UPF选择，UPF重选，网络协议(Internet Protocol，IP)地址分配，负责承载的建立、修改和释放，QoS控制。
PCF，包含策略控制决策和基于流计费控制的功能，包含用户签约数据管理功能，策略控制功能，计费策略控制功能，QoS控制等等。
UDM，负责管理签约数据，当签约数据修改的时候，负责通知相应的网络功能。
UDR，负责存储和检索签约数据、策略数据和公共架构数据等；供UDM、PCF和NEF获取相关数据。UDR要能够针对不同类型的数据如签约数据、策略数据有不同的数据接入鉴权机制，以保证数据接入的安全性；UDR对于非法的服务化操作或者数据接入请求要能够返回携带合适原因值的失败响应。
AF，用于向UE提供某种应用层服务，AF在向UE提供服务时，对服务质量QoS策略(Policy)和计费(Charging)策略有要求，且需要通知网络。同时，AF也需要核心网其它网络功能反馈的应用相关的信息。
NEF，主要支持网络能力开放功能，对外开放网络能力和服务；第三代合作伙伴计划(3rd generation partnership project 3GPP)网络功能(network function，NF)通过NEF向其他NF发布功能和事件。NF开放的能力和事件可以安全地开放给第三方应用。NEF使用UDR的标准化接口(Nudr)将结构化数据进行存储/检索。将AF的交换信息与内部网络功能的交换信息进行翻译。例如，将在AF-服务(Service)-指示符(Identifier)和内部5G核心信息之间进行转换。内部5G核心信息，比如可以是数据网络名称(data network name，DNN)或者单网络切片选择辅助信息(single network slice selection assistanceinformation，S-NSSAI)。
UPF，支持以下全部或者部分功能：将协议数据单元(protocol data unit，PDU)会话与数据网络互连；分组路由和转发功能，例如，支持对流量进行下行分流(uplinkclassifier)后转发到数据网络，支持分支点(Branching point)功能以支持多宿主(multi-homed)PDU会话；数据包检测功能。
AUSF，负责鉴权功能以及负责执行网络切片鉴权授权(network slicespecific authentication and authorization，NSSAA)流程。
NWDAF，用于与其它核心网进行信令交互以了解网络的状态。核心网可以向NWDAF进行订阅，与了解网络的状态。
UE无线能力管理功能(UE radio Capability Management Function，UCMF)用于存储与公共陆地移动网(public land mobile network，PLMN)分配的或制造商分配的UE无线能力ID对应的字典条目。AMF可以订阅UCMF，以从UCMF获得UCMF分配的UE无线能力ID的新值，以在本地缓存它们。
OAM可以覆盖接入网和核心网的网络功能，并且可以从接入网和核心网的这些网络功能上收集数据。
需要说明的是，在图1中第三方(3rd)AF和操作(operator)AF都属于AF。区别在于：3rd AF(比如微信业务服务器、支付宝支付业务服务器)不受运营商管控，operator AF(例如，IP多媒体系统(IP multimedia system)中的代理-呼叫会话控制功能(proxy-call session control function，P-CSCF))受运营商管控，3rd AF与NWDAF交互时需要通过NEF。
图1所示为基于服务化架构的通信网络架构示意图，图1中，NEF、NRF、PCF、UDM、AUSF、UDR、AMF以及SMF之间，任意两个网络功能之间通信可以采用服务化通信方式，比如NEF与AUSF之间通信采用的接口Nnef和Nausf均为服务化的接口，同理，接口Nnrf、Npcf、Nudm、Naf、Nudr、Namf以及Nsmf均为服务化的接口。另外，AMF与终端设备可通过N1接口通信，AMF与(R)AN可通过N2接口通信，RAN和UPF可通过N3接口通信，SMF与UPF可通过N4接口通信，终端设备与RAN之间进行空口通信，UPF与DN可通过N6接口通信。
图2为基于点对点接口的通信网络架构示意图；图1与图2的主要区别在于：图2中的各个网络功能之间的接口是点对点的接口，而不是服务化的接口。为了点对点图的清晰性，未描述UDSF、NEF、NWDAF和NRF。需要说明的是，图2中核心网均可以根据需要与UDSF、NEF、NWDAF和NRF交互。为了清晰起见，OAM未在图1和图2中体现，OAM可以从接入网和核心网收集数据。
可以理解的是，以上说介绍的术语在不同的领域或不同的标准中，可能有不同的名称，因此不应将以上所示的名称理解为对本公开实施例的限定。上述网络功能或者功能既可以是硬件设备中的网络元件，也可以是在专用硬件上运行软件功能，或者是平台(例如，云平台)上实例化的虚拟化功能。
需要说明的是，本公开实施例中所涉及的功能还可以称为网元、功能设备或实体或功能实体，例如，接入和移动性管理还可以称为接入和移动性管理网元、接入和移动性管理功能设备或者接入和移动性管理实体或者接入和移动性管理功能实体。各个功能设备的名称在本公开中不做限定，本领域技术人员可以将上述功能设备的名称更换为其它名称而执行相同的功能，均属于本公开保护的范围。上述功能设备既可以是硬件设备中的网络元件，也可以是在专用硬件上运行软件功能，或者是平台(例如，云平台)上实例化的虚拟化功能。
可以理解的是，本公开实施例描述的通信系统，以及网络架构是为了更加清楚的说明本公开实施例的技术方案，并不构成对于本公开实施例提供的技术方案的限定，本领域普通技术人员可知，随着系统架构的演变和新业务场景的出现，本公开实施例提供的技术方案对于类似的技术问题，同样适用。
此外，为了便于理解本公开实施例，做出以下几点说明。
第一，本公开实施例中，“用于指示”可以包括用于直接指示和用于间接指示。当描述某一信息用于指示A时，可以包括该信息直接指示A或间接指示A，而并不代表该信息中一定携带有A。
将信息所指示的信息称为待指示信息，则具体实现过程中，对待指示信息进行指示的方式有很多种，例如但不限于，可以直接指示待指示信息，如待指示信息本身或者该待指示信息的索引等。也可以通过指示其他信息来间接指示待指示信息，其中该其他信息与待指示信息之间存在关联关系。还可以仅仅指示待指示信息的一部分，而待指示信息的其他部分则是已知的或者提前约定的。例如，还可以借助预先约定(例如协议规定)的各个信息的排列顺序来实现对特定信息的指示，从而在一定程度上降低指示开销。
待指示信息可以作为一个整体一起发送，也可以分成多个子信息分开发送，而且这些子信息的发送周期和/或发送时机可以相同，也可以不同。具体发送方法本公开不进行限定。其中，这些子信息的发送周期和/或发送时机可以是预先定义的，例如根据协议预先定义的。
第二，本公开实施例列举了多个实施方式以对本公开实施例的技术方案进行清晰地说明。当然，本领域内技术人员可以理解，本公开实施例提供的多个实施例，可以被单独执行，也可以与本公开实施例中其他实施例的方法结合后一起被执行，还可以单独或结合后与其他相关技术中的一些方法一起被执行；本公开实施例并不对此进行限定。
下面结合附图对本公开所提供的多模态业务数据流的管理方法和装置进行详细地介绍。
移动媒体类服务、云AR(augmented reality，增强现实)/VR(virtual reality，虚拟现实)等XR(extended reality，扩展现实)业务、云游戏、基于视频的机器或无人机远程控制等业务，预计将为5G网络贡献越来越高的流量。XR业务还涉及多模态数据流，这些多模态数据，可以是描述同一业务或应用的从同一个设备或不同设备(包括传感器)输入的数据，这些数据可能会输出到一个或多个目的设备终端。多模态数据中的各数据流往往具有相关性，比如音频流和视频流的同步，触觉和视觉的同步等。这类媒体业务的数据流本身，各数据流之间，以及这些业务数据流对网络传输的需求，都存在一些共性特征，这些特性的有效识别和利用将更有助于网络和业务的传输、控制，也更有助于业务保障和用户体验。
XRM(XR and media)业务需要第五代移动通信系统(the 5th generation system，5GS)综合考虑业务的相关数据流服务质量(quality of service，QoS)特性，例如延迟严重保证比特率(guaranteed bitrate，GBR)数据流，保证流比特率(guaranteed flow bit rate，GFBR)，包时延预算(packet delay budget，PDB)，违约最大数据突发量(maximum data burstvolume，MDBV)等参数是否能同时满足并协同一致。涉及一个UE的多个XRM数据流，和多个UE的XRM数据流，彼此的QoS授权与执行的一致性保障。
但5GS系统中，尚没有完善机制来支持多UE间的XRM业务和多模态业务的这些需求，没有相应技术方案来支持一个UE的多个XRM数据流之间，或多个UE的XRM数据流之间，策略决策的一致性。
基于此，本公开实施例中，PCF接收AF发送的请求消息，其中，请求消息用于指示将业务数据流添加至第一业务数据流组和/或将业务数据流从第二业务数据流组中移除；PCF可以根据请求消息，生成或更新策略与计费控制(Policy and Charging Control，PCC)规则。由此，PCF可以确定业务数据流所属的业务数据流组，并生成或更新对应的PCC规则，更合理的为业务数据流进行策略决策和资源授权，保证属于同一业务数据流组的业务数据流的策略决策的一致性。
请参见图3，图3是本公开实施例提供的一种多模态业务数据流的管理方法的流程图。该方法由PCF执行，如图3所示，该方法可以包括但不限于如下步骤：
S31：接收AF发送的请求消息。
本公开实施例中，PCF可以接收AF发送的请求消息。
其中，请求消息用于指示以下至少一项：
将业务数据流添加至第一业务数据流组；
将业务数据流从第二业务数据流组中移除。
本公开实施例中，PCF可以接收AF发送的请求消息，其中，请求消息用于指示将业务数据流添加至第一业务数据流组。由此，PCF可以确定业务数据流属于第一业务数据流组。
本公开实施例中，PCF可以接收AF发送的请求消息，其中，请求消息用于指示将业务数据流从第二业务数据流组中移除。由此，PCF可以确定业务数据流不属于第二业务数据流组。
本公开实施例中，PCF可以接收AF发送的请求消息，其中，请求消息用于指示将业务数据流添加至第一业务数据流组和将业务数据流从第二业务数据流组中移除。由此，PCF可以确定业务数据流属于第一业务数据流组以及不属于第二业务数据流组。
可以理解的是，PCF接收AF发送的请求消息，请求消息可以指示将一个或多个业务数据流添加至第一业务数据流组。由此，PCF可以确定一个或多个业务数据流属于的第一业务数据流组。
可以理解的是，PCF接收AF发送的请求消息，请求消息可以指示将一个或多个业务数据流从第二业务数据流组中移除。由此，PCF可以确定一个或多个业务数据流不属于的第二业务数据流组。
可以理解的是，PCF接收AF发送的请求消息，请求消息可以指示将一个或多个业务数据流添加至第一业务数据流组以及从第二业务数据流组中移除。由此，PCF可以确定一个或多个业务数据流属于的第一业务数据流组以及不属于的第二业务数据流组。
在一些实施例中，请求消息中包括业务数据流对应的组标识，组标识关联第一业务数据流组或第二业务数据流组。
本公开实施例中，PCF接收AF发送的请求消息，请求消息中包括业务数据流对应的组标识。
其中，组标识可以为共同标识(common ID)或者还可以为XRM业务标识(XRM service ID)等，共同标识或XRM业务标识可通过不同取值指示不同分组，本公开实施例不作具体限制。
本公开实施例中，组标识可以关联第一业务数据流组，或者组标识还可以关联第二业务数据流组。
可以理解的是，请求消息用于指示将业务数据流添加至第一业务数据流组和/或将业务数据流从第二业务数据流组中移除。
其中，在请求消息中包括业务数据流对应的组标识，组标识关联第一业务数据流组的情况下，请求消息可以用于指示将业务数据流添加至第一业务数据流组和/或将业务数据流从第二业务数据流组中移除。
其中，在请求消息中包括业务数据流对应的组标识，组标识关联第二业务数据流组的情况下，请求消息可以用于指示将业务数据流添加至第一业务数据流组和/或将业务数据流从第二业务数据流组中移除。
在一种可能的实现方式中，PCF可以接收AF发送的请求消息，请求消息中包括组标识，组标识关联第一业务数据流组，请求消息可以用于指示将业务数据流添加至第一业务数据流组。
在另一种可能的实现方式中，PCF可以接收AF发送的请求消息，请求消息中包括组标识，组标识关联第一业务数据流组，在接收AF发送的请求消息之前，业务数据流不属于任何业务数据流组中的情况下，请求消息可以用于指示将业务数据流添加至第一业务数据流组。
在又一种可能的实现方式中，PCF可以接收AF发送的请求消息，请求消息中包括组标识，组标识关联第二业务数据流组，请求消息可以用于指示将业务数据流从第二业务数据流组中移除。
在又一种可能的实现方式中，PCF可以接收AF发送的请求消息，请求消息中包括组标识，组标识关联第一业务数据流组，在接收AF发送的请求消息之前，业务数据流位于第二业务数据流组中的情况下，请求消息可以用于指示将业务数据流添加至第一业务数据流组，以及将业务数据流从第二业务数据流组中移除。
在一些实施例中，在接收AF发送的请求消息之前，业务数据流位于第二业务数据流组中，或业务数据流不属于任何业务数据流组。
本公开实施例中，若在PCF接收AF发送的请求消息之前，业务数据流位于第二业务数据流组中，则PCF接收到AF发送的请求消息，在请求消息中包括业务数据流对应的组标识，且组标识关联第一业务数据流组的情况下，则请求消息可以指示将业务数据流从第二业务数据流组中移除。另外，请求消息还可以指示将业务数据流添加至第一业务数据流组。
本公开实施例中，若在PCF接收AF发送的请求消息之前，业务数据流不属于任何业务数据流组，则PCF接收到AF发送的请求消息，在请求消息中包括业务数据流对应的组标识，且组标识关联第一业务数据流组的情况下，则请求消息可以指示将业务数据流添加至第一业务数据流组中。
在一些实施例中，请求消息中包括业务数据流对应的动作指示。
本公开实施例中，请求消息中包括业务数据流对应的动作指示(action indication)。
本公开实施例中，PCF接收AF发送的请求消息，请求消息中组标识，组标识关联第一业务数据流组或第二业务数据流组，且请求消息中还包括业务数据流对应的动作指示。
其中，动作指示可以用于指示以下至少一项：
将业务数据流添加至第一业务数据流组；
将业务数据流从第二业务数据流组中移除。
在一种可能的实现方式中，PCF接收AF发送的请求消息，请求消息中组标识，组标识关联第一业务数据流组，且请求消息中还包括业务数据流对应的动作指示的情况下，动作指示可以用于指示将业务数据流添加至第一业务数据流组。
可以理解的是，PCF接收AF发送的请求消息，在请求消息中包括业务数据流对应的组标识，组标识关联第一业务数据流组，并且请求消息中还包括业务数据流对应的动作指示，动作指示用于指示将业务数据流添加至第一业务数据流组的情况下，不管业务数据流之前是否位于数据业务流组，或位于哪个业务数据流组，PCF均可以根据请求消息中的动作指示，确定将业务数据流添加至第一业务数据流组。
其中，若业务数据流之前位于第一业务数据流组，则PCF可以不对业务数据流的组信息进行更新，可以确定业务数据流属于第一业务数据流组。
在另一种可能的实现方式中，PCF接收AF发送的请求消息，请求消息中组标识，组标识关联第二业务数据流组，且请求消息中还包括业务数据流对应的动作指示的情况下，动作指示可以用于指示将业务数据流从第二业务数据流组中移除。
其中，若业务数据流之前位于第二业务数据流组，则PCF可以根据请求消息中的动作指示，更新业务数据流的组信息，可以确定业务数据流不属于第二业务数据流组。
其中，若业务数据流之前位于第二业务数据流组以外的其他组，则PCF可以不对业务数据流的组信息进行更新，可以确定业务数据流不属于第二业务数据流组。
在又一种可能的实现方式中，PCF接收AF发送的请求消息，请求消息中组标识，组标识关联第一业务数据流组，且请求消息中还包括业务数据流对应的动作指示的情况下，若在PCF接收AF发送的请求消息之前，业务数据流位于第二业务数据流组中，则动作指示可以用于指示将业务数据流从第二业务数据流组中移除，另外，动作指示信息还可以用于指示将业务数据流添加至第一业务数据流组。
其中，若业务数据流之前位于第二业务数据流组，则PCF可以根据请求消息中的动作指示，更新业务数据流的组信息，将业务数据流从第二业务数据流组中移除并且将业务数据流添加至第一业务数据流组中，可以确定业务数据流属于第一业务数据流组，不属于第二业务数据流组。
在又一种可能的实现方式中，PCF接收AF发送的请求消息，请求消息中组标识，组标识关联第一业务数据流组，且请求消息中还包括业务数据流对应的动作指示的情况下，若在PCF接收AF发送的请求消息之前，业务数据流不属于任何业务数据流组，则动作指示可以用于指示将业务数据流添加至第一业务数据流组。
在一些实施例中，PCF接收AF发送的请求消息，在请求消息中组标识，组标识关联第二业务数据流组，请求消息中还包括业务数据流对应的动作指示的情况下，动作标识可以用于指示将业务数据流从第二业务数据流组中移除。
本公开实施例中，在请求消息中包括业务数据流对应的组标识，组标识关联第二业务数据流组，且请求消息中还包括业务数据流对应的动作指示的情况下，动作标识可以用于指示将业务数据流从第二业务数据流组中移除。
可以理解的是，PCF接收AF发送的请求消息，在请求消息中包括业务数据流对应的组标识，组标识关联第二业务数据流组，且请求消息中还包括业务数据流对应的动作指示，动作指示用于指示将业务数据流从第二业务数据流组中移除的情况下，不管业务数据流之前位于哪个业务数据流组，均可以根据请求消息中的动作指示，确定将业务数据流从第二业务数据流组中移除。
需要说明的是，PCF接收AF发送的请求消息之前，业务数据流可以位于第二业务数据流组中，或者还可以位于第二业务数据流组以外的其他业务数据流组中。
本公开实施例中，PCF接收AF发送的请求消息，可以直接接收AF发送的请求消息，或者还可以间接接收AF发送的请求消息。
在一些实施例中，PCF接收AF发送的请求消息，包括：
接收AF通过网络开放功能NEF发送的请求消息；或者
接收AF通过时敏通信和时同步功能TSCTSF发送的请求消息；或者
接收AF通过NEF和TSCTSF发送的请求消息。
本公开实施例中，PCF接收AF发送的请求消息，可以接收AF通过网络开放功能(network exposure function，NEF)发送的请求消息。
本公开实施例中，PCF接收AF发送的请求消息，可以接收AF通过时敏通信和时同步功能(time sensitive communication and time synchronization function，TSCTSF)发送的请求消息。
本公开实施例中，PCF接收AF发送的请求消息，可以接收AF通过NEF和TSCTSF发送的请求消息。
在一些实施例中，PCF接收AF发送的请求消息，包括：接收AF发送的AF会话创建请求或AF会话更新请求，其中，AF会话创建请求或AF会话更新请求中包括请求消息。
本公开实施例中，PCF接收AF发送的请求消息，可以接收AF发送的AF会话创建请求，其中，AF会话创建请求中包括请求消息。
本公开实施例中，PCF接收AF发送的请求消息，可以接收AF发送的AF会话更新请求，其中，AF会话更新请求中包括请求消息。
在一些实施例中，PCF接收AF发送的请求消息，包括：在以下至少一项流程中，接收AF发送的请求消息：
AF会话建立请求的流程；
AF会话建立更新请求的流程；
业务特定参数的提供流程；
为后续的AF会话设置策略的流程。
本公开实施例中，PCF接收AF发送的请求消息，可以在AF会话建立请求的流程中，接收AF发送的请求消息。
本公开实施例中，PCF接收AF发送的请求消息，可以在AF会话建立更新请求的流程中，接收AF发送的请求消息。
本公开实施例中，PCF接收AF发送的请求消息，可以在业务特定参数的提供流程中，接收AF发送的请求消息。
本公开实施例中，PCF接收AF发送的请求消息，可以在为后续的AF会话设置策略的流程中，接收AF发送的请求消息。
需要说明的是，上述实施例并没有穷举，仅为部分实施例的示意，并且上述实施例可以单独被实施，也可以多个进行组合被实施，上述实施例仅作为示意，不作为对本公开实施例保护范围的具体限制。
S32：根据请求消息，生成或更新策略与计费控制PCC规则。
本公开实施例中，PCF可以根据请求消息，确定业务数据流所属的业务数据流组，进而生成或更新PCC规则，由此，可以更合理的为业务数据流进行策略决策和资源授权，保证属于同一业务数据流组的业务数据流的策略决策的一致性。
本公开实施例中，PCF根据请求消息，生成或更新PCC规则，可以进一步的将生成或更新的PCC规则下发给SMF进行安装和执行。
可选的，SMF可以根据PCF下发的生成或更新的PCC规则，生成相应的QoS规则，下发给UPF和RAN安装执行。
通过实施本公开实施例，PCF接收AF发送的请求消息，根据请求消息，生成或更新策略与计费控制PCC规则。由此，PCF可以确定业务数据流所属的业务数据流组，并生成或更新对应的PCC规则，可以更合理的为业务数据流进行策略决策和资源授权，保证属于同一业务数据流组的业务数据流的策略决策的一致性。
请参见图4，图4是本公开实施例提供的另一种多模态业务数据流的管理方法的流程图。该方法由PCF执行，如图4所示，该方法可以包括但不限于如下步骤：
S41：接收AF发送的请求消息。
其中，请求消息用于指示以下至少一项：
将业务数据流添加至第一业务数据流组；
将业务数据流从第二业务数据流组中移除。
其中，S41的相关描述可以参见上述实施例中的相关描述，此处不再赘述。
S42：根据请求消息，更新第一业务数据流组和/或第二业务数据流组。
本公开实施例中，PCF接收AF发送的请求消息，其中，请求消息用于指示将业务数据流添加至第一业务数据流组，基于此，PCF可以根据请求消息，更新第一业务数据流组。
本公开实施例中，PCF接收AF发送的请求消息，其中，请求消息用于指示将业务数据流从第二业务数据流组中移除，基于此，PCF可以根据请求消息，更新第二业务数据流组。
本公开实施例中，PCF接收AF发送的请求消息，其中，请求消息用于指示将业务数据流添加至第一业务数据流组和将业务数据流从第二业务数据流组中移除，基于此，PCF可以根据请求消息，更新第一业务数据流组和第二业务数据流组。
需要说明的是，本公开实施例中，S41至S42可以单独被实施，也可以结合本公开实施例中的任何一个其他步骤一起被实施，例如结合本公开实施例中的S31至S32一起被实施，本公开实施例并不对此做出限定。
通过实施本公开实施例，PCF接收AF发送的请求消息，根据请求消息，更新第一业务数据流组和/或第二业务数据流组。由此，PCF可以确定业务数据流所属的业务数据流组，以在PCC规则的生成更新时，更合理的为业务数据流进行策略决策和资源授权，保证属于同一业务数据流组的业务数据流的策略决策的一致性。
请参见图5，图5是本公开实施例提供的又一种多模态业务数据流的管理方法的流程图。该方法由PCF执行，如图5所示，该方法可以包括但不限于如下步骤：
S51：接收AF发送的请求消息。
其中，请求消息用于指示以下至少一项：
将业务数据流添加至第一业务数据流组；
将业务数据流从第二业务数据流组中移除。
S52：根据请求消息，更新第一业务数据流组和/或第二业务数据流组。
其中，S51和S52的相关描述可以参见上述实施例中的相关描述，此处不再赘述。
S53：将更新后的第一业务数据流组和/或第二业务数据流组进行存储。
本公开实施例中，PCF接收AF发送的请求消息，在请求消息用于指示将业务数据流添加至第一业务数据流组的情况下，PCF可以根据请求消息，更新第一业务数据流组，并且将更新后的第一业务数据流组进行存储。
本公开实施例中，PCF接收AF发送的请求消息，在请求消息用于指示将业务数据流从第二业务数据流组中移除的情况下，PCF可以根据请求消息，更新第二业务数据流组，并且将更新后的第二业务数据流组进行存储。
本公开实施例中，PCF接收AF发送的请求消息，在请求消息用于指示将业务数据流添加至第一业务数据流组和将业务数据流从第二业务数据流组中移除的情况下，PCF可以根据请求消息，更新第一业务数据流组和第二业务数据流组，并且将更新后的第一业务数据流组和第二业务数据流组进行存储。
在一些实施例中，PCF将更新后的第一业务数据流组和/或第二业务数据流组存储到以下至少一项中：
本地；
统一数据库UDR；
统一数据管理功能UDM；
非结构化数据存储功能UDSF。
本公开实施例中，PCF可以将更新后的第一业务数据流组和/或第二业务数据流组存储到本地。
本公开实施例中，PCF可以将更新后的第一业务数据流组和/或第二业务数据流组存储到统一数据库(unified data repository，UDR)。
本公开实施例中，PCF可以将更新后的第一业务数据流组和/或第二业务数据流组存储到非结构化数据存储功能(Unstructured Data Storage Function，UDSF)。
需要说明的是，本公开实施例中，S51至S53可以单独被实施，也可以结合本公开实施例中的任何一个其他步骤一起被实施，例如结合本公开实施例中的S31至S32和/或S41至S42一起被实施，本公开实施例并不对此做出限定。
通过实施本公开实施例，PCF接收AF发送的请求消息，根据请求消息，更新第一业务数据流组和/或第二业务数据流组，将更新后的第一业务数据流组和/或第二业务数据流组进行存储。由此，PCF可以确定业务数据流所属的业务数据流组，并对业务数据流组进行更新和存储，以在PCC规则的生成更新时，更合理的为业务数据流进行策略决策和资源授权，保证属于同一业务数据流组的业务数据流的策略决策的一致性。
请参见图6，图6是本公开实施例提供的又一种多模态业务数据流的管理方法的流程图。该方法由PCF执行，如图6所示，该方法可以包括但不限于如下步骤：
S61：接收AF发送的请求消息，其中，请求消息用于指示将业务数据流从第二业务数据流组中移除。
其中，S61的相关描述可以参见上述实施例中的相关描述，此处不再赘述。
S62：继续保留或释放请求消息对应的AF会话。
本公开实施例中，PCF接收AF发送的请求消息，其中，请求消息用于指示将业务数据流从第二业务数据流组中移除，在此情况下，PCF可以继续保留或释放请求消息对应的AF会话。
需要说明的是，本公开实施例中，S51至S53可以单独被实施，也可以结合本公开实施例中的任何一个其他步骤一起被实施，例如结合本公开实施例中的S31至S32和/或S41至S42和/或S51至S53一起被实施，本公开实施例并不对此做出限定。
通过实施本公开实施例，PCF接收AF发送的请求消息，其中，请求消息用于指示将业务数据流从第二业务数据流组中移除，继续保留或释放请求消息对应的AF会话。由此，PCF可以根据AF的请求消息将业务数据流从第二业务数据流组中移除，并继续保留或释放请求消息对应的AF会话。
请参见图7，图7是本公开实施例提供的一种多模态业务数据流的管理方法的流程图。该方法由AF执行，如图7所示，该方法可以包括但不限于如下步骤：
S71：向PCF发送请求消息。
本公开实施例中，AF可以向PCF发送请求消息。
其中，请求消息用于指示以下至少一项：
将业务数据流添加至第一业务数据流组；
将业务数据流从第二业务数据流组中移除。
本公开实施例中，AF可以向PCF发送请求消息，其中，请求消息用于指示将业务数据流添加至第一业务数据流组。由此，AF可以向PCF发送业务数据流属于第一业务数据流组的信息。
本公开实施例中，AF可以向PCF发送请求消息，其中，请求消息用于指示将业务数据流从第二业务数据流组中移除。由此，AF可以向PCF发送业务数据流不属于第二业务数据流组的信息。
本公开实施例中，AF可以向PCF发送请求消息，其中，请求消息用于指示将业务数据流添加至第一业务数据流组和将业务数据流从第二业务数据流组中移除。由此，AF可以向PCF发送业务数据流属于第一业务数据流组以及不属于第二业务数据流组的信息。
可以理解的是，AF可以向PCF发送请求消息，请求消息可以指示将一个或多个业务数据流添加至第一业务数据流组。由此，AF可以向PCF发送一个或多个业务数据流属于的第一业务数据流组的信息。
可以理解的是，AF可以向PCF发送请求消息，请求消息可以指示将一个或多个业务数据流从第二业务数据流组中移除。由此，AF可以向PCF发送一个或多个业务数据流不属于的第二业务数据流组的信息。
可以理解的是，AF可以向PCF发送请求消息，请求消息可以指示将一个或多个业务数据流添加至第一业务数据流组以及从第二业务数据流组中移除。由此，AF可以向PCF发送一个或多个业务数据流属于的第一业务数据流组以及不属于的第二业务数据流组的信息。
在一些实施例中，请求消息中包括业务数据流对应的组标识，组标识关联第一业务数据流组或第二业务数据流组。
本公开实施例中，AF向PCF发送请求消息，请求消息中包括业务数据流对应的组标识。
其中，组标识可以为共同标识(common ID)或者还可以为XRM业务标识(XRM service ID)等，共同标识或XRM业务标识可通过不同取值指示不同分组，本公开实施例不作具体限制。
本公开实施例中，组标识可以关联第一业务数据流组，或者组标识还可以关联第二业务数据流组。
可以理解的是，请求消息用于指示将业务数据流添加至第一业务数据流组和/或将业务数据流从第二业务数据流组中移除。
其中，在请求消息中包括业务数据流对应的组标识，组标识关联第一业务数据流组的情况下，请求消息可以用于指示将业务数据流添加至第一业务数据流组和/或将业务数据流从第二业务数据流组中移除。
其中，在请求消息中包括业务数据流对应的组标识，组标识关联第二业务数据流组的情况下，请求消息可以用于指示将业务数据流添加至第一业务数据流组和/或将业务数据流从第二业务数据流组中移除。
在一种可能的实现方式中，AF可以向PCF发送请求消息，请求消息中包括组标识，组标识关联第一业务数据流组，请求消息可以用于指示将业务数据流添加至第一业务数据流组。
在另一种可能的实现方式中，AF可以向PCF发送请求消息，请求消息中包括组标识，组标识关联第一业务数据流组，在向PCF发送请求消息之前，业务数据流不属于任何业务数据流组中的情况下，请求消息可以用于指示将业务数据流添加至第一业务数据流组。
在又一种可能的实现方式中，AF可以向PCF发送请求消息，请求消息中包括组标识，组标识关联第二业务数据流组，请求消息可以用于指示将业务数据流从第二业务数据流组中移除。
在又一种可能的实现方式中，AF可以向PCF发送请求消息，请求消息中包括组标识，组标识关联第一业务数据流组，在接收AF发送的请求消息之前，业务数据流位于第二业务数据流组中的情况下，请求消息可以用于指示将业务数据流添加至第一业务数据流组，以及将业务数据流从第二业务数据流组中移除。
在一些实施例中，在AF向PCF发送请求消息之前，业务数据流位于第二业务数据流组中，或业务数据流不属于任何业务数据流组。
本公开实施例中，若在AF向PCF发送请求消息之前，业务数据流位于第二业务数据流组中，则AF向PCF发送请求消息，在请求消息中包括业务数据流对应的组标识，且组标识关联第一业务数据流组的情况下，则请求消息可以指示将业务数据流从第二业务数据流组中移除，另外，请求消息还可以指示将业务数据流添加至第一业务数据流组。
本公开实施例中，若在AF向PCF发送请求消息之前，业务数据流不属于任何业务数据流组，则AF向PCF发送请求消息，在请求消息中包括业务数据流对应的组标识，且组标识关联第一业务数据流组的情况下，则请求消息可以指示将业务数据流添加至第一业务数据流组中。
在一些实施例中，请求消息中包括业务数据流对应的动作指示。
本公开实施例中，请求消息中包括业务数据流对应的动作指示(action indication)。
本公开实施例中，AF向PCF发送请求消息，请求消息中组标识，组标识关联第一业务数据流组或第二业务数据流组，且请求消息中还包括业务数据流对应的动作指示。
其中，动作指示可以用于指示以下至少一项：
将对应的业务数据流添加至第一业务数据流组；
将对应的业务数据流从第二业务数据流组中移除。
在一种可能的实现方式中，AF向PCF发送请求消息，请求消息中组标识，组标识关联第一业务数据流组，且请求消息中还包括业务数据流对应的动作指示的情况下，动作指示可以用于指示将业务数据流添加至第一业务数据流组。
可以理解的是，AF向PCF发送请求消息，在请求消息中包括业务数据流对应的组标识，组标识关联第一业务数据流组，并且请求消息中还包括业务数据流对应的动作指示，动作指示用于指示将业务数据流添加至第一业务数据流组的情况下，不管业务数据流之前是否位于数据业务流组，或位于哪个业务数据流组，PCF均可以根据请求消息中的动作指示，确定将业务数据流添加至第一业务数据流组。
其中，若业务数据流之前位于第一业务数据流组，则PCF可以不对业务数据流的组信息进行更新，可以确定业务数据流属于第一业务数据流组。
在另一种可能的实现方式中，AF向PCF发送请求消息，请求消息中组标识，组标识关联第二业务数据流组，且请求消息中还包括业务数据流对应的动作指示的情况下，动作指示可以用于指示将业务数据流从第二业务数据流组中移除。
其中，若业务数据流之前位于第二业务数据流组，则PCF可以根据请求消息中的动作指示，更新业务数据流的组信息，可以确定业务数据流不属于第二业务数据流组。
其中，若业务数据流之前位于第二业务数据流组以外的其他组，则PCF可以不对业务数据流的组信息进行更新，可以确定业务数据流不属于第二业务数据流组。
在又一种可能的实现方式中，AF向PCF发送请求消息，请求消息中组标识，组标识关联第一业务数据流组，且请求消息中还包括业务数据流对应的动作指示的情况下，若在AF向PCF发送请求消息之前，业务数据流位于第二业务数据流组中，则动作指示可以用于指示将业务数据流从第二业务数据流组中移除，另外，动作指示信息还可以用于指示将业务数据流添加至第一业务数据流组。
其中，若业务数据流之前位于第二业务数据流组，则PCF可以根据请求消息中的动作指示，更新业务数据流的组信息，将业务数据流从第二业务数据流组中移除并且将业务数据流添加至第一业务数据流组中，可以确定业务数据流属于第一业务数据流组，不属于第二业务数据流组。
在又一种可能的实现方式中，AF向PCF发送请求消息，请求消息中组标识，组标识关联第一业务数据流组，且请求消息中还包括业务数据流对应的动作指示的情况下，若在AF向PCF发送请求消息之前，业务数据流不属于任何业务数据流组，则动作指示可以用于指示将业务数据流添加至第一业务数据流组。
在一些实施例中，AF向PCF发送请求消息，在请求消息中组标识，组标识关联第二业务数据流组，请求消息中还包括业务数据流对应的动作指示的情况下，动作标识可以用于指示将业务数据流从第二业务数据流组中移除。
本公开实施例中，在请求消息中包括业务数据流对应的组标识，组标识关联第二业务数据流组，且请求消息中还包括业务数据流对应的动作指示的情况下，动作标识可以用于指示将业务数据流从第二业务数据流组中移除。
可以理解的是，AF向PCF发送请求消息，在请求消息中包括业务数据流对应的组标识，组标识关联第二业务数据流组，且请求消息中还包括业务数据流对应的动作指示，动作指示用于指示将业务数据流从第二业务数据流组中移除的情况下，不管业务数据流之前位于哪个业务数据流组，PCF均可以根据请求消息中的动作指示，确定将业务数据流从第二业务数据流组中移除。
需要说明的是，AF向PCF发送请求消息之前，业务数据流可以位于第二业务数据流组中，或者还可以位于第二业务数据流组以外的其他业务数据流组中。
本公开实施例中，AF向PCF发送请求消息，可以直接向PCF发送请求消息，或者还可以间接向PCF发送请求消息。
在一些实施例中，AF向PCF发送请求消息，包括：
通过NEF向PCF发送请求消息；或者
通过TSCTSF向PCF发送请求消息；或者
通过NEF和TSCTSF向PCF发送请求消息。
本公开实施例中，AF向PCF发送请求消息，可以通过NEF向PCF发送请求消息。
本公开实施例中，AF向PCF发送请求消息，可以通过TSCTSF向PCF发送请求消息。
本公开实施例中，AF向PCF发送请求消息，可以通过NEF和TSCTSF向PCF发送请求消息。
在一些实施例中，AF向PCF发送请求消息，包括：向PCF发送AF会话创建请求或AF会话更新请求，其中，AF会话创建请求或AF会话更新请求中包括请求消息。。
本公开实施例中，AF向PCF发送请求消息，可以向PCF发送AF会话创建请求，其中，AF会话创建请求中包括请求消息。
本公开实施例中，AF向PCF发送请求消息，可以向PCF发送AF会话更新请求，其中，AF会话更新请求中包括请求消息。
可以理解的是，AF向PCF发送请求消息，可以通过如下流程向PCF发送请求消息：
一种流程如：AF在AF会话期间通过所需的QoS程序向PCF提供RT延迟要求(The AF provides the RT latency requirement to the PCF during AF session with required QoS procedure)。
一种流程如：具有所需QoS更新过程的AF会话流程中(AF session with required QoS update procedure流程中)。
一种流程如：特定于服务的参数预配流程中(Service specific parameter provisioning流程中)。
一种流程如：为将来的AF会话设置策略流程中(Set a policy for a future AF session流程中)。
在一些实施例中，AF向PCF发送请求消息，包括：在以下至少一项流程中，向述PCF发送请求消息：
AF会话建立请求的流程；
AF会话建立更新请求的流程；
业务特定参数的提供流程；
为后续的AF会话设置策略的流程。
本公开实施例中，AF向PCF发送请求消息，可以在AF会话建立请求的流程中，向述PCF发送请求消息。
本公开实施例中，AF向PCF发送请求消息，可以在AF会话建立更新请求的流程中，向述PCF发送请求消息。
本公开实施例中，AF向PCF发送请求消息，可以在业务特定参数的提供流程中，向述PCF发送请求消息。
本公开实施例中，AF向PCF发送请求消息，可以在为后续的AF会话设置策略的流程中，向述PCF发送请求消息。
需要说明的是，上述实施例并没有穷举，仅为部分实施例的示意，并且上述实施例可以单独被实施，也可以多个进行组合被实施，上述实施例仅作为示意，不作为对本公开实施例保护范围的具体限制。
通过实施本公开实施例，AF向PCF发送请求消息请求消息用于指示将业务数据流添加至第一业务数据流组和/或将业务数据流从第二业务数据流组中移除。由此，AF可以向PCF发送确定业务数据流所属的业务数据流组的信息，PCF可以根据业务数据流所属的业务数据流组的信息，生成或更新对应的PCC规则，可以更合理的为业务数据流进行策略决策和资源授权，保证属于同一业务数据流组的业务数据流的策略决策的一致性。
请参见图8，图8是本公开实施例提供的又一种多模态业务数据流的管理方法的流程图。该方法由AF执行，如图8所示，该方法可以包括但不限于如下步骤：
S81：向PCF发送请求消息，其中，请求消息用于指示将业务数据流从第二业务数据流组中移除。
其中，S81的相关描述可以参见上述实施例中的相关描述，此处不再赘述。
S82：继续保留或释放请求消息对应的AF会话。
本公开实施例中，AF向PCF发送请求消息，其中，请求消息用于指示将业务数据流从第二业务数据流组中移除，在此情况下，AF可以继续保留或释放请求消息对应的AF会话。
需要说明的是，本公开实施例中，S81至S82可以单独被实施，也可以结合本公开实施例中的任何一个其他步骤一起被实施，例如结合本公开实施例中的S71一起被实施，本公开实施例并不对此做出限定。
通过实施本公开实施例，AF向PCF发送请求消息，其中，请求消息用于指示将业务数据流从第二业务数据流组中移除，继续保留或释放请求消息对应的AF会话。由此，AF可以向向PCF发送请求消息，指示将业务数据流从第二业务数据流组中移除，并继续保留或释放请求消息对应的AF会话。
为方便理解本公开实施例，本公开实施例提供如下示例性实施例。
示例性实施例中，如图9所示。
1.AF发送AF会话资源请求，例如可以通过Nnef_AFsessionWithQoS_Create request，创建AF请求。请求消息中可以携带共同标识(common ID)或者XRM业务标识(XRM service ID)，同时可以携带动作指示(action indication)，所述动作指示用于指示增加或减少组中业务数据流(service data flow，SDF)的数量(increasing or decreasing the number of SDFs in the group)。
其中，common ID标识该XRM service业务数据流组，携带相同common ID的SDF属于同一个XRM业务组。可选地携带UE地址/UE标识符(UE address/UE Identifier)，AF标识符应用程序ID(AF Identifier Application ID),数据网络名称(data network name，DNN),单个网络切片选择辅助信息(single network slice selection assistance information，S-NSSAI),QoS参数等相应信息。
2.NEF可以授权AF请求(The NEF authorizes the AF request).如果是非可信AF，可以通过NEF发送AF的请求给PCF。(可选地，NEF可以执行相关映射，包括标识XRM service(AF-Service-Identifier)到DNN和S-NSSAI的映射，外部应用到核心网(Core Network，CN)应用标识的映射；以及基于UDM的签约信息，外部UE标识到CN内UE标识的映射(如SUPI)，以及根据UDM签约信息执行外部到内部的XRM service组标识的映射).
3.NEF授权AF请求，并可以根据AF提供的参数确定是调用TSCTSF还是直接联系PCF。(The NEF authorizes the AF request and determines whether to invoke the TSCTSF or to directly contact the PCF depending on the parameters provided by the AF.)这些信令步骤与TS 23.502条款4.15.6.6相同，用于设置具有所需QoS程序的AF会话。(These signalling steps are the same as for TS 23.502clause 4.15.6.6for setting up an AF session with required QoS procedure.)PCF从NEF或TSCTSF接收AF提供的属性(The PCF receives the AF provided attributes from NEF or from TSCTSF)。NEF触发Npcf_PolicyAuthorization_Create request，将AF请求发送给PCF，携带Common ID(or XRM service ID)，以及action indication，供PCF策略决策参考。
4.PCF可以做出政策决定。PCF可能会确定需要将更新的或新的策略信息发送到SMF。(The PCF makes a policy decision.The PCF may determine that the updated or new policy information need to be sent to the SMF.)
PCF收到AF会话(创建/更新)请求，considering common ID(or XRM service ID)，and action indication,可以生成或更新PCC规则(rule)；
可选地，PCF可以更新该common ID关联的组(group)信息；
可选地，将更新后的组信息存储在本地或UDR或UDM或UDSF中。
可选地，该action indication可以是indication显示携带，或者是将AF请求中相应SDF中原有的common ID删除或替换为不同common ID隐式携带，指示该SDF从原先group中移除；
可选地，从原先common ID关联group中移出的SDF，相应的AF会话可继续保留或释放；
(PCF可以将生成/更新的相应PCC规则下发给SMF安装和执行；SMF可以生成相应QoS规则下发给UPF和RAN安装执行。这部分可以参见相关技术中的描述)。
5.PCF可以对NEF的回应是Npcf_Policy Authorization_Create。(The PCF responds to the NEF a Npcf_Policy Authorization_Create response.)
6.NEF可以向AF发送Nnef_AFsessionWithQoS_Create响应消息。(The NEF sends a Nnef_AFsessionWithQoS_Create response message to the AF.)携带结果(Result)，告知是否请求被授权。
7.PCF可以向SMF发起SMC策略关联修改请求(PCC规则(QoS监视策略))。(The PCF initiates SM Policy Association Modification Request(PCC rule(QoS monitoring policy))to the SMF.)
根据从PCF进行测量的QoS监控策略，SMF为UPF(如果需要，为RAN)生成QoS监控配置，如步骤4中所述。(Based on the QoS monitoring policy for measurement from the PCF,the SMF generates the QoS Monitoring configuration for UPF(and for RAN,if needed),as described in step 4.)
8.SMF可以回复SM策略关联修改响应PCF。(The SMF replies SM Policy Association Modification Response to the PCF.)
9.SMF可以向UPF发起N4会话修改请求(QoS监控配置)。(The SMF initiates N4 Session Modification Request(QoS Monitoring configuration)to the UPF.)
10.收到QoS监控配置后，UPF可以启用测量和报告。UPF响应SMF。(Upon reception of QoS Monitoring configuration,the UPF enables the measurement and report.The UPF(s)respond to the SMF.)
11.对于SMF请求的修改，SMF可以调用Namf_Communication_N1N2MessageTransfer([N2 SM信息](PDU会话ID、QFI、QoS配置文件、QoS监控配置)、N1 SM容器))。(For SMF requested modification,the SMF invokes Namf_Communication_N1N2MessageTransfer([N2 SM information](PDU Session ID,QFI(s),QoS Profile(s),QoS Monitoring configuration),N1 SM container)).)
12.AMF可能会向(R)AN发送N2([从SMF接收的N2 SM信息]、NAS消息(PDU会话ID、N1 SM容器(PDU会话修改命令)))消息。收到QoS监控配置后，RAN将启用事件测量和报告。(The AMF may send N2([N2 SM information received from SMF],NAS message(PDU Session ID,N1 SM container(PDU Session Modification Command)))Message to the(R)AN.Upon reception of QoS Monitoring configuration,the RAN enables the event measurement and report.)
14.(R)AN可以通过向AMF发送N2 PDU会话确认消息来确认N2 PDU会话请求。(The(R)AN may acknowledge N2 PDU Session Request by sending a N2 PDU Session Ack Message to the AMF.)
15.AMF可以通过服务操作将从AN接收Nsmf_PDUSession_UpdateSMContext SM信息转发到SMF。(The AMF forwards the N2 SM information received from the AN to the SMF via Nsmf_PDUSession_UpdateSMContext service operation.)
16.SMF可以回复Nsmf_PDUSession_UpdateSMContext响应。(The SMF replies with a Nsmf_PDUSession_UpdateSMContext Response.)
17-18.SMF可以通过向UPF发送N4会话修改请求消息来更新PDU会话修改所涉及的UPF的N4会话。当后续PCF收到QoS监控报告，将通知给AF。(The SMF may update N4 session of the UPF(s)that are involved by the PDU Session Modification by sending N4 Session Modification Request message to the UPF.当后续PCF收到QoS Monitoring report,将notify给AF。)
AF提供XRM业务请求给PCF，本实施例描述了1)使用所需的QoS过程设置AF会话(Setting up an AF session with required QoS procedure)；还可以通过如下流程提供：
2)或具有所需QoS更新过程的AF会话(AF session with required QoS update procedure)；(更新流程)
3)或特定于服务的参数预配(Service specific parameter provisioning)；(2.2.2业务特定参数提供流程)
4)或为将来的AF会话设置策略(Set a policy for a future AF session)；(AF会话请求前提前设定策略)。
示例性实施例中，如图10所示，本公开实施例为AF通过NEF给PCF提供common ID(or XRM service ID)，同时携带action indication，所述indication指示increasing or decreasing the number of SDFs in the group，支持PCF对XRM service的相关数据流的授权。
如图10所示，步骤0，XRM业务或多模态服务数据(or multimodal data Service)相关的部分或全部UE，已注册到网络，选择了PCF完成AM session关联.其中，PCF可以根据XRM业务的策略和QoS需求，向UDM订阅XRM service or multimodal data Service相关签约信息的变更通知。
1.AF可以触发Nnef_XRMServiceParameter service，创建AF请求，请求中包含XRM业务标识、common ID，UE地址或标识等信息。AF在请求消息中携带common ID(or XRM service ID)，同时携带action indication，所述indication指示increasing or decreasing the number of SDFs in the group。
AF通过Nnef_XRMServiceParameter service给业务相关的单个或多个UE提供XRM service or multiple data service specific parameters.AF发送的信息包括common ID，服务参数、UE/UE组和事件订阅(Service Parameters，UE/Group UE,and Subscription to events)。其中具体的：
1)-服务说明(Service Description)，标识XRM业务或XRM业务数据；可用DNN的组合(combination of DNN)和S-NSSAI组合，或者XRM ID来标识；或者AF-Service-Identifier或外部Application Identifier来表示。
2)服务参数。有关XRM服务或多模式数据的AF指南的信息服务相关策略和QoS确定。(Service Parameters.information on the AF guidance for XRM service or multimodal data Service related Policy and QoS determination。)关联XRM服务或多个数据服务应用程序流量、UE策略的规则列表(a list of rules that associate XRM service or multiple data Service application traffic,UE policy)等参数，common ID or Group ID，或DNN和S-NSSAI组合，SSC模式，相应规则的选择优先级(例如Alternative QoS参数优先级，相应location或Time Window优先级，相应计入类型或路由选择优先级等)。
3)AF请求所关联的XRM service or multiple data Service相关的单个UE，或多个UE(Group UE)。
4)订阅事件。AF可以订阅有关SM策略或AM策略或UE Policy的执行和变更结果的通知(Subscription to events.The AF may subscribe to notifications about the outcome of the SM policy或AM policy或UE Policy的执行和变更)；或者XRM service相关媒体数据流的事件订阅,e.g.Date rate,Latency。
当AF需要更新和删除相应请求或订阅时，也可通过该服务发起AF请求的更新和删除流程。
2.AF可以将请求发送给NEF。NEF授权AF请求。NEF执行相关映射，包括，标识XRM service or XRM data Service(AF-Service-Identifier)到DNN和S-NSSAI的映射，外部应用到CN应用标识的映射；以及基于UDM的签约信息，外部UE标识到CN内UE标识的映射(如SUPI)，以及根据UDM签约信息执行外部到内部的XRM service组标识的映射；
3.NEF可以存储应请求信息到UDR(例如，作为Application Data的业务特性参数信息存储)可选地，NEF可能会根据本地配置完善相应业务参数。
可选地，基于运营商策略，NEF可结合签约信息，为单个UE或Group多个UE的XRM service or multimodal data Service，确认是否请求业务特性可授权并将相应参数存储到UDR中。
如果涉及多个UE，则NEF传送相关业务参数到PCF，在每个PCF中执行相应授权，以及策略和规则的决策或更新。PCF根据请求授权结果，存储相应信息到UDR中。(支持但PCF和多PCF场景)
多UE场景,UE group成员的签约数据(Special QoS profile)可通过XRM service Indication或者Group ID/Common ID关联；
AF或PCF等consumer，可通过NEF，订阅相关XRM业务或多模态数据相关事件触发，如QoS监控报告、业务QoS更新、UE重定位、PCF变更等(XRM service or multimodal data related event trigger，例如QoS monitoring report,Service QoS update,UE relocation，PCF change等)。
AF或PCF等，通过接收NEF报告(report)，获取相应通知(notification)；执行后续应用需求或QoS规则的更新。
4.NEF给AF返回创建请求响应消息。
如果步骤0中，PCF在UE注册后执行了签约信息更新通知，则因为AF请求更新了UDR签约信息，而执行后续的流程
5.PCF收到UDR的签约信息变更通知。
PCF更新该common ID关联的group信息；可选地，将更新后的组信息存储在本地或UDR或UDM或UDSF中。
可选地，该action indication可以是indication显示携带，或者是将AF请求中相应SDF中原有的common ID删除或替换为不同common ID隐式携带，指示该SDF从原先group中移除；
可选地，从原先common ID关联group中移出的SDF，相应的AF会话可继续保留或释放；
6.PCF给UE传送UE policy，
7.如果AF订阅了通知XRM服务相关策略的执行通知(If the AF subscribed to notifications XRM service相关policy的执行通知)，则PCF通过NEF发送相关执行结果给AF。同时，若有相关签约参数变更，PCF更新变更到UDR，触发XRM service组相关的其它UE的serving PCF执行策略变更和协同。
8.NEF收到通知后，首先执行内外相关参数的映射(Mapping)，然后将相关报告给AF。
上述本公开提供的实施例中，分别从AF和PCF的角度对本公开实施例提供的方案进行了介绍。可以理解的是，各个设备为了实现上述功能，其包含了执行各个功能相应的硬件结构和/或软件模块。本领域技术人员应该很容易意识到，结合本文中所公开的实施例描述的各示例的算法步骤，本公开能够以硬件或硬件和计算机软件的结合形式来实现。某个功能究竟以硬件还是计算机软件驱动硬件的方式来执行，取决于技术方案的特定应用和设计约束条件。专业技术人员可以对每个特定的应用来使用不同方法来实现所描述的功能，但是这种实现不应认为超出本公开的范围。
请参见图11，为本公开实施例提供的一种通信装置1的结构示意图。图11所示的通信装置1可包括收发模块11和处理模块12。收发模块可包括发送模块和/或接收模块，发送模块用于实现发送功能，接收模块用于实现接收功能，收发模块可以实现发送功能和/或接收功能。
通信装置1，设置于PCF侧：包括：收发模块11和处理模块12。
收发模块11，被配置为接收应用功能AF发送的请求消息，其中，请求消息用于指示以下至少一项：
将业务数据流添加至第一业务数据流组；
将业务数据流从第二业务数据流组中移除；
处理模块12，被配置为根据请求消息，生成或更新策略与计费控制PCC规则。
在一些实施例中，请求消息中包括业务数据流对应的组标识，组标识关联第一业务数据流组或第二业务数据流组。
在一些实施例中，请求消息中包括业务数据流对应的动作指示。
在一些实施例中，在组标识关联第一业务数据流组的情况下，动作指示用于指示以下至少一项：
将业务数据流添加至第一业务数据流组；
将业务数据流从第二业务数据流组中移除。
在一些实施例中，在接收AF发送的请求消息之前，业务数据流位于第二业务数据流组中，或不属于任何业务数据流组。
在一些实施例中，在组标识关联第二业务数据流组的情况下，动作标识用于指示将业务数据流从第二业务数据流组中移除。
在一些实施例中，处理模块12，还被配置为根据请求消息，更新第一业务数据流组和/或第二业务数据流组。
在一些实施例中，处理模块12，还被配置为将更新后的第一业务数据流组和/或第二业务数据流组存储到以下至少一项中：
本地；
统一数据库UDR；
统一数据管理功能UDM；
非结构化数据存储功能UDSF。
在一些实施例中，处理模块12，还被配置为响应于请求消息用于指示将业务数据流从第二业务数据流组中移除，继续保留或释放请求消息对应的AF会话。
在一些实施例中，收发模块11，还被配置为接收AF通过网络开放功能NEF发送的请求消息；或者接收AF通过时敏通信和时同步功能TSCTSF发送的请求消息；或者接收AF通过NEF和TSCTSF发送的请求消息。
在一些实施例中，收发模块11，还被配置为接收AF发送的AF会话创建请求或AF会话更新请求，其中，AF会话创建请求或AF会话更新请求中包括请求消息。
在一些实施例中，收发模块11，还被配置为在以下至少一项流程中，接收所述AF发送的所述请求消息：
AF会话建立请求的流程；
AF会话建立更新请求的流程；
业务特定参数的提供流程；
为后续的AF会话设置策略的流程。
通信装置1，设置于AF侧：包括：收发模块11和处理模块12。
收发模块11，被配置为向PCF发送请求消息，其中，请求消息用于指示以下至少一项：
将业务数据流添加至第一业务数据流组；
将业务数据流从第二业务数据流组中移除。
在一些实施例中，请求消息中包括业务数据流对应的组标识，组标识关联第一业务数据流组或第二业务数据流组。
在一些实施例中，请求消息中包括业务数据流对应的动作指示。
在一些实施例中，在组标识关联第一业务数据流组的情况下，动作指示用于指示以下至少一项：
将业务数据流添加至第一业务数据流组；
将业务数据流从第二业务数据流组中移除。
在一些实施例中，在向PCF发送请求消息之前，业务数据流位于第二业务数据流组中，或不属于任何业务数据流组。
在一些实施例中，在组标识关联第二业务数据流组的情况下，动作标识用于指示将业务数据流从第二业务数据流组中移除。
在一些实施例中，处理模块12，被配置为响应于请求消息用于指示将业务数据流从第二业务数据流组中移除，继续保留或释放请求消息对应的AF会话。
在一些实施例中，收发模块11，还被配置为通过NEF向PCF发送请求消息；或者通过TSCTSF向PCF发送请求消息；或者通过NEF和TSCTSF向PCF发送请求消息。
在一些实施例中，收发模块11，还被配置为向PCF发送AF会话创建请求或AF会话更新请求，其中，AF会话创建请求或AF会话更新请求中包括请求消息。
在一些实施例中，收发模块11，还被配置为在以下至少一项流程中，向所述PCF发送所述请求消息：
AF会话建立请求的流程；
AF会话建立更新请求的流程；
业务特定参数的提供流程；
为后续的AF会话设置策略的流程。
关于上述实施例中的通信装置1，其中各个模块执行操作的具体方式已经在有关该方法的实施例中进行了详细描述，此处将不做详细阐述说明。
本公开上述实施例中提供的通信装置1，与上面一些实施例中提供的多模态业务数据流的管理方法取得相同或相似的有益效果，此处不再赘述。
请参见图12，图12是本公开实施例提供的另一种通信装置1000的结构图。通信装置1000可以是终端设备，也可以是SMF，也可以是PCF。该装置可用于实现上述方法实施例中描述的方法，具体可以参见上述方法实施例中的说明。
通信装置1000可以包括一个或多个处理器1001。处理器1001可以是通用处理器或者专用处理器等。例如可以是基带处理器或中央处理器。基带处理器可以用于对通信协议以及通信数据进行处理，中央处理器可以用于对通信装置(如，基站、基带芯片，终端设备、终端设备芯片，DU或CU等)进行控制，执行计算机程序，处理计算机程序的数据。
可选的，通信装置1000中还可以包括一个或多个存储器1002，其上可以存有计算机程序1004，存储器1002执行所述计算机程序1004，以使得通信装置1000执行上述方法实施例中描述的方法。可选的，所述存储器1002中还可以存储有数据。通信装置1000和存储器1002可以单独设置，也可以集成在一起。
可选的，通信装置1000还可以包括收发器1005、天线1006。收发器1005可以称为收发单元、收发机、或收发电路等，用于实现收发功能。收发器1005可以包括接收器和发送器，接收器可以称为接收机或接收电路等，用于实现接收功能；发送器可以称为发送机或发送电路等，用于实现发送功能。
可选的，通信装置1000中还可以包括一个或多个接口电路1007。接口电路1007用于接收代码指令并传输至处理器1001。处理器1001运行所述代码指令以使通信装置1000执行上述方法实施例中描述的方法。
通信装置1000为PCF，收发器1005用于执行图3中的S31；图4中的S41；图5中的S51；图6中的S61；处理器1001用于执行图3中的S32；图4中的S42；图5中的S52和S53；图6中的S62。
通信装置1000为AF：收发器1005用于执行图7中的S71；图8中的S81；处理器1001用于执行图8中的S82。
在一种实现方式中，处理器1001中可以包括用于实现接收和发送功能的收发器。例如该收发器可以是收发电路，或者是接口，或者是接口电路。用于实现接收和发送功能的收发电路、接口或接口电路可以是分开的，也可以集成在一起。上述收发电路、接口或接口电路可以用于代码/数据的读写，或者，上述收发电路、接口或接口电路可以用于信号的传输或传递。
在一种实现方式中，处理器1001可以存有计算机程序1003，计算机程序1003在处理器1001上运行，可使得通信装置1000执行上述方法实施例中描述的方法。计算机程序1003可能固化在处理器1001中，该种情况下，处理器1001可能由硬件实现。
在一种实现方式中，通信装置1000可以包括电路，所述电路可以实现前述方法实施例中发送或接收或者通信的功能。本公开中描述的处理器和收发器可实现在集成电路(integrated circuit，IC)、模拟IC、射频集成电路RFIC、混合信号IC、专用集成电路(application specific integrated circuit，ASIC)、印刷电路板(printed circuit board，PCB)、电子设备等上。该处理器和收发器也可以用各种IC工艺技术来制造，例如互补金属氧化物半导体(complementary metal oxide semiconductor，CMOS)、N型金属氧化物半导体(nMetal-oxide-semiconductor，NMOS)、P型金属氧化物半导体(positive channel metal oxide semiconductor，PMOS)、双极结型晶体管(bipolar junction transistor，BJT)、双极CMOS(BiCMOS)、硅锗(SiGe)、砷化镓(GaAs)等。
以上实施例描述中的通信装置可以是终端设备，也可以是SMF，也可以是PCF，也可以是核心网，但本公开中描述的通信装置的范围并不限于此，而且通信装置的结构可以不受图12的限制。通信装置可以是独立的设备或者可以是较大设备的一部分。例如所述通信装置可以是：
(1)独立的集成电路IC，或芯片，或，芯片系统或子系统；
(2)具有一个或多个IC的集合，可选的，该IC集合也可以包括用于存储数据，计算机程序的存储部件；
(3)ASIC，例如调制解调器(Modem)；
(4)可嵌入在其他设备内的模块；
(5)接收机、终端设备、智能终端设备、蜂窝电话、无线设备、手持机、移动单元、车载设备、网络设备、云设备、人工智能设备等等；
(6)其他等等。
对于通信装置可以是芯片或芯片系统的情况，请参见图13，为本公开实施例中提供的一种芯片的结构图。
如图13所示，芯片1100包括处理器1101和接口1103。其中，处理器1101的数量可以是一个或多个，接口1103的数量可以是多个。
对于芯片用于实现本公开实施例中终端设备的功能的情况：
接口1103，用于接收代码指令并传输至所述处理器。
处理器1101，用于运行代码指令以执行如上面一些实施例所述的多模态业务数据流的管理方法。
对于芯片用于实现本公开实施例中SMF的功能的情况：
接口1103，用于接收代码指令并传输至所述处理器。
处理器1101，用于运行代码指令以执行如上面一些实施例所述的多模态业务数据流的管理方法。
对于芯片用于实现本公开实施例中PCF的功能的情况：
接口1103，用于接收代码指令并传输至所述处理器。
处理器1101，用于运行代码指令以执行如上面一些实施例所述的多模态业务数据流的管理方法。
可选的，芯片1100还包括存储器1102，存储器1102用于存储必要的计算机程序和数据。
本领域技术人员还可以了解到本公开实施例列出的各种说明性逻辑块(illustrative logical block)和步骤(step)可以通过电子硬件、电脑软件，或两者的结合进行实现。这样的功能是通过硬件还是软件来实现取决于特定的应用和整个系统的设计要求。本领域技术人员可以对于每种特定的应用，可以使用各种方法实现所述的功能，但这种实现不应被理解为超出本公开实施例保护的范围。
本公开实施例还提供一种多模态业务数据流的管理系统，该系统包括前述图11实施例中作为终端设备的通信装置、SMF的通信装置和作为PCF的通信装置，或者，该系统包括前述图12实施例中作为终端设备的通信装置、SMF的通信装置和作为PCF的通信装置。
本公开还提供一种可读存储介质，其上存储有指令，该指令被计算机执行时实现上述任一方法实施例的功能。
本公开还提供一种计算机程序产品，该计算机程序产品被计算机执行时实现上述任一方法实施例的功能。
在上述实施例中，可以全部或部分地通过软件、硬件、固件或者其任意组合来实现。当使用软件实现时，可以全部或部分地以计算机程序产品的形式实现。所述计算机程序产品包括一个或多个计算机程序。在计算机上加载和执行所述计算机程序时，全部或部分地产生按照本公开实施例所述的流程或功能。所述计算机可以是通用计算机、专用计算机、计算机网络、或者其他可编程装置。所述计算机程序可以存储在计算机可读存储介质中，或者从一个计算机可读存储介质向另一个计算机可读存储介质传输，例如，所述计算机程序可以从一个网站站点、计算机、服务器或数据中心通过有线(例如同轴电缆、光纤、数字用户线(digital subscriber line，DSL))或无线(例如红外、无线、微波等)方式向另一个网站站点、计算机、服务器或数据中心进行传输。所述计算机可读存储介质可以是计算机能够存取的任何可用介质或者是包含一个或多个可用介质集成的服务器、数据中心等数据存储设备。所述可用介质可以是磁性介质(例如，软盘、硬盘、磁带)、光介质(例如，高密度数字视频光盘(digital video disc，DVD))、或者半导体介质(例如，固态硬盘(solid state disk，SSD))等。
除非上下文另有要求，否则，在整个说明书和权利要求书中，术语“包括(comprise)”及其其他形式例如第三人称单数形式“包括(comprises)”和现在分词形式“包括(comprising)”被解释为开放、包含的意思，即为“包含，但不限于”。在说明书的描述中，术语“一些实施例(some embodiments)”、“示例性实施例(exemplary embodiments)”等旨在表明与该实施例或示例相关的特定特征、结构、材料或特性包括在本公开的至少一个实施例或示例中。上述术语的示意性表示不一定是指同一实施例或示例。此外，所述的特定特征、结构、材料或特点可以以任何适当方式包括在任何一个或多个实施例或示例中。
本领域普通技术人员可以理解：本公开中涉及的第一、第二等各种数字编号仅为描述方便进行的区分，并不用来限制本公开实施例的范围，也表示先后顺序。
本公开中的至少一个还可以描述为一个或多个，多个可以是两个、三个、四个或者更多个，本公开不做限制。在本公开实施例中，对于一种技术特征，通过“第一”、“第二”、“第三”、“A”、“B”、“C”和“D”等区分该种技术特征中的技术特征，该“第一”、“第二”、“第三”、“A”、“B”、“C”和“D”描述的技术特征间无先后顺序或者大小顺序。“A和/或B”，包括以下三种组合：仅A，仅B，及A和B的组合。
本领域普通技术人员可以意识到，结合本文中所公开的实施例描述的各示例的单元及算法步骤，能够以电子硬件、或者计算机软件和电子硬件的结合来实现。这些功能究竟以硬件还是软件方式来执行，取决于技术方案的特定应用和设计约束条件。专业技术人员可以对每个特定的应用来使用不同方法来实现所描述的功能，但是这种实现不应认为超出本公开的范围。
所属领域的技术人员可以清楚地了解到，为描述的方便和简洁，上述描述的系统、装置和单元的具体工作过程，可以参考前述方法实施例中的对应过程，在此不再赘述。
以上所述，仅为本公开的具体实施方式，但本公开的保护范围并不局限于此，任何熟悉本技术领域的技术人员在本公开揭露的技术范围内，可轻易想到变化或替换，都应涵盖在本公开的保护范围之内。因此，本公开的保护范围应以所述权利要求的保护范围为准。

Claims (25)

  1. 一种多模态业务数据流的管理方法，其特征在于，所述方法由策略控制功能PCF执行，包括：
    接收应用功能AF发送的请求消息，其中，所述请求消息用于指示以下至少一项：
    将业务数据流添加至第一业务数据流组；
    将业务数据流从第二业务数据流组中移除；
    根据所述请求消息，生成或更新策略与计费控制PCC规则。
  2. 如权利要求1所述的方法，其特征在于，所述请求消息中包括所述业务数据流对应的组标识，所述组标识关联所述第一业务数据流组或所述第二业务数据流组。
  3. 如权利要求2所述的方法，其特征在于，所述请求消息中包括所述业务数据流对应的动作指示。
  4. 如权利要求3所述的方法，其特征在于，在所述组标识关联所述第一业务数据流组的情况下，所述动作指示用于指示以下至少一项：
    将所述业务数据流添加至所述第一业务数据流组；
    将所述业务数据流从所述第二业务数据流组中移除。
  5. 如权利要求4所述的方法，其特征在于，在接收所述AF发送的所述请求消息之前，所述业务数据流位于所述第二业务数据流组中，或不属于任何业务数据流组。
  6. 如权利要求3所述的方法，其特征在于，在所述组标识关联所述第二业务数据流组的情况下，所述动作标识用于指示将所述业务数据流从所述第二业务数据流组中移除。
  7. 如权利要求1至6中任一项所述的方法，其特征在于，所述方法还包括：
    根据所述请求消息，更新所述第一业务数据流组和/或所述第二业务数据流组。
  8. 如权利要求7所述的方法，其特征在于，所述方法还包括：
    将更新后的所述第一业务数据流组和/或所述第二业务数据流组存储到以下至少一项中：
    本地；
    统一数据库UDR；
    统一数据管理功能UDM；
    非结构化数据存储功能UDSF。
  9. 如权利要求1至8中任一项所述的方法，其特征在于，所述方法还包括：
    响应于所述请求消息用于指示将业务数据流从第二业务数据流组中移除，继续保留或释放所述请求消息对应的AF会话。
  10. 如权利要求1至9中任一项所述的方法，其特征在于，所述接收AF发送的请求消息，包括：
    接收所述AF通过网络开放功能NEF发送的所述请求消息；或者
    接收所述AF通过时敏通信和时同步功能TSCTSF发送的所述请求消息；或者
    接收所述AF通过NEF和TSCTSF发送的所述请求消息。
  11. 如权利要求1至10中任一项所述的方法，其特征在于，所述接收AF发送的请求消息，包括：
    接收所述AF发送的AF会话创建请求或AF会话更新请求，其中，所述AF会话创建请求或所述AF会话更新请求中包括所述请求消息。
  12. 如权利要求1至11中任一项所述的方法，其特征在于，所述接收AF发送的请求消息，包括：
    在以下至少一项流程中，接收所述AF发送的所述请求消息：
    AF会话建立请求的流程；
    AF会话建立更新请求的流程；
    业务特定参数的提供流程；
    为后续的AF会话设置策略的流程。
  13. 一种多模态业务数据流的管理方法，其特征在于，所述方法由应用功能AF执行，包括：
    向PCF发送请求消息，其中，所述请求消息用于指示以下至少一项：
    将业务数据流添加至第一业务数据流组；
    将业务数据流从第二业务数据流组中移除。
  14. 如权利要求13所述的方法，其特征在于，所述请求消息中包括所述业务数据流对应的组标识，所述组标识关联所述第一业务数据流组或所述第二业务数据流组。
  15. 如权利要求14所述的方法，其特征在于，所述请求消息中包括所述业务数据流对应的动作指示。
  16. 如权利要求15所述的方法，其特征在于，在所述组标识关联所述第一业务数据流组的情况下，所述动作指示用于指示以下至少一项：
    将所述业务数据流添加至所述第一业务数据流组；
    将所述业务数据流从所述第二业务数据流组中移除。
  17. 如权利要求16所述的方法，其特征在于，在向所述PCF发送所述请求消息之前，所述业务数据流位于所述第二业务数据流组中，或不属于任何业务数据流组。
  18. 如权利要求15所述的方法，其特征在于，在所述组标识关联所述第二业务数据流组的情况下，所述动作标识用于指示将所述业务数据流从所述第二业务数据流组中移除。
  19. 如权利要求13至18中任一项所述的方法，其特征在于，所述方法还包括：
    响应于所述请求消息用于指示将业务数据流从第二业务数据流组中移除，继续保留或释放所述请求消息对应的AF会话。
  20. 如权利要求13至19中任一项所述的方法，其特征在于，所述向PCF发送请求消息，包括：
    通过NEF向所述PCF发送所述请求消息；或者
    通过TSCTSF向所述PCF发送所述请求消息；或者
    通过NEF和TSCTSF向所述PCF发送所述请求消息。
  21. 如权利要求13至20中任一项所述的方法，其特征在于，所述向PCF发送请求消息，包括：
    向所述PCF发送AF会话创建请求或AF会话更新请求，其中，所述AF会话创建请求或所述AF会话更新请求中包括所述请求消息。
  22. 如权利要求13至21中任一项所述的方法，其特征在于，所述向PCF发送请求消息，包括：
    在以下至少一项流程中，向所述PCF发送所述请求消息：
    AF会话建立请求的流程；
    AF会话建立更新请求的流程；
    业务特定参数的提供流程；
    为后续的AF会话设置策略的流程。
  23. 一种通信装置，设置于PCF侧，其特征在于，包括：
    收发模块，被配置为接收应用功能AF发送的请求消息，其中，所述请求消息用于指示以下至少一项：
    将业务数据流添加至第一业务数据流组；
    将业务数据流从第二业务数据流组中移除；
    处理模块，被配置为根据所述请求消息，生成或更新策略与计费控制PCC规则。
  24. 一种通信装置，设置于AF侧，其特征在于，包括：
    收发模块，被配置为向PCF发送请求消息，其中，所述请求消息用于指示以下至少一项：
    将业务数据流添加至第一业务数据流组；
    将业务数据流从第二业务数据流组中移除。
  25. 一种通信装置，其特征在于，所述装置，包括：处理器和存储器，所述存储器中存储有计算机程序，所述处理器执行所述存储器中存储的计算机程序，以使所述装置执行如权利要求1至12中任一项所述的方法；或所述处理器执行所述存储器中存储的计算机程序，以使所述装置执行如权利要求13至22中任一项所述的方法。
PCT/CN2023/072422 2023-01-16 2023-01-16 多模态业务数据流的管理方法和装置 WO2024152162A1 (zh)

Priority Applications (1)

Application Number Priority Date Filing Date Title
PCT/CN2023/072422 WO2024152162A1 (zh) 2023-01-16 2023-01-16 多模态业务数据流的管理方法和装置

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/CN2023/072422 WO2024152162A1 (zh) 2023-01-16 2023-01-16 多模态业务数据流的管理方法和装置

Publications (1)

Publication Number Publication Date
WO2024152162A1 true WO2024152162A1 (zh) 2024-07-25

Family

ID=91955106

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2023/072422 WO2024152162A1 (zh) 2023-01-16 2023-01-16 多模态业务数据流的管理方法和装置

Country Status (1)

Country Link
WO (1) WO2024152162A1 (zh)

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2016119818A1 (en) * 2015-01-26 2016-08-04 Telefonaktiebolaget Lm Ericsson (Publ) Dynamic policy rule selection
CN109392014A (zh) * 2017-08-14 2019-02-26 电信科学技术研究院 一种QoS流的接纳控制方法及通信装置
CN113873453A (zh) * 2020-06-29 2021-12-31 华为技术有限公司 通信方法、装置及系统
WO2022095795A1 (zh) * 2020-11-08 2022-05-12 腾讯科技（深圳）有限公司 通信方法、装置、计算机可读介质及电子设备

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2016119818A1 (en) * 2015-01-26 2016-08-04 Telefonaktiebolaget Lm Ericsson (Publ) Dynamic policy rule selection
CN109392014A (zh) * 2017-08-14 2019-02-26 电信科学技术研究院 一种QoS流的接纳控制方法及通信装置
CN113873453A (zh) * 2020-06-29 2021-12-31 华为技术有限公司 通信方法、装置及系统
WO2022095795A1 (zh) * 2020-11-08 2022-05-12 腾讯科技（深圳）有限公司 通信方法、装置、计算机可读介质及电子设备

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
DAN WANG, CHINA MOBILE,NOKIA,NOKIA SHANGHAI BELL, SAMSUNG, XIAOMI: "Policy control enhancements to support multi-modality flows coordinated transmission", 3GPP DRAFT; S2-2300281; TYPE CR; CR 3864; XRM, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE, vol. 3GPP SA 2, no. Online; 20230116 - 20230120, 9 January 2023 (2023-01-09), Mobile Competence Centre ; 650, route des Lucioles ; F-06921 Sophia-Antipolis Cedex ; France, XP052231758 *

Similar Documents

Publication Publication Date Title
US20230093339A1 (en) Session Management Method, Apparatus, and System
US11223941B2 (en) Data feeds of consumer eSIMS for a subscription management service
KR102469191B1 (ko) 정보 전송방법 및 장치, 컴퓨터 판독가능 저장 매체
EP3691306B1 (en) Charging methods, apparatuses and system
CN112312418A (zh) 一种用户面数据的获取方法、装置及存储介质
EP3648521A1 (en) Resource configuration method and device
WO2021051420A1 (zh) 一种dns缓存记录的确定方法及装置
US20230047783A1 (en) Data transmission method and apparatus
WO2021227600A1 (zh) 一种网络切片控制方法及通信装置
WO2023213177A1 (zh) 一种通信方法及装置
WO2020142884A1 (zh) 切换传输路径的方法及装置
WO2024152162A1 (zh) 多模态业务数据流的管理方法和装置
WO2021138784A1 (zh) 一种接入网络的方法、装置及系统
CN113596909B (zh) 通信方法、装置及系统
CN114982284B (zh) 通信方法及装置
KR102318746B1 (ko) 가상 id를 이용하여 복수의 pdu 세션들을 처리하는 방법 및 상기 방법을 수행하는 smf
WO2023212960A1 (zh) 扩展现实业务策略实现方法及装置
WO2023184191A1 (zh) 一种扩展现实多媒体xrm业务的处理方法及其装置
WO2024145902A1 (zh) 密钥获取方法、装置、设备及芯片系统
WO2024130561A1 (zh) 一种用户位置信息的可信确定方法及其装置
WO2024065139A1 (zh) 辅助运营方法和装置
WO2024050778A1 (zh) 一种人工智能服务策略的更新方法及装置
WO2024138581A1 (zh) 一种网络切片的授权方法、装置、设备及存储介质
WO2023010994A1 (zh) 一种网络切片接入控制方法及通信装置
US20220353340A1 (en) Communication Method and Communication Apparatus