WO2019101041A1

WO2019101041A1 - Communication method and device therefor

Info

Publication number: WO2019101041A1
Application number: PCT/CN2018/116215
Authority: WO
Inventors: 朱强华; 熊春山; 周铮
Original assignee: 华为技术有限公司
Priority date: 2017-11-21
Filing date: 2018-11-19
Publication date: 2019-05-31
Also published as: CN109818917B; CN109818917A

Abstract

The embodiments of the present application provide a communication method and a device therefor. The method may comprise the following steps: a UPF receiving a downlink data packet of a non-IP type PDU session, access network tunnel information of the non-IP type PDU session having not been stored in the UPF; the UPF determining, according to transport layer IP header information of the downlink data packet or inner layer header information of the downlink data packet, a tag value corresponding to the downlink data packet; the UPF sending a downlink data notification to a session management function (SMF), the downlink data notification comprising the tag value corresponding to the downlink data packet, the tag value corresponding to the downlink data packet being used for the SMF to determine a paging policy identifier of the downlink data packet. The embodiments of the present application can determine the tag value of the non-IP type PDU session, and further determine a paging policy.

Description

Communication method and device thereof

The present application claims priority to Chinese Patent Application No. JP-A No. No. No. No. No. No. No. No. No. No. No. .

Technical field

The embodiments of the present application relate to the field of communications technologies, and in particular, to a communication method and apparatus thereof.

Background technique

A terminal device (for example, a user equipment (UE)) registered in a mobile network has three states: an idle state, a connected state, and an in-active state. In the idle state, the network can know the registration area where the UE is located, that is, the tracking area list (TAL). If the network needs to send data to the UE, it needs to first send to all the base stations in the TAL where the UE is located. The paging request, the base station pages the UE, and the UE sends a service registration request to enter a connected state. In the connected state, the network knows the base station to which the UE is connected, and can directly send data to the UE. In the in-active state of the UE, the network can decentralize the location management and reachability management functions to the base station to which the UE is connected, and the base station manages the UE on behalf of the network, such as paging of the UE, buffering of data, and the like.

The network-triggered service request process can be as shown in Figure 1. When the downlink data for the UE exists on the network side, the UE is in the idle state, and the user plane function (UPF) notifies the steps 2a and 2b. Notifying the session management function (SMF), the SMF sends an N11 message (UE Feasibility Call Request) to the access and mobility management function (AMF) through steps 3a and 3b, and the AMF is in the TAL. Each radio access network (RAN) sends a paging command, and the RAN pages the UE through step 5. The UE performs the service request procedure triggered by the UE in step 7. After that, the paging UE is stopped at step 8, and finally the UPF transmits the downlink data of the UE. If the AMF finds that the UE is unreachable, or the UE can only page for the policing service, the AMF needs to notify the SMF, the SMF notifies the UPF that the UPF starts the data processing policy, temporarily caches or discards.

In the flow shown in FIG. 1, for an Internet Protocol (IP) type protocol data unit (PDU) session, a tag value may be determined according to an inner IP packet header, such as a difference. A differentiated service code point (DSCP) value, which helps the AMF determine the paging policy of the UE. The paging policy for different flows or services in a PDU session may include: a paging retransmission mechanism, that is, a paging frequency or a time interval; whether to page the UE when the AMF is heavily loaded; whether to apply the sub-region search For example, the paging is first sent in the last tracking area (TA) or cell of the UE, and then paging in the entire registration area of the UE.

Fifth-generation mobile communication technology (5 ^th -Generation, 5G) defined in the standard 5G network supports three types of sessions, IP (e.g. IPv4, IPv6) PDU type session, Ethernet (Ethernet) session and unstructured type PDU ( Unstructured) type PDU session. A scheme for determining a DSCP value for an IP type PDU session is currently given, but a scheme for determining a DSCP value for a non-IP type PDU session is not given.

Summary of the invention

The technical problem to be solved by the embodiments of the present application is to provide a communication method and device thereof, which can implement the determination of a non-IP type PDU session tag value, and further determine a paging policy.

A first aspect of the embodiments of the present application provides a communication method, including:

The UPF receives the downlink data packet of the non-IP type PDU session, and the access network tunnel information of the non-IP type PDU session is not stored in the UPF;

The UPF determines the tag value corresponding to the downlink data packet according to the transport layer IP header information of the downlink data packet or the inner layer header information of the downlink data packet;

The UPF sends a downlink data notification to the SMF, where the downlink data notification includes a tag value corresponding to the downlink data packet, and the tag value corresponding to the downlink data packet is used by the SMF to determine a paging policy indication (PPI) of the downlink data packet, where The PPI is used by the AMF to determine the paging policy of the downlink data packet.

In a second aspect, an embodiment of the present application provides a UPF, including a unit or means for performing the steps of the above first aspect.

In a third aspect, an embodiment of the present application provides a UPF, including at least one processing element and at least one storage element, wherein at least one storage element is configured to store a program and data, and at least one processing element is configured to perform the first aspect of the present application. Methods.

In a fourth aspect, an embodiment of the present application provides a UPF, including at least one processing element (or chip) for performing the method of the above first aspect.

In a fifth aspect, an embodiment of the present application provides a program, when executed by a processor, for performing the method of the above first aspect.

In a sixth aspect, an embodiment of the present application provides a program product, such as a computer readable storage medium, including the program of the fifth aspect.

It can be seen that, in the foregoing first to sixth aspects, the UPF determines the label value corresponding to the downlink data packet by using the transport layer IP header information of the downlink data packet or the inner layer header information of the downlink data packet, so that the UPF determines the identifier of the non-IP type PDU session. The value, which in turn facilitates the AMF to determine the paging policy.

Wherein, the tag value may be a DSCP value. The transport layer IP header information may include the N6/N9 tunnel IP header information, and the N6/N9 tunnel IP header information may include the N6/N9 tunnel IP header DSCP value. The inner header information may be a priority, and the priority may be a priority code point (DPE/PCPority code point, PCP), a drop eligible indicator (DEI), or a PCP+DEI.

In a possible implementation manner, the UPF pre-configures a tag value generation rule for a non-IP type PDU session, that is, configures a tag value generation rule for a non-IP type PDU session before receiving a downlink data packet of a non-IP type PDU session. The tag value generation rule may be a rule for generating a tag value according to a mapping relationship between a priority and a tag value, that is, searching for a corresponding tag value according to a mapping relationship between a priority and a tag value. The tag value generation rule may be a rule for generating a tag value according to the N6/N9 tunnel IP header information, that is, the N6/N9 tunnel IP header DSCP value included in the N6/N9 tunnel IP header information is determined as a tag value. The UPF pre-configures the tag value generation rule, so that when the downlink data packet of the non-IP type PDU session is received, the tag value corresponding to the downlink data packet can be determined by combining the tag value generation rule and the downlink data packet information.

In a possible implementation manner, the UPF determines the N6/N9 tunnel IP header information of the downlink data packet according to the transport layer IP header information of the downlink data packet, that is, extracts the N6/N9 tunnel IP header information of the downlink data packet, and according to the downlink. The N6/N9 tunnel IP header information of the data packet and the rule for generating the tag value according to the N6/N9 tunnel IP header information determine the tag value corresponding to the downlink data packet, that is, the DS6 value of the N6/N9 tunnel IP header of the downlink data packet is determined as the downlink. The tag value corresponding to the packet, thereby determining the value of the non-IP type PDU session tag. This method is applicable to Ethernet type PDU sessions and unstructured type PDU sessions.

In a possible implementation manner, the UPF determines the priority of the downlink data packet according to the inner layer header information of the downlink data packet, that is, extracts the priority of the downlink data packet, and according to the priority of the downlink data packet, and according to the priority and The rule for generating the tag value between the tag values determines the tag value corresponding to the downlink packet, that is, the tag value corresponding to the priority of the downlink packet, thereby determining the non-IP type PDU session tag value. This method is applicable to Ethernet type PDU sessions that can obtain priority.

A seventh aspect of the embodiments of the present application provides a communication method, including:

The UPF obtains the transport layer IP header information of the downlink data packet or the inner layer header information of the downlink data according to the configuration information.

The UPF sends a downlink data notification to the SMF, where the downlink data notification includes the transport layer IP header information of the downlink data packet or the inner layer header information of the downlink data packet, the transport layer IP header information of the downlink data packet, or the inner layer header information of the downlink data packet. Used by the SMF to determine the tag value corresponding to the downlink packet.

In an eighth aspect, an embodiment of the present application provides a UPF, including a unit or a means for performing the foregoing steps of the seventh aspect.

In a ninth aspect, an embodiment of the present application provides a UPF, including at least one processing element and at least one storage element, wherein at least one storage element is configured to store a program and data, and at least one processing element is configured to perform the seventh aspect of the present application. Methods.

In a tenth aspect, an embodiment of the present application provides a UPF, including at least one processing element (or chip) for performing the method of the above seventh aspect.

