WO2022267652A1

WO2022267652A1 - Communication method, communication apparatus, and communication system

Info

Publication number: WO2022267652A1
Application number: PCT/CN2022/087732
Authority: WO
Inventors: 周凯; 丁辉; 谢春生
Original assignee: 华为技术有限公司
Priority date: 2021-06-24
Filing date: 2022-04-19
Publication date: 2022-12-29
Also published as: CN115529637A

Abstract

The present application provides a communication method, a communication apparatus, and a communication system. The method comprises: matching a first data packet and flow description information, wherein the flow description information comprises an offset, a length, and a reference value, the offset is used for indicating a starting point of a target field in a data packet to be matched, the length represents the length of the target field, and the reference value is used for matching the value of the target field; when the first data packet matches the flow description information, adding a QFI corresponding to the flow description information to a header of the first data packet to obtain a second data packet; and sending the data packet. According to the solution, the target field of a service data packet is exactly matched by means of an offset, a length, and a reference value, and thus data packets of different service types can be effectively distinguished, thereby facilitating a network side to execute different controls on the data packets of different service types.

Description

A communication method, communication device and communication system

Cross References to Related Applications

This application claims the priority of the Chinese patent application with the application number 202110702409.8 and the application name "a communication method, communication device and communication system" submitted to the China Patent Office on June 24, 2021, the entire contents of which are incorporated by reference In this application.

technical field

The present application relates to the technical field of communication, and in particular to a communication method, a communication device and a communication system.

Background technique

The fifth generation (5th generation, 5G) network supports the quality of service (Quality of Service, QoS) flow granularity to guarantee the service quality of the business. When establishing a QoS flow or modifying a QoS flow, the session management network element sends the QoS Flow Identifier (QFI) and the QoS configuration (Profile) corresponding to the QFI to the access network device. The QoS configuration includes the 5G QoS identifier (5G QoS Identifier, 5QI), allocation and retention priority (Allocation and Retention Priority, ARP), guaranteed bit rate (Guarantee Bit Rate, GBR) and other parameter information, send QoS rules to the terminal, QoS rules include QFI, packet Filter and match priority information, send packet detection rule (Packet Detection Rule, PDR) to user plane network element, PDR includes QFI, packet filter and match priority information.

When the terminal needs to send an uplink data packet, the uplink data packet is matched according to the packet filter in the QoS rule. When the uplink data packet matches a certain packet filter, the header of the uplink data packet is added. The QFI corresponding to the packet filter, and then send the uplink data packet with the added QFI to the access network device.

When the user plane network element receives a downlink data packet, it matches the downlink data packet according to the packet filter in the PDR. Increase the QFI corresponding to the packet filter, and then send the downlink data packet with the added QFI to the access network device.

After receiving the uplink data packet or downlink data packet, the access network device obtains the QFI in the uplink data packet or downlink data packet, and then performs corresponding QoS guarantee according to the QoS configuration corresponding to the QFI.

The protocol currently defines Internet Protocol (IP) type and Ethernet (Ethernet) type packet filters. Terminals or user plane network elements can filter the packet headers of data packets through IP type or Ethernet type packet filters. Identify or match, and complete the mapping from service flow to QoS flow, so as to implement differentiated processing of data packets according to the granularity of packet filters.

However, relying on existing packet filters, it is impossible to make more precise distinctions between data packets.

Contents of the invention

Embodiments of the present application provide a communication method, a communication device, and a communication system, which are used to implement precise matching of data packets, thereby effectively distinguishing data packets of different service types.

In the first aspect, the embodiment of the present application provides a communication method, which can be executed by a communication device or a module applied to the communication device, and the communication device can be a terminal or a user plane network element. The method includes: matching the first data packet with the flow description information, wherein the flow description information includes an offset, a length and a reference value, and the offset is used to indicate the target field in the data packet to be matched The starting point, the length indicates the length of the target field, and the reference value is used to match the value of the target field; when the first data packet matches the flow description information, add the flow description to the header of the first data packet The quality of service flow identifier QFI corresponding to the information is obtained to obtain a second data packet; and the second data packet is sent.

According to the above scheme, by accurately matching the target field of the service data packet through the offset, length and reference value, it is possible to effectively distinguish data packets of different service types, thereby helping the network side to execute data packets of different service types. different controls.

In a possible implementation method, according to the offset start point and the offset, determine the start point of the target field in the first data packet; according to the start point of the target field in the first data packet and the length , determining the target field in the first data packet; judging whether the first data packet matches the flow description information according to the value of the target field in the first data packet and the reference value.

According to the above solution, the value of the target field can be acquired accurately, so as to achieve accurate matching on the first data packet.

In a possible implementation method, the offset starting point is pre-configured or predefined by the protocol.

In a possible implementation method, the stream description information further includes indication information, and the indication information is used to indicate the offset starting point.

In a possible implementation method, the offset starting point is the starting point of the payload in the first data packet or the starting point of the first data packet.

In a possible implementation method, when the value of the target field in the first data packet is the same as the reference value, it is determined that the first data packet matches the flow description information; or, when the first data packet The value of the target field is different from the reference value, and it is determined that the first data packet does not match the flow description information.

In a possible implementation method, the flow description information also includes a matching rule; when the value of the target field in the first data packet and the reference value meet the matching rule, it is determined that the first data packet and the flow The description information matches; or, when the value of the target field in the first data packet and the reference value do not satisfy the matching rule, it is determined that the first data packet does not match the flow description information.

According to the above scheme, a more flexible matching manner can be realized through matching rules.

In a possible implementation method, the matching rule is greater than, less than, equal to, or a functional relationship.

In a possible implementation method, the communication device is a terminal, and receives a QoS rule from a session management network element, and the QoS rule includes the QFI and the flow description information.

In a possible implementation method, the communication device is a user plane network element, and receives a packet detection rule PDR from a session management network element, and the PDR includes the QFI and the flow description information.

In a second aspect, the embodiment of the present application provides a communication method, and the method may be executed by a session management network element or a module applied to the session management network element. The method includes: receiving a policy charging control PCC rule from a policy control network element, where the PCC rule includes first flow description information; wherein, the first flow description information includes an offset, a length, and a reference value, and the offset It is used to indicate the starting point of the target field in the data packet to be matched, the length indicates the length of the target field, and the reference value is used to match the value of the target field; the packet detection rule PDR is generated according to the PCC rule; to the user The plane network element sends the PDR, which includes the first flow description information and the quality of service flow identifier QFI allocated for the PCC rule.

According to the above solution, it is possible to configure the first flow description information for the user plane network element, so that the user plane network element can accurately match the target field of the service data packet according to the offset, length and reference value in the first flow description information , which can effectively distinguish data packets of different service types, thereby helping the network side to perform different controls on data packets of different service types.

In a possible implementation method, a QoS rule is generated according to the PCC rule; the QoS rule is sent to the terminal, and the QoS rule includes the QFI and the second flow description information.

According to the above solution, it is possible to configure the second stream description information for the terminal, so that the terminal can accurately match the target field of the service data packet according to the offset, length and reference value in the second stream description information, and can realize effective Data packets of different service types are distinguished, thereby helping the network side to perform different controls on data packets of different service types.

