Communication method, communication device, and communication system

Abstract

The application provides a communication method, a communication device and a communication system. The method comprises the following steps: a terminal device receives a first URSP rule, a second URSP rule and indication information, the first URSP rule comprises first associated information of a target service, the second URSP rule comprises second associated information of the target service, and the indication information indicates that redundant transmission is performed for the target service; according to the indication information, a first session of the target service is matched based on the first URSP rule, a second session of the target service is created based on the second URSP rule, the first session and the second session are redundant to each other, and the first associated information and the second associated information are used for associating the first session and the second session. Through the scheme, when the terminal device determines that the data of the target service needs to be redundantly transmitted based on the indication information, the redundant session of the target service is established, instead of establishing the redundant session of the target service in any case, which helps to reduce network resource consumption and device consumption.

Description

Technical Field

[0001] This application relates to the field of wireless communication technology, and in particular to communication methods, communication devices and communication systems. Background Technology

[0002] For services with high reliability requirements, in order to avoid single points of failure during transmission as much as possible, the 3rd generation partnership project (3GPP) defines a redundant protocol data unit (PDU) session mechanism. This mechanism achieves redundant transmission of user plane data between terminal devices and application servers by establishing two independent PDU sessions.

[0003] In the uplink direction, the terminal device sends the same uplink message through two redundant PDU sessions. The application server performs sorting, deduplication, and other processing on the received uplink messages to achieve reliable transmission. In the downlink direction, the application server sends the same downlink message through two redundant PDU sessions. The terminal device performs sorting, deduplication, and other processing on the received downlink messages to achieve reliable transmission.

[0004] How to reduce network resource and equipment overhead for the aforementioned redundant PDU session transmission mechanism remains to be addressed. Summary of the Invention

[0005] This application provides a communication method, communication device, and communication system to reduce network resource consumption and equipment costs.

[0006] In a first aspect, embodiments of this application provide a communication method, which can be executed by a terminal device or a module applied in the terminal device. Taking the execution of the method by a terminal device as an example, the terminal device receives a first URSP rule, a second URSP rule, and indication information. The first UE routing selection policy (URSP) rule includes first association information of the target service, the second URSP rule includes second association information of the target service, and the indication information indicates that redundant transmission is performed for the target service. The terminal device matches a first session of the target service based on the first URSP rule according to the indication information, and creates a second session of the target service based on the second URSP rule. The first session and the second session are redundant to each other, and the first association information and the second association information are used to associate the first session and the second session.

[0007] The above solution, on the one hand, establishes redundant sessions for the target service, which can improve the accuracy of data transmission and increase communication efficiency. On the other hand, when the terminal device determines that redundant transmission of data for the target service is required based on the received indication information, it establishes a redundant session for that target service, rather than establishing a redundant session for the target service in all circumstances. This helps reduce network resource overhead and equipment (such as terminal devices, access network devices, etc.) overhead.

[0008] In one possible implementation, the terminal device receives a first URSP rule, a second URSP rule, and indication information, including: the terminal device receives a policy container from a policy control network element, the policy container including the first URSP rule, the second URSP rule, and the indication information.

[0009] The above scheme, which sends indication information simultaneously with the first and second URSP rules, instead of sending indication information through additional messages, helps reduce signaling overhead.

[0010] In one possible implementation, the terminal device receives a first URSP rule, a second URSP rule, and indication information, including: the terminal device receiving a policy container from a policy control network element, the policy container including the first URSP rule and the second URSP rule; and the terminal device receiving the indication information from an application function network element.

[0011] In one possible implementation, the terminal device matches a first session of the target service based on the first URSP rule, including: the terminal device sending a session modification request message, the session modification request message including the first association information, the session modification request message being used to modify the first session, the first session being used to provide redundant transmission for the target service corresponding to the first URSP rule; the terminal device creating a second session of the target service based on the second URSP rule, including: the terminal device sending a session establishment request message, the session establishment request message including the second association information, the session establishment request message being used to create the second session, the second session being used to provide redundant transmission for the target service corresponding to the second URSP rule.

[0012] The above scheme modifies the already established first session and uses the modified first session as a redundant transmission session. Then, only another new session needs to be established as a redundant transmission session, instead of establishing two new sessions for redundant transmission, which helps to reduce the overhead of establishing sessions.

[0013] In one possible implementation, the terminal device creates a second session for the target service based on the second URSP rule, including: the terminal device sending a session establishment request message, the session establishment request message including the identification information of the first session and the second association information, the session establishment request message being used to create the second session, the first session being used to provide redundant transmission for the target service corresponding to the first URSP rule, and the second session being used to provide redundant transmission for the target service corresponding to the second URSP rule.

[0014] The above scheme utilizes the already established first session as a redundant transmission session, and then only needs to establish another new session as a redundant transmission session, instead of establishing two new sessions for redundant transmission, which helps to reduce the overhead of establishing sessions.

[0015] In one possible implementation, the terminal device matches a first session of the target service based on the first URSP rule, including: the terminal device sending a first session establishment request message, the first session establishment request message including the first association information, the first session establishment request message being used to create the first session, the first session being used to provide redundant transmission for the target service corresponding to the first URSP rule; the terminal device creating a second session of the target service based on the second URSP rule includes: the terminal device sending a second session establishment request message, the second session establishment request message including the second association information, the second session establishment request message being used to create the second session, the second session being used to provide redundant transmission for the target service corresponding to the second URSP rule.

[0016] The above solution establishes two new sessions for redundant transmission, which can help create suitable sessions for redundant transmission for the target service and improve the service experience and quality of service for the target service.

[0017] Secondly, embodiments of this application provide a communication method, which can be executed by a policy control network element or a module applied in the policy control network element. Taking the execution of the method by a policy control network element as an example, the policy control network element obtains service experience information corresponding to a target service; when the service experience information meets preset conditions, the policy control network element generates a first URSP rule and a second URSP rule. The first URSP rule includes first association information of the target service, and the second URSP rule includes second association information of the target service; the policy control network element sends the first URSP rule and the second URSP rule to a terminal device. The first URSP rule is used for matching a first session of the target service, and the second URSP rule is used for creating a second session of the target service. The first session and the second session are redundant, and the first association information and the second association information are used to associate the first session and the second session.

[0018] The above solution, on the one hand, establishes redundant sessions for the target service, which can improve the accuracy of data transmission and increase communication efficiency. On the other hand, when the policy control network element determines that redundant transmission of data for the target service is required based on the received service experience information corresponding to the target service, it triggers the terminal device to establish a redundant session for that target service, rather than establishing a redundant session for the target service under all circumstances. This helps to reduce network resource overhead and equipment (such as terminal devices, access network devices, etc.) overhead.