In an eleventh aspect, an embodiment of the present application provides a program, when executed by a processor, for performing the method of the above seventh aspect.

In a twelfth aspect, the embodiment of the present application provides a program product, such as a computer readable storage medium, including the program of the eleventh aspect.

It can be seen that, in the above seventh to twelfth aspects, the UPF sends the transport layer IP header information of the downlink data packet or the inner layer packet information of the downlink data packet to the SMF according to the configuration information, so that the SMF according to the transport layer IP header information of the downlink data packet. Or the inner layer packet information of the downlink data packet determines the tag value corresponding to the downlink data packet, so that the SMF determines the tag value of the non-IP type PDU session, thereby facilitating the AMF to determine the paging policy.

In a possible implementation manner, the UPF pre-configures the foregoing configuration information, that is, configuring the foregoing configuration information before receiving the downlink data packet of the non-IP type PDU session, where the configuration information is used to specify that the downlink data notification needs to include the transport layer IP header. Information or inner header information. The UPF can obtain information from the downlink data packet in a targeted manner through the configuration information, and carry the corresponding information in the downlink data notification.

A thirteenth aspect of the embodiments of the present application provides a communication method, including:

The SMF receives the downlink data notification sent by the UPF, where the downlink data notification includes the transport layer IP header information of the downlink data packet or the inner layer header information of the downlink data;

The SMF determines the tag value corresponding to the downlink data packet according to the transport layer IP header information of the downlink data packet or the inner layer header information of the downlink data;

The SMF determines the PPI of the downlink data packet according to the tag value corresponding to the downlink data packet;

The SMF sends a request message to the AMF, the request message includes a PPI, and the PPI is used by the AMF to determine a paging policy of the downlink data packet.

In a fourteenth aspect, an embodiment of the present application provides an SMF, including a unit or a means for performing the steps of the thirteenth aspect above.

In a fifteenth aspect, an embodiment of the present application provides an SMF, including at least one processing element and at least one storage element, wherein at least one storage element is used to store a program and data, and at least one processing element is used to execute the thirteenth aspect of the present application. The method provided in .

In a sixteenth aspect, an embodiment of the present application provides an SMF, including at least one processing element (or chip) for performing the method of the above thirteenth aspect.

In a seventeenth aspect, the embodiment of the present application provides a program for executing the method of the above thirteenth aspect when executed by a processor.

In an eighteenth aspect, the embodiment of the present application provides a program product, such as a computer readable storage medium, including the program of the seventeenth aspect.

It can be seen that, in the thirteenth to eighteenth aspects, the SMF determines the tag value corresponding to the downlink data by using the transport layer IP header information of the downlink data packet sent by the UPF or the inner layer header information of the downlink data packet, thereby implementing the SMF determination non- The tag value of the IP type PDU session, which in turn facilitates the AMF to determine the paging policy.

In one possible implementation, the SMF pre-configures tag value generation rules for non-IP type PDU sessions. The tag value generation rule may be a rule for generating a tag value according to a mapping relationship between a priority and a tag value, that is, searching for a corresponding tag value according to a mapping relationship between a priority and a tag value. The tag value generation rule may be a rule for generating a tag value according to the N6/N9 tunnel IP header information, that is, the N6/N9 tunnel IP header DSCP value included in the N6/N9 tunnel IP header information is determined as a tag value. The UPF pre-configures the tag value generation rule, so that when the downlink data packet of the non-IP type PDU session is received, the tag value corresponding to the downlink data packet can be determined by combining the tag value generation rule and the downlink data packet information.

In a possible implementation manner, the SMF determines the N6/N9 tunnel IP header information of the downlink data packet according to the transport layer IP header information of the downlink data packet, that is, extracts the N6/N9 tunnel IP header information of the downlink data packet, and according to the downlink. The N6/N9 tunnel IP header information of the data packet and the rule for generating the tag value according to the N6/N9 tunnel IP header information determine the tag value corresponding to the downlink data packet, that is, the DS6 value of the N6/N9 tunnel IP header of the downlink data packet is determined as the downlink. The tag value corresponding to the packet, thereby determining the value of the non-IP type PDU session tag. This method is applicable to Ethernet type PDU sessions and unstructured type PDU sessions.

In a possible implementation manner, the SMF determines the priority of the downlink data packet according to the inner layer header information of the downlink data packet, that is, extracts the priority of the downlink data packet, and according to the priority of the downlink data packet, and according to the priority and The rule for generating the tag value between the tag values determines the tag value corresponding to the downlink packet, that is, the tag value corresponding to the priority of the downlink packet, thereby determining the non-IP type PDU session tag value. This method is applicable to Ethernet type PDU sessions that can obtain priority.

A nineteenth aspect of the present application provides a communication method, including:

The UPF obtains the session type of the non-IP type PDU session and the priority of the downlink data packet according to the configuration information.

The UPF sends a downlink data notification to the SMF, and the downlink data notification includes the session type and the priority of the downlink data packet.

In a twentieth aspect, the embodiment of the present application provides a UPF, including a unit or means for performing the steps of the above nineteenth aspect.

In a twenty-first aspect, an embodiment of the present application provides a UPF, including at least one processing element and at least one storage element, wherein at least one storage element is used to store programs and data, and at least one processing element is used to execute the nineteenth application. The method provided in the aspect.

In a twenty-second aspect, the embodiment of the present application provides a UPF, including at least one processing element (or chip) for performing the method of the above nineteenth aspect.

In a twenty-third aspect, the embodiment of the present application provides a program for executing the method of the above nineteenth aspect when executed by a processor.

In a twenty-fourth aspect, the embodiment of the present application provides a program product, such as a computer readable storage medium, including the program of the twenty-third aspect.

It can be seen that in the above nineteenth to twenty-fourth aspects, the UPF sends the session type and the priority of the downlink data packet to the SMF, and the SMF sends the information to the AMF, and finally the AMF determines the paging policy to implement the non-IP type. Determination of the paging policy for the PDU session.

In a possible implementation manner, the UPF pre-configures the foregoing configuration information, where the configuration information is used to specify that the downlink data notification includes a session type and a priority, so that the UPF sends the information to the SMF.

A twenty-fifth aspect of the present application provides a communication method, where the method is applied to a non-IP type PDU session, and the access network tunnel information of the non-IP type PDU session is not stored in the UPF, and the method includes:

The AMF receives the session type sent by the SMF and the priority of the downlink data packet of the non-IP type PDU session;

The AMF determines the paging policy of the downlink data packet according to the session type and the priority of the downlink data packet.

In a twenty-sixth aspect, the embodiment of the present application provides an AMF, including a unit or a means for performing the steps of the above twenty-fifth aspect.

The twenty-seventh aspect, the embodiment of the present application provides an AMF, including at least one processing element and at least one storage element, wherein at least one storage element is used to store programs and data, and at least one processing element is used to execute the twentieth tenth of the present application. The method provided in the five aspects.

In a twenty-eighth aspect, an embodiment of the present application provides an AMF, including at least one processing element (or chip) for performing the method of the above twenty-fifth aspect.

In a twenty-ninth aspect, the embodiment of the present application provides a program for executing the method of the above twenty-fifth aspect when executed by a processor.

In a thirtieth aspect, the embodiment of the present application provides a program product, such as a computer readable storage medium, including the program of the twenty-ninth aspect.

It can be seen that, in the above twenty-fifth to thirtieth aspects, the AMF determines the paging policy of the downlink data packet according to the session type and the priority of the downlink data packet, thereby implementing the determination of the paging policy of the non-IP type PDU session.

In a possible implementation manner, the AMF pre-configures a paging policy generation rule for a non-IP type PDU session, the paging policy generation rule includes generating a paging policy according to the session type and priority, so that the AMF receives the session type and In the case of priority, a paging policy can be directly generated according to the session type and priority, thereby realizing the determination of the paging policy of the non-IP type PDU session.

A thirty-first aspect of the present application provides a communication method, where the method is applied to a non-IP type PDU session, and the access network tunnel information of the non-IP type PDU session is not stored in the UPF, and the method includes:

The SMF receives the downlink data notification sent by the UPF, and the downlink data notification includes the session type of the non-IP type PDU session and the priority of the downlink data packet;

The SMF sends the session type and the priority of the downstream data packet to the AMF.

In a thirty-second aspect, an embodiment of the present application provides an AMF, including a unit or a means for performing the steps of the above twenty-fifth aspect.

In a thirty-third aspect, an embodiment of the present application provides an AMF, including at least one processing element and at least one storage element, wherein at least one storage element is used to store a program and data, and at least one processing element is used to execute the twentieth tenth of the present application. The method provided in the five aspects.

In a thirty-fourth aspect, the embodiment of the present application provides an AMF, including at least one processing element (or chip) for performing the method of the above twenty-fifth aspect.

In a thirty-fifth aspect, the embodiment of the present application provides a program for executing the method of the above twenty-fifth aspect when executed by a processor.