In a possible implementation method, the first flow description information includes upstream flow description information and downstream flow description information, the upstream flow description information is used to match the upstream flow, and the downstream flow description information is used to match the downstream flow; the second flow description information is used to match the downstream flow; The flow description information includes the upstream flow description information, or the second flow description information is the same as the first flow description information.

In a possible implementation method, the PCC rule also includes QoS parameters; generate a QoS configuration according to the PCC rule, and the QoS configuration includes the QoS parameters; send the QFI and the QoS configuration to the access network device.

In a possible implementation method, a session modification request from the terminal is received, and the session modification request includes the first flow description information; and the policy association update request is sent to the policy control network element, and the policy association update request includes The first stream describes information.

In a third aspect, the embodiment of the present application provides a communication method, and the method may be executed by a policy control network element or a module applied to the policy control network element. The method includes: obtaining flow description information, the flow description information includes an offset, a length and a reference value, the offset is used to indicate the starting point of the target field in the data packet to be matched, and the length indicates the target field length, the reference value is used to match the value of the target field; generate a policy and charging control PCC rule, the PCC rule includes the flow description information; send the PCC rule to the session management network element.

In a possible implementation method, a policy authorization request from an application function network element is received, and the policy authorization request includes the flow description information.

In a possible implementation method, a policy association update request from the session management network element is received, and the policy association update request includes the flow description information from the terminal.

In a fourth aspect, the embodiment of the present application provides a communication device. The device may be a communication device, and may also be a chip used for the communication device. The communication device may be a terminal or a user plane network element. The device has the function of realizing any realization method of the first aspect above. This function may be implemented by hardware, or may be implemented by executing corresponding software on the hardware. The hardware or software includes one or more modules corresponding to the above functions.

In a fifth aspect, the embodiment of the present application provides a communication device, and the device may be a session management network element, or may be a chip used for the session management network element. The device has the function of implementing any implementation method of the second aspect above. This function may be implemented by hardware, or may be implemented by executing corresponding software on the hardware. The hardware or software includes one or more modules corresponding to the above functions.

In a sixth aspect, the embodiment of the present application provides a communication device, and the device may be a policy control network element, or may be a chip for policy control. The device has the function of realizing any realization method of the third aspect above. This function may be implemented by hardware, or may be implemented by executing corresponding software on the hardware. The hardware or software includes one or more modules corresponding to the above functions.

In the seventh aspect, the embodiment of the present application provides 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 so that the device executes Any implementation method in the first aspect to the third aspect above.

In an eighth aspect, the embodiment of the present application provides a communication device, including a unit or means (means) for performing each step of any implementation method in the first aspect to the third aspect.

In a ninth aspect, the embodiment of the present application provides a communication device, including a processor and an interface circuit, the processor is configured to communicate with other devices through the interface circuit, and execute any implementation method in the first aspect to the third aspect above. The processor includes one or more.

In the tenth aspect, the embodiment of the present application provides a communication device, including a processor coupled to the memory, and the processor is used to call the program stored in the memory to execute any implementation method in the first aspect to the third aspect above . The memory may be located within the device or external to the device. And there may be one or more processors.

In the eleventh aspect, the embodiment of the present application also provides a computer-readable storage medium, the computer-readable storage medium stores instructions, and when it is run on a communication device, the above-mentioned first to third aspects Any implementation method of is executed.

In the twelfth aspect, the embodiment of the present application also provides a computer program product, the computer program product includes a computer program or instruction, when the computer program or instruction is run by a communication device, any of the above first to third aspects The implementation method is executed.

In a thirteenth aspect, the embodiment of the present application further provides a chip system, including: a processor, configured to execute any implementation method in the first aspect to the third aspect above.

In a fourteenth aspect, the embodiment of the present application further provides a communication system, the communication system includes a session management network element for performing any implementation method of the above second aspect and a session management network element for performing any implementation method of the above third aspect Policies control network elements.

In a possible implementation method, the communication system further includes a user plane network element configured to execute any implementation method of the foregoing first aspect.

In a fifteenth aspect, the embodiment of the present application further provides a communication system, the communication system includes a user plane network element for performing any implementation method of the above-mentioned first aspect and a network element for performing any implementation method of the above-mentioned second aspect Session management network element.

Description of drawings

FIG. 1 is a schematic diagram of a communication system provided by an embodiment of the present application;

Figure 2(a) is a schematic diagram of a 5G network architecture based on a service architecture;

Figure 2(b) is a schematic diagram of a 5G network architecture based on a point-to-point interface;

FIG. 3(a) is a schematic diagram of a communication method provided by an embodiment of the present application;

FIG. 3(b) is a schematic diagram of a communication method provided by an embodiment of the present application;

FIG. 4 is a schematic diagram of a communication method provided by an embodiment of the present application;

FIG. 5 is a schematic diagram of a communication device provided in an embodiment of the present application;

FIG. 6 is a schematic diagram of a communication device provided by an embodiment of the present application.

detailed description

In order to make the purpose, technical solution and advantages of the application clearer, the application will be further described in detail below in conjunction with the accompanying drawings. The specific operation methods in the method embodiments can also be applied to the device embodiments or system embodiments.

In order to achieve precise matching of data packets, as shown in FIG. 1 , the present application provides a communication system, which includes a user plane network element and a session management network element. Optionally, the system also includes a policy control network element.

The session management network element is configured to receive a policy and charging control (Policy and Charging Control, PCC) rule from a policy control network element, where the PCC rule includes first flow description information; wherein, the first flow description information includes an offset , length and reference value, the offset is used to indicate the starting point of the target field in the data packet to be matched, the length indicates the length of the target field, and the reference value is used to match the value of the target field; according to the The PCC rule generates a PDR; sends the PDR to the user plane network element, the PDR includes the first flow description information and the QFI allocated for the PCC rule; the user plane network element is used to combine the first data packet with the first flow description information performing matching; when the first data packet matches the first flow description information, adding the QFI corresponding to the first flow description information to the header of the first data packet to obtain a second data packet; sending the second data packet.

In a possible implementation method, the session management network element is further configured to generate a QoS rule according to the PCC rule; and send the QoS rule to the terminal, and the QoS rule includes the QFI and the second flow description information.

In a possible implementation method, the PCC rule also includes a QoS parameter; the session management network element is also used to generate a QoS configuration according to the PCC rule, and the QoS configuration includes the QoS parameter; and send the QoS parameter to the access network device The QFI and the QoS configuration.

In a possible implementation method, the session management network element is further configured to receive a session modification request from the terminal, where the session modification request includes the first flow description information; send the policy association update request to the policy control network element, The policy association update request includes the first flow description information.

In a possible implementation method, the user plane network element is configured to match the first data packet with the first flow description information; when the first data packet matches the first flow description information, in the first data packet Adding the QFI corresponding to the first flow description information to the packet header to obtain a second data packet; sending the second data packet.

In a possible implementation method, the user plane network element is configured to match the first data packet with the first flow description information, specifically including: determining the first flow description information according to the offset starting point and the offset The starting point of the target field in the data packet; according to the starting point and the length of the target field in the first data packet, determine the target field in the first data packet; according to the acquisition of the target field in the first data packet value and the reference value, and determine whether the first data packet matches the first flow description information.

In a possible implementation method, the first stream description information further includes indication information, where the indication information is used to indicate the offset starting point.

