A method and device for determining terminal policy behavior, and network equipment

Abstract

An embodiment of the present application provides a method, an apparatus, and a network device for determining terminal policy behavior. The method includes: a first network element obtains at least one of the following information: first information sent by the terminal, second information sent by the policy control function network element PCF, third information sent by the session management function network element SMF, and fourth information sent by the application server; the first network element determines the terminal policy behavior executed by the terminal based on the at least one information.

Description

[0001] This application is a divisional application of the PCT international patent application PCT / CN2020 / 087472 with an application date of April 28, 2020, which entered the Chinese national phase with Chinese patent application number 202080100317.6 and the invention name being “A method, device and network device for determining terminal policy behavior”. Technical Field

[0002] The embodiments of the present application relate to the field of mobile communication technology, and in particular to a method and apparatus for determining terminal policy behavior, and a network device. Background Art

[0003] When using the UE Route Selection Policy (URSP), the terminal may not select the optimal URSP rule, resulting in "unexpected behavior" of some terminals, and the network side has no way of knowing this, and is unable to optimize the URSP configuration. Summary of the invention

[0004] The embodiments of the present application provide a method and apparatus for determining terminal policy behavior, and a network device.

[0005] The method for determining terminal policy behavior provided in an embodiment of the present application includes:

[0006] The first network element obtains at least one of the following information: first information sent by the terminal, second information sent by a policy control function network element (Policy Control Function, PCF), third information sent by a session management function network element (Session Management Function, SMF), and fourth information sent by the application server;

[0007] The first network element determines a terminal policy behavior executed by the terminal according to the at least one information.

[0008] The device for determining a terminal policy behavior provided in an embodiment of the present application is applied to a first network element, and the device includes:

[0009] An acquisition unit, used to acquire 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;

[0010] A determination unit is used to determine a terminal policy behavior executed by the terminal according to the at least one information.

[0011] The network device provided in the embodiment of the present application includes a processor and a memory. The memory is used to store a computer program, and the processor is used to call and run the computer program stored in the memory to execute the above-mentioned method for determining terminal policy behavior.

[0012] The chip provided in the embodiment of the present application is used to implement the above-mentioned method for determining terminal policy behavior.

[0013] Specifically, the chip includes: a processor, which is used to call and run a computer program from a memory, so that a device equipped with the chip executes the above-mentioned method for determining terminal policy behavior.

[0014] The computer-readable storage medium provided in the embodiment of the present application is used to store a computer program, which enables a computer to execute the above-mentioned method for determining terminal policy behavior.

[0015] The computer program product provided in the embodiment of the present application includes computer program instructions, which enable a computer to execute the above-mentioned method for determining terminal policy behavior.

[0016] The computer program provided in the embodiment of the present application, when executed on a computer, enables the computer to execute the above-mentioned method for determining terminal policy behavior.

[0017] Through the above technical solution, the first network element determines the terminal policy behavior executed by the terminal based on 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, and then the URSP configuration can be optimized according to the execution of the terminal policy behavior. BRIEF DESCRIPTION OF THE DRAWINGS

[0018] The drawings described herein are used to provide a further understanding of the present application and constitute a part of the present application. The illustrative embodiments of the present application and their descriptions are used to explain the present application and do not constitute an improper limitation on the present application. In the drawings:

[0019] Figure 1 is a schematic diagram of a communication system architecture provided by an embodiment of the present application;

[0020] Figure 2 5G architecture diagram provided for the embodiment of the present application;

[0021] Figure 3 UCU flow chart provided for the embodiment of the present application;

[0022] Figure 4 A schematic diagram of binding an application data stream to a PDU session provided in an embodiment of the present application;

[0023] Figure 5A flowchart of a PDU session establishment being rejected and retrying PDU session establishment provided in an embodiment of the present application;

[0024] Figure 6 Schematic diagram of the process of determining terminal policy behavior provided in the embodiment of the present application Figure 1 ;

[0025] Figure 7 Schematic diagram of the process of determining terminal policy behavior provided in the embodiment of the present application Figure 2 ;

[0026] Figure 8 Schematic diagram of the process of determining terminal policy behavior provided in the embodiment of the present application Figure 3 ;

[0027] Fig. 9 A schematic diagram of the structure of the device for determining terminal policy behavior provided in an embodiment of the present application;

[0028] Fig.10 is a schematic structural diagram of a communication device provided in an embodiment of the present application;

[0029] Fig.11 is a schematic structural diagram of a chip according to an embodiment of the present application;

[0030] Fig.12 It is a schematic block diagram of a communication system provided in an embodiment of the present application. DETAILED DESCRIPTION

[0031] The following will describe the technical solutions in the embodiments of the present application in conjunction with the drawings in the embodiments of the present application. Obviously, the described embodiments are part of the embodiments of the present application, not all of the embodiments. Based on the embodiments in the present application, all other embodiments obtained by ordinary technicians in this field without creative work are within the scope of protection of this application.

[0032] The technical solutions of the embodiments of the present application can be applied to various communication systems, such as: Long Term Evolution (LTE) system, LTE Frequency Division Duplex (FDD) system, LTE Time Division Duplex (TDD) system, 5G communication system or future communication system, etc.

[0033] For example, the communication system 100 used in the embodiment of the present application is as follows: Figure 1As shown. The communication system 100 may include a network device 110, which may be a device that communicates with a terminal 120 (or referred to as a communication terminal, terminal). The network device 110 may provide communication coverage for a specific geographical area, and may communicate with terminals located within the coverage area. Optionally, the network device 110 may be an evolved base station (eNB or eNodeB) in an LTE system, or a wireless controller in a cloud radio access network (CRAN), or the network device may be a mobile switching center, a relay station, an access point, a vehicle-mounted 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.