In a thirty-sixth aspect, the embodiment of the present application provides a program product, such as a computer readable storage medium, including the program of the twenty-ninth aspect.

It can be seen that in the above 31st to 36th aspects, the SMF receives the priority of the session type and the downlink data packet from the UPF, and sends it to the AMF, and the AMF determines the downlink according to the session type and the priority of the downlink data packet. The paging policy of the data, thereby determining the paging policy of the non-IP type PDU session.

DRAWINGS

In order to more clearly illustrate the technical solutions in the embodiments of the present application or the background art, the drawings to be used in the embodiments of the present application or the background art will be described below.

FIG. 1 is a schematic diagram of a network triggered service request process;

2 is a schematic diagram of a network architecture to which an embodiment of the present application is applied;

3 is a schematic diagram of bits of DSCP and IP priority in an IPv4 header;

4 is a schematic flowchart of a communication method according to Embodiment 1 of the present application;

FIG. 5 is a schematic flowchart of a communication method according to Embodiment 2 of the present application;

FIG. 6 is a schematic flowchart of a communication method according to Embodiment 3 of the present application;

FIG. 7 is a schematic flowchart of a communication method according to Embodiment 4 of the present application;

8 is a schematic flowchart of a communication method according to Embodiment 5 of the present application;

FIG. 9 is a schematic diagram of a logical structure of a communication device according to an embodiment of the present application;

FIG. 10 is a schematic structural diagram of a physical structure of a communication apparatus according to an embodiment of the present application.

Detailed ways

Referring to FIG. 2, it is a schematic diagram of a network architecture in which an embodiment of the present application is applied. The network architecture diagram may be a schematic diagram of a network architecture of a 5G system, including an authentication server function (AUSF), unified data management (UDM), access and mobility management (AMF), and session management functions ( SMF), policy control function (PCF), application function (AF), terminal equipment, access network (AN), user plane function (UPF), and data network (DN) ). The access network may be a radio access network (RAN).

The interface between the terminal device and the AMF is an N1 interface, and the interface between the (R) AN and the AMF is an N2 interface, and the interface between the (R) AN and the UPF is an N3 interface, and the interface between the UPF and the SMF is On the N4 interface, the interface between the PCF and the AF is the N5 interface, the interface between the UPF and the DN is the N6 interface, the interface between the SMF and the PCF is the N7 interface, and the interface between the AMF and the UDM is the N8 interface, UPF and UPF. The interface between the AUM and the SMF is the N11 interface, the interface between the AMF and the AMF is the N12 interface, and the interface between the AUX and the UDM is the N13 interface. Interface, the interface between AMF and AMF is N14 interface, and the interface between AMF and PCF is N15 interface.

The terminal device is an entry point for the mobile user to interact with the network, and can provide basic computing power, storage capability, display a service window to the user, and accept user operation input. The terminal device establishes a signal connection with the (R)AN, and the data connection, thereby transmitting control signals and service data to the mobile network.

(R)AN is similar to the base station in the traditional network, and is deployed close to the terminal device to provide the network access function for authorized users in a specific area, and can transmit user data by using different quality transmission tunnels according to the user level and service requirements. . (R) AN can manage its own resources, make reasonable use, provide access services for terminal devices as needed, and forward control signals and user data between the terminal devices and the core network.

The core network is responsible for maintaining the subscription data of the mobile network, managing the network elements of the mobile network, and providing functions such as session management, mobility management, policy management, and security authentication for the terminal device. When the terminal device is attached, the terminal device is provided with network access authentication; when the terminal device has a service request, the terminal device is allocated network resources; when the terminal device is moved, the terminal device is updated with network resources; when the terminal device is idle, Providing a fast recovery mechanism for the terminal device; releasing the network resource for the terminal device when the terminal device is detached; providing the data routing function for the terminal device, such as forwarding the uplink data to the data network; or the data from the data when the terminal device has the service data The network receives the downlink data of the terminal device and forwards it to the (R) AN, thereby transmitting to the terminal device. The core network includes UPF, AUSF, AMF, SMF, UDM, PCF, and AF. The core network user plane includes UPF, and the core network control plane includes AUSF, AMF, SMF, UDM, PCF, and AF.

The UPF performs user packet forwarding according to the routing rules of the SMF. AUSF is responsible for the security certification of terminal equipment. AMF is responsible for access management and mobility management of terminal equipment. SMF, responsible for session management of terminal devices. UDM, responsible for user contract context management. PCF, responsible for user policy management. AF, responsible for user application management.

A data network is a data network that provides business services to users. The general client is located in the terminal device and the server is located in the data network. The data network can be a private network, such as a local area network, or an external network that is not controlled by the operator, such as the Internet (Internet), or a proprietary network deployed by the operator, such as to configure the IP multimedia network subsystem (IP). Multimedia core network subsystem, IMS) IMS service.

The DSCP distinguishes the priority by the encoded value in the type of service (ToS) identification byte of each packet IP header, using the used 6 bits and the unused 2 bits. It can be understood that DSCP is to ensure the quality of service (QoS) of the communication, and encode the identification byte of the IP header of the packet to classify the service class and distinguish the priority of the service.

In the IPv4 header, the ToS field is 1 byte (8 bits), and the first three bits are IP Precedence. These three bits can be divided into eight priority levels, that is, IP priority fields, which can be applied to the stream. Classification, the larger the value, the higher the priority. These three IP precedence fields can only be prioritized for eight services, which is sufficient for a single service type with a small amount of traffic. However, when actually deployed in the network, the eight priorities are far from enough, so a new definition of ToS is made, the first six bits are defined as DSCP, and the last two are reserved. Thus, the DSCP value ranges from 0 to 63. Figure 3 is a schematic diagram of the bits of DSCP and IP priority in an IPv4 header.

It can be seen from the above that for an IP type PDU session, the DSCP value can be directly determined according to the ToS field in the IP packet. However, for a non-IP type PDU session, the DSCP value cannot be determined. For example, the Ethernet frame format currently exists. No Ethernet frame format can provide a priority field, and thus the DSCP value cannot be determined according to the priority field, for example, for example. Unstructured data packets are not visible to the UPF, and the UPF cannot obtain DSCP values.

In view of this, the embodiment of the present application provides a communication method and device thereof, and provides a method for determining a DSCP for a non-IP type PDU session, thereby facilitating determining a paging policy for a non-IP type session.

It should be noted that the marking value involved in the embodiment of the present application may be a DSCP value, and the embodiment of the present application introduces the DSCP value as an example.

Currently, non-IP type PDU sessions include Ethernet type PDU sessions and unstructured type PDU sessions, and may include other non-IP type PDU sessions as standards evolve or communication technologies evolve. The embodiment of the present application is directed to an Ethernet type PDU session and an unstructured type PDU session. It should be understood that other non-IP type PDU sessions should fall within the protection scope of the embodiments of the present application.

The communication method provided by the embodiment of the present application will be described in detail from the perspective of multi-terminal interaction, with reference to FIG.

FIG. 4 is a schematic flowchart diagram of a communication method according to Embodiment 1 of the present application. The embodiment may include, but is not limited to, steps S401 to S407:

Step S401, the UPF configures a tag value generation rule for a non-IP type PDU session.

The UPF configures a tag value generation rule for an Ethernet type PDU session and a tag value generation rule for an unstructured type PDU session.

For the Ethernet type, the Ethernet frame format is modified in the 802.1Q/P standard, and a 4-byte 802.1Q tag is added between the source media access control (MAC) address field and the cooperation type field ( Tag). The priority (PRI) of these four bytes can be used as the class of service (CoS) of the Ethernet frame, and the CoS is similar to the ToS of layer three, except that the CoS is differentiated in layer 2, ToS Make a difference in layer three. It can be understood that CoS is similar to ToS, so the priority can be obtained from the CoS field.

The priority may be a priority code point (DEI/PCPority code point, PCP), a drop eligible indicator (DEI), or a PCP+DEI. The PCP is used to mark the priority level of the data frame, and the DEI is used to identify the drop priority level of the packet.

If the priority can be obtained from the CoS field, the tag value generation rule is a rule for generating a tag value according to a mapping relationship between the DEI and/or the PCP and the tag value, and may specifically be a value and a tag according to the DEI and/or PCP field. The mapping between values determines the rules for tag values. It can be understood that the DEI and/or PCP are the priority of the inner packet, and the inner packet is the data packet that the terminal device can apply.

If the priority field cannot be obtained from the CoS field, the tag value generation rule is a rule for generating a tag value according to the N6/N9 tunnel IP header information. The N6 tunnel is a tunnel between the UPF and the data network. When the IP header information of the N6 tunnel is transmitted between the UPF and the data network, the IP header information of the N6 tunnel is carried in the data packet. The N9 tunnel is between the UPF and the UPF. When the IP header information of the N9 tunnel is transmitted between the UPF and the UPF, the N9 tunnel IP header information is carried in the data packet. It can be understood that the N6/N9 tunnel IP header information is carried after the data packet is transmitted through the N6/N9 tunnel, and the N6/N9 tunnel IP header information can be regarded as the transport layer IP header information.