[0019] In one possible implementation, the service experience information is used to indicate the current service quality of the target service.

[0020] In one possible implementation, the policy control network element sends the first URSP rule and the second URSP rule to the terminal device, including: the policy control network element sends a policy container to the terminal device, the policy container including the first URSP rule and the second URSP rule.

[0021] In one possible implementation, the policy container also includes indication information that indicates redundant transmission for the target service.

[0022] The above scheme, by instructing redundant transmission for the target service through indication information, can accurately trigger the terminal device to perform redundant transmission, thus improving the service experience of the target service. Furthermore, this method sends the indication information simultaneously with the first and second URSP rules, rather than sending the indication information through an additional message, which helps reduce signaling overhead.

[0023] In one possible implementation, the policy control network element obtains service experience information corresponding to the target service, including: the policy control network element sending a request message to the data collection network element, the request message including the identifier information of the target (DNN, S-NSSAI) combination or the session under the target (DNN, S-NSSAI) combination corresponding to the target service, the request message being used to request the service experience information corresponding to the target service; and the policy control network element receiving the service experience information from the data collection network element.

[0024] In one possible implementation, the request message also includes an application identifier, which is used to identify the target service.

[0025] In one possible implementation, the business experience information meets preset conditions, including at least one of the following: The packet loss rate in the service experience information shall not be less than the packet loss rate in the requirement parameters of the target service; The latency in the service experience information shall not be less than the latency in the requirement parameters of the target service; The jitter in the service experience information shall not be less than the jitter in the requirement parameters of the target service; The bandwidth in the service experience information is not greater than the bandwidth in the requirement parameters of the target service.

[0026] The above scheme compares the service experience information of the target service with the requirement parameters of the target service to determine whether the service experience information of the target service meets the requirements, which helps to accurately determine whether redundant session transmission of the target service needs to be established.

[0027] In one possible implementation, the strategy control network element receives the demand parameters of the target service from the application function network element.

[0028] The above solution receives the target service requirement parameters from the application function network element, which can ensure the accuracy of the requirement parameters.

[0029] In one possible implementation, the requirement parameters of the target service are pre-configured on the policy control network element.

[0030] The above solution pre-configures the target service's requirements parameters on the policy control network element, which helps to quickly obtain the target service's requirements parameters.

[0031] In one possible implementation, based on any of the implementation methods of the first or second aspect described above, the first association information includes a first redundant sequence number, and the second association information includes a second redundant sequence number; or, the first association information and the second association information include a session pair identifier; or, the first association information includes a first redundant sequence number and a session pair identifier, and the second association information includes a second redundant sequence number and the session pair identifier.

[0032] Thirdly, embodiments of this application provide a communication device, which can be a terminal device or a chip for a terminal device. This device has the function of implementing any of the methods described in the first aspect. This function can be implemented in hardware or by hardware executing corresponding software. The hardware or software includes one or more modules corresponding to the above-described function.

[0033] Fourthly, embodiments of this application provide a communication device, which can be a policy control network element or a chip for a policy control network element. This device has the function of implementing any of the implementation methods of the second aspect described above. This function can be implemented in hardware or by hardware executing corresponding software. The hardware or software includes one or more modules corresponding to the above-described functions.

[0034] Fifthly, embodiments of this application provide a communication device including a processor coupled to a memory, the processor being configured to invoke a program stored in the memory to execute any of the implementation methods described in the first to second aspects above. The memory may be located within or outside the device. Furthermore, the processor may be one or more.

[0035] In a sixth aspect, embodiments of this application provide a communication device, including a processor and a memory; the memory is used to store computer instructions, and when the device is running, the processor executes the computer instructions stored in the memory to cause the device to perform any of the implementation methods in the first to second aspects described above.

[0036] In a seventh aspect, embodiments of this application provide a communication apparatus, including units or means for performing various steps of any of the implementation methods in the first to second aspects described above.

[0037] Eighthly, embodiments of this application provide a communication device, including a processor and an interface circuit. The processor is configured to communicate with other devices via the interface circuit and execute any of the implementation methods described in the first to second aspects. The processor may include one or more devices.

[0038] Ninthly, embodiments of this application also provide a computer-readable storage medium storing instructions that, when executed on a communication device, cause any of the implementation methods of the first to second aspects described above to be performed.

[0039] In a tenth aspect, embodiments of this application also provide a computer program product, which includes a computer program or instructions that, when executed by a communication device, cause any of the implementation methods in the first to second aspects described above to be executed.

[0040] Eleventhly, embodiments of this application also provide a chip system, including: a processor, configured to execute any of the implementation methods of the first to second aspects described above.

[0041] In a twelfth aspect, embodiments of this application also provide a communication system, which includes a policy control network element for executing any implementation method of the second aspect described above, and a data collection network element for sending service experience information corresponding to a target service to the policy control network element. Attached Figure Description

[0042] Figure 1 A schematic diagram of a communication system provided in an embodiment of this application; Figure 2 This is a schematic diagram of a 5G network architecture based on a service-oriented architecture. Figure 3This is a schematic diagram of a 5G network architecture based on a point-to-point interface. Figure 4 A flowchart illustrating a communication method provided in an embodiment of this application; Figure 5 A flowchart illustrating a communication method provided in an embodiment of this application; Figure 6 A schematic diagram of a communication device provided in an embodiment of this application; Figure 7 This is a schematic diagram of a communication device provided in an embodiment of this application. Detailed Implementation

[0043] To reduce network resource and equipment costs, such as Figure 1 As shown, this application provides a communication system, which includes a policy control network element and a data collection network element. Optionally, the communication system also includes an application function network element.

[0044] Figure 1 The system shown can be used in Figure 2 or Figure 3 The fifth-generation (5G) network architecture shown can, of course, also be used in future network architectures, such as the sixth-generation (6G) network architecture, etc., and this application does not limit it.

[0045] A data collection network element is used to send service experience information corresponding to a target service to a policy control network element; the policy control network element is used to obtain the service experience information; when the service experience information meets preset conditions, a first URSP rule and a second URSP rule are generated, the first URSP rule includes the first association information of the target service, and the second URSP rule includes the second association information of the target service; the first URSP rule and the second URSP rule are sent to the terminal device, the first URSP rule is used for matching the first session of the target service, and the second URSP rule is used for creating the second session of the target service, the first session and the second session are redundant, and the first association information and the second association information are used to associate the first session and the second session.

[0046] In one possible implementation, the policy control network element is used to send the first URSP rule and the second URSP rule to the terminal device, specifically including: sending a policy container to the terminal device, the policy container including the first URSP rule and the second URSP rule.