[0034] The communication system 100 also includes at least one terminal 120 located within the coverage of the network device 110. As used herein, "terminal" includes but is not limited to connecting via a wired line, such as via a Public Switched Telephone Networks (PSTN), a Digital Subscriber Line (DSL), a digital cable, a direct cable connection; and / or another data connection / network; and / or via a wireless interface, such as, for a cellular network, a Wireless Local Area Network (WLAN), a digital television network such as a DVB-H network, a satellite network, an AM-FM broadcast transmitter; and / or another terminal configured to receive / send communication signals; and / or an Internet of Things (IoT) device. A terminal configured to communicate via a wireless interface may be referred to as a "wireless communication terminal", "wireless terminal" or "mobile terminal". Examples of mobile terminals include, but are not limited to, satellite or cellular telephones; Personal Communications System (PCS) terminals that may combine cellular radiotelephones with data processing, fax, and data communications capabilities; PDAs that may include radiotelephones, pagers, Internet / Intranet access, Web browsers, notepads, calendars, and / or Global Positioning System (GPS) receivers; and conventional laptop and / or palmtop receivers or other electronic devices that include radiotelephone transceivers. A terminal may refer to an access terminal, User Equipment (UE), a subscriber unit, a subscriber station, a mobile station, a mobile station, a remote station, a remote terminal, a mobile device, a user terminal, a terminal, a wireless communication device, a user agent, or a user device. The access terminal can be a cellular phone, a cordless phone, a Session Initiation Protocol (SIP) phone, a Wireless Local Loop (WLL) station, a Personal Digital Assistant (PDA), a handheld device with wireless communication capabilities, a computing device or other processing device connected to a wireless modem, a vehicle-mounted device, a wearable device, a terminal in a 5G network, or a terminal in a future evolved PLMN, etc.

[0035] Optionally, the terminals 120 may perform device-to-device (D2D) communication.

[0036] Optionally, the 5G communication system or 5G network may also be referred to as a New Radio (NR) system or NR network.

[0037] Figure 1 One network device and two terminals are shown exemplarily. Optionally, the communication system 100 may include multiple network devices and each network device may include another number of terminals within its coverage area, which is not limited in the embodiments of the present application.

[0038] Optionally, the communication system 100 may also include other network entities such as a network controller and a mobility management entity, which is not limited in the embodiments of the present application.

[0039] It should be understood that the device with communication function in the network / system in the embodiment of the present application can be referred to as a communication device. Figure 1 Taking the communication system 100 shown as an example, the communication equipment may include a network device 110 and a terminal 120 with communication functions. The network device 110 and the terminal 120 may be the specific devices described above and will not be repeated here. The communication equipment may also include other devices in the communication system 100, such as a network controller, a mobile management entity and other network entities, which is not limited in the embodiments of the present application.

[0040] It should be understood that the terms "system" and "network" are often used interchangeably in this article. The term "and / or" in this article is only a description of the association relationship of associated objects, indicating that three relationships can exist. For example, A and / or B can represent: A exists alone, A and B exist at the same time, and B exists alone. In addition, the character " / " in this article generally indicates that the associated objects before and after are in an "or" relationship.

[0041] To facilitate understanding of the technical solutions of the embodiments of the present application, the technical solutions related to the embodiments of the present application are described below.

[0042] UE policy configuration method based on 5G architecture

[0043] 5G architecture Figure 2As shown in the figure, the devices involved in the 5G architecture include: terminal, radio access network (Radio Access Network, RAN), user plane function network element (User Plane Function, UPF), data network (Data Network, DN), access and mobility management function network element (Access and Mobility Management Function, AMF), session management function network element (Session Management Function, SMF), policy control function network element (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).

[0044] like Figure 2 As shown in the figure, the network elements related to policies are mainly PCF, AMF, SMF, RAN, and terminals. Among them, SMF is mainly responsible for the execution of policies related to sessions, and AMF is mainly responsible for the execution of policies related to access and terminal policies. The policy issuance and update on the two network elements (AMF and SMF) are all controlled by PCF.

[0045] Specifically for terminal policies, PCF and the terminal use containers to monitor information related to terminal policies, including the content of the terminal policy, terminal policy identifiers, etc. In the uplink direction, the container is sent by the terminal to AMF through a Non-Access Stratum (NAS) message, and AMF continues to transparently transmit (without perception or modification) to PCF. In the downlink direction, the PCF sends the container to AMF, and AMF then transparently transmits it to the terminal through a NAS message.

[0046] Based on the above 5G architecture, the terminal policy is implemented through the UE Configuration Update (UCU) process, such as Figure 3 As shown, the UCU process includes the following steps:

[0047] Step 301: PCF decides to update the terminal policy.

[0048] Step 302: The PCF puts the terminal policy to be updated in a container and sends it to the AMF.

[0049] Step 303: AMF forwards the container directly to the terminal using a NAS message.

[0050] Step 304: The terminal sends the policy configuration result (Result of the delivery of UE policies) to the AMF.

[0051] Using terminal policies

[0052] Terminal policies include Access Network Discovery and Selection Policy (ANDSP), URSP, etc. Among them, URSP determines the binding relationship between application data and protocol data unit (PDU) sessions, and also determines what kind of PDU session the terminal needs to establish to satisfy this binding relationship. Figure 4 As shown, different application data streams are bound to different PDU sessions according to URSP rules. Data stream-a is bound to PDU session-1 according to rule-1, data stream-b is bound to PDU session-2 according to rule-2, and data stream-c is bound to PDU session-3 according to rule-3.

[0053] 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), and Service and Session Continuity Mode (SSC Mode).

[0054] The terminal can carry the above session attribute parameters in the PDU session establishment request message. If some session attribute parameters are not carried, the network side can fill them in. For example, the PDU session establishment request message carries PDU Session id = 1, DNN-1, PDU Sessiontype = IPv4. The SMF accepts the request and fills in the following other attribute parameters: S-NSSAI = 1, SSC Mode = 1.

[0055] It should be noted that, in this case, 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 in by the network.

[0056] Referring to Table 1 and Table 2 below, URSP contains multiple URSP rules, each of which consists of a traffic descriptor and a set of route selection descriptors (RSD). The service descriptor in URSP is used to describe a specific service. For example, a microblog service can be described by a range of IP addresses 1 to 9, and an IMS service can be described by an IMS DNN. Then, there can be one or more RSDs under a service descriptor. The value of S-NSSAI and the value of DNN in an RSD can be one or more, and other parameters contain only one value. Therefore, each RSD can correspond to one or more parameter value combinations, each parameter value combination is a feature of a set of PDU sessions, and the service data corresponding to the service descriptor can be transmitted in a PDU session corresponding to a certain parameter value combination of the RSD. When an application data stream described by a service descriptor appears, the terminal can select a parameter value combination according to the corresponding RSD and initiate a PDU session establishment request.

[0057] Each time the terminal initiates a PDU session establishment request, it adds a set of session attribute parameters in the PDU session establishment request message, which is a combination of parameter values ​​in the RSD table in a URSP rule.

[0058]

[0059] Table 1: Service descriptors in URSP rules and corresponding RSD lists

[0060]

[0061] Table 2: RSD