The IP header information of the N6/N9 tunnel includes the DSCP value, and the DSCP value is similar to the DSCP in the IPv4 packet header. Then, the rule for generating the tag value according to the N6/N9 tunnel IP header information is the N6/N9 tunnel IP header information. The included DSCP value is used as a rule for the tag value corresponding to the downlink packet.

For the unstructured type, since the unstructured type data is invisible to the UPF and there is no priority indication, the mapping value cannot be determined according to the mapping relationship between the DEI and/or PCP and the tag value, and can be based on the N6/N9 tunnel IP header. The information generates a tag value, and then for the unstructured type, its tag value generation rule is a rule for generating a tag value based on the N6/N9 tunnel IP header information.

According to the above summary, for the unstructured type PDU session, the UPF configures the tag value generation rule to generate a tag value according to the N6/N9 tunnel IP header information, that is, the DSCP value included in the N6/N9 tunnel IP header information is used as The tag value corresponding to the downstream packet. For an Ethernet type PDU session, in the case where the priority can be obtained, the UPF configures its tag value generation rule as a rule for generating a tag value according to a mapping relationship between the priority and the tag value, that is, according to the DEI and/or PCP and the tag value. The rule of the mapping relationship generates a tag value. If the priority cannot be obtained, the UPF configures its tag value generation rule to generate a tag value according to the N6/N9 tunnel IP header information.

Step S402, the UPF receives the downlink data packet of the non-IP type PDU session.

The UPF receives the downlink data packet of the non-IP type PDU session from the data network, where the access network tunnel information of the non-IP type PDU session is not stored in the UPF.

It can be understood that, before the UPF receives the downlink data packet of the non-IP type PDU session from the data network, the terminal device establishes a non-IP type PDU session, and the terminal device is in an idle state.

In step S403, the UPF determines the tag value corresponding to the downlink data packet according to the transport layer IP header information of the downlink data packet or the inner layer header information of the downlink data packet.

When receiving the downlink data packet, the UPF determines the transport layer IP header information of the downlink data packet or the inner layer header information of the downlink data packet. The transport layer IP header information of the downlink data packet is that the downlink data packet adds the transport layer IP header information to the downlink data packet during the transmission process, and may include the N6/N9 tunnel IP header information. The inner packet header information of the downlink data packet is the inner layer data packet information of the downlink data packet, and may include a priority.

The UPF determines the tag value corresponding to the downlink data packet according to the tag value generation rule of the non-IP type PDU session configured in step S401, combined with the transport layer IP header information of the downlink data packet or the inner layer header information of the downlink data packet.

In a possible implementation manner, if the UPF can determine the N6/N9 tunnel IP header information of the downlink data packet according to the transport layer IP header information of the downlink data packet, that is, the transport layer IP header information includes the N6/N9 tunnel IP header information, Then, the UPF determines the tag value corresponding to the downlink data packet according to the N6/N9 tunnel IP header information of the downlink data packet and the rule for generating the tag value according to the N6/N9 tunnel IP header information, that is, the N6/N9 tunnel IP header information of the downlink data packet. The included DSCP value is determined as the tag value corresponding to the downlink packet.

In a possible implementation manner, if the UPF can determine the priority of the downlink data packet according to the inner layer header information of the downlink data packet, that is, the inner layer header information includes the priority, the UPF according to the priority of the downlink data packet and the priority according to the priority The mapping between the level and the tag value generates a tag value. The rule corresponding to the downlink data packet determines the tag value corresponding to the priority of the downlink data packet according to the mapping relationship between the priority and the tag value, that is, according to the DEI and / Or the mapping relationship between the PCP and the tag value to find the tag value corresponding to the DEI and/or PCP of the downlink data packet.

In a possible implementation manner, the UPF may determine the tag value corresponding to the downlink data packet by considering parameters such as the session type, the address type, and the N6/N9 tunnel IP header information/priority. The session type is an unstructured type or an Ethernet type, and the address type is multicast or broadcast. The specific method for determining the value of the label by the UPF according to these parameters is not limited in the embodiment of the present application.

Step S404, the UPF sends a downlink data notification to the SMF, where the downlink data notification includes a tag value corresponding to the downlink data packet. Accordingly, the SMF receives the downlink data notification from the UPF.

The UPF, in the case of determining the tag value corresponding to the downlink data packet, sends a downlink data notification to the SMF, the downlink data notification including the tag value corresponding to the downlink data packet determined by the UPF. The downlink data notification may also include a session identifier (ID) of the non-IP type PDU session, and the session identifier is used to identify different non-IP type PDU sessions.

Step S405, the SMF determines the PPI corresponding to the downlink data packet according to the tag value corresponding to the downlink data packet.

When receiving the downlink data notification sent by the UPF, the SMF determines a paging policy indication (PPI) corresponding to the downlink data packet according to the flag value corresponding to the downlink data packet carried by the downlink data notification. There is a mapping relationship between the tag value and the PPI, and the corresponding PPI can be determined according to the tag value.

Step S406, the SMF sends a request message to the AMF, where the request message includes a PPI corresponding to the downlink data packet. Accordingly, the AMF receives the request message from the SMF.

The SMF sends a request message to the AMF in the case of determining the PPI corresponding to the downlink data packet, where the request message includes the PPI corresponding to the downlink data packet determined by the SMF, and may also include the session identifier of the non-IP type PDU session. The request message may be a call to a terminal device reachability service request.

Step S407, the AMF determines a paging policy of the downlink data packet according to the PPI corresponding to the downlink data packet, and performs paging.

When receiving the request message, the AMF determines a paging policy of the downlink data packet according to the PPI corresponding to the downlink data packet, and performs paging.

The paging policy may include a paging retransmission mechanism, that is, a paging frequency or a time interval; whether to page the terminal device when the AMF is heavily loaded; whether to apply the sub-region paging, for example, the last tracker of the terminal device first. Or the cell issues a page, and then pages in the entire registration area of the terminal device.

The AMF may send a paging response to the SMF, the paging response being used to indicate that the paging was successful or the paging failed. If the paging response indicates that the paging fails, the SMF sends a paging failure indication to the UPF to enable the UPF to initiate a response data processing policy, such as buffering or discarding.

The AMF determines the paging policy and the paging process is:

a. The AMF sends a paging command to each radio access network in the tracking area list, that is, sends a paging command to each base station in the tracking area list.

b. The base station sends a paging request to the terminal device.

The terminal device performs the service request process triggered by the terminal device, and the terminal device sends the service request signaling to the AMF through the base station, and the AMF performs the security authentication on the terminal device by using the AUSF, and the SMF restores the user plane resource on the network side for the non-IP type PDU session. The network side updates the base station side tunnel address and the forwarding tunnel. Through the service request process triggered by the terminal device, the terminal device can enter the connection state and restore the user plane resource of the non-IP type PDU session to transmit the downlink data of the data network.

d, the terminal device enters the connected state and successfully restores the user plane resource of the non-IP type PDU session;

e. The UPF sends the downlink data sent by the data network to the terminal device.

In the embodiment shown in FIG. 4, the flag value generation rule of the non-IP type PDU session is configured by the UPF, and if the downlink data packet is received, the transport layer IP header information of the downlink data packet or the inner layer of the downlink data packet is used. The packet header information is combined with the tag value generation rule to determine the tag value corresponding to the downlink data packet, and sends it to the SMF, so that the SMF determines the PPI of the downlink data packet, and the SMF sends the PPI of the downlink data packet to the AMF, and the AMF determines the paging. The policy is to perform paging to determine the tag value of the non-IP type PDU session in order to determine the paging policy and implement the paging policy determination of the non-IP type PDU session.

5 is a schematic flowchart of a communication method according to Embodiment 2 of the present application. For the same or similar parts of the embodiment shown in FIG. 4, refer to the detailed description of FIG. 4, and details are not described herein again. The embodiment shown in 5 may include, but is not limited to, steps S501 - S510:

Step S501, the UPF configures a tag value generation rule for the non-IP type PDU session.

Step S502, the PCF determines a mapping relationship between the service data flow and the tag value or a mapping relationship between the service quality stream and the tag value.

The terminal device establishes a non-IP type PDU session, such as an Ethernet type PDU session or an unstructured type PDU session. In the process of establishing a non-IP type PDU session by the terminal device, the SMF sends a session request message to the PCF, and the session request message may be a PDU-CAN session message.

When receiving the request sent by the SMF, the PCF obtains the service type, the service data flow (SDF) information, the protocol type, the N6 interface information, and the like from the application function AF/network exposure function (NEF). Information, from the unified data management UDM to obtain user subscription information. The PCF determines the mapping relationship between the SDF and the tag value in each non-IP type PDU session according to the obtained information, or determines the quality of service (QoS) flow and the tag value in each non-IP type PDU session. The mapping relationship between them.

