WO2022170798A1 - 确定策略的方法和通信装置 - Google Patents

确定策略的方法和通信装置 Download PDF

Info

Publication number
WO2022170798A1
WO2022170798A1 PCT/CN2021/129713 CN2021129713W WO2022170798A1 WO 2022170798 A1 WO2022170798 A1 WO 2022170798A1 CN 2021129713 W CN2021129713 W CN 2021129713W WO 2022170798 A1 WO2022170798 A1 WO 2022170798A1
Authority
WO
WIPO (PCT)
Prior art keywords
application
network element
information
service
service chain
Prior art date
Application number
PCT/CN2021/129713
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 华为技术有限公司
Publication of WO2022170798A1 publication Critical patent/WO2022170798A1/zh

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
    • H04W4/50—Service provisioning or reconfiguring
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04M—TELEPHONIC COMMUNICATION
    • H04M15/00—Arrangements for metering, time-control or time indication ; Metering, charging or billing arrangements for voice wireline or wireless communications, e.g. VoIP
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04M—TELEPHONIC COMMUNICATION
    • H04M15/00—Arrangements for metering, time-control or time indication ; Metering, charging or billing arrangements for voice wireline or wireless communications, e.g. VoIP
    • H04M15/66—Policy and charging system
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04M—TELEPHONIC COMMUNICATION
    • H04M15/00—Arrangements for metering, time-control or time indication ; Metering, charging or billing arrangements for voice wireline or wireless communications, e.g. VoIP
    • H04M15/68—Payment of value-added services
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
    • H04W4/24—Accounting or billing