[0062] like Figure 4 As described above, the terminal associates the application data flow to the corresponding PDU session for transmission based on the URSP rule. The mechanism is as follows:

[0063] When data appears in the application layer, the terminal uses the URSP rules in the URSP to check whether the characteristics of the application data match the Traffic Descriptor of a rule in the URSP rules. The order of checking is determined by the priority (Precedence) in the URSP rules, that is, the terminal checks the matching situation in order based on the priority. When a URSP rule is matched, the RSD list under the URSP rule is used to bind the PDU session.

[0064] When a URSP rule is matched,

[0065] 1) The terminal first searches for a valid RSD in the currently established PDU session that satisfies the matching URSP rule. If yes, the terminal binds the matching application data to the PDU session for transmission. Otherwise:

[0066] 2) Try to establish a PDU session according to the precedence order in the valid RSD. Here, the RSD with a high priority is used to establish the PDU session. If a parameter in the RSD has one or more values, the terminal selects one of them and combines it with other parameters to establish the PDU session:

[0067] -If the PDU session is successfully established, the terminal binds the application data to the PDU session for transmission;

[0068] -If the PDU session establishment fails, the terminal attempts to establish the PDU session again based on other parameter value combinations in the RSD or using parameter value combinations in an RSD with lower priority.

[0069] If a suitable PDU session cannot be found for binding according to the matching URSP rule, the terminal searches the Traffic Descriptor in the second priority URSP rule according to the precedence order to see whether it can match the characteristics of the application data. When it matches, the above 1) and 2) processes are repeated.

[0070] The above process of finding or establishing a suitable PDU session for application data is called the "evaluation process". The RSD in the URSP rule is considered to be a valid RSD only if it meets the following conditions (here, the valid RSD is used to perform the above evaluation process):

[0071] - If there is S-NSSAI in RSD, S-NSSAI must belong to one of Allowed NSSAI (non-roaming) or Mapping of Allowed NSSAI (roaming);

[0072] -If there is a DNN in the RSD and it is a LADN DNN, the terminal must be within the valid area corresponding to the LADN;

[0073] -If the RSD has Access Type Prefrence and is set to Multi-Access, the terminal must support the ASSS function;

[0074] -If there are Timer Window and Location Criteria in the RSD, the terminal must meet the required time and location conditions.

[0075] For RSDs that do not meet the above conditions, the terminal will not use the RSDs to bind application data or establish PDU sessions.

[0076] According to the mechanism of the above evaluation process, the terminal can try to establish a PDU session again according to the parameters in the RSD after the PDU session establishment is rejected. Figure 5 As shown, the process of PDU session establishment being rejected and retrying PDU session establishment includes the following steps:

[0077] Step 501: The terminal sends a PDU session establishment request message to the SMF.

[0078] Here, 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.

[0079] Step 502: SMF sends a PDU session establishment request reply message to the terminal, carrying a rejection reason value.

[0080] Here, if the network side rejects the session request, the rejection reason value will be carried in the PDU session establishment request reply message.

[0081] Step 503: The terminal adjusts the parameter value combination according to the RSD in the URSP rule and initiates PDU session establishment again.

[0082] Currently, the URSP mechanism has the following characteristics and problems:

[0083] 1) Parameters in URSP rules, such as the Applicaton Descriptor parameter in TrafficDescriptor, may not be recognized by the terminal. The reason is that some parameters require coordination between operators and terminal companies, and cannot be determined unilaterally by operators. According to the evaluation process, if the terminal cannot recognize the parameters 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 them have been ignored. This causes some URSP rules issued by the network side to never be executed by the terminal, but the network side is unaware of this situation.

[0084] 2) 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 binding relationship between the application data and the PDU session according to the new URSP rule. However, when the terminal evaluates the new URSP rule and when the new binding relationship is executed are all self-implemented by the terminal. After the network updates the URSP rule for the terminal, it cannot be determined when the terminal will execute the new URSP rule to bind the application data flow.

[0085] 3) For each application data flow, the terminal will eventually 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 flow may not be the highest priority, but the network side cannot determine which URSP rule and RSD the terminal uses for the application data flow.

[0086] To sum up, although it does not violate the evaluation mechanism, it can be considered as an "unexpected behavior" of the terminal, because the terminal did not perform the evaluation process according to the highest priority or most expected URSP rule issued by the network side. The network side cannot determine whether there is such "unexpected behavior", so a mechanism is needed for the network side to determine the "terminal policy behavior" being executed by the terminal. To this end, the following technical solutions of the embodiments of the present application are proposed. It should be noted that the technical solutions of the embodiments of the present application can be applied to 5G networks, but are not limited to this. The technical solutions of the embodiments of the present application can also be applied to 4G networks or future new networks.

[0087] Figure 6 Schematic diagram of the process of determining terminal policy behavior provided in the embodiment of the present application Figure 1 ,like Figure 6 As shown, the method for determining terminal policy behavior includes the following steps:

[0088] 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.

[0089] In the embodiment of the present application, the first network element is a network element with an analysis function. In an optional manner, the first network element is a network data analysis function network element (Network Data Analysis Function, NWDAF).

[0090] In the embodiment of the present application, the information acquired 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. These information are described in detail below.

[0091] ●The first message sent by the terminal

[0092] In an optional manner, the first information sent by the terminal includes at least one of the following:

[0093] First indication information, where the first indication information is used to indicate at least one of the following: a URSP rule being used by the terminal, a Traffic Descriptor of the URSP rule being used by the terminal, and an RSD in the URSP rule being used by the terminal; here, when the terminal sends the Traffic Descriptor, all parameters in the Traffic Descriptor may be sent, or only part of the parameters in the Traffic Descriptor may be sent;

[0094] second indication information, where 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, and the updated URSP rule that has been used (or executed) by the terminal (i.e., which updated URSP rules have been used or executed by the terminal);

[0095] The third indication information is used to indicate at least one of the following: a PDU session established by the terminal for transmitting data for a specific application, a URSP rule corresponding to the PDU session established by the terminal, a Traffic Descriptor of the URSP rule corresponding to the PDU session established by the terminal, and an RSD in the URSP rule corresponding to the PDU session established by the terminal.

[0096] In an optional manner, the first information is sent by the terminal to the first network element via a control plane message. Further, 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.

[0097] In another optional manner, the first information is sent by the terminal to the first network element through a user plane message. Specifically, the first information is sent by the terminal to the user plane network element through a user plane message, and is forwarded by the user plane network element to the first network element. Optionally, the 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. Here, optionally, the header of the user plane message is an SDAP header or a GTP-U header. Optionally, the user plane network element is a UPF.