It can be understood that the PCF dynamically determines the mapping relationship between the SDF and the tag value of each non-IP type PDU session or the mapping relationship between the QoS flow of each non-IP type PDU session and the tag value according to the obtained information. This is a fine-grained tag value generation rule. The tag value generation rule of the UPF configuration is a coarse-grained tag value generation rule. The coarse-grained and fine-grained method of determining the mark value may be performed by one of them, and may correspond to step S506a and step S506b, respectively.

Step S503: The PCF sends a session message to the SMF, where the session message includes a mapping relationship between the service data stream and the tag value and an SDF identifier (SDF ID), or includes a mapping relationship between the QoS flow and the tag value and a QoS flow. Identity, QFI). Accordingly, the SMF receives the session message from the PCF.

The PCF sends a session message to the SMF in the case of deciding the mapping relationship between the SDF and the tag value of each non-IP type PDU session or the mapping relationship between the QoS flow and the tag value of each non-IP type PDU session, and the session message may be It is a session response message, which is used to respond to the session request message, and may be a PDU-CAN session message.

In a possible implementation manner, the session message includes an SDF identifier (SDF ID) of the non-IP type PDU session and a mapping relationship between the SDF and the tag value. In a possible implementation, the session message includes a QFI of the non-IP type PDU session and a mapping relationship between the quality of service stream and the tag value.

Step S504, the SMF sends an N4 message to the UPF, where the N4 message includes a mapping relationship between the service data stream and the tag value and an SDF ID, or a mapping relationship between the quality of service stream and the tag value and QFI. Accordingly, the UPF receives the N4 message from the SMF.

The base station side configures the user plane path resource for the non-IP type PDU session, and the UPF configures the user plane path resource for the non-IP type PDU session, and the SMF configures the mapping relationship between the SDF and the tag value or the mapping relationship between the QoS flow and the tag value to the UPF. That is, the mapping relationship between the SDF and the tag value or the mapping relationship between the QoS flow and the tag value is sent to the UPF. At this point, the terminal device is in an idle state.

The SMF sends the mapping relationship between the SDF and the tag value or the mapping relationship between the QoS flow and the tag value to the UPF through the N4 message. N4 is an interface between the UPF and the SMF, and the N4 message is a message transmitted between the UPF and the SMF through the N4 interface. The N4 message also includes the SDF ID or QFI of the non-IP type PDU session. The N4 message may also include a session ID of a non-IP type PDU session.

The UPF can store the mapping relationship when receiving the mapping relationship between the SDF and the tag value or the mapping relationship between the QoS flow and the tag value.

Step S505, the UPF receives the downlink data packet of the non-IP type PDU session.

The UPF determines the transport layer IP header information of the downlink data packet or the inner layer header information of the downlink data packet when receiving the downlink data packet of the non-IP type PDU session.

If the transport layer IP header information of the downlink data packet includes the N6/N9 tunnel IP header information, or the inner layer header information of the downlink data packet includes the priority, step S506a is performed.

If the transport layer IP header information of the downlink data packet does not include the N6/N9 tunnel IP header information, and the inner layer header information of the downlink data packet does not include the priority, step S506b is performed. It can be understood that, at this time, the label value corresponding to the downlink data packet cannot be determined according to the transport layer IP header information or the inner layer header information of the downlink data packet.

Step S506a, the UPF determines the tag value corresponding to the downlink data packet according to the transport layer IP header information of the downlink data packet or the inner layer header information of the downlink data packet.

Step S506b: The UPF determines the tag value corresponding to the downlink data packet according to the mapping relationship included in the N4 message.

In the case that the UPF cannot determine the tag value corresponding to the downlink packet according to the transport layer IP header information or the inner packet header information of the downlink data packet, the UPF determines the tag corresponding to the downlink data packet according to the SDF ID and the mapping relationship between the SDF and the tag value. The value, or the tag value corresponding to the downlink packet is determined according to the QFI and the mapping relationship between the quality of service stream and the tag value.

Step S507: The UPF sends a downlink data notification to the SMF, where the downlink data notification includes a tag value corresponding to the downlink data packet. Accordingly, the SMF receives the downlink data notification from the UPF.

The downlink data notification includes a tag value corresponding to the downlink data packet.

Step S508, the SMF determines the PPI corresponding to the downlink data packet according to the tag value corresponding to the downlink data packet.

Step S509, the SMF sends a request message to the AMF, where the request message includes a PPI corresponding to the downlink data packet. Accordingly, the AMF receives the request message from the SMF.

Step S510, the AMF determines a paging policy of the downlink data packet according to the PPI corresponding to the downlink data packet, and performs paging.

The embodiment shown in FIG. 5, on the basis of the embodiment shown in FIG. 4, increases the mapping relationship between the PCF dynamic decision SDF and the tag value or the mapping relationship between the service quality stream and the tag value, so that the downlink data cannot be obtained. When the transport layer IP header information or the inner packet header information of the packet determines the tag value corresponding to the downlink data packet, the mapping corresponding to the downlink data packet may be determined according to the mapping relationship between the SDF and the tag value or the mapping relationship between the service quality flow and the tag value. Value, the determination of the tag value of the non-IP type PDU session is implemented in two ways to determine the paging policy, and the paging policy determination of the non-IP type PDU session is implemented.

FIG. 6 is a schematic flowchart of a communication method according to Embodiment 3 of the present application. The embodiment shown in FIG. 6 may include, but is not limited to, Step S601 to Step S609:

Step S601, the SMF configures a tag value generation rule for the non-IP type PDU session.

The SMF configures a tag value generation rule for an Ethernet type PDU session and a tag value generation rule for an unstructured type PDU session.

For the unstructured type PDU session, the SMF configures its tag value generation rule as a rule for generating a tag value according to the N6/N9 tunnel IP header information, that is, the DSCP value included in the N6/N9 tunnel IP header information is used as a tag corresponding to the downlink packet. value. For an Ethernet type PDU session, when the priority can be obtained, the SMF configures its tag value generation rule as a rule for generating a tag value according to a mapping relationship between the priority and the tag value, and if the priority cannot be obtained, The SMF configures its tag value generation rule as a rule for generating a tag value based on the N6/N9 tunnel IP header information.

Step S602: The UPF configures configuration information, where the configuration information specifies that the downlink data notification includes transport layer IP header information or inner layer header information.

The configuration information is used to specify the content of the downlink data notification sent by the UPF to the SMF, and specifically includes the transport layer IP header information or the inner header information, that is, the N6/N9 tunnel IP header information or priority is required. level.

It should be noted that the sequence of steps S601 and S602 is not limited in the embodiment of the present application.

Step S603, the UPF receives the downlink data packet of the non-IP type PDU session.

It should be noted that the configuration of the SMF and the UPF is before the terminal device establishes a non-IP type PDU session.

Step S604, the UPF acquires the transport layer IP header information of the downlink data packet or the inner layer header information of the downlink data according to the configuration information.

The UPF acquires the transport layer IP header information of the downlink data packet or the inner layer header information of the downlink data when receiving the downlink data packet of the non-IP type PDU session according to the content specified by the configuration information. The transport layer IP header information includes the N6/N9 tunnel IP header information, and the inner layer header information includes the priority.

Step S605: The UPF sends a downlink data notification to the SMF, where the downlink data notification includes the transport layer IP header information of the downlink data packet or the inner layer header information of the downlink data packet. Accordingly, the SMF receives the downlink data notification from the UPF.

The UPF sends a downlink data notification to the SMF according to the content specified by the configuration information, and the downlink data notification includes the transport layer IP header information of the downlink data packet or the inner layer header information of the downlink data packet.

When receiving the downlink data notification, the SMF may feed back the downlink data notification ack to the UPF to inform the UPF that the SMF receives the downlink data notification.

Step S606, the SMF determines the tag value corresponding to the downlink data packet according to the transport layer IP header information of the downlink data packet or the inner layer header information of the downlink data.

When receiving the downlink data notification, the SMF determines the tag value corresponding to the downlink data packet according to the transport layer IP header information of the downlink data packet included in the downlink data packet or the inner layer header information of the downlink data.

In a possible implementation manner, the SMF determines, according to the N6/N9 tunnel IP header information of the downlink data packet and the rule for generating the label value according to the N6/N9 tunnel IP header information, the label value corresponding to the downlink data packet, that is, the downlink data packet. The tag value included in the IP header information of the N6/N9 tunnel is determined as the tag value corresponding to the downlink packet.

In a possible implementation manner, the SMF determines a tag value corresponding to the downlink data packet according to a priority of the downlink data packet and a rule for generating a tag value according to a mapping relationship between the priority value and the tag value, that is, mapping according to the priority and the tag value. The relationship searches for the tag value corresponding to the priority of the downlink data packet, that is, searches for the DEI and/or the tag value corresponding to the PCP according to the mapping relationship between the DEI and/or the PCP and the tag value.