[0047] In one possible implementation, the policy container also includes indication information that indicates redundant transmission for the target service.

[0048] In one possible implementation, the policy control network element is used to obtain service experience information corresponding to the target service, specifically including: sending a request message to the data collection network element, the request message including the identification information of the target (DNN, S-NSSAI) combination or the session under the target (DNN, S-NSSAI) combination corresponding to the target service, the request message being used to request the service experience information corresponding to the target service; and receiving the service experience information from the data collection network element.

[0049] The interactions between various network elements in the system, as well as the specific execution, can be referred to in the following method implementation examples, which will not be repeated here. To address the challenges of wireless broadband technology and maintain the leading advantage of 3GPP networks, the 3GPP standards group has developed a Next Generation System architecture, known as the 5G network architecture. This architecture not only supports access to the 5G core network (CN) using radio access technologies defined by the 3GPP standards group (such as Long Term Evolution (LTE) and 5G Radio Access Network (RAN) technologies), but also supports access to the core network using non-3GPP access technologies through non-3GPP interworking functions (N3IWF) or next-generation packet data gateways (ngPDG).

[0050] Figure 2 This is a schematic diagram of a 5G network architecture based on a service-oriented architecture. Figure 2The 5G network architecture shown may include access network equipment and core network equipment. Terminal devices access the data network (DN) through access network equipment and core network equipment. The core network equipment includes, but is not limited to, some or all of the following network elements: authentication server function (AUSF) network element (not shown in the figure), unified data management (UDM) network element, unified data repository (UDR) network element, network repository function (NRF) network element (not shown in the figure), network exposure function (NEF) network element (not shown in the figure), application function (AF) network element, policy control function (PCF) network element, access and mobility management function (AMF) network element, session management function (SMF) network element, user plane function (UPF) network element, and binding support function (BSF) network element (not shown in the figure).

[0051] Terminal devices can be user equipment (UE), mobile stations, mobile terminal devices, etc. They can be widely used in various scenarios, such as device-to-device (D2D), vehicle-to-everything (V2X) communication, machine-type communication (MTC), the Internet of Things (IoT), virtual reality, augmented reality, industrial control, autonomous driving, telemedicine, smart grids, smart furniture, smart offices, smart wearables, smart transportation, smart cities, etc. Terminal devices can include mobile phones, tablets, computers with wireless transceiver capabilities, wearable devices, vehicles, urban air mobility vehicles (such as drones, helicopters, etc.), ships, robots, robotic arms, smart home devices, etc.

[0052] Access network equipment can be either wireless or wired. Wireless access network equipment includes 3GPP access network equipment, untrusted non-3GPP access network equipment, and trusted non-3GPP access network equipment. 3GPP access network equipment includes, but is not limited to: evolved NodeBs (eNodeBs) in LTE, next-generation NodeBs (gNBs) in 5G mobile communication systems, base stations in future mobile communication systems, or modules or units that perform some base station functions, such as central units (CUs) and distributed units (DUs). Untrusted non-3GPP access network equipment includes, but is not limited to: untrusted non-3GPP access gateways or N3IWF devices, untrusted wireless local area network (WLAN) access points (APs), switches, and routers. Trusted non-3GPP access network equipment includes, but is not limited to: trusted non-3GPP access gateways, trusted WLAN APs, switches, and routers. Wired access network equipment includes, but is not limited to: wireline access gateways, fixed-line telephone network equipment, switches, and routers.

[0053] Access network equipment and terminal equipment can be fixed or mobile. They can be deployed on land, including indoors or outdoors, handheld or vehicle-mounted; they can also be deployed on water; and they can be deployed in the air on aircraft, balloons, and satellites. The embodiments of this application do not limit the application scenarios of the access network equipment and terminal equipment.

[0054] The AMF (Automatic Mobility Management) network element includes functions such as mobility management and access authentication / authorization. In addition, it is responsible for transmitting user policies between terminal devices and the PCF (Programmable Default Function).

[0055] The SMF network element includes functions such as performing session management, executing control policies issued by the PCF network element, selecting the UPF network element, and allocating Internet Protocol (IP) addresses to terminal devices.

[0056] UPF network elements include functions such as user plane data forwarding, session / flow-based billing statistics, and bandwidth limiting.

[0057] UDM network elements include functions such as managing contracted data and authorizing user access.

[0058] UDR includes functions for storing and retrieving data of various types, such as contract data, policy data, and application data.

[0059] NEF network elements are used to support the opening of capabilities and events.

[0060] AF (Application Provider) network elements convey application-side requests to the network side, such as QoS requirements or user state event subscriptions. AF can be a third-party functional entity or an application service deployed by the operator, such as the IP Multimedia Subsystem (IMS) voice call service. AF network elements include those within the core network (i.e., the operator's AF network elements) and third-party AF network elements (such as an enterprise's application server).

[0061] PCF (Policy Control Function) network elements include policy control functions responsible for session and service flow-level billing, QoS bandwidth guarantee, mobility management, and terminal device policy decisions. PCF network elements include access and mobility management policy control function (AM PCF) network elements and session management policy control function (SM PCF) network elements. AM PCF network elements are used to formulate AM policies and user policies for terminal devices; AM PCF network elements can also be referred to as policy control network elements providing services to terminal devices (PCF for aUE). SM PCF network elements are used to formulate session management policies (SM policies); SM PCF network elements can also be referred to as policy control network elements providing services to a PDU session (PCF for a PDU session).

[0062] NRF network elements can be used to provide network element discovery functionality, providing network element information corresponding to the network element type based on requests from other network elements. NRF network elements also provide network element management services, such as network element registration, updates, deregistration, and network element status subscription and push.

[0063] BSF network elements can provide functions such as BSF service registration / deregistration / update, connection detection with NRF network elements, session binding information creation, terminal device information acquisition, and session binding information query for duplicate IP addresses.

[0064] The AUSF network element is responsible for authenticating users to determine whether to allow users or devices to access the network.

[0065] A Domain Provider (DN) is a network located outside of the carrier's network. A carrier's network can connect to multiple DNs, and various services can be deployed on a DN, providing data and / or voice services to terminal devices. For example, a DN might be the private network of a smart factory. Sensors installed in the workshop can act as terminal devices, and a control server for these sensors is deployed within the DN. The control server provides services to the sensors. Sensors can communicate with the control server, receive instructions from it, and transmit the collected sensor data back to the control server accordingly. Another example is a DN serving as an internal office network for a company. Employees' mobile phones or computers can act as terminal devices, accessing information and data resources on the company's internal office network.