In a possible implementation method, the user plane network element is configured to determine whether the first data packet matches the flow description information according to the value of the target field in the first data packet and the reference value, specifically including : used to determine that the first data packet matches the second description information of the flow when the value of the target field in the first data packet is the same as the reference value; or, when the value of the target field in the first data packet If the value is different from the reference value, it is determined that the first data packet does not match the first flow description information.

In a possible implementation method, the first flow description information also includes a matching rule; the user plane network element is configured to judge the first data flow according to the value of the target field in the first data packet and the reference value Whether the packet matches the first flow description information specifically includes: determining that the first data packet matches the first flow description information when the value of the target field in the first data packet and the reference value satisfy the matching rule; or , when the value of the target field in the first data packet and the reference value do not satisfy the matching rule, it is determined that the first data packet does not match the first flow description information.

In a possible implementation method, the policy control network element is configured to obtain the first flow description information; generate the PCC rule; and send the PCC rule to the session management network element.

In a possible implementation method, the policy control network element is configured to obtain the first flow description information, specifically including: receiving a policy authorization request from an application function network element, where the policy authorization request includes the first flow description information.

In a possible implementation method, the policy control network element is used to obtain the first flow description information, which specifically includes: receiving a policy association update request from the session management network element, and the policy association update request includes information from the terminal. The first stream describes information.

The system shown in Figure 1 can be used in the 5G network architecture shown in Figure 2(a) or Figure 2(b), of course, it can also be used in future network architectures, such as the sixth generation (6th generation, 6G) network architecture etc., this application does not make a limitation.

Figure 2(a) is a schematic diagram of a 5G network architecture based on a service-based architecture. The 5G network architecture shown in Figure 2(a) may include a data network (data network, DN) and an operator network. The functions of some of the network elements are briefly introduced and described below.

Wherein, the operator network may include one or more of the following network elements: authentication server function (Authentication Server Function, AUSF) network element, network exposure function (network exposure function, NEF) network element, policy control function (policy control function, PCF) network element, unified data management (unified data management, UDM) network element, unified database (Unified Data Repository, UDR), network storage function (Network Repository Function, NRF) network element, application function (application function, AF) ) network elements, access and mobility management function (access and mobility management function, AMF) network elements, session management function (session management function, SMF) network elements, radio access network (radio access network, RAN) equipment and users Plane function (user plane function, UPF) network element, network slice selection function (Network Slice Selection Function, NSSF) network element (not shown in the figure), etc. In the above operator network, network elements or devices other than radio access network devices may be referred to as core network elements or core network devices.

The wireless access network equipment can be a base station (base station), an evolved base station (evolved NodeB, eNodeB), a transmission reception point (transmission reception point, TRP), and a next generation base station (next generation NodeB, gNB) in a 5G mobile communication system , a next-generation base station in a 6G mobile communication system, a base station in a future mobile communication system, or an access node in a wireless fidelity (Wireless Fidelity, WiFi) system, etc.; it can also be a module or unit that completes some functions of the base station, for example, It can be a centralized unit (central unit, CU) or a distributed unit (distributed unit, DU). The radio access network equipment may be a macro base station, a micro base station or an indoor station, or a relay node or a donor node. The embodiment of the present application does not limit the specific technology and specific equipment form adopted by the radio access network equipment.

The terminal communicating with the RAN may also be called terminal equipment, user equipment (user equipment, UE), mobile station, mobile terminal, and so on. Terminals can be widely used in various scenarios, such as device-to-device (D2D), vehicle-to-everything (V2X) communication, machine-type communication (MTC), Internet of Things ( Internet of things, IOT), virtual reality, augmented reality, industrial control, automatic driving, telemedicine, smart grid, smart furniture, smart office, smart wearables, smart transportation, smart city, etc. Terminals can be mobile phones, tablet computers, computers with wireless transceiver functions, wearable devices, vehicles, drones, helicopters, airplanes, ships, robots, robotic arms, smart home devices, etc. The embodiment of the present application does not limit the specific technology and specific device form adopted by the terminal.

Base stations and terminals can be fixed or mobile. Base stations and terminals can be deployed on land, including indoors or outdoors, handheld or vehicle-mounted; they can also be deployed on water; they can also be deployed on aircraft, balloons and artificial satellites in the air. The embodiments of the present application do not limit the application scenarios of the base station and the terminal.

The AMF network element performs functions such as mobility management and access authentication/authorization. In addition, it is also responsible for transferring user policies between the terminal and the PCF.

The SMF network element performs functions such as session management, execution of control policies issued by the PCF, selection of UPF, and allocation of Internet Protocol (IP) addresses for terminals.

The UPF network element, as the interface UPF with the data network, completes functions such as user plane data forwarding, session/flow-based charging statistics, and bandwidth limitation.

The UDM network element performs functions such as managing subscription data and user access authorization.

UDR implements the access function of contract data, policy data, application data and other types of data.

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

The AF network element transmits the requirements from the application side to the network side, such as QoS requirements or user status event subscription. The AF may be a third-party functional entity, or an application service deployed by an operator, such as an IP Multimedia Subsystem (IP Multimedia Subsystem, IMS) voice call service.

The PCF network element is responsible for policy control functions such as charging for sessions and service flow levels, QoS bandwidth guarantee, mobility management, and terminal policy decision-making.

The NRF network element can be used to provide a network element discovery function, and provide network element information corresponding to the network element type based on the request of other network elements. NRF also provides network element management services, such as network element registration, update, de-registration, network element status subscription and push, etc.

The AUSF network element is responsible for authenticating users to determine whether users or devices are allowed to access the network.

The NSSF network element is used to select a network slice and count users in the network slice.

DN is a network outside the operator's network. The operator's network can access multiple DNs, and various services can be deployed on the DN, which can provide data and/or voice services for terminals. For example, DN is a private network of a smart factory. The sensors installed in the workshop of the smart factory can be terminals, and the control server of the sensors is deployed in the DN, and the control server can provide services for the sensors. The sensor can communicate with the control server, obtain instructions from the control server, and transmit the collected sensor data to the control server according to the instructions. For another example, DN is a company's internal office network. The mobile phone or computer of the company's employees can be a terminal, and the employee's mobile phone or computer can access information and data resources on the company's internal office network.

In Figure 2(a), Nausf, Nnef, Npcf, Nudm, Naf, Namf, and Nsmf are the service interfaces provided by the above-mentioned AUSF, NEF, PCF, UDM, AF, AMF, and SMF, respectively, and are used to call corresponding service operations. N1, N2, N3, N4, and N6 are interface serial numbers. The meanings of these interface serial numbers may refer to the meanings defined in the third generation partnership project (3rd generation partnership project, 3GPP) standard agreement, and no limitation is made here.

Figure 2(b) is a schematic diagram of a 5G network architecture based on a point-to-point interface, and the introduction of the functions of the network elements can refer to the introduction of the functions of the corresponding network elements in Figure 2(a), and will not be repeated here. The main difference between Figure 2(b) and Figure 2(a) is that the interface between each control plane network element in Figure 2(a) is a service interface, and each control plane network element in Figure 2(b) The interface between them is a point-to-point interface.

In the architecture shown in Figure 2(b), the interface names and functions between each network element are as follows:

1), N1: the interface between the AMF and the terminal, which can be used to transmit QoS control rules and the like to the terminal.