In a possible implementation manner, if the configuration information specifies that the downlink data notification further includes other information, such as a session type, an address type, and the like, the downlink data notification sent by the UPF to the SMF further includes the information, and the SMF may be based on the parameters. To determine the value of the tag corresponding to the downlink data packet, the specific method for determining the SMF according to the parameter is not limited in the embodiment of the present application.

Step S607, the SMF determines the PPI of the downlink data packet according to the tag value corresponding to the downlink data packet.

There is a mapping relationship between the tag value and the PPI, and the SMF can determine the PPI corresponding to the downlink packet according to the tag value corresponding to the downlink data packet. In addition to determining the PPI based on the tag value, the PPI can also be determined based on the session type and priority.

Step S608, the SMF sends a request message to the AMF, where the request message includes a PPI corresponding to the downlink data packet. Accordingly, the AMF receives the request message from the SMF.

Step S609, the AMF determines a paging policy of the downlink data packet according to the PPI corresponding to the downlink data packet, and performs paging.

For specific implementations of step S608 and step S609, reference may be made to the detailed description of step S406 and step S407 in the embodiment shown in FIG. 4, and details are not described herein again.

In the embodiment shown in FIG. 6, the tag value generation rule is configured by the SMF, and the UPF configures the downlink data to notify the content to be carried, and in the embodiment shown in FIG. 4, the tag value generation rule is configured by the UPF, which simplifies The function of the UPF, however, complicates the function of the SMF and can achieve the same effect as the embodiment shown in FIG.

As an optional embodiment, on the basis of the embodiment shown in FIG. 6, the process of dynamically determining the mapping relationship between the SDF and the tag value or the mapping relationship between the service quality flow and the tag value may be added, and the added process may be Figure 5 is similar, but the SMF does not need to send the N4 message carrying the mapping relationship to the UPF, and the SMF can determine the mapping relationship between the SDF and the tag value carried by the session message and the SDF ID, or the mapping relationship between the service quality flow and the tag value and the QFI. The value is marked to determine the PPI, so that the determination of the tag value of the non-IP type PDU session is implemented in two ways to determine the paging policy and implement the paging policy determination of the non-IP type PDU session.

FIG. 7 is a schematic flowchart of a communication method according to Embodiment 4 of the present application. The embodiment shown in FIG. 7 may include, but is not limited to, Step S701-Step S707:

Step S701, the AMF configures a paging policy generation rule for a non-IP type PDU session, and the paging policy generation rule includes generating a paging policy according to the session type and the priority.

Step S702: The UPF configures configuration information, where the configuration information specifies that the downlink data notification includes a session type and a priority.

The configuration information specifies that the downlink data sent by the UPF to the SMF includes the session type and priority of the non-IP type PDU session. The session type can be an Ethernet type or an unstructured type.

It should be noted that the sequence of steps S701 and S702 is not limited in the embodiment of the present application.

Step S703, the UPF receives the downlink data packet of the non-IP type PDU session.

It should be noted that the configuration of the AMF and the UPF is before the terminal device establishes a non-IP type PDU session.

Step S704, the UPF acquires the session type and the priority of the downlink data packet according to the configuration information.

The UPF obtains the session type and the priority of the downlink data packet of the non-IP type PDU session according to the configuration information.

Step S705: The UPF sends a downlink data notification to the SMF, where the downlink data notification includes a session type and a priority of the downlink data packet. Accordingly, the SMF receives the downlink data notification from the UPF.

Step S706, the SMF sends an N11 message to the AMF, where the N11 message includes the session type and the priority of the downlink data packet. Accordingly, the AMF receives the N11 message from the SMF.

N11 is an interface between the AMF and the SMF, and the N11 message is a message transmitted between the AMF and the SMF through the N11 interface.

After receiving the N11 message, the AMF may feed back an N11 message confirmation (N11message ack) to the SMF to inform the SMF that the AMF has received the N11 message.

Step S707, the AMF determines a paging policy of the downlink data packet according to the session type and the priority of the downlink data packet, and performs paging.

When receiving the N11 message, the AMF determines the paging policy of the downlink data packet according to the session type and the priority of the downlink data packet, and performs paging.

The AMF determines the paging policy. For the process of paging, refer to the detailed description in the embodiment shown in FIG. 4, and details are not described herein again.

In the embodiment shown in FIG. 7, neither the SMF nor the UPF configures the tag value generation rule, and the AMF directly determines the paging policy according to the session type and the priority of the downlink data packet, which can simplify the functions of the SMF and the UPF, and can also be implemented. The determination of the tag value of the non-IP type PDU session to determine the paging policy to implement the paging policy determination for the non-IP type PDU session.

FIG. 8 is a schematic flowchart of a communication method according to Embodiment 5 of the present application. FIG. 8 is based on the embodiment shown in FIG. 5, and extends a PCF dynamic decision mapping relationship to an intermediate UPF (intermediate, I-UPF) and The scenario of the anchor point UPF (anchor, A-UPF), that is, the scenario in which a plurality of UPFs are extended to the session, and the same parts as those in FIG. 5 are specifically described in FIG. 5, and details are not described herein again. The embodiment shown in FIG. 8 may include, but is not limited to, steps S801-S809:

Step S801, the I-UPF configures a tag value generation rule for the non-IP type PDU session.

It should be noted that the tag value generation rule of the non-IP type PDU session configured by the I-UPF can be synchronized to the A-UPF.

It can be understood that the I-UPF is a UPF in a remote area and is mainly responsible for forwarding. The A-UPF is a UPF in the central area and is mainly responsible for the execution of core functions.

Step S802, the PCF determines a mapping relationship between the service data flow and the tag value or a mapping relationship between the service quality stream and the tag value.

Step S803, the PCF sends a session message to the SMF, where the session message includes a mapping relationship between the SDF and the tag value and an SDF ID, or a mapping relationship between the quality of service stream and the tag value and QFI. Accordingly, the SMF receives the session message from the PCF.

Step S804, the SMF sends an N4 message to the A-UPF, where the N4 message includes a mapping relationship between the service data stream and the tag value and an SDF ID, or a mapping relationship between the quality of service stream and the tag value and QFI. Accordingly, the A-UPF receives the N4 message from the SMF.

The base station side configures user plane path resources for non-IP type PDU sessions. A-UPF and I-UPF configure user plane path resources for non-IP type PDU sessions, and SMF maps SDF to tag values or QoS flows and tag values. The mapping relationship is configured on the A-UPF, that is, the mapping relationship between the SDF and the tag value or the mapping relationship between the QoS flow and the tag value is sent to the A-UPF. At this point, the terminal device is in an idle state.

Step S805, the A-UPF receives the downlink data packet of the non-IP type PDU session.

Step S806a, the A-UPF determines the tag value corresponding to the downlink data packet according to the N6 tunnel IP header information of the downlink data packet or the inner layer header information of the downlink data packet.

The A-UPF determines the tag value corresponding to the downlink data packet according to the N6 tunnel IP header information of the downlink data packet or the inner layer header information of the downlink data packet.

Step S806b, the A-UPF determines the tag value corresponding to the downlink data packet according to the mapping relationship included in the N4 message.

The A-UPF determines the tag value corresponding to the downlink data packet according to the mapping relationship included in the N4 message.

Step S807, the A-UPF sets the flag value corresponding to the downlink data packet to the DSCP value of the N9 tunnel IP header.

The A-UPF sets the tag value corresponding to the downlink data packet to the DSCP value of the N9 tunnel IP header. Then, when the downlink data packet is transmitted to the I-UPF through the N9 interface, the DSCP value of the N9 tunnel IP header is carried, then I- When receiving the downlink data packet, the UPF can obtain the DSCP value of the IP header of the N9 tunnel.

Step S808: The A-UPF sends a downlink data packet to the I-UPF, where the downlink data packet includes a DSCP value of the N9 tunnel IP header. Accordingly, the I-UPF receives downlink packets from the A-UPF.

Since the downlink data packet sent by the A-UPF to the I-UPF is transmitted through the N9 interface, the downlink data packet carries the DSCP value of the N9 tunnel IP header.

Step S809: The I-UPF sends a downlink data notification to the SMF, where the downlink data notification includes a DSCP value of the N9 tunnel IP header. Accordingly, the SMF receives the downlink data notification from the I-UPF.

When receiving the downlink data notification, the SMF may notify the downlink data of the DSCP value of the N9 tunnel IP header included as the tag value.

Step S810, the SMF determines the PPI corresponding to the downlink data packet according to the DSCP value of the IP header of the N9 tunnel.

The SMF determines the PPI corresponding to the downlink data packet according to the DSCP value of the IP header of the N9 tunnel.

Step S811, the SMF sends a request message to the AMF, where the request message includes a PPI corresponding to the downlink data packet. Accordingly, the AMF receives the request message from the SMF.