[0066] Figure 2 Npcf, Nudr, Nudm, Naf, Namf, and Nsmf are the service interfaces provided by PCF, UDR, UDM, AF, AMF, and SMF, respectively, used to invoke the corresponding service operations. N1, N2, N3, N4, and N6 are interface sequence numbers, and their meanings are as follows: 1) N1: The interface between the AMF network element and the terminal device, which can be used to transmit non-access stratum (NAS) signaling (such as QoS rules from the AMF network element) to the terminal device.

[0067] 2) N2: The interface between the AMF network element and the access network equipment, which can be used to transmit radio bearer control information from the core network side to the access network equipment.

[0068] 3) N3: The interface between the access network equipment and the UPF network element, mainly used to transmit uplink and downlink user plane data between the access network equipment and the UPF network element.

[0069] 4) N4: The interface between SMF network elements and UPF network elements. It can be used to transmit information between the control plane and the user plane, including the distribution of forwarding rules, QoS rules, traffic statistics rules, etc. from the control plane to the user plane, as well as the reporting of information from the user plane.

[0070] 5) N6: The interface between the UPF network element and the DN, used to transmit uplink and downlink user data streams between the UPF network element and the DN.

[0071] Figure 3 This is a schematic diagram of a 5G network architecture based on a point-to-point interface. For a description of the functions of the network elements, please refer to [reference needed]. Figure 2 The functions of the corresponding network elements will not be described in detail here. Figure 3 and Figure 2 The main difference is: Figure 2 The interfaces between the various control plane network elements are service-oriented interfaces. Figure 3 The interfaces between the various control plane network elements are point-to-point interfaces.

[0072] exist Figure 3 In the architecture shown, the interface names and functions between the various network elements are as follows: 1) The meanings of interfaces N1, N2, N3, N4 and N6 can be found in the previous description.

[0073] 2) N5: The interface between the AF network element and the PCF network element, which can be used for application service request distribution and network event reporting.

[0074] 3) N7: The interface between PCF network elements and SMF network elements, which can be used to issue PDU session granularity and service data flow granularity control policies.

[0075] 4) N8: The interface between the AMF network element and the UDM network element. It can be used by the AMF network element to obtain access and mobility management related subscription data and authentication data from the UDM network element, as well as by the AMF to register terminal device mobility management related information with the UDM.

[0076] 5) N9: User plane interface between UPF network elements, used to transmit uplink and downlink user data streams between UPF network elements.

[0077] 6) N10: The interface between SMF network elements and UDM network elements. It can be used for SMF network elements to obtain session management-related subscription data from UDM network elements, and for SMF network elements to register terminal device session-related information with UDM.

[0078] 7) N11: The interface between SMF network elements and AMF network elements. It can be used to transmit PDU session tunnel information between access network devices and UPF network elements, transmit control messages sent to terminal devices, and transmit radio resource control information sent to access network devices.

[0079] 8) N15: The interface between PCF network elements and AMF network elements, which can be used to issue terminal equipment policies and access control related policies.

[0080] 9) N35: Interface between UDM network element and UDR network element, which can be used by UDM network element to obtain user subscription data information from UDR network element.

[0081] 10) N36: The interface between PCF network elements and UDR network elements, which can be used by PCF network elements to obtain policy-related contract data and application data related information from UDR network elements.

[0082] It is understood that the aforementioned network element or function can be a network component in a hardware device, a software function running on dedicated hardware, or a virtualized function instantiated on a platform (e.g., a cloud platform). Optionally, the aforementioned network element or function can be implemented by one device, multiple devices working together, or a functional module within a single device; this application embodiment does not specifically limit this.

[0083] The policy control network element and application function network element in this application can be the AM PCF network element and AF network element in a 5G system, respectively, or they can be network elements with the functions of the aforementioned AM PCF network element and AF network element in future communications such as 6G networks. This application does not limit them in this way. In the embodiments of this application, the AM PCF network element and AF network element are described as examples of policy control network element and application function network element, respectively. Furthermore, the AM PCF network element and AF network element are abbreviated as AM PCF and AF, respectively.

[0084] The data collection network element in this application may be a network data analysis function (NWDAF) network element (NWDAF for short), an SM PCF network element (SM PCF for short), or other network elements.

[0085] Figure 4 This is a flowchart illustrating a communication method provided in an embodiment of this application. Figure 4 Let's take 5G as an example.

[0086] The method includes the following steps: Step 401: AM PCF obtains the service experience information corresponding to the target service.

[0087] The service experience information is used to indicate the current service quality of the target service. This service experience information includes one or more parameters such as packet loss rate, latency, jitter, or bandwidth. The target service can be Ultra-Reliable and Low-Latency Communication (uRLLC) service.

[0088] The method by which the AM PCF obtains service experience information corresponding to the target service can be as follows: the AM PCF sends a request message to the data collection network element, which requests the service experience information corresponding to the target service, and then the AM PCF receives the service experience information from the data collection network element. This request message can be a subscription request message or other messages; this application does not limit the specific message.

[0089] In one implementation method, the request message includes a target (DNN, S-NSSAI) combination corresponding to the target service. This target (DNN, S-NSSAI) combination can establish a session for the target service or sessions for other services. After receiving the request message, the NWDAF collects session data under the target (DNN, S-NSSAI) combination. For example, it can collect session data from one or more devices, such as network management devices, UPF, SMF, AF, or terminal devices. Then, it analyzes or summarizes the collected data to obtain service experience information corresponding to the target service. This service experience information can be obtained based on session data for the target service and / or session data for other services. Here, DNN is short for datanetwork name, and S-NSSAI is short for single network slice selection assistance information. The session described in this application embodiment can be a PDU session, an Ethernet session, or other sessions; this application is not limited to these.

[0090] In another implementation, the request message includes the identifier information of the session under the target (DNN, S-NSSAI) combination. This session may include a session of the target service or sessions of other services. After receiving the request message, the NWDAF collects the session data, for example, it can collect session data from one or more devices such as network management devices, UPF, SMF, AF, or terminal devices. Then, it analyzes or summarizes the collected data to obtain the service experience information corresponding to the target service. This service experience information may be obtained based on the session data of the target service and / or the session data of other services.

[0091] In another implementation, the request message includes a target (DNN, S-NSSAI) combination corresponding to the target service, and an application identifier used to identify the target service. Upon receiving the request message, the NWDAF collects session data for the target service under the target (DNN, S-NSSAI) combination. For example, session data can be collected from one or more devices, such as network management devices, UPF, SMF, AF, or terminal devices. The collected data is then analyzed or summarized to obtain service experience information corresponding to the target service. This service experience information can be obtained based on the session data of the target service.