2), N2: the interface between the AMF and the RAN, which can be used to transfer radio bearer control information from the core network side to the RAN.

3), N3: the interface between the RAN and the UPF, mainly used to transfer the uplink and downlink user plane data between the RAN and the UPF.

4), N4: The interface between SMF and UPF, which can be used to transfer information between the control plane and the user plane, including controlling the distribution of forwarding rules, QoS control rules, traffic statistics rules, etc. Information reporting.

5), N5: the interface between the AF and the PCF, which can be used for sending application service requests and reporting network events.

6), N6: the interface between UPF and DN, used to transfer the uplink and downlink user data flow between UPF and DN.

7), N7: the interface between PCF and SMF, which can be used to deliver protocol data unit (protocol data unit, PDU) session granularity and service data flow granularity control policy.

8), N8: The interface between AMF and UDM, which can be used for AMF to obtain subscription data and authentication data related to access and mobility management from UDM, and for AMF to register terminal current mobility management related information with UDM.

9), N9: a user plane interface between UPF and UPF, used to transmit uplink and downlink user data flows between UPFs.

10), N10: the interface between SMF and UDM, which can be used for SMF to obtain session management-related subscription data from UDM, and for SMF to register terminal current session-related information with UDM.

11), N11: the interface between SMF and AMF, which can be used to transfer PDU session tunnel information between RAN and UPF, transfer control messages sent to terminals, transfer radio resource control information sent to RAN, etc.

12), N12: the interface between AMF and AUSF, which can be used for AMF to initiate an authentication process to AUSF, which can carry SUCI as a subscription identifier;

13), N13: the interface between UDM and AUSF, which can be used for AUSF to obtain user authentication vector from UDM to execute the authentication process.

14), N15: the interface between the PCF and the AMF, which can be used to issue terminal policies and access control-related policies.

15), N35: the interface between UDM and UDR, which can be used for UDM to obtain user subscription data information from UDR.

16), N36: the interface between the PCF and the UDR, which can be used for the PCF to obtain policy-related subscription data and application data-related information from the UDR.

It can be understood that the above-mentioned network element or function may be a network element in a hardware device, or a software function running on dedicated hardware, or a virtualization function instantiated on a platform (for example, a cloud platform). Optionally, the foregoing network element or function may be implemented by one device, or jointly implemented by multiple devices, or may be a functional module in one device, which is not specifically limited in this embodiment of the present application.

The session management network element, user plane network element, and policy control network element in this application can be the SMF, UPF, and PCF in Figure 2(a) or Figure 2(b), respectively, or they can be The above-mentioned network elements with functions of SMF, UPF, and PCF are not limited in this application. In the embodiment of the present application, SMF, UPF, and PCF are respectively used as an example of a session management network element, a user plane network element, and a policy control network element for description.

The access network device in the embodiment of the present application may be a wireless access network device. For convenience of description, in the embodiment of the present application, a base station is used as an example of the access network device for description.

At present, in actual scenarios, data packets of multiple service flows may have the same IP header characteristics or Ethernet packet header characteristics, so only relying on existing packet filters may not be able to effectively distinguish data packets, resulting in failure to meet More fine-grained business requirements for uplink and downlink business flows. Let's illustrate with an example.

Taking Profinet in industrial scenarios as an example, real-time communication (real-time, RT) data packets usually require a delay within 10 milliseconds (ms), and the corresponding protocol is the 802.1Q protocol. The structure of the data packet is shown in Table 1.

Table 1

This data packet can be used for the transmission of periodic user data, event-driven information, alarm information, etc. The network side may generally adopt different QoS guarantee requirements for the above-mentioned data packets of different service types. For example, for periodic user data, the base station pre-allocates scheduling resources for periodic user data based on an uplink pre-scheduling policy configured by a separate 5QI, thereby greatly reducing uplink scheduling delay.

The currently defined Ethernet type packet filter only supports identification to the Ethernet type field, and some switches will discard the information in the virtual local area network (virtual local area network, VLAN) tag field because they do not support the 802.1Q protocol , so that the RT data packet can only be identified based on characteristics such as source address, destination address, and Ethernet type. However, for the above-mentioned RT data packets of different service types, that is, data packets of periodic user data, data packets carrying event-driven information, and data packets carrying alarm information, the headers of these data packets have the same source address, destination Address and Ethernet type, so that when the terminal or UPF identifies the header of the data packet according to the packet filter, it cannot judge the actual service type corresponding to the data packet, so that the mapping from the data packet to the QoS flow cannot be accurately completed.

To solve the above problem, an embodiment of the present application provides a communication method, the method may be executed by a communication device or a module (such as a chip) used for the communication device, and the communication device may be a terminal or a UPF. With reference to Fig. 3 (a), this method comprises the following steps:

Step 301a, matching the first data packet with the flow description information.

Wherein, the flow description information includes an offset (offset), a length (length) and a reference value (value).

The offset is used to indicate the starting point of the target field in the data packet to be matched. Specifically, the offset indicates the forward or backward offset from the offset starting point. When the offset is a positive number , which means backward offset from the offset start point, and when the offset is negative, it means forward offset from the offset start point. Through the offset, the starting point of the target field can be obtained. length indicates the length of the target field. Through the offset and length, the target field can be obtained. The reference value is used to match the value of the target field, that is, by judging the relationship between the actual value of the target field of the data packet to be matched and the reference value, it is judged whether the data packet matches the flow description information.

As an implementation method, matching the first data packet with the flow description information may specifically be: determine the starting point of the target field in the first data packet according to the offset starting point and the offset, and determine the starting point of the target field in the first data packet according to The starting point and length of the target field of the first data packet determine the target field in the first data packet, and judge whether the first data packet matches the flow description information according to the value and reference value of the target field in the first data packet. Wherein, the offset start point may be pre-configured or predefined by the protocol, or may also be indicated by indication information, for example, the flow description information may further include indication information for indicating the offset start point. The offset starting point may be the starting point of the payload in the first data packet or the starting point of the first data packet.

Wherein, according to the value of the target field in the first data packet and the reference value, it is judged whether the first data packet matches the flow description information. Specifically, it may be: when the value of the target field in the first data packet matches the flow description information The reference value of the same, it is determined that the first data packet matches the flow description information; or, when the value of the target field in the first data packet is different from the reference value in the flow description information, it is determined that the first data packet does not match the flow description information match.

Or, judging whether the first data packet matches the flow description information according to the value of the target field in the first data packet and the reference value, may also be: when the value of the target field in the first data packet matches the flow description information The reference value of the first data packet satisfies the matching rule, and it is determined that the first data packet matches the flow description information; or, when the value of the target field in the first data packet and the reference value in the flow description information do not meet the matching rule, it is determined that the first data packet Does not match stream description information. The matching rule may be carried in the above flow description information. Optionally, the matching rule may be greater than (>), less than (<), equal to (=) or a functional relationship.

The following will be described in conjunction with the aforementioned example of the ProfinetNet scenario.