Definitions

  • the present application relates to the field of communication technologies, and in particular, to a method and a communication device for determining a strategy.
  • a protocol data unit (PDU) session (PDU session) is established, and the user accesses the external data network through the PDU session to communicate with Interaction with application servers deployed in the data network.
  • PDU session protocol data unit
  • QoE quality of experience
  • the present application provides a method and a communication device for determining a strategy, so as to quickly respond to the rapidly changing requirements of the business chain.
  • a method for determining a policy is provided, and the method may be executed by a network device, or may also be executed by a chip, a chip system, or a circuit used for the network device, which is not limited in this application.
  • the following description is performed by taking the execution by the first network element as an example.
  • the method may include: the first network element receives a first request message from the second network element, where the first request message includes information of a service chain required by the application; the first network element sends the service chain corresponding to the application to the third network element Strategy, the business chain strategy corresponding to the application is formulated according to the information of the business chain required by the application.
  • the first network element may be, for example, a policy control function (policy control function, PCF) network element, or a visited-policy control function (visited-policy control function, V-PCF) network element, or the like.
  • policy control function policy control function
  • V-PCF visited-policy control function
  • the second network element may be, for example, an application function (application function, AF) network element, or a capability exposure function (network exposure function, NEF) network element, or the like.
  • application function application function
  • NEF network exposure function
  • the third network element can be, for example, a session management function (session management function, SMF) network element, or other network devices that can implement the function of the network element.
  • SMF session management function
  • the first request message may be a data-oriented message, or may also be a quality of service request message.
  • the method may further include: formulating a service chain policy corresponding to the application according to the service chain information required by the application.
  • Formulate the business chain policy corresponding to the application for example, it can be understood as formulating a traffic steering policy (TSP) for the application accessed by the user.
  • TSP traffic steering policy
  • the information of the service chain required by the application can be carried when requesting to formulate a service chain policy. Therefore, the first network element can determine whether to authorize according to the information of the service chain required by the application carried in the request, or the first network element can directly formulate a service chain policy according to the information of the service chain required by the application carried in the request. Therefore, it is possible to quickly respond to the rapidly changing demands of the application on the business chain.
  • the information of the service chain required by the application is the service chain identifier required by the application.
  • the first network element may formulate a service chain policy corresponding to the application based on the service chain identifier required by the application.
  • the information of the service chain required by the application is information of one or more service functions required by the application.
  • the first network element may formulate a service chain policy corresponding to the application based on the information of one or more service functions required by the application.
  • the method further includes: the first network element, according to the information of one or more service functions required by the application, determines information of one or more service functions that support the application , and send information supporting one or more service functions of the application to the second network element.
  • the first network element may determine the information of one or more service functions of the supported application based on the information of one or more service functions required by the application, for example, the one or more service functions of the supported application, A business function that is part of one or more business functions required by an application. Therefore, the second network element can flexibly adjust and process based on the information of one or more service functions supported by the first network element.
  • the information of one or more service functions is an identifier or type of one or more service functions.
  • the service function can be identified by an identifier or a type.
  • the first network element receives a first request message from the second network element, where the first request message includes information about a service chain required by the application, including: a first The network element receives the first request message from the second network element, where the first request message includes the correspondence between the information of the service chain required by the application and the data network access identifier.
  • the information of the service chain required by the application included in the first request message is specifically the correspondence between the information of the service chain required by the application and the data network access identifier.
  • the first request message specifically includes the correspondence between the service chain identifier required by the application and the data network access identifier.
  • the first request message specifically includes the correspondence between one or more service functions required by the application and the data network access identifier.
  • the first request message can carry the correspondence between the information of the service chain required by the application and the data network access identifier, so that the service chain corresponding to the application can be determined according to the information of the service chain required by the application strategy, and then the corresponding relationship between the service chain strategy and the data network access identifier can be obtained.
  • the first network element sends to the third network element the correspondence between the service chain policy corresponding to the application and the data network access identifier.
  • the correspondence between the service chain policy corresponding to the application and the data network access identifier is determined according to the correspondence between the service chain information required by the application and the data network access identifier.
  • the method further includes: the first network element sends a second request message to the fourth network element, where the second request message includes the service chain policy corresponding to the application and the information for accessing the application.
  • the identifier of the user, and the second request message is used to request authorization for the service chain policy corresponding to the application accessed by the user.
  • the first network element formulates the service chain policy according to the request, it can send the service chain policy to the fourth network element for further authorization by the fourth network element.
  • the method further includes: before the first network element sends the second request message to the fourth network element, the method further includes: the first network element receives the third network element The first data network access identifier sent, the first network element determines the service chain policy corresponding to the user access application according to the first data network access identifier; or, the first network element receives the user access application sent by the third network element. business chain strategy.
  • the service chain policy corresponding to the application there is a correspondence between the service chain policy corresponding to the application and the data network access identifier, where the data network access identifier includes the first data network access identifier.
  • the method further includes: the first network element sends a third request message to the fourth network element, where the third request message includes information about one or more supported service functions and the identity of the user accessing the application, the third request message is used to request authorization for information on one or more service functions supported by the accessed application.
  • the first network element determines the supported service function according to the request, it can send the information of the service function to the fourth network element, so as to further perform further operations on the fourth network element. authorized.
  • the method before the first network element sends the third request message to the fourth network element, the method further includes: the first network element receives the first network element sent by the third network element A data network access identifier, one or more service functions of applications that support user access are determined according to the first data network access identifier; or, the first network element receives a service chain policy corresponding to the user access application sent by the third network element, One or more service functions of the application that supports the user's access are determined according to the service chain policy corresponding to the user-accessed application.
  • the service chain policy corresponding to the application there is a correspondence between the service chain policy corresponding to the application and the data network access identifier, where the data network access identifier includes the first data network access identifier.
  • a method for determining a policy is provided, and the method may be executed by a network device, or may also be executed by a chip, a chip system, or a circuit used for the network device, which is not limited in this application.
  • the following description is performed by taking the execution by the second network element as an example.
  • the method may include: sending a first request message to a first network element, where the first request message includes service chain information required by the application; and receiving indication information from the first network element, where the indication information is used to indicate acceptance of the service chain required by the application business chain request.
  • the second network element may be, for example, an AF network element, a NEF network element, or the like.
  • the information of the service chain required by the application can be carried when requesting to formulate a service chain policy. Therefore, the first network element can be made to determine whether to authorize according to the information of the service chain required by the application carried in the request, or directly formulate a service chain policy according to the information of the service chain required by the application carried in the request.
  • the solution provided by the embodiments of the present application can quickly respond to the rapidly changing requirements of the application on the service chain.
  • the information of the service chain required by the application is any one of the following: the service chain identifier required by the application, the external service chain identifier required by the application, the service chain identifier required by the application.
  • the method further includes: the second network element receives information from the first network element that supports one or more service functions of the application.
  • the information of the service chain required by the application is the information of one or more service functions required by the application.
  • the method further includes: the second network element receiving information from the first network element that supports one or more external service functions of the application.
  • the information of the service chain required by the application is the information of one or more external service functions required by the application.
  • the information of one or more service functions is the identification or type of one or more service functions.
  • the method before sending the first request message to the first network element, the method further includes: the second network element sends a second request message to the fifth network element, the second The request message includes the information of the queried service chain; the second network element receives one or more of the following information of the queried service chain from the fifth network element: service function identifier, service chain identifier, service function identifier and data network connection.
  • service function identifier the information of the queried service chain
  • service function identifier includes the information of the queried service chain
  • service function identifier includes the information of the queried service chain
  • service function identifier includes the information of the queried service chain
  • service function identifier includes the information of the queried service chain
  • service function identifier includes the information of the queried service chain
  • service function identifier includes the information of the queried service chain
  • data network connection includes the access identifier, service chain identifier, service function identifier and data network connection.
  • the information of the queried business chain includes the type of the queried business function.
  • the second network element can dynamically request the service chain. For example, the second network element can obtain the corresponding service function or service chain through query.
  • a method for determining a policy is provided, and the method may be executed by a network device, or may also be executed by a chip, a chip system or a circuit used for the network device, which is not limited in this application.
  • the execution by the fifth network element is taken as an example for description below.
  • the method may include: the fifth network element receives a request message from the second network element, where the request message includes the information of the service chain required by the application; the fifth network element processes the information of the service chain required by the application, and sends the request message to the third network element.
  • a network element sends the information of the processed service chain.
  • the fifth network element can be, for example, an NEF network element, or other network devices that can implement the function of the network element.
  • the requested information can carry the information of the service chain required by the application, and then the fifth network element can first perform the processing of the service chain required by the application.
  • the information of the service chain required by the application is processed, and then the processed information is sent to the first network element.
  • the first network element can determine the corresponding service chain policy based on the request of the second network element, or perform authorization. Therefore, it is possible to quickly respond to the rapidly changing demands of the application on the business chain.
  • the information of the service chain required by the application is an external service chain identifier required by the application
  • the fifth network element processes the information of the service chain required by the application, Including: the fifth network element maps the external service chain identifier to the internal service chain identifier; the fifth network element sends the processed service chain information to the first network element, including: the fifth network element sends the internal service chain to the first network element.
  • Business chain logo is an external service chain identifier required by the application
  • the fifth network element processes the information of the service chain required by the application, Including: the fifth network element maps the external service chain identifier to the internal service chain identifier; the fifth network element sends the processed service chain information to the first network element, including: the fifth network element sends the internal service chain to the first network element.
  • the information of the service chain required by the application is the information of the external service function required by the application
  • the fifth network element processes the information of the service chain required by the application , including: the fifth network element maps the external service function to the internal service function; the fifth network element sends the information of the processed service chain to the first network element, including: the fifth network element sends the internal service to the first network element function information.
  • the method further includes: a fifth network element determining one or more external service functions that support the application according to information of one or more external service functions required by the application information, and send information supporting one or more external service functions of the application to the second network element.
  • the information of the one or more external service functions is the identification or type of the one or more external service functions.
  • the information of the service chain required by the application is the correspondence between the external service chain identifier required by the application and the data network access identifier, or, the information required by the application
  • the information of the service chain is the correspondence between one or more external service functions required by the application and the data network access identifier.
  • the information of the service chain required by the application is the correspondence between the external service chain identifier required by the application and the data network access identifier, and the fifth network element pairs
  • the processing of the information of the service chain required by the application includes: the fifth network element maps the external service chain identifier to the internal service chain identifier; the fifth network element sends the processed service chain information to the first network element, including: The fifth network element sends the first network element the correspondence between the internal service chain identifier required by the application and the data network access identifier.
  • the information of the service chain required by the application is the correspondence between the external service function required by the application and the data network access identifier
  • the fifth network element is used for the application. Processing the required service chain information, including: the fifth network element maps external service functions to internal service functions; the fifth network element sends the processed service chain information to the first network element, including: the fifth network element The element sends the corresponding relationship between the internal service function required by the application and the data network access identifier to the first network element.
  • the method further includes: the fifth network element receives a registration request message from the service chain management device, where the registration request message includes one of the following items of the registered service chain or Multiple pieces of information: correspondence between business function types and business function identifiers, correspondence between business function types and external business chain identifiers, business function types, correspondence between business function identifiers and data network access identifiers, business function identifiers, external business The correspondence between the chain identifier and the correspondence between the data network access identifier.
  • a method for determining a policy is provided, and the method may be executed by a network device, or may also be executed by a chip, a chip system, or a circuit used for the network device, which is not limited in this application.
  • the following description is performed by taking the execution by the third network element as an example.
  • the method may include: the third network element receiving information on the correspondence between the service chain policy corresponding to the application of the first network element and the data network access identifier, wherein the data network access identifier includes the first data network access identifier identifier; the third network element selects the user plane network element according to the first data network access identifier, and instructs the user plane network element to execute the first service chain policy, where the first service chain policy is the service chain corresponding to the first data network access identifier Strategy.
  • the third network element can be, for example, an SMF network element, or other network devices that can implement the function of the network element.
  • the method further includes: the third network element sends the first data network access identifier to the first network element; or the third network element sends the first network element The first business chain strategy.
  • a method for determining a policy is provided, and the method may be executed by a network device, or may also be executed by a chip, a chip system, or a circuit used for the network device, which is not limited in this application.
  • the following description is performed by taking the execution by the first network element as an example.
  • the method may include: the first network element sends a request message to the fourth network element, where the request message is used to request authorization of one or more service functions, or the request message is used to request authorization of a service chain policy corresponding to the application; The first network element receives a response message to the request message from the fourth network element.
  • the first network element may be, for example, a V-PCF network element, etc., or other network devices that can implement the function of the network element;
  • the fourth network element may be, for example, a home-policy control function (home-policy control function, H-PCF) network element, etc., or other network devices that can implement the function of the network element.
  • H-PCF home-policy control function
  • a method for determining a policy is provided, and the method may be executed by a network device, or may also be executed by a chip, a chip system, or a circuit used for the network device, which is not limited in this application.
  • the following description is given by taking the execution by the fourth network element as an example.
  • the method may include: the fourth network element receives a request message from the first network element, where the request message is used to request authorization of one or more service functions, or the request message is used to request authorization of a service chain policy corresponding to the application ; the fourth network element sends a response message to the request message to the first network element.
  • the fourth network element After the fourth network element performs authorization, it sends confirmation information indicating acceptance.
  • the first network element after the first network element formulates the service chain policy according to the request, it can send the service chain policy to the fourth network element for further authorization by the fourth network element. Or, after determining the supported service function according to the request, the first network element may send the information of the service function to the fourth network element, so as to perform further authorization of the fourth network element.
  • the first network element sends a request message to the fourth network element, where the request message includes the service chain policy corresponding to the application and the identifier of the user accessing the application, the request message It is used to request authorization for the business chain policy corresponding to the application accessed by the user.
  • the first network element sends a request message to the fourth network element, where the request message includes information of one or more service functions and an identifier of a user accessing the application, the request The message is used to request authorization of information for one or more business functions of the application accessed by the user.
  • a seventh aspect provides a service chain management method, which can be executed by a network device, or can also be executed by a chip, a chip system, or a circuit used for the network device, which is not limited in this application, for the convenience of description , which is described below by taking the execution by the fifth network element as an example.
  • the method may include: the fifth network element receives a request message from the second network element, where the request message includes information of the queried service chain; the fifth network element sends a response message to the second network element, where the response message is used to indicate the supported business chain information.
  • the method may further include: the fifth network element receives a registration request message from a service chain manager (service chain manager), where the registration request message includes one or more of the following information of the registered service chain: service function type Correspondence between business function identifiers, business function types and external business chain identifiers, business function types, business function identifiers and data network access identifiers, business function identifiers, external business chain identifiers and data network access identifiers The corresponding relationship of the corresponding relationship of the identification.
  • service chain manager service chain manager
  • a service chain management method is provided.
  • the method can be executed by a network device, or can also be executed by a chip, a chip system or a circuit used for the network device, which is not limited in this application, for the convenience of description , which is described below by taking the execution by the second network element as an example.
  • the method may include: the second network element sends a request message to the fifth network element, where the request message includes information of the queried service chain; the second network element receives a response message from the fifth network element, where the response message is used to indicate the supported business chain information.
  • the second network element can dynamically request the service chain. For example, the second network element can obtain the corresponding service function or service chain through query.
  • the information of the queried service chain carried in the request message includes: the type of the required service function (service function) and the data network access identification information.
  • the fifth network element may return, according to the data network access identifier information, the service function or service chain identifier supported by the data network access identifier and the included service function type.
  • the fifth network element may return the corresponding service function identifier or service chain identifier and the included service function type according to the type of the service function.
  • a communication device is provided, and the device is configured to perform the methods provided in the above-mentioned first to eighth aspects.
  • the apparatus may include units and/or modules for executing the methods provided in the first to eighth aspects, such as a processing unit and/or a communication unit.
  • the apparatus is a network device.
  • the communication unit may be a transceiver, or an input/output interface;
  • the processing unit may be a processor.
  • the apparatus is a chip, a system of chips, or a circuit used in a network device.
  • the communication unit may be an input/output interface, interface circuit, output circuit, input circuit, pin or related circuit on the chip, chip system or circuit etc.
  • the processing unit may be a processor, a processing circuit or a logic circuit, or the like.
  • the device is the first network element or a chip, a chip system or a circuit in the first network element.
  • the apparatus may include units and/or modules for performing the methods provided in the first and fifth aspects, such as a processing unit and/or a communication unit.
  • the device is the second network element or a chip, a chip system or a circuit in the second network element.
  • the apparatus may include units and/or modules for performing the methods provided in the second aspect and the eighth aspect, such as a processing unit and/or a communication unit.
  • the device is a third network element or a chip, a chip system or a circuit in the third network element.
  • the apparatus may comprise units and/or modules for performing the method provided by the fourth aspect, such as a processing unit and/or a communication unit.
  • the device is a fourth network element or a chip, a chip system or a circuit in the fourth network element.
  • the apparatus may comprise units and/or modules for performing the method provided by the sixth aspect, such as a processing unit and/or a communication unit.
  • the apparatus is a fifth network element or a chip, a chip system or a circuit in the fifth network element.
  • the apparatus may include units and/or modules for performing the methods provided in the third and seventh aspects, such as a processing unit and/or a communication unit.
  • the above transceiver may be a transceiver circuit.
  • the above-mentioned input/output interface may be an input/output circuit.
  • a communication device comprising: a memory for storing a program; a processor for executing a program stored in the memory, and when the program stored in the memory is executed, the processor is configured to execute the above-mentioned first aspect to The method provided by the eighth aspect.
  • the apparatus is a network device (such as each of the above network elements).
  • the apparatus is a chip, a chip system or a circuit used in a network device (eg, each of the above network elements).
  • the present application provides a processor for executing the methods provided by the above aspects.
  • the process of sending the above-mentioned information and obtaining/receiving the above-mentioned information in the above-mentioned methods can be understood as the process of outputting the above-mentioned information by the processor and the process of receiving the above-mentioned input information by the processor.
  • the processor When outputting the above-mentioned information, the processor outputs the above-mentioned information to the transceiver for transmission by the transceiver. After the above information is output by the processor, other processing may be required before reaching the transceiver.
  • the transceiver obtains/receives the above-mentioned information, and inputs it into the processor. Furthermore, after the transceiver receives the above-mentioned information, the above-mentioned information may need to perform other processing before being input to the processor.
  • the receiving request message mentioned in the foregoing method can be understood as the processor receiving the input information.
  • the above-mentioned processor may be a processor specially used to execute these methods, or may be a processor that executes computer instructions in a memory to execute these methods, such as a general-purpose processor.
  • the above-mentioned memory can be a non-transitory (non-transitory) memory, such as a read-only memory (Read Only Memory, ROM), which can be integrated with the processor on the same chip, or can be set on different chips respectively.
  • ROM read-only memory
  • the embodiment does not limit the type of the memory and the setting manner of the memory and the processor.
  • a twelfth aspect provides a computer-readable storage medium, where the computer-readable medium stores program codes for device execution, the program codes including methods for executing the above-mentioned first to eighth aspects.
  • a thirteenth aspect provides a computer program product comprising instructions, which, when the computer program product runs on a computer, causes the computer to execute the methods provided in the first to eighth aspects above.
  • a fourteenth aspect provides a chip, the chip includes a processor and a communication interface, the processor reads an instruction stored in a memory through the communication interface, and executes the methods provided in the first to eighth aspects.
  • the chip may further include a memory, in which instructions are stored, the processor is configured to execute the instructions stored in the memory, and when the instructions are executed, the The processor is configured to execute the methods provided in the first to eighth aspects above.
  • a fifteenth aspect provides a communication system, including one or more of the following: a first network element, a second network element, a third network element, a fourth network element, and a fifth network element.
  • FIG. 1 shows a schematic diagram of a network architecture suitable for this embodiment of the present application.
  • FIG. 2 shows another schematic diagram of a network architecture suitable for this embodiment of the present application.
  • FIG. 3 is a schematic diagram of a method 300 for determining a strategy provided by an embodiment of the present application.
  • FIG. 4 is a schematic diagram of a method 400 for determining a policy according to another embodiment of the present application.
  • FIG. 5 is a schematic flowchart of a determination strategy applicable to an embodiment of the present application.
  • FIG. 6 is another schematic flowchart of a determination strategy applicable to an embodiment of the present application.
  • FIG. 7 is another schematic flowchart of a determination strategy applicable to an embodiment of the present application.
  • FIG. 8 is another schematic flowchart of a determination strategy applicable to an embodiment of the present application.
  • FIG. 9 is another schematic flowchart of a determination strategy applicable to an embodiment of the present application.
  • FIG. 10 is another schematic flowchart of a determination strategy applicable to an embodiment of the present application.
  • FIG. 11 is a schematic flowchart of business chain management applicable to this embodiment of the present application.
  • FIG. 12 is a schematic block diagram of a communication apparatus provided according to an embodiment of the present application.
  • FIG. 13 is another schematic block diagram of a communication apparatus provided according to an embodiment of the present application.
  • FIG. 14 is a schematic structural diagram of a communication apparatus provided by an embodiment of the present application.
  • the technical solutions of the embodiments of the present application can be applied to various communication systems, for example, fifth generation (5th generation, 5G) systems or new radio (NR), long term evolution (LTE) systems, LTE frequency Division duplex (frequency division duplex, FDD) system, LTE time division duplex (time division duplex, TDD) and so on.
  • LTE long term evolution
  • LTE frequency Division duplex frequency division duplex
  • FDD frequency division duplex
  • TDD time division duplex
  • the technical solutions provided in this application can also be applied to future communication systems, such as the sixth generation mobile communication system.
  • the technical solutions of the embodiments of the present application can also be applied to device to device (D2D) communication, vehicle-to-everything (V2X) communication, machine to machine (M2M) communication, machine Machine type communication (MTC), and Internet of things (IoT) communication systems or other communication systems.
  • D2D device to device
  • V2X vehicle-to-everything
  • M2M machine to machine
  • MTC machine
  • FIG. 1 and FIG. 2 To facilitate understanding of the embodiments of the present application, a communication system applicable to the embodiments of the present application is first described in detail with reference to FIG. 1 and FIG. 2 .
  • FIG. 1 shows a schematic diagram of a network architecture suitable for this embodiment of the present application.
  • the network architecture may include, but is not limited to, the following, for example: user equipment (user equipment, UE), access network (access network, AN), access and mobility management function (access and mobility management function, AMF) network element, session management function (SMF) network element, user plane function (UPF) network element, policy control function (PCF) network element, unified data management (unified data) network element management, UDM) network element, application function (application function, AF), data network (data network, DN), etc.
  • user equipment user equipment
  • UE access network
  • AMF access and mobility management function
  • SMF session management function
  • UPF user plane function
  • PCF policy control function
  • UDM unified data management
  • application function application function, AF
  • data network data network
  • DN data network
  • Terminal equipment can be called user equipment (UE), access terminal, subscriber unit, subscriber station, mobile station, mobile station (MS), mobile terminal (MT), remote station , remote terminal, mobile device, user terminal, terminal, wireless communication device, user agent or user equipment.
  • the terminal device may be a device that provides voice/data connectivity to the user, such as a handheld device with a wireless connection function, a vehicle-mounted device, and the like.
  • terminals can be: mobile phone (mobile phone), tablet computer (pad), computer with wireless transceiver function (such as notebook computer, palmtop computer, etc.), mobile internet device (mobile internet device, MID), virtual reality (virtual reality, VR) equipment, augmented reality (augmented reality, AR) equipment, wireless terminals in industrial control (industrial control), wireless terminals in unmanned driving (self driving), wireless terminals in remote medical (remote medical) Terminal, wireless terminal in smart grid, wireless terminal in transportation safety, wireless terminal in smart city, wireless terminal in smart home, cellular phone, cordless Telephone, session initiation protocol (SIP) telephone, wireless local loop (WLL) station, personal digital assistant (PDA), handheld device, computing device or connection with wireless communication capabilities
  • Other processing equipment to wireless modems in-vehicle equipment, wearable equipment, terminal equipment in 5G networks or terminal equipment in the future evolved public land mobile network (PLMN), etc.
  • PLMN public land mobile network
  • the terminal device may also be a terminal device in an Internet of things (Internet of things, IoT) system.
  • IoT Internet of things
  • Its main technical feature is to connect items to the network through communication technology, so as to realize the intelligent network of human-machine interconnection and interconnection of things.
  • IoT technology can achieve massive connections, deep coverage, and terminal power saving through, for example, narrow band (NB) technology.
  • NB narrow band
  • terminal equipment can also include sensors such as smart printers, train detectors, and gas stations.
  • the main functions include collecting data (part of terminal equipment), receiving control information and downlink data of network equipment, and sending electromagnetic waves to transmit uplink data to network equipment. .
  • the terminal device may be any device that can access the network.
  • a certain air interface technology can be used to communicate with each other between the terminal device and the access network device.
  • the UE may be used to act as a base station.
  • a UE may act as a scheduling entity that provides sidelink signals between UEs in V2X or D2D or the like.
  • UEs may be used to act as a base station.
  • a UE may act as a scheduling entity that provides sidelink signals between UEs in V2X or D2D or the like.
  • cell phones and automobiles communicate with each other using sidelink signals. Communication between cell phones and smart home devices without relaying communication signals through base stations.
  • Access network The access network can provide network access functions for authorized users in a specific area, including radio access network (RAN) equipment and AN equipment.
  • the RAN equipment is mainly the 3rd Generation Partnership Project (3rd Generation Partnership Project, 3GPP) network wireless network equipment, and the AN equipment may be the access network equipment defined by non-3GPP (non-3GPP).
  • 3GPP 3rd Generation Partnership Project
  • the access network may be an access network using different access technologies.
  • 3GPP access technologies such as those employed in 3G, 4G or 5G systems
  • non-3GPP (non-3GPP) access technologies 3GPP access technology refers to the access technology that conforms to the 3GPP standard specifications.
  • the access network equipment in the 5G system is called the next generation Node Base station (gNB) or RAN.
  • Non-3GPP access technologies refer to access technologies that do not conform to 3GPP standards, such as air interface technologies represented by access points (APs) in wireless fidelity (WiFi), global interconnection microwave access (worldwide interoperability for microwave access, WiMAX), code division multiple access (code division multiple access, CDMA) networks, etc.
  • the access network equipment (AN equipment) can allow the terminal equipment and the 3GPP core network to use non-3GPP technology for interconnection and intercommunication.
  • An access network that implements an access network function based on a wireless communication technology may be referred to as a RAN.
  • the radio access network can be responsible for functions such as radio resource management, quality of service (QoS) management, data compression and encryption on the air interface side.
  • QoS quality of service
  • the wireless access network provides access services for terminal equipment, and then completes the forwarding of control signals and user data between the terminal and the core network.
  • a radio access network may include, but is not limited to, a macro base station, a micro base station (also called a small cell), a radio network controller (RNC), a Node B (Node B, NB), a base station controller (base station controller, BSC), base transceiver station (base transceiver station, BTS), home base station (for example, home evolved NodeB, or home Node B, HNB), baseband unit (baseband unit, BBU), AP in WiFi systems, wireless Relay node, wireless backhaul node, transmission point (TP) or transmission and reception point (TRP), etc. It can also be a gNB or a transmission point (TRP or TRP) in a 5G (eg, NR) system.
  • RNC radio network controller
  • Node B Node B
  • BSC base station controller
  • base transceiver station base transceiver station
  • BTS home base station
  • home base station for example, home evolved NodeB, or home Node B, HNB
  • TP one or a group (including multiple antenna panels) antenna panels of a base station in a 5G system, or, it can also be a network node that constitutes a gNB or a transmission point, such as a baseband unit (BBU), or a distributed unit ( distributed unit, DU), or the base station in the next-generation communication 6G system, etc.
  • BBU baseband unit
  • DU distributed unit
  • the embodiments of the present application do not limit the specific technology and specific device form adopted by the wireless access network device.
  • the access network may provide services to the cell.
  • the terminal device may communicate with the cell through transmission resources (eg, frequency domain resources, or spectrum resources) allocated by the access network device.
  • transmission resources eg, frequency domain resources, or spectrum resources
  • AMF network element mainly used for mobility management and access management, such as user location update, user registration network, user switching, etc.
  • AMF can also be used to implement other functions than session management in mobility management entity (mobility management entity, MME). For example, legal interception, or access authorization (or authentication) and other functions.
  • SMF network element It is mainly used for session management, UE's Internet Protocol (IP) address allocation and management, selection of user plane functions that can be managed, policy control, or termination point of charging function interfaces, and downlink data notification, etc.
  • IP Internet Protocol
  • the SMF main user is responsible for session management in the mobile network, such as session establishment, modification, release, and the like.
  • Specific functions may include, for example, assigning IP addresses to terminal devices, selecting UPFs that provide packet forwarding functions, and the like.
  • UPF network element responsible for the forwarding and reception of user data in the terminal equipment.
  • the UPF network element can receive user data from the data network (DN), and transmit it to the terminal equipment through the access network equipment.
  • the UPF network element can also receive user data from the terminal device through the access network device and forward it to the data network.
  • the transmission resources and scheduling functions that provide services to terminal equipment in the UPF network element are managed and controlled by the SMF network element.
  • PCF network element a unified policy framework for guiding network behavior, providing policy rule information for control plane functional network elements (such as AMF, SMF network elements, etc.), and being responsible for acquiring user subscription information related to policy decision-making.
  • control plane functional network elements such as AMF, SMF network elements, etc.
  • AF network element mainly supports interaction with the 3GPP core network to provide services, such as influencing data routing decisions, interacting with policy control functions (PCF), or providing third parties to the network side.
  • PCF policy control functions
  • UDM network element used to generate authentication credential, user identification processing (such as storing and managing user permanent identity, etc.), access authorization control and contract data management, etc.
  • Data Network A service network for providing data services to users.
  • the Internet Internet
  • a third-party service network an IP multimedia service (IP multi-media service, IMS) network, etc.
  • IP multimedia service IP multi-media service, IMS
  • each network element can communicate with each other through the interfaces shown in the figure, and some interfaces can be implemented in the form of service-oriented interfaces.
  • the UE and the AMF can interact through the N1 interface, and the interactive message can be called, for example, an N1 message (N1 Message).
  • the RAN and the AMF can interact through the N2 interface, and the N2 interface can be used for sending non-access stratum (NAS) messages.
  • the RAN and the UPF can interact through the N3 interface, and the N3 interface can be used to transmit data on the user plane.
  • the SMF and the UPF can interact through the N4 interface, and the N4 interface can be used to transmit information such as the tunnel identification information of the N3 connection, the data buffer indication information, and the downlink data notification message.
  • the AF and PCF can interact through the N5 interface, and the N5 interface can be used for application service request delivery and network events.
  • the UPF and the DN can interact through the N6 interface, and the N6 interface can be used to transmit data on the user plane.
  • the PCF and the SMF can interact through the N7 interface, and the N7 interface can be used to deliver protocol data unit (PDU) session (PDU session) granularity and business data flow granularity control policies.
  • the AMF and the UDM can interact through the N8 interface.
  • the N8 interface can be used by the AMF to obtain access and mobility management-related subscription data and authentication data from the UDM, and to register the UE's current mobility management-related information with the UDM.
  • the SMF and the UDM can interact through the N10 interface, and the N10 interface can be used for the SMF to obtain the session management-related subscription data from the UDM, and the SMF to register the UE's current session related information with the UDM.
  • the SMF and AMF can interact through the N11 interface, and the N11 interface can be used to transfer PDU session tunnel information between the RAN and the UPF, transfer control messages sent to the UE, and transfer radio resource control information sent to the RAN.
  • the PCF and the AMF can interact through the N15 interface, and the N15 interface can be used to deliver UE policies and access control related policies.
  • the relationship between other interfaces and each network element is shown in Figure 1, and for the sake of brevity, it will not be described in detail here.
  • AMF, SMF, UPF, PCF, UDM, etc. shown in FIG. 1 can be understood as network elements for implementing different functions, for example, they can be combined into network slices as required. These network elements can be independent devices, or integrated in the same device to implement different functions, or can be network elements in hardware devices, software functions running on dedicated hardware, or platforms (for example, cloud The virtualization function instantiated on the platform), the present application does not limit the specific form of the above network element.
  • the name of the interface between each network element in FIG. 1 is just an example, and the name of the interface in a specific implementation may be other names, which are not specifically limited in this application.
  • the names of the messages (or signaling) transmitted between the above network elements are only an example, and do not constitute any limitation on the functions of the messages themselves.
  • the UE establishes a PDU session after accessing the network, and accesses the external data network DN through the PDU session, and interacts with the application server deployed in the DN.
  • the network can select the UPF that accesses the DN as the anchor according to the network policy, such as the PDU session anchor (PSA), and access the application server through the N6 interface of the PSA.
  • PSA PDU session anchor
  • Operators or third-party application providers can deploy mobile service value-added networks to provide users with quality of experience (QoE), reduce network bandwidth pressure, and provide value-added services.
  • FIG. 2 shows another schematic diagram of a network architecture suitable for this embodiment of the present application.
  • FIG 2 mainly uses a dynamic business chain scheme of local area network (LAN) (such as N6-LAN) to adapt to flexible and rapid service deployment changes, while reducing capital expenditure (capital expenditure, CAPX)
  • LAN local area network
  • CAPX capital expenditure
  • the architecture is: examples are illustrated.
  • PCF can formulate a data-oriented policy (traffic steering policy, TSP) for the application accessed by the user.
  • TSP rules usually include service data flow description information and corresponding service chain identifiers. After the UPF detects the service data, it marks the corresponding service chain identifier on the data packets of the service data flow.
  • the switch will dynamically guide the data packet to the corresponding service function node, also called the enabler, according to the service chain identifier.
  • switch1 dynamically guides the data packets to the corresponding service function node 1 and service function node 2 according to the service chain identifier
  • switch 2 dynamically guides the data packet to the corresponding service function according to the service chain identifier. on node 3 and service function node 4.
  • the PCF usually formulates the TSP according to the user's subscription and the policy configured by the operator. In this way, the adjustment period of the dynamic business chain is relatively long, and it cannot quickly respond to the rapidly changing demands of the application on the business chain.
  • the present application provides a method that can quickly respond to the rapidly changing requirements of the application on the business chain. It should be understood that the embodiments of the present application are not only applicable to the architectures shown in FIG. 1 and FIG. 2 above, but also applicable to other architectures, which are not limited thereto. For example, the embodiments of the present application can be applied to any scenario where a network device formulates a service chain policy for an application; for another example, the embodiments of the present application can be applied to any scenario where a service chain is deployed for an application.
  • FIG. 3 is a schematic diagram of a method 300 for determining a strategy provided by an embodiment of the present application.
  • Method 300 may include the following steps.
  • the second network element sends a request message #1 to the first network element, where the request message #1 includes information of a service chain required by the application.
  • the first network element receives the request message #1.
  • request message #1 is named for distinction, and the naming does not limit the protection scope of the embodiments of the present application.
  • the information of the service chain required by the application such as but not limited to: service chain identifier (service chain identifier, SC Id) required by the application, external service chain identifier (external service chain identifier, external SC Id) required by the application , information of one or more service functions required by the application, information of one or more external service functions required by the application, information of the service chain required by the application, and data network access identifier identification, DNAI), or information about applying the corresponding business chain strategy.
  • the correspondence between the information of the service chain required by the application and the DNAI for example, may be the correspondence between the service chain identifier required by the application and the DNAI, or may be one or more required by the application. Correspondence between a business function and DNAI. Specifically, it will be introduced in detail below.
  • method 300 may further include step 320 .
  • the first network element determines a service chain policy corresponding to the application according to the service chain information required by the application.
  • the information of the service chain required by the application can be carried when the request is sent. Therefore, whether to authorize can be determined according to the information of the service chain required by the application carried in the request, or a service chain policy can be formulated directly according to the information of the service chain required by the application carried in the request.
  • the solution provided by the embodiments of the present application can quickly respond to the rapidly changing requirements of the application on the service chain.
  • the specific forms of the first network element and the second network element are not limited in this embodiment of the present application.
  • the second network element represents the requested device, for example, the second network element carries the information of the service chain required by the application in the request message #1; the first network element represents the authorized device or determines A service chain policy device, such as the first network element, authorizes or formulates a service chain policy according to the service chain information required by the application carried in the request message #1.
  • the first network element may be, for example, a PCF, or may also be a V-PCF, etc., which is not limited thereto.
  • the second network element may be an AF, or may also be a capability exposure function (network exposure function, NEF), etc., which is not limited.
  • the information of the service chain required by the application includes the service chain identifier required by the application, and the first network element determines the service chain policy corresponding to the application according to the service chain identifier required by the application.
  • the first network element is PCF
  • the second network element is AF.
  • the AF sends the service chain identifier required by the application to the PCF
  • the PCF determines the service chain policy corresponding to the application according to the service chain identifier required by the application.
  • the first network element is PCF
  • the second network element is NEF.
  • the NEF receives the external service chain identifier required by the application, for example, the NEF receives the external service chain identifier required by the application from the AF.
  • the NEF maps the external service chain identifier required by the application to the internal service chain identifier (ie, the service chain identifier), and sends the internal service chain identifier to the PCF.
  • the PCF determines the service chain policy corresponding to the application according to the service chain identifier required by the application.
  • the information of the service chain required by the application includes information of one or more service functions required by the application, and the first network element determines the service chain corresponding to the application according to the information of the one or more service functions required by the application Strategy.
  • the information of the service function may include, for example, the identifier of the service function and/or the type of the service function.
  • the first network element is PCF
  • the second network element is AF.
  • the AF sends the information of the service function required by the application to the PCF
  • the PCF determines the service chain policy corresponding to the application according to the information of the service function required by the application.
  • the first network element is PCF
  • the second network element is NEF.
  • the NEF receives the information of the external service function required by the application, eg, the NEF receives the information of the external service function required by the application from the AF.
  • the NEF maps the external service functions required by the application to the internal service functions (ie, service functions), and sends the information of the internal service functions to the PCF.
  • the PCF determines the service chain policy corresponding to the application according to the information of the internal service function required by the application.
  • Implementation mode 3 The information of the service chain required by the application includes the corresponding relationship between the service chain identifier required by the application and the DNAI, and the first network element determines the application according to the corresponding relationship between the service chain identifier required by the application and the DNAI Corresponding business chain strategy.
  • the first network element is PCF
  • the second network element is AF.
  • the AF sends the correspondence between the service chain identifier required by the application and the DNAI to the PCF
  • the PCF determines the service chain policy corresponding to the application according to the correspondence between the service chain identifier required by the application and the DNAI.
  • the first network element is PCF
  • the second network element is NEF.
  • the NEF receives the correspondence between the external service chain identifier required by the application and the DNAI, such as the correspondence between the external service chain identifier and the DNAI required by the NEF to receive the application from the AF.
  • the NEF maps the external service chain identifier required by the application to the internal service chain identifier (ie, the service chain identifier), and sends the correspondence between the internal service chain identifier and the DNAI to the PCF.
  • the PCF determines the service chain policy corresponding to the application according to the correspondence between the service chain identifier required by the application and the DNAI.
  • the information of the service chain required by the application includes the corresponding relationship between the information of one or more service functions required by the application and the DNAI, and the first network element is based on the information of one or more service functions required by the application.
  • the corresponding relationship with DNAI determines the business chain strategy corresponding to the application.
  • the first network element is PCF
  • the second network element is AF.
  • the AF sends the correspondence between the service functions required by the application and the DNAI to the PCF
  • the PCF determines the service chain policy corresponding to the application according to the correspondence between the service functions required by the application and the DNAI.
  • the first network element is PCF
  • the second network element is NEF.
  • the NEF receives the corresponding relationship between the external service function required by the application and the DNAI, such as the corresponding relationship between the external service function required by the NEF to receive the application from the AF and the DNAI.
  • the NEF maps the external service functions required by the application to the internal service functions (ie, service functions), and sends the correspondence between the internal service functions and the DNAI to the PCF.
  • the PCF determines the service chain policy corresponding to the application according to the corresponding relationship between the internal service functions required by the application and the DNAI.
  • the first network element determines the service chain policy corresponding to the application according to the corresponding relationship between the service chain policy corresponding to the application and the DNAI.
  • the correspondence between the business chain policy corresponding to the application and the DNAI can be carried in the information of the business chain required by the application, or based on the correspondence between the information of one or more business functions required by the application and the DNAI Determined, or determined based on the corresponding relationship between the service chain identifier required by the application and the DNAI.
  • the second network element can notify the first network element of the relevant information of the service chain required by the application, and the first network element can directly authorize or determine the corresponding application according to the relevant information of the service chain required by the application.
  • the solutions of the chain strategy all fall within the protection scope of the embodiments of the present application.
  • the first network element sends the service chain policy corresponding to the application to the third network element.
  • the third network element receives the service chain policy corresponding to the application.
  • the first network element may also send indication information to the second network element, where the indication information is used to indicate acceptance of the request.
  • the first network element may also determine the information of one or more service functions supporting the application according to the information of one or more service functions required by the application, and send the information supporting the application to the second network element. Information on one or more business functions.
  • the first network element may determine one or more service functions supported by the application, which are not limited in this embodiment of the present application.
  • the first network element may determine, according to the subscription with the application and the network configuration, one or more service functions that the user accesses the application can support.
  • FIG. 4 is a schematic diagram of a method 400 for determining a policy according to another embodiment of the present application.
  • Method 400 may include the following steps.
  • the first network element sends a request message #2 to the fourth network element, where the request message #2 is used to request authorization of one or more service functions that support the user to access the application, or the request message #2 is used to request the user to access the application. Access the business chain policy corresponding to the application for authorization.
  • the fourth network element receives the request message #2.
  • the first network element sends a request message #2 to the fourth network element, the request message #2 includes the service chain policy corresponding to the application and the identifier of the user accessing the application, and the request message #2 is used to request Apply the corresponding business chain policy for authorization.
  • the first network element sends a request message #2 to the fourth network element, and the request message #2 includes the information of one or more service functions and the identifier of the user accessing the application.
  • the request message #2 is used for Request authorization for one or more business functions that support user access to the application.
  • the first network element receives the response message of the fourth network element.
  • the fourth network element sends the response message to the first network element.
  • the fourth network element after the fourth network element performs authorization, it sends confirmation information indicating acceptance to the first network element.
  • method 400 may further include step 401 .
  • the first network element determines a service chain policy corresponding to the application. For example, the first network element may determine to apply the corresponding service chain policy according to the solution described in method 300 .
  • the first network element after the first network element formulates the service chain policy according to the request, it can send the service chain policy to the fourth network element, so as to further authorize the fourth network element . Or, after determining the supported service function according to the request, the first network element may send the information of the service function to the fourth network element, so as to perform further authorization of the fourth network element.
  • the fourth network element is not limited in this embodiment of the present application.
  • the fourth network element may represent an authorized device.
  • the first network element is, for example, a V-PCF
  • the fourth network element is, for example, an H-PCF.
  • the method 400 and the method 300 can be used in combination or independently, which is not limited. Taking combined use as an example, the first network element may first apply the corresponding service chain policy through the solution shown in method 300 , and then request authorization of the service chain through the solution of method 400 .
  • the service chain identifier is represented by SC Id
  • the service function is represented by service function.
  • FIG. 5 is a schematic flowchart of service chain processing applicable to an embodiment of the present application.
  • the method 500 is mainly illustrated by taking the interaction among the UE, AMF, UPF, SMF, PCF and AF as an example.
  • the method 500 shown in FIG. 5 can be used for the AF to request the service chain processing flow required by the application from the network when the AF requests network resources for the application.
  • the second network element may be, for example, an AF
  • the first network element may be, for example, a PCF.
  • the method 500 shown in FIG. 5 may include the following steps.
  • PDU session establishment procedure PDU session establishment procedure
  • the UE initiates the establishment of a PDU session, the network selects a PSA for the PDU, and the network assigns an address to the UE.
  • the UE can access the application server in the DN network through the established PDU session. It can be understood that after the PDU session is established, the data transmission channel between the terminal device and the DN is established.
  • the SMF primary user is responsible for session management in the mobile network.
  • the PDU session can be established, modified or released between the UE and the SMF through NAS session management (session management, SM) signaling.
  • NAS session management session management, SM
  • step 501 is not limited in this embodiment of the present application.
  • step 501 may refer to the prior art or a manner to appear later.
  • the AF sends the SC Id information to the PCF.
  • the AF When the AF decides to request resources and value-added services for the application that the UE is accessing, the AF can send a request message to the PCF requesting service chain authorization, and the request message carries the SC Id information.
  • the SC Id may be known in advance by the AF.
  • the SC Id may be the service chain identifier negotiated between the application and the operator, or may be the service chain identifier pre-defined by the protocol or network, which is not limited.
  • the AF can provide different uplink and downlink SC Ids.
  • the AF may provide an uplink SC Id for the uplink and a downlink SC Id for the downlink.
  • the SC Id information sent by the AF to the PCF may include the uplink SC Id and the downlink SC Id.
  • the AF may send an Npcf interface policy authorization establishment request (Npcf_PolicyAuthorization_Create Request) message to the PCF, where the message includes SC Id information.
  • the Npcf interface is a service interface provided by PCF externally.
  • the message may also include, but is not limited to, service flow description information (such as quintuple information) and requested quality of service (quality of service, QoS) requirements.
  • the quintuple information usually refers to the source IP address, the source port, the destination IP address, the destination port and the transport layer protocol.
  • Npcf_PolicyAuthorization_Create Request message is only an exemplary description, which is not limited thereto. As long as the AF can send the information of the SC Id to the PCF, it is feasible to carry the information of the SC Id in any message.
  • the PCF After the PCF receives the information of the SC Id from the AF, it can save the received information. Additionally, the PCF can send a response to the AF.
  • the PCF sends confirmation information to the AF.
  • the PCF When the PCF requests the service chain authorization to the AF successfully, the PCF sends confirmation information indicating acceptance to the AF.
  • the PCF may send an Npcf interface policy authorization establishment response (Npcf_PolicyAuthorization_Create Response) message to the AF, where the message includes confirmation information indicating acceptance.
  • Npcf_PolicyAuthorization_Create Response Npcf interface policy authorization establishment response
  • Npcf_PolicyAuthorization_Create Response message is only an exemplary description, which is not limited thereto. As long as the PCF can indicate the acknowledgment to the AF, it is feasible that the acknowledgment indicating acceptance is carried in any message.
  • the PCF formulates a policy and charging control (policy and charging control, PCC) rule.
  • the PCF may, upon request of the AF, formulate PCC rules.
  • the PCC rule includes the TSP Id determined by the PCF according to the SC Id.
  • a rule represents a policy information element related to a PDU session or a service data flow, for which reference may be made to the existing description, which is not limited here.
  • the PCC rules may include different uplink and downlink TSP Ids.
  • the PCF can determine a TSP Id for uplink (for example, the PCF can determine an uplink TSP Id based on an uplink SC Id), and a TSP Id for downlink (for example, the PCF can determine a downlink TSP Id based on a downlink SC Id),
  • the PCC rule formulated by the PCF may include an uplink TSP Id and a downlink TSP Id.
  • the PCF sends the PCC rule to the SMF.
  • the PCC rules include the TSP Id determined by the PCF based on the SC Id.
  • the PCC rules include the upstream TSP Id and the downstream TSP Id.
  • the PCF may send a session management policy control update request (Npcf_SMPolicyControl_UpdateNotify Request) message to the SMF, where the message includes PCC rule information.
  • Npcf_SMPolicyControl_UpdateNotify Request session management policy control update request
  • Npcf_SMPolicyControl_UpdateNotify Request message is only an exemplary description, and is not limited thereto.
  • the PCF can indicate the information of the PCC rule to the SMF, it is feasible to carry the information of the PCC rule in any message.
  • the SMF sends confirmation information to the PCF.
  • the SMF After the SMF installs the PCC rules, it can return confirmation information to the PCF.
  • the SMF may send a session management policy control update response (Npcf_SMPolicyControl_UpdateNotify Response) message to the PCF.
  • Npcf_SMPolicyControl_UpdateNotify Response session management policy control update response
  • Npcf_SMPolicyControl_UpdateNotify Response message is only an exemplary description, which is not limited thereto.
  • the SMF can formulate N4 rules based on PCC rules.
  • the N4 rule may include a packet detection rule (packet detection rule, PDR) and an associated forwarding action rule (forwarding action rule, FAR).
  • PDR packet detection rule
  • FAR forwarding action rule
  • PDR packet detection rule
  • FAR forwarding action rule
  • a possible implementation is to perform N4 session modification (N4 session modification) between SMF and UPF to formulate N4 rules.
  • the UPF performs traffic steering.
  • the UPF matches the service data flow according to the PDR, and the UPF marks the data packet of the data flow according to the FAR, and sends it to the local area network (such as N6-LAN).
  • the switch in the local area network will send the data to the service function nodes in sequence according to the marking of the data packet.
  • a possible service chain processing flow is exemplified above with reference to steps 501-508 shown in FIG. 5 , such as a scenario in which an application requests service chain processing required by the application from the network when requesting network resources for the application.
  • steps 501-508 shown in FIG. 5 such as a scenario in which an application requests service chain processing required by the application from the network when requesting network resources for the application.
  • the above steps are only exemplary descriptions and are not strictly limited.
  • the size of the sequence numbers of the above processes does not mean the sequence of execution, and the execution sequence of each process should be determined by its function and internal logic, and should not constitute any limitation on the implementation process of the embodiments of the present application.
  • step 503 may be performed first, and then step 504 may be performed; or step 504 may be performed first, and then step 503 may be performed; or it may be performed synchronously. Not limited.
  • the network can dynamically make business chain decisions according to the application's request. For example, when the AF requests the application value-added service (ie, service chain) required by the service data flow from the network, it carries the service chain identifier required by the application. In this way, based on the request of the AF (ie, the service chain identifier required by the application), the PCF determines the corresponding service chain policy, or performs authorization. Therefore, it is possible to quickly respond to the rapidly changing demands of the application on the business chain.
  • the application value-added service ie, service chain
  • the PCF determines the corresponding service chain policy, or performs authorization. Therefore, it is possible to quickly respond to the rapidly changing demands of the application on the business chain.
  • FIG. 6 is another schematic flowchart of service chain processing applicable to an embodiment of the present application.
  • the method 600 is mainly illustrated by taking the interaction among the UE, AMF, UPF, SMF, PCF, NEF and AF as an example.
  • the method 600 shown in FIG. 6 can be used for the service chain processing flow required by the AF to request the network from the network through the NEF when the AF requests network resources for the application.
  • the second network element may be, for example, an NEF
  • the first network element may be, for example, a PCF.
  • the method 600 shown in FIG. 6 may include the following steps.
  • the UE initiates the establishment of a PDU session, the network selects a PSA for the PDU, and the network assigns an address to the UE.
  • the UE can access the application server in the DN network through the established PDU session.
  • step 601. For example, the description of step 501 above may be referred to.
  • step 601 reference may be made to the prior art or a manner that will appear later, and will not be described here.
  • the AF sends the information of the external service chain identifier external SC Id to the NEF.
  • the AF When the AF decides to request resources and value-added services for the application the UE is accessing, the AF can send a request message to the NEF to request service chain authorization, and the request message carries the information of the external SC Id.
  • the external SC Id can be known in advance by the AF.
  • the external SC Id can be the service chain identifier negotiated between the application and the operator, or it can be the service chain identifier pre-defined by the protocol or network, which is not limited.
  • the AF can provide different uplink and downlink external SC Ids.
  • the AF can provide an uplink external SC Id for the uplink and a downlink external SC Id for the downlink.
  • the external SC Id information sent by the AF to the NEF may include the uplink external SC Id and the downlink external SC Id. SCId.
  • the AF may send an AF session establishment request (Nnef_AFsessionWithQoS_Create Request) message with QoS on the Nnef interface to the NEF, and the message includes the information of the external SC Id.
  • the Nnef interface is a service interface provided by NEF externally.
  • the message may also include, but is not limited to, service flow description information (such as quintuple information) and requested QoS requirements.
  • Nnef_AFsessionWithQoS_Create Request message is only an exemplary description, which is not limited thereto. As long as the AF can send the information of the external SC Id to the NEF, it is feasible to carry the information of the external SC Id in any message.
  • the NEF may determine to authorize the AF's request.
  • the NEF can map the external SC Id to the internal service chain identifier (internal SC Id), that is, the NEF can obtain the internal SC Id required by the application.
  • the NEF can map the uplink external SC Id to the uplink internal SC Id, and map the uplink external SC Id to the uplink internal SC Id.
  • the downlink external SC Id is mapped to the downlink internal SC Id.
  • the NEF obtains the internal SC Id required by the application and can send the internal SC Id to the PCF.
  • the NEF sends the information of the internal SC Id to the PCF.
  • the NEF can send the Npcf_PolicyAuthorization_Create Request message to the PCF, which contains the information of the internal SC Id.
  • the message may also include, but is not limited to, service flow description information (such as quintuple information) and requested QoS requirements.
  • Npcf_PolicyAuthorization_Create Request message is only an exemplary description, which is not limited thereto. As long as the NEF can send the information of the internal SC Id to the PCF, it is feasible to carry the information of the internal SC Id in any message.
  • the PCF sends confirmation information to the NEF.
  • the PCF When the PCF successfully authorizes the requested service chain, the PCF sends a confirmation message indicating acceptance to the NEF.
  • the PCF may send an Npcf_PolicyAuthorization_Create Response message to the NEF, where the message includes confirmation information indicating acceptance.
  • Npcf_PolicyAuthorization_Create Response message is only an exemplary description, which is not limited thereto. As long as the PCF can indicate the accepted confirmation to the NEF, it is feasible to carry the accepted confirmation in any message.
  • the NEF sends confirmation information to the AF.
  • the NEF may send an AF session establishment response (Nnef_AFsessionWithQoS_Create Response) message with QoS on the Nnef interface to the AF, where the message includes confirmation information indicating acceptance.
  • AF session establishment response Nnef_AFsessionWithQoS_Create Response
  • Nnef_AFsessionWithQoS_Create Response message is only an exemplary description, which is not limited thereto. As long as the NEF can indicate to the AF the acknowledgment of acceptance, it is feasible that the acknowledgment of acceptance is carried in any message.
  • PCF makes PCC rules.
  • the PCF can formulate PCC rules according to the request of the AF (ie, the request conveyed through the NEF).
  • the PCC rule includes the TSP Id determined by the PCF according to the SC Id (that is, the internal SC Id received in step 604).
  • the PCC rules may include different uplink and downlink TSP Ids.
  • the PCF can determine a TSP Id for the uplink (for example, the PCF can determine an uplink TSP Id based on the internal SC Id of the uplink), and determine a TSP Id for the downlink (for example, the PCF can determine a downlink TSP Id based on the internal SC Id of the downlink) ), in step 607, the PCC rule formulated by the PCF may include the upstream TSP Id and the downstream TSP Id.
  • the PCF sends the PCC rule to the SMF.
  • step 608 for example, reference may be made to the description of the above-mentioned step 505, which will not be described here.
  • the SMF sends confirmation information to the PCF.
  • step 609 for example, reference may be made to the description of step 506, which will not be described here.
  • step 610 for example, reference may be made to the description of step 507, which will not be described here.
  • the UPF performs service routing.
  • step 611 for example, reference may be made to the description of step 508, which will not be described here.
  • step 605 may be performed first, and then step 607 may be performed; or step 607 may be performed first, and then step 605 may be performed; or it may be performed synchronously. Not limited.
  • the network can dynamically make business chain decisions according to the application's request. For example, when the AF requests the service chain processing required by the application to the network through the NEF, it carries the external service chain identifier. After mapping the external service chain identifier to the internal service chain identifier, the NEF sends the internal service chain identifier to the PCF. In this way, the PCF determines the corresponding service chain policy, or authorizes, based on the request of the AF (ie, the internal service chain identifier). Therefore, it is possible to quickly respond to the rapidly changing demands of the application on the business chain.
  • FIG. 7 is another schematic flowchart of service chain processing applicable to an embodiment of the present application.
  • the method 700 mainly takes the interaction among UE, AMF, UPF, SMF, PCF, NEF, unified data repository (UDR) and AF as an example for exemplary description.
  • the method 700 shown in FIG. 7 can be used for the service chain processing flow in which the AF provides the application corresponding to each DNAI to the network through the NEF.
  • the second network element may be, for example, UDR or NEF
  • the first network element may be, for example, PCF.
  • the method 700 shown in FIG. 7 may include the following steps.
  • the AF sends the information of the correspondence between the external service chain identifier external SC Id and the DNAI to the NEF.
  • Information about the correspondence between external SC Id and DNAI can be sent in the form of a list.
  • the AF can send the NEF a list of correspondences between external SC Ids and DNAIs.
  • the AF can send an Nnef interface traffic guidance establishment request (Nnef_TrafficInfluence_Create Request) message to the NEF, where the message contains data guidance request information, and the data guidance request information includes a list of correspondences between the external SC Id and the DNAI.
  • the data steering request information may further include, but is not limited to, applicable user external group identifiers or indication information of any user.
  • Nnef_TrafficInfluence_Create Request message is only an exemplary description, and is not limited thereto. As long as the AF can send the information about the correspondence between the external SC Id and the DNAI to the NEF, it is feasible to carry the information about the correspondence between the external SC Id and the DNAI in any message.
  • NEF performs processing.
  • the NEF may determine to authorize the AF's request.
  • NEF can map external SC Id to internal SC Id, that is, NEF can obtain the correspondence between internal SC Id and DNAI.
  • NEF can also map external group IDs to internal group IDs.
  • NEF saves the correspondence between the internal SC Id and the DNAI to the UDR.
  • the UDR receives the correspondence between the internal SC Id and the DNAI from the NEF, and saves the correspondence between the internal SC Id and the DNAI.
  • the NEF may save the data steering request information received in step 701 into the UDR. It can be understood that in step 702, the NEF can map the external SC Id to the internal SC Id, and can also map the external group identifier to the internal group identifier. Therefore, the data steering request information stored in the UDR may include: the internal SC Id and the internal SC Id. The corresponding relationship of DNAI, the applicable user's internal identifier or any user's instruction information.
  • the NEF sends confirmation information to the AF.
  • the NEF may send the Nnef interface traffic steering establishment response (Nnef_TrafficInfluence_Create Response) message to the AF, and the message contains confirmation information indicating acceptance.
  • Nnef interface traffic steering establishment response Nnef_TrafficInfluence_Create Response
  • Nnef_TrafficInfluence_Create Response message is only an exemplary description, which is not limited thereto. As long as the NEF can indicate to the AF the acknowledgment of acceptance, it is feasible that the acknowledgment of acceptance is carried in any message.
  • the UDR notifies the corresponding PCF of the data steering request information.
  • the data-oriented request information may include: the corresponding relationship between the internal SC Id and the DNAI, the applicable user internal identifier or the indication information of any user.
  • the UE establishes a PDU session.
  • the UE initiates the establishment of a PDU session, the network selects a PSA for the PDU, and the network assigns an address to the UE.
  • Step 706 may refer to the prior art or a manner that will appear later, and will not be described here.
  • PCF makes PCC rules.
  • the PCF formulates corresponding PCC rules.
  • the PCF can determine the TSP Id based on the internal SC Id.
  • the PCC rule may include a data-oriented policy, and the data-oriented policy may include the correspondence between the TSP Id and the DNAI corresponding to the internal SC Id.
  • the PCC rules may include different uplink and downlink TSP Ids.
  • the PCF can determine a TSP Id for the uplink (for example, the PCF can determine an uplink TSP Id according to the internal SC Id of the uplink, or determine the correspondence between the TSP Id and the DNAI in the uplink), and determine a TSP Id for the downlink (such as PCF A downlink TSP Id may be determined according to the downlink internal SC Id, or the corresponding relationship between the downlink TSP Id and DNAI), in step 707, the PCC rule formulated by the PCF may include the TSP Id corresponding to the uplink internal SC Id The corresponding relationship with DNAI, and the corresponding relationship between the TSP Id and DNAI corresponding to the downstream internal SC Id.
  • the PCF sends the PCC rule to the SMF.
  • the PCC rules include a list of correspondences between TSP Ids and DNAIs.
  • the PCC rule includes a list of correspondences between TSP Ids and DNAIs in the uplink, and a list of correspondences between TSP Ids and DNAIs in the downlink.
  • the PCF may send an Npcf_SMPolicyControl_UpdateNotify Request message to the SMF, where the message includes the PCC rule information.
  • the SMF sends confirmation information to the PCF.
  • the SMF After the SMF installs the PCC rules, it can return confirmation information to the PCF.
  • the SMF can send the Npcf_SMPolicyControl_UpdateNotify Response message to the PCF.
  • Npcf_SMPolicyControl_UpdateNotify Response message is only an exemplary description, which is not limited thereto.
  • the SMF and the UPF perform user plane configuration (or reconfiguration).
  • the SMF can determine the target DNAI for the PDU session. For example, the SMF may determine the target DNAI for the PDU session based on the UE's location, operator policy, and DNAI list.
  • the SMF can determine the new PSA and TSP Id based on the target NDAI.
  • SMF can also formulate N4 rules based on PCC rules.
  • the PDR and associated FAR may be included in the N4 rule.
  • PDR includes service flow description information
  • FAR includes TSP Id.
  • UPF conducts traffic steering.
  • the UPF matches the service data flow according to the PDR, and the UPF marks the data packet of the data flow according to the FAR, and sends it to the local area network (such as N6-LAN).
  • the switch in the local area network will send the data to the service function nodes in sequence according to the marking of the data packet.
  • a possible service chain processing flow is exemplified above with reference to steps 701-711 shown in FIG. 7 , such as a scenario in which the application provides service chain processing corresponding to each DNAI to the network through the NEF.
  • steps 701-711 shown in FIG. 7 such as a scenario in which the application provides service chain processing corresponding to each DNAI to the network through the NEF.
  • the above steps are only exemplary descriptions and are not strictly limited.
  • the size of the sequence numbers of the above processes does not mean the sequence of execution, and the execution sequence of each process should be determined by its function and internal logic, and should not constitute any limitation on the implementation process of the embodiments of the present application.
  • the AF when it provides the data-oriented request information to the network, it can provide a list of the corresponding relationship between the DNAI and the external service chain identifier.
  • the NEF After mapping the external service chain identifier to the internal service chain identifier, the NEF sends the list of the correspondence between the DNAI and the internal service chain identifier to the PCF.
  • the PCF determines the corresponding TSP Id according to the internal service chain identifier, so that the corresponding relationship between the DNAI and the TSP Id is carried in the PCC rule sent to the SMF.
  • the SMF can determine the corresponding TSP Id according to the selected target DNAI, so that when the UE accesses the application through the target DNAI, the service data flow can be directed to the corresponding service function (service function).
  • FIG. 8 is another schematic flowchart of service chain processing applicable to an embodiment of the present application.
  • the method 800 is mainly illustrated by taking the interaction among the UE, AMF, UPF, SMF, PCF, NEF and AF as an example.
  • the method 800 shown in FIG. 8 can be used for the AF to provide the service value-added function requirement process to the network through the NEF.
  • the second network element may be, for example, NEF
  • the first network element may be, for example, PCF.
  • the method 800 shown in FIG. 8 may include the following steps.
  • the UE initiates the establishment of a PDU session, the network selects a PSA for the PDU, and the network assigns an address to the UE.
  • the UE can access the application server in the DN network through the established PDU session.
  • Step 801 is not limited in this embodiment of the present application, for example, the description of step 501 above may be referred to.
  • step 801 reference may be made to the prior art or a manner that will appear later, and will not be described here.
  • AF sends a list of external service functions to NEF.
  • a list of external service functions including information about one or more service functions.
  • the service function can be identified by a specific identifier or type, which is not limited.
  • a service function can be identified by the Id of the service function, that is, the list of external service functions includes the Id of the external service function.
  • the service function can be identified by the type of the service function, that is, the external service function list includes the type of the external service function.
  • Information about external service functions can be sent in the form of a list.
  • the AF may send a list of external service functions to the NEF, by way of example and not limitation, this list may be carried, for example, in the order in which the service functions are used.
  • the AF When the AF decides to request resources and value-added services for the application that the UE is accessing, the AF can send a request message to the NEF to request service chain authorization, and the request message carries the information of the external service function.
  • the AF can provide a list of different uplink and downlink external service functions.
  • the AF may provide a list of upstream service functions for the upstream and a list of downstream service functions for the downstream.
  • the list of service functions sent by the AF to the NEF may include the list of upstream service functions and the list of downstream services. A list of service functions.
  • the AF can send the Nnef_AFsessionWithQoS_Create Request message to the NEF, which contains a list of external service functions.
  • the message may also include, but is not limited to, service flow description information (such as quintuple information) and requested QoS requirements.
  • Nnef_AFsessionWithQoS_Create Request message is only an exemplary description, which is not limited thereto. As long as the AF can send the list of external service functions to the NEF, it is feasible to carry the list of external service functions in any message.
  • the NEF may determine to authorize the AF's request.
  • NEF can map external service functions to internal service functions, that is, NEF can obtain a list of internal service functions.
  • the NEF can map the uplink external service function list For the list of upstream internal service functions, map the list of downstream external service functions to the list of downstream internal service functions.
  • the NEF sends a list of internal service functions to the PCF.
  • the NEF can send the Npcf_PolicyAuthorization_Create Request message to the PCF, which contains a list of internal service functions.
  • the message may also include, but is not limited to, service flow description information (such as quintuple information) and QoS requirements.
  • Npcf_PolicyAuthorization_Create Request message is only an exemplary description, which is not limited thereto. Carrying the list of internal service functions in any message is feasible as long as the NEF can send the list of internal service functions to the PCF.
  • the PCF sends confirmation information to the NEF.
  • the PCF When the PCF successfully authorizes the requested service chain (that is, when the PCF successfully authorizes the requested service function), the PCF sends a confirmation message indicating acceptance to the NEF.
  • the PCF may determine whether to return an acknowledgement message to the NEF according to the network configuration and the operator's policy, that is, determine whether to authorize the requested service chain.
  • the confirmation information may also include: a list of internal service functions authorized by the PCF.
  • the PCF may authorize some of the multiple internal service functions, or the PCF may authorize all of the multiple internal service functions. limited.
  • the PCF can send the Npcf_PolicyAuthorization_Create Response message to the NEF, and the message contains confirmation information indicating that the internal service function is accepted.
  • Npcf_PolicyAuthorization_Create Response message is only an exemplary description, which is not limited thereto. As long as the PCF can indicate to the NEF to accept the confirmation information of the internal service function, it is feasible to carry the confirmation information of the indication to accept the internal service function in any message.
  • the NEF sends confirmation information to the AF.
  • the confirmation information may also include: a list of internal service functions authorized by the PCF.
  • the NEF can send the Nnef_AFsessionWithQoS_Create Response message to the AF, which contains confirmation information indicating that the internal service function is accepted.
  • Nnef_AFsessionWithQoS_Create Response message is only an exemplary description, which is not limited thereto. As long as the NEF can indicate to the AF to accept the confirmation information of the internal service function, it is feasible to carry the confirmation information of the indication to accept the internal service function in any message.
  • PCF makes PCC rules.
  • the PCF can determine the corresponding service chain according to the list of authorized internal service functions, so as to further determine the corresponding TSP Id.
  • PCF formulates PCC rules and includes TSP Ids in PCC rules.
  • the PCC rules may include different uplink and downlink TSP Ids.
  • the PCF sends the PCC rule to the SMF.
  • step 808 for example, reference may be made to the description of step 505, which will not be described here.
  • the SMF sends confirmation information to the PCF.
  • step 809 for example, reference may be made to the description of step 506, which will not be described here.
  • the SMF made the N4 rule.
  • step 810 for example, reference may be made to the description of step 507, which is not described here.
  • the UPF performs service routing.
  • step 811 for example, reference may be made to the description of step 508, which is not described here.
  • a possible service chain processing flow is exemplified above in conjunction with steps 801-811 shown in FIG. 8 , such as a scenario in which an application provides service value-added function requirements to the network through the NEF.
  • steps 801-811 shown in FIG. 8 , such as a scenario in which an application provides service value-added function requirements to the network through the NEF.
  • the above steps are only exemplary descriptions and are not strictly limited.
  • the size of the sequence numbers of the above processes does not mean the sequence of execution, and the execution sequence of each process should be determined by its function and internal logic, and should not constitute any limitation on the implementation process of the embodiments of the present application.
  • step 805 may be performed first, and then step 807 may be performed; or step 807 may be performed first, and then step 805 may be performed; or it may be performed synchronously. Not limited.
  • the network can dynamically make business chain decisions according to the application's request. For example, when the AF requests the service chain processing required by the application to the network through the NEF, it carries a list of external service functions. After mapping the external service function to the internal service function, the NEF sends the list of the internal service function to the PCF. In this way, the PCF determines the corresponding service chain based on the AF's request (ie, the list of internal service functions) and according to the list of authorized internal service functions, thereby further determining the corresponding service chain policy. Therefore, it is possible to quickly respond to the rapidly changing demands of the application on the business chain.
  • the AF requests the service chain processing required by the application to the network through the NEF
  • the NEF After mapping the external service function to the internal service function, the NEF sends the list of the internal service function to the PCF.
  • the PCF determines the corresponding service chain based on the AF's request (ie, the list of internal service functions) and according to the list of authorized internal
  • FIG. 9 is another schematic flowchart of service chain processing applicable to an embodiment of the present application.
  • the method 900 is mainly illustrated by taking the interaction among the UE, AMF, UPF, SMF, V-PCF, H-PCF, NEF and AF as an example.
  • the method 900 shown in FIG. 9 can be used in a roaming scenario where the UE is in local grooming.
  • the AF requests network resources for the application
  • the service chain processing flow required by the application is requested from the network.
  • the second network element may be, for example, NEF
  • the first network element may be, for example, V-PCF
  • the fourth network element may be, for example, H-PCF.
  • the method 900 shown in FIG. 9 may include the following steps.
  • the UE establishes a PDU session, the network selects a PSA for the PDU, and the network assigns an address to the UE.
  • the UE can access the application server in the DN network through the established PDU session.
  • the UE sends a session establishment request message
  • the session establishment request message may include but is not limited to: single network slice selection assistance information (single network slice selection assistance information, S-NSSAI), data network name (data network name, DNN), subscription permanent identifier (SUPI).
  • S-NSSAI single network slice selection assistance information
  • DNN data network name
  • SUPI subscription permanent identifier
  • the SMF interacts with the V-PCF, establishes a session management policy association, and obtains the PCC policy from the PCF.
  • step 901 may refer to the prior art or a method that appears later, and will not be described here.
  • the AF sends the information of the external service chain identifier external SC Id to the NEF.
  • the AF When the AF decides to request resources and business value-added services for the application that the UE is accessing, the AF can send a request message requesting service chain authorization to the NEF, and the request message carries the information of the external SC Id.
  • the external SC Id can be known in advance by the AF.
  • the external SC Id can be the service chain identifier negotiated between the application and the operator, or it can be the service chain identifier pre-defined by the protocol or network, which is not limited.
  • the AF can provide different uplink and downlink external SC Ids.
  • the AF can provide an uplink external SC Id for the uplink and a downlink external SC Id for the downlink.
  • the external SC Id information sent by the AF to the NEF may include the uplink external SC Id and the downlink external SC Id. SCId.
  • the AF can send the Nnef_AFsessionWithQoS_Create Request message to the NEF, and the message contains the information of the external SC Id.
  • the message may also include, but is not limited to, service flow description information (such as quintuple information) and requested QoS requirements.
  • Nnef_AFsessionWithQoS_Create Request message is only an exemplary description, which is not limited thereto. As long as the AF can send the information of the external SC Id to the NEF, it is feasible to carry the information of the external SC Id in any message.
  • the NEF may determine to authorize the AF's request. NEF can map external SC Id to internal SC Id.
  • the NEF can map the uplink external SC Id to the uplink internal SC Id, and map the uplink external SC Id to the uplink internal SC Id.
  • the downlink external SC Id is mapped to the downlink internal SC Id.
  • the NEF sends the information of the internal SC Id to the V-PCF.
  • the NEF may send the Npcf_PolicyAuthorization_Create Request message to the V-PCF, where the message includes the information of the internal SC Id.
  • the message may also include, but is not limited to, service flow description information (such as quintuple information) and requested QoS requirements.
  • Npcf_PolicyAuthorization_Create Request message is only an exemplary description, which is not limited thereto. As long as the NEF can send the information of the internal SC Id to the V-PCF, it is feasible to carry the information of the internal SC Id in any message.
  • V-PCF 905, V-PCF to make PCC rules.
  • the V-PCF can authorize according to the request of the AF (ie, the request conveyed by the NEF).
  • the V-PCF can determine the corresponding TSP Id according to the internal SC Id.
  • the V-PCF formulates PCC rules and includes TSP Ids in the PCC rules.
  • the PCC rules may include different uplink and downlink TSP Ids.
  • the V-PCF can determine a TSP Id for the uplink (for example, the V-PCF can determine an uplink TSP Id based on the internal SC Id of the uplink), and determine a TSP Id for the downlink (for example, the V-PCF can determine the TSP Id based on the internal SC Id of the downlink) Determine a downlink TSP Id), in step 905, the PCC rule formulated by the V-PCF may include the uplink TSP Id and the downlink TSP Id.
  • the V-PCF sends a PCC authorization request message to the H-PCF.
  • the V-PCF determines that the UE is a roaming user, and the V-PCF can send a PCC authorization request message to the H-PCF, where the PCC authorization request message can carry: the identifier of the UE (such as SUPI), DNN, and S-NSSAI.
  • the V-PCF can select the H-PCF through the NF repository function (NRF) of the visited place after determining the home operator of the UE according to the SUPI, or select the H-PCF through the NRF of the home place.
  • NRF NF repository function
  • the PCC authorization request message may include one or more of the following: PCC rules determined by V-PCF, TSP Id determined by V-PCF, internal SC Id determined by V-PCF, service function list authorized by V-PCF .
  • the PCC rules include the TSP Id determined by the V-PCF according to the SC Id.
  • the PCC rules include the upstream TSP Id and the downstream TSP Id.
  • the service function can be identified by a specific identifier or type, which is not limited.
  • the service function can be identified by the ID of the service function, that is, the service function list includes the ID of the service function authorized by the V-PCF.
  • the service function can be identified by the type of the service function, that is, the service function list includes the type of the service function authorized by the V-PCF.
  • the V-PCF may send an Npcf interface PCC authorization establishment request (Npcf_PccAuthorization_Create Request) message to the H-PCF.
  • Npcf_PccAuthorization_Create Request Npcf interface PCC authorization establishment request
  • the Npcf_PccAuthorization_Create Request message is only an exemplary description, which is not limited thereto.
  • the H-PCF sends confirmation information to the V-PCF.
  • step 907 after the H-PCF authorizes, it sends confirmation information indicating acceptance to the V-PCF.
  • the H-PCF may send the Npcf interface PCC authorization establishment response (Npcf_PccAuthorization_Create Response) message to the V-PCF.
  • Npcf_PccAuthorization_Create Response is only an exemplary description, which is not limited thereto.
  • the V-PCF sends confirmation information to the NEF.
  • the V-PCF can send the Npcf_PolicyAuthorization_Create Response message to the NEF. It should be understood that the Npcf_PolicyAuthorization_Create Response message is only an exemplary description, which is not limited thereto.
  • NEF sends confirmation information to AF.
  • the NEF can send the Nnef_AFsessionWithQoS_Create Response message to the AF. It should be understood that the Nnef_AFsessionWithQoS_Create Response message is only an exemplary description, which is not limited thereto.
  • the V-PCF sends the PCC rule to the SMF.
  • the TSP Id is included in the PCC rules.
  • the PCC rules include the upstream TSP Id and the downstream TSP Id.
  • the V-PCF may send an Npcf_SMPolicyControl_UpdateNotify Request message to the SMF, where the message includes PCC rule information.
  • Npcf_SMPolicyControl_UpdateNotify Request message is only an exemplary description, and is not limited thereto.
  • the V-PCF can indicate the information of the PCC rule to the SMF, it is feasible to carry the information of the PCC rule in any message.
  • the SMF sends confirmation information to the V-PCF.
  • the SMF After the SMF installs the PCC rules, it can return confirmation information to the V-PCF.
  • the SMF may send the Npcf_SMPolicyControl_UpdateNotify Response message to the V-PCF. It should be understood that the Npcf_SMPolicyControl_UpdateNotify Response message is only an exemplary description, which is not limited thereto.
  • the SMF made the N4 rule.
  • step 912 for example, reference may be made to the description of the foregoing step 507, which will not be described here.
  • the UPF performs service routing.
  • step 913 for example, reference may be made to the description of step 508, which will not be described here.
  • step 908 may be performed first, and then step 910 may be performed; or step 910 may be performed first, and then step 908 may be performed; or it may be performed synchronously. Not limited.
  • the V-PCF can formulate a service chain policy (ie, TSP policy) according to the request of the AF, and send the service chain policy to the H-PCF for further authorization by the H-PCF.
  • a service chain policy ie, TSP policy
  • FIG. 10 is another schematic flowchart of service chain processing applicable to an embodiment of the present application.
  • the method 1000 is mainly illustrated by taking the interaction among the UE, AMF, UPF, SMF, V-PCF, H-PCF, UDR, NEF and AF as an example.
  • the method 1000 shown in FIG. 10 can be used in a roaming scenario where the UE is in local grooming, and the AF requests the network for service chain processing required by the application when providing data steering request information.
  • the second network element may be, for example, UDR or NEF or H-PCF
  • the first network element may be, for example, V-PCF
  • the fourth network element may be, for example, H-PCF.
  • the method 1000 shown in FIG. 10 may include the following steps.
  • the AF sends the information of the correspondence between the external service chain identifier external SC Id and the DNAI to the NEF.
  • Information about the correspondence between external SC Id and DNAI can be sent in the form of a list.
  • the AF can send the NEF a list of correspondences between external SC Ids and DNAIs.
  • the AF may send an Nnef_TrafficInfluence_Create Request message to the NEF, where the message includes data-oriented request information, and the data-oriented request information includes a list of correspondences between external SC Ids and DNAIs.
  • the data steering request information may further include, but is not limited to, applicable user external group identifiers or indication information of any user.
  • Nnef_TrafficInfluence_Create Request message is only an exemplary description, and is not limited thereto. As long as the AF can send the information about the correspondence between the external SC Id and the DNAI to the NEF, it is feasible to carry the information about the correspondence between the external SC Id and the DNAI in any message.
  • the NEF is processed.
  • the NEF may determine to authorize the AF's request.
  • NEF can map external SC Id to internal SC Id, that is, NEF can obtain the correspondence between internal SC Id and DNAI.
  • NEF can also map external group IDs to internal group IDs.
  • NEF saves the correspondence between the internal SC Id and the DNAI to the UDR.
  • the UDR receives the correspondence between the internal SC Id and the DNAI from the NEF, and saves the correspondence between the internal SC Id and the DNAI.
  • the NEF may save the data steering request information received in step 1001 into the UDR. It can be understood that in step 1002, the NEF can map the external SC Id to the internal SC Id, and can also map the external group identifier to the internal group identifier. Therefore, the data steering request information saved in the UDR may include: the internal SC Id and the internal SC Id. The corresponding relationship of DNAI, the applicable user's internal identifier or any user's instruction information.
  • the NEF sends confirmation information to the AF.
  • NEF can send Nnef_TrafficInfluence_Create Response message to AF. It should be understood that the Nnef_TrafficInfluence_Create Response message is only an exemplary description, which is not limited thereto.
  • the UDR notifies the corresponding PCF of the data steering request information.
  • the UDR notifies the V-PCF and the H-PCF of the data steering request information.
  • the data-oriented request information may include: the corresponding relationship between the internal SC Id and the DNAI, the applicable user internal identifier or the indication information of any user.
  • the UE establishes a PDU session.
  • step 1006 for example, reference may be made to the description of the above-mentioned step 901, which will not be described here.
  • V-PCF made PCC rules.
  • the V-PCF formulates corresponding PCC rules.
  • the V-PCF can determine the corresponding relationship between the TSP Id and the DNAI corresponding to the internal SC Id according to the corresponding relationship between the internal SC Id and the DNAI.
  • the PCC rule may include a data-oriented policy, and the data-oriented policy may include the correspondence between the TSP Id and the DNAI corresponding to the internal SC Id.
  • the PCC rules may include different uplink and downlink TSP Ids.
  • the V-PCF can determine a TSP Id for the uplink (for example, the V-PCF can determine an uplink TSP Id according to the internal SC Id of the uplink, or determine the correspondence between the TSP Id and the DNAI in the uplink), and determine a TSP for the downlink.
  • the V-PCF can determine a downlink TSP Id according to the downlink internal SC Id, or determine the corresponding relationship between the downlink TSP Id and DNAI
  • the PCC rules formulated by the PCF may include the uplink internal The corresponding relationship between the TSP Id and DNAI corresponding to the SC Id, and the corresponding relationship between the TSP Id and DNAI corresponding to the downstream internal SC Id.
  • the V-PCF sends the PCC rule to the SMF.
  • the PCC rules include a list of correspondences between TSP Ids and DNAIs.
  • the PCC rule includes a list of correspondences between TSP Ids and DNAIs in the uplink, and a list of correspondences between TSP Ids and DNAIs in the downlink.
  • the V-PCF may send an Npcf_SMPolicyControl_UpdateNotify Request message to the SMF, where the message includes PCC rule information.
  • the SMF sends confirmation information to the V-PCF.
  • the SMF After the SMF installs the PCC rules, it can return confirmation information to the V-PCF.
  • the SMF may send the Npcf_SMPolicyControl_UpdateNotify Response message to the V-PCF.
  • Npcf_SMPolicyControl_UpdateNotify Response message is only an exemplary description and is not limited thereto.
  • SMF and UPF perform user plane configuration (or reconfiguration).
  • the SMF can determine the target DNAI for the PDU session. For example, the SMF may determine the target DNAI for the PDU session based on the UE's location, operator policy, network configuration, and DNAI list.
  • the SMF can determine the new PSA and TSP Id based on the target NDAI.
  • SMF can also formulate N4 rules based on PCC rules.
  • the PDR and associated FAR may be included in the N4 rule.
  • PDR includes service flow description information
  • FAR includes TSP Id.
  • the SMF sends the information of the target DNAI and/or the TSP Id to the V-PCF, which is used to request the authorization of the service chain policy.
  • the SMF may send an Npcf_SMPolicyControl_Update Request message to the V-PCF, where the message carries the determined target DNAI and/or TSP Id.
  • Npcf_SMPolicyControl_Update Request message is only an exemplary description, which is not limited thereto.
  • the V-PCF sends a PCC authorization request message to the H-PCF.
  • the V-PCF determines that the UE is a roaming user, and the V-PCF may send a PCC authorization request message to the H-PCF, where the PCC authorization request message may carry: the SUPI, DNN, and S-NSSAI of the UE.
  • the V-PCF can select the H-PCF through the NRF of the visited place, or select the H-PCF through the NRF of the home place.
  • the PCC authorization request message may include one or more of the following: the PCC rule determined by the V-PCF corresponding to the target DNAI (the PCC rule includes the TSP Id), the TSP Id determined by the V-PCF corresponding to the target DNAI, the target The internal SC Id determined by the V-PCF corresponding to the DNAI, the list of service functions authorized by the V-PCF corresponding to the target DNAI, and the list of service functions authorized by the V-PCF corresponding to the TSP Id.
  • the service function can be identified by a specific identifier or type, which is not limited.
  • the V-PCF may send an Npcf_PccAuthorization_Create Request message to the H-PCF. It should be understood that the Npcf_PccAuthorization_Create Request message is only an exemplary description, which is not limited thereto.
  • the H-PCF sends confirmation information to the V-PCF.
  • step 1013 after the H-PCF authorizes, it sends confirmation information indicating acceptance to the V-PCF.
  • the H-PCF may send the Npcf_PccAuthorization_Create Response message to the V-PCF. It should be understood that the Npcf_PccAuthorization_Create Response message is only an exemplary description, which is not limited thereto.
  • the V-PCF sends confirmation information to the SMF.
  • V-PCF sends confirmation information to SMF to indicate service chain policy authorization.
  • the V-PCF can send the Npcf_SMPolicyControl_Update Response message to the SMF. It should be understood that the Npcf_SMPolicyControl_Update Response message is only an exemplary description, which is not limited thereto.
  • UPF conducts traffic steering.
  • step 1015 for example, reference may be made to the description of the above-mentioned step 508, which will not be described here.
  • step 1003 can be executed first, and then step 1004 can be executed; or step 1004 can be executed first, and then step 1003 can be executed; or it can be executed synchronously. Not limited.
  • the V-PCF can formulate a service chain policy (ie, TSP policy) according to the request of the AF, and send the service chain policy to the H-PCF for further authorization by the H-PCF.
  • TSP policy a service chain policy
  • the NEF After mapping the external service chain identifier to the internal service chain identifier, the NEF sends a list of the correspondence between the DNAI and the internal service chain identifier to the V-PCF.
  • the V-PCF determines the corresponding TSP Id according to the internal service chain identifier, thereby carrying the corresponding relationship between the DNAI and the TSP Id in the PCC rules. After the SMF determines the target DNAI, it reports to the V-PCF, and the V-PCF further sends the corresponding service chain policy (ie, the TSP policy) to request the H-PCF for further authorization.
  • the corresponding service chain policy ie, the TSP policy
  • FIGS. 5 to 10 may be used to perform the scheme of the method 300
  • FIGS. 9 to 10 may also be used to perform the scheme of the method 400 .
  • the embodiments of the present application considering that the information of the service chain required by the application is carried when the request is sent, the embodiments of the present application provide a method for management of the service chain. A possible flow of business chain management is described below with reference to FIG. 11 .
  • FIG. 11 is a schematic flowchart of business chain management applicable to this embodiment of the present application.
  • the method 1100 mainly takes the interaction among the service chain manager (service chain manager), the NEF and the AF as an example to illustrate.
  • the method 1100 shown in FIG. 11 can be used to register the service function with the NEF after an operator or a third-party application deploys the service function.
  • the third party requests Query the process of obtaining the business chain.
  • the second network element may be, for example, an AF.
  • the method 1100 shown in FIG. 11 may include the following steps.
  • Business chain management devices such as operators or third-party applications, can perceive the operation of the service function after deploying the service function.
  • the operation of the service function for example, it can include but is not limited to: creation, modification or deletion.
  • the service chain registration information is exchanged between the service chain management device and the NEF.
  • the service chain management device sends the service chain registration information to the NEF, and the service chain registration information can carry one or more of the following information: the correspondence between the service function type and the service function identifier, the service function Correspondence between type and external SC Id, service function type, service function identifier and DNAI correspondence, service function identifier, external SC Id identifier and DNAI correspondence.
  • the service function may include, for example, a service function such as creation, modification or deletion.
  • the AF receives the trigger and decides that it needs to request service chain processing. For example, the AF decides to request resources and business value-added services for the application that the UE is accessing.
  • the AF sends a service chain discovery (service chain discovery) request message to the NEF.
  • service chain discovery service chain discovery
  • the request message may carry: the required service function type and DNAI information.
  • NEF can return the service function or SC Id supported by DNAI and the type of service function included according to the DNAI information.
  • NEF can return the corresponding service function Id or SC Id and the included service function type according to the type of service function.
  • the AF may initiate a request message as in the previous method 500 to method 1000 embodiments.
  • a possible business chain processing flow is exemplarily introduced above in conjunction with steps 1101-1104 shown in FIG. 11.
  • the service function is registered to the NEF. Scenarios in which a third party requests a query to obtain a business chain when it is required to request business chain processing.
  • the above steps are only exemplary descriptions and are not strictly limited.
  • the size of the sequence numbers of the above processes does not mean the sequence of execution, and the execution sequence of each process should be determined by its function and internal logic, and should not constitute any limitation on the implementation process of the embodiments of the present application.
  • third-party applications can dynamically request service chains.
  • the network registers the supported service functions or service chains with the NEF, and third-party applications can obtain the corresponding service functions or service chains through query.
  • the information of the service chain is mentioned many times, such as the information of the required service chain or the information of the service chain to be queried, which is used to represent the information related to the service chain, for example, it may include SC Id, external SC Id, service function information, external service function information, DNAI, etc.
  • the network elements in the existing network architecture are mainly used as examples for illustrative description.
  • the application examples are not limited.
  • network elements that can implement the same function in the future are all applicable to the embodiments of the present application.
  • any architecture in which a service chain can be deployed in the future is applicable to the embodiments of the present application.
  • the service chain policy corresponding to the request application is mainly used as an example for illustrative description, and it should be understood that this is not limited.
  • a service chain policy can be formulated using the solutions of the embodiments of the present application.
  • method 400 and method 300 may be used in combination or independently.
  • method 1100 may be used alone, or may be used in combination as a preparation for method 500-method 1000, and so on.
  • network devices eg. various network elements
  • components eg, chips or circuits
  • FIG. 12 is a schematic block diagram of an apparatus 1200 provided by an embodiment of the present application.
  • the apparatus 1200 includes a transceiver unit 1210 and a processing unit 1220 .
  • the transceiver unit 1210 can implement corresponding communication functions, and the processing unit 1220 is used for data processing.
  • Transceiver unit 1210 may also be referred to as a communication interface or a communication unit.
  • the apparatus 1200 may further include a storage unit, which may be used to store instructions and/or data, and the processing unit 1220 may read the instructions and/or data in the storage unit, so that the apparatus implements the foregoing method embodiments .
  • a storage unit which may be used to store instructions and/or data
  • the processing unit 1220 may read the instructions and/or data in the storage unit, so that the apparatus implements the foregoing method embodiments .
  • the apparatus 1200 may be used to perform the actions performed by the network equipment (eg, various network elements) in the above method embodiments.
  • the apparatus 1200 may be a network equipment or a component that can be configured in the network equipment, and the transceiver unit 1210 is used for To perform the operations related to sending and receiving on the network device side in the above method embodiments, the processing unit 1220 is configured to perform the operations related to the processing on the network device side in the above method embodiments.
  • the apparatus 1200 is configured to perform the actions performed by the first network element in the above method embodiments.
  • the transceiver unit 1210 is configured to receive a first request message from the second network element, where the first request message includes the information of the service chain required by the application; the transceiver unit 1210 is further configured to send a message to the third network Meta sends the business chain policy corresponding to the application, and the business chain policy corresponding to the application is formulated according to the information of the business chain required by the application.
  • the processing unit 1220 is configured to determine the service chain policy corresponding to the application according to the information of the service chain required by the application.
  • the apparatus 1200 may implement steps or processes corresponding to the first network element in the method embodiment according to the embodiment of the present application, and the apparatus 1200 may include a unit for executing the method performed by the first network element in the method embodiment .
  • each unit in the apparatus 1200 and the above-mentioned other operations and/or functions are respectively for implementing the corresponding flow of the method embodiment in the first network element in the method embodiment.
  • the transceiver unit 1210 can be used to execute steps 310 and 330 in the method 300 ; the processing unit 1220 can be used to execute the processing steps in the method 300 , such as step 320 .
  • the transceiver unit 1210 can be used to execute steps 410 and 420 in the method 400 ; the processing unit 1220 can be used to execute the processing steps in the method 400 , such as step 401 .
  • the transceiver unit 1210 can be used to execute steps 502 , 503 , 505 and 506 in the method 500 ; the processing unit 1220 can be used to execute the processing steps of the method 500 , such as step 504 .
  • the transceiver unit 1210 can be used to execute steps 604 , 605 , 608 and 609 in the method 600 ; the processing unit 1220 can be used to execute the processing steps of the method 600 , such as step 607 .
  • the transceiver unit 1210 can be used to perform steps 705 , 708 and 709 in the method 700 ; the processing unit 1220 can be used to perform the processing steps in the method 700 , such as step 707 .
  • the transceiver unit 1210 can be used to execute steps 804 , 805 , 808 and 809 in the method 800 ; the processing unit 1220 can be used to execute the processing steps of the method 800 , such as step 807 .
  • the transceiver unit 1210 can be used to execute steps 904 , 906 - 908 , 910 , and 911 in the method 900 ; the processing unit 1220 can be used to execute the processing steps in the method 900 , such as Step 905.
  • the transceiver unit 1210 can be used to execute steps 1005 , 1008 , 1009 , 1011 to 1014 in the method 1000 ; the processing unit 1220 can be used to execute the processing steps in the method 1000 , such as Step 1007
  • the apparatus 1200 is configured to perform the actions performed by the second network element in the above method embodiments.
  • the transceiver unit 1210 is configured to send a first request message to the first network element, where the first request message includes the information of the service chain required by the application; the transceiver unit 1210 is further configured to receive information from the first network element. Meta indication information, the indication information is used to instruct to accept the request of the service chain required by the application.
  • the apparatus 1200 may implement steps or processes corresponding to those performed by the second network element in the method embodiment according to the embodiment of the present application, and the apparatus 1200 may include a unit for performing the method performed by the second network element in the method embodiment .
  • each unit in the apparatus 1200 and the above-mentioned other operations and/or functions are respectively for implementing the corresponding flow of the method embodiment in the second network element in the method embodiment.
  • the transceiver unit 1210 can be used to execute steps 310 and 320 in the method 300 ;
  • the transceiver unit 1210 can be used to execute steps 502 and 503 in the method 500 ; the processing unit 1220 can be used to execute the processing steps in the method 500 , such as step 501 .
  • the transceiver unit 1210 can be used to execute steps 602 , 604 , 605 and 606 in the method 600 ; the processing unit 1220 can be used to execute the processing steps of the method 600 , such as step 603 .
  • the transceiver unit 1210 can be used to perform steps 701 , 704 or 705 in the method 700 ; the processing unit 1220 can be used to perform the processing steps of the method 700 , such as step 702 .
  • the transceiver unit 1210 can be used to execute steps 802 , 804 , 805 , and 806 of the method 800 ; the processing unit 1220 can be used to execute the processing steps of the method 800 , such as step 803 .
  • the transceiver unit 1210 can be used to execute steps 902 , 904 , 909 , or 904 , 906 - 908 in the method 900 ; the processing unit 1220 can be used to execute the processing in the method 900 steps, such as step 903 or 905.
  • the transceiver unit 1210 can be used to execute steps 1001 , 1004 , 1005 , 1008 , 1009 , 1011 to 1014 in the method 1000 ; the processing unit 1220 can be used to execute the steps in the method 1000 Processing steps, such as steps 1002, 1003, or 1007.
  • the transceiver unit 1210 can be used to execute the step 1104 in the method 1100 ; the processing unit 1220 can be used to execute the processing steps of the method 1100 .
  • the apparatus 1200 is configured to perform the actions performed by the fourth network element in the above method embodiments.
  • the transceiver unit 1210 is used to receive a request message from the first network element, where the request message is used to request authorization of one or more service functions, or the request message is used to request a service corresponding to an application
  • the chain policy performs authorization; the transceiver unit 1210 is further configured to send a response message of the request message to the first network element.
  • the transceiver unit 1210 is specifically configured to receive a request message from the first network element, where the request message includes the service chain policy corresponding to the application and the identifier of the user accessing the application, and the request message is used to request the application corresponding to the application accessed by the user. authorized by the business chain strategy.
  • the transceiver unit 1210 is specifically configured to receive a request message from the first network element, where the request message includes information of one or more service functions and an identifier of a user accessing the application, and the request message is used to request a user access Authorization is performed by applying the information of one or more corresponding business functions.
  • the apparatus 1200 may implement steps or processes corresponding to the fourth network element in the method embodiment according to the embodiment of the present application, and the apparatus 1200 may include a unit for executing the method performed by the fourth network element in the method embodiment .
  • each unit in the apparatus 1200 and the above-mentioned other operations and/or functions are respectively for implementing the corresponding flow of the method embodiment in the fourth network element in the method embodiment.
  • the transceiver unit 1210 can be used to execute steps 410 and 420 in the method 400 ; the processing unit 1220 can be used to execute the processing steps in the method 400 .
  • the transceiver unit 1210 can be used to execute steps 906 and 907 in the method 900 ; the processing unit 1220 can be used to execute the processing steps of the method 900 .
  • the transceiver unit 1210 can be used to perform steps 1005 , 1012 and 1013 in the method 1000 ; the processing unit 1220 can be used to perform the processing steps in the method 1000 .
  • the apparatus 1200 is configured to perform the actions performed by the fifth network element in the above method embodiments.
  • the transceiver unit 1210 is used to receive a request message from the second network element, where the request message includes the information of the service chain required by the application; the processing unit 1220 is used for the information of the service chain required by the application. Perform processing; the transceiver unit 1210 is further configured to send the processed service chain information to the first network element.
  • the apparatus 1200 may implement steps or processes corresponding to the fifth network element in the method embodiment according to the embodiment of the present application, and the apparatus 1200 may include a unit for executing the method performed by the fifth network element in the method embodiment . Moreover, each unit in the apparatus 1200 and the above-mentioned other operations and/or functions are respectively for implementing the corresponding process of the method embodiment in the fifth network element in the method embodiment.
  • the transceiver unit 1210 can be used to execute steps 602 , 604 , 605 , and 605 of the method 600 ; the processing unit 1220 can be used to execute the processing steps of the method 600 , such as Step 603.
  • the transceiver unit 1210 can be used to execute steps 701 and 704 in the method 700 ; the processing unit 1220 can be used to execute the processing steps in the method 700 , such as step 702 .
  • the transceiver unit 1210 can be used to execute steps 802 , 804 - 806 of the method 800 ; the processing unit 1220 can be used to execute the processing steps of the method 800 , such as step 803 .
  • the transceiver unit 1210 can be used to execute steps 902 , 904 , 908 and 909 in the method 900 ; the processing unit 1220 can be used to execute the processing steps of the method 900 , such as step 903 .
  • the transceiver unit 1210 can be used to execute steps 1001 and 1004 in the method 1000 ; the processing unit 1220 can be used to execute the processing steps of the method 1000 , such as steps 1002 and 1003 .
  • the processing unit 1220 in the above embodiments may be implemented by at least one processor or processor-related circuits.
  • the transceiver unit 1210 may be implemented by a transceiver or a transceiver-related circuit.
  • the storage unit may be implemented by at least one memory.
  • an embodiment of the present application further provides an apparatus 1300 .
  • the apparatus 1300 includes a processor 1310 coupled with a memory 1320 for storing computer programs or instructions and/or data, and the processor 1310 for executing the computer programs or instructions and/or data stored in the memory 1320 such that The methods in the above method embodiments are performed.
  • the apparatus 1300 includes one or more processors 1310 .
  • the apparatus 1300 may further include a memory 1320 .
  • the device 1300 may include one or more memories 1320 .
  • the memory 1320 may be integrated with the processor 1310, or provided separately.
  • the apparatus 1300 may further include a transceiver 1330, and the transceiver 1330 is used for signal reception and/or transmission.
  • the processor 1310 is used to control the transceiver 1330 to receive and/or transmit signals.
  • the apparatus 1300 is configured to implement the operations performed by the network device (eg, each of the foregoing network elements) in the above method embodiments.
  • This embodiment of the present application further provides an apparatus 1400, where the apparatus 1400 may be a network device or a chip.
  • the apparatus 1400 may be configured to perform the operations performed by the network device (eg, each of the foregoing network elements) in the foregoing method embodiments.
  • Figure 14 shows a simplified schematic diagram of the structure.
  • Device 1400 includes part 1410 and part 1420 .
  • the 1410 part is mainly used for sending and receiving radio frequency signals and the conversion of radio frequency signals and baseband signals; the 1420 part is mainly used for baseband processing and controlling the base station.
  • the 1410 part may generally be referred to as a transceiver unit, a transceiver, a transceiver circuit, or a transceiver.
  • the 1420 part is usually the control center of the base station, which can usually be called a processing unit, and is used to control the base station to perform the processing operations on the receiving end device side in the above method embodiments.
  • the transceiver unit of part 1410 which may also be called a transceiver or a transceiver, etc., includes an antenna and a radio frequency circuit, where the radio frequency circuit is mainly used for radio frequency processing.
  • the device used for implementing the receiving function in part 1410 may be regarded as a receiving unit
  • the device used for implementing the sending function may be regarded as a sending unit, that is, part 1410 includes a receiving unit and a sending unit.
  • the receiving unit may also be referred to as a receiver, a receiver, or a receiving circuit, and the like
  • the transmitting unit may be referred to as a transmitter, a transmitter, or a transmitting circuit, and the like.
  • the 1420 portion may include one or more single boards, each of which may include one or more processors and one or more memories.
  • the processor is used to read and execute the program in the memory to realize the baseband processing function and control the base station. If there are multiple boards, each board can be interconnected to enhance the processing capability.
  • one or more processors may be shared by multiple boards, or one or more memories may be shared by multiple boards, or one or more processors may be shared by multiple boards at the same time. device.
  • FIG. 14 is only an example and not a limitation, and the above-mentioned network device including a transceiver unit and a processing unit may not depend on the structure shown in FIG. 14 .
  • the chip When the device 1400 is a chip, the chip includes a transceiver unit and a processing unit.
  • the transceiver unit may be an input/output circuit or a communication interface;
  • the processing unit may be a processor, a microprocessor or an integrated circuit integrated on the chip.
  • the apparatus 1400 may also be a chip system or a processing system, so that the device on which the apparatus 1400 is installed can implement the methods and functions of the embodiments of the present application.
  • the processing unit 1420 can be a chip system or a processing circuit in the processing system, which can control the device on which the chip system or the processing system is installed, and can also be coupled and linked to the storage unit to call the instructions in the storage unit, so that the device can realize the
  • the transceiver unit 1410 may be an input/output circuit in a chip system or a processing system, which outputs information processed by the chip system, or inputs data or signaling information to be processed into the chip system for processing. .
  • Embodiments of the present application further provide a computer-readable storage medium, on which computer instructions for implementing the method performed by a network device (eg, each network element) in the foregoing method embodiments are stored.
  • a network device eg, each network element
  • the computer program when executed by a computer, the computer can implement the method executed by the network device in the above method embodiments.
  • Embodiments of the present application further provide a computer program product including instructions, which, when executed by a computer, enable the computer to implement the method executed by a network device (eg, each network element) in the above method embodiments.
  • a network device eg, each network element
  • Embodiments of the present application further provide a communication system, where the communication system includes the network devices (eg, various network elements) in the above embodiments, such as AF and PCF, or NEF and PCF, or AF, NEF, and PCF, etc. Wait.
  • the network devices eg, various network elements
  • the network devices such as AF and PCF, or NEF and PCF, or AF, NEF, and PCF, etc. Wait.
  • processors mentioned in the embodiments of the present application may be a central processing unit (central processing unit, CPU), and may also be other general-purpose processors, digital signal processors (digital signal processors, DSP), application-specific integrated circuits ( application specific integrated circuit, ASIC), off-the-shelf programmable gate array (field programmable gate array, FPGA) or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, etc.
  • a general purpose processor may be a microprocessor or the processor may be any conventional processor or the like.
  • the memory mentioned in the embodiments of the present application may be a volatile memory and/or a non-volatile memory.
  • the non-volatile memory may be read-only memory (ROM), programmable read-only memory (PROM), erasable programmable read-only memory (EPROM), electrically programmable Erase programmable read-only memory (electrically EPROM, EEPROM) or flash memory.
  • Volatile memory may be random access memory (RAM).
  • RAM can be used as an external cache.
  • RAM may include the following forms: static random access memory (SRAM), dynamic random access memory (DRAM), synchronous dynamic random access memory (SDRAM) , double data rate synchronous dynamic random access memory (double data rate SDRAM, DDR SDRAM), enhanced synchronous dynamic random access memory (enhanced SDRAM, ESDRAM), synchronous link dynamic random access memory (synchlink DRAM, SLDRAM) and Direct memory bus random access memory (direct rambus RAM, DR RAM).
  • SRAM static random access memory
  • DRAM dynamic random access memory
  • SDRAM synchronous dynamic random access memory
  • SDRAM double data rate synchronous dynamic random access memory
  • ESDRAM enhanced synchronous dynamic random access memory
  • SLDRAM synchronous link dynamic random access memory
  • Direct memory bus random access memory direct rambus RAM, DR RAM
  • the processor is a general-purpose processor, DSP, ASIC, FPGA or other programmable logic devices, discrete gate or transistor logic devices, or discrete hardware components
  • the memory storage module
  • memory described herein is intended to include, but not be limited to, these and any other suitable types of memory.
  • the disclosed apparatus and method may be implemented in other manners.
  • the apparatus embodiments described above are only illustrative.
  • the division of the units is only a logical function division. In actual implementation, there may be other division methods.
  • multiple units or components may be combined or Can be integrated into another system, or some features can be ignored, or not implemented.
  • the shown or discussed mutual coupling or direct coupling or communication connection may be through some interfaces, indirect coupling or communication connection of devices or units, which may be in electrical, mechanical or other forms.
  • the units described as separate components may or may not be physically separated, and components displayed as units may or may not be physical units, that is, may be located in one place, or may be distributed to multiple network units. Some or all of the units may be selected according to actual needs to implement the solution provided in this application.
  • each functional unit in each embodiment of the present application may be integrated into one unit, or each unit may exist physically alone, or two or more units may be integrated into one unit.
  • the computer may be implemented in whole or in part by software, hardware, firmware or any combination thereof.
  • software it can be implemented in whole or in part in the form of a computer program product.
  • the computer program product includes one or more computer instructions.
  • the computer may be a general purpose computer, special purpose computer, computer network, or other programmable device.
  • the computer may be a personal computer, a server, or a network device or the like.
  • the computer instructions may be stored in or transmitted from one computer-readable storage medium to another computer-readable storage medium, for example, the computer instructions may be downloaded from a website site, computer, server, or data center Transmission to another website site, computer, server, or data center is by wire (eg, coaxial cable, fiber optic, digital subscriber line (DSL)) or wireless (eg, infrared, wireless, microwave, etc.).
  • the computer-readable storage medium may be any available medium that can be accessed by a computer or a data storage device such as a server, data center, etc. that includes an integration of one or more available media.
  • the usable media may be magnetic media (eg, floppy disks, hard disks, magnetic tapes), optical media (eg, DVDs), or semiconductor media (eg, solid state disks (SSDs), etc.
  • the aforementioned usable media may include But not limited to: U disk, mobile hard disk, read-only memory (ROM), random access memory (RAM), magnetic disk or optical disk and other media that can store program codes.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Business, Economics & Management (AREA)
  • Accounting & Taxation (AREA)
  • Mobile Radio Communication Systems (AREA)
  • Communication Control (AREA)

Abstract

本申请提供了一种确定策略的方法和通信装置。该方法可以包括：第一网元接收来自第二网元的请求消息，该请求消息包括应用所需的业务链的信息；第一网元根据该应用所需的业务链的信息，为应用制定业务链策略，并且向第三网元发送该应用对应的业务链策略。这样，当确定要提供应用增值服务的情况下，可以在请求消息中将所需的业务链的相关信息通知给第二网元，从而第二网元可以根据该所需的业务链的信息，直接制定业务链策略，从而可以快速响应对业务链的快速变化的需求。

Description

确定策略的方法和通信装置
本申请要求于2021年02月09日提交中国专利局、申请号为202110179154.1、申请名称为“确定策略的方法和通信装置”的中国专利申请的优先权，其全部内容通过引用结合在本申请中。
技术领域
本申请涉及通信技术领域，尤其涉及一种确定策略的方法和通信装置。
背景技术
在一些***中，如第五代(5th generation，5G)***中，用户接入网络后建立协议数据单元(protocol data unit，PDU)会话(PDU session)，并通过PDU会话访问外部数据网络，与部署在数据网络中的应用服务器交互。通过部署移动服务增值网络，即提供业务链的方式，可以为用户提供质量体验(quality of experience，QoE)，减少网络带宽压力。如何能够满足对业务链的快速变化的需求是亟需解决的问题。
发明内容
本申请提供一种确定策略的方法和通信装置，以期可以快速响应对业务链的快速变化的需求。
第一方面，提供了一种确定策略的方法，该方法可以由网络设备执行，或者，也可以由用于网络设备的芯片、芯片***或电路执行，本申请对此不作限定。为了便于描述，下面以由第一网元执行为例进行说明。
该方法可以包括：第一网元接收来自第二网元的第一请求消息，第一请求消息包括应用所需的业务链的信息；第一网元向第三网元发送应用对应的业务链策略，应用对应的业务链策略是根据应用所需的业务链的信息制定的。
示例地，该第一网元例如可以为策略控制功能(policy control function，PCF)网元、或者拜访地策略控制功能(visited-policy control function，V-PCF)网元等。
示例地，该第二网元例如可以为应用功能(application function，AF)网元、或者能力开放功能(network exposure function，NEF)网元等。
示例地，该第三网元例如可以为会话管理功能(session management function，SMF)网元，或者其它可以实现该网元功能的网络设备。
示例地，第一请求消息可以为数据导向消息，或者也可以为服务质量请求消息。
示例地，方法还可以包括：根据应用所需的业务链的信息，制定应用对应的业务链策略。制定应用对应的业务链策略，例如可以理解为，对用户访问的应用制定业务导向策略(traffic steering policy，TSP)。
基于上述技术方案，当确定要提供应用增值服务的情况下，在请求制定业务链策略时， 可以携带应用所需的业务链的信息。从而，第一网元可以根据请求中携带的应用所需的业务链的信息确定是否授权，或者第一网元可以直接根据请求中携带的应用所需的业务链的信息来制定业务链策略。从而，可以快速响应应用对业务链的快速变化需求。
结合第一方面，在第一方面的某些实现方式中，应用所需的业务链的信息为应用所需的业务链标识。
基于上述技术方案，第一网元可以基于应用所需要的业务链标识，制定应用对应的业务链策略。
结合第一方面，在第一方面的某些实现方式中，应用所需的业务链的信息为应用所需的一个或多个业务功能的信息。
基于上述技术方案，第一网元可以基于应用所需要的一个或多个业务功能的信息，制定应用对应的业务链策略。
结合第一方面，在第一方面的某些实现方式中，方法还包括：第一网元根据应用所需的一个或多个业务功能的信息，确定支持应用的一个或多个业务功能的信息，并向第二网元发送支持应用的一个或多个业务功能的信息。
基于上述技术方案，第一网元可以基于应用所需要的一个或多个业务功能的信息，确定支持应用的一个或多个业务功能的信息，例如，该支持应用的一个或多个业务功能，属于应用所需的一个或多个业务功能中的部分业务功能。从而第二网元可以基于第一网元支持的一个或多个业务功能的信息，进行灵活调整和处理。
结合第一方面，在第一方面的某些实现方式中，一个或多个业务功能的信息，为一个或多个业务功能的标识或类型。
基于上述技术方案，业务功能可以用标识或类型来标识。
结合第一方面，在第一方面的某些实现方式中，第一网元接收来自第二网元的第一请求消息，第一请求消息包括应用所需的业务链的信息，包括：第一网元接收来自第二网元的第一请求消息，第一请求消息包括应用所需的业务链的信息与数据网络接入标识之间的对应关系。
也就是说，第一请求消息中包括的应用所需的业务链的信息具体为，应用所需的业务链的信息与数据网络接入标识之间的对应关系。
一示例，第一请求消息中具体包括应用所需的业务链标识与数据网络接入标识之间的对应关系。
又一示例，第一请求消息中具体包括应用所需的一个或多个业务功能与数据网络接入标识之间的对应关系。
基于上述技术方案，可以在第一请求消息中携带应用所需的业务链的信息与数据网络接入标识之间的对应关系，这样可以根据应用所需的业务链的信息确定应用对应的业务链策略，进而可以得到业务链策略与数据网络接入标识之间的对应关系。
结合第一方面，在第一方面的某些实现方式中，第一网元向第三网元发送应用对应的业务链策略与数据网络接入标识之间的对应关系。
示例地，应用对应的业务链策略与数据网络接入标识之间的对应关系，是根据应用所需的业务链的信息与数据网络接入标识之间的对应关系确定的。
结合第一方面，在第一方面的某些实现方式中，方法还包括：第一网元向第四网元发 送第二请求消息，第二请求消息包括应用对应的业务链策略和访问应用的用户的标识，第二请求消息用于请求对用户访问的应用对应的业务链策略进行授权。
基于上述技术方案，在有些场景下，如在漫游场景下，第一网元根据请求制定业务链策略后，可以向第四网元发送该业务链策略，以便进行第四网元的进一步授权。
结合第一方面，在第一方面的某些实现方式中，方法还包括：在第一网元向第四网元发送第二请求消息之前，方法还包括：第一网元接收第三网元发送的第一数据网络接入标识，第一网元根据第一数据网络接入标识确定用户访问应用对应的业务链策略；或者，第一网元接收第三网元发送的用户访问应用对应的业务链策略。
示例地，应用对应的业务链策略与数据网络接入标识之间具有对应关系，该数据网络接入标识包括第一数据网络接入标识。
结合第一方面，在第一方面的某些实现方式中，方法还包括：第一网元向第四网元发送第三请求消息，第三请求消息包括支持的一个或多个业务功能的信息和访问应用的用户的标识，第三请求消息用于请求对用于访问的应用支持的一个或多个业务功能的信息进行授权。
基于上述技术方案，在有些场景下，如在漫游场景下，第一网元根据请求确定支持的业务功能后，可以向第四网元发送该业务功能的信息，以便进行第四网元的进一步授权。
结合第一方面，在第一方面的某些实现方式中，在第一网元向第四网元发送第三请求消息之前，方法还包括：第一网元接收第三网元发送的第一数据网络接入标识，根据第一数据网络接入标识确定支持用户访问的应用的一个或多个业务功能；或者，第一网元接收第三网元发送的用户访问应用对应的业务链策略，根据用户访问应用对应的业务链策略确定支持用户访问的应用的一个或多个业务功能。
示例地，应用对应的业务链策略与数据网络接入标识之间具有对应关系，该数据网络接入标识包括第一数据网络接入标识。
第二方面，提供了一种确定策略的方法，该方法可以由网络设备执行，或者，也可以由用于网络设备的芯片、芯片***或电路执行，本申请对此不作限定。为了便于描述，下面以由第二网元执行为例进行说明。
该方法可以包括：向第一网元发送第一请求消息，第一请求消息包括应用所需的业务链的信息；接收来自第一网元的指示信息，指示信息用于指示接受应用所需的业务链的请求。
示例地，该第二网元例如可以为AF网元、或者NEF网元等。
基于上述技术方案，当确定要提供应用增值服务的情况下，在请求制定业务链策略时，可以携带应用所需的业务链的信息。从而，可以使得第一网元根据请求中携带的应用所需的业务链的信息确定是否授权，或者直接根据请求中携带的应用所需的业务链的信息来制定业务链策略。相比于需要依靠运营商策略来为应用制定业务链策略的方案，本申请实施例提供的方案能够快速响应应用对业务链的快速变化需求。
结合第二方面，在第二方面的某些实现方式中，应用所需的业务链的信息为以下任一项：应用所需的业务链标识、应用所需的外部业务链标识、应用所需的一个或多个业务功能的信息、应用所需的一个或多个外部业务功能的信息、应用所需的业务链的信息与数据网络接入标识之间的对应关系。
结合第二方面，在第二方面的某些实现方式中，方法还包括：第二网元接收来自第一网元的支持应用的一个或多个业务功能的信息。
示例地，应用所需的业务链的信息为应用所需的一个或多个业务功能的信息。
结合第二方面，在第二方面的某些实现方式中，方法还包括：第二网元接收来自第一网元的支持应用的一个或多个外部业务功能的信息。
示例地，应用所需的业务链的信息为应用所需的一个或多个外部业务功能的信息。
结合第二方面，在第二方面的某些实现方式中，一个或多个业务功能的信息，为一个或多个业务功能的标识或类型。
结合第二方面，在第二方面的某些实现方式中，在向第一网元发送第一请求消息之前，方法还包括：第二网元向第五网元发送第二请求消息，第二请求消息包括查询的业务链的信息；第二网元接收来自第五网元的支持查询的业务链的以下一项或多项信息：业务功能标识、业务链标识、业务功能标识和数据网络接入标识对应关系、业务链标识和数据网络接入标识对应关系。
示例地，查询的业务链的信息包括查询的业务功能的类型。
基于上述技术方案，第二网元可以动态请求业务链。例如，第二网元可通过查询获得相应的业务功能或业务链。
第三方面，提供了一种确定策略的方法，该方法可以由网络设备执行，或者，也可以由用于网络设备的芯片、芯片***或电路执行，本申请对此不作限定。为了便于描述，下面以由第五网元执行为例进行说明。
该方法可以包括：第五网元接收来自第二网元的请求消息，请求消息包括应用所需的业务链的信息；第五网元对应用所需的业务链的信息进行处理，并向第一网元发送处理后的业务链的信息。
示例地，该第五网元例如可以为NEF网元，或者其它可以实现该网元功能的网络设备。
基于上述技术方案，第二网元通过第五网元请求应用所需要的业务链处理时，在请求的信息中可以携带应用所需的业务链的信息，然后该第五网元可以先对该应用所需的业务链的信息进行处理，然后将处理后的信息发送给第一网元。这样，可以实现第一网元基于第二网元的请求，确定对应的业务链策略，或者说进行授权。从而，能够快速响应应用对业务链的快速变化的需求。
结合第三方面，在第三方面的某些实现方式中，应用所需的业务链的信息为应用所需的外部业务链标识，第五网元对应用所需的业务链的信息进行处理，包括：第五网元将外部业务链标识，映射为内部业务链标识；第五网元向第一网元发送处理后的业务链的信息，包括：第五网元向第一网元发送内部业务链标识。
结合第三方面，在第三方面的某些实现方式中，应用所需的业务链的信息为应用所需的外部业务功能的信息，第五网元对应用所需的业务链的信息进行处理，包括：第五网元将外部业务功能，映射为内部业务功能；第五网元向第一网元发送处理后的业务链的信息，包括：第五网元向第一网元发送内部业务功能的信息。
结合第三方面，在第三方面的某些实现方式中，方法还包括：第五网元根据应用所需的一个或多个外部业务功能的信息，确定支持应用的一个或多个外部业务功能的信息，并 向第二网元发送支持应用的一个或多个外部业务功能的信息。
结合第三方面，在第三方面的某些实现方式中，一个或多个外部业务功能的信息，为一个或多个外部业务功能的标识或类型。
结合第三方面，在第三方面的某些实现方式中，应用所需的业务链的信息为应用所需的外部业务链标识与数据网络接入标识之间的对应关系，或者，应用所需的业务链的信息为应用所需的一个或多个外部业务功能与数据网络接入标识之间的对应关系。
结合第三方面，在第三方面的某些实现方式中，应用所需的业务链的信息为应用所需的外部业务链标识与数据网络接入标识之间的对应关系，第五网元对应用所需的业务链的信息进行处理，包括：第五网元将外部业务链标识，映射为内部业务链标识；第五网元向第一网元发送处理后的业务链的信息，包括：第五网元向第一网元发送应用所需的内部业务链标识与数据网络接入标识之间的对应关系。
结合第三方面，在第三方面的某些实现方式中，应用所需的业务链的信息为应用所需的外部业务功能与数据网络接入标识之间的对应关系，第五网元对应用所需的业务链的信息进行处理，包括：第五网元将外部业务功能，映射为内部业务功能；第五网元向第一网元发送处理后的业务链的信息，包括：第五网元向第一网元发送应用所需的内部业务功能与数据网络接入标识之间的对应关系。
结合第三方面，在第三方面的某些实现方式中，方法还包括：第五网元接收来自业务链管理设备的注册请求消息，该注册请求消息中包括注册的业务链的以下一项或多项信息：业务功能类型和业务功能标识的对应关系、业务功能类型和外部业务链标识的对应关系、业务功能类型、业务功能标识和数据网络接入标识的对应关系、业务功能标识、外部业务链标识和数据网络接入标识的对应关系的对应关系。
第四方面，提供了一种确定策略的方法，该方法可以由网络设备执行，或者，也可以由用于网络设备的芯片、芯片***或电路执行，本申请对此不作限定。为了便于描述，下面以由第三网元执行为例进行说明。
该方法可以包括：第三网元接收来自第一网元的应用对应的业务链策略与数据网络接入标识之间的对应关系的信息，其中，数据网络接入标识包括第一数据网络接入标识；第三网元根据第一数据网络接入标识选择用户面网元，并指示用户面网元执行第一业务链策略，第一业务链策略为第一数据网络接入标识对应的业务链策略。
示例地，该第三网元例如可以为SMF网元，或者其它可以实现该网元功能的网络设备。
结合第四方面，在第四方面的某些实现方式中，方法还包括：第三网元向第一网元发送第一数据网络接入标识；或者，第三网元向第一网元发送第一业务链策略。
第五方面，提供了一种确定策略的方法，该方法可以由网络设备执行，或者，也可以由用于网络设备的芯片、芯片***或电路执行，本申请对此不作限定。为了便于描述，下面以由第一网元执行为例进行说明。
该方法可以包括：第一网元向第四网元发送请求消息，请求消息用于请求对一个或多个业务功能进行授权，或者，请求消息用于请求对应用对应的业务链策略进行授权；第一网元接收来自第四网元的该请求消息的响应消息。
示例地，该第一网元例如可以为V-PCF网元等，或者其它可以实现该网元功能的网 络设备；该第四网元例如可以为归属地策略控制功能(home-policy control function，H-PCF)网元等，或者其它可以实现该网元功能的网络设备。
第六方面，提供了一种确定策略的方法，该方法可以由网络设备执行，或者，也可以由用于网络设备的芯片、芯片***或电路执行，本申请对此不作限定。为了便于描述，下面以由第四网元执行为例进行说明。
该方法可以包括：第四网元接收来自第一网元的请求消息，请求消息用于请求对一个或多个业务功能进行授权，或者，请求消息用于请求对应用对应的业务链策略进行授权；第四网元向第一网元发送该请求消息的响应消息。
例如，第四网元进行授权后，发送指示接受的确认信息。
基于上述技术方案，在有些场景下，如在漫游场景下，第一网元根据请求制定业务链策略后，可以向第四网元发送该业务链策略，以便进行第四网元的进一步授权。或者第一网元根据请求确定支持的业务功能后，可以向第四网元发送该业务功能的信息，以便进行第四网元的进一步授权。
结合第五方面或第六方面，在某些实现方式中，第一网元向第四网元发送请求消息，请求消息包括应用对应的业务链策略和访问该应用的用户的标识，该请求消息用于请求对用户访问的应用对应的业务链策略进行授权。
结合第五方面或第六方面，在某些实现方式中，第一网元向第四网元发送请求消息，请求消息包括一个或多个业务功能的信息和访问应用的用户的标识，该请求消息用于请求对用户访问的应用的一个或多个业务功能的信息进行授权。
第七方面，提供了一种业务链管理的方法，该方法可以由网络设备执行，或者，也可以由用于网络设备的芯片、芯片***或电路执行，本申请对此不作限定，为了便于描述，下面以由第五网元执行为例进行说明。
该方法可以包括：第五网元接收来自第二网元的请求消息，请求消息包括查询的业务链的信息；第五网元向第二网元发送响应消息，该响应消息用于指示支持的业务链的信息。
示例地，方法还可以包括：第五网元接收来业务链管理设备(service chain manager)的注册请求消息，该注册请求消息中包括注册的业务链的以下一项或多项信息：业务功能类型和业务功能标识的对应关系、业务功能类型和外部业务链标识的对应关系、业务功能类型、业务功能标识和数据网络接入标识的对应关系、业务功能标识、外部业务链标识和数据网络接入标识的对应关系的对应关系。
第八方面，提供了一种业务链管理的方法，该方法可以由网络设备执行，或者，也可以由用于网络设备的芯片、芯片***或电路执行，本申请对此不作限定，为了便于描述，下面以由第二网元执行为例进行说明。
该方法可以包括：第二网元向第五网元发送请求消息，请求消息包括查询的业务链的信息；第二网元接收来自第五网元的响应消息，该响应消息用于指示支持的业务链的信息。
基于上述技术方案，第二网元可以动态请求业务链。例如，第二网元可通过查询获得相应的业务功能或业务链。
结合第七方面或第八方面，在某些实现方式中，请求消息中携带的查询的业务链的信息，包括：需要的业务功能(service function)的类型以及数据网络接入标识信息。
示例地，第五网元可以根据数据网络接入标识信息，返回数据网络接入标识对应支持 的service function或者业务链标识以及包括的service function类型。
示例地，第五网元可以根据service function的类型，返回对应的service function标识或是业务链标识以及包括的service function类型。
第九方面，提供一种通信装置，该装置用于执行上述第一方面至第八方面提供的方法。具体地，该装置可以包括用于执行第一方面至第八方面提供的方法的单元和/或模块，如处理单元和/或通信单元。
在一种实现方式中，该装置为网络设备。当该装置为网络设备时，通信单元可以是收发器，或，输入/输出接口；处理单元可以是处理器。
在另一种实现方式中，该装置为用于网络设备中的芯片、芯片***或电路。当该装置为用于通信设备中的芯片、芯片***或电路时，通信单元可以是该芯片、芯片***或电路上的输入/输出接口、接口电路、输出电路、输入电路、管脚或相关电路等；处理单元可以是处理器、处理电路或逻辑电路等。
一可能情况，该装置为第一网元或第一网元中的芯片、芯片***或电路。在该情况下，该装置可以包括用于执行第一方面、第五方面提供的方法的单元和/或模块，如处理单元和/或通信单元。
又一可能情况，该装置为第二网元或第二网元中的芯片、芯片***或电路。在该情况下，该装置可以包括用于执行第二方面、第八方面提供的方法的单元和/或模块，如处理单元和/或通信单元。
又一可能情况，该装置为第三网元或第三网元中的芯片、芯片***或电路。在该情况下，该装置可以包括用于执行第四方面提供的方法的单元和/或模块，如处理单元和/或通信单元。
又一可能情况，该装置为第四网元或第四网元中的芯片、芯片***或电路。在该情况下，该装置可以包括用于执行第六方面提供的方法的单元和/或模块，如处理单元和/或通信单元。
又一可能情况，该装置为第五网元或第五网元中的芯片、芯片***或电路。在该情况下，该装置可以包括用于执行第三方面、第七方面提供的方法的单元和/或模块，如处理单元和/或通信单元。
可选地，上述收发器可以为收发电路。可选地，上述输入/输出接口可以为输入/输出电路。
第十方面，提供一种通信装置，该装置包括：存储器，用于存储程序；处理器，用于执行存储器存储的程序，当存储器存储的程序被执行时，处理器用于执行上述第一方面至第八方面提供的方法。
在一种实现方式中，该装置为网络设备(如上述各个网元)。
在另一种实现方式中，该装置为用于网络设备(如上述各个网元)中的芯片、芯片***或电路。
第十一方面，本申请提供一种处理器，用于执行上述各方面提供的方法。在执行这些方法的过程中，上述方法中有关发送上述信息和获取/接收上述信息的过程，可以理解为由处理器输出上述信息的过程，以及处理器接收输入的上述信息的过程。在输出上述信息时，处理器将该上述信息输出给收发器，以便由收发器进行发射。该上述信息在由处理器 输出之后，还可能需要进行其他的处理，然后才到达收发器。类似的，处理器接收输入的上述信息时，收发器获取/接收该上述信息，并将其输入处理器。更进一步的，在收发器收到该上述信息之后，该上述信息可能需要进行其他的处理，然后才输入处理器。
基于上述原理，举例来说，前述方法中提及的接收请求消息可以理解为处理器接收输入的信息。
对于处理器所涉及的发射、发送和获取/接收等操作，如果没有特殊说明，或者，如果未与其在相关描述中的实际作用或者内在逻辑相抵触，则均可以更加一般性的理解为处理器输出和接收、输入等操作，而不是直接由射频电路和天线所进行的发射、发送和接收操作。
在实现过程中，上述处理器可以是专门用于执行这些方法的处理器，也可以是执行存储器中的计算机指令来执行这些方法的处理器，例如通用处理器。上述存储器可以为非瞬时性(non-transitory)存储器，例如只读存储器(Read Only Memory，ROM)，其可以与处理器集成在同一块芯片上，也可以分别设置在不同的芯片上，本申请实施例对存储器的类型以及存储器与处理器的设置方式不做限定。
第十二方面，提供一种计算机可读存储介质，该计算机可读介质存储用于设备执行的程序代码，该程序代码包括用于执行上述第一方面至第八方面提供的方法。
第十三方面，提供一种包含指令的计算机程序产品，当该计算机程序产品在计算机上运行时，使得计算机执行上述第一方面至第八方面提供的方法。
第十四方面，提供一种芯片，所述芯片包括处理器与通信接口，所述处理器通过所述通信接口读取存储器上存储的指令，执行上述第一方面至第八方面提供的方法。
可选地，作为一种实现方式，所述芯片还可以包括存储器，所述存储器中存储有指令，所述处理器用于执行所述存储器上存储的指令，当所述指令被执行时，所述处理器用于执行上述第一方面至第八方面提供的方法。
第十五方面，提供一种通信***，包括以下一项或多项：第一网元、第二网元、第三网元、第四网元、第五网元。
附图说明
图1示出了适用于本申请实施例的网络架构的一示意图。
图2示出了适用于本申请实施例的网络架构的另一示意图。
图3是本申请一实施例提供的一种确定策略的方法300的示意图。
图4是根据本申请另一实施例提供的一种确定策略的方法400的示意图。
图5是适用于本申请一实施例的确定策略的一示意性流程图。
图6是适用于本申请一实施例的确定策略的又一示意性流程图。
图7是适用于本申请一实施例的确定策略的又一示意性流程图。
图8是适用于本申请一实施例的确定策略的又一示意性流程图。
图9是适用于本申请一实施例的确定策略的又一示意性流程图。
图10是适用于本申请一实施例的确定策略的又一示意性流程图。
图11是适用于本申请实施例的业务链管理的示意性流程图。
图12是根据本申请实施例提供的通信装置的示意性框图。
图13是根据本申请实施例提供的通信装置的另一示意性框图。
图14是本申请实施例提供的一种通信装置的结构示意图。
具体实施方式
下面将结合附图，对本申请中的技术方案进行描述。
本申请实施例的技术方案可以应用于各种通信***，例如：第五代(5th generation，5G)***或新无线(new radio，NR)、长期演进(long term evolution，LTE)***、LTE频分双工(frequency division duplex，FDD)***、LTE时分双工(time division duplex，TDD)等。本申请提供的技术方案还可以应用于未来的通信***，如第六代移动通信***。本申请实施例的技术方案还可以应用于设备到设备(device to device，D2D)通信，车辆外联(vehicle-to-everything，V2X)通信，机器到机器(machine to machine，M2M)通信，机器类型通信(machine type communication，MTC)，以及物联网(internet of things，IoT)通信***或者其他通信***。
为便于理解本申请实施例，首先结合图1和图2详细说明适用于本申请实施例的通信***。
作为示例性说明，图1示出了适用于本申请实施例的网络架构的一示意图。如图1所示，该网络架构例如可以包括但不限于以下：用户设备(user equipment，UE)、接入网(access network，AN)、接入和移动性管理功能(access and mobility management function，AMF)网元、会话管理功能(session management function，SMF)网元、用户面功能(user plane function，UPF)网元、策略控制功能(policy control function，PCF)网元、统一数据管理(unified data management，UDM)网元、应用功能(application function，AF)、数据网络(data network，DN)等。
下面对图1中示出的各网元做简单介绍：
1、终端设备：可以称为用户设备(user equipment，UE)、接入终端、用户单元、用户站、移动站、移动台(mobile station，MS)、移动终端(mobile terminal，MT)、远方站、远程终端、移动设备、用户终端、终端、无线通信设备、用户代理或用户装置。终端设备可以是一种向用户提供语音/数据连通性的设备，例如，具有无线连接功能的手持式设备、车载设备等。目前，一些终端的举例可以为：手机(mobile phone)、平板电脑(pad)、带无线收发功能的电脑(如笔记本电脑、掌上电脑等)、移动互联网设备(mobile internet device，MID)、虚拟现实(virtual reality，VR)设备、增强现实(augmented reality，AR)设备、工业控制(industrial control)中的无线终端、无人驾驶(self driving)中的无线终端、远程医疗(remote medical)中的无线终端、智能电网(smart grid)中的无线终端、运输安全(transportation safety)中的无线终端、智慧城市(smart city)中的无线终端、智慧家庭(smart home)中的无线终端、蜂窝电话、无绳电话、会话启动协议(session initiation protocol，SIP)电话、无线本地环路(wireless local loop，WLL)站、个人数字助理(personal digital assistant，PDA)、具有无线通信功能的手持设备、计算设备或连接到无线调制解调器的其它处理设备、车载设备、可穿戴设备，5G网络中的终端设备或者未来演进的公用陆地移动通信网络(public land mobile network，PLMN)中的终端设备等。
此外，终端设备还可以是物联网(Internet of things，IoT)***中的终端设备。IoT是 未来信息技术发展的重要组成部分，其主要技术特点是将物品通过通信技术与网络连接，从而实现人机互连，物物互连的智能化网络。IoT技术可以通过例如窄带(narrow band，NB)技术，做到海量连接，深度覆盖，终端省电。
此外，终端设备还可以包括智能打印机、火车探测器、加油站等传感器，主要功能包括收集数据(部分终端设备)、接收网络设备的控制信息与下行数据，并发送电磁波，向网络设备传输上行数据。
应理解，终端设备可以是任何可以接入网络的设备。终端设备与接入网设备之间可以采用某种空口技术相互通信。
可选地，UE可以用于充当基站。例如，UE可以充当调度实体，其在V2X或D2D等中的UE之间提供侧行链路信号。比如，蜂窝电话和汽车利用侧行链路信号彼此通信。蜂窝电话和智能家居设备之间通信，而无需通过基站中继通信信号。
2、接入网(access network，AN)：接入网可以为特定区域的授权用户提供入网功能，包含无线接入网(radio access network，RAN)设备和AN设备。RAN设备主要是第三代合作伙伴计划(3rd Generation Partnership Project，3GPP)网络无线网络设备，AN设备可以是非3GPP(non-3GPP)定义的接入网设备。
接入网络可以为采用不同接入技术的接入网络。目前的无线接入技术有两种类型：3GPP接入技术(例如3G、4G或5G***中采用的无线接入技术)和非3GPP(non-3GPP)接入技术。3GPP接入技术是指符合3GPP标准规范的接入技术，例如，5G***中的接入网设备称为下一代基站节点(next generation Node Base station，gNB)或者RAN。非3GPP接入技术是指不符合3GPP标准规范的接入技术，例如，以无线保真(wireless fidelity，WiFi)中的接入点(access point，AP)为代表的空口技术、全球互联微波接入(worldwide interoperability for microwave access，WiMAX)、码分多址(code division multiple access，CDMA)网络等。接入网设备(AN设备)可以允许终端设备和3GPP核心网之间采用非3GPP技术互连互通。
基于无线通信技术实现接入网络功能的接入网可以称为RAN。无线接入网能够负责空口侧的无线资源管理、服务质量(quality of service，QoS)管理、数据压缩和加密等功能。无线接入网为终端设备提供接入服务，进而完成控制信号和用户数据在终端和核心网之间的转发。
无线接入网例如可以包括但不限于：宏基站、微基站(也称为小站)、无线网络控制器(radio network controller，RNC)、节点B(Node B，NB)、基站控制器(base station controller，BSC)、基站收发台(base transceiver station，BTS)、家庭基站(例如，home evolved NodeB，或home Node B，HNB)、基带单元(baseband unit，BBU)，WiFi***中的AP、无线中继节点、无线回传节点、传输点(transmission point，TP)或者发送接收点(transmission and reception point，TRP)等，还可以为5G(如，NR)***中的gNB或传输点(TRP或TP)，5G***中的基站的一个或一组(包括多个天线面板)天线面板，或者，还可以为构成gNB或传输点的网络节点，如基带单元(BBU)，或，分布式单元(distributed unit，DU)，或者下一代通信6G***中的基站等。本申请实施例对无线接入网设备所采用的具体技术和具体设备形态不做限定。
接入网可以为小区提供服务。终端设备可以通过接入网设备分配的传输资源(例如， 频域资源，或者说，频谱资源)与小区通信。
3、AMF网元：主要用于移动性管理和接入管理等，如用户位置更新、用户注册网络、用户切换等。AMF还可用于实现移动性管理实体(mobility management entity，MME)中除会话管理之外的其它功能。例如，合法监听、或接入授权(或鉴权)等功能。
4、SMF网元：主要用于会话管理、UE的网际协议(Internet Protocol，IP)地址分配和管理、选择可管理用户平面功能、策略控制、或收费功能接口的终结点以及下行数据通知等。在本申请实施例中，SMF主要用户负责移动网络中的会话管理，如会话建立、修改、释放等。具体功能例如可以包括为终端设备分配IP地址、选择提供报文转发功能的UPF等。
5、UPF网元：负责终端设备中用户数据的转发和接收。UPF网元可以从数据网络(data network，DN)接收用户数据，通过接入网设备传输给终端设备。UPF网元还可以通过接入网设备从终端设备接收用户数据，转发到数据网络。UPF网元中为终端设备提供服务的传输资源和调度功能由SMF网元管理控制的。
6、PCF网元：用于指导网络行为的统一策略框架，为控制平面功能网元(例如AMF，SMF网元等)提供策略规则信息，负责获取与策略决策相关的用户签约信息等。
7、AF网元：主要支持与3GPP核心网交互来提供服务，例如影响数据路由决策、与策略控制功能(PCF)交互、或者向网络侧提供第三方等。
8、UDM网元：用于生成认证信任状，用户标识处理(如存储和管理用户永久身份等)，接入授权控制和签约数据管理等。
9、数据网络(DN)：用于为用户提供数据服务的服务网络。例如，因特网(Internet)、第三方的业务网络、IP多媒体服务业务(IP multi-media service，IMS)网络等。
在图1所示的网络架构中，各网元之间可以通过图中所示的接口通信，部分接口可以采用服务化接口的方式实现。如图1所示，UE和AMF之间可以通过N1接口进行交互，交互消息例如可以称为N1消息(N1Message)。RAN和AMF之间可以通过N2接口进行交互，N2接口可以用于非接入层(non-access stratum，NAS)消息的发送等。RAN和UPF之间可以通过N3接口进行交互，N3接口可以用于传输用户面的数据等。SMF和UPF之间可以通过N4接口进行交互，N4接口可以用于传输例如N3连接的隧道标识信息，数据缓存指示信息，以及下行数据通知消息等信息。AF与PCF之间可以通过N5接口进行交互，N5接口可以用于应用业务请求下发以及网络事件上。UPF和DN之间可以通过N6接口进行交互，N6接口可以于传输用户面的数据等。PCF与SMF之间可以通过N7接口进行交互，N7接口可以用于下发协议数据单元(protocol data unit，PDU)会话(PDU session)粒度以及业务数据流粒度控制策略等。AMF与UDM之间可以通过N8接口进行交互，N8接口可以用于AMF向UDM获取接入与移动性管理相关签约数据与鉴权数据，以及AMF向UDM注册UE当前移动性管理相关信息等。SMF与UDM之间可以通过N10接口进行交互，N10接口可以用于SMF向UDM获取会话管理相关签约数据，以及SMF向UDM注册UE当前会话相关信息等。SMF与AMF之间可以通过N11接口进行交互，N11接口可以用于传递RAN和UPF之间的PDU会话隧道信息、传递发送给UE的控制消息、传递发送给RAN的无线资源控制信息等。PCF与AMF之间可以通过N15接口进行交互，N15接口可以用于下发UE策略及接入控制相关策略等。其他接口与各网元之间的关系如 图1中所示，为了简洁，这里不一一详述。
应理解，上述应用于本申请实施例的网络架构仅是示例性说明，适用本申请实施例的网络架构并不局限于此，任何能够实现上述各个网元的功能的网络架构都适用于本申请实施例。
还应理解，图1中所示的AMF、SMF、UPF、PCF、UDM等可以理解为用于实现不同功能的网元，例如可以按需组合成网络切片。这些网元可以各自独立的设备，也可以集成于同一设备中实现不同的功能，或者可以是硬件设备中的网络元件，也可以是在专用硬件上运行的软件功能，或者是平台(例如，云平台)上实例化的虚拟化功能，本申请对于上述网元的具体形态不作限定。
还应理解，上述命名仅为便于区分不同的功能而定义，不应对本申请构成任何限定。本申请并不排除在5G网络以及未来其它的网络中采用其他命名的可能。例如，在6G网络中，上述各个网元中的部分或全部可以沿用5G中的术语，也可能采用其他名称等。
还应理解，图1中的各个网元之间的接口名称只是一个示例，具体实现中接口的名称可能为其他的名称，本申请对此不作具体限定。此外，上述各个网元之间的所传输的消息(或信令)的名称也仅仅是一个示例，对消息本身的功能不构成任何限定。
在一些***中(如5G***中)，UE接入网络后建立PDU会话，并通过PDU会话访问外部数据网络DN，与部署在DN中的应用服务器交互。根据用户访问的DN不同，网络可以根据网络策略选择接入DN的UPF作为锚点(anchor)，如记为PDU会话锚点(PDU session anchor，PSA)，并通过PSA的N6接口访问应用服务器。运营商或者第三方应用提供商可以部署移动服务增值网络，为用户提供质量体验(quality of experience，QoE)，减少网络带宽压力，并提供增值服务。
作为示例性说明，图2示出了适用于本申请实施例的网络架构的另一示意图。
图2主要以一种局域网(local area network，LAN)(如N6-LAN)的动态业务链的方案以适应于弹性的快速的服务部署变动，同时降低资本支出(capital expenditure，CAPX)的架构为例进行了示例性说明。以图2所示的架构为例，PCF可以对用户访问的应用制定数据导向策略(traffic steering policy，TSP)。TSP规则通常包括业务数据流描述信息以及对应的业务链(service chain)标识。UPF对业务数据进行检测后，将对应业务链标识标记在业务数据流的数据包上。交换机(switch)将根据业务链标识，将数据包动态的导向到相应的业务功能(service function)节点，也称使能器(enabler)。如图2所示，switch1根据业务链标识，将数据包动态的导向到相应的业务功能节点1和业务功能节点2上，switch 2根据业务链标识，将数据包动态的导向到相应的业务功能节点3和业务功能节点4上。
在现有方式中，PCF通常是根据用户的签约和运营商配置的策略制定TSP。这种方式，动态业务链的调整周期相对较长，不能快速响应应用对业务链的快速变化的需求。
本申请提供一种方法，能够快速响应应用对业务链的快速变化需求。应理解，本申请实施例不仅可以适用于上述图1和图2所示的架构，也可以适用于其他架构，对此不作限定。例如，本申请实施例可以适用于网络设备为应用制定业务链的策略的任何场景中；又如，本申请实施例可以适用于为应用部署业务链的任何场景中。
下面将结合附图详细说明本申请提供的各个实施例。
图3是本申请一实施例提供的一种确定策略的方法300的示意图。方法300可以包括如下步骤。
310，第二网元向第一网元发送请求消息#1，该请求消息#1包括应用所需的业务链的信息。相应地，第一网元接收该请求消息#1。
应理解，请求消息#1是为区分做的命名，其命名不对本申请实施例的保护范围造成限定。
应用所需的业务链的信息，例如可以包括但不限于：应用所需的业务链标识(service chain identifier，SC Id)、应用所需的外部业务链标识(external service chain identifier，external SC Id)、应用所需的一个或多个业务功能(service function)的信息、应用所需的一个或多个外部service function的信息、应用所需的业务链的信息与数据网络接入标识(data network access identification，DNAI)之间的对应关系、或应用对应的业务链策略的信息。作为示例而非限定，应用所需的业务链的信息与DNAI之间的对应关系，例如可以为应用所需的业务链标识与DNAI之间的对应关系，或者可以为应用所需的一个或多个业务功能与DNAI之间的对应关系。具体地，下文详细介绍。
可选地，方法300还可以包括步骤320。
320，第一网元根据应用所需的业务链的信息，确定应用对应的业务链策略。
通过本申请实施例，当需要提供应用增值服务的情况下，在发送请求时，可以携带应用所需的业务链的信息。从而，可以根据请求中携带的应用所需的业务链的信息确定是否授权，或者直接根据请求中携带的应用所需的业务链的信息来制定业务链策略。相比于需要依靠运营商策略来为应用制定业务链策略的方案，本申请实施例提供的方案能够快速响应应用对业务链的快速变化需求。
应理解，本申请实施例关于第一网元和第二网元的具体形式不作限定。在需要提供应用增值服务的情况下，第二网元表示请求的设备，如第二网元在请求消息#1中携带应用所需的业务链的信息；第一网元表示授权的设备或者确定业务链策略的设备，如第一网元根据请求消息#1中携带的应用所需的业务链的信息，授权或者制定业务链策略。
作为示例而非限定，第一网元例如可以为PCF，或者也可以为V-PCF，等等，对此不作限定。第二网元例如可以为AF，或者也可以为能力开放功能(network exposure function，NEF)，等等，对此不作限定。
作为示例而非限定，下面介绍几种可能的实现方式。
实现方式1，应用所需的业务链的信息包括应用所需的业务链标识，第一网元根据应用所需的业务链标识，确定应用对应的业务链策略。
一示例，第一网元为PCF，第二网元为AF。例如，AF向PCF发送应用所需的业务链标识，PCF根据应用所需的业务链标识，确定应用对应的业务链策略。
又一示例，第一网元为PCF，第二网元为NEF。例如，NEF接收应用所需的外部业务链标识，如NEF接收来自AF的应用所需的外部业务链标识。NEF将应用所需的外部业务链标识映射为内部业务链标识(即业务链标识)，并且将该内部业务链标识发送给PCF。PCF根据应用所需的业务链标识，确定应用对应的业务链策略。
实现方式2，应用所需的业务链的信息包括应用所需的一个或多个业务功能的信息，第一网元根据应用所需的一个或多个业务功能的信息，确定应用对应的业务链策略。其中， 业务功能的信息，例如可以包括业务功能的标识和/或业务功能的类型。
一示例，第一网元为PCF，第二网元为AF。例如，AF向PCF发送应用所需的业务功能的信息，PCF根据应用所需的业务功能的信息，确定应用对应的业务链策略。
又一示例，第一网元为PCF，第二网元为NEF。例如，NEF接收应用所需的外部业务功能的信息，如NEF接收来自AF的应用所需的外部业务功能的信息。NEF将应用所需的外部业务功能映射为内部业务功能(即业务功能)，并且将该内部业务功能的信息发送给PCF。PCF根据应用所需的内部业务功能的信息，确定应用对应的业务链策略。
实现方式3，应用所需的业务链的信息包括应用所需的业务链标识与DNAI之间的对应关系，第一网元根据应用所需的业务链标识与DNAI之间的对应关系，确定应用对应的业务链策略。
一示例，第一网元为PCF，第二网元为AF。例如，AF向PCF发送应用所需的业务链标识与DNAI之间的对应关系，PCF根据应用所需的业务链标识与DNAI之间的对应关系，确定应用对应的业务链策略。
又一示例，第一网元为PCF，第二网元为NEF。例如，NEF接收应用所需的外部业务链标识与DNAI之间的对应关系，如NEF接收来自AF的应用所需的外部业务链标识与DNAI之间的对应关系。NEF将应用所需的外部业务链标识映射为内部业务链标识(即业务链标识)，并且将该内部业务链标识与DNAI之间的对应关系发送给PCF。PCF根据应用所需的业务链标识与DNAI之间的对应关系，确定应用对应的业务链策略。
实现方式4，应用所需的业务链的信息包括应用所需的一个或多个业务功能的信息与DNAI之间的对应关系，第一网元根据应用所需的一个或多个业务功能的信息与DNAI之间的对应关系，确定应用对应的业务链策略。
一示例，第一网元为PCF，第二网元为AF。例如，AF向PCF发送应用所需的业务功能与DNAI之间的对应关系，PCF根据应用所需的业务功能与DNAI之间的对应关系，确定应用对应的业务链策略。
又一示例，第一网元为PCF，第二网元为NEF。例如，NEF接收应用所需的外部业务功能与DNAI之间的对应关系，如NEF接收来自AF的应用所需的外部业务功能与DNAI之间的对应关系。NEF将应用所需的外部业务功能映射为内部业务功能(即业务功能)，并且将该内部业务功能与DNAI之间的对应关系发送给PCF。PCF根据应用所需的内部业务功能与DNAI之间的对应关系，确定应用对应的业务链策略。
实现方式5，第一网元根据应用对应的业务链策略与DNAI之间的对应关系，确定应用对应的业务链策略。其中，应用对应的业务链策略与DNAI之间的对应关系，可以携带于应用所需的业务链的信息中，或者基于应用所需的一个或多个业务功能的信息与DNAI之间的对应关系确定，或者基于应用所需的业务链标识与DNAI之间的对应关系确定。
应理解，上述几种可能的实现方式仅是示例性说明，对此不作严格限定。只要在请求时，第二网元可以将应用所需的业务链的相关信息通知给第一网元，第一网元可以根据应用所需的业务链的相关信息，直接授权或者确定相应的应用链策略的方案，都落入本申请实施例的保护范围。
330，第一网元向第三网元发送应用对应的业务链策略。相应地，第三网元接收该应用对应的业务链策略。
可选地，第一网元还可以向第二网元发送指示信息，该指示信息用于指示接受请求。
或者可以理解为，通过指示信息，指示对请求的业务链授权成功。
可选地，第一网元还可以根据应用所需的一个或多个业务功能的信息，确定支持应用的一个或多个业务功能的信息，并向第二网元发送该支持所述应用的一个或多个业务功能的信息。
第一网元确定支持应用的一个或多个业务功能的方式有很多，对此本申请实施例不作限定。一种可能的实现方式，第一网元可以根据与应用的签约和网络配置，确定用户访问应用可以支持的一个或多个业务功能。
应理解，上面仅是简单的说明，具体地，下面结合图5至图10所示的流程详细说明。
图4是根据本申请另一实施例提供的一种确定策略的方法400的示意图。方法400可以包括如下步骤。
410，第一网元向第四网元发送请求消息#2，请求消息#2用于请求支持用户访问应用的对一个或多个业务功能进行授权，或者，请求消息#2用于请求对用户访问应用对应的业务链策略进行授权。相应地，第四网元接收该请求消息#2。
一种可能的情况，第一网元向第四网元发送请求消息#2，请求消息#2包括应用对应的业务链策略和访问该应用的用户的标识，该请求消息#2用于请求对应用对应的业务链策略进行授权。
又一种可能的情况，第一网元向第四网元发送请求消息#2，请求消息#2包括一个或多个业务功能的信息和访问应用的用户的标识，该请求消息#2用于请求对支持用户访问应用的一个或多个业务功能进行授权。
420，第一网元接收第四网元的响应消息。相应地，第四网元向第一网元发送该响应消息。
例如，第四网元进行授权后，向第一网元发送指示接受的确认信息。
可选地，方法400还可以包括步骤401。
401，第一网元确定应用对应的业务链策略。示例地，第一网元可以根据方法300所述的方案确定应用对应的业务链策略。
通过本申请实施例，在有些场景下，如在漫游场景下，第一网元根据请求制定业务链策略后，可以向第四网元发送该业务链策略，以便进行第四网元的进一步授权。或者第一网元根据请求确定支持的业务功能后，可以向第四网元发送该业务功能的信息，以便进行第四网元的进一步授权。
应理解，本申请实施例关于第四网元的具体形式不作限定。在需要提供应用增值服务的情况下，第四网元可以表示授权的设备。作为示例而非限定，第一网元例如为V-PCF，第四网元例如为H-PCF。
方法400和方法300可以结合使用，也可以单独使用，对此不作限定。以结合使用为例，第一网元可以先通过方法300所示的方案定应用对应的业务链策略，然后通过方法400的方案请求业务链的授权。
为便于理解，结合图5至图10介绍可能的具体流程进行示例性说明。下面，为简洁，用SC Id表示业务链标识，用service function表示业务功能。
图5是适用于本申请一实施例的业务链处理的一示意性流程图。
如图5所示，方法500主要以UE、AMF、UPF、SMF、PCF以及AF之间的交互为例进行示例性说明。作为示例而非限定，图5所示的方法500可以用于AF在为应用请求网络资源时，向网络请求应用所需要的业务链处理流程。在方法500中，第二网元例如可以为AF，第一网元例如可以为PCF。图5所示的方法500可以包括如下步骤。
501，PDU会话的建立过程(PDU session establishment procedure)。
例如，UE发起PDU会话的建立，网络为PDU选择PSA，网络给UE分配地址。UE通过建立的PDU会话，可以访问DN网络中的应用服务器。可以理解，PDU会话建立后，也就是建立了终端设备和DN的数据传输通道。
如前所述，SMF主要用户负责移动网络中的会话管理。PDU会话可以在UE和SMF之间可以通过NAS会话管理(session management，SM)信令进行建立、修改或释放。
上述仅是示例性说明，对于步骤501本申请实施例不作限定。例如，步骤501可以参考现有技术或以后出现的方式。
502，AF向PCF发送SC Id的信息。
AF决定为UE正在访问的应用请求资源以及应用增值服务的情况下，AF可以向PCF发送请求业务链授权的请求消息，并且在该请求消息中携带SC Id的信息。
SC Id可以是AF提前获知的。例如，SC Id可以是应用和运营商之前协商好的业务链标识，或者也可以是协议或网络预先定义好的业务链标识，对此不作限定。
可选地，如果AF对应用上下行数据有不同的上下行业务量需求，那么AF可以提供不同的上下行SC Id。例如，AF可以针对上行提供一个上行的SC Id，针对下行提供一个下行的SC Id，在步骤502中，AF向PCF发送的SC Id的信息可以包括上行的SC Id和下行的SC Id。
一种可能的实现方式，AF可以向PCF发送Npcf接口策略授权建立请求(Npcf_PolicyAuthorization_Create Request)消息，该消息中包含SC Id的信息。其中，Npcf接口为PCF对外提供的服务化接口。可选地，该消息中还可以包括但不限于：业务流描述信息(如五元组信息)、请求的服务质量(quality of service，QoS)需求。其中，五元组信息通常是指源IP地址，源端口，目的IP地址，目的端口和传输层协议。
应理解，Npcf_PolicyAuthorization_Create Request消息，仅是示例性说明，对此不作限定。只要AF可以向PCF发送SC Id的信息，该SC Id的信息携带于任何消息中均是可行的。
PCF收到来自AF的SC Id的信息后，可以保存接收到的信息。此外，PCF可以向AF发送响应。
503，PCF向AF发送确认信息。
当PCF对AF请求业务链授权成功时，PCF向AF发送指示接受的确认信息。
一种可能的实现方式，PCF可以向AF发送Npcf接口策略授权建立响应(Npcf_PolicyAuthorization_Create Response)消息，该消息中包含指示接受的确认信息。
应理解，Npcf_PolicyAuthorization_Create Response消息，仅是示例性说明，对此不作限定。只要PCF可以向AF指示接受的确认信息，该指示接受的确认信息携带于任何消息中均是可行的。
504，PCF制定策略计费控制(policy and charging control，PCC)规则。
PCF可以根据AF的请求，制定PCC规则。该PCC规则中包括PCF根据SC Id确定的TSP Id。
可以理解，规则即表示与PDU会话或业务数据流相关的策略信息元素，对此可以参考现有描述，此处不作限定。
可选地，如果PCF决策的上下行TSP不同，那么PCC规则中可以包括不同的上下行TSP Id。例如，PCF可以针对上行确定一个TSP Id(如PCF可以根据上行的SC Id确定一个上行的TSP Id)，针对下行确定一个TSP Id(如PCF可以根据下行的SC Id确定一个下行的TSP Id)，在步骤504中，PCF制定的PCC规则中可以包括上行的TSP Id和下行的TSP Id。
505，PCF向SMF发送PCC规则。
PCC规则中包括PCF根据SC Id确定的TSP Id。如PCC规则中包括上行的TSP Id和下行的TSP Id。
一种可能的实现方式，PCF可以向SMF发送会话管理策略控制更新请求(Npcf_SMPolicyControl_UpdateNotify Request)消息，该消息中包含PCC规则的信息。
应理解，Npcf_SMPolicyControl_UpdateNotify Request消息，仅是示例性说明，对此不作限定。只要PCF可以向SMF指示PCC规则的信息，该PCC规则的信息携带于任何消息中均是可行的。
506，SMF向PCF发送确认信息。
SMF安装PCC规则后，可以向PCF返回确认信息。
一种可能的实现方式，SMF可以向PCF发送会话管理策略控制更新响应(Npcf_SMPolicyControl_UpdateNotify Response)消息。
应理解，Npcf_SMPolicyControl_UpdateNotify Response消息，仅是示例性说明，对此不作限定。
507，SMF制定N4规则。
SMF可以根据PCC规则，制定N4规则。该N4规则中可以包括分组检测规则(packet detection rule，PDR)和关联的转发动作规则(forwarding action rule，FAR)。PDR中包括业务流描述信息，FAR中包括TSP Id。
一可能的实现方式，SMF与UPF之间进行N4会话修改(N4 session modification)，以制定N4规则。
508，UPF进行业务路由(traffic steering)。
一种可能的实现方式，UPF根据PDR匹配到业务数据流，UPF根据FAR在数据流的数据包进行标记后，发送给局域网(如N6-LAN)。局域网中的交换机将根据数据包的标记将数据依次发送给业务功能节点。
上文结合图5所示的步骤501-508示例地介绍了一种可能的业务链处理流程，如应用在为应用请求网络资源时，向网络请求应用所需要的业务链处理的场景。应理解，上述各个步骤仅是示例性说明，对此不作严格限定。此外，上述各过程的序号的大小并不意味着执行顺序的先后，各过程的执行顺序应以其功能和内在逻辑确定，而不应对本申请实施例的实施过程构成任何限定。例如，上述步骤503和步骤504之间并没有严格的先后顺序，如可以先执行步骤503，再执行步骤504；或者也可以先执行步骤504，再执行步骤503； 或者也可以同步进行，对此不作限定。
基于上述方案，网络可动态的根据应用的请求，进行业务链的决策。例如，AF向网络请求业务数据流需要的应用增值服务(即业务链)时，携带应用所需要的业务链标识。这样，PCF基于AF的请求(即应用所需要的业务链标识)，确定对应的业务链策略，或者说进行授权。从而，能够快速响应应用对业务链的快速变化的需求。
图6是适用于本申请一实施例的业务链处理的又一示意性流程图。
如图6所示，方法600主要以UE、AMF、UPF、SMF、PCF、NEF以及AF之间的交互为例进行示例性说明。作为示例而非限定，图6所示的方法600可以用于AF在为应用请求网络资源时，通过NEF向网络请求应用所需要的业务链处理流程。在方法600中，第二网元例如可以为NEF，第一网元例如可以为PCF。图6所示的方法600可以包括如下步骤。
601，PDU会话的建立过程。
例如，UE发起PDU会话的建立，网络为PDU选择PSA，网络给UE分配地址。UE通过建立的PDU会话，可以访问DN网络中的应用服务器。
对于步骤601本申请实施例不作限定，例如，可以参考上述步骤501的描述。步骤601可以参考现有技术或以后出现的方式，此处不再介绍。
602，AF向NEF发送外部业务链标识external SC Id的信息。
AF决定为UE正在访问的应用请求资源以及应用增值服务的情况下，AF可以向NEF发送请求业务链授权的请求消息，并且在该请求消息中携带external SC Id的信息。
external SC Id可以是AF提前获知的。例如，external SC Id可以是应用和运营商之前协商好的业务链标识，或者也可以是协议或网络预先定义好的业务链标识，对此不作限定。
可选地，如果AF对应用上下行数据有不同的上下行业务量需求，那么AF可以提供不同的上下行external SC Id。例如，AF可以针对上行提供一个上行的external SC Id，针对下行提供一个下行的external SC Id，在步骤602中，AF向NEF发送的external SC Id的信息可以包括上行的external SC Id和下行的external SC Id。
一种可能的实现方式，AF可以向NEF发送Nnef接口有QoS的AF会话建立请求(Nnef_AFsessionWithQoS_Create Request)消息，该消息中包含external SC Id的信息。其中，Nnef接口为NEF对外提供的服务化接口。可选地，该消息中还可以包括但不限于：业务流描述信息(如五元组信息)、请求的QoS需求。
应理解，Nnef_AFsessionWithQoS_Create Request消息，仅是示例性说明，对此不作限定。只要AF可以向NEF发送external SC Id的信息，该external SC Id的信息携带于任何消息中均是可行的。
603，NEF进行处理。
NEF可以确定对AF的请求进行授权。NEF可以将external SC Id映射为内部业务链标识(internal service chain identifier，internal SC Id)，即NEF可以获得应用所需的internal SC Id。
可选地，如果AF提供不同的上下行external SC Id，如包括一个上行的external SC Id和一个下行的external SC Id，那么，NEF可以将上行的external SC Id映射为上行的internal SC Id，将下行的external SC Id映射为下行的internal SC Id。
NEF获得应用所需的internal SC Id，可以将该internal SC Id发送给PCF。
604，NEF向PCF发送internal SC Id的信息。
一种可能的实现方式，NEF可以向PCF发送Npcf_PolicyAuthorization_Create Request消息，该消息中包含internal SC Id的信息。可选地，该消息中还可以包括但不限于：业务流描述信息(如五元组信息)、请求的QoS需求。
应理解，Npcf_PolicyAuthorization_Create Request消息，仅是示例性说明，对此不作限定。只要NEF可以向PCF发送internal SC Id的信息，该internal SC Id的信息携带于任何消息中均是可行的。
605，PCF向NEF发送确认信息。
当PCF对请求的业务链授权成功时，PCF向NEF发送指示接受的确认信息。
一种可能的实现方式，PCF可以向NEF发送Npcf_PolicyAuthorization_Create Response消息，该消息中包含指示接受的确认信息。
应理解，Npcf_PolicyAuthorization_Create Response消息，仅是示例性说明，对此不作限定。只要PCF可以向NEF指示接受的确认信息，该指示接受的确认信息携带于任何消息中均是可行的。
606，NEF向AF发送确认信息。
一种可能的实现方式，NEF可以向AF发送Nnef接口有QoS的AF会话建立响应(Nnef_AFsessionWithQoS_Create Response)消息，该消息中包含指示接受的确认信息。
应理解，Nnef_AFsessionWithQoS_Create Response消息，仅是示例性说明，对此不作限定。只要NEF可以向AF指示接受的确认信息，该指示接受的确认信息携带于任何消息中均是可行的。
607，PCF制定PCC规则。
PCF可以根据AF的请求(即通过NEF转达的请求)，制定PCC规则。该PCC规则中包括PCF根据SC Id(即步骤604中接收到的internal SC Id)确定的TSP Id。
可选地，如果PCF决策的上下行TSP不同，那么PCC规则中可以包括不同的上下行TSP Id。例如，PCF可以针对上行确定一个TSP Id(如PCF可以根据上行的internal SC Id确定一个上行的TSP Id)，针对下行确定一个TSP Id(如PCF可以根据下行的internal SC Id确定一个下行的TSP Id)，在步骤607中，PCF制定的PCC规则中可以包括上行的TSP Id和下行的TSP Id。
608，PCF向SMF发送PCC规则。
对于步骤608，例如可以参考上述步骤505的描述，此处不再介绍。
609，SMF向PCF发送确认信息。
对于步骤609，例如可以参考上述步骤506的描述，此处不再介绍。
610，SMF制定N4规则。
对于步骤610，例如可以参考上述步骤507的描述，此处不再介绍。
611，UPF进行业务路由。
对于步骤611，例如可以参考上述步骤508的描述，此处不再介绍。
上文结合图6所示的步骤601-611示例地介绍了一种可能的业务链处理流程，如应用在为应用请求网络资源时，通过NEF向网络请求应用所需要的业务链处理的场景。应理 解，上述各个步骤仅是示例性说明，对此不作严格限定。此外，上述各过程的序号的大小并不意味着执行顺序的先后，各过程的执行顺序应以其功能和内在逻辑确定，而不应对本申请实施例的实施过程构成任何限定。例如，上述步骤605和步骤607之间并没有严格的先后顺序，如可以先执行步骤605，再执行步骤607；或者也可以先执行步骤607，再执行步骤605；或者也可以同步进行，对此不作限定。
基于上述方案，网络可动态的根据应用的请求，进行业务链的决策。例如，AF通过NEF向网络请求应用所需要的业务链处理时，携带外部业务链标识。NEF将该外部业务链标识映射为内部业务链标识后，将该内部业务链标识发送给PCF。这样，PCF基于AF的请求(即内部业务链标识)，确定对应的业务链策略，或者说进行授权。从而，能够快速响应应用对业务链的快速变化的需求。
图7是适用于本申请一实施例的业务链处理的又一示意性流程图。
如图7所示，方法700主要以UE、AMF、UPF、SMF、PCF、NEF、统一数据存储(unified data repository，UDR)以及AF之间的交互为例进行示例性说明。作为示例而非限定，图7所示的方法700可以用于AF通过NEF向网络提供各个DNAI对应的应用的业务链处理流程。在方法700中，第二网元例如可以为UDR或NEF，第一网元例如可以为PCF。图7所示的方法700可以包括如下步骤。
701，AF向NEF发送外部业务链标识external SC Id与DNAI的对应关系的信息。
external SC Id与DNAI的对应关系的信息可以通过列表的形式发送。例如，AF可以向NEF发送external SC Id与DNAI的对应关系列表。
一种可能的实现方式，AF可以向NEF发送Nnef接口流量引导建立请求(Nnef_TrafficInfluence_Create Request)消息，该消息中包含数据导向请求信息，该数据导向请求信息中包括external SC Id与DNAI的对应关系列表。可选地，该数据导向请求信息中还可以包括但不限于：适用的用户外部组标识或任意用户的指示信息。
应理解，Nnef_TrafficInfluence_Create Request消息，仅是示例性说明，对此不作限定。只要AF可以向NEF发送external SC Id与DNAI的对应关系的信息，该external SC Id与DNAI的对应关系的信息携带于任何消息中均是可行的。
702，NEF进行处理。
NEF可以确定对AF的请求进行授权。NEF可以将external SC Id映射为internal SC Id，即NEF可以获得internal SC Id与DNAI的对应关系。NEF还可以将外部组标识映射为内部组标识。
703，NEF将internal SC Id与DNAI的对应关系保存到UDR。
一种可能的实现方式，UDR从NEF处接收internal SC Id与DNAI的对应关系，并且保存internal SC Id与DNAI的对应关系。
示例地，NEF可以将在步骤701中接收到的数据导向请求信息保存到UDR中。可以理解，在步骤702中，NEF可以将external SC Id映射为internal SC Id，还可以将外部组标识映射为内部组标识，因此，UDR中保存的数据导向请求信息中可以包括：internal SC Id与DNAI的对应关系，适用的用户内部标识或任意用户的指示信息。
704，NEF向AF发送确认信息。
一种可能的实现方式，NEF可以向AF发送Nnef接口流量引导建立响应 (Nnef_TrafficInfluence_Create Response)消息，该消息中包含指示接受的确认信息。
应理解，Nnef_TrafficInfluence_Create Response消息，仅是示例性说明，对此不作限定。只要NEF可以向AF指示接受的确认信息，该指示接受的确认信息携带于任何消息中均是可行的。
705，UDR将数据导向请求信息通知给相应的PCF。
数据导向请求信息中可以包括：internal SC Id与DNAI的对应关系，适用的用户内部标识或任意用户的指示信息。
706，UE建立PDU会话。
例如，UE发起PDU会话的建立，网络为PDU选择PSA，网络给UE分配地址。
对于步骤706本申请实施例不作限定，例如，可以参考上述步骤501的描述。步骤706可以参考现有技术或以后出现的方式，此处不再介绍。
707，PCF制定PCC规则。
一可能的情况，如果数据导向请求信息中包括任意用户指示信息，或者UE属于内部组标识标识的用户组的成员，那么PCF制定对应的PCC规则。
PCF可以根据internal SC Id确定的TSP Id。PCC规则可以包括数据导向策略，并且在数据导向策略中可以包括internal SC Id对应的TSP Id与DNAI的对应关系。
可选地，如果PCF决策的上下行TSP不同，那么PCC规则中可以包括不同的上下行TSP Id。例如，PCF可以针对上行确定一个TSP Id(如PCF可以根据上行的internal SC Id确定一个上行的TSP Id，或者说确定上行的TSP Id与DNAI的对应关系)，针对下行确定一个TSP Id(如PCF可以根据下行的internal SC Id确定一个下行的TSP Id，或者说确定下行的TSP Id与DNAI的对应关系)，在步骤707中，PCF制定的PCC规则中可以包括上行的internal SC Id对应的TSP Id与DNAI的对应关系，以及下行的internal SC Id对应的TSP Id与DNAI的对应关系。
708，PCF向SMF发送PCC规则。
PCC规则中包括TSP Id与DNAI的对应关系列表。如PCC规则中包括上行的TSP Id与DNAI的对应关系列表，以及下行的TSP Id与DNAI的对应关系列表。
一种可能的实现方式，PCF可以向SMF发送Npcf_SMPolicyControl_UpdateNotify Request消息，该消息中包含PCC规则的信息。
709，SMF向PCF发送确认信息。
SMF安装PCC规则后，可以向PCF返回确认信息。
一种可能的实现方式，SMF可以向PCF发送Npcf_SMPolicyControl_UpdateNotify Response消息。
应理解，Npcf_SMPolicyControl_UpdateNotify Response消息，仅是示例性说明，对此不作限定。
710，SMF和UPF进行用户面配置(configuration)(或重配置(reconfiguration))。
SMF可以为PDU会话确定目标DNAI。示例地，SMF可以根据UE的位置、运营商策略以及DNAI列表，为PDU会话确定目标DNAI。
SMF可以根据目标NDAI确定新的PSA以及TSP Id。
此外，SMF还可以根据PCC规则制定N4规则。该N4规则中可以包括PDR和关联 的FAR。PDR中包括业务流描述信息，FAR中包括TSP Id。
711，UPF进行traffic steering。
一种可能的实现方式，UPF根据PDR匹配到业务数据流，UPF根据FAR在数据流的数据包进行标记后，发送给局域网(如N6-LAN)。局域网中的交换机将根据数据包的标记将数据依次发送给业务功能节点。
上文结合图7所示的步骤701-711示例地介绍了一种可能的业务链处理流程，如应用通过NEF向网络提供各个DNAI对应的业务链处理的场景。应理解，上述各个步骤仅是示例性说明，对此不作严格限定。此外，上述各过程的序号的大小并不意味着执行顺序的先后，各过程的执行顺序应以其功能和内在逻辑确定，而不应对本申请实施例的实施过程构成任何限定。
基于上述方案，AF在向网络提供数据导向请求信息时，可以提供DNAI和外部业务链标识对应关系的列表。NEF将该外部业务链标识映射为内部业务链标识后，将DNAI和该内部业务链标识对应关系的列表发送给PCF。PCF根据内部业务链标识，确定对应的TSP Id，从而在向SMF发送的PCC规则中携带DNAI与TSP Id的对应关系。SMF可以根据选择的目标DNAI确定对应的TSP Id，从而当UE通过目标DNAI访问应用时，业务数据流可以导向到对应的业务功能(service function)。
图8是适用于本申请一实施例的业务链处理的又一示意性流程图。
如图8所示，方法800主要以UE、AMF、UPF、SMF、PCF、NEF以及AF之间的交互为例进行示例性说明。作为示例而非限定，图8所示的方法800可以用于AF通过NEF向网络提供业务增值功能需求流程。在方法800中，第二网元例如可以为NEF，第一网元例如可以为PCF。图8所示的方法800可以包括如下步骤。
801，PDU会话的建立过程。
例如，UE发起PDU会话的建立，网络为PDU选择PSA，网络给UE分配地址。UE通过建立的PDU会话，可以访问DN网络中的应用服务器。
对于步骤801本申请实施例不作限定，例如，可以参考上述步骤501的描述。步骤801可以参考现有技术或以后出现的方式，此处不再介绍。
802，AF向NEF发送外部service function的列表。
外部service function的列表，包括一个或多个service function的信息。其中，service function可以用具体的标识或是类型来标识，对此不作限定。例如，service function可以用service function的Id来标识，即外部service function的列表中包括外部service function的Id。又如，service function可以用service function的类型来标识，即外部service function列表中包括外部service function的类型。
外部service function的信息可以通过列表的形式发送。例如，AF可以向NEF发送外部service function的列表，作为示例而非限定，这个列表例如可以按照service function被使用的顺序来携带。
AF决定为UE正在访问的应用请求资源以及应用增值服务的情况下，AF可以向NEF发送请求业务链授权的请求消息，并且在该请求消息中携带外部service function的信息。
可选地，如果AF对应用上下行数据有不同的上下行业务量需求，那么AF可以提供不同的上下行外部service function的列表。例如，AF可以针对上行提供一个上行的service  function的列表，针对下行提供一个下行的service function的列表，在步骤802中，AF向NEF发送的service function的列表可以包括上行的service function的列表和下行的service function的列表。
一种可能的实现方式，AF可以向NEF发送Nnef_AFsessionWithQoS_Create Request消息，该消息中包含外部service function的列表。可选地，该消息中还可以包括但不限于：业务流描述信息(如五元组信息)、请求的QoS需求。
应理解，Nnef_AFsessionWithQoS_Create Request消息，仅是示例性说明，对此不作限定。只要AF可以向NEF发外部service function的列表，该外部service function的列表携带于任何消息中均是可行的。
803，NEF进行处理。
NEF可以确定对AF的请求进行授权。NEF可以将外部service function映射为内部service function，即NEF可以获得内部service function的列表。
可选地，如果AF提供不同的上下行外部service function的列表，如包括一个上行的外部service function的列表和一个下行的外部service function的列表，那么，NEF可以将上行的外部service function的列表映射为上行的内部service function的列表，将下行的外部service function的列表映射为下行的内部service function的列表。
804，NEF向PCF发送内部service function的列表。
一种可能的实现方式，NEF可以向PCF发送Npcf_PolicyAuthorization_Create Request消息，该消息中包含内部service function的列表。可选地，该消息中还可以包括但不限于：业务流描述信息(如五元组信息)、QoS需求。
应理解，Npcf_PolicyAuthorization_Create Request消息，仅是示例性说明，对此不作限定。只要NEF可以向PCF发送内部service function的列表，该内部service function的列表携带于任何消息中均是可行的。
805，PCF向NEF发送确认信息。
当PCF对请求的业务链授权成功时(即PCF对请求的service function授权成功时)，PCF向NEF发送指示接受的确认信息。作为示例而非限定，PCF可以根据网络配置和运营商策略确定是否向NEF返回确认消息，即确定对请求的业务链是否授权。
可选地，该确认信息中还可以包括：PCF授权的内部service function的列表。NEF可以向PCF发送多个内部service function时，PCF可能对该多个内部service function中的部分内部service function授权，或者PCF可能对该多个内部service function中的全部内部service function授权，对此不作限定。
一种可能的实现方式，PCF可以向NEF发送Npcf_PolicyAuthorization_Create Response消息，该消息中包含指示接受内部service function的确认信息。
应理解，Npcf_PolicyAuthorization_Create Response消息，仅是示例性说明，对此不作限定。只要PCF可以向NEF指示接受内部service function的确认信息，该指示接受内部service function的确认信息携带于任何消息中均是可行的。
806，NEF向AF发送确认信息。
可选地，该确认信息中还可以包括：PCF授权的内部service function的列表。
一种可能的实现方式，NEF可以向AF发送Nnef_AFsessionWithQoS_Create Response 消息，该消息中包含指示接受内部service function的确认信息。
应理解，Nnef_AFsessionWithQoS_Create Response消息，仅是示例性说明，对此不作限定。只要NEF可以向AF指示接受内部service function的确认信息，该指示接受内部service function的确认信息携带于任何消息中均是可行的。
807，PCF制定PCC规则。
PCF可以根据授权的内部service function的列表，确定对应的业务链，从而进一步确定对应的TSP Id。PCF制定PCC规则，在PCC规则中包括TSP Id。
可选地，如果PCF决策的上下行TSP不同，那么PCC规则中可以包括不同的上下行TSP Id。
808，PCF向SMF发送PCC规则。
对于步骤808，例如可以参考上述步骤505的描述，此处不再介绍。
809，SMF向PCF发送确认信息。
对于步骤809，例如可以参考上述步骤506的描述，此处不再介绍。
810，SMF制定N4规则。
对于步骤810，例如可以参考上述步骤507的描述，此处不再介绍。
811，UPF进行业务路由。
对于步骤811，例如可以参考上述步骤508的描述，此处不再介绍。
上文结合图8所示的步骤801-811示例地介绍了一种可能的业务链处理流程，如应用通过NEF向网络提供业务增值功能需求的场景。应理解，上述各个步骤仅是示例性说明，对此不作严格限定。此外，上述各过程的序号的大小并不意味着执行顺序的先后，各过程的执行顺序应以其功能和内在逻辑确定，而不应对本申请实施例的实施过程构成任何限定。例如，上述步骤805和步骤807之间并没有严格的先后顺序，如可以先执行步骤805，再执行步骤807；或者也可以先执行步骤807，再执行步骤805；或者也可以同步进行，对此不作限定。
基于上述方案，网络可动态的根据应用的请求，进行业务链的决策。例如，AF通过NEF向网络请求应用所需要的业务链处理时，携带外部业务功能的列表。NEF将该外部业务功能映射为内部业务功能后，将该内部业务功能的列表发送给PCF。这样，PCF基于AF的请求(即内部业务功能的列表)，根据授权的内部业务功能的列表，确定对应的业务链，从而进一步确定对应的业务链策略。从而，能够快速响应应用对业务链的快速变化的需求。
图9是适用于本申请一实施例的业务链处理的又一示意性流程图。
如图9所示，方法900主要以UE、AMF、UPF、SMF、V-PCF、H-PCF、NEF以及AF之间的交互为例进行示例性说明。作为示例而非限定，图9所示的方法900可以用于UE处于本地疏导的漫游场景下，AF在为应用请求网络资源时，向网络请求应用所需要的业务链处理流程。在方法900中，第二网元例如可以为NEF，第一网元例如可以为V-PCF，第四网元例如可以为H-PCF。图9所示的方法900可以包括如下步骤。
901，PDU会话的建立过程。
例如，UE在本地疏导的漫游场景下，建立PDU会话，网络为PDU选择PSA，网络给UE分配地址。UE通过建立的PDU会话，可以访问DN网络中的应用服务器。
一种可能的实现方式，UE发送会话建立请求消息，会话建立请求消息中可以包括但不限于：单一网络切片选择辅助信息(single network slice selection assistance information，S-NSSAI)、数据网络名称(data network name，DNN)、订阅永久标识符(subscription permanent identifier，SUPI)。SMF与V-PCF交互，建立会话管理策略关联，从PCF获取PCC策略。
对于步骤901本申请实施例不作限定，步骤901可以参考现有技术或以后出现的方式，此处不再介绍。
902，AF向NEF发送外部业务链标识external SC Id的信息。
AF决定为UE正在访问的应用请求资源以及业务增值服务的情况下，AF可以向NEF发送请求业务链授权的请求消息，并且在该请求消息中携带external SC Id的信息。
external SC Id可以是AF提前获知的。例如，external SC Id可以是应用和运营商之前协商好的业务链标识，或者也可以是协议或网络预先定义好的业务链标识，对此不作限定。
可选地，如果AF对应用上下行数据有不同的上下行业务量需求，那么AF可以提供不同的上下行external SC Id。例如，AF可以针对上行提供一个上行的external SC Id，针对下行提供一个下行的external SC Id，在步骤902中，AF向NEF发送的external SC Id的信息可以包括上行的external SC Id和下行的external SC Id。
一种可能的实现方式，AF可以向NEF发送Nnef_AFsessionWithQoS_Create Request消息，该消息中包含external SC Id的信息。可选地，该消息中还可以包括但不限于：业务流描述信息(如五元组信息)、请求的QoS需求。
应理解，Nnef_AFsessionWithQoS_Create Request消息，仅是示例性说明，对此不作限定。只要AF可以向NEF发送external SC Id的信息，该external SC Id的信息携带于任何消息中均是可行的。
903，NEF进行处理。
NEF可以确定对AF的请求进行授权。NEF可以将external SC Id映射为internal SC Id。
可选地，如果AF提供不同的上下行external SC Id，如包括一个上行的external SC Id和一个下行的external SC Id，那么，NEF可以将上行的external SC Id映射为上行的internal SC Id，将下行的external SC Id映射为下行的internal SC Id。
904，NEF向V-PCF发送internal SC Id的信息。
一种可能的实现方式，NEF可以向V-PCF发送Npcf_PolicyAuthorization_Create Request消息，该消息中包含internal SC Id的信息。可选地，该消息中还可以包括但不限于：业务流描述信息(如五元组信息)、请求的QoS需求。
应理解，Npcf_PolicyAuthorization_Create Request消息，仅是示例性说明，对此不作限定。只要NEF可以向V-PCF发送internal SC Id的信息，该internal SC Id的信息携带于任何消息中均是可行的。
905，V-PCF制定PCC规则。
V-PCF可以根据AF的请求(即通过NEF转达的请求)，进行授权。V-PCF可以根据internal SC Id确定对应的TSP Id。V-PCF制定PCC规则，在PCC规则中包括TSP Id。
可选地，如果V-PCF决策的上下行TSP不同，那么PCC规则中可以包括不同的上下行TSP Id。例如，V-PCF可以针对上行确定一个TSP Id(如V-PCF可以根据上行的internal  SC Id确定一个上行的TSP Id)，针对下行确定一个TSP Id(如V-PCF可以根据下行的internal SC Id确定一个下行的TSP Id)，在步骤905中，V-PCF制定的PCC规则中可以包括上行的TSP Id和下行的TSP Id。
906，V-PCF向H-PCF发送PCC授权请求消息。
V-PCF确定UE为漫游用户，V-PCF可以向H-PCF发送PCC授权请求消息，该PCC授权请求消息中可以携带：UE的标识(如SUPI)、DNN、S-NSSAI。V-PCF可以根据SUPI确定UE的归属地运营商后，通过拜访地的网络存储功能(NF repository function，NRF)选择H-PCF，或者通过归属地的NRF选择H-PCF。
此外，该PCC授权请求消息中可以包括以下一项或多项：V-PCF确定的PCC规则、V-PCF确定的TSP Id、V-PCF确定的internal SC Id、V-PCF授权的service function列表。其中，PCC规则中包括V-PCF根据SC Id确定的TSP Id。如PCC规则中包括上行的TSP Id和下行的TSP Id。
其中，service function可以用具体的标识或是类型来标识，对此不作限定。例如，service function可以用service function的Id来标识，即service function列表中包括V-PCF授权的service function的Id。又如，service function可以用service function的类型来标识，即service function列表中包括V-PCF授权的service function的类型。
一种可能的实现方式，V-PCF可以向H-PCF发送Npcf接口PCC授权建立请求(Npcf_PccAuthorization_Create Request)消息。应理解，Npcf_PccAuthorization_Create Request消息，仅是示例性说明，对此不作限定。
907，H-PCF向V-PCF发送确认信息。
在步骤907中，H-PCF进行授权后，向V-PCF发送指示接受的确认信息。
一种可能的实现方式，H-PCF可以向V-PCF发送Npcf接口PCC授权建立响应(Npcf_PccAuthorization_Create Response)消息。应理解，Npcf_PccAuthorization_Create Response消息，仅是示例性说明，对此不作限定。
908，V-PCF向NEF发送确认信息。
一种可能的实现方式，V-PCF可以向NEF发送Npcf_PolicyAuthorization_Create Response消息。应理解，Npcf_PolicyAuthorization_Create Response消息，仅是示例性说明，对此不作限定。
909，NEF向AF发送确认信息。
一种可能的实现方式，NEF可以向AF发送Nnef_AFsessionWithQoS_Create Response消息。应理解，Nnef_AFsessionWithQoS_Create Response消息，仅是示例性说明，对此不作限定。
910，V-PCF向SMF发送PCC规则。
PCC规则中包括TSP Id。如PCC规则中包括上行的TSP Id和下行的TSP Id。
一种可能的实现方式，V-PCF可以向SMF发送Npcf_SMPolicyControl_UpdateNotify Request消息，该消息中包含PCC规则的信息。
应理解，Npcf_SMPolicyControl_UpdateNotify Request消息，仅是示例性说明，对此不作限定。只要V-PCF可以向SMF指示PCC规则的信息，该PCC规则的信息携带于任何消息中均是可行的。
911，SMF向V-PCF发送确认信息。
SMF安装PCC规则后，可以向V-PCF返回确认信息。
一种可能的实现方式，SMF可以向V-PCF发送Npcf_SMPolicyControl_UpdateNotify Response消息。应理解，Npcf_SMPolicyControl_UpdateNotify Response消息，仅是示例性说明，对此不作限定。
912，SMF制定N4规则。
对于步骤912，例如可以参考上述步骤507的描述，此处不再介绍。
913，UPF进行业务路由。
对于步骤913，例如可以参考上述步骤508的描述，此处不再介绍。
上文结合图9所示的步骤901-913示例地介绍了一种可能的业务链处理流程，如UE处于本地疏导的漫游场景下，应用在为应用请求网络资源时，向网络请求应用所需要的业务链处理的场景。应理解，上述各个步骤仅是示例性说明，对此不作严格限定。此外，上述各过程的序号的大小并不意味着执行顺序的先后，各过程的执行顺序应以其功能和内在逻辑确定，而不应对本申请实施例的实施过程构成任何限定。例如，上述步骤908和步骤910之间并没有严格的先后顺序，如可以先执行步骤908，再执行步骤910；或者也可以先执行步骤910，再执行步骤908；或者也可以同步进行，对此不作限定。
基于上述方案，在漫游场景下，V-PCF可以根据AF的请求制定业务链策略(即TSP策略)，并向H-PCF发送该业务链策略，以便进行H-PCF的进一步授权。
图10是适用于本申请一实施例的业务链处理的又一示意性流程图。
如图10所示，方法1000主要以UE、AMF、UPF、SMF、V-PCF、H-PCF、UDR、NEF以及AF之间的交互为例进行示例性说明。作为示例而非限定，图10所示的方法1000可以用于UE处于本地疏导的漫游场景下，AF在提供数据导向请求信息时，向网络请求应用所需要的业务链处理的场景。在方法1000中，第二网元例如可以为UDR或NEF或H-PCF，第一网元例如可以为V-PCF，第四网元例如可以为H-PCF。图10所示的方法1000可以包括如下步骤。
1001，AF向NEF发送外部业务链标识external SC Id与DNAI的对应关系的信息。
external SC Id与DNAI的对应关系的信息可以通过列表的形式发送。例如，AF可以向NEF发送external SC Id与DNAI的对应关系列表。
一种可能的实现方式，AF可以向NEF发送Nnef_TrafficInfluence_Create Request消息，该消息中包含数据导向请求信息，该数据导向请求信息中包括external SC Id与DNAI的对应关系列表。可选地，该数据导向请求信息中还可以包括但不限于：适用的用户外部组标识或任意用户的指示信息。
应理解，Nnef_TrafficInfluence_Create Request消息，仅是示例性说明，对此不作限定。只要AF可以向NEF发送external SC Id与DNAI的对应关系的信息，该external SC Id与DNAI的对应关系的信息携带于任何消息中均是可行的。
1002，NEF进行处理。
NEF可以确定对AF的请求进行授权。NEF可以将external SC Id映射为internal SC Id，即NEF可以获得internal SC Id与DNAI的对应关系。NEF还可以将外部组标识映射为内部组标识。
1003，NEF将internal SC Id与DNAI的对应关系保存到UDR。
一种可能的实现方式，UDR从NEF处接收internal SC Id与DNAI的对应关系，并且保存internal SC Id与DNAI的对应关系。
示例地，NEF可以将在步骤1001中接收到的数据导向请求信息保存到UDR中。可以理解，在步骤1002中，NEF可以将external SC Id映射为internal SC Id，还可以将外部组标识映射为内部组标识，因此，UDR中保存的数据导向请求信息中可以包括：internal SC Id与DNAI的对应关系，适用的用户内部标识或任意用户的指示信息。
1004，NEF向AF发送确认信息。
一种可能的实现方式，NEF可以向AF发送Nnef_TrafficInfluence_Create Response消息。应理解，Nnef_TrafficInfluence_Create Response消息，仅是示例性说明，对此不作限定。
1005，UDR将数据导向请求信息通知给相应的PCF。
例如，UDR将数据导向请求信息通知给V-PCF和H-PCF。数据导向请求信息中可以包括：internal SC Id与DNAI的对应关系，适用的用户内部标识或任意用户的指示信息。
1006，UE建立PDU会话。
对于步骤1006，例如可以参考上述步骤901的描述，此处不再介绍。
1007，V-PCF制定PCC规则。
一可能的情况，如果数据导向请求信息中包括任意用户指示信息，或者UE属于内部组标识标识的用户组的成员，那么V-PCF制定对应的PCC规则。
V-PCF可以根据internal SC Id与DNAI的对应关系，确定的internal SC Id对应的TSP Id与DNAI的对应关系。PCC规则可以包括数据导向策略，并且在数据导向策略中可以包括internal SC Id对应的TSP Id与DNAI的对应关系。
可选地，如果V-PCF决策的上下行TSP不同，那么PCC规则中可以包括不同的上下行TSP Id。例如，V-PCF可以针对上行确定一个TSP Id(如V-PCF可以根据上行的internal SC Id确定一个上行的TSP Id，或者说确定上行的TSP Id与DNAI的对应关系)，针对下行确定一个TSP Id(如V-PCF可以根据下行的internal SC Id确定一个下行的TSP Id，或者说确定下行的TSP Id与DNAI的对应关系)，在步骤1007中，PCF制定的PCC规则中可以包括上行的internal SC Id对应的TSP Id与DNAI的对应关系，以及下行的internal SC Id对应的TSP Id与DNAI的对应关系。
1008，V-PCF向SMF发送PCC规则。
PCC规则中包括TSP Id与DNAI的对应关系列表。如PCC规则中包括上行的TSP Id与DNAI的对应关系列表，以及下行的TSP Id与DNAI的对应关系列表。
一种可能的实现方式，V-PCF可以向SMF发送Npcf_SMPolicyControl_UpdateNotify Request消息，该消息中包含PCC规则的信息。
1009，SMF向V-PCF发送确认信息。
SMF安装PCC规则后，可以向V-PCF返回确认信息。
一种可能的实现方式，SMF可以向V-PCF发送Npcf_SMPolicyControl_UpdateNotify Response消息。
应理解，Npcf_SMPolicyControl_UpdateNotify Response消息，仅是示例性说明，对此 不作限定。
1010，SMF和UPF进行用户面配置(或重配置)。
SMF可以为PDU会话确定目标DNAI。示例地，SMF可以根据UE的位置、运营商策略、网络配置以及DNAI列表，为PDU会话确定目标DNAI。
SMF可以根据目标NDAI确定新的PSA以及TSP Id。
此外，SMF还可以根据PCC规则制定N4规则。该N4规则中可以包括PDR和关联的FAR。PDR中包括业务流描述信息，FAR中包括TSP Id。
1011，SMF向V-PCF发送目标DNAI的信息和/或TSP Id，用于请求业务链策略授权。
一种可能的实现方式，SMF可以向V-PCF发送Npcf_SMPolicyControl_Update Request消息，该消息中携带确定的目标DNAI和/或TSP Id。
应理解，Npcf_SMPolicyControl_Update Request消息，仅是示例性说明，对此不作限定。
1012，V-PCF向H-PCF发送PCC授权请求消息。
V-PCF确定UE为漫游用户，V-PCF可以向H-PCF发送PCC授权请求消息，该PCC授权请求消息中可以携带：UE的SUPI、DNN、S-NSSAI。V-PCF可以根据SUPI确定UE的归属地运营商后，通过拜访地的NRF选择H-PCF，或者通过归属地的NRF选择H-PCF。
此外，该PCC授权请求消息中可以包括以下一项或多项：目标DNAI对应的V-PCF确定的PCC规则(PCC规则中包括TSP Id)、目标DNAI对应的V-PCF确定的TSP Id、目标DNAI对应的V-PCF确定的internal SC Id、目标DNAI对应的V-PCF授权的service function列表、TSP Id对应的V-PCF授权的service function列表。其中，service function可以用具体的标识或是类型来标识，对此不作限定。
一种可能的实现方式，V-PCF可以向H-PCF发送Npcf_PccAuthorization_Create Request消息。应理解，Npcf_PccAuthorization_Create Request消息，仅是示例性说明，对此不作限定。
1013，H-PCF向V-PCF发送确认信息。
在步骤1013中，H-PCF进行授权后，向V-PCF发送指示接受的确认信息。
一种可能的实现方式，H-PCF可以向V-PCF发送Npcf_PccAuthorization_Create Response消息。应理解，Npcf_PccAuthorization_Create Response消息，仅是示例性说明，对此不作限定。
1014，V-PCF向SMF发送确认信息。
V-PCF向SMF发送确认信息，以指示业务链策略授权。
一种可能的实现方式，V-PCF可以向SMF发送Npcf_SMPolicyControl_Update Response消息。应理解，Npcf_SMPolicyControl_Update Response消息，仅是示例性说明，对此不作限定。
1015，UPF进行traffic steering。
对于步骤1015，例如可以参考上述步骤508的描述，此处不再介绍。
上文结合图10所示的步骤1001-1015示例地介绍了一种可能的业务链处理流程，如UE处于本地疏导的漫游场景下，应用在提供数据导向请求信息时，向网络请求应用所需要的业务链处理的场景。应理解，上述各个步骤仅是示例性说明，对此不作严格限定。此 外，上述各过程的序号的大小并不意味着执行顺序的先后，各过程的执行顺序应以其功能和内在逻辑确定，而不应对本申请实施例的实施过程构成任何限定。例如，上述步骤1003和步骤1004之间并没有严格的先后顺序，如可以先执行步骤1003，再执行步骤1004；或者也可以先执行步骤1004，再执行步骤1003；或者也可以同步进行，对此不作限定。
基于上述方案，在漫游场景下，V-PCF可以根据AF的请求制定业务链策略(即TSP策略)，并向H-PCF发送该业务链策略，以便进行H-PCF的进一步授权。例如，AF在向网络提供数据导向请求信息时，提供DNAI和外部业务链标识对应关系的列表。NEF将该外部业务链标识映射为内部业务链标识后，将DNAI和该内部业务链标识对应关系的列表发送给V-PCF。V-PCF根据该内部业务链标识，确定对应的TSP Id，从而在PCC规则中携带DNAI与TSP Id的对应关系。当SMF确定目标DNAI后，报告给V-PCF，V-PCF进一步发送对应的业务链策略(即TSP策略)请求H-PCF进一步授权。
上面结合图5至图10详细地介绍了适用于方法300和方法400的可能的流程。作为示例，图5至图10可用于执行方法300的方案，图9至图10还可用于执行方法400的方案。
在本申请实施例中，考虑到在发送请求时，携带应用所需的业务链的信息，故本申请实施例提供一种关于业务链管理的方法。下面结合图11介绍关于业务链管理的可能的流程。
图11是适用于本申请实施例的业务链管理的示意性流程图。
如图11所示，方法1100主要以业务链管理设备(service chain manager)、NEF以及AF之间的交互为例进行示例性说明。作为示例而非限定，图11所示的方法1100可以用于当运营商或是第三方应用部署了service function后，将service function注册到NEF，当第三方需要请求业务链处理时，第三方请求查询获取业务链的流程。在方法1100中，第二网元例如可以为AF。图11所示的方法1100可以包括如下步骤。
1101，创建、修改或删除service function。
业务链管理设备，如运营商或是第三方应用，部署了service function后，可以感知对于service function的操作。关于service function的操作，例如可以包括但不限于：创建、修改或删除。
1102，业务链管理设备和NEF之间交互业务链登记(service chain registration)的信息。
一种可能的实现方式，业务链管理设备向NEF发送service chain registration的信息，该service chain registration的信息中可以携带以下一项或多项信息：service function类型和service function标识的对应关系、service function类型和external SC Id的对应关系、service function类型、service function标识和DNAI的对应关系、service function标识、external SC Id标识和DNAI的对应关系的对应关系。其中，service function例如可以包括如创建、修改或删除的service function。
1103，AF触发。
也就是说，在步骤1103中，AF接收到触发，决定需要请求业务链处理。如AF决定为UE正在访问的应用请求资源以及业务增值服务。
1104，AF向NEF发送业务链发现(service chain discovery)请求消息。
可选地，该请求消息可以携带：需要的service function的类型以及DNAI信息。
NEF可以根据DNAI信息，返回DNAI对应支持的service function或者SC Id以及包括的service function类型。
NEF可以根据service function的类型，返回对应的service function Id或是SC Id以及包括的service function类型。
此后，作为示例，AF可以发起如前面方法500至方法1000实施例的请求消息。
上文结合图11所示的步骤1101-1104示例地介绍了一种可能的业务链处理流程，如当运营商或是第三方应用部署了service function后，将service function注册到NEF，当第三方需要请求业务链处理时，第三方请求查询获取业务链的场景。应理解，上述各个步骤仅是示例性说明，对此不作严格限定。此外，上述各过程的序号的大小并不意味着执行顺序的先后，各过程的执行顺序应以其功能和内在逻辑确定，而不应对本申请实施例的实施过程构成任何限定。
基于上述方案，第三方应用可以动态请求业务链。例如，网络将支持的业务功能或业务链注册到NEF，第三方应用可通过查询获得相应的业务功能或业务链。
应理解，在上述一些实施例中，涉及到一些消息名称，如接口请求消息或接口响应消息，等等，应理解，其命名不对本申请实施例的保护范围造成限定。
还应理解，在上述一些实施例中，多次提到业务链的信息，如需要的业务链的信息或者查询的业务链的信息，其用于表示与业务链相关的信息，例如可以包括SC Id、external SC Id、service function的信息、外部service function的信息，DNAI等等。
还应理解，在上述一些实施例中，主要以现有的网络架构中的网元为例进行了示例性说明(如AF、PCF、SMF等等)，应理解，对于网元的具体形式本申请实施例不作限定。例如，在未来可以实现同样功能的网元都适用于本申请实施例。此外，在未来可以部署业务链的任何架构都适用于本申请实施例。
还应理解，在上述一些实施例中，主要以请求应用对应的业务链策略为例进行示例性说明，应理解，对此不作限定。例如，在任何提供业务链的场景中，都可以使用本申请实施例的方案制定业务链策略。
本文中描述的各个实施例可以为独立的方案，也可以根据内在逻辑进行组合，这些方案都落入本申请的保护范围中。例如，方法400和方法300可以结合使用，也可以独立使用。又如，方法1100可以单独使用，也可以作为方法500-方法1000的准备工作结合使用，等等。
可以理解的是，上述各个方法实施例中，由网络设备(如各个网元)实现的方法和操作，也可以由可用于网络设备的部件(例如芯片或者电路)实现。
以上，结合图3至图11详细说明了本申请实施例提供的方法。以下，结合图12至图14详细说明本申请实施例提供的装置。应理解，装置实施例的描述与方法实施例的描述相互对应，因此，未详细描述的内容可以参见上文方法实施例，为了简洁，这里不再赘述。
图12是本申请实施例提供的装置1200的示意性框图。该装置1200包括收发单元1210和处理单元1220。收发单元1210可以实现相应的通信功能，处理单元1220用于进行数据处理。收发单元1210还可以称为通信接口或通信单元。
可选地，该装置1200还可以包括存储单元，该存储单元可以用于存储指令和/或数据， 处理单元1220可以读取存储单元中的指令和/或数据，以使得装置实现前述方法实施例。
该装置1200可以用于执行上文方法实施例中网络设备(如各个网元)所执行的动作，这时，该装置1200可以为网络设备或者可配置于网络设备的部件，收发单元1210用于执行上文方法实施例中网络设备侧的收发相关的操作，处理单元1220用于执行上文方法实施例中网络设备侧的处理相关的操作。
作为一种设计，该装置1200用于执行上文方法实施例中第一网元所执行的动作。
一种可能的实现方式，收发单元1210，用于接收来自第二网元的第一请求消息，第一请求消息包括应用所需的业务链的信息；收发单元1210，还用于向第三网元发送应用对应的业务链策略，应用对应的业务链策略是根据应用所需的业务链的信息制定的。
可选地，处理单元1220，用于根据应用所需的业务链的信息，确定应用对应的业务链策略。
该装置1200可实现对应于根据本申请实施例的方法实施例中的第一网元执行的步骤或者流程，该装置1200可以包括用于执行方法实施例中的第一网元执行的方法的单元。并且，该装置1200中的各单元和上述其他操作和/或功能分别为了实现方法实施例中的第一网元中的方法实施例的相应流程。
其中，当该装置1200用于执行图3中的方法300时，收发单元1210可用于执行方法300中的步骤310、330；处理单元1220可用于执行方法300中的处理步骤，如步骤320。
当该装置1200用于执行图4中的方法400时，收发单元1210可用于执行方法400中的步骤410、420；处理单元1220可用于执行方法400中的处理步骤，如步骤401。
当该装置1200用于执行图5中的方法500时，收发单元1210可用于执行方法500中的步骤502、503、505、506；处理单元1220可用于执行方法500中的处理步骤，如步骤504。
当该装置1200用于执行图6中的方法600时，收发单元1210可用于执行方法600中的步骤604、605、608、609；处理单元1220可用于执行方法600中的处理步骤，如步骤607。
当该装置1200用于执行图7中的方法700时，收发单元1210可用于执行方法700中的步骤705、708、709；处理单元1220可用于执行方法700中的处理步骤，如步骤707。
当该装置1200用于执行图8中的方法800时，收发单元1210可用于执行方法800中的步骤804、805、808、809；处理单元1220可用于执行方法800中的处理步骤，如步骤807。
当该装置1200用于执行图9中的方法900时，收发单元1210可用于执行方法900中的步骤904、906-908、910、911；处理单元1220可用于执行方法900中的处理步骤，如步骤905。
当该装置1200用于执行图10中的方法1000时，收发单元1210可用于执行方法1000中的步骤1005、1008、1009、1011-1014；处理单元1220可用于执行方法1000中的处理步骤，如步骤1007
应理解，各单元执行上述相应步骤的具体过程在上述方法实施例中已经详细说明，为了简洁，在此不再赘述。
作为另一种设计，该装置1200用于执行上文方法实施例中第二网元所执行的动作。
一种可能的实现方式，收发单元1210，用于向第一网元发送第一请求消息，第一请求消息包括应用所需的业务链的信息；收发单元1210，还用于接收来自第一网元的指示信息，指示信息用于指示接受应用所需的业务链的请求。
该装置1200可实现对应于根据本申请实施例的方法实施例中的第二网元执行的步骤或者流程，该装置1200可以包括用于执行方法实施例中的第二网元执行的方法的单元。并且，该装置1200中的各单元和上述其他操作和/或功能分别为了实现方法实施例中的第二网元中的方法实施例的相应流程。
其中，当该装置1200用于执行图3中的方法300时，收发单元1210可用于执行方法300中的步骤310、320；处理单元1220可用于执行方法300中的处理步骤，如步骤301。
当该装置1200用于执行图5中的方法500时，收发单元1210可用于执行方法500中的步骤502、503；处理单元1220可用于执行方法500中的处理步骤，如步骤501。
当该装置1200用于执行图6中的方法600时，收发单元1210可用于执行方法600中的步骤602、604、605、606；处理单元1220可用于执行方法600中的处理步骤，如步骤603。
当该装置1200用于执行图7中的方法700时，收发单元1210可用于执行方法700中的步骤701、704、或705；处理单元1220可用于执行方法700中的处理步骤，如步骤702。
当该装置1200用于执行图8中的方法800时，收发单元1210可用于执行方法800中的步骤802、804、805、806；处理单元1220可用于执行方法800中的处理步骤，如步骤803。
当该装置1200用于执行图9中的方法900时，收发单元1210可用于执行方法900中的步骤902、904、909、或者904、906-908；处理单元1220可用于执行方法900中的处理步骤，如步骤903或905。
当该装置1200用于执行图10中的方法1000时，收发单元1210可用于执行方法1000中的步骤1001、1004、1005、1008、1009、1011-1014；处理单元1220可用于执行方法1000中的处理步骤，如步骤1002、1003、或1007。
当该装置1200用于执行图11中的方法1100时，收发单元1210可用于执行方法1100中的步骤1104；处理单元1220可用于执行方法1100中的处理步骤。
应理解，各单元执行上述相应步骤的具体过程在上述方法实施例中已经详细说明，为了简洁，在此不再赘述。
作为另一种设计，该装置1200用于执行上文方法实施例中第四网元所执行的动作。
一种可能的实现方式，收发单元1210，用于接收来自第一网元的请求消息，请求消息用于请求对一个或多个业务功能进行授权，或者，请求消息用于请求对应用对应的业务链策略进行授权；收发单元1210，还用于向第一网元发送该请求消息的响应消息。
一示例，收发单元1210，具体用于接收来自第一网元的请求消息，请求消息包括应用对应的业务链策略和访问该应用的用户的标识，该请求消息用于请求对用户访问的应用对应的业务链策略进行授权。
又一示例，收发单元1210，具体用于接收来自第一网元的请求消息，请求消息包括一个或多个业务功能的信息和访问应用的用户的标识，该请求消息用于请求对用户访问的应用对应的一个或多个业务功能的信息进行授权。
该装置1200可实现对应于根据本申请实施例的方法实施例中的第四网元执行的步骤或者流程，该装置1200可以包括用于执行方法实施例中的第四网元执行的方法的单元。并且，该装置1200中的各单元和上述其他操作和/或功能分别为了实现方法实施例中的第四网元中的方法实施例的相应流程。
其中，当该装置1200用于执行图4中的方法400时，收发单元1210可用于执行方法400中的步骤410、420；处理单元1220可用于执行方法400中的处理步骤。
当该装置1200用于执行图9中的方法900时，收发单元1210可用于执行方法900中的步骤906、907；处理单元1220可用于执行方法900中的处理步骤。
当该装置1200用于执行图10中的方法1000时，收发单元1210可用于执行方法1000中的步骤1005、1012、1013；处理单元1220可用于执行方法1000中的处理步骤。
应理解，各单元执行上述相应步骤的具体过程在上述方法实施例中已经详细说明，为了简洁，在此不再赘述。
作为另一种设计，该装置1200用于执行上文方法实施例中第五网元所执行的动作。
一种可能的实现方式，收发单元1210，用于接收来自第二网元的请求消息，请求消息包括应用所需的业务链的信息；处理单元1220，用于对应用所需的业务链的信息进行处理；收发单元1210，还用于向第一网元发送处理后的业务链的信息。
该装置1200可实现对应于根据本申请实施例的方法实施例中的第五网元执行的步骤或者流程，该装置1200可以包括用于执行方法实施例中的第五网元执行的方法的单元。并且，该装置1200中的各单元和上述其他操作和/或功能分别为了实现方法实施例中的第五网元中的方法实施例的相应流程。
其中，当该装置1200用于执行图6中的方法600时，收发单元1210可用于执行方法600中的步骤602、604、605、605；处理单元1220可用于执行方法600中的处理步骤，如步骤603。
当该装置1200用于执行图7中的方法700时，收发单元1210可用于执行方法700中的步骤701、704；处理单元1220可用于执行方法700中的处理步骤，如步骤702。
当该装置1200用于执行图8中的方法800时，收发单元1210可用于执行方法800中的步骤802、804-806；处理单元1220可用于执行方法800中的处理步骤，如步骤803。
当该装置1200用于执行图9中的方法900时，收发单元1210可用于执行方法900中的步骤902、904、908、909；处理单元1220可用于执行方法900中的处理步骤，如步骤903。
当该装置1200用于执行图10中的方法1000时，收发单元1210可用于执行方法1000中的步骤1001、1004；处理单元1220可用于执行方法1000中的处理步骤，如步骤1002、1003。
应理解，各单元执行上述相应步骤的具体过程在上述方法实施例中已经详细说明，为了简洁，在此不再赘述。
上文实施例中的处理单元1220可以由至少一个处理器或处理器相关电路实现。收发单元1210可以由收发器或收发器相关电路实现。存储单元可以通过至少一个存储器实现。
如图13所示，本申请实施例还提供一种装置1300。该装置1300包括处理器1310，处理器1310与存储器1320耦合，存储器1320用于存储计算机程序或指令和/或数据，处 理器1310用于执行存储器1320存储的计算机程序或指令和/或数据，使得上文方法实施例中的方法被执行。
可选地，该装置1300包括的处理器1310为一个或多个。
可选地，如图13所示，该装置1300还可以包括存储器1320。
可选地，该装置1300包括的存储器1320可以为一个或多个。
可选地，该存储器1320可以与该处理器1310集成在一起，或者分离设置。
可选地，如图13所示，该装置1300还可以包括收发器1330，收发器1330用于信号的接收和/或发送。例如，处理器1310用于控制收发器1330进行信号的接收和/或发送。
作为一种方案，该装置1300用于实现上文方法实施例中由网络设备(如上述各个网元)执行的操作。
本申请实施例还提供一种装置1400，该装置1400可以是网络设备也可以是芯片。该装置1400可以用于执行上述方法实施例中由网络设备(如上述各个网元)所执行的操作。
图14示出了一种简化的结构示意图。装置1400包括1410部分以及1420部分。1410部分主要用于射频信号的收发以及射频信号与基带信号的转换；1420部分主要用于基带处理，对基站进行控制等。1410部分通常可以称为收发单元、收发机、收发电路、或者收发器等。1420部分通常是基站的控制中心，通常可以称为处理单元，用于控制基站执行上述方法实施例中接收端设备侧的处理操作。
1410部分的收发单元，也可以称为收发机或收发器等，其包括天线和射频电路，其中射频电路主要用于进行射频处理。可选地，可以将1410部分中用于实现接收功能的器件视为接收单元，将用于实现发送功能的器件视为发送单元，即1410部分包括接收单元和发送单元。接收单元也可以称为接收机、接收器、或接收电路等，发送单元可以称为发射机、发射器或者发射电路等。
1420部分可以包括一个或多个单板，每个单板可以包括一个或多个处理器和一个或多个存储器。处理器用于读取和执行存储器中的程序以实现基带处理功能以及对基站的控制。若存在多个单板，各个单板之间可以互联以增强处理能力。作为一种可选的实施方式，也可以是多个单板共用一个或多个处理器，或者是多个单板共用一个或多个存储器，或者是多个单板同时共用一个或多个处理器。
应理解，图14仅为示例而非限定，上述包括收发单元和处理单元的网络设备可以不依赖于图14所示的结构。
当该装置1400为芯片时，该芯片包括收发单元和处理单元。其中，收发单元可以是输入输出电路、通信接口；处理单元为该芯片上集成的处理器或者微处理器或者集成电路。当然装置1400还可以为一个芯片***或处理***，使得安装该装置1400的设备可以实现本申请实施例的方法和功能。例如，处理单元1420可以为芯片***或处理***中的处理电路，实现对安装了该芯片***或处理***的设备的控制，还可以耦合链接存储单元，调用存储单元中的指令，使得设备可以实现本申请实施例的方法和功能，收发单元1410，可以为芯片***或处理***中的输入输出电路，将芯片***处理好的信息输出，或将待处理的数据或信令信息输入芯片***进行处理。
本申请实施例还提供一种计算机可读存储介质，其上存储有用于实现上述方法实施例中由网络设备(如各个网元)执行的方法的计算机指令。
例如，该计算机程序被计算机执行时，使得该计算机可以实现上述方法实施例中由网络设备执行的方法。
本申请实施例还提供一种包含指令的计算机程序产品，该指令被计算机执行时使得该计算机实现上述方法实施例中由网络设备(如各个网元)执行的方法。
本申请实施例还提供一种通信***，该通信***包括上文实施例中的网络设备(如各个网元)，如AF和PCF，或者，NEF和PCF，或者，AF、NEF以及PCF，等等。
上述提供的任一种装置中相关内容的解释及有益效果均可参考上文提供的对应的方法实施例，此处不再赘述。
应理解，本申请实施例中提及的处理器可以是中央处理单元(central processing unit，CPU)，还可以是其他通用处理器、数字信号处理器(digital signal processor，DSP)、专用集成电路(application specific integrated circuit，ASIC)、现成可编程门阵列(field programmable gate array，FPGA)或者其他可编程逻辑器件、分立门或者晶体管逻辑器件、分立硬件组件等。通用处理器可以是微处理器或者该处理器也可以是任何常规的处理器等。
还应理解，本申请实施例中提及的存储器可以是易失性存储器和/或非易失性存储器。其中，非易失性存储器可以是只读存储器(read-only memory，ROM)、可编程只读存储器(programmable ROM，PROM)、可擦除可编程只读存储器(erasable PROM，EPROM)、电可擦除可编程只读存储器(electrically EPROM，EEPROM)或闪存。易失性存储器可以是随机存取存储器(random access memory，RAM)。例如，RAM可以用作外部高速缓存。作为示例而非限定，RAM可以包括如下多种形式：静态随机存取存储器(static RAM，SRAM)、动态随机存取存储器(dynamic RAM，DRAM)、同步动态随机存取存储器(synchronous DRAM，SDRAM)、双倍数据速率同步动态随机存取存储器(double data rate SDRAM，DDR SDRAM)、增强型同步动态随机存取存储器(enhanced SDRAM，ESDRAM)、同步连接动态随机存取存储器(synchlink DRAM，SLDRAM)和直接内存总线随机存取存储器(direct rambus RAM，DR RAM)。
需要说明的是，当处理器为通用处理器、DSP、ASIC、FPGA或者其他可编程逻辑器件、分立门或者晶体管逻辑器件、分立硬件组件时，存储器(存储模块)可以集成在处理器中。
还需要说明的是，本文描述的存储器旨在包括但不限于这些和任意其它适合类型的存储器。
本领域普通技术人员可以意识到，结合本文中所公开的实施例描述的各示例的单元及步骤，能够以电子硬件、或者计算机软件和电子硬件的结合来实现。这些功能究竟以硬件还是软件方式执行，取决于技术方案的特定应用和设计约束条件。专业技术人员可以对每个特定的应用使用不同方法来实现所描述的功能，但是这种实现不应认为超出本申请的保护范围。
在本申请所提供的几个实施例中，应该理解到，所揭露的装置和方法，可以通过其它的方式实现。例如，以上所描述的装置实施例仅是示意性的，例如，所述单元的划分，仅仅为一种逻辑功能划分，实际实现时可以有另外的划分方式，例如多个单元或组件可以结合或者可以集成到另一个***，或一些特征可以忽略，或不执行。此外，所显示或讨论的 相互之间的耦合或直接耦合或通信连接可以是通过一些接口，装置或单元的间接耦合或通信连接，可以是电性，机械或其它的形式。
所述作为分离部件说明的单元可以是或者也可以不是物理上分开的，作为单元显示的部件可以是或者也可以不是物理单元，即可以位于一个地方，或者也可以分布到多个网络单元上。可以根据实际的需要选择其中的部分或者全部单元实现本申请提供的方案。
另外，在本申请各个实施例中的各功能单元可以集成在一个单元中，也可以是各个单元单独物理存在，也可以两个或两个以上单元集成在一个单元中。
在上述实施例中，可以全部或部分地通过软件、硬件、固件或者其任意组合来实现。当使用软件实现时，可以全部或部分地以计算机程序产品的形式实现。所述计算机程序产品包括一个或多个计算机指令。在计算机上加载和执行所述计算机程序指令时，全部或部分地产生按照本申请实施例所述的流程或功能。所述计算机可以是通用计算机、专用计算机、计算机网络、或者其他可编程装置。例如，所述计算机可以是个人计算机，服务器，或者网络设备等。所述计算机指令可以存储在计算机可读存储介质中，或者从一个计算机可读存储介质向另一个计算机可读存储介质传输，例如，所述计算机指令可以从一个网站站点、计算机、服务器或数据中心通过有线(例如同轴电缆、光纤、数字用户线(DSL))或无线(例如红外、无线、微波等)方式向另一个网站站点、计算机、服务器或数据中心进行传输。所述计算机可读存储介质可以是计算机能够存取的任何可用介质或者是包含一个或多个可用介质集成的服务器、数据中心等数据存储设备。所述可用介质可以是磁性介质(例如，软盘、硬盘、磁带)、光介质(例如，DVD)、或者半导体介质(例如固态硬盘(solid state disk，SSD)等。例如，前述的可用介质可以包括但不限于：U盘、移动硬盘、只读存储器(read-only memory，ROM)、随机存取存储器(random access memory，RAM)、磁碟或者光盘等各种可以存储程序代码的介质。
以上所述，仅为本申请的具体实施方式，但本申请的保护范围并不局限于此，任何熟悉本技术领域的技术人员在本申请揭露的技术范围内，可轻易想到变化或替换，都应涵盖在本申请的保护范围之内。因此，本申请的保护范围应以所述权利要求的保护范围为准。

Claims (50)

  1. 一种确定策略的方法，其特征在于，包括：
    第一网元接收来自第二网元的第一请求消息，所述第一请求消息包括应用所需的业务链的信息；
    所述第一网元向第三网元发送应用对应的业务链策略，所述应用对应的业务链策略是根据所述应用所需的业务链的信息制定的。
  2. 根据权利要求1所述的方法，其特征在于，所述应用所需的业务链的信息为所述应用所需的业务链标识。
  3. 根据权利要求1所述的方法，其特征在于，所述应用所需的业务链的信息为所述应用所需的一个或多个业务功能的信息。
  4. 根据权利要求3所述的方法，其特征在于，所述方法还包括：
    所述第一网元根据所述应用所需的一个或多个业务功能的信息，确定支持所述应用的一个或多个业务功能的信息，并向所述第二网元发送所述支持所述应用的一个或多个业务功能的信息。
  5. 根据权利要求3或4所述的方法，其特征在于，
    所述一个或多个业务功能的信息，为所述一个或多个业务功能的标识或类型。
  6. 根据权利要求1所述的方法，其特征在于，所述第一网元接收来自第二网元的第一请求消息，所述第一请求消息包括应用所需的业务链的信息，包括：
    所述第一网元接收来自所述第二网元的所述第一请求消息，所述第一请求消息包括所述应用所需的业务链的信息与所述数据网络接入标识之间的对应关系。
  7. 根据权利要求6所述的方法，其特征在于，所述第一网元向第三网元发送应用对应的业务链策略，包括：
    所述第一网元向所述第三网元发送所述应用对应的业务链策略与所述数据网络接入标识之间的对应关系。
  8. 根据权利要求1所述的方法，其特征在于，
    第一网元向第四网元发送第二请求消息，所述第二请求消息包括所述应用对应的业务链策略和访问所述应用的用户的标识，所述第二请求消息用于请求对所述用户访问所述应用对应的业务链策略进行授权。
  9. 根据权利要求3所述的方法，其特征在于，
    所述第一网元向第四网元发送第三请求消息，所述第三请求消息包括所述支持的一个或多个业务功能的信息和访问所述应用的用户的标识，所述第三请求消息用于请求对支持所述用户访问的所述应用的一个或多个业务功能进行授权。
  10. 一种确定策略的方法，其特征在于，包括：
    第二网元向第一网元发送第一请求消息，所述第一请求消息包括应用所需的业务链的信息；
    所述第二网元接收来自所述第一网元的指示信息，所述指示信息用于指示接受所述应用所需的业务链的请求。
  11. 根据权利要求10所述的方法，其特征在于，所述应用所需的业务链的信息为以下任一项：
    所述应用所需的业务链标识、所述应用所需的外部业务链标识、所述应用所需的一个或多个业务功能的信息、所述应用所需的一个或多个外部业务功能的信息、所述应用所需的业务链的信息与数据网络接入标识之间的对应关系。
  12. 根据权利要求10或11所述的方法，其特征在于，所述方法还包括：
    所述第二网元接收来自所述第一网元的支持所述应用的一个或多个业务功能的信息；或者，所述第二网元接收来自所述第一网元的支持所述应用的一个或多个外部业务功能的信息。
  13. 根据权利要求11或12所述的方法，其特征在于，所述一个或多个业务功能的信息，为所述一个或多个业务功能的标识或类型。
  14. 根据权利要求10至13中任一项所述的方法，其特征在于，在向所述第一网元发送第一请求消息之前，所述方法还包括：
    所述第二网元向第五网元发送第二请求消息，所述第二请求消息包括查询的业务链的信息；
    所述第二网元接收来自所述第五网元的支持所述查询的业务链的以下一项或多项信息：业务功能标识、业务链标识、业务功能标识和数据网络接入标识对应关系、业务链标识和数据网络接入标识对应关系。
  15. 一种通信装置，其特征在于，包括收发单元和处理单元，
    所述收发单元，用于接收来自第二网元的第一请求消息，所述第一请求消息包括应用所需的业务链的信息；
    所述处理单元，用于确定应用对应的业务链策略；
    所述收发单元，还用于向第三网元发送所述应用对应的业务链策略，所述应用对应的业务链策略是根据所述应用所需的业务链的信息制定的。
  16. 根据权利要求15所述的通信装置，其特征在于，所述应用所需的业务链的信息为所述应用所需的业务链标识。
  17. 根据权利要求15所述的通信装置，其特征在于，所述应用所需的业务链的信息为所述应用所需的一个或多个业务功能的信息。
  18. 根据权利要求17所述的通信装置，其特征在于，
    所述处理单元，还用于根据所述应用所需的一个或多个业务功能的信息，确定支持所述应用的一个或多个业务功能的信息；
    所述收发单元，还用于向所述第二网元发送所述支持所述应用的一个或多个业务功能的信息。
  19. 根据权利要求17或18所述的通信装置，其特征在于，
    所述一个或多个业务功能的信息，为所述一个或多个业务功能的标识或类型。
  20. 根据权利要求15所述的通信装置，其特征在于，所述收发单元，用于接收来自所述第二网元的所述第一请求消息，所述第一请求消息包括所述应用所需的业务链的信息与所述数据网络接入标识之间的对应关系。
  21. 根据权利要求20所述的通信装置，其特征在于，所述收发单元，用于向所述第三 网元发送所述应用对应的业务链策略与所述数据网络接入标识之间的对应关系。
  22. 根据权利要求15所述的通信装置，其特征在于，
    所述收发单元，还用于向第四网元发送第二请求消息，所述第二请求消息包括所述应用对应的业务链策略和访问所述应用的用户的标识，所述第二请求消息用于请求对所述用户访问所述应用对应的业务链策略进行授权。
  23. 根据权利要求17所述的通信装置，其特征在于，
    所述收发单元，还用于向第四网元发送第三请求消息，所述第三请求消息包括所述支持的一个或多个业务功能的信息和访问所述应用的用户的标识，所述第三请求消息用于请求对支持所述用户访问的所述应用的一个或多个业务功能进行授权。
  24. 根据权利要求15至23中任一项所述的通信装置，其特征在于，所述处理单元为处理器，和/或，所述收发单元为收发器。
  25. 根据权利要求15至24中任一项所述的通信装置，其特征在于，所述通信装置为以下任一项：网络设备、芯片或芯片***。
  26. 一种通信装置，其特征在于，包括收发单元和处理单元，
    所述处理单元，用于确定应用所需的业务链的信息；
    所述收发单元，用于向第一网元发送第一请求消息，所述第一请求消息包括所述应用所需的业务链的信息；
    所述收发单元，还用于接收来自所述第一网元的指示信息，所述指示信息用于指示接受所述应用所需的业务链的请求。
  27. 根据权利要求26所述的通信装置，其特征在于，所述应用所需的业务链的信息为以下任一项：
    所述应用所需的业务链标识、所述应用所需的外部业务链标识、所述应用所需的一个或多个业务功能的信息、所述应用所需的一个或多个外部业务功能的信息、所述应用所需的业务链的信息与数据网络接入标识之间的对应关系。
  28. 根据权利要求26或27所述的通信装置，其特征在于，
    所述收发单元，还用于接收来自所述第一网元的支持所述应用的一个或多个业务功能的信息；或者，
    所述收发单元，还用于接收来自所述第一网元的支持所述应用的一个或多个外部业务功能的信息。
  29. 根据权利要求27或28所述的通信装置，其特征在于，所述一个或多个业务功能的信息，为所述一个或多个业务功能的标识或类型。
  30. 根据权利要求26至29中任一项所述的通信装置，其特征在于，
    所述收发单元，还用于向第五网元发送第二请求消息，所述第二请求消息包括查询的业务链的信息；
    所述收发单元，还用于接收来自所述第五网元的支持所述查询的业务链的以下一项或多项信息：业务功能标识、业务链标识、业务功能标识和数据网络接入标识对应关系、业务链标识和数据网络接入标识对应关系。
  31. 根据权利要求26至30中任一项所述的通信装置，其特征在于，所述处理单元为处理器，和/或，所述收发单元为收发器。
  32. 根据权利要求26至31中任一项所述的通信装置，其特征在于，所述通信装置为以下任一项：网络设备、芯片或芯片***。
  33. 一种通信***，其特征在于，所述通信***包括第一网元和第二网元；
    所述第二网元，用于向所述第一网元发送第一请求消息，所述第一请求消息包括应用所需的业务链的信息；
    所述第一网元，用于向第三网元发送应用对应的业务链策略，所述应用对应的业务链策略是根据所述应用所需的业务链的信息制定的。
  34. 根据权利要求33所述的通信***，其特征在于，所述通信***还包括第三网元，
    所述第三网元，用于接收来自所述第一网元的应用对应的业务链策略与数据网络接入标识之间的对应关系的信息，其中，数据网络接入标识包括第一数据网络接入标识；根据所述第一数据网络接入标识选择用户面网元，并指示所述用户面网元执行第一业务链策略，所述第一业务链策略为所述第一数据网络接入标识对应的业务链策略。
  35. 根据权利要求34所述的通信***，其特征在于，所述第三网元还用于：向所述第一网元发送所述第一数据网络接入标识；或者，向所述第一网元发送所述第一业务链策略。
  36. 根据权利要求35所述的通信***，所述第一网元还用于：接收所述第三网元发送的所述第一数据网络接入标识，并根据所述第一数据网络接入标识确定所述用户访问所述应用对应的业务链策略；或者，接收所述第三网元发送的所述第一数据网络接入标识，并根据所述第一数据网络接入标识确定支持所述用户访问的所述应用的一个或多个业务功能；或者，所述第三网元向所述第一网元发送所述第一业务链策略，并根据所述第一业务链策略确定所述支持所述用户访问的所述应用的一个或多个业务功能。
  37. 根据权利要求33至36中任一项所述的通信***，其特征在于，所述通信***还包括第四网元，
    所述第四网元，用于接收来自所述第一网元的第二请求消息或第三请求消息，其中，所述第二请求消息包括所述应用对应的业务链策略和访问所述应用的用户的标识，所述第二请求消息用于请求对所述用户访问所述应用对应的业务链策略进行授权；所述第三请求消息包括所述支持的一个或多个业务功能的信息和访问所述应用的用户的标识，所述第三请求消息用于请求对支持所述用户访问的所述应用的一个或多个业务功能进行授权。
  38. 根据权利要求33至37中任一项所述的通信***，其特征在于，所述通信***还包括第五网元，
    所述第五网元，用于接收来自所述第二网元的所述第一请求消息；对所述应用所需的业务链的信息进行处理，并且向所述第一网元发送处理后的所述业务链的信息。
  39. 一种通信装置，其特征在于，包括至少一个处理器，所述至少一个处理器用于执行如权利要求1至9中任一项所述的方法。
  40. 根据权利要求39所述的装置，其特征在于，所述装置还包括存储器，所述处理器用于执行所述存储器中存储的计算机指令，以使得所述装置执行如权利要求1至9中任一项所述的方法。
  41. 根据权利要求39或40所述的装置，其特征在于，所述装置还包括通信接口，所述通信接口与所述处理器耦合，
    所述通信接口，用于输入和/或输出信息。
  42. 根据权利要求39至41中任一项所述的装置，其特征在于，所述装置为以下任一项：网络设备、芯片或芯片***。
  43. 一种通信装置，其特征在于，包括至少一个处理器，所述至少一个处理器用于执行如权利要求10至14中任一项所述的方法。
  44. 根据权利要求43所述的装置，其特征在于，所述装置还包括存储器，所述处理器用于执行所述存储器中存储的计算机指令，以使得所述装置执行如权利要求1至9中任一项所述的方法。
  45. 根据权利要求43或44所述的装置，其特征在于，所述装置还包括通信接口，所述通信接口与所述处理器耦合，
    所述通信接口，用于输入和/或输出信息。
  46. 根据权利要求43至45中任一项所述的装置，其特征在于，所述装置为以下任一项：网络设备、芯片或芯片***。
  47. 一种计算机可读存储介质，其特征在于，所述计算机可读介质存储有计算机程序；所述计算机程序由一个或多个处理器执行时，使得包括所述处理器的装置执行如权利要求1至9中任一项所述的方法。
  48. 一种计算机可读存储介质，其特征在于，所述计算机可读介质存储有计算机程序；所述计算机程序由一个或多个处理器执行时，使得包括所述处理器的装置执行如权利要求10至14中任一项所述的方法。
  49. 一种计算机程序产品，其特征在于，所述计算机程序产品包括计算机程序代码，当所述计算机程序代码在计算机上运行时，实现权利要求1至9中任一项所述的方法。
  50. 一种计算机程序产品，其特征在于，所述计算机程序产品包括计算机程序代码，当所述计算机程序代码在计算机上运行时，实现权利要求10至14中任一项所述的方法。
PCT/CN2021/129713 2021-02-09 2021-11-10 确定策略的方法和通信装置 WO2022170798A1 (zh)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN202110179154.1 2021-02-09
CN202110179154.1A CN114915929A (zh) 2021-02-09 2021-02-09 确定策略的方法和通信装置

Publications (1)

Publication Number Publication Date
WO2022170798A1 true WO2022170798A1 (zh) 2022-08-18

Family

ID=82762311

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2021/129713 WO2022170798A1 (zh) 2021-02-09 2021-11-10 确定策略的方法和通信装置

Country Status (2)

Country Link
CN (1) CN114915929A (zh)
WO (1) WO2022170798A1 (zh)

Families Citing this family (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN118139019A (zh) * 2022-12-01 2024-06-04 华为技术有限公司 一种业务链策略处理方法、装置和***

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN109842895A (zh) * 2019-03-20 2019-06-04 腾讯科技（深圳）有限公司 一种网络可靠性配置方法、信息传输方法和装置以及***
CN110048873A (zh) * 2018-01-16 2019-07-23 华为技术有限公司 多锚点协议数据单元会话的策略控制的方法和通信装置
CN110740430A (zh) * 2018-07-20 2020-01-31 维沃移动通信有限公司 资源计费方法与***、af以及策略与计费功能实体

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN110048873A (zh) * 2018-01-16 2019-07-23 华为技术有限公司 多锚点协议数据单元会话的策略控制的方法和通信装置
CN110740430A (zh) * 2018-07-20 2020-01-31 维沃移动通信有限公司 资源计费方法与***、af以及策略与计费功能实体
CN109842895A (zh) * 2019-03-20 2019-06-04 腾讯科技（深圳）有限公司 一种网络可靠性配置方法、信息传输方法和装置以及***

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
HUAWEI, HISILICON: "Correction to traffic steering control", 3GPP DRAFT; S2-1810763 - 23501 CORRECTION TO TRAFFIC STEERING CONTROL, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE, vol. SA WG2, no. Dongguan, China; 20181015 - 20181019, 9 October 2018 (2018-10-09), Mobile Competence Centre ; 650, route des Lucioles ; F-06921 Sophia-Antipolis Cedex ; France , XP051539712 *

Also Published As

Publication number Publication date
CN114915929A (zh) 2022-08-16

Similar Documents

Publication Publication Date Title
JP7041212B2 (ja) 仮想化されたモバイルコアネットワークへの接続
WO2020168840A1 (zh) 网络节点选择方法及装置
WO2023280121A1 (zh) 一种获取边缘服务的方法和装置
US20220217611A1 (en) Service Configuration Method, Communication Apparatus, and Communication System
WO2021136211A1 (zh) 授权结果的确定方法及装置
KR20190133239A (ko) 중계 통신 방법과 중계 통신 장치 및 시스템
KR20210024160A (ko) 통신 방법 및 장치
US20230254922A1 (en) Multipath transmission method and communication apparatus
CN112752297B (zh) 一种通信方法及设备
US20230156833A1 (en) Packet Forwarding Method, Apparatus, and System
US20240172084A1 (en) Data transmission method and apparatus
WO2022199451A1 (zh) 会话切换的方法和装置
US20220272577A1 (en) Communication method and communication apparatus
US20240196316A1 (en) Systems and methods for inhomogeneous slice support
WO2022170798A1 (zh) 确定策略的方法和通信装置
WO2023087965A1 (zh) 一种通信方法及装置
KR20210144491A (ko) 무선 통신 시스템에서 단말의 데이터 세션 앵커의 재배치를 위한 방법 및 장치
KR20240060670A (ko) 통신 방법 및 장치
WO2022142792A1 (zh) 用于传输数据的方法和装置
US20230180212A1 (en) P-bsr enhancements for iab networks to improve e2e latency
WO2024001897A1 (zh) 通信方法和装置
WO2023142717A1 (zh) 一种确定用户设备路由选择策略的方法和装置
WO2023160394A1 (zh) 通信的方法和装置
WO2023197772A1 (zh) 一种通信方法及相关装置
US20240155325A1 (en) Information obtaining method and apparatus, and system

Legal Events

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

Ref document number: 21925445

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 21925445

Country of ref document: EP

Kind code of ref document: A1