[0092] In another implementation, the request message includes identification information of the session under the target (DNN, S-NSSAI) combination, as well as an application identifier used to identify the target service. The session may include sessions of the target service or sessions of other services. After receiving the request message, the NWDAF collects session data of the target service. For example, it can collect session data from one or more devices, such as network management devices, UPF, SMF, AF, or terminal devices. Then, it analyzes or summarizes the collected data to obtain service experience information corresponding to the target service. This service experience information can be obtained based on the session data of the target service.

[0093] Step 402: When the business experience information meets the preset conditions, AM PCF generates the first URSP rule and the second URSP rule.

[0094] Step 402 can also be understood as AM PCF determining that the service experience information meets the preset conditions, and then generating the first URSP rule and the second URSP rule.

[0095] In one implementation method, the business experience information meets preset conditions, including at least one of the following: 1) The packet loss rate in the business experience information is not less than the packet loss rate in the target business's requirement parameters; 2) The latency in the business experience information is not less than the latency in the target business's requirement parameters; 3) The jitter in the business experience information is not less than the jitter in the target business's requirement parameters; 4) The bandwidth in the service experience information is not greater than the bandwidth in the target service's requirement parameters.

[0096] If one or more of the above conditions 1) to 4) are met, it indicates that the current service experience of the target service may not be very good and has not met the needs of the target service. Therefore, it is necessary to trigger the establishment of redundant sessions to improve service quality and service experience.

[0097] The target service's requirements parameters can be sent from the AF to the AM PCF, or pre-configured on the AM PCF.

[0098] The first URSP rule includes the first associated information of the target business, and the second URSP rule includes the second associated information of the target business.

[0099] In one implementation method, a first URSP rule includes first flow description information and first routing description information, wherein the first routing description information includes the first association information. A second URSP rule includes second flow description information and second routing description information, wherein the second routing description information includes the second association information. The first flow description information and the second flow description information are different, and both the first flow description information and the second flow description information can match the target service. The first routing description information and the second routing description information may be partially the same or completely different.

[0100] Step 403: AM PCF sends the first URSP rule and the second URSP rule to the terminal device. Correspondingly, the terminal device receives the first URSP rule and the second URSP rule.

[0101] In one implementation, the AM PCF sends a policy container to the terminal device during the UE Configuration Update procedure. This policy container includes a first URSP rule and a second URSP rule. This policy container can be a UE policy container.

[0102] Step 404: The terminal device matches the first session of the target service based on the first URSP rule, and creates the second session of the target service based on the second URSP rule.

[0103] The first session and the second session are redundant to each other, that is, the first session is a redundant session of the second session, and the second session is a redundant session of the first session. Both the first session and the second session are used for redundant transmission of the target service, and the first session and the second session are used to transmit the same data of the target service.

[0104] The first URSP rule is used for matching the first session of the target service, and the second URSP rule is used for creating the second session of the target service.

[0105] The first and second association information are used to associate a first session and a second session. In one implementation, the first association information includes a first redundant sequence number (RSN), and the second association information includes a second redundant sequence number; the first and second redundant sequence numbers may be the same or different. In another implementation, the first and second association information include the same session pair ID. In yet another implementation, the first association information includes a first redundant sequence number and a session pair ID, and the second association information includes a second redundant sequence number and a session pair ID; the first and second redundant sequence numbers may be the same or different, and both the first and second association information include the same session pair ID.

[0106] Prior to step 404, the terminal device also determines that a redundant session needs to be created. The method for triggering the terminal device to create a redundant session can be any one of the following methods one to three.

[0107] In Method 1, in step 403 above, in the configuration update process of the terminal device, the AM PCF sends not only the first URSP rule and the second URSP rule, but also an indication message. This indication message indicates whether to perform redundant transmission for the target service or to establish a redundant session for the target service. Based on this indication message, the terminal device determines that a redundant session needs to be created.

[0108] In one implementation method, the indication information can be carried in a policy container and sent to the terminal device. That is, AM PCF sends a policy container to the terminal device, and the policy container includes a first URSP rule, a second URSP rule, and indication information.

[0109] Method 2: The terminal device determines whether a redundant session needs to be created based on the first association information in the first URSP rule and / or the second association information in the second URSP rule.

[0110] For example, if the terminal device is pre-configured with configuration information that instructs the terminal device to perform a redundant session establishment or modification process based on the received association information, then after receiving the first URSP rule and the second URSP rule, the terminal device can determine whether a redundant session needs to be created based on the first association information in the first URSP rule and / or the second association information in the second URSP rule.

[0111] Method 3: After step 402, the AM PCF also sends an indication message to the AF, which indicates that redundant transmission should be performed for the target service or that a redundant session should be established for the target service. Then, the AF sends an indication message to the user-facing terminal device, which indicates that redundant transmission should be performed for the target service or that a redundant session should be established for the target service. The terminal device determines whether a redundant session needs to be created based on the received indication message.

[0112] The indication information received by the AF from the AM PCF has the same function as the indication information sent by the AF to the terminal device, but the implementation methods can be the same or different.

[0113] After determining that redundant sessions need to be created, the terminal device matches the first session of the target service based on the first URSP rule and creates the second session of the target service based on the second URSP rule. Different implementation methods are described below.

[0114] Method A: The terminal device sends a session modification request message, which includes first association information. This message modifies a first session, which provides redundant transmission for the target service corresponding to the first URSP rule. Simultaneously, the terminal device sends a session establishment request message, which includes second association information. This message creates a second session, which provides redundant transmission for the target service corresponding to the second URSP rule.

[0115] Based on this method, a first session for the target service has been created on the terminal device. The terminal device triggers a modification process for the first session, sending first association information to the SMF through this process. The SMF then sends the first association information to the access network device. The terminal device also triggers a second session establishment process, sending second association information to the SMF through this process. The SMF then sends the second association information to the access network device. The access network device, based on the first and second association information, associates the first and second sessions as redundant sessions and triggers the establishment of a redundant access network link. In the above scheme, the SMF corresponding to the first session and the SMF corresponding to the second session can be different SMF instances; this invention does not limit this.

[0116] Method B: The terminal device sends a session establishment request message. The session establishment request message includes the identification information of the first session and the second association information. The session establishment request message is used to create a second session. The first session is used to provide redundant transmission for the target service corresponding to the first URSP rule, and the second session is used to provide redundant transmission for the target service corresponding to the second URSP rule.

[0117] Based on this method, a first session for the target service has already been created on the terminal device. The terminal device triggers the establishment process for the second session, sending the identification information and second association information of the first session to the SMF through this process. The SMF then sends the identification information and second association information of the first session to the access network device. The access network device, based on the identification information and second association information of the first session, associates the already established first session with the newly established second session as a redundant session and triggers the establishment of a redundant access network link.