In one example, the default offset starting point is the starting point of the payload (playload) in the data packet to be matched. Referring to Table 1, the starting point of the payload is the starting point of the Frame ID. When the offset is 0, the length is 2 bytes, and the reference value is 1, wherein the reference value 1 indicates cyclic transmission, that is, it is used to indicate a periodic service data packet in the RT stream. Therefore, according to the offset and the length, the value of the Frame ID field in the service data packet (such as the first data packet) can be obtained. And when the value of the Frame ID field is 1, it means that the flow description information matches the first data packet, and when the value of the Frame ID field is not 1, it means that the flow description information does not match the first data packet superior. Alternatively, when the above-mentioned flow description information also includes a matching rule, for example, the matching rule is greater than (>), then when the value of the Frame ID field is greater than 1, it means that the flow description information matches the first data packet, when When the value of the Frame ID field is less than or equal to 1, it means that the flow description information does not match the first data packet.

In another example, modify the default offset starting point in the above example to the starting point of the data packet to be matched, that is, the starting point of the packet header of the data packet, and its offset value is a, where a represents the starting point of the data packet The value of the Frame ID field can also be obtained according to the offset and length of the number of bytes between the starting point of the packet header and the starting point of the Frame ID field.

In another example, indication information may also be carried in the flow description information, for example, the indication information indicates that the offset starting point is the starting point of the load (playload), then according to the indication information, offset and length, you can also obtain to the value of the Frame ID field.

Step 302a, when the first data packet matches the flow description information, add the QFI corresponding to the flow description information to the header of the first data packet to obtain the second data packet.

Step 303a, sending the second data packet.

If the communication device executing the above method is a terminal, the second data packet is an uplink data packet; if the communication device executing the above method is a UPF, the second data packet is a downlink data packet.

Optionally, when the above-mentioned target field is used to indicate the service type corresponding to the data packet to be matched, if the service type is a periodic service or an aperiodic service, then through the flow description information, the service type corresponding to the different data packets Make a distinction.

According to the above step 301a to step 303a, through the offset, length and reference value, the target field of the service data packet is accurately matched, which can effectively distinguish the data packets of different service types, thus helping the network side to identify different service types packets perform different controls.

The implementation method of configuring the flow description information to the UPF and/or the terminal is introduced below. Referring to FIG. 3(b), it is a schematic diagram of a communication method provided by an embodiment of the present application, and the method includes the following steps:

In step 301b, the PCF acquires first flow description information.

The first stream description information includes an offset, a length, and a reference value. For meanings of the offset, length, and reference value, reference may be made to the foregoing description.

Wherein, the first flow description information may include upstream flow description information and/or downstream flow description information, the upstream flow description information is used to match the upstream flow, and the downstream flow description information is used to match the downstream flow. The upstream description information includes a first offset, the first length, and a first reference value, and the downstream description information includes a second offset, a second length, and a second reference value. Wherein, the first offset and the second offset may be the same or different, the first length and the second length may be the same or different, and the first reference value and the second reference value may be the same or different.

As an implementation method, the PCF can obtain first-flow description information from an application function (AF) network element. For example, the PCF receives a policy authorization request from an application function network element, where the policy authorization request includes first flow description information.

As another implementation method, the PCF can obtain the first flow description information from the SMF. For example, the PCF receives the policy association update request from the SMF, the policy association update request includes the session modification request from the terminal, and the session modification request includes the first flow description information. That is, the terminal sends a session modification request carrying the first flow description information to the SMF, and then the SMF carries the first flow description information in the policy association update request and sends it to the PCF.

In step 302b, the PCF generates a PCC rule, and the PCC rule includes the first flow description information.

In step 303b, the PCF sends the PCC rule to the SMF. Correspondingly, the SMF receives the PCC rule.

In step 304b, the SMF generates a PDR according to the PCC rule, and the PDR includes the first flow description information and the QFI allocated for the PCC rule.

In step 305b, the SMF sends a PDR to the UPF. Correspondingly, the UPF receives the PDR.

Optionally, the following steps 306b to 307b are also performed.

In step 306b, the SMF generates a QoS rule according to the PCC rule, and the QoS rule includes the second flow description information and the QFI allocated for the PCC rule.

Wherein, the second flow description information includes upstream flow description information, or the second flow description information is the same as the first flow description information, that is, the second flow description information includes upstream flow description information and downstream flow description information.

In step 307b, the SMF sends the QoS rules to the terminal. Correspondingly, the terminal receives the QoS rule.

Optionally, the following steps 308b to 309b are also performed.

In step 308b, the SMF generates a QoS configuration (QoS profile) according to the PCC rule, and the QoS configuration includes QoS parameters.

The QoS parameters include parameter information such as 5QI, ARP, and GBR.

In step 309b, the SMF sends the QoS configuration and the QFI allocated for the PCC rule to the base station. Correspondingly, the base station receives the QoS configuration and the QFI.

According to the above solution, flow description information can be configured for the terminal and/or UPF, so that the terminal and/UPF can match data packets according to the flow description information.

The solutions in Fig. 3(a) and Fig. 3(b) above will be described below with reference to a specific example.

FIG. 4 is a schematic diagram of a communication method provided by an embodiment of the present application. The method is described by taking the feature description of the RT type packet in the above-mentioned Profinet scenario as an example. In order to meet the differentiated scheduling requirements for periodic RT data packets, the method uses a packet filter configured with a fixed offset to identify or match periodic data packets and aperiodic data packets in the RT service flow.

The method includes the following steps:

Step 401, the terminal accesses the core network via the base station, and establishes a PDU session.

In step 402a, the AF sends a policy authorization request to the PCF, and the policy authorization request includes the address of the terminal and flow description information. Correspondingly, the PCF receives the policy authorization request.

Optionally, the policy authorization request may be directly sent by the AF to the PCF or sent to the PCF via the NEF, and the policy authorization request may be, for example, Npcf_PolicyAuthorization_Create/Update.

The stream description information includes an offset (offset), a length (length) and a reference value (value). Optionally, the flow description information includes a source address and a destination address. Optionally, the flow description information further includes a matching rule, and the matching rule may be greater than (>), less than (<), equal to (=) or a functional relationship.

In step 402b, the SMF sends a policy association update request to the PCF, and the policy association update request includes flow description information. Correspondingly, the PCF receives the policy association update request.

The flow description information in the policy association update request is sent by the terminal to the SMF. Specifically, the terminal sends a PDU session modification request to the SMF, and the PDU session modification request includes the flow description information. Optionally, the PDU session modification request also includes the requested QoS (requested QoS), and the policy association update request may also include the requested QoS.

For the stream description information, refer to the description of step 402a.

It should be noted that both the above step 402a and step 402b are optional steps. As an implementation method, the above step 402a is performed but the above step 402b is not performed. As another implementation method, the above step 402b is performed but the above step 402a is not performed. As yet another implementation method, the above step 402a and step 402b are not executed.

In step 403, the PCF generates PCC rules.

The PCC rule includes the above-mentioned flow description information and QoS parameters, and optionally also includes charging policies, flow control policies, and the like.

The QoS parameters include parameter information such as 5QI, ARP, and GBR. The QoS parameter indicates the QoS guarantee to be performed on the service flow.

As an implementation method, when the above step 402a is executed, the PCF generates a PCC rule according to the flow description information provided by the AF.

As another implementation method, when the above step 402b is executed, the PCF generates a PCC rule according to the flow description information provided by the terminal.

As another implementation method, when the above step 402a and step 402b are not executed, the PCF can determine the PCC rule according to the local policy, other event information reported by the SMF or the UDR subscription.

