WO2021217412A1 - 一种确定终端策略行为的方法及装置、网络设备 - Google Patents

一种确定终端策略行为的方法及装置、网络设备 Download PDF

Info

Publication number
WO2021217412A1
WO2021217412A1 PCT/CN2020/087472 CN2020087472W WO2021217412A1 WO 2021217412 A1 WO2021217412 A1 WO 2021217412A1 CN 2020087472 W CN2020087472 W CN 2020087472W WO 2021217412 A1 WO2021217412 A1 WO 2021217412A1
Authority
WO
WIPO (PCT)
Prior art keywords
terminal
information
pdu session
indication information
ursp
Prior art date
Application number
PCT/CN2020/087472
Other languages
English (en)
French (fr)
Inventor
许阳
Original Assignee
Oppo广东移动通信有限公司
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 Oppo广东移动通信有限公司 filed Critical Oppo广东移动通信有限公司
Priority to CN202080100317.6A priority Critical patent/CN115516920A/zh
Priority to CN202310653096.0A priority patent/CN116709420A/zh
Priority to PCT/CN2020/087472 priority patent/WO2021217412A1/zh
Priority to EP20933831.8A priority patent/EP4142372B1/en
Publication of WO2021217412A1 publication Critical patent/WO2021217412A1/zh
Priority to US17/975,761 priority patent/US20230068189A1/en

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W40/00—Communication routing or communication path finding
    • H04W40/34—Modification of an existing route
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L45/00—Routing or path finding of packets in data switching networks
    • H04L45/80—Ingress point selection by the source endpoint, e.g. selection of ISP or POP
    • H04L45/85—Selection among different networks
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W28/00—Network traffic management; Network resource management
    • H04W28/02—Traffic management, e.g. flow control or congestion control
    • H04W28/0268—Traffic management, e.g. flow control or congestion control using specific QoS parameters for wireless networks, e.g. QoS class identifier [QCI] or guaranteed bit rate [GBR]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/10—Connection setup