[0118] In method C, the terminal device sends a first session establishment request message, which includes first association information. This first session is used to create a first session, and the first session provides redundant transmission for the target service corresponding to the first URSP rule. The terminal device then sends a second session establishment request message, which includes second association information. This second session is used to create a second session, and the second session provides redundant transmission for the target service corresponding to the second URSP rule.

[0119] Based on this method, the terminal device triggers a first session establishment process, through which it sends first association information to the SMF, and the SMF sends the first association information to the access network device. The terminal device then triggers a second session establishment process, through which it sends second association information to the SMF, and the SMF sends the second association information to the access network device. The access network device, based on the first and second association information, associates the newly established first session and the newly established second session as redundant sessions and triggers the establishment of a redundant access network link.

[0120] The above solution, on the one hand, establishes redundant sessions for the target service, which can improve the accuracy of data transmission and increase communication efficiency. On the other hand, when the AM PCF determines that redundant transmission of data for the target service is required based on the received service experience information corresponding to the target service, it triggers the terminal device to establish a redundant session for that target service, rather than establishing a redundant session for the target service under all circumstances. This helps to reduce network resource overhead and equipment (such as terminal devices, access network devices, etc.) overhead.

[0121] Figure 5 This is a flowchart illustrating a communication method provided in an embodiment of this application. Figure 5 The embodiments are as described above. Figure 4 A specific example of an embodiment is provided, which uses a PDU session as an example for illustration. The method includes the following steps: Step 501: The AF sends a request message to the AM PCF, which includes the identification information of the target service, the identification information of the terminal device, and indication information. The AM PCF then receives the request message.

[0122] The identification information of the target service is used to identify the target service. The target service can be a uRLLC service.

[0123] The identification information of the terminal device is used to identify the terminal device, such as SUPI, generic public subscription identifier (GPSI), or user group identifier.

[0124] This instruction indicates that a redundant PDU session mechanism should be dynamically enabled for the target service.

[0125] Optionally, the request message may also include demand parameters for the target service, which may include one or more of packet loss rate, latency, jitter, or bandwidth. These demand parameters for the target service can be used to assist AM PCF in deciding whether to trigger the redundant PDU session mechanism.

[0126] Step 501 is an optional step.

[0127] Step 502, AM PCF senses PDU session creation event.

[0128] For example, the AM PCF sends a subscription request message to the AMF, SMF, BSF, or SM PCF. The subscription request message includes the identification information of the terminal device and the target (DNN, S-NSSAI) combination corresponding to the target service. The subscription request message is used to subscribe to the PDU session creation event of the terminal device under the target (DNN, S-NSSAI) combination.

[0129] Among them, under the target (DNN, S-NSSAI) combination corresponding to the target service, one or more PDU sessions can be created for the terminal device. These one or more PDU sessions may include PDU sessions corresponding to the target service or PDU sessions corresponding to other services.

[0130] When a terminal device creates a PDU session under the target (DNN, S-NSSAI) combination, the AMF, SMF, BSF, or SMPCF notifies the AM PCF that the terminal device has created a PDU session under the target (DNN, S-NSSAI) combination. This created PDU session can include the PDU session corresponding to the target service, or it can include PDU sessions corresponding to other services.

[0131] Step 502 is an optional step.

[0132] Step 503: The AM PCF sends a subscription request message to the NWDAF. This subscription request message includes the service experience analysis event identifier and the terminal device identifier, as well as the identifier of the target (DNN, S-NSSAI) combination or PDU session. The NWDAF then receives this subscription request message.

[0133] When step 502 is executed, and in step 502 the AM PCF detects that the terminal device has created a PDU session under the target (DNN, S-NSSAI) combination, the subscription request message includes the identification information of the PDU session created by the terminal device under the target (DNN, S-NSSAI) combination.

[0134] If step 502 above is not performed, or if step 502 above is performed but AM PCF does not detect that the terminal device has created a PDU session under the target (DNN, S-NSSAI) combination, then the subscription request message includes the target (DNN, S-NSSAI) combination.

[0135] Optionally, the subscription request message may also include an application identifier used to identify the target service.

[0136] Step 504: The NWDAF sends the service experience information corresponding to the target service to the AM PCF. Correspondingly, the AM PCF receives the service experience information corresponding to the target service.

[0137] Based on the subscription request message sent by AM PCF, NWDAF obtains data related to the PDU session from one or more devices, including network management devices, UPF, SMF, AF, or terminal devices. Then, it analyzes the obtained data and generates service experience information corresponding to the target service. This service experience information includes one or more parameters such as packet loss rate, latency, jitter, or bandwidth.

[0138] For details on the specific implementation method of NWDAF data collection, please refer to [link / reference]. Figure 4 The description of step 401 in the embodiments will not be repeated here.

[0139] Step 505: When the service experience information meets the preset conditions, AM PCF generates a first URSP rule and a second URSP rule corresponding to redundant transmission. The first URSP rule includes first association information, and the second URSP rule includes second association information.

[0140] In its implementation, the AM PCF determines whether redundant transmission is needed based on the target service's requirement parameters and the corresponding service experience information from the NWDAF. If redundant transmission is determined to be needed, the AM PCF generates a first URSP rule and a second URSP rule. The target service's requirement parameters can be obtained through step 502 above, or pre-configured on the AM PCF.

[0141] For example, AM PCF determines that redundant transmission is required when one or more of the following conditions are met: 1) The packet loss rate in the business experience information is not less than the packet loss rate in the target business's requirement parameters; 2) The latency in the business experience information is not less than the latency in the target business's requirement parameters; 3) The jitter in the business experience information is not less than the jitter in the target business's requirement parameters; 4) The bandwidth in the service experience information is not greater than the bandwidth in the target service's requirement parameters.

[0142] Step 506: AM PCF sends the first URSP rule and the second URSP rule to the terminal device. Correspondingly, the terminal device receives the first URSP rule and the second URSP rule.

[0143] In its implementation, AM PCF can send the first URSP rule and the second URSP rule to the terminal device through the terminal device configuration update process. For example, in the configuration update process, AM PCF sends a Namf_Communication_N1N2MessageTransfer message to the terminal device, which carries the first URSP rule and the second URSP rule.

[0144] In its specific implementation, the message sent by AM PCF to the terminal device includes a policy container, which contains a first URSP rule and a second URSP rule.

[0145] Step 507: The terminal device matches the first PDU session of the target service based on the first URSP rule, and creates the second PDU session of the target service based on the second URSP rule.

