WO2019101041A1 - Procédé de communication et dispositif associé - Google Patents

Procédé de communication et dispositif associé Download PDF

Info

Publication number
WO2019101041A1
WO2019101041A1 PCT/CN2018/116215 CN2018116215W WO2019101041A1 WO 2019101041 A1 WO2019101041 A1 WO 2019101041A1 CN 2018116215 W CN2018116215 W CN 2018116215W WO 2019101041 A1 WO2019101041 A1 WO 2019101041A1
Authority
WO
WIPO (PCT)
Prior art keywords
downlink data
data packet
upf
tag value
header information
Prior art date
Application number
PCT/CN2018/116215
Other languages
English (en)
Chinese (zh)
Inventor
朱强华
熊春山
周铮
Original Assignee
华为技术有限公司
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 华为技术有限公司 filed Critical 华为技术有限公司
Publication of WO2019101041A1 publication Critical patent/WO2019101041A1/fr

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L9/00—Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols
    • H04L9/40—Network security protocols
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W68/00—User notification, e.g. alerting and paging, for incoming communication, change of service or the like
    • H04W68/02—Arrangements for increasing efficiency of notification or paging channel

Definitions

  • the embodiments of the present application relate to the field of communications technologies, and in particular, to a communication method and apparatus thereof.
  • 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.
  • 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.
  • the network knows the base station to which the UE is connected, and can directly send data to 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.
  • the UE 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.
  • the SMF 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.
  • 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.
  • 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.
  • TA tracking area
  • 5G Fifth-generation mobile communication technology
  • IP e.g. IPv4, IPv6
  • Ethernet Ethernet
  • 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.
  • 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.
  • PPI paging policy indication
  • an embodiment of the present application provides a UPF, including a unit or means for performing the steps of the above 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 configured to store a program and data, and at least one processing element is configured to perform the first aspect of the present application.
  • 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.
  • an embodiment of the present application provides a program, when executed by a processor, for performing the method of the above first 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • 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 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 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.
  • an embodiment of the present application provides a UPF, including a unit or a means for performing the foregoing steps of the seventh 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.
  • 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.
  • an embodiment of the present application provides a program, when executed by a processor, for performing the method of the above seventh 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.
  • 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.
  • 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.
  • 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.
  • an embodiment of the present application provides an SMF, including a unit or a means for performing the steps of the thirteenth aspect above.
  • 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 includes 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.
  • 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.
  • the embodiment of the present application provides a program for executing the method of the above thirteenth aspect when executed by a processor.
  • the embodiment of the present application provides a program product, such as a computer readable storage medium, including the program of the seventeenth aspect.
  • 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.
  • 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.
  • 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.
  • 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 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 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.
  • the embodiment of the present application provides a UPF, including a unit or means for performing the steps of the above nineteenth 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 is not limited to:
  • 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.
  • the embodiment of the present application provides a program for executing the method of the above nineteenth aspect when executed by a processor.
  • 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.
  • 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.
  • 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.
  • 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 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.
  • 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.
  • 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.
  • the embodiment of the present application provides a program for executing the method of the above twenty-fifth aspect when executed by a processor.
  • 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.
  • 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.
  • 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.
  • 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.
  • 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 is used to execute the twentieth tenth of the present application.
  • 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.
  • the embodiment of the present application provides a program for executing the method of the above twenty-fifth aspect when executed by a processor.
  • 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.
  • 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.
  • FIG. 1 is a schematic diagram of a network triggered service request process
  • FIG. 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
  • 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.
  • FIG. 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.
  • 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
  • the interface between the (R) AN and the AMF is an N2 interface
  • the interface between the (R) AN and the UPF is an N3 interface
  • 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
  • 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
  • the interface between the AUX and the UDM is the N13 interface.
  • Interface the interface between AMF and AMF is N14 interface
  • 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.
  • 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
  • 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.
  • IP IP multimedia network subsystem
  • IMS IP multimedia core network subsystem
  • 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.
  • QoS quality of service
  • 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.
  • the DSCP value can be directly determined according to the ToS field in the IP packet.
  • the DSCP value cannot be determined.
  • 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.
  • 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.
  • marking value involved in the embodiment of the present application may be a DSCP value
  • the embodiment of the present application introduces the DSCP value as an example.
  • 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.
  • 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.
  • 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.
  • PCP priority code point
  • DEI drop eligible indicator
  • PCP+DEI priority code point
  • the PCP is used to mark the priority level of the data frame
  • the DEI is used to identify the drop priority level of the packet.
  • 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.
  • 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.
  • the IP header information of the N6 tunnel is carried in the data packet.
  • the N9 tunnel is 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.
  • 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.
  • 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.
  • 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.
  • the terminal device 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • ID session identifier
  • Step S405 the SMF determines the PPI corresponding to the downlink data packet according to the tag value corresponding to the downlink data packet.
  • the SMF 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.
  • PPI paging policy indication
  • 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.
  • 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.
  • a paging retransmission mechanism that is, a paging frequency or a time interval
  • 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.
  • a response data processing policy such as buffering or discarding.
  • the AMF determines the paging policy and the paging process is:
  • 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.
  • 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.
  • 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.
  • the terminal device enters the connected state and successfully restores the user plane resource of the non-IP type PDU session;
  • the UPF sends the downlink data sent by the data network to the terminal device.
  • 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.
  • FIG. 5 is a schematic flowchart of a communication method according to Embodiment 2 of the present application.
  • steps S501 - S510 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.
  • a non-IP type PDU session such as an Ethernet type PDU session or an unstructured type PDU session.
  • the SMF sends a session request message to the PCF, and the session request message may be a PDU-CAN session message.
  • the PCF 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.
  • 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.
  • SDF ID SDF identifier
  • QFI QoS flow. Identity
  • 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.
  • 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.
  • 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
  • the UPF configures the user plane path resource for the non-IP type PDU session
  • 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.
  • 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.
  • step S506a is performed.
  • 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • Step S603 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.
  • the terminal device 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • 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
  • the SMF may be based on the parameters.
  • 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.
  • the SMF can determine the PPI corresponding to the downlink packet according to the tag value corresponding to the downlink data packet.
  • 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.
  • step S608 and step S609 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.
  • 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.
  • 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.
  • Step S703 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.
  • the terminal device 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.
  • 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.
  • 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.
  • N11 message confirmation N11message ack
  • 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.
  • 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 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.
  • a response data processing policy such as buffering or discarding.
  • the AMF determines the paging policy.
  • 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.
  • 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.
  • tag value generation rule of the non-IP type PDU session configured by the I-UPF can be synchronized to the A-UPF.
  • 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • 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
  • 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.
  • step S602 and step S604 in the embodiment step S702 and step S704 in the embodiment shown in FIG. 7 are performed.
  • step S702 and step S704 in the embodiment shown in FIG. 7 are performed.
  • details refer to the corresponding description in the embodiment shown in FIG. 4 to FIG. 7 , and details are not described herein again.
  • 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.
  • 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.
  • 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.
  • 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.
  • 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
  • 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.
  • step S701 and step S707 in the embodiment shown in Fig. 7 step S812 in the embodiment shown in Fig. 8 is executed.
  • step S812 in the embodiment shown in Fig. 8 is executed.
  • 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.
  • step S508 in the embodiment shown in FIG. 5 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.
  • step S508 in the embodiment shown in FIG. 5 executing step S508 in the embodiment shown in FIG. 5, and performing step S601 and step S606 in the embodiment shown in FIG.
  • step S607, step S810 in the embodiment shown in FIG. 8 is performed.
  • 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.
  • RAM random access memory
  • ROM read-only memory
  • EPROM erasable programmable read only memory
  • CD-ROM compact disc read-only memory
  • 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).
  • processors for example, including one or more central processing units (CPUs).
  • CPUs central processing units
  • the CPU may be a single core CPU, It can be a multi-core CPU.
  • 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.
  • 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.
  • the processor 502 is configured to support the A-UPF to perform steps S806a, S806b, and S807 in the embodiment shown in FIG.
  • the processor 502 is configured to support the I-UPF to perform step S801 in the embodiment shown in FIG.
  • 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.
  • Figure 9 only shows a simplified design of the communication device.
  • 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.
  • 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.
  • 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.
  • the disclosed systems, devices, and methods may be implemented in other manners.
  • the device embodiments described above are merely illustrative.
  • the division of the unit is only a logical function division.
  • 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.
  • 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.
  • 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.
  • the above embodiments it may be implemented in whole or in part by software, hardware, firmware, or any combination thereof.
  • 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.
  • the computer program 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.