Definitions

  • the embodiments of the present application relate to the field of mobile communication technology, and in particular to a method and device for determining a terminal policy behavior, and network equipment.
  • URSP rule When the terminal uses the UE Route Selection Policy (URSP), it may not select the optimal URSP rule (URSP rule), resulting in some “undesired behaviors” of the terminal, and the network side has no way of knowing this , And then unable to optimize the URSP configuration.
  • URSP rule UE Route Selection Policy
  • the embodiment of the present application provides a method and device for determining a terminal policy behavior, and a network device.
  • the first network element obtains at least one of the following information: the first information sent by the terminal, the second information sent by the policy control function network element (Policy Control Function, PCF), and the session management function network element (Session Management Function, SMF) sent The third information, the fourth information sent by the application server;
  • Policy Control Function Policy Control Function
  • SMF Session Management Function
  • the first network element determines the terminal policy behavior executed by the terminal according to the at least one kind of information.
  • the device for determining the policy behavior of the terminal is applied to a first network element, and the device includes:
  • the acquiring unit is configured to acquire at least one of the following information: the first information sent by the terminal, the second information sent by the PCF, the third information sent by the SMF, and the fourth information sent by the application server;
  • the determining unit is configured to determine the terminal policy behavior executed by the terminal according to the at least one type of information.
  • the network device provided by the embodiment of the present application includes a processor and a memory.
  • the memory is used to store a computer program
  • the processor is used to call and run the computer program stored in the memory to execute the above-mentioned method for determining a terminal policy behavior.
  • the chip provided in the embodiment of the present application is used to implement the above-mentioned method for determining the terminal policy behavior.
  • the chip includes: a processor, configured to call and run a computer program from the memory, so that the device installed with the chip executes the above-mentioned method for determining the terminal policy behavior.
  • the computer-readable storage medium provided by the embodiment of the present application is used to store a computer program, and the computer program enables a computer to execute the above-mentioned method for determining a terminal policy behavior.
  • the computer program product provided by the embodiment of the present application includes computer program instructions that cause the computer to execute the above-mentioned method for determining the terminal policy behavior.
  • the computer program provided by the embodiment of the present application when it runs on a computer, causes the computer to execute the above-mentioned method for determining the terminal policy behavior.
  • the first network element determines the terminal strategy executed by the terminal according to at least one of the first information sent by the terminal, the second information sent by the PCF, the third information sent by the SMF, and the fourth information sent by the application server. Behavior, and then the URSP configuration can be optimized according to the execution of the terminal policy behavior.
  • FIG. 1 is a schematic diagram of a communication system architecture provided by an embodiment of the present application.
  • Figure 2 is a 5G architecture diagram provided by an embodiment of the application.
  • FIG. 3 is a flow chart of UCU provided by an embodiment of the application.
  • FIG. 4 is a schematic diagram of binding an application data stream to a PDU session provided by an embodiment of the application
  • FIG. 5 is a flowchart of the PDU session establishment being rejected and the PDU session establishment being tried again according to an embodiment of the application;
  • FIG. 6 is a schematic flowchart 1 of a method for determining a terminal policy behavior provided by an embodiment of the application
  • FIG. 7 is a second schematic flowchart of a method for determining a terminal policy behavior provided by an embodiment of the application.
  • FIG. 8 is a third schematic flowchart of a method for determining a terminal policy behavior provided by an embodiment of the application.
  • FIG. 9 is a schematic structural composition diagram of an apparatus for determining a terminal policy behavior provided by an embodiment of the application.
  • FIG. 10 is a schematic structural diagram of a communication device provided by an embodiment of the present application.
  • FIG. 11 is a schematic structural diagram of a chip of an embodiment of the present application.
  • FIG. 12 is a schematic block diagram of a communication system provided by an embodiment of the present application.
  • LTE Long Term Evolution
  • FDD Frequency Division Duplex
  • TDD Time Division Duplex
  • 5G communication system or future communication system etc.
  • the communication system 100 applied in the embodiment of the present application is shown in FIG. 1.
  • the communication system 100 may include a network device 110, and the network device 110 may be a device that communicates with a terminal 120 (or called a communication terminal or terminal).
  • the network device 110 may provide communication coverage for a specific geographic area, and may communicate with terminals located in the coverage area.
  • the network device 110 may be an evolved base station (Evolutional Node B, eNB, or eNodeB) in an LTE system, or a wireless controller in a cloud radio access network (Cloud Radio Access Network, CRAN), or
  • the network equipment can be a mobile switching center, a relay station, an access point, an in-vehicle device, a wearable device, a hub, a switch, a bridge, a router, a network side device in a 5G network, or a network device in a future communication system, etc.
  • the communication system 100 also includes at least one terminal 120 located within the coverage area of the network device 110.
  • the "terminal” used here includes, but is not limited to, connection via a wired line, such as via a public switched telephone network (PSTN), digital subscriber line (Digital Subscriber Line, DSL), digital cable, and direct cable connection; And/or another data connection/network; and/or via a wireless interface, such as for cellular networks, wireless local area networks (WLAN), digital TV networks such as DVB-H networks, satellite networks, AM-FM Broadcast transmitter; and/or another terminal's device configured to receive/send communication signals; and/or Internet of Things (IoT) equipment.
  • PSTN public switched telephone network
  • DSL Digital Subscriber Line
  • DSL Digital Subscriber Line
  • DSL Digital Subscriber Line
  • DSL Digital Subscriber Line
  • DSL Digital Subscriber Line
  • DSL Digital Subscriber Line
  • DSL Digital Subscriber Line
  • DSL Digital Subscriber Line
  • DSL Digital Subscriber Line
  • DSL Digital Subscriber Line
  • a terminal set to communicate through a wireless interface may be referred to as a "wireless communication terminal", a “wireless terminal” or a “mobile terminal”.
  • mobile terminals include, but are not limited to, satellite or cellular phones; Personal Communications System (PCS) terminals that can combine cellular radio phones with data processing, fax, and data communication capabilities; can include radio phones, pagers, Internet/intranet PDA with internet access, web browser, memo pad, calendar, and/or Global Positioning System (GPS) receiver; and conventional laptop and/or palmtop receivers or others including radio telephone transceivers Electronic device.
  • PCS Personal Communications System
  • GPS Global Positioning System
  • Terminal can refer to access terminal, user equipment (UE), user unit, user station, mobile station, mobile station, remote station, remote terminal, mobile device, user terminal, terminal, wireless communication equipment, user agent or user Device.
  • the access terminal can be a cellular phone, a cordless phone, a Session Initiation Protocol (SIP) phone, a wireless local loop (Wireless Local Loop, WLL) station, a personal digital processing (Personal Digital Assistant, PDA), with wireless communication Functional handheld devices, computing devices or other processing devices connected to wireless modems, in-vehicle devices, wearable devices, terminals in 5G networks, or terminals in the future evolution of PLMN, etc.
  • SIP Session Initiation Protocol
  • WLL Wireless Local Loop
  • PDA Personal Digital Assistant
  • direct terminal connection (Device to Device, D2D) communication may be performed between the terminals 120.
  • the 5G communication system or 5G network may also be referred to as a New Radio (NR) system or NR network.
  • NR New Radio
  • FIG. 1 exemplarily shows one network device and two terminals.
  • the communication system 100 may include multiple network devices and the coverage of each network device may include other numbers of terminals. This embodiment of the present application There is no restriction on this.
  • the communication system 100 may also include other network entities such as a network controller and a mobility management entity, which are not limited in the embodiment of the present application.
  • network entities such as a network controller and a mobility management entity, which are not limited in the embodiment of the present application.
  • the devices with communication functions in the network/system in the embodiments of the present application may be referred to as communication devices.
  • the communication device may include a network device 110 and a terminal 120 with communication functions, and the network device 110 and the terminal 120 may be the specific devices described above, which will not be repeated here; communication
  • the device may also include other devices in the communication system 100, such as other network entities such as a network controller and a mobility management entity, which are not limited in the embodiment of the present application.
  • the 5G architecture is shown in Figure 2.
  • the equipment involved in the 5G architecture includes: terminal, radio access network (RAN), user plane function network element (User Plane Function, UPF), data network (Data Network, DN), Access and Mobility Management Function (AMF), Session Management Function (SMF), Policy Control Function (PCF), Application Function Network element (Application Function, AF), authentication server function network element (Authentication Server Function, AUSF), unified data management network element (Unified Data Management, UDM).
  • RAN radio access network
  • UPF User Plane Function
  • Data Network Data Network
  • AMF Access and Mobility Management Function
  • SMF Session Management Function
  • PCF Policy Control Function
  • Application Function Network element Application Function, AF
  • AUSF Authentication Server Function
  • UDM Unified Data Management
  • the network elements related to the strategy are mainly PCF, AMF, SMF, RAN, and terminals.
  • the SMF is mainly responsible for the execution of the policies related to the session
  • the AMF is mainly responsible for the execution of the policies related to the access and terminal policies
  • the policy issuance and update on the two network elements (AMF and SMF) are all controlled by the PCF.
  • the PCF and the terminal monitor the information related to the terminal policy through a container (Container), including the content of the terminal policy, the terminal policy identifier, and so on.
  • Container a container
  • the container is sent by the terminal to the AMF through a non-access stratum (NAS) message, and the AMF continues to transparently transmit (not aware or modify) to the PCF.
  • NAS non-access stratum
  • the PCF transfers the container to the container. Send to AMF, and AMF then transparently transmits to the terminal through NAS message.
  • the terminal strategy is implemented through the UE Configuration Update (UCU) process.
  • UCU UE Configuration Update
  • the UCU process includes the following steps:
  • Step 301 The PCF decides to update the terminal strategy.
  • Step 302 The PCF puts the terminal policy to be updated in a container and sends it to the AMF.
  • Step 303 The AMF uses the NAS message to directly forward the container to the terminal.
  • Step 304 The terminal sends the policy configuration result (Result of the delivery of UE policies) to the AMF.
  • Terminal strategies include Access Network Discovery and Selection Policy (ANDSP), URSP, etc.
  • URSP determines the binding relationship between application data and Protocol Data Unit (PDU) sessions, and also determines What PDU session needs to be established by the terminal to satisfy this binding relationship.
  • PDU Protocol Data Unit
  • FIG 4 different application data flows are bound to different PDU sessions according to URSP rules, data flow-a is bound to PDU session-1 according to rule-1, and data flow-b is bound according to rule-2 To PDU session-2, data flow-c is bound to PDU session-3 according to rule-3.
  • the session attribute parameters associated with the PDU session include: Single-Network Slice Selection Assistant Information (S-NSSAI), Data Network Name (DNN), PDU Session ID (PDU Session id), PDU Session type (PDU Session Type), service and session continuity mode (Service and Session Continuity Mode, SSC Mode).
  • S-NSSAI Single-Network Slice Selection Assistant Information
  • DNN Data Network Name
  • PDU Session ID PDU Session ID
  • PDU Session Type PDU Session type
  • service and session continuity mode Service and Session Continuity Mode, SSC Mode
  • the terminal can carry the above-mentioned session attribute parameters in the PDU session establishment request message. If some session attribute parameters are not carried, the network side can fill it up.
  • both the terminal and/or the network side can save the session attribute parameters of the successfully established PDU session, as well as which session attribute parameters are requested by the terminal and which session attribute parameters are filled by the network.
  • the URSP includes multiple URSP rules, and each URSP rule is composed of a traffic descriptor (Traffic Descriptor) and a set of routing selectors (Route Selection Descriptor, RSD).
  • the service descriptor in URSP is used to describe a specific service.
  • the microblog service can be described by the range of IP address 1-9
  • the IMS service can be described by IMS DNN.
  • the value of S-NSSAI and the value of DNN in an RSD can be one or more, and other parameters only contain one value.
  • each RSD can correspond to one or more parameter value combinations, and each parameter value combination is a set of PDU session characteristics.
  • the service data corresponding to the service descriptor can be performed in the PDU session corresponding to a certain parameter value combination of the RSD. transmission.
  • the terminal can select a parameter value combination according to the corresponding RSD and initiate a PDU session establishment request.
  • Table 1 List of service descriptors and corresponding RSDs in URSP rules
  • the terminal associates the application data stream to the corresponding PDU session for transmission based on the URSP rules, and the mechanism is as follows:
  • the terminal uses the URSP rules in the URSP to check whether the characteristics of the application data match the Traffic Descriptor of a certain rule in the URSP rules, and the viewing order is based on the priority (Precedence) in the URSP rules. Decision, that is, the terminal checks the matching situation in sequence based on the priority order, and when a URSP rule is matched, the RSD list under the URSP rule is used to bind the PDU session.
  • the priority Precedence
  • the terminal first finds whether the currently established PDU session has a valid RSD that meets the matching URSP rule, and if so, binds the matching application data to the PDU session for transmission, otherwise:
  • the terminal will bind the application data to the PDU session for transmission;
  • the terminal tries to establish the PDU session again based on other parameter value combinations in the RSD or using the parameter value combination in the second priority RSD.
  • the terminal will look up whether the Traffic Descriptor in the second-priority URSP rule can match the characteristics of the application data according to the Precedence order. When it matches, repeat The process of 1) and 2) above.
  • the above process of finding or establishing a suitable PDU session for application data is called an "evaluation process".
  • the RSD in the URSP rule is considered to be a valid RSD only if the following conditions are met (here, the valid RSD is used to perform the above evaluation process):
  • S-NSSAI must belong to one of Allowed NSSAI (non-roaming) or Mapping of Allowed NSSAI (roaming);
  • the terminal must be in the effective area corresponding to the LADN;
  • the terminal must support the ATSSS function;
  • the terminal must meet the required time and location conditions.
  • the terminal will not use the RSD to bind application data or establish a PDU session.
  • the terminal can try to establish the PDU session again according to the parameters in the RSD after the initiation of the PDU session establishment is rejected.
  • the process of PDU session establishment being rejected and retrying PDU session establishment includes the following steps:
  • Step 501 The terminal sends a PDU session establishment request message to the SMF.
  • the PDU session establishment request message carries at least one of the following session attribute parameters: DNN, S-NSSAI, PDU Session Type, SSC Mode, and PDU Session ID.
  • Step 502 The SMF sends a PDU session establishment request reply message to the terminal, carrying the rejection reason value.
  • the PDU session establishment request reply message will carry the rejection reason value.
  • Step 503 The terminal adjusts the parameter value combination according to the RSD in the URSP rule to initiate PDU session establishment again.
  • the URSP mechanism has the following characteristics and problems:
  • the parameters in the URSP rule may not be recognized by the terminal.
  • some parameters require coordination between operators and terminal companies, which cannot be determined unilaterally by operators.
  • the terminal if the terminal cannot recognize a parameter in a URSP rule, it will automatically ignore the URSP rule. However, the terminal will not inform the network side which URSP rules or RSDs in it have been ignored. As a result, some URSP rules issued by the network side may never be executed by the terminal, but the network side does not know the situation.
  • the terminal When the terminal receives a new URSP rule (for example, the terminal receives a new URSP rule through the UCU process), the terminal will re-evaluate the new URSP rule, and determine the new relationship between the application data and the PDU session according to the new URSP rule. Binding relationship. However, when the terminal evaluates this new URSP rule, and when to execute the new binding relationship, the terminal is self-fulfilling. After the network has updated the URSP rule for the terminal, it cannot be determined when the terminal will execute the new URSP rule to bind the application data stream.
  • a new URSP rule for example, the terminal receives a new URSP rule through the UCU process
  • the terminal will finally select a PDU session corresponding to the RSD under the URSP rule for data transmission through the evaluation process. Then, this binding relationship will not be changed for a considerable period of time.
  • the URSP rule and RSD used by the terminal for a specific application data stream may not have the highest priority, but the network side cannot determine which URSP rule and RSD the terminal uses for the application data stream.
  • FIG. 6 is a schematic flowchart 1 of a method for determining a terminal policy behavior provided by an embodiment of the application. As shown in FIG. 6, the method for determining a terminal policy behavior includes the following steps:
  • Step 601 The first network element obtains at least one of the following information: first information sent by the terminal, second information sent by the PCF, third information sent by the SMF, and fourth information sent by the application server.
  • the first network element is a network element with an analysis function.
  • the first network element is a network data analysis function (Network Data Analysis Function, NWDAF).
  • NWDAF Network Data Analysis Function
  • the information obtained by the first network element includes at least one of the following: first information sent by the terminal, second information sent by the PCF, third information sent by the SMF, and fourth information sent by the application server. This information is explained in detail below.
  • the first information sent by the terminal includes at least one of the following:
  • the first indication information is used to indicate at least one of the following: the URSP rule being used by the terminal, the Traffic Descriptor of the URSP rule being used by the terminal, and the RSD in the URSP rule being used by the terminal; here, the terminal sends When Traffic Descriptor, you can send all the parameters in Traffic Descriptor, or you can also send only some of the parameters in Traffic Descriptor;
  • the second indication information is used to indicate at least one of the following: whether the terminal has used (or executed) the updated URSP rule, the terminal has used (or executed) the updated URSP rule (that is, which updated The URSP rules have been used or implemented by the terminal);
  • the third indication information is used to indicate at least one of the following: the PDU session established by the terminal to transmit data for a specific application, the URSP rule corresponding to the PDU session established by the terminal, and the URSP rule corresponding to the PDU session established by the terminal Traffic Descriptor, RSD in the URSP rule corresponding to the PDU session established by the terminal.
  • the first information is sent by the terminal to the first network element through a control plane message.
  • the control plane message is a NAS message, and the first information is carried in the NAS message; or, the first information is carried in a container in the NAS message.
  • the first information is sent by the terminal to the first network element through a user plane message.
  • the first information is sent by the terminal to a user plane network element through a user plane message, and is forwarded by the user plane network element to the first network element.
  • a header of the user plane message carries a first identifier, and the first identifier is used to instruct the user plane network element to forward the user plane message to the first network element.
  • the header of the user plane message is an SDAP header or a GTP-U header.
  • the user plane network element is UPF.
  • the first information sent by the terminal may also be referred to as policy execution information.
  • the terminal may send seventh indication information to the network side, where the seventh indication information is used to indicate that the terminal on the network side requests to report the first information or has the ability to report the first information.
  • the seventh indication information is further used to indicate what content the terminal can or request to report includes the first information.
  • the seventh indication information may be sent to the network side through an uplink NAS message.
  • the terminal includes the seventh indication information in a registration request message and sends it to the network side.
  • the network side sends eighth indication information to the terminal, where the eighth indication information is used to indicate that the terminal is required or allowed to report the first information. Further, optionally, the eighth indication information is also used to indicate what content contained in the first information reported by the terminal is required or allowed.
  • the network side may be the first network element.
  • the eighth indication information may be sent to the terminal through a downlink NAS message,
  • the network side adds the eighth instruction information to the registration reply message and sends it to the terminal.
  • the second information includes fourth indication information, and the fourth indication information is used to indicate at least one of the following:
  • the URSP rule issued to the terminal the traffic descriptor of the URSP rule issued to the terminal, the mapping relationship between the URSP rule issued to the terminal and the application, the mapping between the traffic descriptor of the URSP rule issued to the terminal and the application relation.
  • the third information includes fifth indication information, and the fifth indication information is used to indicate at least one of the following:
  • the session attribute parameter corresponding to the PDU session established by the terminal, the session attribute parameter corresponding to the PDU session established by the terminal, and the session attribute parameter corresponding to the established PDU session of the terminal belong to the session attribute parameter requested by the terminal (that is, the session attribute corresponding to the PDU session established by the terminal).
  • Which session attribute parameters in the parameters are requested by the terminal the session attribute parameters corresponding to the established PDU session of the terminal belong to the session attribute parameters added by the network (that is, which session attribute parameters of the session attribute parameters corresponding to the established PDU session of the terminal are (Added by the network), the address information of the established PDU session of the terminal.
  • the address information of the PDU session refers to the IP address information of the PDU session.
  • the fourth information includes sixth indication information, and the sixth indication information is used to indicate at least one of the following:
  • the address information of the terminal refers to the IP address information of the terminal.
  • Step 602 The first network element determines the terminal policy behavior executed by the terminal according to the at least one type of information.
  • the first network element may analyze the at least one type of information, and then determine the terminal policy behavior performed by the terminal.
  • the terminal policy behavior includes at least one of the following:
  • the UE routing strategy URSP rule being used by the terminal
  • the protocol data unit PDU session used by the terminal to transmit data for a specific application
  • a specific application may refer to an application corresponding to a specific application identifier (Application Id).
  • the first network element receives the first information (that is, the policy execution information) sent by the terminal, and the first network element determines the terminal policy behavior that the terminal is executing based on the first information.
  • the first information that is, the policy execution information
  • the first network element further receives at least one of the following: the second information sent by the PCF, the third information sent by the SMF, and the fourth information sent by the application server.
  • the first network element determines the terminal policy behavior that the terminal is executing based on the first information and at least one of the second information, the third information, and the fourth information.
  • the content of the first information, the second information, the third information, and the fourth information can refer to the description of the foregoing solution.
  • Fig. 7 takes the first network element being NWDAF as an example, and includes the following steps:
  • Step 701 NWDAF receives the first information sent by the terminal.
  • Step 702 NWDAF receives the second information sent by PCF.
  • Step 703 NWDAF receives the third information sent by SMF.
  • Step 704 NWDAF receives the fourth information sent by the application server.
  • Step 705 NWDAF determines the terminal policy behavior executed by the terminal according to the obtained information.
  • steps 702 to 704 are optional.
  • the following is a description with specific examples.
  • the terminal is using RSD-3 in URSP-Rule2;
  • URSP-Rule3 (RSD-1/2), corresponding to Application Id-3.
  • the fourth message from the application server request to detect on which network slice the data of Application Id-2 is transmitted (or request to detect on which network slice the data of Application Id-2 is transmitted on which S-NSSAI corresponds) .
  • NWDAF combined with the above information can determine: the terminal is using the RSD-3 in URSP-Rule2 as Application id-2 for data transmission, and the S-NSSAI parameter in RSD-3 is S-NSSAI-a, so ApplicationId -2 data is transmitted on the network slice corresponding to S-NSSAI-a.
  • the terminal is using RSD-3 in URSP-Rule2;
  • URSP-Rule3 (RSD-1/2), corresponding to Application Id-3.
  • NWDAF combined with the above information can determine: Application Id-1, 2 and 3 respectively on which PDU session is to be transmitted. Further, NWDAF can send the determined result to other network elements (such as a network management system) for statistical storage.
  • NWDAF can send the determined result to other network elements (such as a network management system) for statistical storage.
  • NWDAF is not the only network element that determines the terminal's policy behavior.
  • NWDAF can inform the PCF of the URSP rules currently being used by the terminal and the corresponding RSD, and the PCF determines the terminal policy behavior.
  • the first network element receives at least one of the following: the second information sent by the PCF, the third information sent by the SMF, and the fourth information sent by the application server.
  • the first network element determines, based on at least one of the second information, the third information, and the fourth information, the terminal policy behavior that the terminal is executing.
  • the content of the second information, the third information, and the fourth information can refer to the description of the foregoing solution.
  • Figure 8 takes the first network element being NWDAF as an example, and includes the following steps:
  • Step 801 NWDAF receives the second information sent by PCF.
  • Step 802 NWDAF receives the third information sent by SMF.
  • Step 803 NWDAF receives the fourth information sent by the application server.
  • Step 804 NWDAF determines the terminal policy behavior executed by the terminal according to the obtained information.
  • step 801 to step 803 some or all of the steps can be selected for execution.
  • the following is a description with specific examples.
  • PDU Session-1 corresponds to IP address 1
  • PDU Session-2 corresponds to IP address 2
  • session attribute parameters requested by the terminal corresponding to PDU Session-1 are S-NSSAI-1, DNN-1.
  • URSP-Rule1 (RSD-1 is composed of S-NSSAI-1 and DNN-1), corresponding to Application Id-1, Application Id-2;
  • URSP-Rule2 (RSD-1/2/3 do not include S-NSSAI-1), corresponding to Application Id-2;
  • URSP-Rule3 (RSD-1/2), corresponding to Application Id-3.
  • the IP address of the terminal is IP address 1* (corresponding to IP address 1), Application Id-2.
  • the IP address of the terminal provided by the application server may be a public network IP address that has undergone NAT conversion, while the IP address corresponding to the PDU session is a private network IP address.
  • the conversion relationship between the two can be controlled by the network side. That is to say, the IP address of the terminal notified by the application server is IP address 1*, and the operator network can know that IP address 1* corresponds to IP address 1.
  • NWDAF combined with the above information can determine that the terminal is using PDU Session-1 to transmit the application data stream, and the terminal is using URSP-Rule1 (RSD1) to transmit the application data stream.
  • RSD1 URSP-Rule1
  • the terminal has two PDU Sessions, namely PDU Session-1 and PDU Session-2.
  • the session attribute parameters requested by the terminal corresponding to PDU Session-1 are S-NSSAI-1, DNN- 1.
  • the session attribute parameters requested by the terminal corresponding to PDU Session-2 are S-NSSAI-2 and DNN-2.
  • the Traffic Descriptor corresponding to the application is the IP address y.
  • NWDAF combined with the above information can determine that the terminal is using RSD-2 in URSP-Rule2 and is using PDU Session-2 to transmit application data.
  • the terminal has two PDU Sessions, namely PDU Session-1 and PDU Session-2, where the address information of PDU Session-1 is IP address 1, and the session attribute parameter is S-NSSAI-1 , DNN-1;
  • the address information of PDU Session-2 is IP address 2, and the session attribute parameters are S-NSSAI-2, DNN-2.
  • URSP-Rule1 (RSD-1), RSD-1 is composed of S-NSSAI-1 and DNN-1.
  • URSP-Rule2 (RSD-2), RSD-2 is composed of S-NSSAI-2 and DNN-2.
  • the address information of the terminal is IP address 2
  • NWDAF combined with the above information can determine that the terminal is using RSD-2 in URSP-Rule2 and is using PDU Session-2 to transmit application data.
  • NWDAF determines the traffic descriptor and the corresponding PDU session used by the current application based on the terminal address information and traffic descriptor obtained from the application server, and the address information of the PDU session and session attribute parameters of the PDU session obtained from SMF.
  • the attribute parameters are compared with the URSP rules (including Traffic descriptor and corresponding PDU session attribute parameters) obtained from the PCF to determine the URSP rules being used by the terminal.
  • NWDAF compares the traffic descriptor with the URSP rule obtained from the PCF to determine the session attribute parameters of the PDU session that the terminal may use, and based on the address obtained from the SMF The session attribute parameter of the PDU session corresponding to the information determines the URSP rule being used by the terminal.
  • the terminal has two PDU Sessions, namely PDU Session-1 and PDU Session-2, where the address information of PDU Session-1 is IP address 1, and the session attribute parameter is S-NSSAI-1 , DNN-1;
  • the address information of PDU Session-2 is IP address 2, and the session attribute parameters are S-NSSAI-2, DNN-2.
  • URSP-Rule1 (RSD-1), RSD-1 is composed of S-NSSAI-1 and DNN-1.
  • URSP-Rule2 (RSD-2), RSD-2 is composed of S-NSSAI-2 and DNN-2.
  • the address information of the terminal is IP address 2
  • the application identifier is Application Id-1.
  • Application descriptor "youtube service”.
  • the mapping relationship between the application identifier (Application Id) and the service descriptor (Traffic Descriptor) can be obtained by the PCF, or pre-configured on the NWDAF.
  • NWDAF combined with the above information can determine that the terminal is using RSD-2 in URSP-Rule2 and is using PDU Session-2 to transmit application data.
  • the application ID in the above solution of this application is used between the core network and the application server to refer to specific applications, and the application descriptor (Application descriptor) is used by the terminal to identify specific applications.
  • the format and value can be different, but there can be a corresponding relationship, that is, there is a corresponding relationship between Application Id and Application descriptor.
  • the technical solution of the embodiment of the present application proposes a mechanism for the network side to determine whether the terminal policy behavior executed by the terminal meets expectations, so that the network side determines whether the URSP rule executed by the terminal is what it wants. To this end, it is necessary to report relevant information through the terminal, core network elements (such as PCF, SMF), and application server, so that the analysis network element on the network side can analyze and obtain the corresponding results (such as whether the terminal is using the URSP rule with the highest priority) , And implement policy adjustments and updates when needed.
  • core network elements such as PCF, SMF
  • application server so that the analysis network element on the network side can analyze and obtain the corresponding results (such as whether the terminal is using the URSP rule with the highest priority) , And implement policy adjustments and updates when needed.
  • FIG. 9 is a schematic structural composition diagram of an apparatus for determining a terminal policy behavior according to an embodiment of the application, which is applied to a first network element.
  • the apparatus for determining a terminal policy behavior includes:
  • the obtaining unit 901 is configured to obtain at least one of the following information: first information sent by the terminal, second information sent by the PCF, third information sent by the SMF, and fourth information sent by the application server;
  • the determining unit 902 is configured to determine the terminal policy behavior performed by the terminal according to the at least one type of information.
  • the terminal policy behavior includes at least one of the following:
  • the URSP rules being used by the terminal
  • the PDU session used by the terminal to transmit data for a specific application
  • the first information includes at least one of the following:
  • First indication information where the first indication information is used to indicate at least one of the following: the URSP rule being used by the terminal, the Traffic Descriptor of the URSP rule being used by the terminal, and the RSD in the URSP rule being used by the terminal;
  • Second indication information where the second indication information is used to indicate at least one of the following: whether the terminal has used the updated URSP rule, and the updated URSP rule that the terminal has used;
  • the third indication information is used to indicate at least one of the following: the PDU session established by the terminal to transmit data for a specific application, the URSP rule corresponding to the PDU session established by the terminal, and the URSP rule corresponding to the PDU session established by the terminal Traffic Descriptor, RSD in the URSP rule corresponding to the PDU session established by the terminal.
  • the first information is sent by the terminal to the first network element through a control plane message.
  • control plane message is a NAS message
  • the first information is carried in the NAS message; or,
  • the first information is carried in a container in the NAS message.
  • the first information is sent by the terminal to the first network element through a user plane message.
  • the first information is sent by the terminal to a user plane network element through a user plane message, and is forwarded by the user plane network element to the first network element.
  • a header of the user plane message carries a first identifier, and the first identifier is used to instruct the user plane network element to forward the user plane message to the first network element.
  • the second information includes fourth indication information, and the fourth indication information is used to indicate at least one of the following:
  • the URSP rule issued to the terminal the traffic descriptor of the URSP rule issued to the terminal, the mapping relationship between the URSP rule issued to the terminal and the application, the mapping between the traffic descriptor of the URSP rule issued to the terminal and the application relation.
  • the third information includes fifth indication information, and the fifth indication information is used to indicate at least one of the following:
  • the PDU session established by the terminal, the session attribute parameter corresponding to the PDU session established by the terminal, the session attribute parameter corresponding to the PDU session established by the terminal belong to the session attribute parameter requested by the terminal, and the session attribute parameter corresponding to the PDU session established by the terminal It belongs to the session attribute parameter added by the network and the address information of the established PDU session of the terminal.
  • the fourth information includes sixth indication information, and the sixth indication information is used to indicate at least one of the following:
  • the acquiring unit 901 is further configured to receive seventh indication information sent by the terminal, where the seventh indication information is used to instruct the terminal on the network side to request to report the first information or have a report The ability to describe the first information.
  • the seventh indication information is further used to indicate what content the terminal can or request to report includes the first information.
  • the seventh indication information may be sent to the network side through an uplink NAS message.
  • the terminal includes the seventh indication information in a registration request message and sends it to the network side.
  • the device further includes: a sending unit (not shown in the figure), configured to send eighth indication information to the terminal, where the eighth indication information is used to indicate a requirement or allow the terminal to report ⁇ Said first information. Further, optionally, the eighth indication information is also used to indicate what content contained in the first information reported by the terminal is required or allowed.
  • the network side may be the first network element. The eighth indication information may be sent to the terminal through a downlink NAS message, for example, the network side adds the eighth indication information to the registration reply message and sends it to the terminal.
  • FIG. 10 is a schematic structural diagram of a communication device 1000 according to an embodiment of the present application.
  • the communication device may be a terminal or a network device (such as the first network element in the above solution).
  • the communication device 1000 shown in FIG. 10 includes a processor 1010, and the processor 1010 can call and run a computer program from a memory. To implement the method in the embodiment of the present application.
  • the communication device 1000 may further include a memory 1020.
  • the processor 1010 can call and run a computer program from the memory 1020 to implement the method in the embodiment of the present application.
  • the memory 1020 may be a separate device independent of the processor 1010, or may be integrated in the processor 1010.
  • the communication device 1000 may further include a transceiver 1030, and the processor 1010 may control the transceiver 1030 to communicate with other devices. Specifically, it may send information or data to other devices, or receive other devices. Information or data sent by the device.
  • the transceiver 1030 may include a transmitter and a receiver.
  • the transceiver 1030 may further include an antenna, and the number of antennas may be one or more.
  • the communication device 1000 may specifically be a network device of an embodiment of the application, and the communication device 1000 may implement the corresponding process implemented by the network device in each method of the embodiment of the application. For the sake of brevity, details are not repeated here. .
  • the communication device 1000 may specifically be a mobile terminal/terminal according to an embodiment of the present application, and the communication device 1000 may implement the corresponding process implemented by the mobile terminal/terminal in each method of the embodiment of the present application. For the sake of brevity, This will not be repeated here.
  • FIG. 11 is a schematic structural diagram of a chip of an embodiment of the present application.
  • the chip 1100 shown in FIG. 11 includes a processor 1110, and the processor 1110 can call and run a computer program from the memory to implement the method in the embodiment of the present application.
  • the chip 1100 may further include a memory 1120.
  • the processor 1110 can call and run a computer program from the memory 1120 to implement the method in the embodiment of the present application.
  • the memory 1120 may be a separate device independent of the processor 1110, or may be integrated in the processor 1110.
  • the chip 1100 may further include an input interface 1130.
  • the processor 1110 can control the input interface 1130 to communicate with other devices or chips, and specifically, can obtain information or data sent by other devices or chips.
  • the chip 1100 may further include an output interface 1140.
  • the processor 1110 can control the output interface 1140 to communicate with other devices or chips, and specifically, can output information or data to other devices or chips.
  • the chip can be applied to the network device in the embodiment of the present application, and the chip can implement the corresponding process implemented by the network device in each method of the embodiment of the present application.
  • the chip can implement the corresponding process implemented by the network device in each method of the embodiment of the present application.
  • the chip can be applied to the mobile terminal/terminal in the embodiment of the present application, and the chip can implement the corresponding process implemented by the mobile terminal/terminal in each method of the embodiment of the present application.
  • the chip can implement the corresponding process implemented by the mobile terminal/terminal in each method of the embodiment of the present application.
  • it will not be omitted here Go into details.
  • the chip mentioned in the embodiment of the present application may also be referred to as a system-level chip, a system-on-chip, a system-on-chip, or a system-on-chip, etc.
  • FIG. 12 is a schematic block diagram of a communication system 1200 according to an embodiment of the present application. As shown in FIG. 12, the communication system 1200 includes a terminal 1210 and a network device 1220.
  • the terminal 1210 may be used to implement the corresponding functions implemented by the terminal in the foregoing method
  • the network device 1220 may be used to implement the corresponding functions implemented by the network device in the foregoing method.
  • details are not described herein again.
  • the processor of the embodiment of the present application may be an integrated circuit chip with signal processing capability.
  • the steps of the foregoing method embodiments may be completed by hardware integrated logic circuits in the processor or instructions in the form of software.
  • the above-mentioned processor may be a general-purpose processor, a digital signal processor (Digital Signal Processor, DSP), an application specific integrated circuit (ASIC), a ready-made programmable gate array (Field Programmable Gate Array, FPGA) or other Programming logic devices, discrete gates or transistor logic devices, discrete hardware components.
  • DSP Digital Signal Processor
  • ASIC application specific integrated circuit
  • FPGA Field Programmable Gate Array
  • the methods, steps, and logical block diagrams disclosed in the embodiments of the present application can be implemented or executed.
  • the general-purpose processor may be a microprocessor or the processor may also be any conventional processor or the like.
  • the steps of the method disclosed in the embodiments of the present application may be directly embodied as being executed and completed by a hardware decoding processor, or executed and completed by a combination of hardware and software modules in the decoding processor.
  • the software module can be located in a mature storage medium in the field, such as random access memory, flash memory, read-only memory, programmable read-only memory, or electrically erasable programmable memory, registers.
  • the storage medium is located in the memory, and the processor reads the information in the memory and completes the steps of the above method in combination with its hardware.
  • the memory in the embodiments of the present application may be a volatile memory or a non-volatile memory, or may include both volatile and non-volatile memory.
  • the non-volatile memory can be read-only memory (Read-Only Memory, ROM), programmable read-only memory (Programmable ROM, PROM), erasable programmable read-only memory (Erasable PROM, EPROM), and electrically available Erase programmable read-only memory (Electrically EPROM, EEPROM) or flash memory.
  • the volatile memory may be a random access memory (Random Access Memory, RAM), which is used as an external cache.
  • RAM random access memory
  • SRAM static random access memory
  • DRAM dynamic random access memory
  • DRAM synchronous dynamic random access memory
  • DDR SDRAM Double Data Rate Synchronous Dynamic Random Access Memory
  • Enhanced SDRAM, ESDRAM Enhanced Synchronous Dynamic Random Access Memory
  • Synchronous Link Dynamic Random Access Memory Synchronous Link Dynamic Random Access Memory
  • DR RAM Direct Rambus RAM
  • the memory in the embodiment of the present application may also be static random access memory (static RAM, SRAM), dynamic random access memory (dynamic RAM, DRAM), Synchronous dynamic random access memory (synchronous DRAM, 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 connection Dynamic random access memory (synch link DRAM, SLDRAM) and direct memory bus random access memory (Direct Rambus RAM, DR RAM) and so on. That is to say, the memory in the embodiments of the present application is intended to include, but is not limited to, these and any other suitable types of memory.
  • the embodiments of the present application also provide a computer-readable storage medium for storing computer programs.
  • the computer-readable storage medium can be applied to the network device in the embodiment of the present application, and the computer program causes the computer to execute the corresponding process implemented by the network device in each method of the embodiment of the present application.
  • the computer program causes the computer to execute the corresponding process implemented by the network device in each method of the embodiment of the present application.
  • the computer-readable storage medium can be applied to the mobile terminal/terminal in the embodiment of the present application, and the computer program causes the computer to execute the corresponding process implemented by the mobile terminal/terminal in each method of the embodiment of the present application, in order to It's concise, so I won't repeat it here.
  • the embodiments of the present application also provide a computer program product, including computer program instructions.
  • the computer program product can be applied to the network device in the embodiment of the present application, and the computer program instructions cause the computer to execute the corresponding process implemented by the network device in each method of the embodiment of the present application.
  • the computer program instructions cause the computer to execute the corresponding process implemented by the network device in each method of the embodiment of the present application.
  • the computer program product can be applied to the mobile terminal/terminal in the embodiment of the present application, and the computer program instructions cause the computer to execute the corresponding process implemented by the mobile terminal/terminal in each method of the embodiment of the present application, for the sake of brevity , I won’t repeat it here.
  • the embodiment of the present application also provides a computer program.
  • the computer program can be applied to the network device in the embodiment of the present application.
  • the computer program runs on the computer, it causes the computer to execute the corresponding process implemented by the network device in each method of the embodiment of the present application.
  • I won’t repeat it here.
  • the computer program can be applied to the mobile terminal/terminal in the embodiments of the present application.
  • the computer program runs on the computer, the computer can execute the corresponding methods implemented by the mobile terminal/terminal in the various methods of the embodiments of the present application. For the sake of brevity, the process will not be repeated here.
  • the disclosed system, device, and method can be implemented in other ways.
  • the device embodiments described above are merely illustrative.
  • the division of the units is only a logical function division, and there may be other divisions in actual implementation, for example, multiple units or components may be combined or It can be integrated into another system, or some features can be ignored or not implemented.
  • the displayed or discussed mutual coupling or direct coupling or communication connection may be indirect coupling or communication connection through some interfaces, devices or units, and may be in electrical, mechanical or other forms.
  • the units described as separate components may or may not be physically separate, and the components displayed as units may or may not be physical units, that is, they may be located in one place, or they may be distributed on multiple network units. Some or all of the units may be selected according to actual needs to achieve the objectives of the solutions of the embodiments.
  • the functional units in the various embodiments of the present application may be integrated into one processing unit, or each unit may exist alone physically, or two or more units may be integrated into one unit.
  • the function is implemented in the form of a software functional unit and sold or used as an independent product, it can be stored in a computer readable storage medium.
  • the technical solution of the present application essentially or the part that contributes to the existing technology or the part of the technical solution can be embodied in the form of a software product, and the computer software product is stored in a storage medium, including Several instructions are used to make a computer device (which may be a personal computer, a server, or a network device, etc.) execute all or part of the steps of the methods described in the various embodiments of the present application.
  • the aforementioned storage media include: U disk, mobile hard disk, read-only memory (Read-Only Memory,) ROM, random access memory (Random Access Memory, RAM), magnetic disk or optical disk and other media that can store program code .

Landscapes

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

Abstract

本申请实施例提供一种确定终端策略行为的方法及装置、网络设备，该方法包括：第一网元获取以下至少一种信息：终端发送的第一信息、策略控制功能网元PCF发送的第二信息、会话管理功能网元SMF发送的第三信息、应用服务器发送的第四信息；所述第一网元根据所述至少一种信息，确定终端执行的终端策略行为。

Description

一种确定终端策略行为的方法及装置、网络设备 技术领域
本申请实施例涉及移动通信技术领域，具体涉及一种确定终端策略行为的方法及装置、网络设备。
背景技术
终端在使用UE路由选择策略(UE Route Selection Policy，URSP)时，可能会没有选择到最优的URSP规则(URSP rule)，导致出现一些终端的“非期望行为”，而网络侧对此无从知晓，进而无法对URSP配置进行优化。
发明内容
本申请实施例提供一种确定终端策略行为的方法及装置、网络设备。
本申请实施例提供的确定终端策略行为的方法，包括：
第一网元获取以下至少一种信息：终端发送的第一信息、策略控制功能网元(Policy Control Function，PCF)发送的第二信息、会话管理功能网元(Session Management Function，SMF)发送的第三信息、应用服务器发送的第四信息；
所述第一网元根据所述至少一种信息，确定终端执行的终端策略行为。
本申请实施例提供的确定终端策略行为的装置，应用于第一网元，所述装置包括：
获取单元，用于获取以下至少一种信息：终端发送的第一信息、PCF发送的第二信息、SMF发送的第三信息、应用服务器发送的第四信息；
确定单元，用于根据所述至少一种信息，确定终端执行的终端策略行为。
本申请实施例提供的网络设备，包括处理器和存储器。该存储器用于存储计算机程序，该处理器用于调用并运行该存储器中存储的计算机程序，执行上述的确定终端策略行为的方法。
本申请实施例提供的芯片，用于实现上述的确定终端策略行为的方法。
具体地，该芯片包括：处理器，用于从存储器中调用并运行计算机程序，使得安装有该芯片的设备执行上述的确定终端策略行为的方法。
本申请实施例提供的计算机可读存储介质，用于存储计算机程序，该计算机程序使得计算机执行上述的确定终端策略行为的方法。
本申请实施例提供的计算机程序产品，包括计算机程序指令，该计算机程序指令使得计算机执行上述的确定终端策略行为的方法。
本申请实施例提供的计算机程序，当其在计算机上运行时，使得计算机执行上述的确定终端策略行为的方法。
通过上述技术方案，第一网元根据终端发送的第一信息、PCF发送的第二信息、SMF发送的第三信息以及应用服务器发送的第四信息中的至少之一，确定终端执行的终端策略行为，进而可以根据终端策略行为的执行情况对URSP配置进行优化。
附图说明
此处所说明的附图用来提供对本申请的进一步理解，构成本申请的一部分，本申请的示意性实施例及其说明用于解释本申请，并不构成对本申请的不当限定。在附图中：
图1是本申请实施例提供的一种通信系统架构的示意性图；
图2为本申请实施例提供的5G架构图；
图3为本申请实施例提供的UCU流程图；
图4为本申请实施例提供的应用数据流绑定到PDU会话的示意图；
图5为本申请实施例提供的PDU会话建立被拒绝和再次尝试PDU会话建立的流程图；
图6为本申请实施例提供的确定终端策略行为的方法的流程示意图一；
图7为本申请实施例提供的确定终端策略行为的方法的流程示意图二；
图8为本申请实施例提供的确定终端策略行为的方法的流程示意图三；
图9为本申请实施例提供的确定终端策略行为的装置的结构组成示意图；
图10是本申请实施例提供的一种通信设备示意性结构图；
图11是本申请实施例的芯片的示意性结构图；
图12是本申请实施例提供的一种通信系统的示意性框图。
具体实施方式
下面将结合本申请实施例中的附图，对本申请实施例中的技术方案进行描述，显然，所描述的实施例是本申请一部分实施例，而不是全部的实施例。基于本申请中的实施例，本领域普通技术人员在没有做出创造性劳动前提下所获得的所有其他实施例，都属于本申请保护的范围。
本申请实施例的技术方案可以应用于各种通信系统，例如：长期演进(Long Term Evolution，LTE)系统、LTE频分双工(Frequency Division Duplex，FDD)系统、LTE时分双工(Time Division Duplex，TDD)、系统、5G通信系统或未来的通信系统等。
示例性的，本申请实施例应用的通信系统100如图1所示。该通信系统100可以包括网络设备110，网络设备110可以是与终端120(或称为通信终端、终端)通信的设备。网络设备110可以为特定的地理区域提供通信覆盖，并且可以与位于该覆盖区域内的终端进行通信。可选地，该网络设备110可以是LTE系统中的演进型基站(Evolutional Node B，eNB或eNodeB)，或者是云无线接入网络(Cloud Radio Access Network，CRAN)中的无线控制器，或者该网络设备可以为移动交换中心、中继站、接入点、车载设备、可穿戴设备、集线器、交换机、网桥、路由器、5G网络中的网络侧设备或者未来通信系统中的网络设备等。
该通信系统100还包括位于网络设备110覆盖范围内的至少一个终端120。作为在此使用的“终端”包括但不限于经由有线线路连接，如经由公共交换电话网络(Public Switched Telephone Networks，PSTN)、数字用户线路(Digital Subscriber Line，DSL)、数字电缆、直接电缆连接；和/或另一数据连接/网络；和/或经由无线接口，如，针对蜂窝网络、无线局域网(Wireless Local Area Network，WLAN)、诸如DVB-H网络的数字电视网络、卫星网络、AM-FM广播发送器；和/或另一终端的被设置成接收/发送通信信号的装置；和/或物联网(Internet of Things，IoT)设备。被设置成通过无线接口通信的终端可以被称为“无线通信终端”、“无线终端”或“移动终端”。移动终端的示例包括但不限于卫星或蜂窝电话；可以组合蜂窝无线电电话与数据处理、传真以及数据通信能力的个人通信系统(Personal Communications System，PCS)终端；可以包括无线电电 话、寻呼机、因特网/内联网接入、Web浏览器、记事簿、日历以及/或全球定位系统(Global Positioning System，GPS)接收器的PDA；以及常规膝上型和/或掌上型接收器或包括无线电电话收发器的其它电子装置。终端可以指接入终端、用户设备(User Equipment，UE)、用户单元、用户站、移动站、移动台、远方站、远程终端、移动设备、用户终端、终端、无线通信设备、用户代理或用户装置。接入终端可以是蜂窝电话、无绳电话、会话启动协议(Session Initiation Protocol，SIP)电话、无线本地环路(Wireless Local Loop，WLL)站、个人数字处理(Personal Digital Assistant，PDA)、具有无线通信功能的手持设备、计算设备或连接到无线调制解调器的其它处理设备、车载设备、可穿戴设备、5G网络中的终端或者未来演进的PLMN中的终端等。
可选地，终端120之间可以进行终端直连(Device to Device，D2D)通信。
可选地，5G通信系统或5G网络还可以称为新无线(New Radio，NR)系统或NR网络。
图1示例性地示出了一个网络设备和两个终端，可选地，该通信系统100可以包括多个网络设备并且每个网络设备的覆盖范围内可以包括其它数量的终端，本申请实施例对此不做限定。
可选地，该通信系统100还可以包括网络控制器、移动管理实体等其他网络实体，本申请实施例对此不作限定。
应理解，本申请实施例中网络/系统中具有通信功能的设备可称为通信设备。以图1示出的通信系统100为例，通信设备可包括具有通信功能的网络设备110和终端120，网络设备110和终端120可以为上文所述的具体设备，此处不再赘述；通信设备还可包括通信系统100中的其他设备，例如网络控制器、移动管理实体等其他网络实体，本申请实施例中对此不做限定。
应理解，本文中术语“系统”和“网络”在本文中常被可互换使用。本文中术语“和/或”，仅仅是一种描述关联对象的关联关系，表示可以存在三种关系，例如，A和/或B，可以表示：单独存在A，同时存在A和B，单独存在B这三种情况。另外，本文中字符“/”，一般表示前后关联对象是一种“或”的关系。
为便于理解本申请实施例的技术方案，以下对本申请实施例相关的技术方案进行说明。
Figure PCTCN2020087472-appb-000001
基于5G架构的UE策略配置方法
5G架构如图2所示，5G架构中涉及到的设备包括：终端、无线接入网(Radio Access Network，RAN)、用户平面功能网元(User Plane Function，UPF)、数据网络(Data Network，DN)、接入和移动性管理功能网元(Access and Mobility Management Function，AMF)、会话管理功能网元(Session Management Function，SMF)、策略控制功能网元(Policy Control Function，PCF)、应用功能网元(Application Function，AF)、鉴权服务器功能网元(Authentication Server Function，AUSF)、统一数据管理网元(Unified Data Management，UDM)。
如图2所示，与策略相关的网元主要是PCF、AMF、SMF、RAN、终端。其中，SMF主要是负责与会话相关的策略的执行，AMF主要负责与接入和终端策略相关的策略执行，两个网元(AMF和SMF)上的策略下发、更新全都由PCF来管控。
具体到终端策略，PCF与终端之间通过容器(Container)来监护终端策略相关的信息，包括终端策略的内容、终端策略标识等。容器在上行方向上由终端通过非接入层(Non Access Stratum，NAS)消息发送给AMF，并由AMF继续透传(不感知或不修改)给PCF，下行方向与之相反，由PCF将容器发给AMF，AMF进而通过NAS消息透传给终端。
基于上述5G架构，终端策略通过UE配置更新(UE Configuration Update，UCU)流程实现，如图3所示，该UCU流程包括以下步骤：
步骤301：PCF决定更新终端策略。
步骤302：PCF将要更新的终端策略放在一个容器里发送给AMF。
步骤303：AMF使用NAS消息将容器直接转发给终端。
步骤304：终端向AMF发送策略配置结果(Result of the delivery of UE policies)。
Figure PCTCN2020087472-appb-000002
终端策略的使用
终端策略包括接入网发现选择策略(Access Network Discovery and Selection Policy，ANDSP)、URSP等，其中，URSP决定了应用数据与协议数据单元(Protocol Data Unit，PDU)会话的绑定关系，也决定了终端需要建立什么样的PDU会话来满足这种绑定关系。如图4所示，不同的应用数据流根据URSP规则绑定到不同的PDU会话上，数据流-a根据规则-1绑定到PDU会话-1上，数据流-b根据规则-2绑定到PDU会话-2上，数据流-c根据规则-3绑定到PDU会话-3上。
PDU会话关联的会话属性参数包括：单网络切片选择辅助信息(Single-Network Slice Selection Assistant Information，S-NSSAI)、数据网络名(Data Network Name，DNN)、PDU会话标识(PDU Session id)、PDU会话类型(PDU Session Type)、业务和会话连续模式(Service and Session Continuity Mode，SSC Mode)。
终端可以在PDU会话建立请求消息中携带上述会话属性参数，如果有些会话属性参数没有携带，网络侧可以为其填补。比如，PDU会话建立请求消息中携带PDU Session id＝1，DNN-1，PDU Sessiontype＝IPv4，SMF接受该请求，并填补如下其他属性参数：S-NSSAI＝1，SSC Mode＝1。
需要说明的是，这种情况下，终端和/或网络侧均可以保存建立成功的PDU会话的会话属性参数，以及哪些会话属性参数是终端请求的，哪些会话属性参数是网络填补的。
参照如下表1和表2，URSP包含多个URSP规则，每一个URSP规则由业务描述符(Traffic Descriptor)和一组路由选择符(Route Selection Descriptor，RSD)组成。URSP中的业务描述符用于描述一种具体的业务，比如微博业务可以用IP地址1～9的范围来描述，再比如IMS业务可以用IMS DNN来描述。然后，一个业务描述符下面可以有一个或多个RSD。一个RSD中的S-NSSAI的值和DNN的值可以是一个或多个，其他参数只包含一个值。因此，每一个RSD可以对应一个或多个参数值组合，每个参数值组合为一套PDU会话的特征，业务描述符对应的业务数据可以在RSD的某一个参数值组合对应的PDU会话中进行传输。当有业务描述符描述的应用数据流出现时，终端可以根据对应的RSD选取一个参数值组合，发起PDU会话建立请求。
终端每次发起PDU会话建立请求时，都在PDU会话建立请求消息中添加一套会话属性参数，即为某个URSP规则中的RSD表中的参数值组合。
Figure PCTCN2020087472-appb-000003
表1：URSP规则中的业务描述符和对应的RSD列表
Figure PCTCN2020087472-appb-000004
表2：RSD
如图4所述，终端基于URSP规则将应用数据流关联到相应的PDU会话上进行传输，机制如下：
当应用层出现数据时，终端使用URSP中的URSP规则来查看该应用数据的特征是 否匹配到了URSP规则中的某一个规则的Traffic Descriptor上，查看的顺序按照URSP规则中的优先级(Precedence)来决定，即终端基于优先级的顺序依次查看匹配情况，当匹配到一个URSP规则时，用该URSP规则下的RSD列表进行PDU会话的绑定。
当有URSP规则匹配上时，
1)终端首先查找当前已经建立的PDU会话是否有满足在该匹配的URSP规则下的有效RSD，有的话则将匹配的应用数据绑定到该PDU会话上进行传输，否则：
2)按照有效RSD中的Precedence顺序来尝试建立PDU会话，这里优先使用优先级高的RSD建立PDU会话，如果该RSD中的某个参数为一个或多个取值，则终端选用其中一个与其他参数一起组合建立PDU会话：
-若PDU会话建立成功，则终端将该应用数据绑定到该PDU会话进行传输；
-若PDU会话建立不成功，则终端基于该RSD中的其他参数值组合或者使用次优先级的RSD中的参数值组合再次尝试PDU会话建立。
若根据该匹配的URSP规则中都不能找到一个合适的PDU会话进行绑定，则终端根据Precedence顺序查找次优先的URSP规则中的Traffic Descriptor是否能够匹配该应用数据的特征，当匹配上时，重复上述1)和2)的过程。
上述为应用数据寻找或建立合适的PDU会话的过程称之为“评估(evaluation)过程”。URSP规则中的RSD只有满足以下条件才认为是有效RSD(这里，有效RSD用来执行上述的evaluation过程)：
-如果RSD中有S-NSSAI，S-NSSAI必须属于Allowed NSSAI(非漫游)或者Mapping of Allowed NSSAI(漫游)中的一个；
-如果RSD中有DNN且为LADN DNN，则终端必须在该LADN对应的有效区域内；
-如果RSD中有Access Type Prefrence并且设置成了Multi-Access，则终端必须支持ATSSS功能；
-如果RSD中有Timer Window和Location Criteria，则终端必须满足要求的时间和地点条件。
对于不满足以上条件的RSD，终端不会使用该RSD进行应用数据的绑定或PDU会话的建立。
根据上述evaluation过程的机制，终端可以在发起PDU会话建立被拒绝后，根据RSD中的参数再次尝试PDU会话建立。如图5所示，PDU会话建立被拒绝和再次尝试PDU会话建立的流程包括以下步骤：
步骤501：终端向SMF发送PDU会话建立请求消息。
这里，PDU会话建立请求消息中携带以下至少一种会话属性参数：DNN、S-NSSAI、PDU Session Type、SSC Mode、PDU Session ID。
步骤502：SMF向终端发送PDU会话建立请求回复消息，携带拒绝原因值。
这里，若网络侧拒绝会话请求，会PDU会话建立请求回复消息中携带拒绝原因值。
步骤503：终端根据URSP规则中的RSD，调整参数值组合再次发起PDU会话建立。
目前，URSP机制有如下几个特点和问题：
1)URSP规则中的参数，比如TrafficDescriptor中的Applicaton Descriptor参数，可能无法被终端识别。原因比如有些参数需要运营商、终端公司之间的协同，不是运营商单方面可以确定的。根据evaluation过程，如果终端无法识别一个URSP规则里的参数，则会自动忽略掉该URSP规则。但是终端不会告知网络侧哪些URSP规则或里面的RSD被忽略了。这就造成网络侧下发的某些URSP规则可能永远都不会被终端执行，但是网络侧并不知道该情况。
2)当终端接收到新的URSP规则时(比如终端通过UCU过程接收到新的URSP规则)，终端会重新评估新的URSP规则，根据新的URSP规则确定应用数据与PDU会话之间的新的绑定关系。但是，终端何时评估这个新的URSP规则，以及何时执行新的绑定关系都是终端自我实现的。网络为终端更新了URSP规则后，不能确定何时终端会执行新的URSP规则来绑定应用数据流。
3)对于每一个应用数据流，终端通过evaluation过程最终会选择一个URSP规则下的RSD对应的PDU会话进行数据传输。然后，在后续的相当一段时间内不会再改变这种绑定关系。终端为特定的应用数据流使用的URSP规则以及RSD可能不是优先级最高的，但网络侧并不能确定终端为应用数据流使用了哪个URSP规则和RSD。
综上所述，虽然不违反evaluation机制，但可以认为是一种终端的“非期望行为”，因为终端并没有按照网络侧下发的最高优先级或最期望的URSP规则执行evaluation过程。网络侧无法确定是否有这种“非期望行为”，因此，需要一种机制让网络侧确定终端正在执行的“终端策略行为”。为此，提出了本申请实施例的以下技术方案，需要说明的是，本申请实施例的技术方案可以应用于5G网络，不局限于此，本申请实施例的技术方案也可以应用于4G网络或未来的新型网络。
图6为本申请实施例提供的确定终端策略行为的方法的流程示意图一，如图6所示，所述确定终端策略行为的方法包括以下步骤：
步骤601：第一网元获取以下至少一种信息：终端发送的第一信息、PCF发送的第二信息、SMF发送的第三信息、应用服务器发送的第四信息。
本申请实施例中，所述第一网元为具有分析功能的网元。在一可选方式中，所述第一网元为网络数据分析功能网元(Network Data Analysis Function，NWDAF)。
本申请实施例中，所说第一网元获取的信息包括以下至少之一：终端发送的第一信息、PCF发送的第二信息、SMF发送的第三信息、应用服务器发送的第四信息。以下对这些信息进行详细说明。
●终端发送的第一信息
在一可选方式中，所述终端发送的第一信息包括以下至少之一：
第一指示信息，所述第一指示信息用于指示以下至少之一：终端正在使用的URSP规则、终端正在使用的URSP规则的Traffic Descriptor、终端正在使用的URSP规则中的RSD；这里，终端发送Traffic Descriptor时，可以发送Traffic Descriptor中的全部参数，或者也可以只发送Traffic Descriptor中的部分参数；
第二指示信息，所述第二指示信息用于指示以下至少之一：终端是否已使用(或已执行)更新的URSP规则、终端已使用(或已执行)的更新的URSP规则(即哪些更新的URSP规则已经被终端使用或执行)；
第三指示信息，所述第三指示信息用于指示以下至少之一：终端为特定应用传输数据建立的PDU会话、终端建立的PDU会话对应的URSP规则、终端建立的PDU会话对应的URSP规则的Traffic Descriptor、终端建立的PDU会话对应的URSP规则中的RSD。
在一可选方式中，所述第一信息由所述终端通过控制面消息发送给所述第一网元。进一步，所述控制面消息为NAS消息，所述第一信息携带在所述NAS消息中；或者，所述第一信息携带在所述NAS消息中的容器中。
在另一可选方式中，所述第一信息由所述终端通过用户面消息发送给所述第一网元。具体地，所述第一信息由所述终端通过用户面消息发送给用户面网元，并由所述用户面网元转发给所述第一网元。可选地，所述用户面消息的包头中携带第一标识，所述第一标识用于指示所述用户面网元将所述用户面消息转发给所述第一网元。这 里，可选地，所述用户面消息的包头为SDAP包头或GTP-U包头。可选地，所述用户面网元为UPF。
上述方案中，所述终端发送的第一信息也可以称为策略执行信息。
在一可选方式中，终端可以向网络侧发送第七指示信息，所述第七指示信息用于指示网络侧所述终端请求上报所述第一信息或具备上报所述第一信息的能力。可选地，所述第七指示信息还用于指示所述终端能够或请求上报的所述第一信息包含的内容有哪些。所述第七指示信息可以通过上行NAS消息发送给网络侧，比如终端将所述第七指示信息包含在注册请求消息中发送给网络侧。
在一可选方式中，网络侧向终端发送第八指示信息，所述第八指示信息用于指示要求或允许所述终端上报所述第一信息。进一步，可选地，所述第八指示信息还用于指示要求或允许所述终端上报的所述第一信息包含的内容有哪些。这里，可选地，网络侧可以是所述第一网元。所述第八指示信息可以通过下行NAS消息发送给终端，
比如网络侧将所述第八指示信息添加在注册回复消息中发送给终端。
●PCF发送的第二信息
在一可选方式中，所述第二信息包括第四指示信息，所述第四指示信息用于指示以下至少之一：
给终端下发的URSP规则、给终端下发的URSP规则的Traffic descriptor、给终端下发的URSP规则与应用之间的映射关系、给终端下发的URSP规则的Traffic descriptor与应用之间的映射关系。
●SMF发送的第三信息
在一可选方式中，所述第三信息包括第五指示信息，所述第五指示信息用于指示以下至少之一：
终端已建立的PDU会话、终端已建立的PDU会话对应的会话属性参数、终端已建立的PDU会话对应的会话属性参数中属于终端请求的会话属性参数(即终端已建立的PDU会话对应的会话属性参数中哪些会话属性参数是终端请求的)、终端已建立的PDU会话对应的会话属性参数中属于网络添加的会话属性参数(即终端已建立的PDU会话对应的会话属性参数中哪些会话属性参数是网络添加的)、终端已建立的PDU会话的地址信息。
这里，可选地，PDU会话的地址信息是指PDU会话的IP地址信息。
●应用服务器发送的第四信息
在一可选方式中，所述第四信息包括第六指示信息，所述第六指示信息用于指示以下至少之一：
终端的地址信息、终端的应用数据流使用的PDU会话、终端的应用数据流对应的应用标识、终端的应用数据流对应的Traffic descriptor参数。
这里，可选地，终端的地址信息是指终端的IP地址信息。
步骤602：所述第一网元根据所述至少一种信息，确定终端执行的终端策略行为。
本申请实施例中，所述第一网元可以对所述至少一种信息进行分析，进而确定终端执行的终端策略行为。具体地，所述终端策略行为包括以下至少之一：
终端正在使用的UE路由选择策略URSP规则；
终端正在使用的URSP规则中的路由选择符RSD；
终端为特定应用传输数据使用的URSP规则；
终端为特定应用传输数据使用的URSP规则中的RSD；
终端为特定应用传输数据使用的协议数据单元PDU会话；
终端是否已使用更新的URSP规则；
终端已使用的更新的URSP规则。
这里，特定应用可以指某个特定应用标识(Application Id)对应的应用。
以下结合具体应用示例对本申请实施例的技术方案进行举例说明。
示例一
第一网元接收终端发送的第一信息(即策略执行信息)，第一网元基于所述第一信息确定终端正在执行的终端策略行为。
进一步，可选地，所述第一网元还接收以下至少之一：PCF发送的第二信息、SMF发送的第三信息、应用服务器发送的第四信息。第一网元基于第一信息，以及第二信息、第三信息和第四信息中的至少之一，确定终端正在执行的终端策略行为。
需要说明的是，所述第一信息，第二信息，第三信息和第四信息的内容可以参照前述方案的描述。
参照图7，图7以第一网元是NWDAF为例，包括以下步骤：
步骤701：NWDAF接收终端发送的第一信息。
步骤702：NWDAF接收PCF发送的第二信息。
步骤703：NWDAF接收SMF发送的第三信息。
步骤704：NWDAF接收应用服务器发送的第四信息。
步骤705：NWDAF根据获得的信息确定终端执行的终端策略行为。
需要说明的是，步骤702至步骤704是可选地。以下结合具体例子进行说明。
例子1：NWDAF获得以下信息：
-来自终端的第一信息：终端正在使用URSP-Rule2中的RSD-3；
-来自PCF的第二信息：为终端用户下发了
URSP-Rule1(RSD-1)，对应Application Id-1、Application Id-2；
URSP-Rule2(RSD-1/2/3)，对应；Application Id-2；
URSP-Rule3(RSD-1/2)，对应Application Id-3。
-来自应用服务器的第四信息：请求检测Application Id-2的数据在哪一个网络切片上进行传输(或者说请求检测Application Id-2的数据在哪一个S-NSSAI对应的网络切片上进行传输)。
NWDAF结合上述信息可以确定：终端正在使用URSP-Rule2中的RSD-3为Application id-2的应用数据进行数据传输，而RSD-3里面的S-NSSAI参数是S-NSSAI-a，因此Application Id-2的数据在S-NSSAI-a对应的网络切片上进行传输。
例子2：NWDAF获得以下信息：
-来自终端的第一信息：终端正在使用URSP-Rule2中的RSD-3；
-来自PCF的第二信息：为终端用户下发了
URSP-Rule1(RSD-1)，对应Application Id-1、Application Id-2；
URSP-Rule2(RSD-1/2/3)，对应；Application Id-2；
URSP-Rule3(RSD-1/2)，对应Application Id-3。
-来自SMF的第三信息：PDU Session-1和会话属性参数(含终端请求的会话属性参数)的对应关系。
NWDAF结合上述信息可以确定：Application Id-1、2、3分别在哪一个PDU会话上进行传输。进一步，NWDAF可以将确定的结果发送给其他网元(如网管系统)进行统计存储。
需要说明的是，NWDAF并非唯一一个确定终端策略行为的网元。在一可选方式中，当PCF不提供URSP规则和应用之间的映射关系，NWDAF可以将当前终端正在使用的URSP规则和对应的RSD告知给PCF，由PCF来确定终端策略行为。
示例二
第一网元接收以下至少之一：PCF发送的第二信息、SMF发送的第三信息、应用服务器发送的第四信息。第一网元基于第二信息、第三信息和第四信息中的至少之一，确定终端正在执行的终端策略行为。
需要说明的是，所述第二信息，第三信息和第四信息的内容可以参照前述方案的描述。
参照图8，图8以第一网元是NWDAF为例，包括以下步骤：
步骤801：NWDAF接收PCF发送的第二信息。
步骤802：NWDAF接收SMF发送的第三信息。
步骤803：NWDAF接收应用服务器发送的第四信息。
步骤804：NWDAF根据获得的信息确定终端执行的终端策略行为。
需要说明的是，步骤801至步骤803中可以选择其中部分步骤或全部步骤执行。以下结合具体例子进行说明。
例子3：NWDAF获得以下信息：
-来自SMF的第三信息：PDU Session-1对应IP地址1，PDU Session-2对应IP地址2，且PDU Session-1对应的终端请求的会话属性参数为S-NSSAI-1，DNN-1。
-来自PCF的第二信息：为终端下发了
URSP-Rule1(RSD-1由S-NSSAI-1和DNN-1组成)，对应Application Id-1、Application Id-2；
URSP-Rule2(RSD-1/2/3均不包含S-NSSAI-1)，对应Application Id-2；
URSP-Rule3(RSD-1/2)，对应Application Id-3。
-来自应用服务器的第四信息：终端的IP地址是IP地址1*(对应IP地址1)、Application Id-2。
需要说明的是，应用服务器提供的终端的IP地址可能是经过NAT转换的公网IP地址，而PDU会话对应的IP地址是私网IP地址，两者之间的转换关系可以用网络侧控制，也就是说应用服务器通知的终端的IP地址是IP地址1*，运营商网络可以知道IP地址1*对应的是IP地址1。
NWDAF结合上述信息可以确定：终端正在使用PDU Session-1传输应用数据流，且终端正在使用URSP-Rule1(RSD1)传输应用数据流。
例子4：NWDAF获得以下信息：
-来自SMF的第三信息：终端有两个PDU Session，分别为PDU Session-1和PDU Session-2，其中，PDU Session-1对应的终端请求的会话属性参数为S-NSSAI-1，DNN-1，PDU Session-2对应的终端请求的会话属性参数为S-NSSAI-2，DNN-2。
-来自PCF的第二信息：为终端用户下发了
URSP-Rule1(RSD-1)，规则中的Traffic descriptor＝IP地址x；
URSP-Rule2(RSD-1/2/3，其中仅RSD-2由S-NSSAI-2和DNN-2组成)，规则中的Traffic descriptor＝IP地址y；
URSP-Rule3(RSD-1/2)，规则中的Traffic descriptor＝Application descriptor-3。
-来自应用服务器的第四信息：应用对应的Traffic Descriptor是IP地址y。
NWDAF结合上述信息可以确定：终端正在使用URSP-Rule2中的RSD-2，且正在使用PDU Session-2传输应用数据。
例子5：NWDAF获得以下信息：
-来自SMF的第三信息：终端有两个PDU Session，分别为PDU Session-1和PDU Session-2，其中，PDU Session-1的地址信息为IP地址1，会话属性参数为S-NSSAI-1， DNN-1；PDU Session-2的地址信息为IP地址2，会话属性参数为S-NSSAI-2，DNN-2。
-来自PCF的第二信息：为终端用户下发了
URSP-Rule1(RSD-1)，RSD-1由S-NSSAI-1和DNN-1组成，规则中的Traffic descriptor为：Connection Capabilities＝"internet"；
URSP-Rule2(RSD-2)，RSD-2由S-NSSAI-2和DNN-2组成，规则中的Traffic descriptor为：Connection Capabilities＝"internet"；
URSP-Rule3(RSD-3)，规则中的Traffic descriptor为Connection Capabilities＝"IMS"。
-来自应用服务器的第四信息：终端的地址信息为IP地址2，应用对应的Traffic Descriptor是Connection Capabilities＝"internet"。
NWDAF结合上述信息可以确定：终端正在使用URSP-Rule2中的RSD-2，且正在使用PDU Session-2传输应用数据。
本例子中，NWDAF根据从应用服务器获得的终端的地址信息和Traffic descriptor，以及从SMF获得的PDU会话的地址信息和PDU会话的会话属性参数，确定当前应用所使用的Traffic descriptor以及对应的PDU会话属性参数，从而与从PCF获得的URSP规则(包括Traffic descriptor及对应的PDU会话属性参数)进行比对，确定终端正在使用的URSP规则。或者，NWDAF根据从应用服务器获得的终端的地址信息和Traffic descriptor，使用Traffic descriptor与从PCF获得的URSP规则进行比对，确定终端可能使用的PDU会话的会话属性参数，并根据从SMF获得的地址信息所对应的PDU会话的会话属性参数，确定终端正在使用的URSP规则。
例子6：
NWDAF获得以下信息：
-来自SMF的第三信息：终端有两个PDU Session，分别为PDU Session-1和PDU Session-2，其中，PDU Session-1的地址信息为IP地址1，会话属性参数为S-NSSAI-1，DNN-1；PDU Session-2的地址信息为IP地址2，会话属性参数为S-NSSAI-2，DNN-2。
-来自PCF的第二信息：为终端用户下发了
URSP-Rule1(RSD-1)，RSD-1由S-NSSAI-1和DNN-1组成，规则中的Traffic descriptor为：Application descriptor＝"youtube service"；
URSP-Rule2(RSD-2)，RSD-2由S-NSSAI-2和DNN-2组成，规则中的Traffic descriptor为：Application descriptor＝"youtube service"；
URSP-Rule3(RSD-3)，规则中的Traffic descriptor为Application descriptor＝"google service"。
-来自应用服务器的第四信息：终端的地址信息为IP地址2，应用标识为Application Id-1。
此外，NWDAF可以从PCF得到或者基于NWDAF上的预配信息得到：Application Id-1对应的Traffic Descriptor是Application descriptor＝"youtube service"。这里，需要说明是，应用标识(Application Id)与业务描述符(Traffic Descriptor)之间的映射关系可以由PCF获得，也可以在NWDAF上预配。
NWDAF结合上述信息可以确定：终端正在使用URSP-Rule2中的RSD-2，且正在使用PDU Session-2传输应用数据。
需要说明的是，本申请上述方案中的应用标识(Application Id)是核心网和应用服务器之间指代特定应用使用的，应用描述符(Application descriptor)是终端识别特定应用使用的，两者的格式和取值可以是不同的，但可以有对应关系，即Application Id与Application descriptor之间具有对应关系。
本申请实施例的技术方案，提出了一种机制能够让网络侧判断终端执行的终端策略 行为是否符合期望的方式，从而让网络侧判断终端执行的URSP规则是否是自己期望的。为此，需要通过终端、核心网网元(如PCF、SMF)、应用服务器上报相关信息，让网络侧的分析网元进行分析得到相应的结果(如终端是否在使用优先级最高的URSP规则)，并在需要的情况下执行策略的调整和更新。
图9为本申请实施例提供的确定终端策略行为的装置的结构组成示意图，应用于第一网元，如图9所示，所述确定终端策略行为的装置包括：
获取单元901，用于获取以下至少一种信息：终端发送的第一信息、PCF发送的第二信息、SMF发送的第三信息、应用服务器发送的第四信息；
确定单元902，用于根据所述至少一种信息，确定终端执行的终端策略行为。
在一可选方式中，所述终端策略行为包括以下至少之一：
终端正在使用的URSP规则；
终端正在使用的URSP规则中的RSD；
终端为特定应用传输数据使用的URSP规则；
终端为特定应用传输数据使用的URSP规则中的RSD；
终端为特定应用传输数据使用的PDU会话；
终端是否已使用更新的URSP规则；
终端已使用的更新的URSP规则。
在一可选方式中，所述第一信息包括以下至少之一：
第一指示信息，所述第一指示信息用于指示以下至少之一：终端正在使用的URSP规则、终端正在使用的URSP规则的Traffic Descriptor、终端正在使用的URSP规则中的RSD；
第二指示信息，所述第二指示信息用于指示以下至少之一：终端是否已使用更新的URSP规则、终端已使用的更新的URSP规则；
第三指示信息，所述第三指示信息用于指示以下至少之一：终端为特定应用传输数据建立的PDU会话、终端建立的PDU会话对应的URSP规则、终端建立的PDU会话对应的URSP规则的Traffic Descriptor、终端建立的PDU会话对应的URSP规则中的RSD。
在一可选方式中，述第一信息由所述终端通过控制面消息发送给所述第一网元。
在一可选方式中，所述控制面消息为NAS消息，
所述第一信息携带在所述NAS消息中；或者，
所述第一信息携带在所述NAS消息中的容器中。
在一可选方式中，所述第一信息由所述终端通过用户面消息发送给所述第一网元。
在一可选方式中，所述第一信息由所述终端通过用户面消息发送给用户面网元，并由所述用户面网元转发给所述第一网元。
在一可选方式中，所述用户面消息的包头中携带第一标识，所述第一标识用于指示所述用户面网元将所述用户面消息转发给所述第一网元。
在一可选方式中，所述第二信息包括第四指示信息，所述第四指示信息用于指示以下至少之一：
给终端下发的URSP规则、给终端下发的URSP规则的Traffic descriptor、给终端下发的URSP规则与应用之间的映射关系、给终端下发的URSP规则的Traffic descriptor与应用之间的映射关系。
在一可选方式中，所述第三信息包括第五指示信息，所述第五指示信息用于指示以下至少之一：
终端已建立的PDU会话、终端已建立的PDU会话对应的会话属性参数、终端已建立的PDU会话对应的会话属性参数中属于终端请求的会话属性参数、终端已建立的PDU会话对应的会话属性参数中属于网络添加的会话属性参数、终端已建立的PDU会话的地址信息。
在一可选方式中，所述第四信息包括第六指示信息，所述第六指示信息用于指示以下至少之一：
终端的地址信息、终端的应用数据流使用的PDU会话、终端的应用数据流对应的应用标识、终端的应用数据流对应的Traffic descriptor参数。
在一可选方式中，所述获取单元901，还用于接收终端发送的第七指示信息，所述第七指示信息用于指示网络侧所述终端请求上报所述第一信息或具备上报所述第一信息的能力。可选地，所述第七指示信息还用于指示所述终端能够或请求上报的所述第一信息包含的内容有哪些。所述第七指示信息可以通过上行NAS消息发送给网络侧，比如终端将所述第七指示信息包含在注册请求消息中发送给网络侧。
在一可选方式中，所述装置还包括：发送单元(图中未示出)，用于向终端发送第八指示信息，所述第八指示信息用于指示要求或允许所述终端上报所述第一信息。进一步，可选地，所述第八指示信息还用于指示要求或允许所述终端上报的所述第一信息包含的内容有哪些。这里，可选地，网络侧可以是所述第一网元。所述第八指示信息可以通过下行NAS消息发送给终端，比如网络侧将所述第八指示信息添加在注册回复消息中发送给终端。
本领域技术人员应当理解，本申请实施例的上述确定终端策略行为的装置的相关描述可以参照本申请实施例的确定终端策略行为的方法的相关描述进行理解。
图10是本申请实施例提供的一种通信设备1000示意性结构图。该通信设备可以是终端，也可以是网络设备(如上述方案中的第一网元)，图10所示的通信设备1000包括处理器1010，处理器1010可以从存储器中调用并运行计算机程序，以实现本申请实施例中的方法。
可选地，如图10所示，通信设备1000还可以包括存储器1020。其中，处理器1010可以从存储器1020中调用并运行计算机程序，以实现本申请实施例中的方法。
其中，存储器1020可以是独立于处理器1010的一个单独的器件，也可以集成在处理器1010中。
可选地，如图10所示，通信设备1000还可以包括收发器1030，处理器1010可以控制该收发器1030与其他设备进行通信，具体地，可以向其他设备发送信息或数据，或接收其他设备发送的信息或数据。
其中，收发器1030可以包括发射机和接收机。收发器1030还可以进一步包括天线，天线的数量可以为一个或多个。
可选地，该通信设备1000具体可为本申请实施例的网络设备，并且该通信设备1000可以实现本申请实施例的各个方法中由网络设备实现的相应流程，为了简洁，在此不再赘述。
可选地，该通信设备1000具体可为本申请实施例的移动终端/终端，并且该通信设备1000可以实现本申请实施例的各个方法中由移动终端/终端实现的相应流程，为了简洁，在此不再赘述。
图11是本申请实施例的芯片的示意性结构图。图11所示的芯片1100包括处理器1110，处理器1110可以从存储器中调用并运行计算机程序，以实现本申请实施例中的方法。
可选地，如图11所示，芯片1100还可以包括存储器1120。其中，处理器1110可 以从存储器1120中调用并运行计算机程序，以实现本申请实施例中的方法。
其中，存储器1120可以是独立于处理器1110的一个单独的器件，也可以集成在处理器1110中。
可选地，该芯片1100还可以包括输入接口1130。其中，处理器1110可以控制该输入接口1130与其他设备或芯片进行通信，具体地，可以获取其他设备或芯片发送的信息或数据。
可选地，该芯片1100还可以包括输出接口1140。其中，处理器1110可以控制该输出接口1140与其他设备或芯片进行通信，具体地，可以向其他设备或芯片输出信息或数据。
可选地，该芯片可应用于本申请实施例中的网络设备，并且该芯片可以实现本申请实施例的各个方法中由网络设备实现的相应流程，为了简洁，在此不再赘述。
可选地，该芯片可应用于本申请实施例中的移动终端/终端，并且该芯片可以实现本申请实施例的各个方法中由移动终端/终端实现的相应流程，为了简洁，在此不再赘述。
应理解，本申请实施例提到的芯片还可以称为系统级芯片，系统芯片，芯片系统或片上系统芯片等。
图12是本申请实施例提供的一种通信系统1200的示意性框图。如图12所示，该通信系统1200包括终端1210和网络设备1220。
其中，该终端1210可以用于实现上述方法中由终端实现的相应的功能，以及该网络设备1220可以用于实现上述方法中由网络设备实现的相应的功能为了简洁，在此不再赘述。
应理解，本申请实施例的处理器可能是一种集成电路芯片，具有信号的处理能力。在实现过程中，上述方法实施例的各步骤可以通过处理器中的硬件的集成逻辑电路或者软件形式的指令完成。上述的处理器可以是通用处理器、数字信号处理器(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可用，例如静态随机存取存储器(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)。应注意，本文描述的系统和方法的存储器旨在包 括但不限于这些和任意其它适合类型的存储器。
应理解，上述存储器为示例性但不是限制性说明，例如，本申请实施例中的存储器还可以是静态随机存取存储器(static RAM，SRAM)、动态随机存取存储器(dynamic RAM，DRAM)、同步动态随机存取存储器(synchronous DRAM，SDRAM)、双倍数据速率同步动态随机存取存储器(double data rate SDRAM，DDR SDRAM)、增强型同步动态随机存取存储器(enhanced SDRAM，ESDRAM)、同步连接动态随机存取存储器(synch link DRAM，SLDRAM)以及直接内存总线随机存取存储器(Direct Rambus RAM，DR RAM)等等。也就是说，本申请实施例中的存储器旨在包括但不限于这些和任意其它适合类型的存储器。
本申请实施例还提供了一种计算机可读存储介质，用于存储计算机程序。
可选的，该计算机可读存储介质可应用于本申请实施例中的网络设备，并且该计算机程序使得计算机执行本申请实施例的各个方法中由网络设备实现的相应流程，为了简洁，在此不再赘述。
可选地，该计算机可读存储介质可应用于本申请实施例中的移动终端/终端，并且该计算机程序使得计算机执行本申请实施例的各个方法中由移动终端/终端实现的相应流程，为了简洁，在此不再赘述。
本申请实施例还提供了一种计算机程序产品，包括计算机程序指令。
可选的，该计算机程序产品可应用于本申请实施例中的网络设备，并且该计算机程序指令使得计算机执行本申请实施例的各个方法中由网络设备实现的相应流程，为了简洁，在此不再赘述。
可选地，该计算机程序产品可应用于本申请实施例中的移动终端/终端，并且该计算机程序指令使得计算机执行本申请实施例的各个方法中由移动终端/终端实现的相应流程，为了简洁，在此不再赘述。
本申请实施例还提供了一种计算机程序。
可选的，该计算机程序可应用于本申请实施例中的网络设备，当该计算机程序在计算机上运行时，使得计算机执行本申请实施例的各个方法中由网络设备实现的相应流程，为了简洁，在此不再赘述。
可选地，该计算机程序可应用于本申请实施例中的移动终端/终端，当该计算机程序在计算机上运行时，使得计算机执行本申请实施例的各个方法中由移动终端/终端实现的相应流程，为了简洁，在此不再赘述。
本领域普通技术人员可以意识到，结合本文中所公开的实施例描述的各示例的单元及算法步骤，能够以电子硬件、或者计算机软件和电子硬件的结合来实现。这些功能究竟以硬件还是软件方式来执行，取决于技术方案的特定应用和设计约束条件。专业技术人员可以对每个特定的应用来使用不同方法来实现所描述的功能，但是这种实现不应认为超出本申请的范围。
所属领域的技术人员可以清楚地了解到，为描述的方便和简洁，上述描述的系统、装置和单元的具体工作过程，可以参考前述方法实施例中的对应过程，在此不再赘述。
在本申请所提供的几个实施例中，应该理解到，所揭露的系统、装置和方法，可以通过其它的方式实现。例如，以上所描述的装置实施例仅仅是示意性的，例如，所述单元的划分，仅仅为一种逻辑功能划分，实际实现时可以有另外的划分方式，例如多个单元或组件可以结合或者可以集成到另一个系统，或一些特征可以忽略，或不执行。另一点，所显示或讨论的相互之间的耦合或直接耦合或通信连接可以是通过一些接口，装置或单元的间接耦合或通信连接，可以是电性，机械或其它的形式。
所述作为分离部件说明的单元可以是或者也可以不是物理上分开的，作为单元显示 的部件可以是或者也可以不是物理单元，即可以位于一个地方，或者也可以分布到多个网络单元上。可以根据实际的需要选择其中的部分或者全部单元来实现本实施例方案的目的。
另外，在本申请各个实施例中的各功能单元可以集成在一个处理单元中，也可以是各个单元单独物理存在，也可以两个或两个以上单元集成在一个单元中。
所述功能如果以软件功能单元的形式实现并作为独立的产品销售或使用时，可以存储在一个计算机可读取存储介质中。基于这样的理解，本申请的技术方案本质上或者说对现有技术做出贡献的部分或者该技术方案的部分可以以软件产品的形式体现出来，该计算机软件产品存储在一个存储介质中，包括若干指令用以使得一台计算机设备(可以是个人计算机，服务器，或者网络设备等)执行本申请各个实施例所述方法的全部或部分步骤。而前述的存储介质包括：U盘、移动硬盘、只读存储器(Read-Only Memory，)ROM、随机存取存储器(Random Access Memory，RAM)、磁碟或者光盘等各种可以存储程序代码的介质。
以上所述，仅为本申请的具体实施方式，但本申请的保护范围并不局限于此，任何熟悉本技术领域的技术人员在本申请揭露的技术范围内，可轻易想到变化或替换，都应涵盖在本申请的保护范围之内。因此，本申请的保护范围应所述以权利要求的保护范围为准。

Claims (31)

  1. 一种确定终端策略行为的方法，所述方法包括：
    第一网元获取以下至少一种信息：终端发送的第一信息、策略控制功能网元PCF发送的第二信息、会话管理功能网元SMF发送的第三信息、应用服务器发送的第四信息；
    所述第一网元根据所述至少一种信息，确定终端执行的终端策略行为。
  2. 根据权利要求1所述的方法，其中，所述终端策略行为包括以下至少之一：
    终端正在使用的UE路由选择策略URSP规则；
    终端正在使用的URSP规则中的路由选择符RSD；
    终端为特定应用传输数据使用的URSP规则；
    终端为特定应用传输数据使用的URSP规则中的RSD；
    终端为特定应用传输数据使用的协议数据单元PDU会话；
    终端是否已使用更新的URSP规则；
    终端已使用的更新的URSP规则。
  3. 根据权利要求1或2所述的方法，其中，所述第一信息包括以下至少之一：
    第一指示信息，所述第一指示信息用于指示以下至少之一：终端正在使用的URSP规则、终端正在使用的URSP规则的业务描述符Traffic Descriptor、终端正在使用的URSP规则中的RSD；
    第二指示信息，所述第二指示信息用于指示以下至少之一：终端是否已使用更新的URSP规则、终端已使用的更新的URSP规则；
    第三指示信息，所述第三指示信息用于指示以下至少之一：终端为特定应用传输数据建立的PDU会话、终端建立的PDU会话对应的URSP规则、终端建立的PDU会话对应的URSP规则的Traffic Descriptor、终端建立的PDU会话对应的URSP规则中的RSD。
  4. 根据权利要求1至3中任一项所述的方法，其中，所述第一信息由所述终端通过控制面消息发送给所述第一网元。
  5. 根据权利要求4所述的方法，其中，所述控制面消息为非接入层NAS消息，
    所述第一信息携带在所述NAS消息中；或者，
    所述第一信息携带在所述NAS消息中的容器中。
  6. 根据权利要求1至3中任一项所述的方法，其中，所述第一信息由所述终端通过用户面消息发送给所述第一网元。
  7. 根据权利要求6所述的方法，其中，所述第一信息由所述终端通过用户面消息发送给用户面网元，并由所述用户面网元转发给所述第一网元。
  8. 根据权利要求7所述的方法，其中，所述用户面消息的包头中携带第一标识，所述第一标识用于指示所述用户面网元将所述用户面消息转发给所述第一网元。
  9. 根据权利要求1至8中任一项所述的方法，其中，所述第二信息包括第四指示信息，所述第四指示信息用于指示以下至少之一：
    给终端下发的URSP规则、给终端下发的URSP规则的Traffic descriptor、给终端下发的URSP规则与应用之间的映射关系、给终端下发的URSP规则的Traffic descriptor与应用之间的映射关系。
  10. 根据权利要求1至9中任一项所述的方法，其中，所述第三信息包括第五指示信息，所述第五指示信息用于指示以下至少之一：
    终端已建立的PDU会话、终端已建立的PDU会话对应的会话属性参数、终端已建立的PDU会话对应的会话属性参数中属于终端请求的会话属性参数、终端已建立的PDU会话对应的会话属性参数中属于网络添加的会话属性参数、终端已建立的PDU会话的地址信息。
  11. 根据权利要求1至10中任一项所述的方法，其中，所述第四信息包括第六指示信息，所述第六指示信息用于指示以下至少之一：
    终端的地址信息、终端的应用数据流使用的PDU会话、终端的应用数据流对应的应用标识、终端的应用数据流对应的Traffic descriptor参数。
  12. 根据权利要求1至11中任一项所述的方法，其中，所述方法还包括：
    所述第一网元接收终端发送的第七指示信息，所述第七指示信息用于指示网络侧所述终端请求上报所述第一信息或具备上报所述第一信息的能力。
  13. 根据权利要求1至12中任一项所述的方法，其中，所述方法还包括：
    所述第一网元向终端发送第八指示信息，所述第八指示信息用于指示要求或允许所述终端上报所述第一信息。
  14. 一种确定终端策略行为的装置，应用于第一网元，所述装置包括：
    获取单元，用于获取以下至少一种信息：终端发送的第一信息、PCF发送的第二信息、SMF发送的第三信息、应用服务器发送的第四信息；
    确定单元，用于根据所述至少一种信息，确定终端执行的终端策略行为。
  15. 根据权利要求14所述的装置，其中，所述终端策略行为包括以下至少之一：
    终端正在使用的URSP规则；
    终端正在使用的URSP规则中的RSD；
    终端为特定应用传输数据使用的URSP规则；
    终端为特定应用传输数据使用的URSP规则中的RSD；
    终端为特定应用传输数据使用的PDU会话；
    终端是否已使用更新的URSP规则；
    终端已使用的更新的URSP规则。
  16. 根据权利要求14或15所述的装置，其中，所述第一信息包括以下至少之一：
    第一指示信息，所述第一指示信息用于指示以下至少之一：终端正在使用的URSP规则、终端正在使用的URSP规则的Traffic Descriptor、终端正在使用的URSP规则中的RSD；
    第二指示信息，所述第二指示信息用于指示以下至少之一：终端是否已使用更新的URSP规则、终端已使用的更新的URSP规则；
    第三指示信息，所述第三指示信息用于指示以下至少之一：终端为特定应用传输数据建立的PDU会话、终端建立的PDU会话对应的URSP规则、终端建立的PDU会话对应的URSP规则的Traffic Descriptor、终端建立的PDU会话对应的URSP规则中的RSD。
  17. 根据权利要求14至16中任一项所述的装置，其中，所述第一信息由所述终端通过控制面消息发送给所述第一网元。
  18. 根据权利要求17所述的装置，其中，所述控制面消息为NAS消息，
    所述第一信息携带在所述NAS消息中；或者，
    所述第一信息携带在所述NAS消息中的容器中。
  19. 根据权利要求14至16中任一项所述的装置，其中，所述第一信息由所述终端通过用户面消息发送给所述第一网元。
  20. 根据权利要求19所述的装置，其中，所述第一信息由所述终端通过用户面 消息发送给用户面网元，并由所述用户面网元转发给所述第一网元。
  21. 根据权利要求20所述的装置，其中，所述用户面消息的包头中携带第一标识，所述第一标识用于指示所述用户面网元将所述用户面消息转发给所述第一网元。
  22. 根据权利要求14至21中任一项所述的装置，其中，所述第二信息包括第四指示信息，所述第四指示信息用于指示以下至少之一：
    给终端下发的URSP规则、给终端下发的URSP规则的Traffic descriptor、给终端下发的URSP规则与应用之间的映射关系、给终端下发的URSP规则的Traffic descriptor与应用之间的映射关系。
  23. 根据权利要求14至22中任一项所述的装置，其中，所述第三信息包括第五指示信息，所述第五指示信息用于指示以下至少之一：
    终端已建立的PDU会话、终端已建立的PDU会话对应的会话属性参数、终端已建立的PDU会话对应的会话属性参数中属于终端请求的会话属性参数、终端已建立的PDU会话对应的会话属性参数中属于网络添加的会话属性参数、终端已建立的PDU会话的地址信息。
  24. 根据权利要求14至23中任一项所述的装置，其中，所述第四信息包括第六指示信息，所述第六指示信息用于指示以下至少之一：
    终端的地址信息、终端的应用数据流使用的PDU会话、终端的应用数据流对应的应用标识、终端的应用数据流对应的Traffic descriptor参数。
  25. 根据权利要求14至24中任一项所述的装置，其中，所述获取单元，还用于接收终端发送的第七指示信息，所述第七指示信息用于指示网络侧所述终端请求上报所述第一信息或具备上报所述第一信息的能力。
  26. 根据权利要求14至25中任一项所述的装置，其中，所述装置还包括：
    发送单元，用于向终端发送第八指示信息，所述第八七指示信息用于指示要求或允许所述终端上报所述第一信息。
  27. 一种网络设备，包括：处理器和存储器，该存储器用于存储计算机程序，所述处理器用于调用并运行所述存储器中存储的计算机程序，执行如权利要求1至13中任一项所述的方法。
  28. 一种芯片，包括：处理器，用于从存储器中调用并运行计算机程序，使得安装有所述芯片的设备执行如权利要求1至13中任一项所述的方法。
  29. 一种计算机可读存储介质，用于存储计算机程序，所述计算机程序使得计算机执行如权利要求1至13中任一项所述的方法。
  30. 一种计算机程序产品，包括计算机程序指令，该计算机程序指令使得计算机执行如权利要求1至13中任一项所述的方法。
  31. 一种计算机程序，所述计算机程序使得计算机执行如权利要求1至13中任一项所述的方法。
PCT/CN2020/087472 2020-04-28 2020-04-28 一种确定终端策略行为的方法及装置、网络设备 WO2021217412A1 (zh)

Priority Applications (5)

Application Number Priority Date Filing Date Title
CN202080100317.6A CN115516920A (zh) 2020-04-28 2020-04-28 一种确定终端策略行为的方法及装置、网络设备
CN202310653096.0A CN116709420A (zh) 2020-04-28 2020-04-28 一种确定终端策略行为的方法及装置、网络设备
PCT/CN2020/087472 WO2021217412A1 (zh) 2020-04-28 2020-04-28 一种确定终端策略行为的方法及装置、网络设备
EP20933831.8A EP4142372B1 (en) 2020-04-28 2020-04-28 Method and apparatus for determining terminal policy behavior, and network device
US17/975,761 US20230068189A1 (en) 2020-04-28 2022-10-28 Method and apparatus for determining terminal policy behavior, and network device

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/CN2020/087472 WO2021217412A1 (zh) 2020-04-28 2020-04-28 一种确定终端策略行为的方法及装置、网络设备

Related Child Applications (1)

Application Number Title Priority Date Filing Date
US17/975,761 Continuation US20230068189A1 (en) 2020-04-28 2022-10-28 Method and apparatus for determining terminal policy behavior, and network device

Publications (1)

Publication Number Publication Date
WO2021217412A1 true WO2021217412A1 (zh) 2021-11-04

Family

ID=78331580

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2020/087472 WO2021217412A1 (zh) 2020-04-28 2020-04-28 一种确定终端策略行为的方法及装置、网络设备

Country Status (4)

Country Link
US (1) US20230068189A1 (zh)
EP (1) EP4142372B1 (zh)
CN (2) CN116709420A (zh)
WO (1) WO2021217412A1 (zh)

Cited By (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2023126004A1 (zh) * 2021-12-31 2023-07-06 维沃移动通信有限公司 数据传输方法、装置及终端
WO2023164849A1 (zh) * 2022-03-02 2023-09-07 Oppo广东移动通信有限公司 无线通信方法、装置、设备、存储介质及程序产品
WO2024065758A1 (zh) * 2022-09-30 2024-04-04 Oppo广东移动通信有限公司 一种无线通信方法及装置、设备、存储介质
WO2024088195A1 (zh) * 2022-10-26 2024-05-02 维沃移动通信有限公司 执行结果上报方法、接收方法、终端及网络侧设备

Families Citing this family (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN116708383A (zh) * 2020-09-30 2023-09-05 腾讯科技（深圳）有限公司 控制媒体流业务传输的方法及电子设备
CN112217812B (zh) * 2020-09-30 2023-04-21 腾讯科技（深圳）有限公司 控制媒体流业务传输的方法及电子设备

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20190268835A1 (en) * 2018-05-18 2019-08-29 Intel Corporation Ue indication to pcf whether or not to send ue policy
CN110519825A (zh) * 2018-05-21 2019-11-29 中国移动通信有限公司研究院 路由选择策略的处理方法、装置、相关设备和存储介质
CN110839261A (zh) * 2018-08-15 2020-02-25 华为技术有限公司 数据传输的方法和装置

Family Cites Families (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US10986516B2 (en) * 2017-03-10 2021-04-20 Huawei Technologies Co., Ltd. System and method of network policy optimization
CN110519795B (zh) * 2018-05-21 2021-12-10 华为技术有限公司 一种确定背景流量传输策略的方法及装置

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20190268835A1 (en) * 2018-05-18 2019-08-29 Intel Corporation Ue indication to pcf whether or not to send ue policy
CN110519825A (zh) * 2018-05-21 2019-11-29 中国移动通信有限公司研究院 路由选择策略的处理方法、装置、相关设备和存储介质
CN110839261A (zh) * 2018-08-15 2020-02-25 华为技术有限公司 数据传输的方法和装置

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
KDDI, CONVIDA WIRELESS LLC, TOYOTA ITC, ZTE: "Adding Support for Delivering Background Data Transfer Polices to the UE", 3GPP DRAFT; S2-1904376 REV OF 4337 AND 03389 - XBDT - 23503 V8, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE, vol. SA WG2, no. Xi’an, China; 20190408 - 20190412, 12 April 2019 (2019-04-12), Mobile Competence Centre ; 650, route des Lucioles ; F-06921 Sophia-Antipolis Cedex ; France , XP051720155 *

Cited By (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2023126004A1 (zh) * 2021-12-31 2023-07-06 维沃移动通信有限公司 数据传输方法、装置及终端
WO2023164849A1 (zh) * 2022-03-02 2023-09-07 Oppo广东移动通信有限公司 无线通信方法、装置、设备、存储介质及程序产品
WO2024065758A1 (zh) * 2022-09-30 2024-04-04 Oppo广东移动通信有限公司 一种无线通信方法及装置、设备、存储介质
WO2024088195A1 (zh) * 2022-10-26 2024-05-02 维沃移动通信有限公司 执行结果上报方法、接收方法、终端及网络侧设备

Also Published As

Publication number Publication date
EP4142372A1 (en) 2023-03-01
CN116709420A (zh) 2023-09-05
US20230068189A1 (en) 2023-03-02
CN115516920A (zh) 2022-12-23
EP4142372B1 (en) 2024-05-01
EP4142372A4 (en) 2023-05-03

Similar Documents

Publication Publication Date Title
WO2021217412A1 (zh) 一种确定终端策略行为的方法及装置、网络设备
CN114287142B (zh) 一种通信方法及装置、网络设备、终端设备
WO2021163895A1 (zh) 网络模型的管理方法及建立或修改会话的方法、装置
WO2021007785A1 (zh) 一种策略映射方法及装置、终端
WO2020107751A1 (zh) 一种数据传输方法及装置、终端
US11503531B2 (en) Control data transmission method and network device and storage medium
WO2021030989A1 (zh) 一种路径选择方法及装置、终端
WO2021046825A1 (zh) 无线通信的方法及设备
WO2020186529A1 (zh) 一种策略确定方法及装置、终端
WO2020206677A1 (zh) 一种配置策略的方法及装置、网络设备、终端
WO2021030965A1 (zh) 一种中继选择方法及装置、终端设备
WO2021087910A1 (zh) 用于连接网络的方法和设备
WO2021056576A1 (zh) 一种业务传输方法及装置、通信设备
WO2021007734A1 (zh) 一种会话设置方法、网络设备、用户设备
WO2021056573A1 (zh) 建立会话的方法和终端设备
WO2021022460A1 (zh) 一种会话验证方法、电子设备及存储介质
WO2020199105A1 (zh) 数据绑定方法、信息更新方法及装置、终端
WO2020223907A1 (zh) 一种信息传输方法及装置、网络设备
WO2020019910A1 (zh) 一种车联网中的通信方法及终端设备、网络设备
WO2020062042A1 (zh) 无线通信方法和设备
WO2020010619A1 (zh) 数据传输方法、终端设备和网络设备
WO2022147836A1 (zh) 一种连接建立方法及装置、网络设备
WO2020199215A1 (zh) 传输数据的方法、终端设备和核心网设备
WO2020087546A1 (zh) 一种网络信息传输方法、获取方法、网络设备及终端设备
WO2020164019A1 (zh) 一种承载配置方法及装置、网络设备

Legal Events

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

Ref document number: 20933831

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

ENP Entry into the national phase

Ref document number: 2020933831

Country of ref document: EP

Effective date: 20221121