In step 404, the PCF sends the PCC rule to the SMF. Correspondingly, the SMF receives the PCC rule.

In step 405, the SMF allocates a QFI for the PCC rule, and generates a QoS rule (rule), PDR, and QoS configuration (profile).

SMF performs QoS flow binding according to QoS parameters in PCC rules. The SMF judges whether there is a QoS flow corresponding to the QoS parameter. If not, the SMF allocates a new QFI for the PCC rule. If it exists, the SMF uses the QFI of the QoS flow.

The PDR generated by SMF contains flow description information in QFI and PCC rules.

The QoS rules generated by SMF include the flow description information in QFI and PCC rules. Optionally, the flow description information in the PCC rule includes upstream flow description information and downstream flow description information, and the QoS rule only includes upstream flow description information.

The QoS configuration generated by SMF includes the QoS parameters in the PCC rules.

In step 406, the SMF sends a PDR to the UPF.

As an implementation method, SMF sends N4Session Modification to UPF, which carries PDR.

Step 407, the SMF sends the QoS rule to the terminal via the AMF. Correspondingly, the terminal receives the QoS rule.

As an implementation method, the SMF sends a PDU session modification request/response to the terminal via the AMF, which carries QoS rules.

Step 408, the SMF sends the QFI and QoS configuration to the base station. Correspondingly, the base station receives the QFI and QoS configuration.

In step 409, the UPF performs QoS flow matching on the downlink data packet according to the flow description information in the PDR.

After the UPF receives the downlink data packet, it matches the downlink data packet according to the flow description information in the PDR. When the flow description information in the PDR matches the downlink data packet, the UPF encapsulates the QFI in the PDR in the header of the downlink data packet and forwards it to the base station.

Wherein, the specific method for the UPF to match the downlink data packet according to the flow description information in the PDR can refer to the foregoing description and will not be repeated here.

Step 410, the terminal performs QoS flow matching on the uplink data packet according to the flow description information in the QoS rule.

UPF matches uplink data packets according to flow description information in QoS rules. When the flow description information in the QoS rule matches the uplink data packet, the terminal encapsulates the QFI in the QoS rule in the header of the uplink data packet and forwards it to the base station.

Wherein, for the specific method for the terminal to match the uplink data packet according to the flow description information in the QoS rule, reference may be made to the foregoing description, and details are not repeated here.

Step 411, the base station implements QoS guarantee for uplink data packets or downlink data packets according to QFI and QoS configuration.

After receiving the uplink data packet or the downlink data packet, the base station obtains the QFI in the uplink data packet or the downlink data packet, and then performs corresponding QoS guarantee according to the QoS configuration corresponding to the QFI.

According to the above solution, by introducing a more flexible form of packet filter, the network can perform more fine-grained service matching for the data packets of the service flow, so as to meet the finer-grained service requirements of the uplink and downlink service flows.

It can be understood that, in order to realize the functions in the above embodiments, the SMF, PCF, UPF, base station and terminal include hardware structures and/or software modules corresponding to each function. Those skilled in the art should easily realize that the present application can be implemented in the form of hardware or a combination of hardware and computer software with reference to the units and method steps of the examples described in the embodiments disclosed in the present application. Whether a certain function is executed by hardware or computer software drives the hardware depends on the specific application scenario and design constraints of the technical solution.

FIG. 5 and FIG. 6 are schematic structural diagrams of possible communication devices provided by the embodiments of the present application. These communication devices can be used to implement the functions of the SMF, PCF, UPF, and terminal in the above method embodiments, and thus can also realize the beneficial effects of the above method embodiments. In the embodiment of the present application, the communication device may be SMF, PCF, UPF and terminal, or may be a module (such as a chip) applied to SMF, PCF, UPF and terminal.

As shown in FIG. 5 , a communication device 500 includes a processing unit 510 and a transceiver unit 520 . The communication device 500 is configured to implement functions of the SMF, PCF, UPF and terminal in the method embodiment shown in FIG. 3(a), FIG. 3(b) or FIG. 4 above.

When the communication device 500 is used to implement the functions of a terminal or a user plane network element (UPF) in the method embodiment shown in FIG. 3(a), FIG. 3(b) or FIG. The data packet is matched with the flow description information, wherein the flow description information includes an offset, a length and a reference value, the offset is used to indicate the starting point of the target field in the data packet to be matched, and the The length indicates the length of the target field, and the reference value is used to match the value of the target field; when the first data packet matches the flow description information, add the flow to the header of the data packet The quality of service flow identifier QFI corresponding to the description information is used to obtain a second data packet; the transceiver unit 520 is configured to send the second data packet.

In a possible implementation method, the processing unit 510 is configured to match the first data packet with the flow description information, specifically including: determining the first packet according to the offset starting point and the offset The starting point of the target field in a data packet; according to the starting point and the length of the target field in the first data packet, determine the target field in the first data packet; according to the The value of the target field and the reference value, and determine whether the first data packet matches the flow description information.

In a possible implementation method, the processing unit 510 is configured to judge the first data packet and the flow description information according to the value of the target field in the first data packet and the reference value Whether it matches, specifically includes: when the value of the target field in the first data packet is the same as the reference value, determining that the first data packet matches the flow description information; or, when the first data packet matches the flow description information; The value of the target field in a data packet is different from the reference value, and it is determined that the first data packet does not match the flow description information.

In a possible implementation method, the flow description information further includes a matching rule; the processing unit 510 is configured to determine the value of the target field in the first data packet and the reference value Whether the first data packet matches the flow description information specifically includes: when the value of the target field in the first data packet and the reference value satisfy the matching rule, determine the first data packet The packet matches the flow description information; or, when the value of the target field in the first data packet and the reference value do not satisfy the matching rule, determine that the first data packet matches the flow description information Mismatch.

When the communication device 500 is used to realize the function of the session management network element (SMF) in the method embodiment shown in FIG. 3(a), FIG. 3(b) or FIG. 4: the transceiver unit 520 is configured to receive Controlling the policy charging control PCC rule of the network element, the PCC rule includes first flow description information; wherein, the first flow description information includes an offset, a length, and a reference value, and the offset is used to indicate the The starting point of the target field in the matched data packet, the length represents the length of the target field, and the reference value is used to match the value of the target field; the processing unit 510 is configured to rule generation packet detection rule PDR; the transceiver unit 520 is further configured to send the PDR to the user plane network element, the PDR includes the first flow description information and the quality of service flow identifier QFI allocated for the PCC rule .

In a possible implementation method, the processing unit 510 is further configured to generate a QoS rule according to the PCC rule; the transceiver unit 520 is further configured to send the QoS rule to the terminal, and the QoS rule includes The QFI and second stream description information.

In a possible implementation method, the PCC rules further include QoS parameters; the processing unit 510 is further configured to generate a QoS configuration according to the PCC rules, and the QoS configuration includes the QoS parameters; The transceiver unit 520 is further configured to send the QFI and the QoS configuration to the access network device.

In a possible implementation method, the transceiving unit 520 is further configured to receive a session modification request from the terminal, where the session modification request includes the first flow description information; and send to the policy control network element The policy association update request includes the first stream description information.