Landscapes

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

Abstract

Les modes de réalisation de la présente invention fournissent un procédé de communication et un dispositif associé. Le procédé peut comprendre les étapes suivantes consistant à : recevoir, par une UPF, un paquet de données de liaison descendante d'une session de PDU de type autre que IP, des informations de tunnel de réseau d'accès de la session de PDU de type autre que IP n'ayant pas été mémorisées dans l'UPF ; déterminer, par l'UPF, conformément à des informations d'en-tête d'IP de couche de transport du paquet de données de liaison descendante ou à des informations d'en-tête de couche interne du paquet de données de liaison descendante, une valeur d'étiquette correspondant au paquet de données de liaison descendante ; envoyer, par l'UPF, une notification de données de liaison descendante à une fonction de gestion de session (SMF), la notification de données de liaison descendante comprenant la valeur d'étiquette correspondant au paquet de données de liaison descendante, la valeur d'étiquette correspondant au paquet de données de liaison descendante étant utilisée par la SMF pour déterminer un identifiant de politique de radiomessagerie du paquet de données de liaison descendante. Les modes de réalisation de la présente invention permettent de déterminer la valeur d'étiquette de la session de PDU de type autre que IP, et de déterminer en outre une politique de radiomessagerie.
PCT/CN2018/116215 2017-11-21 2018-11-19 Procédé de communication et dispositif associé WO2019101041A1 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201711209692.0A CN109818917B (zh) 2017-11-21 2017-11-21 一种通信方法及其装置
CN201711209692.0 2017-11-21