[0098] In the above solution, the first information sent by the terminal may also be referred to as policy execution information.

[0099] In an optional manner, the terminal may send seventh indication information to the network side, and the seventh indication information is used to indicate to the network side that the terminal requests to report the first information or has the ability to report the first information. Optionally, the seventh indication information is also used to indicate what contents are included in the first information that the terminal can or requests to report. The seventh indication information may be sent to the network side via an uplink NAS message, for example, the terminal includes the seventh indication information in a registration request message and sends it to the network side.

[0100] In an optional manner, the network side sends an eighth indication information to the terminal, and 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 contents are included in the first information that the terminal is required or allowed to report. Here, optionally, the network side may be the first network element. The eighth indication information may be sent to the terminal via a downlink NAS message, for example, the network side adds the eighth indication information to a registration reply message and sends it to the terminal.

[0101] ●The second message sent by PCF

[0102] In an optional manner, the second information includes fourth indication information, and the fourth indication information is used to indicate at least one of the following:

[0103] URSP rules delivered to the terminal, Traffic descriptors of URSP rules delivered to the terminal, mapping relationships between URSP rules delivered to the terminal and applications, and mapping relationships between Traffic descriptors of URSP rules delivered to the terminal and applications.

[0104] ●The third information sent by SMF

[0105] In an optional manner, the third information includes fifth indication information, and the fifth indication information is used to indicate at least one of the following:

[0106] The PDU session established by the terminal, the session attribute parameters corresponding to the PDU session established by the terminal, the session attribute parameters requested by the terminal among the session attribute parameters corresponding to the PDU session established by the terminal (i.e. which session attribute parameters among the session attribute parameters corresponding to the PDU session established by the terminal are requested by the terminal), the session attribute parameters added by the network among the session attribute parameters corresponding to the PDU session established by the terminal (i.e. which session attribute parameters among the session attribute parameters corresponding to the PDU session established by the terminal are added by the network), and the address information of the PDU session established by the terminal.

[0107] Here, optionally, the address information of the PDU session refers to the IP address information of the PDU session.

[0108] ●The fourth message sent by the application server

[0109] In an optional manner, the fourth information includes sixth indication information, and the sixth indication information is used to indicate at least one of the following:

[0110] The address information of the terminal, the PDU session used by the application data flow of the terminal, the application identifier corresponding to the application data flow of the terminal, and the Traffic descriptor parameters corresponding to the application data flow of the terminal.

[0111] Here, optionally, the address information of the terminal refers to the IP address information of the terminal.

[0112] Step 602: The first network element determines a terminal policy behavior executed by the terminal according to the at least one information.

[0113] In the embodiment of the present application, the first network element may analyze the at least one information to determine the terminal policy behavior executed by the terminal. Specifically, the terminal policy behavior includes at least one of the following:

[0114] UE routing policy URSP rules currently used by the terminal;

[0115] The routing selector RSD in the URSP rule being used by the terminal;

[0116] URSP rules used by the terminal to transmit data for a specific application;

[0117] The RSD in the URSP rules used by the terminal to transmit data for a specific application;

[0118] A protocol data unit (PDU) session used by a terminal to transmit data for a specific application;

[0119] Whether the terminal has used the updated URSP rules;

[0120] The updated URSP rules used by the terminal.

[0121] Here, the specific application may refer to an application corresponding to a specific application identifier (Application Id).

[0122] The technical solution of the embodiment of the present application is illustrated below with reference to specific application examples.

[0123] Example 1

[0124] The first network element receives first information (ie, policy execution information) sent by the terminal, and the first network element determines the terminal policy behavior being executed by the terminal based on the first information.

[0125] Further, optionally, the first network element also receives at least one of the following: second information sent by the PCF, third information sent by the SMF, and fourth information sent by the application server. The first network element determines the terminal policy behavior being executed by the terminal based on the first information and at least one of the second information, the third information, and the fourth information.

[0126] It should be noted that the contents of the first information, the second information, the third information and the fourth information can refer to the description of the aforementioned scheme.

[0127] Reference Figure 7 , Figure 7 Taking the first network element being NWDAF as an example, the following steps are included:

[0128] Step 701: NWDAF receives first information sent by a terminal.

[0129] Step 702: NWDAF receives the second information sent by PCF.

[0130] Step 703: NWDAF receives the third information sent by SMF.

[0131] Step 704: NWDAF receives the fourth information sent by the application server.

[0132] Step 705: NWDAF determines the terminal policy behavior executed by the terminal according to the obtained information.

[0133] It should be noted that step 702 to step 704 are optional. The following describes the steps in conjunction with specific examples.

[0134] Example 1: NWDAF obtains the following information:

[0135] - First information from the terminal: the terminal is using RSD-3 in URSP-Rule2;

[0136] - Second message from PCF: sent to end users

[0137] URSP-Rule1 (RSD-1), corresponding to Application Id-1 and Application Id-2;

[0138] URSP-Rule2 (RSD-1 / 2 / 3), corresponding to; Application Id-2;

[0139] URSP-Rule3(RSD-1 / 2), corresponding to Application Id-3.

[0140] -The fourth information from the application server: requesting to detect on which network slice the data of Application Id-2 is transmitted (or requesting to detect on which network slice corresponding to the S-NSSAI the data of Application Id-2 is transmitted).

[0141] Based on the above information, NWDAF can determine that the terminal is using RSD-3 in URSP-Rule2 to transmit application data for Application id-2, and the S-NSSAI parameter in RSD-3 is S-NSSAI-a, so the data of Application Id-2 is transmitted on the network slice corresponding to S-NSSAI-a.

[0142] Example 2: NWDAF obtains the following information:

[0143] - First information from the terminal: the terminal is using RSD-3 in URSP-Rule2;

[0144] - Second message from PCF: sent to end users

[0145] URSP-Rule1 (RSD-1), corresponding to Application Id-1 and Application Id-2;

[0146] URSP-Rule2 (RSD-1 / 2 / 3), corresponding to; Application Id-2;

[0147] URSP-Rule3(RSD-1 / 2), corresponding to Application Id-3.

[0148] - The third information from SMF: the correspondence between PDU Session-1 and session attribute parameters (including session attribute parameters requested by the terminal).

[0149] Based on the above information, NWDAF can determine on which PDU session Application ID-1, 2, and 3 are transmitted respectively. Further, NWDAF can send the determination result to other network elements (such as a network management system) for statistical storage.