When the communication device 500 is used to realize the function of the policy control network element (PCF) in the method embodiment shown in FIG. 3(a), FIG. 3(b) or FIG. 4: the processing unit 510 is configured to obtain flow description information, The flow description information includes an offset, a length and a reference value, the offset is used to indicate the starting point of the target field in the data packet to be matched, the length indicates the length of the target field, and the The reference value is used to match the value of the target field; a policy and charging control PCC rule is generated, and the PCC rule includes the flow description information; the transceiver unit 520 is configured to send the PCC rule to a session management network element.

More detailed descriptions about the processing unit 510 and the transceiver unit 520 can be directly obtained by referring to the relevant descriptions in the method embodiment shown in FIG. 3(a), FIG. 3(b) or FIG.

As shown in FIG. 6 , the communication device 600 includes a processor 610 and an interface circuit 620 . The processor 610 and the interface circuit 620 are coupled to each other. It can be understood that the interface circuit 620 may be a transceiver or an input-output interface. Optionally, the communication device 600 may further include a memory 630 for storing instructions executed by the processor 610 or storing input data required by the processor 610 to execute the instructions or storing data generated after the processor 610 executes the instructions.

When the communication device 600 is used to implement the method shown in Figure 3(a), Figure 3(b) or Figure 4, the processor 610 is used to implement the functions of the processing unit 510, and the interface circuit 620 is used to implement the transceiver unit 520 function.

When the above communication device is a chip applied to a terminal, the terminal chip implements the functions of the terminal in the above method embodiment. The terminal chip receives information from other modules in the terminal (such as radio frequency modules or antennas), and the information is sent to the terminal by the base station; or, the terminal chip sends information to other modules in the terminal (such as radio frequency modules or antennas), and the The information is sent by the terminal to the base station.

It can be understood that the processor in the embodiments of the present application can be a central processing unit (Central Processing Unit, CPU), and can also be other general-purpose processors, digital signal processors (Digital Signal Processor, DSP), application-specific integrated circuits (Application Specific Integrated Circuit, ASIC), Field Programmable Gate Array (Field Programmable Gate Array, FPGA) or other programmable logic devices, transistor logic devices, hardware components or any combination thereof. A general-purpose processor can be a microprocessor, or any conventional processor.

The method steps in the embodiments of the present application may be implemented by means of hardware, or may be implemented by means of a processor executing software instructions. Software instructions can be composed of corresponding software modules, and software modules 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 disk, removable hard disk, CD-ROM or any other form of storage medium known in the art. An exemplary storage medium is coupled to the processor such the processor can read information from, and write information to, the storage medium. Of course, the storage medium may also be a component of the processor. The processor and storage medium can be located in the ASIC. In addition, the ASIC can be located in the base station or the terminal. Certainly, the processor and the storage medium may also exist in the base station or the terminal as discrete components.

In the above embodiments, all or part of them may be implemented by software, hardware, firmware or any combination thereof. When implemented using software, it may be implemented in whole or in part in the form of a computer program product. The computer program product comprises one or more computer programs or instructions. When the computer program or instructions are loaded and executed on the computer, the processes or functions described in the embodiments of the present application are executed in whole or in part. The computer may be a general purpose computer, a special purpose computer, a computer network, a base station, user equipment or other programmable devices. The computer program or instructions may be stored in or transmitted from one computer-readable storage medium to another computer-readable storage medium, for example, the computer program or instructions may be downloaded from a website, computer, A server or data center transmits to another website site, computer, server or data center by wired or wireless means. The computer-readable storage medium may be any available medium that can be accessed by a computer, or a data storage device such as a server or a data center integrating one or more available media. The available medium may be a magnetic medium, such as a floppy disk, a hard disk, or a magnetic tape; it may also be an optical medium, such as a digital video disk; it may also be a semiconductor medium, such as a solid state disk. The computer readable storage medium may be a volatile or a nonvolatile storage medium, or may include both volatile and nonvolatile types of storage media.

In each embodiment of the present application, if there is no special explanation and logical conflict, the terms and/or descriptions between different embodiments are consistent and can be referred to each other, and the technical features in different embodiments are based on their inherent Logical relationships can be combined to form new embodiments.

In this application, "at least one" means one or more, and "multiple" means two or more. "And/or" describes the association relationship of associated objects, indicating that there may be three types of relationships, for example, A and/or B, which can mean: A exists alone, A and B exist simultaneously, and B exists alone, where A, B can be singular or plural. In the text description of this application, the character "/" generally indicates that the contextual objects are an "or" relationship; in the formulas of this application, the character "/" indicates that the contextual objects are a "division" Relationship.

It can be understood that the various numbers involved in the embodiments of the present application are only for convenience of description, and are not used to limit the scope of the embodiments of the present application. The size of the serial numbers of the above-mentioned processes does not mean the order of execution, and the execution order of each process should be determined by its functions and internal logic.

Claims

A communication method applied to a communication device, characterized in that it includes:

Matching the first data packet with the flow description information, wherein the flow description information includes an offset, a length and a reference value, and the offset is used to indicate the starting point of the target field in the data packet to be matched , the length represents the length of the target field, and the reference value is used to match the value of the target field;

When the first data packet matches the flow description information, adding the quality of service flow identifier QFI corresponding to the flow description information to the header of the first data packet to obtain a second data packet;

Send the second data packet.
The method according to claim 1, wherein said matching the first data packet with the flow description information comprises:

determining the starting point of the target field in the first data packet according to the offset starting point and the offset;

determining the target field in the first data packet according to the starting point and the length of the target field in the first data packet;

According to the value of the target field in the first data packet and the reference value, it is judged whether the first data packet matches the flow description information.
The method according to claim 2, wherein the offset starting point is pre-configured or predefined by a protocol.
The method according to claim 2, wherein the stream description information further includes indication information, and the indication information is used to indicate the offset starting point.
The method according to any one of claims 2 to 4, wherein the offset starting point is the starting point of the payload in the first data packet or the starting point of the first data packet.
The method according to any one of claims 2 to 5, wherein, according to the value of the target field in the first data packet and the reference value, judging whether the first data packet is related to the Whether the above stream description information matches, including:

When the value of the target field in the first data packet is the same as the reference value, determine that the first data packet matches the flow description information; or,

When the value of the target field in the first data packet is different from the reference value, it is determined that the first data packet does not match the flow description information.
The method according to any one of claims 2 to 5, wherein the flow description information further includes matching rules;

The determining whether the first data packet matches the flow description information according to the value of the target field in the first data packet and the reference value includes:

When the value of the target field in the first data packet and the reference value satisfy the matching rule, determine that the first data packet matches the flow description information; or,

When the value of the target field in the first data packet and the reference value do not satisfy the matching rule, it is determined that the first data packet does not match the flow description information.
The method according to claim 7, wherein the matching rule is greater than, less than, equal to or a functional relationship.
The method according to any one of claims 1 to 8, wherein the communication device is a terminal;

The method also includes:

Receive a quality of service QoS rule from a session management network element, where the QoS rule includes the QFI and the flow description information.
The method according to any one of claims 1 to 8, wherein the communication device is a user plane network element;

The method also includes:

Receive a packet detection rule PDR from a session management network element, where the PDR includes the QFI and the flow description information.
A communication method, applied to a session management network element, characterized in that it includes:

Receive a policy charging control PCC rule from a policy control network element, where the PCC rule includes first flow description information; wherein, the first flow description information includes an offset, a length, and a reference value, and the offset is used To indicate the starting point of the target field in the data packet to be matched, the length indicates the length of the target field, and the reference value is used to match the value of the target field;

Generate a packet detection rule PDR according to the PCC rule, the PDR includes the first flow description information and the quality of service flow identifier QFI allocated for the PCC rule;

Send the PDR to a user plane network element.
The method of claim 11, further comprising:

generating a QoS rule according to the PCC rule, the QoS rule including the QFI and second flow description information;

Send the QoS rule to the terminal.
The method of claim 12, wherein,

The first flow description information includes upstream flow description information and downstream flow description information, the upstream flow description information is used to match the upstream flow, and the downstream flow description information is used to match the downstream flow;

The second flow description information includes the upstream flow description information, or the second flow description information is the same as the first flow description information.
The method according to any one of claims 11 to 13, wherein the PCC rules also include QoS parameters;

The method also includes:

Generate a QoS configuration according to the PCC rule, the QoS configuration includes the QoS parameters;

sending the QFI and the QoS configuration to an access network device.
The method according to any one of claims 11 to 14, further comprising:

receiving a session modification request from a terminal, where the session modification request includes the first stream description information;

Sending the policy association update request to the policy control network element, where the policy association update request includes the first flow description information.
A communication method, applied to a policy control network element, characterized in that it includes:

Obtain flow description information, the flow description information includes offset, length and reference value, the offset is used to indicate the starting point of the target field in the data packet to be matched, and the length indicates the target field The length of the reference value is used to match the value of the target field;

Generate policy charging control PCC rules, the PCC rules include the flow description information;

Send the PCC rule to the session management network element.
The method according to claim 16, wherein said obtaining flow description information comprises:

Receive a policy authorization request from an application function network element, where the policy authorization request includes the flow description information.
The method according to claim 16, wherein said obtaining flow description information comprises:

Receive a policy association update request from the session management network element, where the policy association update request includes the flow description information from the terminal.
A communication device, characterized by comprising:

A processing unit, configured to match the first data packet with the flow description information, wherein the flow description information includes an offset, a length, and a reference value, and the offset is used to indicate the The starting point of the target field, the length indicates the length of the target field, and the reference value is used to match the value of the target field; when the first data packet matches the flow description information, in the Adding the quality of service flow identifier QFI corresponding to the flow description information to the header of the first data packet to obtain the second data packet;

A transceiver unit, configured to send the second data packet.
The device according to claim 19, wherein the processing unit is configured to match the first data packet with the flow description information, specifically comprising:

It is used to determine the starting point of the target field in the first data packet according to the offset starting point and the offset; determine the starting point of the target field in the first data packet and the length The target field in the first data packet; according to the value of the target field in the first data packet and the reference value, determine whether the first data packet matches the flow description information.
The device according to claim 20, wherein the processing unit is configured to judge the relationship between the first data packet and the Whether the flow description information matches, including:

It is used to determine that the first data packet matches the flow description information when the value of the target field in the first data packet is the same as the reference value; or, when the target field in the first data packet The value of the field is different from the reference value, and it is determined that the first data packet does not match the flow description information.
The device according to claim 20, wherein the flow description information further includes matching rules;

The processing unit is configured to judge whether the first data packet matches the flow description information according to the value of the target field in the first data packet and the reference value, specifically including:

It is used to determine that the first data packet matches the flow description information when the value of the target field in the first data packet and the reference value satisfy the matching rule; or, when the first data packet The value of the target field in the packet and the reference value do not satisfy the matching rule, and it is determined that the first data packet does not match the flow description information.
The device according to any one of claims 19 to 22, wherein the communication device is a terminal; the transceiver unit is further configured to receive a quality of service QoS rule from a session management network element, and the QoS rule contains the QFI and the stream description information.
The device according to any one of claims 19 to 22, wherein the communication device is a user plane network element; the transceiver unit is further configured to receive a packet detection rule PDR from a session management network element, so The PDR includes the QFI and the flow description information.
A communication device, characterized by comprising a transceiver unit and a processing unit;

The transceiving unit is configured to receive a policy charging control PCC rule from a policy control network element, where the PCC rule includes first flow description information; wherein, the first flow description information includes an offset, a length, and a reference value , the offset is used to indicate the starting point of the target field in the data packet to be matched, the length indicates the length of the target field, and the reference value is used to match the value of the target field;

The processing unit is configured to generate a packet detection rule PDR according to the PCC rule, and the PDR includes the first flow description information and the quality of service flow identifier QFI allocated for the PCC rule;

The transceiver unit is further configured to send the PDR to a user plane network element.
The device according to claim 25, wherein the processing unit is further configured to generate a QoS rule according to the PCC rule, and the QoS rule includes the QFI and the second flow description information;

The transceiving unit is further configured to send the QoS rule to the terminal.
A communication device, characterized by comprising:

A processing unit, configured to obtain flow description information, the flow description information includes an offset, a length and a reference value, the offset is used to indicate the starting point of the target field in the data packet to be matched, and the length Indicates the length of the target field, and the reference value is used to match the value of the target field; generates a policy charging control PCC rule, and the PCC rule includes the flow description information;

A transceiver unit, configured to send the PCC rule to a session management network element.
A communication system, characterized by comprising a session management network element for performing the method according to any one of claims 11 to 15 and a policy for performing the method according to any one of claims 16 to 18 Control network elements.
A communication device, characterized in that it includes: a processor, the processor is coupled with a memory, and the memory is used to store a program or an instruction, and when the program or instruction is executed by the processor, the device Perform the communication method as described in any one of claims 1 to 10, or perform the communication method as described in any one of claims 11 to 15, or perform the communication method described in any one of claims 16 to 18 communication method.
A communication device, characterized by comprising: a processor and an interface;

The processor is used to control the device to execute the communication method according to any one of claims 1 to 10, or to execute the communication method according to any one of claims 11 to 15, or to execute the communication method according to claim 16. The communication method described in any one of to 18;

The processor is also used to control the interface to communicate with other devices.
A communication device, characterized in that it is used for the communication method according to any one of claims 1 to 10, or executes the communication method according to any one of claims 11 to 15, or executes the communication method according to any one of claims The communication method described in any one of 16 to 18.
A communication device, characterized in that it includes: a processor and a communication interface,

The communication interface is configured to receive code instructions and transmit them to the processor, and the processor is configured to run the code instructions to execute the communication method according to any one of claims 1 to 10.
A computer-readable storage medium, on which are stored computer programs or instructions, characterized in that, when the computer programs or instructions are executed, the method described in any one of claims 1 to 10 is performed, or the rights The method of any one of claims 11 to 15 being performed, or causing the method of any one of claims 16 to 18 to be performed.
A computer program product, characterized in that the computer program product includes a computer program, and when the computer program is run, the method according to any one of claims 1 to 10 is executed, or the method according to any one of claims 11 to 15 is executed. The method of any one of claims 16 to 18 is carried out.
A system on a chip, characterized in that it comprises:

memory for storing computer programs;

A processor, configured to call and run the computer program from the memory, so that the device installed with the system-on-a-chip executes the communication method according to any one of claims 1 to 10, or executes the communication method according to any one of claims 11 to 10. The communication method described in any one of claims 15, or execute the communication method described in any one of claims 16-18.