Publications (1)

Publication Number Publication Date
WO2019101041A1 true WO2019101041A1 (fr) 2019-05-31

Family

ID=66601426

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2018/116215 WO2019101041A1 (fr) 2017-11-21 2018-11-19 Procédé de communication et dispositif associé

Country Status (2)

Country Link
CN (1) CN109818917B (fr)
WO (1) WO2019101041A1 (fr)

Families Citing this family (9)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN111800857B (zh) * 2019-08-27 2023-01-03 维沃移动通信有限公司 一种寻呼方法和设备
CN112867039B (zh) * 2019-11-28 2022-04-05 大唐移动通信设备有限公司 一种用户面网元故障处理方法和装置
EP4140163A4 (fr) * 2020-04-23 2024-01-17 Qualcomm Inc Procédure de radiomessagerie à terminaison mobile (mt) pour des appels de sous-système multimédia ip (ims)
CN113573381A (zh) * 2020-04-28 2021-10-29 大唐移动通信设备有限公司 非ip类型数据的传输处理方法、设备、装置及介质
CN111526552B (zh) * 2020-05-13 2024-02-02 腾讯科技（深圳）有限公司 Ue执行的方法及ue、以及smf实体执行的方法及smf实体
CN115004847A (zh) * 2020-05-29 2022-09-02 Oppo广东移动通信有限公司 一种数据传输方法、设备及存储介质
CN114979963A (zh) * 2021-02-25 2022-08-30 华为技术有限公司 组播/广播业务的通信方法、装置及系统
CN117062142A (zh) * 2022-05-05 2023-11-14 华为技术有限公司 通信方法和装置
CN115842793A (zh) * 2022-11-16 2023-03-24 深圳市丰润达科技有限公司 三层交换机的路由转发方法、装置、设备及存储介质

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101931898A (zh) * 2009-06-26 2010-12-29 华为技术有限公司 用户面数据的传输方法、装置及系统
CN102843348A (zh) * 2011-06-23 2012-12-26 中兴通讯股份有限公司 业务数据流处理方法及装置
WO2017173098A1 (fr) * 2016-03-30 2017-10-05 Idac Holdings, Inc. Systèmes et procédés de prise en charge de dispositifs à faible mobilité dans un réseau sans fil de prochaine génération
WO2017196161A1 (fr) * 2016-05-13 2017-11-16 Samsung Electronics Co., Ltd. Procédé et appareil de commande de connexion légère