[0150] It should be noted that NWDAF is not the only network element that determines the terminal policy behavior. In an optional manner, when PCF does not provide the mapping relationship between URSP rules and applications, NWDAF can inform PCF of the URSP rules and corresponding RSD currently being used by the terminal, and PCF determines the terminal policy behavior.

[0151] Example 2

[0152] The first network element receives at least one of the following: second information sent by the PCF, third information sent by the SMF, and fourth information sent by the application server. The first network element determines the terminal policy behavior being executed by the terminal based on at least one of the second information, the third information, and the fourth information.

[0153] It should be noted that the contents of the second information, the third information and the fourth information can refer to the description of the aforementioned solution.

[0154] Reference Figure 8 , Figure 8 Taking the first network element being NWDAF as an example, the following steps are included:

[0155] Step 801: NWDAF receives the second information sent by PCF.

[0156] Step 802: NWDAF receives the third information sent by SMF.

[0157] Step 803: NWDAF receives the fourth information sent by the application server.

[0158] Step 804: NWDAF determines the terminal policy behavior executed by the terminal according to the obtained information.

[0159] It should be noted that, in step 801 to step 803, some or all of the steps may be selected for execution.

[0160] Example 3: NWDAF obtains the following information:

[0161] -The third information from SMF: PDU Session-1 corresponds to IP address 1, PDU Session-2 corresponds to IP address 2, and the session attribute parameters requested by the terminal corresponding to PDU Session-1 are S-NSSAI-1, DNN-1.

[0162] -Second message from PCF: sent to the terminal

[0163] URSP-Rule1 (RSD-1 consists of S-NSSAI-1 and DNN-1), corresponding to Application Id-1 and Application Id-2;

[0164] URSP-Rule2 (RSD-1 / 2 / 3 do not include S-NSSAI-1), corresponding to Application Id-2;

[0165] URSP-Rule3(RSD-1 / 2), corresponding to Application Id-3.

[0166] - The fourth information from the application server: the IP address of the terminal is IP address 1* (corresponding to IP address 1), Application Id-2.

[0167] It should be noted that the IP address of the terminal provided by the application server may be a public IP address converted by NAT, while the IP address corresponding to the PDU session is a private 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.

[0168] Based on the above information, the NWDAF can determine that the terminal is using PDU Session-1 to transmit the application data flow, and the terminal is using URSP-Rule1 (RSD1) to transmit the application data flow.

[0169] Example 4: NWDAF obtains the following information:

[0170] -The third information from SMF: The terminal has two PDU Sessions, namely PDU Session-1 and PDUSession-2. The session attribute parameters requested by the terminal corresponding to PDU Session-1 are S-NSSAI-1, DNN-1, and the session attribute parameters requested by the terminal corresponding to PDUSession-2 are S-NSSAI-2, DNN-2.

[0171] - Second message from PCF: sent to end users

[0172] URSP-Rule1 (RSD-1), Traffic descriptor in the rule = IP address x;

[0173] URSP-Rule2 (RSD-1 / 2 / 3, where only RSD-2 consists of S-NSSAI-2 and DNN-2), Traffic descriptor in the rule = IP address y;

[0174] URSP-Rule3 (RSD-1 / 2), Traffic descriptor in the rule = Application descriptor-3.

[0175] -The fourth information from the application server: the Traffic Descriptor corresponding to the application is the IP address y.

[0176] Based on the above information, NWDAF can determine that the terminal is using RSD-2 in URSP-Rule2 and is using PDU Session-2 to transmit application data.

[0177] Example 5: NWDAF obtains the following information:

[0178] -The third information from SMF: The terminal has two PDU Sessions, namely PDU Session-1 and PDUSession-2, where the address information of PDU Session-1 is IP address 1, and the session attribute parameters are 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.

[0179] - Second message from PCF: sent to end users

[0180] URSP-Rule1 (RSD-1), RSD-1 consists of S-NSSAI-1 and DNN-1, and the Trafficdescriptor in the rule is: Connection Capabilities = "internet";

[0181] URSP-Rule2 (RSD-2), RSD-2 consists of S-NSSAI-2 and DNN-2. The Trafficdescriptor in the rule is: Connection Capabilities = "internet";

[0182] URSP-Rule3 (RSD-3), the Traffic descriptor in the rule is Connection Capabilities = "IMS".

[0183] - The fourth information from the application server: the address information of the terminal is IP address 2, and the TrafficDescriptor corresponding to the application is Connection Capabilities = "internet".

[0184] Based on the above information, NWDAF can determine that the terminal is using RSD-2 in URSP-Rule2 and is using PDU Session-2 to transmit application data.

[0185] In this example, NWDAF determines the Traffic descriptor and the corresponding PDU session attribute parameters used by the current application based on the terminal address information and Traffic descriptor obtained from the application server, and the address information and session attribute parameters of the PDU session obtained from the SMF, and compares them with the URSP rules (including Traffic descriptor and corresponding PDU session attribute parameters) obtained from the PCF to determine the URSP rules currently being used by the terminal. Alternatively, NWDAF determines the session attribute parameters of the PDU session that may be used by the terminal based on the terminal address information and Traffic descriptor obtained from the application server, and determines the URSP rules currently being used by the terminal based on the session attribute parameters of the PDU session corresponding to the address information obtained from the SMF.

[0186] Example 6:

[0187] NWDAF obtained the following information:

[0188] -The third information from SMF: The terminal has two PDU Sessions, namely PDU Session-1 and PDUSession-2, where the address information of PDU Session-1 is IP address 1, and the session attribute parameters are 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.

[0189] - Second message from PCF: sent to end users

[0190] URSP-Rule1 (RSD-1), RSD-1 consists of S-NSSAI-1 and DNN-1, and the Trafficdescriptor in the rule is: Application descriptor = "youtube service";

[0191] URSP-Rule2 (RSD-2), RSD-2 consists of S-NSSAI-2 and DNN-2. The Trafficdescriptor in the rule is: Application descriptor = "youtube service";

[0192] URSP-Rule3 (RSD-3), the Traffic descriptor in the rule is Application descriptor = "google service".

[0193] - The fourth information from the application server: the address information of the terminal is IP address 2, and the application identifier is Application Id-1.

[0194] In addition, NWDAF can obtain from PCF or based on the provisioned information on NWDAF: Traffic Descriptor corresponding to Application Id-1 is Application descriptor = "youtube service". Here, it should be noted that the mapping relationship between the application identifier (Application Id) and the service descriptor (Traffic Descriptor) can be obtained by PCF or provisioned on NWDAF.