[0146] Before step 507, the terminal device determines that a redundant PDU session needs to be created. The method for triggering the terminal device to create a redundant PDU session can be referred to the description in step 404 of embodiment 4, and will not be repeated here.

[0147] The specific implementation method of the terminal device matching the first PDU session of the target service based on the first URSP rule and creating the second PDU session of the target service based on the second URSP rule can also refer to the description in step 404 of embodiment 4, and will not be repeated here.

[0148] The above scheme, on the one hand, establishes redundant PDU sessions for the target service, which can improve the accuracy of data transmission and increase communication efficiency. On the other hand, when the AM PCF determines that redundant transmission of data for the target service is required based on the received service experience information, it triggers the terminal device to establish a redundant PDU session for that target service, rather than establishing a redundant PDU session for the target service under all circumstances. This helps reduce network resource overhead and equipment (such as terminal devices, access network devices, etc.) overhead.

[0149] In the above scheme, the AM PCF subscribes to the service experience information corresponding to the target service from the NWDAF. In another implementation, the AM PCF can also subscribe to the service experience information corresponding to the target service from the SM PCF. For example, the AM PCF sends a subscription request message to the SMPCF. This subscription request message includes the terminal device's identification information, as well as the identification information of the target (DNN, S-NSSAI) combination or PDU session. Optionally, it also includes an application identifier for identifying the target service. Then, the SMPCF collects the service experience information corresponding to the target service based on the target (DNN, S-NSSAI) combination, or based on the PDU session's identification information, or based on the target (DNN, S-NSSAI) combination and the application identifier, or based on the PDU session's identification information and the application identifier. The service experience information corresponding to the target service is obtained by the SM PCF based on the PDU session data of the target service and / or the PDU session data of other services. Then, the SM PCF sends the service experience information corresponding to the target service to the AM PCF.

[0150] It is understood that, in order to achieve the functions in the above embodiments, the AM PCF or terminal device includes hardware structures and / or software modules corresponding to perform each function. Those skilled in the art should readily recognize that, based on the units and method steps described in conjunction with the embodiments disclosed in this application, this application can be implemented in hardware or a combination of hardware and computer software. Whether a function is executed in hardware or by computer software driving hardware depends on the specific application scenario and design constraints of the technical solution.

[0151] Figure 6 and Figure 7 The diagram illustrates the possible communication devices provided in the embodiments of this application. These communication devices can be used to implement the functions of the AM PCF or terminal device in the above method embodiments, and thus can also achieve the beneficial effects of the above method embodiments. In the embodiments of this application, the communication device can be an AM PCF or terminal device, or it can be a module (such as a chip) applied to an AM PCF or terminal device.

[0152] Figure 6 The communication device 600 shown includes a processing unit 610 and a transceiver unit 620. The communication device 600 is used to implement the above-described... Figure 4 or Figure 5 The method embodiments shown illustrate the functions of the AM PCF or terminal device.

[0153] When the communication device 600 is used to implement Figure 4 or Figure 5In the method embodiment shown, the terminal device has the following functions: a transceiver unit 620 is used to receive a first URSP rule, a second URSP rule, and indication information. The first URSP rule includes first association information of the target service, the second URSP rule includes second association information of the target service, and the indication information indicates that redundant transmission should be performed for the target service. A processing unit 610 is used to match a first session of the target service based on the first URSP rule according to the indication information, and to create a second session of the target service based on the second URSP rule. The first session and the second session are redundant to each other, and the first association information and the second association information are used to associate the first session and the second session.

[0154] When the communication device 600 is used to implement Figure 4 or Figure 5 In the method embodiment shown, the PCF function includes a processing unit 610, which is used to obtain service experience information corresponding to the target service; when the service experience information meets preset conditions, it generates a first URSP rule and a second URSP rule. The first URSP rule includes first association information of the target service, and the second URSP rule includes second association information of the target service. A transceiver unit 620 is used to send the first URSP rule and the second URSP rule to the terminal device. The first URSP rule is used for matching the first session of the target service, and the second URSP rule is used for creating the second session of the target service. The first session and the second session are redundant to each other, and the first association information and the second association information are used to associate the first session and the second session.

[0155] For a more detailed description of the processing unit 610 and the transceiver unit 620, please refer to [link / reference needed]. Figure 4 or Figure 5 The relevant descriptions in the method embodiments shown are directly obtained and will not be repeated here.

[0156] Figure 7 The communication device 700 shown includes a processor 710 and an interface circuit 720. The processor 710 and the interface circuit 720 are coupled to each other. It is understood that the interface circuit 720 can be a transceiver or an input / output interface. Optionally, the communication device 700 may also include a memory 730 for storing instructions executed by the processor 710, or storing input data required by the processor 710 to execute instructions, or storing data generated after the processor 710 executes instructions.

[0157] When the communication device 700 is used to implement Figure 4 or Figure 5 In the method shown, the processor 710 is used to implement the functions of the processing unit 610, and the interface circuit 720 is used to implement the functions of the transceiver unit 620.

[0158] It is understood that the processor in the embodiments of this application may be a Central Processing Unit (CPU), or other general-purpose processors, digital signal processors (DSPs), application-specific integrated circuits (ASICs), field-programmable gate arrays (FPGAs), or other programmable logic devices, transistor logic devices, hardware components, or any combination thereof. A general-purpose processor may be a microprocessor or any conventional processor.

[0159] The method steps in the embodiments of this application can be implemented in hardware or by a processor executing software instructions. The software instructions can consist of corresponding software modules, which can be stored in random access memory, flash memory, read-only memory, programmable read-only memory, erasable programmable read-only memory, electrically erasable programmable read-only memory, registers, hard disks, portable hard disks, CD-ROMs, or any other form of storage medium known in the art. An exemplary storage medium is coupled to a processor, enabling the processor to read information from and write information to the storage medium. Of course, the storage medium can also be a component of the processor. The processor and storage medium can reside in an ASIC. Furthermore, the ASIC can reside in a base station or terminal device. Alternatively, the processor and storage medium can exist as discrete components in the base station or terminal device.

[0160] In the above embodiments, implementation can be achieved entirely or partially through software, hardware, firmware, or any combination thereof. When implemented using software, it can be implemented entirely or partially in the form of a computer program product. The computer program product includes one or more computer programs or instructions. When the computer program or instructions are loaded and executed on a computer, the processes or functions described in the embodiments of this application are performed entirely or partially. The computer can be a general-purpose computer, a special-purpose computer, a computer network, a base station, a user equipment, or other programmable device. The computer program or instructions can be stored in a computer-readable storage medium or transferred from one computer-readable storage medium to another. For example, the computer program or instructions can be transferred from one website, computer, server, or data center to another website, computer, server, or data center via wired or wireless means. The computer-readable storage medium can be any available medium that a computer can access or a data storage device such as a server or data center that integrates one or more available media. The available medium can be a magnetic medium, such as a floppy disk, hard disk, or magnetic tape; it can also be an optical medium, such as a digital video optical disc; or it can be a semiconductor medium, such as a solid-state drive. The computer-readable storage medium may be a volatile or non-volatile storage medium, or may include both types of storage media.