Step S812, the AMF determines a paging policy of the downlink data packet according to the PPI corresponding to the downlink data packet, and performs paging.

In the embodiment shown in FIG. 8, the embodiment shown in FIG. 5 is extended to the scenarios of I-UPF and A-UPF. If there are multiple I-UPFs, the DSCP value of the N9 tunnel IP header can be in multiple I. - Forwarding between UPFs, and finally sent by an I-UPF to the SMF through downlink data notification, the same can be used to determine the tag value of the non-IP type PDU session, in order to determine the paging policy, and implement the paging policy of the non-IP type PDU session. determine.

As an optional embodiment, in the embodiment shown in FIG. 8, the flow of the PCF dynamic decision mapping relationship may be deleted, that is, the embodiment shown in FIG. 4 is extended to the scenarios of I-UPF and A-UPF, and The same effect is shown in the embodiment shown in FIG.

The above describes the method of the embodiment of the present application in detail, and the apparatus of the embodiment of the present application is provided below.

FIG. 8 is a schematic diagram showing the logical structure of a communication apparatus according to an embodiment of the present application. The communication apparatus 40 may include a processing unit 401 and a transceiver unit 402. The communication device 40 may be UPF or SMF or AMF in the embodiment shown in Figures 4-7, and may also be I-UPF or A-UPF or SMF or AMF in the embodiment shown in Figure 8.

If the communication device 40 is the UPF in the embodiment shown in FIG. 4-7, the transceiver unit 402 can be used to communicate with the SMF and the data network, for example, performing step S402 and step S404 in the embodiment shown in FIG. In step S504, step S505, and step S507 in the embodiment shown in FIG. 5, step S603 and step S605 in the embodiment shown in FIG. 6 are executed, and step S703 and step S705 in the embodiment shown in FIG. 7 are executed. The processing unit 401 can be configured to perform the operation of controlling the UPF, for example, performing step S401 and step S403 in the embodiment shown in FIG. 4, performing step S501, step S506a, and step S506b in the embodiment shown in FIG. In step S602 and step S604 in the embodiment, step S702 and step S704 in the embodiment shown in FIG. 7 are performed. For details, refer to the corresponding description in the embodiment shown in FIG. 4 to FIG. 7 , and details are not described herein again.

If the communication device 40 is the A-UPF in the embodiment shown in FIG. 8, the transceiver unit 402 can be used to communicate with the I-UPF, the SMF, and the data network, for example, performing step S804 and step S805 in the embodiment shown in FIG. And S808. The processing unit 401 can be configured to perform an operation of controlling the A-UPF, for example, performing step S806a, step S806b, and step S807 in the embodiment shown in FIG. For details, refer to the description in the embodiment shown in FIG. 8 , and details are not described herein again.

If the communication device 40 is an I-UPF in the embodiment shown in FIG. 8, the transceiving unit 402 can be used to communicate with the A-UPF and the SMF, for example, steps S808 and S809 in the embodiment shown in FIG. The processing unit 401 can be configured to perform an operation of controlling the A-UPF, for example, performing step S801 in the embodiment shown in FIG. For details, refer to the description in the embodiment shown in FIG. 8 , and details are not described herein again.

If the communication device 40 is the AMF in the embodiment shown in FIG. 4-8, the transceiver unit 402 can be used to communicate with the SMF and other communication devices, for example, performing step S406 in the embodiment shown in FIG. In step S509 in the embodiment, step S608 in the embodiment shown in FIG. 6 is executed, step S706 in the embodiment shown in FIG. 7 is executed, and step S811 in the embodiment shown in FIG. 8 is executed. The processing unit 401 can be used to perform the operation of controlling the AMF, for example, performing step S407 in the embodiment shown in FIG. 4, executing step S510 in the embodiment shown in FIG. 5, and executing step S609 in the embodiment shown in FIG. In step S701 and step S707 in the embodiment shown in Fig. 7, step S812 in the embodiment shown in Fig. 8 is executed. For details, refer to the corresponding description in the embodiment shown in FIG. 4 to FIG. 8 , and details are not described herein again.

If the communication device 40 is the SMF in the embodiment shown in FIG. 4-8, the transceiver unit 402 can be used to communicate with the AMF, the UPF, and other communication devices, for example, performing step S404 and step S406 in the embodiment shown in FIG. Step S503, step S504, step S507 and step S509 in the embodiment shown in FIG. 5 are executed, and steps S605 and S608 in the embodiment shown in FIG. 6 are executed to execute step S705 and steps in the embodiment shown in FIG. S706, performing step S803, step S804, step S809, and step S811 in the embodiment shown in FIG. The processing unit 401 can be used to perform the operation of controlling the AMF, for example, performing step S405 in the embodiment shown in FIG. 4, executing step S508 in the embodiment shown in FIG. 5, and performing step S601 and step S606 in the embodiment shown in FIG. And step S607, step S810 in the embodiment shown in FIG. 8 is performed. For details, refer to the corresponding description in the embodiment shown in FIG. 4 to FIG. 8 , and details are not described herein again.

FIG. 9 is a simplified schematic diagram of a physical structure of a communication device according to an embodiment of the present disclosure. The communication device 50 may be a UPF or an SMF or an AMF in the embodiment shown in FIG. 4-7, or may be as shown in FIG. I-UPF or A-UPF or SMF or AMF in the examples. The communication device 50 includes a transceiver 501, a processor 502, and a memory 503. The transceiver 501, the processor 502, and the memory 503 may be connected to one another via a bus 504, or may be connected in other manners. Related functions implemented by the processing unit 401 shown in FIG. 8 may be implemented by one or more processors 502. The related functions implemented by the transceiver unit 402 shown in FIG. 8 can be implemented by the transceiver 501.

The memory 503 includes, but is not limited to, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read only memory (EPROM), or A compact disc read-only memory (CD-ROM) for use in related instructions and data.

The transceiver 501 is configured to transmit data and/or signaling, as well as receive data and/or signaling.

The processor 502 may include one or more processors, for example, including one or more central processing units (CPUs). In the case where the processor 502 is a CPU, the CPU may be a single core CPU, It can be a multi-core CPU.

If the communication device 50 is a UPF, the processor 502 is configured to support the UPF to perform step S401 and step S403 in the embodiment shown in FIG. 4, and perform step S501, step S506a, and step S506b in the embodiment shown in FIG. In step S602 and step S604 in the embodiment shown in FIG. 6, step S702 and step S704 in the embodiment shown in FIG. 7 are executed.

If the communication device 50 is an A-UPF, the processor 502 is configured to support the A-UPF to perform steps S806a, S806b, and S807 in the embodiment shown in FIG.

If the communication device 50 is an I-UPF, the processor 502 is configured to support the I-UPF to perform step S801 in the embodiment shown in FIG.

If the communication device 50 is an AMF, the processor 502 is configured to support the AMF to perform step S407 in the embodiment shown in FIG. 4, and perform step S510 in the embodiment shown in FIG. 5 to perform the steps in the embodiment shown in FIG. S609, performing step S701 and step S707 in the embodiment shown in FIG. 7 to perform step S812 in the embodiment shown in FIG.

The processor 502 is configured to support the SMF to perform step S405 in the embodiment shown in FIG. S601, step S606 and step S607, step S810 in the embodiment shown in Fig. 8 is executed.

The memory 503 is used to store program codes and data of the communication device 50.

The transceiver 501 is configured to communicate with other communication devices. If the communication device 50 is a UPF, the transceiver 501 is configured to communicate with the SMF and the data network; if the communication device is an A-UPF, the transceiver 501 is used with the I- The UPF, SMF, and data network communicate; if the communication device is an I-UPF, the transceiver is used to communicate with the A-UPF and the SMF; if the communication device is an AMF, the transceiver 501 is configured to communicate with the SMF and other communication devices. If the communication device is an SMF, the transceiver 501 is configured to communicate with AMF, UPF, and other communication devices.

For details about the steps performed by the processor 502 and the transceiver 501, refer to the description of the embodiment shown in FIG. 4 to FIG. 8 , and details are not described herein again.

It will be appreciated that Figure 9 only shows a simplified design of the communication device. In practical applications, the communication device may also include other necessary components, including but not limited to any number of transceivers, processors, controllers, memories, communication units, etc., and all communication devices that can implement the present application are in this embodiment. Within the scope of protection of the application.

The embodiment of the present application further provides a communication system, including the AMF, SMF, and UPF shown in FIG. 4, FIG. 6, and FIG. 7, or including the AMF, PCF, SMF, and UPF shown in FIG. 5, or including the FIG. AMF, PCF, SMF, I-UPF and A-UPF are shown.

One of ordinary skill in the art can understand all or part of the process of implementing the above embodiments, which can be completed by a computer program to instruct related hardware, the program can be stored in a computer readable storage medium, when the program is executed The flow of the method embodiments as described above may be included. The foregoing storage medium includes various media that can store program codes, such as a ROM or a random access memory RAM, a magnetic disk, or an optical disk. Accordingly, yet another embodiment of the present application provides a computer readable storage medium having instructions stored therein that, when executed on a computer, cause the computer to perform the methods described in the various aspects above.