[0195] Based on the above information, NWDAF can determine that the terminal is using RSD-2 in URSP-Rule2 and is using PDU Session-2 to transmit application data.

[0196] It should be noted that the application identifier (Application Id) in the above scheme of the present application is used between the core network and the application server to refer to a specific application, and the application descriptor (Application descriptor) is used by the terminal to identify a specific application. The formats and values ​​of the two may be different, but there may be a corresponding relationship, that is, there is a corresponding relationship between the Application Id and the Application descriptor.

[0197] The technical solution of the embodiment of the present application proposes a mechanism that enables the network side to determine whether the terminal policy behavior executed by the terminal conforms to the expected method, so that the network side can determine whether the URSP rule executed by the terminal is what it expects. To this end, it is necessary to report relevant information through the terminal, core network elements (such as PCF, SMF), and application servers, so that the analysis element on the network side can analyze and obtain corresponding results (such as whether the terminal is using the URSP rule with the highest priority), and adjust and update the policy when necessary.

[0198] Fig. 9 A schematic diagram of the structure of the device for determining the terminal policy behavior provided in an embodiment of the present application is applied to a first network element, such as Fig. 9 As shown, the device for determining the terminal policy behavior includes:

[0199] The acquisition unit 901 is used to acquire 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;

[0200] The determination unit 902 is configured to determine a terminal policy behavior executed by the terminal according to the at least one information.

[0201] In an optional manner, the terminal policy behavior includes at least one of the following:

[0202] The URSP rules currently used by the terminal;

[0203] The RSD in the URSP rules that the terminal is using;

[0204] URSP rules used by the terminal to transmit data for a specific application;

[0205] The RSD in the URSP rules used by the terminal to transmit data for a specific application;

[0206] PDU session used by the terminal to transmit data for a specific application;

[0207] Whether the terminal has used the updated URSP rules;

[0208] The updated URSP rules used by the terminal.

[0209] In an optional manner, the first information includes at least one of the following:

[0210] first indication information, where the first indication information is used to indicate at least one of the following: a URSP rule being used by the terminal, a Traffic Descriptor of the URSP rule being used by the terminal, and an RSD in the URSP rule being used by the terminal;

[0211] 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 used by the terminal;

[0212] The third indication information is used to indicate at least one of the following: a PDU session established by the terminal for transmitting data for a specific application, a URSP rule corresponding to the PDU session established by the terminal, a Traffic Descriptor of the URSP rule corresponding to the PDU session established by the terminal, and an RSD in the URSP rule corresponding to the PDU session established by the terminal.

[0213] In an optional manner, the first information is sent by the terminal to the first network element via a control plane message.

[0214] In an optional manner, the control plane message is a NAS message.

[0215] The first information is carried in the NAS message; or,

[0216] The first information is carried in a container in the NAS message.

[0217] In an optional manner, the first information is sent by the terminal to the first network element via a user plane message.

[0218] In an optional manner, 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.

[0219] In an optional manner, 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.

[0220] In an optional manner, the second information includes fourth indication information, and the fourth indication information is used to indicate at least one of the following:

[0221] URSP rules delivered to the terminal, Traffic descriptors of URSP rules delivered to the terminal, mapping relationships between URSP rules delivered to the terminal and applications, and mapping relationships between Traffic descriptors of URSP rules delivered to the terminal and applications.

[0222] In an optional manner, the third information includes fifth indication information, and the fifth indication information is used to indicate at least one of the following:

[0223] The PDU session established by the terminal, the session attribute parameters corresponding to the PDU session established by the terminal, the session attribute parameters requested by the terminal in the session attribute parameters corresponding to the PDU session established by the terminal, the session attribute parameters added by the network in the session attribute parameters corresponding to the PDU session established by the terminal, and the address information of the PDU session established by the terminal.

[0224] In an optional manner, the fourth information includes sixth indication information, and the sixth indication information is used to indicate at least one of the following:

[0225] The address information of the terminal, the PDU session used by the application data flow of the terminal, the application identifier corresponding to the application data flow of the terminal, and the Traffic descriptor parameters corresponding to the application data flow of the terminal.

[0226] In an optional manner, the acquisition unit 901 is further used to receive seventh indication information sent by the terminal, and the seventh indication information is used to indicate to the network side that the terminal requests to report the first information or has the ability to report the first information. Optionally, the seventh indication information is also used to indicate what contents are included in the first information that the terminal can or requests to report. The seventh indication information can be sent to the network side via an uplink NAS message, for example, the terminal includes the seventh indication information in a registration request message and sends it to the network side.

[0227] In an optional manner, the device further includes: a sending unit (not shown in the figure), configured to send an eighth indication information to the terminal, wherein 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 contents are included in the first information that the terminal is required or allowed to report. Here, optionally, the network side may be the first network element. The eighth indication information may be sent to the terminal via a downlink NAS message, for example, the network side adds the eighth indication information to a registration reply message and sends it to the terminal.

[0228] Those skilled in the art should understand that the relevant description of the above-mentioned device for determining terminal policy behavior in the embodiment of the present application can be understood by referring to the relevant description of the method for determining terminal policy behavior in the embodiment of the present application.

[0229] Fig.10 1 is a schematic structural diagram of a communication device 1000 provided in 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). Fig.10 The communication device 1000 shown 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.

[0230] Alternatively, if Fig.10 As shown, the communication device 1000 may further include a memory 1020. The processor 1010 may call and run a computer program from the memory 1020 to implement the method in the embodiment of the present application.

[0231] The memory 1020 may be a separate device independent of the processor 1010 , or may be integrated into the processor 1010 .

[0232] Alternatively, if Fig.10 As shown, 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, may send information or data to other devices, or receive information or data sent by other devices.

[0233] 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.

[0234] Optionally, the communication device 1000 may specifically be a network device of an embodiment of the present application, and the communication device 1000 may implement corresponding processes implemented by the network device in each method of the embodiment of the present application, which will not be described in detail here for the sake of brevity.

[0235] Optionally, the communication device 1000 may specifically be a mobile terminal / terminal of an embodiment of the present application, and the communication device 1000 may implement the corresponding processes implemented by the mobile terminal / terminal in each method of the embodiment of the present application, which will not be described again for the sake of brevity.