[0161] In the various embodiments of this application, unless otherwise specified or in case of logical conflict, the terminology and / or descriptions of different embodiments are consistent and can be referenced by each other. The technical features of different embodiments can be combined to form new embodiments according to their inherent logical relationship.

[0162] In this application, "at least one" means one or more, and "more than one" means two or more. "And / or" describes the relationship between related objects, indicating that three relationships can exist. For example, A and / or B can represent: A alone, A and B simultaneously, or B alone, where A and B can be singular or plural. In the textual description of this application, the character " / " generally indicates an "or" relationship between the preceding and following related objects; in the formulas of this application, the character " / " indicates a "division" relationship between the preceding and following related objects.

[0163] It is understood that the various numerical designations used in the embodiments of this application are merely for descriptive convenience and are not intended to limit the scope of the embodiments of this application. The order of the process numbers described above does not imply the order of execution; the execution order of each process should be determined by its function and internal logic.

Claims

1. A communication method, characterized in that, The method, applied to a terminal device or a module within a terminal device, includes: The system receives a policy container from a policy control network element. The policy container includes a first user routing policy URSP rule, a second URSP rule, and indication information. The first URSP rule includes first association information of the target service, the second URSP rule includes second association information of the target service, and the indication information indicates that redundant transmission should be performed for the target service. According to the instruction information, a first session of the target service is matched based on the first URSP rule, and a second session of the target service is created based on the second URSP rule. The first session and the second session are redundant to each other. The first association information and the second association information are used to associate the first session and the second session. Wherein, the first association information includes a first redundant sequence number and the second association information includes a second redundant sequence number; or, the first association information and the second association information include a session pair identifier; or, the first association information includes a first redundant sequence number and a session pair identifier and the second association information includes a second redundant sequence number and the session pair identifier.

2. The method as described in claim 1, characterized in that, The first session that matches the target service based on the first URSP rule includes: Send a session modification request message, the session modification request message including the first association information, the session modification request message is used to modify the first session, the first session is used to provide redundant transmission for the target service corresponding to the first URSP rule; Creating a second session for the target service based on the second URSP rule includes: Send a session establishment request message, the session establishment request message including the second association information, the session establishment request message is used to create the second session, the second session is used to provide redundant transmission for the target service corresponding to the second URSP rule.

3. The method as described in claim 1, characterized in that, The creation of the second session for the target service based on the second URSP rule includes: A session establishment request message is sent, which includes the identification information of the first session and the second association information. The session establishment request message is used to create the second session. The first session is used to provide redundant transmission for the target service corresponding to the first URSP rule, and the second session is used to provide redundant transmission for the target service corresponding to the second URSP rule.

4. The method as described in claim 1, characterized in that, The first session that matches the target service based on the first URSP rule includes: Send a first session establishment request message, the first session establishment request message includes the first association information, the first session establishment request message is used to create the first session, the first session is used to provide redundant transmission for the target service corresponding to the first URSP rule; Creating a second session for the target service based on the second URSP rule includes: Send a second session establishment request message, which includes the second association information. The second session establishment request message is used to create the second session, and the second session is used to provide redundant transmission for the target service corresponding to the second URSP rule.

5. A communication method, characterized in that, include: Obtain business experience information corresponding to the target business; When the service experience information meets the preset conditions, a first user routing selection policy URSP rule and a second URSP rule are generated. The first URSP rule includes the first association information of the target service, and the second URSP rule includes the second association information of the target service. A policy container is sent to the terminal device. The policy container includes a first URSP rule, a second URSP rule, and indication information. The first URSP rule is used for matching a first session of the target service. The second URSP rule is used for creating a second session of the target service. The first session and the second session are redundant. The first association information and the second association information are used to associate the first session and the second session. The indication information indicates that redundant transmission is performed for the target service. Wherein, the first association information includes a first redundant sequence number and the second association information includes a second redundant sequence number; or, the first association information and the second association information include a session pair identifier; or, the first association information includes a first redundant sequence number and a session pair identifier and the second association information includes a second redundant sequence number and the session pair identifier.

6. The method as described in claim 5, characterized in that, The service experience information is used to indicate the current service quality of the target service.

7. The method as described in claim 5 or 6, characterized in that, The acquisition of service experience information corresponding to the target service includes: Send a request message to the data collection network element. The request message includes the identification information of the target (DNN, S-NSSAI) combination or the session under the target (DNN, S-NSSAI) combination corresponding to the target service. The request message is used to request the service experience information corresponding to the target service. Receive the service experience information from the data collection network element.

8. The method as described in claim 7, characterized in that, The request message also includes an application identifier, which is used to identify the target service.

9. The method as described in claim 5 or 6, characterized in that, The service experience information meets preset conditions, including at least one of the following: The packet loss rate in the service experience information is not less than the packet loss rate in the requirement parameters of the target service; The latency in the service experience information is not less than the latency in the requirement parameters of the target service; The jitter in the service experience information is not less than the jitter in the requirement parameters of the target service; The bandwidth in the service experience information is no greater than the bandwidth in the requirement parameters of the target service.

10. The method as described in claim 9, characterized in that, Also includes: Receive the requirement parameters of the target service from the application function network element.

11. The method as described in claim 9, characterized in that, The requirements parameters for the target service are pre-configured.

12. A communication device, characterized in that, Includes a module for performing the method as described in any one of claims 1 to 4.

13. A communication device, characterized in that, Includes modules for performing the method as described in any one of claims 5 to 11.

14. A computer program product, characterized in that, The computer program product includes a computer program or instructions that, when executed on a processor, cause the processor to perform the method as described in any one of claims 1 to 4, or the method as described in any one of claims 5 to 11.

15. A computer-readable storage medium, characterized in that, The storage medium stores a computer program or instructions that, when executed by a communication device, implement the method as described in any one of claims 1 to 4, or the method as described in any one of claims 5 to 11.

16. A communication system, characterized in that, It includes a policy control network element for performing the method as described in any one of claims 5 to 11, and a data collection network element for sending service experience information corresponding to the target service to the policy control network element.

17. A chip system, characterized in that, include: A processor, the processor being configured to perform the method as described in any one of claims 1 to 4, or to perform the method as described in any one of claims 5 to 11.

Images