Yet another embodiment of the present application also provides a computer program product comprising instructions that, when executed on a computer, cause the computer to perform the methods described in the various aspects above.

Those of ordinary skill in the art will appreciate that the elements and algorithm steps of the various examples described in connection with the embodiments disclosed herein can be implemented in electronic hardware or a combination of computer software and electronic hardware. Whether these functions are performed in hardware or software depends on the specific application and design constraints of the solution. A person skilled in the art can use different methods to implement the described functions for each particular application, but such implementation should not be considered to be beyond the scope of the present application.

A person skilled in the art can clearly understand that for the convenience and brevity of the description, the specific working process of the system, the device and the unit described above can refer to the corresponding process in the foregoing method embodiment, and details are not described herein again.

In the several embodiments provided by the present application, it should be understood that the disclosed systems, devices, and methods may be implemented in other manners. For example, the device embodiments described above are merely illustrative. For example, the division of the unit is only a logical function division. In actual implementation, there may be another division manner, for example, multiple units or components may be combined or Can be integrated into another system, or some features can be ignored or not executed. In addition, the mutual coupling or direct coupling or communication connection shown or discussed may be an indirect coupling or communication connection through some interface, device or unit, and may be in an electrical, mechanical or other form.

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

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

In the above embodiments, it may be implemented in whole or in part by software, hardware, firmware, or any combination thereof. When implemented in software, it may be implemented in whole or in part in the form of a computer program product. The computer program product includes one or more computer instructions. When the computer program instructions are loaded and executed on a computer, the processes or functions described in accordance with embodiments of the present invention are generated in whole or in part. The computer can be a general purpose computer, a special purpose computer, a computer network, or other programmable device. The computer instructions can be stored in or transmitted by a computer readable storage medium. The computer instructions may be from a website site, computer, server or data center via a wired (eg, coaxial cable, fiber optic, digital subscriber line (DSL)) or wireless (eg, infrared, wireless, microwave, etc.) Another website site, computer, server, or data center for transmission. The computer readable storage medium can be any available media that can be accessed by a computer or a data storage device such as a server, data center, or the like that includes one or more available media. The usable medium may be a magnetic medium (eg, a floppy disk, a hard disk, a magnetic tape), an optical medium (eg, a DVD), or a semiconductor medium (such as a solid state disk (SSD)) or the like.

Claims

A communication method, comprising:

The user plane function UPF receives the downlink data packet of the non-Internet Protocol IP type protocol data unit PDU session, and the access network tunnel information of the non-IP type PDU session is not stored in the UPF;

Determining, by the UPF, a tag value corresponding to the downlink data packet according to the transport layer IP packet header information of the downlink data packet or the inner layer packet header information of the downlink data packet;

The UPF sends a downlink data notification to the session management function SMF, where the downlink data notification includes a tag value corresponding to the downlink data packet, and a flag value corresponding to the downlink data packet is used by the SMF to determine the downlink data packet. The paging policy identifies the PPI.
The method according to claim 1, wherein before the UPF receives the downlink data packet of the non-IP type PDU session, the method further includes:

The UPF configures a tag value generation rule of the non-IP type PDU session, where the tag value generation rule is a rule for generating a tag value according to a mapping relationship between a priority and a tag value, or according to an N6/N9 tunnel IP header information. A rule that generates tag values.
The method according to claim 2, wherein the UPF determines a tag value corresponding to the downlink data packet according to the transport layer IP header information of the downlink data packet or the inner layer header information of the downlink data packet. include:

Determining, by the UPF, the N6/N9 tunnel IP header information of the downlink data packet according to the transport layer IP header information of the downlink data packet;

Determining, by the UPF, the tag value corresponding to the downlink data packet according to the N6/N9 tunnel IP header information of the downlink data packet and the rule for generating a tag value according to the N6/N9 tunnel IP header information;

Or determining, by the UPF, a priority of the downlink data packet according to inner header information of the downlink data packet;

The UPF determines a tag value corresponding to the downlink data packet according to a priority of the downlink data packet and a rule for generating a tag value according to a mapping relationship between a priority value and a tag value.
A communication method, comprising:

The UPF receives the downlink data packet of the non-IP type PDU session, and the access network tunnel information of the non-IP type PDU session is not stored in the UPF;

Obtaining, by the UPF, the transport layer IP header information of the downlink data packet or the inner layer header information of the downlink data according to the configuration information;

The UPF sends a downlink data notification to the SMF, where the downlink data notification includes a transport layer IP header information of the downlink data packet or an inner layer header information of the downlink data packet, and a transport layer IP header information of the downlink data packet. Or the inner layer header information of the downlink data packet is used by the SMF to determine a tag value corresponding to the downlink data packet.
The method according to claim 4, wherein before the UPF receives the downlink data packet of the non-IP type PDU session, the method further includes:

The UPF configures the configuration information, where the configuration information specifies that the downlink data notification includes transport layer IP header information or inner layer header information.
A communication method, comprising:

The SMF receives the downlink data notification sent by the UPF, where the downlink data notification includes the transport layer IP header information of the downlink data packet or the inner layer header information of the downlink data;

Determining, by the SMF, a tag value corresponding to the downlink data packet according to the transport layer IP header information of the downlink data packet or the inner layer header information of the downlink data;

Determining, by the SMF, a PPI of the downlink data packet according to a tag value corresponding to the downlink data packet;

The SMF sends a request message to the AMF, where the request message includes the PPI, and the PPI is used by the AMF to determine a paging policy of the downlink data packet.
The method according to claim 6, wherein before the SMF receives the downlink data notification sent by the UPF, the method further includes:

The SMF configures a DSCP generation rule of the non-IP type PDU session, where the DSCP generation rule is a rule for generating a tag value according to a mapping relationship between a priority and a tag value, or generating a tag according to the N6/N9 tunnel IP header information. The rule of value.
The method according to claim 7, wherein the SMF determines a tag value corresponding to the downlink data packet according to a transport layer IP header information of the downlink data packet or an inner layer header information of the downlink data, including :

Determining, by the SMF, the N6/N9 tunnel IP header information of the downlink data packet according to the transport layer IP header information of the downlink data packet;

Determining, by the SMF, the tag value corresponding to the downlink data packet according to the N6/N9 tunnel IP header information of the downlink data packet and the rule for generating a tag value according to the N6/N9 tunnel IP header information;

Or the SMF determines a priority of the downlink data packet according to the inner layer header information of the downlink data packet;

The SMF determines a tag value corresponding to the downlink data packet according to a priority of the downlink data packet and a rule for generating a tag value according to a mapping relationship between a priority value and a tag value.
A communication method, comprising:

The UPF receives the downlink data packet of the non-IP type PDU session, and the access network tunnel information of the non-IP type PDU session is not stored in the UPF;

Obtaining, by the UPF, a session type of the non-IP type PDU session and a priority of the downlink data packet according to the configuration information;

The UPF sends a downlink data notification to the SMF, where the downlink data notification includes the session type and the priority of the downlink data packet.
The method according to claim 9, wherein before the UPF receives the downlink data packet of the non-IP type PDU session, the method further includes:

The UPF configures the configuration information, where the configuration information specifies that the downlink data notification includes a session type and a priority.
A communication method, the communication method is applied to a non-IP type PDU session, and the access network tunnel information of the non-IP type PDU session is not stored in the UPF, and the method includes:

The AMF receives the session type sent by the SMF and the priority of the downlink data packet of the non-IP type PDU session;

The AMF determines a paging policy of the downlink data packet according to the session type and a priority of the downlink data packet.
The method according to claim 11, wherein before the AMF receives the session type sent by the SMF and the priority of the downlink data packet of the non-IP type PDU session, the method further includes:

The AMF configures a paging policy generation rule of the non-IP type PDU session, and the paging policy generation rule includes generating a paging policy according to a session type and a priority.
A communication method, the communication method is applied to a non-IP type PDU session, and the access network tunnel information of the non-IP type PDU session is not stored in the UPF, and the method includes:

Receiving, by the SMF, a downlink data notification sent by the UPF, where the downlink data notification includes a session type of the non-IP type PDU session and a priority of the downlink data packet;

The SMF sends the session type and the priority of the downlink data packet to the AMF.
A communication device, characterized in that the communication device is for performing the method according to any of claims 1-3.
A communication device, characterized in that the communication device is for performing the method according to any of claims 4-5.
A communication device, characterized in that the communication device is for performing the method according to any of claims 6-8.
A communication device, characterized in that the communication device is for performing the method according to any of claims 9-10.
A communication device, characterized in that the communication device is for performing the method according to any of claims 11-12.
A communication device, characterized in that the communication device is for performing the method of claim 13.