[0236] Fig.11 It is a schematic structural diagram of the chip of an embodiment of the present application. Fig.11 The chip 1100 shown includes a processor 1110, which can call and run a computer program from a memory to implement the method in the embodiment of the present application.

[0237] Alternatively, if Fig.11 As shown, the chip 1100 may further include a memory 1120. The processor 1110 may call and run a computer program from the memory 1120 to implement the method in the embodiment of the present application.

[0238] The memory 1120 may be a separate device independent of the processor 1110 , or may be integrated into the processor 1110 .

[0239] Optionally, the chip 1100 may further include an input interface 1130. The processor 1110 may control the input interface 1130 to communicate with other devices or chips, and specifically, may obtain information or data sent by other devices or chips.

[0240] Optionally, the chip 1100 may further include an output interface 1140. The processor 1110 may control the output interface 1140 to communicate with other devices or chips, and specifically, may output information or data to other devices or chips.

[0241] Optionally, the chip can be applied to the network device in the embodiments of the present application, and the chip can implement the corresponding processes implemented by the network device in each method of the embodiments of the present application. For the sake of brevity, they will not be repeated here.

[0242] Optionally, the chip can be applied to the mobile terminal / terminal in the embodiments of the present application, and the chip can implement the corresponding processes implemented by the mobile terminal / terminal in the various methods of the embodiments of the present application. For the sake of brevity, they will not be repeated here.

[0243] It should be understood that the chip mentioned in the embodiments of the present application can also be called a system-level chip, a system chip, a chip system or a system-on-chip chip, etc.

[0244] Fig.12 1 is a schematic block diagram of a communication system 1200 provided in an embodiment of the present application. Fig.12 As shown, the communication system 1200 includes a terminal 1210 and a network device 1220 .

[0245] Among them, the terminal 1210 can be used to implement the corresponding functions implemented by the terminal in the above method, and the network device 1220 can be used to implement the corresponding functions implemented by the network device in the above method. For the sake of brevity, they are not repeated here.

[0246] It should be understood that the processor of the embodiment of the present application may be an integrated circuit chip with signal processing capabilities. In the implementation process, each step of the above method embodiment can be completed by the hardware integrated logic circuit or software instructions in the processor. The above processor can be a general processor, a digital signal processor (Digital Signal Processor, DSP), an application-specific integrated circuit (Application Specific Integrated Circuit, ASIC), a field programmable gate array (Field Programmable Gate Array, FPGA) or other programmable logic devices, discrete gates or transistor logic devices, discrete hardware components. The methods, steps and logic block diagrams disclosed in the embodiments of the present application can be implemented or executed. The general processor can be a microprocessor or the processor can also be any conventional processor. The steps of the method disclosed in the embodiment of the present application can be directly embodied as a hardware decoding processor to perform, or the hardware and software modules in the decoding processor are combined and performed. The software module can be located in a random access memory, a flash memory, a read-only memory, a programmable read-only memory or an electrically erasable programmable memory, a register, and other mature storage media in the art. 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.

[0247] It can be understood that the memory in the embodiments of the present application can be a volatile memory or a non-volatile memory, or can include both volatile and non-volatile memories. Among them, the non-volatile memory can be a read-only memory (ROM), a programmable read-only memory (PROM), an erasable programmable read-only memory (EPROM), an electrically erasable programmable read-only memory (EEPROM), or a flash memory. The volatile memory can be a random access memory (RAM), which is used as an external cache. By way of example and not limitation, many forms of RAM are available, such as static random access memory (SRAM), dynamic random access memory (DRAM), synchronous dynamic random access memory (SDRAM), double data rate synchronous dynamic random access memory (DDR SDRAM), enhanced synchronous dynamic random access memory (ESDRAM), synchronous link dynamic random access memory (SLDRAM), and direct RAM bus random access memory (DR RAM). It should be noted that the memory of the systems and methods described herein is intended to include, but is not limited to, these and any other suitable types of memory.

[0248] It should be understood that the above-mentioned memory is exemplary but not restrictive. For example, the memory in the embodiments 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 link dynamic random access memory (synch link DRAM, SLDRAM) and direct memory bus random access memory (Direct Rambus RAM, DR RAM), etc. That is to say, the memory in the embodiments of the present application is intended to include but not limited to these and any other suitable types of memory.

[0249] An embodiment of the present application also provides a computer-readable storage medium for storing a computer program.

[0250] Optionally, the computer-readable storage medium can be applied to the network device in the embodiments of the present application, and the computer program enables the computer to execute the corresponding processes implemented by the network device in the various methods of the embodiments of the present application. For the sake of brevity, they are not repeated here.

[0251] Optionally, the computer-readable storage medium can be applied to the mobile terminal / terminal in the embodiments of the present application, and the computer program enables the computer to execute the corresponding processes implemented by the mobile terminal / terminal in the various methods of the embodiments of the present application. For the sake of brevity, they are not repeated here.

[0252] An embodiment of the present application also provides a computer program product, including computer program instructions.

[0253] Optionally, the computer program product can be applied to the network device in the embodiments of the present application, and the computer program instructions enable the computer to execute the corresponding processes implemented by the network device in the various methods of the embodiments of the present application. For the sake of brevity, they are not repeated here.

[0254] Optionally, the computer program product can be applied to the mobile terminal / terminal in the embodiments of the present application, and the computer program instructions enable the computer to execute the corresponding processes implemented by the mobile terminal / terminal in the various methods of the embodiments of the present application. For the sake of brevity, they are not repeated here.

[0255] The embodiment of the present application also provides a computer program.

[0256] Optionally, the computer program can be applied to the network device in the embodiments of the present application. When the computer program runs on a computer, the computer executes the corresponding processes implemented by the network device in the various methods in the embodiments of the present application. For the sake of brevity, they are not described here.

[0257] Optionally, the computer program can be applied to the mobile terminal / terminal in the embodiments of the present application. When the computer program runs on the computer, the computer executes the corresponding processes implemented by the mobile terminal / terminal in the various methods of the embodiments of the present application. For the sake of brevity, they are not repeated here.

[0258] Those of ordinary skill in the art will appreciate that the units and algorithm steps of each example described in conjunction with the embodiments disclosed herein can be implemented in electronic hardware, or a combination of computer software and electronic hardware. Whether these functions are performed in hardware or software depends on the specific application and design constraints of the technical solution. Professional and technical personnel can use different methods to implement the described functions for each specific application, but such implementation should not be considered to be beyond the scope of this application.