Family Cites Families (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN102595508B (zh) * 2011-01-14 2016-09-28 中兴通讯股份有限公司 一种策略控制方法及系统
CN103731919A (zh) * 2012-10-15 2014-04-16 中国移动通信集团公司 一种基于优先级的寻呼方法和设备

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101931898A (zh) * 2009-06-26 2010-12-29 华为技术有限公司 用户面数据的传输方法、装置及系统
CN102843348A (zh) * 2011-06-23 2012-12-26 中兴通讯股份有限公司 业务数据流处理方法及装置
WO2017173098A1 (fr) * 2016-03-30 2017-10-05 Idac Holdings, Inc. Systèmes et procédés de prise en charge de dispositifs à faible mobilité dans un réseau sans fil de prochaine génération
WO2017196161A1 (fr) * 2016-05-13 2017-11-16 Samsung Electronics Co., Ltd. Procédé et appareil de commande de connexion légère

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
"3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; System Architecture for the 5G System; Stage 2 (Release 15", 3GPP TS 23.501, 13 November 2017 (2017-11-13), XP051391712 *

Also Published As

Publication number Publication date
CN109818917B (zh) 2021-10-26
CN109818917A (zh) 2019-05-28

Similar Documents

Publication Publication Date Title
WO2019101041A1 (fr) Procédé de communication et dispositif associé
US11146462B2 (en) Network slice management method, device, and system
JP7183416B2 (ja) 時間依存ネットワーキング通信方法及び装置
US10616120B2 (en) Service layer southbound interface and quality of service
US20220060416A1 (en) Routing Rule Management Method and Communications Apparatus
EP3836577B1 (fr) Procédé et dispositif de gestion de session pour groupes d'utilisateurs
WO2020001572A1 (fr) Appareil et procédé de communication
CN111526552B (zh) Ue执行的方法及ue、以及smf实体执行的方法及smf实体
WO2017215401A1 (fr) Procédé et dispositif de traitement de message
US20220377819A1 (en) Method and apparatus for establishing data transmission link and computer-readable storage medium
CN112913212A (zh) 控制面-用户面分离的用户面功能控制
US20220182804A1 (en) Communication processing method, and communication processing apparatus and system
BR112021012912A2 (pt) Método para suportar comunicação entre ues, portadora, e, aparelho
US11546255B2 (en) Packet processing method, controller, and forwarding device
US10924518B2 (en) UPF programming over enhanced N9 interface
CN110166414B (zh) 一种通信方法、装置及系统
US11856632B2 (en) Method and apparatus for implementing a forwarding path on a user plane function network element
WO2021109824A1 (fr) Procédé et dispositif de création de session, procédé et dispositif de commande de création de session, système de création de session, élément de réseau et support de stockage
WO2021135650A1 (fr) Procédé et appareil de communication
WO2017177753A1 (fr) Procédé de gestion de porteuse à base de flux, et procédé et dispositif de transmission de données
WO2019196000A1 (fr) Procédés et système pour réaliser une communication par chemin rapide de petites données
KR20220158018A (ko) 접속 수립 방법, 통신 장치, 및 시스템
CN109819530B (zh) 一种通信方法及装置
WO2018214821A1 (fr) Procédé, dispositif et système de contrôle de qualité de service
CN114128227B (zh) 在支持SRv6的数据面上传输MTNC-ID以实现5G传输

Legal Events

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

Ref document number: 18880583

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 18880583

Country of ref document: EP

Kind code of ref document: A1