[0259] Those skilled in the art can clearly understand that, for the convenience and brevity of description, the specific working processes of the systems, devices and units described above can refer to the corresponding processes in the aforementioned method embodiments and will not be repeated here.

[0260] In the several embodiments provided in the present application, it should be understood that the disclosed systems, devices and methods can be implemented in other ways. For example, the device embodiments described above are only schematic. For example, the division of the units is only a logical function division. There may be other division methods in actual implementation, such as multiple units or components can be combined or integrated into another system, or some features can be ignored or not executed. Another point is that the mutual coupling or direct coupling or communication connection shown or discussed can be through some interfaces, indirect coupling or communication connection of devices or units, which can be electrical, mechanical or other forms.

[0261] The units described as separate components may or may not be physically separated, and the components shown as units may or may not be physical units, that is, they may be located in one place or distributed on multiple network units. Some or all of the units may be selected according to actual needs to achieve the purpose of the solution of this embodiment.

[0262] In addition, each functional unit in each embodiment of the present application may be integrated into one processing unit, or each unit may exist physically separately, or two or more units may be integrated into one unit.

[0263] If the functions are implemented in the form of software functional units and sold or used as independent products, they can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of the present application can be essentially or partly embodied in the form of a software product that contributes to the prior art. The computer software product is stored in a storage medium and includes several instructions for a computer device (which can be a personal computer, a server, or a network device, etc.) to perform all or part of the steps of the methods described in each embodiment of the present application. The aforementioned storage medium includes: various media that can store program codes, such as a USB flash drive, a mobile hard disk, a read-only memory (ROM), a random access memory (RAM), a magnetic disk or an optical disk.

[0264] The above is only a specific implementation of the present application, but the protection scope of the present application is not limited thereto. Any technician familiar with the technical field can easily think of changes or substitutions within the technical scope disclosed in the present application, which should be included in the protection scope of the present application. Therefore, the protection scope of the present application should be based on the protection scope of the claims.

Claims

1. A method for determining terminal policy behavior, the method comprising: The first network element obtains first information sent by the terminal; The first network element determines a terminal policy behavior executed by the terminal according to the first information, Among them, the first information includes: third indication information, and the third indication information is used to indicate at least one of the following: the service descriptor TrafficDescriptor of the UE routing selection policy URSP rule corresponding to the protocol data unit PDU session established by the terminal, and the routing selector RSD in the URSP rule corresponding to the PDU session established by the terminal.

2. The method according to claim 1, wherein: The terminal policy behavior includes: The terminal identifies the URSP rule used by the application to transmit data corresponding to the application.

3. The method according to claim 1 or 2, wherein: The first information also includes: The first indication information is used to indicate: a URSP rule being used by the terminal, or a Traffic Descriptor of the URSP rule being used by the terminal.

4. The method according to claim 1 or 2, wherein: The method further comprises: The first network element receives seventh indication information sent by the terminal, where the seventh indication information is used to indicate on the network side that the terminal has the ability to report the first information.

5. The method according to claim 4, wherein: The seventh indication information is included in the registration request message.

6. The method according to claim 1 or 2, wherein: The method further comprises: The first network element sends eighth indication information to the terminal, where the eighth indication information is used to instruct the terminal to report the first information.

7. A method for determining terminal policy behavior, the method comprising: The terminal sends first information to the first network element, wherein the first information is used to determine the terminal policy behavior executed by the terminal, Among them, the first information includes: third indication information, and the third indication information is used to indicate at least one of the following: the service descriptor TrafficDescriptor of the UE routing selection policy URSP rule corresponding to the protocol data unit PDU session established by the terminal, and the routing selector RSD in the URSP rule corresponding to the PDU session established by the terminal.

8. The method according to claim 7, wherein: The terminal policy behavior includes: The terminal identifies the URSP rule used by the application to transmit data corresponding to the application.

9. The method according to claim 7 or 8, wherein: The first information also includes: The first indication information is used to indicate: a URSP rule being used by the terminal, or a Traffic Descriptor of the URSP rule being used by the terminal.

10. The method according to claim 7 or 8, wherein: The method further comprises: The terminal sends seventh indication information to the first network element, where the seventh indication information is used to indicate to the network side that the terminal has the ability to report the first information.

11. The method according to claim 10, wherein: The seventh indication information is included in the registration request message.

12. The method according to claim 7 or 8, wherein: The method further comprises: The terminal receives eighth indication information sent by the first network element, where the eighth indication information is used to indicate that the terminal is required to report the first information.

13. A device for determining terminal policy behavior, applied to a first network element, the device comprising: An acquiring unit, configured to acquire first information sent by a terminal; a determining unit, configured to determine a terminal policy behavior executed by the terminal according to the first information, Among them, the first information includes: third indication information, and the third indication information is used to indicate at least one of the following: the service descriptor TrafficDescriptor of the UE routing selection policy URSP rule corresponding to the protocol data unit PDU session established by the terminal, and the routing selector RSD in the URSP rule corresponding to the PDU session established by the terminal.

14. The device according to claim 13, wherein: The terminal policy behavior includes: The terminal identifies the URSP rule used by the application to transmit data corresponding to the application.

15. The device according to claim 13 or 14, wherein: The first information also includes: The first indication information is used to indicate: a URSP rule being used by the terminal, or a Traffic Descriptor of the URSP rule being used by the terminal.

16. The device according to claim 13 or 14, wherein: The acquisition unit is further used to receive seventh indication information sent by the terminal, where the seventh indication information is used to indicate on the network side that the terminal has the ability to report the first information.

17. The device according to claim 16, wherein: The seventh indication information is included in the registration request message.

18. The device according to claim 13 or 14, wherein: The device also includes: The sending unit is used to send eighth indication information to the terminal, where the eighth indication information is used to indicate that the terminal is required to report the first information.

19. A network device comprising: A processor and a memory, the memory being used to store a computer program, the processor being used to call and run the computer program stored in the memory to execute the method according to any one of claims 1 to 6.

20. A terminal, comprising: A processor and a memory, the memory being used to store a computer program, the processor being used to call and run the computer program stored in the memory to execute the method as claimed in any one of claims 7 to 12.

21. A chip, comprising: A processor, configured to call and run a computer program from a memory, so that a device equipped with the chip executes a method as claimed in any one of claims 1 to 6, or a method as claimed in any one of claims 7 to 12.

22. A computer-readable storage medium for storing a computer program, wherein the computer program causes a computer to execute the method according to any one of claims 1 to 6, or the method according to any one of claims 7 to 12.

Images