WO2021088554A1 - 一种通信方法及装置 - Google Patents

一种通信方法及装置 Download PDF

Info

Publication number
WO2021088554A1
WO2021088554A1 PCT/CN2020/117222 CN2020117222W WO2021088554A1 WO 2021088554 A1 WO2021088554 A1 WO 2021088554A1 CN 2020117222 W CN2020117222 W CN 2020117222W WO 2021088554 A1 WO2021088554 A1 WO 2021088554A1
Authority
WO
WIPO (PCT)
Prior art keywords
qos flow
identifier
connection
network element
management network
Prior art date
Application number
PCT/CN2020/117222
Other languages
English (en)
French (fr)
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 WO2021088554A1 publication Critical patent/WO2021088554A1/zh

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W8/00—Network data management
    • H04W8/02—Processing of mobility data, e.g. registration information at HLR [Home Location Register] or VLR [Visitor Location Register]; Transfer of mobility data, e.g. between HLR, VLR or external networks
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W24/00—Supervisory, monitoring or testing arrangements
    • H04W24/04—Arrangements for maintaining operational condition
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W36/00—Hand-off or reselection arrangements
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W36/00—Hand-off or reselection arrangements
    • H04W36/0005—Control or signalling for completing the hand-off
    • H04W36/0011—Control or signalling for completing the hand-off for data sessions of end-to-end connection
    • H04W36/0016—Hand-off preparation specially adapted for end-to-end data sessions
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W36/00—Hand-off or reselection arrangements
    • H04W36/0005—Control or signalling for completing the hand-off
    • H04W36/0011—Control or signalling for completing the hand-off for data sessions of end-to-end connection
    • H04W36/0027—Control or signalling for completing the hand-off for data sessions of end-to-end connection for a plurality of data sessions of end-to-end connections, e.g. multi-call or multi-bearer end-to-end data connections
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W36/00—Hand-off or reselection arrangements
    • H04W36/0005—Control or signalling for completing the hand-off
    • H04W36/0011—Control or signalling for completing the hand-off for data sessions of end-to-end connection
    • H04W36/0033—Control or signalling for completing the hand-off for data sessions of end-to-end connection with transfer of context information
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W8/00—Network data management
    • H04W8/02—Processing of mobility data, e.g. registration information at HLR [Home Location Register] or VLR [Visitor Location Register]; Transfer of mobility data, e.g. between HLR, VLR or external networks
    • H04W8/08—Mobility data transfer

Definitions

  • This application relates to the field of communication technology, and in particular to a communication method and device.
  • the current third generation partnership project (the 3rd generation partner project, 3GPP) protocol supports the interaction between the evolved packet system (EPS) network and the fifth generation mobile communication technology system (5th generation system, 5GS) network. operating. Since the EPS network performs quality of service (QoS) control through the EPS bearer, the 5GS network performs QoS control through the QoS flow, and the interoperability between the EPS network and the 5GS network requires the mapping between the EPS bearer and the QoS flow.
  • QoS quality of service
  • the number of EPS bearers that an EPS network can create for a user is not equal to the number of QoS flows that a 5GS network can create for a user.
  • the number of QoS flows created by the 5GS network for a user is greater than the maximum number of EPS bearers that the EPS network can create for the user, only part of the QoS flows can be selected to switch to the EPS network.
  • Whether a QoS flow can be switched to the EPS network can be realized by whether to allocate an EPS bearer identity (EBI) for the QoS flow.
  • EBI EPS bearer identity
  • the existing technical solution is to determine whether the QoS flow can be switched to the EPS network according to the allocation and retention priority (ARP) of a QoS flow.
  • ARP allocation and retention priority
  • the ARP information of the default QoS flow must be set to a non-preemptible type with the highest priority, otherwise the EBI may not be assigned to the default QoS flow, or the EBI of the default QoS flow may be revoked, and the entire PDU session cannot be switched.
  • strict constraints on ARP are difficult to guarantee in actual service deployment.
  • the embodiments of the present application provide a communication method and device, which are used to allocate the corresponding bearer in the second connection of the second network to the default QoS flow in the first connection of the first network without relying on ARP planning. Identification, so as to ensure business continuity when switching between the first network and the second network.
  • an embodiment of the present application provides a communication method, which can be applied to a mobility management network element in a first network, and the method includes: the mobility management network element of the first network receives the first network element from the session management network element.
  • a request message, the first request message includes the first allocation and retention priority ARP information; after receiving the first request message, the mobility management network element allocates a first identifier for the default quality of service QoS flow of the first connection in the first network , The first identifier is used to identify the bearer corresponding to the default QoS flow in the second connection in the second network; the mobility management network element sends a first response message to the session management network element, and the first response message includes the first Logo.
  • the foregoing default quality of service QoS flow may be an implementation manner of the default first data channel of the first connection in the first network, and the present invention is also applicable to other forms of first data channels.
  • the above-mentioned bearer may be an implementation manner of the second data channel corresponding to the above-mentioned first data channel in the second connection in the second network, and the present invention is also applicable to other forms of second data channels.
  • the first request message indicates that the first ARP information is ARP information corresponding to the default quality of service QoS flow of the first connection in the first network.
  • the first request message sent by the session management network element to the mobility management network element of the first network can indicate that the first ARP information it carries is the ARP information corresponding to the default QoS flow in the first connection of the first network.
  • the mobility management network element can identify the default QoS flow of the first connection of the first network, so as to allocate a corresponding identifier to the default QoS flow to ensure service continuity.
  • this method does not need to restrict the ARP planning, and has better flexibility and applicability.
  • the first request message only includes the first ARP information, and accordingly, the first response message only includes the first identifier.
  • the first request message may also include ARP information corresponding to at least one other QoS flow of the first connection, and the first ARP information is included in the first request message.
  • the position in is located before the position in the first request message of the ARP information corresponding to at least one other QoS flow.
  • the first response message may include a first identifier and an identifier assigned by the mobility management network element to the at least one other QoS flow
  • the first response message may include a first identifier and an identifier assigned by the mobility management network element to the at least one other QoS flow.
  • the position of an identifier in the first response message is located before the position of the identifier allocated by the mobility management network element for the at least one other QoS flow in the first response message.
  • the first request message further includes first indication information, and the first indication information is used to indicate that the first ARP information corresponds to the default QoS flow of the first connection.
  • ARP information is used to indicate that the first ARP information corresponds to the default QoS flow of the first connection.
  • the first response message includes a first identifier and second indication information, and the second indication information is used to indicate that the first identifier is a mobility management network element.
  • the identifier of the default QoS flow allocation for the first connection is a mobility management network element.
  • the first ARP information is ARP information corresponding to the default QoS flow of the first connection.
  • the first response message further includes second indication information, and the second indication information is used to indicate that the first identifier is that the mobility management network element is the first connection
  • the identification of the default QoS flow allocation, or the first response message may also include the identification allocated by the mobility management network element to the at least one other QoS flow, and the first identification is in the first response message The position of is located before the position of the identifier allocated by the mobility management network element for the at least one other QoS flow in the first response message.
  • the first request message is the first request message after the first connection is created, and the first connection is the connection of the terminal device.
  • the method further includes: the mobility management network element determines, among the identifiers assigned to each QoS flow of the first connection, the identifier assigned to the default QoS flow This is the last logo to be revoked.
  • an embodiment of the present application provides a communication method, which can be applied to a session management network element, and the method includes: the session management network element sends a first request message to a mobility management network element of a first network, and the first request message is sent by the session management network element to the mobility management network element of the first network.
  • a request message includes the first allocation and retention priority ARP information; the session management network element receives a first response message from the mobility management network element, and the first response message includes that the mobility management network element is the first connection in the first network.
  • the first identifier assigned to the default quality of service QoS flow where the first identifier is used to identify the bearer corresponding to the default QoS flow in the second connection in the second network.
  • the first request message indicates that the first ARP information is ARP information corresponding to the default quality of service QoS flow of the first connection in the first network.
  • the session management network element indicates through the first request message sent to the mobility management network element of the first network that the first ARP information it carries is the ARP information corresponding to the default QoS flow in the first connection of the first network.
  • the mobility management network element can identify the default QoS flow of the first connection of the first network, so as to allocate a corresponding identifier to the default QoS flow to ensure service continuity.
  • this method does not need to restrict the ARP planning, and has better flexibility and applicability.
  • the first request message only includes the first ARP information; correspondingly, the first response message only includes the first identifier.
  • the first request message further includes ARP information corresponding to at least one other QoS flow of the first connection, and the first ARP information is in the first request message The position of is located before the position of the ARP information corresponding to at least one other QoS flow in the first request message.
  • the first response message includes a first identifier and an identifier assigned by the mobility management network element to at least one other QoS flow, and the first identifier is in the first response The position in the message is located before the position in the first response message that the identifier allocated by the mobility management network element for at least one other QoS flow is.
  • the first request message further includes first indication information, and the first indication information is used to indicate that the first ARP information corresponds to the default QoS flow of the first connection.
  • ARP information is used to indicate that the first ARP information corresponds to the default QoS flow of the first connection.
  • the first response message includes a first identifier and second indication information, and the second indication information is used to indicate that the first identifier is a mobility management network element.
  • the first ARP information is ARP information corresponding to the default QoS flow of the first connection.
  • the first response message further includes second indication information, and the second indication information is used to indicate that the first identifier is that the mobility management network element is the first connection
  • the first response message also includes the identifier assigned by the mobility management network element to the at least one other QoS flow, and the first identifier is in the first response message The location is located before the location of the identifier allocated by the mobility management network element for the at least one other QoS flow in the first response message.
  • the first request message is the first request message after the first connection is created, and the first connection is the connection of the terminal device.
  • embodiments of the present application provide a communication method, which can be applied to a mobility management network element in a first network, and the method includes: a mobility management network element of the first network receives a request from a session management network element Message, the request message is used to request to assign an identifier to the first quality of service QoS flow of the first connection of the terminal device in the first network, and the identifier is used to identify the second connection in the second network corresponding to the first QoS flow
  • the mobility management network element determines that it needs to revoke the assigned identity for the terminal device; the mobility management network element revokes the second identity of the second QoS flow from the allocated identities according to the policy, which is the first QoS flow Allocate a second identifier, wherein the strategy is: among the identifiers assigned to each QoS flow connected in a first network of the terminal device, the identifier assigned to the default QoS flow is the last revoked identifier; mobility management The network element sends a request from
  • the mobility management network element of the first network can choose to be selected according to the policy of preferentially revoking the identifier assigned to the non-default QoS flow in the connection of the first network. Revocation of the identified QoS flow, in this way, can avoid the problem that the connection of the first network where the default QoS flow is located cannot be switched to the second network because the identification assigned to the default QoS flow is revoked, which can effectively guarantee the service of the terminal device Continuity.
  • the second QoS flow is a non-default QoS flow of the first connection.
  • the second QoS flow is a preemptible non-default QoS flow with the lowest priority in the first connection.
  • the second QoS flow is a QoS flow of a terminal device other than the first connection.
  • the second QoS flow is the QoS flow with the lowest priority that can be preempted among the connections in the first network of the terminal device.
  • the second QoS flow is the terminal device The default QoS flow for connections other than the first connection.
  • the method further includes: the mobility management network element determines that the first QoS flow has a preemption capability.
  • the method further includes: the mobility management network element sending a response message, where the response message includes the second identifier.
  • the request message further includes ARP information corresponding to at least one other QoS flow of the first connection, and the response message further includes Assigned ID;
  • the response message further includes second indication information.
  • the indication information is used to indicate that the second identifier is the identifier assigned by the mobility management network element to the default QoS flow of the first connection, or the position of the second identifier in the response message is located in the other QoS flow assignment The identifier of is before the position in the response message.
  • the method further includes: the mobility management network element receives an update message from the session management network element, the update message is used to update the correspondence between the ARP and the identifier .
  • the method further includes: the mobility management network element receives a message from the source mobility management network element or the session management network element, and the message includes that the terminal device has been allocated logo.
  • the assigned identifier includes the identifier of the QoS flow distribution in the connection of one or more first networks of the terminal device.
  • the assigned identifier includes an identifier assigned to a default QoS flow, and may also include an identifier assigned to a non-default QoS flow.
  • the position of the identifier assigned by the default QoS flow in the message is located at the position of the identifier assigned to the non-default QoS flow in the connection of the first network. Before the position in the message.
  • the message includes indication information, and the indication information is used to indicate an identifier corresponding to a default QoS flow.
  • the indication information is an identifier corresponding to the default QoS flow.
  • this application provides a communication device, which may be a mobility management network element or a chip in the mobility management network element.
  • the device may include a processing unit and a transceiving unit.
  • the processing unit may be a processor, and the transceiving unit may be a communication interface;
  • the mobility management network element may also include a storage unit, and the storage unit may be a memory;
  • the processing unit executes the instructions stored in the storage unit, so that the mobility management network element executes the method described in the first aspect or the third aspect.
  • the processing unit may be a processor, and the transceiving unit may be an input/output interface, a pin or a circuit, etc.; the processing unit executes the instructions stored in the storage unit to To cause the mobility management network element to execute the method described in the first aspect or the third aspect, the storage unit may be a storage unit (for example, a register, a cache, etc.) in the chip, or may be in the mobility management network element The storage unit (for example, read-only memory, random access memory, etc.) located outside the chip.
  • an embodiment of the present application provides a communication device.
  • the communication device may be a session management network element or a chip in the session management network element.
  • the communication device may include a processing unit and a transceiving unit.
  • the processing unit may be a processor, and the transceiving unit may be a communication interface;
  • the session management network element may also include a storage unit, and the storage unit may be a memory; the storage unit is used for storing Instruction, the processing unit executes the instruction stored in the storage unit, so that the session management network element executes the method described in the second aspect.
  • the processing unit may be a processor, and the transceiving unit may be an input/output interface, a pin or a circuit, etc.; the processing unit executes the instructions stored in the storage unit to make
  • the session management network element executes the method described in the second aspect
  • the storage unit may be a storage unit (for example, a register, a cache, etc.) in the chip, or a storage located outside the chip in the session management network element. Unit (for example, read only memory, random access memory, etc.).
  • an embodiment of the present application provides a chip system, including: a processor, the processor is coupled with a memory, the memory is used to store a program or an instruction, when the program or an instruction is executed by the processor , Enabling the chip system to implement the method in any possible design of the first aspect or the first aspect, or implement the method in any possible design of the second aspect or the second aspect, and implement the third Aspect or any one of the possible design methods of the third aspect.
  • the chip system further includes an interface circuit for receiving and transmitting code instructions to the processor.
  • processors in the chip system, and the processors may be implemented by hardware or software.
  • the processor may be a logic circuit, an integrated circuit, or the like.
  • the processor may be a general-purpose processor, which is implemented by reading software codes stored in the memory.
  • the memory may be integrated with the processor, or may be provided separately from the processor, which is not limited in this application.
  • the memory may be a non-transitory processor, such as a read-only memory ROM, which may be integrated with the processor on the same chip, or may be set on different chips.
  • the setting method of the processor is not specifically limited.
  • an embodiment of the present application provides a computer-readable storage medium in which a computer program is stored.
  • the processor executes the first aspect or the first aspect. Any possible design method, or implementation of the second aspect or any possible design method of the second aspect, or implementation of the third aspect or any possible design method of the third aspect.
  • an embodiment of the present application provides a computer program product, the computer program product comprising: computer program code, when the computer program code is executed by a processor, the processor executes the first aspect or any one of the first aspect One possible design method, or implementation of the second aspect or any one of the possible designs of the second aspect, or implementation of the third aspect or any one of the possible designs of the third aspect.
  • an embodiment of the present application provides a communication system.
  • the communication system includes a session management network element and a mobility management network element in a first network.
  • the communication system further includes terminal equipment.
  • FIG. 1 is a schematic diagram of a network architecture to which an embodiment of this application is applicable;
  • FIG. 2 is a schematic flowchart of a communication method provided by an embodiment of this application.
  • FIG. 3 is a schematic flowchart of another communication method provided by an embodiment of this application.
  • FIG. 4 is a schematic diagram of a process of allocating EBI to a first QoS flow in an example provided by an embodiment of the application;
  • FIG. 5 is a schematic diagram of the 5GS EBI allocation process provided in specific embodiment 1 of this application.
  • FIG. 6 is a schematic diagram of the 5GS EBI allocation process provided in specific embodiment 2 of this application.
  • FIG. 7 is a schematic diagram of the 5GS EBI allocation process provided in the third embodiment of the application.
  • FIG. 8 is a schematic diagram of the EPS to 5GS Registration or Handover process provided in specific embodiment 4 of this application;
  • FIG. 9 is a schematic diagram of the EPS to 5GS Registration or Handover process provided in specific embodiment 5 of this application.
  • FIG. 10 is a schematic structural diagram of a communication device provided by an embodiment of this application.
  • FIG. 11 is a schematic diagram of another structure of a communication device provided by an embodiment of this application.
  • GSM global system for mobile communications
  • CDMA code division multiple access
  • WCDMA broadband code division multiple access
  • GPRS general packet radio service
  • LTE long term evolution
  • LTE frequency division duplex FDD
  • TDD LTE Time division duplex
  • UMTS universal mobile telecommunication system
  • WIMAX worldwide interoperability for microwave access
  • 5G fifth generation
  • NR new radio
  • the technical solutions provided by the embodiments of the present application are applicable to scenarios that support the interoperability of the first network and the second network, where the first network and the second network are systems supporting different communication standards.
  • the first network can also It is called the first-standard system
  • the second network can also be called the second-standard system.
  • the first network can be a 5G communication system
  • the second network can be a 4G communication system.
  • the 5G communication system can also be called a 5GS network or a 5G system for short
  • the 4G communication system can also be called an EPS network or a 4G system for short.
  • the first network and the second network in the embodiments of this application may also be other types of communication systems, which are not limited in this application.
  • FIG. 1 is a schematic diagram of a possible network architecture applicable to the embodiments of this application.
  • the 5GS network and the EPS network coexist.
  • the following describes the main network elements involved in the network architecture.
  • the EPS network can include the following network elements:
  • Radio access network, (R)AN) network element used to provide network access functions for authorized terminal equipment in a specific area, and can use different quality according to the level of terminal equipment, business requirements, etc. Transmission tunnel.
  • (R)AN network elements can manage wireless resources, provide access services for terminal devices, and then complete the forwarding of control signals and terminal device data between terminal devices and the core network.
  • (R)AN network elements can also be understood as traditional networks In the base station.
  • (R)AN network elements can also be called evolved universal terrestrial radio access network (evovled universal terrestrial radio access network, E-UTRAN) or evolved base station (eNB), as shown in Figure 1. Show.
  • E-UTRAN evolved universal terrestrial radio access network
  • eNB evolved base station
  • network element may also be referred to as an entity, equipment, device, or module, etc., which is not particularly limited in this application.
  • the description of “network element” is omitted in part of the description.
  • the (R)AN network element is referred to as RAN for short.
  • the "(R)AN network element” is abbreviated as RAN.
  • “Element” should be understood as (R)AN network element network element or (R)AN entity. In the following, description of the same or similar situations is omitted.
  • a mobility management entity (mobility management entity, MME) is used to provide mobility management functions.
  • MME can also provide functions such as lawful interception and access authorization/authentication.
  • a serving gateway (SGW) is used to provide functions such as user data forwarding.
  • PGW-U packet data network gateway user function
  • PGW-C packet data network gateway control function
  • PCRF policy and charging rules function
  • the home subscriber server including the user profile, is used to perform user authentication and authorization, and can provide information about the user's physical location.
  • the 5GS network can include the following network elements:
  • (R)AN network element It is used to provide network access function for authorized terminal equipment in a specific area, and can use transmission tunnels of different quality according to the level of terminal equipment and service requirements.
  • the (R)AN network element may also be called the next generation radio access network (NG-RAN, as shown in Figure 1) or the next generation base station (gNB).
  • NG-RAN next generation radio access network
  • gNB next generation base station
  • Access and mobility management function used for access management and mobility management functions.
  • AMF can also provide functions such as lawful interception and access authorization/authentication.
  • the AMF can communicate with the MME through the N26 interface.
  • the letters and numbers in the attachments between the various network elements represent the names of the communication interfaces between the various network elements.
  • the communication interfaces between the various network elements may also have other names. not limited.
  • UPF User plane function
  • QoS quality of service
  • Session management function (session management function, SMF), mainly used for session management, terminal equipment network interconnection protocol (IP) address allocation and management, selection and management of user plane functions.
  • SMF can also be the termination point of policy control and charging function interfaces.
  • PCF Policy control function
  • AMF Access Management Function
  • SMF Session Management Function
  • Unified data management (UDM) network elements are used to manage contracted data. In addition, it is also used for user service registration management, processing terminal device identification, access authentication, etc.
  • network elements with the same or similar functions can be set jointly.
  • UPF and PGW-U can be set up together
  • SMF and PGW-C can be set up together
  • PCF and PCRF can be set up together
  • HSS and UDM can be set up together
  • "+" in Figure 1 means that two devices can be set up together.
  • the foregoing network elements or functions may be network elements in hardware devices, software functions running on dedicated hardware, or virtualization functions instantiated on a platform (for example, a cloud platform).
  • the terminal device can be switched from a 4G communication system to a 5G communication system, or it can be switched from a 5G communication system to a 4G communication system.
  • the terminal device is a device with wireless communication function, which can be deployed on land, including indoor or outdoor, handheld or vehicle-mounted; it can also be deployed on the water (such as ships, etc.); it can also be deployed in the air (such as airplanes). , Balloons and satellites etc.).
  • the terminal can be a mobile phone (mobile phone), a tablet computer (pad), a computer with wireless transceiver function, a virtual reality (VR) terminal, an augmented reality (AR) terminal, and an industrial control (industrial control).
  • VR virtual reality
  • AR augmented reality
  • industrial control industrial control
  • the wireless terminal in the self-driving self-driving
  • the wireless terminal in the remote medical remote medical
  • the wireless terminal in the smart grid smart grid
  • the wireless terminal in the transportation safety transportation safety
  • the smart The wireless terminal in the city smartt city
  • the wireless terminal in the smart home smart home
  • it can also be various forms of user equipment (UE), mobile station (MS), terminal equipment ( terminal device).
  • UE user equipment
  • MS mobile station
  • terminal equipment terminal device
  • the mobility management network element is the access and mobility management function AMF network element
  • the session management network element is the session management function SMF network element, as an example for description.
  • AMF AMF
  • SMF SMF
  • AMF AMF
  • SMF SMF
  • FIG. 2 is a schematic flowchart of a communication method provided in an embodiment of this application. The method specifically includes the following steps:
  • Step S201 The session management network element sends a first request message to the mobility management network element of the first network, where the first request message includes first ARP information, and the first request message indicates that the first ARP information is in the first network.
  • ARP information corresponding to the default QoS flow of the first connection.
  • the first request message is used to request the mobility management network element of the first network to assign an identifier to the default QoS flow of the first connection in the first network, and the identifier is used to identify the second connection of the default QoS flow in the second network.
  • the corresponding bearer in the second network may be, for example, the identifier of the bearer corresponding to the default QoS flow in the second connection in the second network.
  • the first connection in the first network may refer to a PDU session in the 5GS network
  • the second connection in the second network may refer to the EPS network
  • this application will refer to it as the first PDU session and the first PDN connection in the following.
  • a PDU session includes at least one default QoS flow.
  • the PDU session may also include one or more other QoS flows.
  • the one or more other QoS flows The flow is a non-default QoS flow, or can also be called a dedicated QoS flow (dedicate QoS flow). In other words, if only one QoS flow is included in a PDU session, then the QoS flow must be the default QoS flow. If a PDU session includes multiple QoS flows, then there must be one default QoS flow among these multiple QoS flows. The other QoS flows are non-default QoS flows.
  • a PDN connection includes at least one default EPS bearer.
  • the PDN connection may also include one or more other EPS bearers, and the one or more other EPS bearers are non-default EPS bearers, or It can also be called a dedicated EPS bearer.
  • the first request message can be understood as that the session management network element (such as SMF) requests the mobility management network element (such as AMF) in the 5GS network to allocate an EBI for the default QoS flow of the first PDU session, and the EBI refers to the The identifier of the EPS bearer corresponding to the default QoS flow in the first PDN connection in the EPS network.
  • the first request message may also be referred to as the first EBI allocation request message, or may also have other names, which is not limited in this application. It can be understood that if a QoS flow is assigned an EBI, it means that the QoS flow can be successfully switched from the 5GS network to the EPS network.
  • the first connection in the first network and the second connection in the second network are connections for the same terminal device. That is, the first PDU session is the PDU session of the terminal device, and the first PDN connection is also the PDN connection of the terminal device.
  • the session management network element may send the first request message to the mobility management network element of the first network during the creation process of the first connection in the first network.
  • the first request message may also be the first request message after the first connection is created. That is to say, when the first PDU session in the 5GS network is created, SMF first applies for EBI for the default QoS flow in the first PDU session, so that when the terminal device switches from the 5GS network to the EPS network, the PDU session The default QoS flow in can be successfully switched to the EPS network to ensure the business continuity of the terminal equipment.
  • the ARP information indicating that the first ARP information is the default QoS of the first connection in the first network may have multiple possible implementation manners.
  • the first request message may only include the first ARP information. That is, the first request message may only carry the ARP information of the default QoS flow of the first connection, so that the mobility management network element can easily identify the default QoS flow of the first connection. It should be noted that the first request message may only include the first ARP information, which means that the first request message does not include the ARP information of other QoS flows of the first connection. Of course, according to different scenarios, the first request message may also Include other information.
  • the mobility management network element may receive the first ARP information carried in the first first request message from the session management network element after the first connection of the first network is created, and confirm it as the default QoS flow of the first connection Corresponding ARP information.
  • the first request message may include the first ARP information and ARP information corresponding to at least one other QoS flow of the first connection.
  • the position of the first ARP information in the first request message is located in the first connection.
  • the ARP information corresponding to at least one other QoS flow of the first connection is located in the first connection.
  • the first ARP information and the ARP information corresponding to at least one other QoS flow of the first connection may be included in different fields in the first request message, and the field containing the first ARP information is located at least in the at least one containing the first connection.
  • the first ARP information may be located in one field in the first request message, and the ARP information corresponding to at least one other QoS flow of the first connection may be located in another or more fields in the first request message; or
  • the ARP information corresponding to each QoS flow may have an independent field in the first request message, which is not limited in this application.
  • the first ARP information and the ARP information corresponding to at least one other QoS flow of the first connection may be included in the same field in the first request message, and the position of the first ARP information in the field is located in the first request message.
  • the ARP information corresponding to at least one other connected QoS flow is before the position in this field.
  • the first request message may include a list of ARP information, the first ARP information is located in the first position of the list of ARP information, and the ARP information corresponding to at least one other QoS flow of the first connection is located in the ARP. After the first ARP message in the list of messages.
  • the first request message may include first ARP information and first indication information, and the first indication information is used to indicate that the first ARP information is the ARP corresponding to the default QoS flow of the first connection. information.
  • the first request message may also include ARP information corresponding to at least one other QoS flow of the first connection, and the position of the first ARP information in the first request message is located in at least one other QoS flow of the first connection Before the corresponding ARP information.
  • ARP information corresponding to at least one other QoS flow of the first connection
  • the position of the first ARP information in the first request message is located in at least one other QoS flow of the first connection Before the corresponding ARP information.
  • the first indication information may be expressed as information carried in a certain field in the first request message. For example, if the first ARP information corresponds to the ARP information corresponding to at least one other QoS flow of the first connection, it is located in the first connection. In different fields in a request message, the first indication information may be used to indicate the field where the first ARP information is located, and the first indication information may be located in the field where the first ARP information is located, or may be located in a separate field, This application is not limited.
  • the first indication information may be used to indicate that the first ARP information contained in this field is the first ARP. information.
  • the first request message includes an ARP list, and the ARP list includes all ARPs corresponding to the QoS flows that need to be allocated EBI.
  • the first request message also includes the ARPs corresponding to the default QoS flows. The ARP corresponding to the default QoS flow is used as the first indication information.
  • the first indication information is used to indicate that the first ARP information in the list of ARP information is the first ARP information.
  • the first indication information may also exist in an implicit form. For example, the existence of a specific field for indicating the first ARP information contained in the first request message may be regarded as the first indication information.
  • the third possible implementation can be applied to the scenario where the PCF issues multiple rules during the PDU session creation process and needs to be mapped into a QoS rule, or the terminal device does not originally support the first Interoperability between the network and the second network, but the subsequent contract is modified to support the interoperability between the first network and the second network.
  • the first request message may include the first ARP information and the ARP information corresponding to at least one other QoS flow of the first connection.
  • the first ARP information is ARP information corresponding to the default quality of service QoS flow of the first connection in the first network.
  • the first ARP itself may be used as indication information to indicate that the first ARP information is ARP information corresponding to the default quality of service QoS flow of the first connection in the first network.
  • the priority of the first ARP is set to a specific value, and the specific value indicates that the ARP is the ARP corresponding to the default quality of service QoS flow.
  • the priority value of the ARP corresponding to the default QoS flow is predefined, and the ARP corresponding to other QoS flows cannot be set to the predefined value.
  • you can set whether the ARP supports Pre-emption vulnerability is used to distinguish the ARP corresponding to the default QoS flow from the ARP of other QoS flows.
  • the ARP of the default QoS flow is set to not be preempted, and the ARP of other QoS flows is set to be preempted .
  • other methods can also be used to distinguish the ARP of the default QoS flow from the ARP of other QoS flows, which is not limited in this embodiment.
  • This implementation may not require additional indication information, and may also not require the first ARP to be placed before other ARPs.
  • the mobility management network element can determine whether the ARP is the ARP corresponding to the default QoS flow according to the ARP.
  • the ARP information corresponding to the QoS flow mentioned in the embodiment of the present application does not limit one ARP information to one QoS flow in a one-to-one correspondence, and one ARP information may correspond to one or more QoS flows. That is, the ARP information corresponding to different QoS flows may be the same.
  • the first request message includes the ARP information corresponding to multiple QoS flows
  • the ARP information corresponding to some of the multiple QoS flows is the same, Then the same ARP information can appear multiple times in the first request message, that is, one ARP information corresponds to one QoS flow; the same ARP information can also appear only once in the first request message, that is, there are one or more The QoS flow corresponds to the same ARP information.
  • the foregoing first and second possible implementation manners can be understood as indicating in an implicit form that the first APR information in the first request message is the ARP information corresponding to the default QoS flow.
  • the foregoing third possible implementation manner can be It is understood that the first APR information in the first request message is indicated in an explicit form as the ARP information corresponding to the default QoS flow.
  • Step S202 The mobility management network element receives a first request message from the session management network element.
  • Step S203 After receiving the first request message, the mobility management network element allocates a first identifier to the default QoS flow of the first connection in the first network, and the first identifier is used to identify the second connection in the second network.
  • the mobility management network element may assign a first identifier to the default QoS flow of the first connection in the first network according to a policy.
  • the strategy includes: if the terminal device currently has an available bearer identifier of the second connection in the second network, the mobility management network element can use the available bearer identifier of the second connection as the default for the first connection.
  • the QoS flow is assigned an identifier. If the terminal device does not currently have the identifier of the bearer of the second connection in the second network available, the identifier of the second bearer of the second connection that has been allocated for the terminal device needs to be revoked, and the mobility management network element may revoke it.
  • the identifier of the second bearer of the second connection is again allocated to the default QoS flow of the first connection.
  • the identification allocated to the default QoS flow is the last revoked identification.
  • the mobility management network element may preferentially allocate an EBI to the default QoS flow. That is, when the mobility management network element confirms that the EBI cannot be allocated for all requested QoS flows, the mobility management network element first allocates the available EBI to the default QoS flow.
  • the mobility management network element may use the same as the default QoS flow allocation.
  • the identification of the corresponding bearer in the second connection is allocated to some or all of the QoS flows in at least one other QoS flow of the first connection. That is to say, because the identifiers of the bearers in the second connection that can be allocated to a QoS flow of a terminal device are limited, there may be cases where some non-default QoS flows cannot be assigned an identifier.
  • the first request message may include the ARP information corresponding to the default QoS flow in the first PDU session, and the mobility management network element in the 5GS network (such as AMF) )
  • the mobility management network element in the 5GS network such as AMF
  • a first EBI can be assigned to the default QoS flow in the first PDU session.
  • the first EBI is the first PDN connection in the EPS network corresponding to the default QoS flow in the first PDU session
  • the identity of the EPS bearer is the identity of the EPS bearer.
  • the AMF can use the same manner as the one or more non-default QoS flows of the first PDU session. Part or all of the QoS flows are allocated EBI.
  • Step S204 The mobility management network element sends a first response message to the session management network element, where the first response message includes a first identifier.
  • the first response message may only include the first allocated for the default QoS flow. logo. Similarly, the first response message may only include the first identifier assigned to the default QoS flow, which means that the first response message does not include the identifier assigned to other QoS flows. Of course, according to different scenarios, the first response message may also Include other information.
  • the first response message may only include the first EBI allocated for the default QoS flow of the first PDU session.
  • the first response message may include the first identifier and the mobility management network element is The identifier assigned to at least one other QoS flow of the first connection, and the position of the first identifier in the first response message is located in the mobility management network element The identifier assigned to at least one other QoS flow of the first connection is in the first response Before the position in the message.
  • the first response message may include the first EBI assigned by the AMF for the default QoS flow of the first PDU session, and the AMF as the minimum value of the first PDU session.
  • An EBI allocated by another QoS flow, and the position of the first EBI in the first response message is before the position of the EBI allocated by the AMF for at least one other QoS flow of the first PDU session in the first response message.
  • the specific implementation of the location of the first identifier in the first response message is similar to the specific implementation of the location of the first ARP information in the first request message, that is, the field containing the first identifier may be located in the network element containing the mobility management Before the field of the identifier assigned to at least one other QoS flow of the first connection, it may also be in a field, and the position of the first identifier in this field is located in the mobility management network element for at least one other of the first connection. Before the position of the identifier assigned by the QoS flow in this field, it can also be a list of the identifiers of the bearers of the second connection in the first response message, and the first identifier is at the first position in the list of identifiers. For details, please See the description above.
  • the first response message may include the first identifier and the second indication information.
  • the second indication information is used to indicate that the first identifier is an identifier allocated by the mobility management network element to the default QoS flow of the first connection.
  • the first response message may also include an identifier assigned by the mobility management network element to at least one other QoS flow of the first connection, and the position of the first identifier in the first response message is located in the mobility management network element
  • the identifier assigned to at least one other QoS flow of the first connection is before the position in the first response message.
  • the specific implementation manner of the position of the first identifier in the first response message is similar to the specific implementation manner of the position of the first ARP information in the first request message. For details, please refer to the above description.
  • the first response message may include the first EBI and second indication information allocated by the AMF for the default QoS flow of the first PDU session.
  • the second indication information Used to indicate that the first EBI is the EBI allocated by the AMF for the default QoS flow of the first PDU session.
  • the first response message may include the EBI allocated by the AMF for at least one other QoS flow of the first PDU session, and the position of the first EBI in the first response message is at least when the AMF is the first PDU session.
  • An EBI assigned by another QoS flow precedes the position in the first response message.
  • the specific implementation manner of the second indication information is similar to the specific implementation manner of the first indication information, that is, the second indication information can be expressed as information carried in a certain field in the first response message, or one of the first response messages.
  • Information element information element, IE
  • the second indication information can be used to indicate where the first identification information is located.
  • the second indication information can be located in the field where the first identifier is located, or in a separate field, which is not limited in this application; for another example, if the first identifier and the mobility management network element are connected to the first
  • the identification of at least one other QoS flow allocation is located in the same field in the first response message, and the first indication information may be used to indicate that the first identification contained in the field is the first identification of the default QoS flow allocated to the first connection.
  • the first response message includes a list of correspondences between the ARPs corresponding to all QoS flows that have been allocated EBI and the EBI allocated for the QoS flow.
  • the first response message also includes the allocation for the default QoS flow.
  • the EBI is used as the second indication information.
  • the second indication information is used to indicate that the first identifier in the list of identifiers is the first identifier of the default QoS flow allocated to the first connection.
  • the first indication information may also exist in an implicit form. For example, the presence of a specific field used to indicate the first identifier of the default QoS flow assigned to the first connection contained in the first response message may be determined by the existence of the first identifier. It is the second instruction information.
  • the sequence of the identifiers assigned by the multiple QoS flows in the first response message may be the same as that of the multiple QoS flows.
  • the sequence of the corresponding ARP information in the first request message is the same or different, which is not limited by this application.
  • the mobility management network element may continue to allocate the identifiers of the corresponding bearers in the second connection in the second network to other QoS flows in the first connection, or the identifier of the corresponding bearer in the second connection in the first network.
  • the QoS flows in other connections are allocated with the identifiers of the corresponding bearers in the second connection in the second network, and the other connections in the first network and the aforementioned first connection are all connections of the same terminal device.
  • the mobility management network element may receive from the same session management network element a second request message requesting to assign identifiers to other QoS flows in the first connection or QoS flows in other connections of the first network, and also A second request message for assigning identifiers to other QoS flows in the first connection or QoS flows in other connections of the first network may be received from another session management network element, which is not limited in this application.
  • the AMF may also allocate EBI to other QoS flows of the first PDU session or the QoS flow of the second PDU session of the terminal device. If the AMF receives the first request message from the first SMF requesting the allocation of EBI for the default QoS flow of the first PDU session, it is assumed that the request will be the other QoS flow of the first PDU session or the QoS flow of the second PDU session of the terminal device
  • the request message for allocating EBI is recorded as the second request message, and then the AMF can receive the second request message from the first SMF, and can also receive the second request message from the second SMF.
  • the session management network element receives the first response message, if the ARP corresponding to the first identifier indicated in the first response message is not the ARP corresponding to the default QoS flow (for example, the mobility management network element When determining the ARP corresponding to the default QoS flow in the four ways, the wrong ARP is determined as the ARP corresponding to the default QoS flow, and the session management network element can perform the following processing:
  • the session management network element determines the first identifier as the EBI corresponding to the default QoS flow.
  • the first request message includes ARP1 and ARP2
  • the first ARP determined by SMF is ARP1
  • the first ARP determined by AMF is ARP2
  • AMF assigns EBI1 to ARP1
  • ARP2 assigns EBI2
  • AMF sends in the first response message ⁇ ARP2, EBI2>, ⁇ ARP1, EBI1>, and indicate that EBI2 is the EBI corresponding to the default QoS flow
  • SMF will use EBI2 as the EBI corresponding to the default QoS flow, that is, the information actually saved by SMF is ⁇ ARP1, EBI2>, ⁇ ARP2,EBI1>.
  • the session management network element sends an update message to the AMF to update the correspondence between ARP and EBI. That is, after re-determining the corresponding relationship, the SMF sends the new corresponding relationship to the AMF.
  • the update message sent by SMF to AMF includes: ⁇ ARP1, EBI2>, ⁇ ARP2, EBI1>, so that the same correspondence relationship is stored in AMF and SMF. This update operation does not change which EBI determined by AMF is the EBI corresponding to the default QoS flow.
  • FIG. 3 is a schematic flowchart of another communication method provided by an embodiment of this application. The method specifically includes the following steps:
  • Step S301 The mobility management network element of the first network receives a request message from the session management network element.
  • the request message is used to request to assign an identifier to the first QoS flow of the first connection of the terminal device in the first network.
  • the request message may include ARP information corresponding to the first QoS flow.
  • the first QoS flow may be the default QoS flow of the first connection, or may be a non-default QoS flow of the first connection, which is not limited in this embodiment of the application.
  • the request message may also indicate that the first ARP information is the ARP information corresponding to the default quality of service QoS flow of the first connection in the first network, where The first ARP information refers to the ARP information corresponding to the first QoS flow.
  • the first ARP itself may be used as indication information to indicate that the first ARP information is ARP information corresponding to the default quality of service QoS flow of the first connection in the first network. That is to say, the two communication methods provided in the embodiments of the present application can also be combined with each other during application.
  • the request message may also include ARP information corresponding to other QoS flows of the first connection, so as to assign identifiers to other QoS flows.
  • the first connection in the first network can refer to a PDU session in the 5GS network, such as the first PDU session and the second connection in the second network It may refer to a PDN connection in the EPS network, such as the first PDN connection.
  • a PDU session can include one or more QoS flows, the one or more QoS flows include a default QoS flow, and in addition to the default QoS flow, other QoS in the one or more QoS flows The flow is a non-default QoS flow, and can also be referred to as a dedicated QoS flow.
  • a PDN connection may include one or more EPS bearers.
  • the first or more EPS bearers include a default EPS bearer. Except for the default EPS bearer, other EPS bearers in the first or more EPS bearers are non-
  • the default EPS bearer or may also be called a dedicated EPS bearer, and the identifier used to identify the bearer of the second connection in the second network refers to the identifier of the EPS bearer, that is, EBI.
  • the request message is used to request to allocate an EBI for the first QoS flow of the first PDU session of the terminal device in the 5GS network.
  • the EBI is the identifier of the EPS bearer corresponding to the first QoS flow in the EPS network.
  • a QoS flow can be a default QoS flow or a non-default QoS flow in the first PDU session.
  • Step S302 The mobility management network element determines that the identification that has been allocated to the terminal device needs to be revoked.
  • each terminal device may be configured with a maximum number of identities that are allowed to be allocated to the terminal device, and the identities refer to the identities carried in the second connection in the second network.
  • the maximum number of assignable identifiers corresponding to different terminal devices may be the same or different, which is not limited by this application.
  • the mobility management network element determines that it is necessary to revoke the assigned identities for the terminal device may be: the mobility management network element determines that the number of identities assigned to the terminal device reaches the set threshold, and the terminal device currently has no available identities. Then, the set threshold is the maximum number of assignable identifiers corresponding to the terminal device. It should be understood that the determination by the mobility management network element that it is necessary to revoke the assigned identifier for the terminal device may also be in other situations, which is not limited in this application.
  • the terminal device changes from supporting interoperability between the first network and the second network to not supporting interoperability between the first network and the second network, and the session management network element requests the mobility management network element to be revoked as the terminal device
  • the assigned identifier then the mobility management network element can determine that the assigned identifier for the terminal device needs to be revoked.
  • each terminal device can correspond to a maximum number of EBIs that can be allocated. If the number of EBIs currently allocated for the QoS flow of the terminal device is equal to the maximum number of EBIs, it means that the terminal device currently has no available EBI, and the EBI allocated for a certain QoS flow of the terminal device needs to be revoked .
  • Step S303 The mobility management network element removes the second identifier of the second QoS flow from the assigned identifiers according to the policy, and allocates the second identifier to the first QoS flow.
  • the strategy is: among the identifiers assigned to each QoS flow connected in a first network of the terminal device, the identifier assigned to the default QoS flow is the identifier that is finally revoked.
  • the second QoS flow can be a non-default QoS flow of the first connection, that is, the second QoS flow and the first QoS flow can both belong to the first connection, or in other words, the first QoS flow can preempt the non-default QoS flow that belongs to the same first connection.
  • the identifier of the QoS flow This situation requires that the first QoS flow is a non-default QoS flow for the first connection.
  • the second QoS flow may be a preemptible non-default QoS flow with the lowest priority in the first connection.
  • the second QoS flow may also be a non-default QoS flow of connections of the first network other than the first connection of the terminal device, that is, the second QoS flow and the first QoS flow may belong to different first network connections, and the first A QoS flow can preempt the identification of the non-default QoS flow of the connection of the other first network.
  • the first QoS flow may be a non-default QoS flow or a default QoS flow of the first connection, and is not limited.
  • the second QoS flow may be a non-default QoS flow with the lowest priority that can be preempted among other connections of the first network where the second QoS flow is located, or the second QoS flow may also be all of the terminal equipment The non-default QoS flow with the lowest priority among the connections of the first network that can be preempted.
  • the second QoS flow may also be the default QoS flow of the connection of the first network other than the first connection of the terminal device, that is, the second QoS flow and the first QoS flow may belong to different first network connections.
  • a QoS flow can preempt the identification of the default QoS flow of the connection of the other first network.
  • the second QoS flow is required to be assigned an identifier among the connections of other first networks where the second QoS flow is located, and no non-default QoS flow is assigned an identifier. That is to say, the identifier assigned to the second QoS flow is the last identifierevoked among the connections of the other first network where the second QoS flow is located.
  • the second QoS flow may be a preemptible default QoS flow with the lowest priority among all first connections of the terminal device.
  • the mobility management network element may decide to revoke the assigned identifier for which QoS flow based on the ARP information corresponding to the first QoS flow and the ARP information corresponding to each QoS flow to which the terminal device has been assigned an identifier. , That is, determine the identity of the second QoS flow that needs to be revoked.
  • the mobility management network element may first determine which first network connection of the terminal device to revoke the identifier, that is, determine the identity of the first network connection where the second QoS flow is located. Furthermore, the second QoS flow is determined in the determined connection of the first network.
  • the mobility management network element may select, according to the ARP information of the connection of each first network to which the identifier has been assigned, from the connection of each first network to which the identifier has been assigned, the priority of the selected QoS flow is less than or The connection of the first network that is less than or equal to the priority of the QoS flow included in the connection of the other first network. If there is at least one non-default QoS flow that has been assigned an identifier in the connection of the selected first network, the mobility management network element may select one of the non-default QoS flows from the at least one non-default QoS flow that has been assigned an identifier. Flow as the second QoS flow.
  • the AMF may select the non-default QoS flow with the lowest priority that can be preempted as the second QoS flow from the at least one non-default QoS flow that has been assigned an identifier.
  • the mobility management network element may use the default QoS flow as the second QoS flow . Otherwise, if only the default QoS flow is assigned an identifier among the connections of the selected first network, but the connection of the selected first network is the first connection, then the mobility management network element may determine not to assign the first QoS flow Logo.
  • the AMF can prioritize the QoS flow included in each PDU session of the terminal device
  • the second PDU session is determined, and the second PDU session specifically refers to a PDU session in which the priorities of the included QoS flows are all less than or less than or equal to the priorities of the QoS flows included in other PDU sessions.
  • the AMF may select a non-default QoS flow from the at least one non-default QoS flow allocated with an EBI as the second QoS flow.
  • the second QoS flow specifically refers to a non-default QoS flow with the lowest priority that can be preempted among at least one non-default QoS flow allocated with an EBI.
  • the AMF may use the default QoS flow of the second PDU session as the second QoS flow. If only the default QoS flow in the second PDU session is allocated with EBI, but the second PDU session and the first PDU session are actually the same PDU session, then AMF can determine not to allocate EBI to the first QoS flow, that is, AMF refuses to be the first QoS flow. A QoS flow allocates EBI.
  • the mobility management network element may select from the at least one non-default QoS flow that has been assigned an identifier.
  • a non-default QoS flow is selected from the non-default QoS flow as the second QoS flow.
  • the mobility management network element may select the non-default QoS flow with the lowest priority that can be preempted from the at least one non-default QoS flow to which the identifier has been assigned, as the second QoS flow.
  • the mobility management network element can select a default QoS flow from the default QoS flows that have been assigned identifiers as the first Two QoS flow.
  • the mobility management network element may select the default QoS flow with the lowest priority that can be preempted from each default QoS flow that has been assigned an identifier, as the second QoS flow.
  • the AMF can first determine whether there is at least one non-default QoS flow that has been assigned an identifier in each PDU session of the terminal device. Among the at least one non-default QoS flow to which the identifier has been assigned, a non-default QoS flow is selected as the second QoS flow.
  • the second QoS flow is a preemptible non-default QoS flow with the lowest priority among the at least one non-default QoS flow that has been assigned an identifier.
  • the AMF may select a default QoS flow from the default QoS flows that have been assigned identifiers as the second QoS flow.
  • the second QoS flow is a default QoS flow that has the lowest priority and can be preempted among the default QoS flows that have been assigned an identifier.
  • the mobility management network element may also use the ARP corresponding to the first QoS flow before revoking the second identification of the second QoS flow from the allocated identification.
  • the information determines that the first QoS flow has preemption capability, and the priority corresponding to the first QoS flow is greater than the priority corresponding to the second QoS flow. That is, the first first QoS flow can only preempt the identifier of the QoS flow with a lower priority than itself.
  • the mobility management network element If the request message includes the ARP of other QoS flows of the first connection, the mobility management network element also assigns identifiers to other QoS flows, and the method for the mobility management network element to assign identifiers to other QoS flows can be found in Assignment to the first QoS flow. The identification method will not be repeated here.
  • Step S304 The mobility management network element sends a response message to the session management network element, where the response message includes the second identifier.
  • the response message may also be used to indicate that the second identifier is an identifier assigned to the default QoS flow of the first connection.
  • the AMF After the AMF receives a request message from the SMF requesting to allocate EBI for the first QoS flow of the first PDU session of the terminal device, it can first determine that it is the terminal device The number of EBI allocated. If the number of EBIs allocated to the terminal device does not exceed the set threshold, the AMF may select an EBI from the available EBIs and allocate it to the first QoS flow.
  • the AMF may determine that the allocated EBIs need to be cancelled. Furthermore, the AMF may determine whether the first QoS flow has the preemption capability according to the ARP information corresponding to the first QoS flow carried in the request message.
  • the AMF can continue to determine whether there is at least one non-default QoS flow that has been allocated EBI and has a priority lower than the first QoS flow and can be preempted in each PDU session of the terminal device, If it exists, the AMF may revoke the EBI of the QoS flow with the lowest priority among the at least one non-default QoS flow, and then allocate the EBI to the first QoS flow.
  • the AMF may send a response message to the SMF. If the AMF successfully allocates the EBI for the first QoS flow, the response message may include the EBI allocated for the first QoS flow. If the AMF does not allocate the EBI for the first QoS flow, the The response message may include information used to indicate failure to allocate EBI for the first QoS flow.
  • the AMF may not determine whether the ARP corresponding to the first QoS flow indicates that the first QoS flow has the preemption capability, and the AMF always considers the first QoS flow. Has the ability to preempt.
  • the mobility management network element may also receive a message from the source mobility management network element, and the message includes an identifier assigned to the terminal device.
  • the assigned identifier for the terminal device may include: the identifier assigned by the source mobility management network element to the QoS flow in the connection of one or more first networks of the terminal device, which may include a default QoS flow
  • the assigned identifier may also include an identifier assigned to a non-default QoS flow, which is not limited in this application. It should be understood that the identifier assigned to a QoS flow refers to the identifier of the bearer corresponding to the QoS flow in the second network.
  • the position in the message of the identifier assigned to the default QoS flow in the connection of the first network is located in the position in the message assigned to the non-default QoS flow in the connection of the first network Identifies before the position in the message.
  • reception of a message by the mobility management network element from the source mobility management network element may correspond to a scenario in which a context is transferred between the mobility management network elements of two first networks.
  • the mobility management network element may also receive a message from the session management network element, and the message includes an identifier assigned by the terminal device.
  • the assigned identifier for the terminal device may include: a mobility management network element in the second network, and an identifier assigned to a QoS flow in one or more connections of the first network of the terminal device. Among them, it may include the identifier assigned to the default QoS flow, and may also include the identifier assigned to the non-default QoS flow, which is not limited in this application. It should be understood that the identifier assigned to a QoS flow refers to the identifier of the bearer corresponding to the QoS flow in the second network.
  • the position in the message of the identifier assigned to the default QoS flow in the connection of the first network is located in the position in the message assigned to the non-default QoS flow in the connection of the first network Identifies before the position in the message.
  • reception of a message by the mobility management network element from the session management network element may correspond to a scenario in which the terminal device switches from the second network to the first network.
  • the message received by the mobility management network element from the source mobility management network element or the session management network element may further include indication information.
  • the indication information includes at least one EBI, and the indication information may be used to indicate the at least one EBI.
  • the first EBI in the EBI is the EBI corresponding to the default QoS flow of the first connection of the first network.
  • the indication information may be, for example, that a default EBI is added outside the ⁇ ARP, EBI> list to indicate which EBI is the EBI corresponding to the default QoS flow.
  • the AMF may save the at least one EBI received from the message.
  • the source mobility management network element or the session management network element may receive the foregoing message.
  • SMF only carries one ARP when applying for EBI for the first time for a QoS flow in a PDU session.
  • the SMF In order to identify the default QoS flow, the SMF always carries the ARP corresponding to the default QoS flow in the first EBI allocation request message; accordingly, the AMF identifies the first allocated EBI in each PDU session as the EBI corresponding to the default QoS flow by default.
  • the detailed process is as follows:
  • the SMF initiates an EBI allocation request message to the AMF, and the message only carries the ARP corresponding to the default QoS flow.
  • the AMF allocates an EBI for the ARP and identifies this EBI as the EBI corresponding to the default QoS flow, and then sends an EBI allocation response message to the SMF, which carries the allocated EBI.
  • the AMF judges that the ARP is the ARP corresponding to the default QoS flow according to the request message being the first EBI request message of the PDU session, and the EBI allocated for the QoS flow is the EBI corresponding to the default QoS flow.
  • the SMF can continue to apply to the AMF to allocate an EBI for the PDU session, and the AMF can determine that the ARP in the subsequent request message is the ARP corresponding to the non-default QoS flow.
  • the request to allocate EBI may be used to allocate EBI to the non-default QoS flow of the PDU session in step 1, or to allocate EBI to the default QoS flow or non-default QoS flow of other PDU sessions.
  • the process of AMF withdrawing the allocated EBI can refer to the description in the above method embodiment.
  • the AMF sends a response message to the SMF, and the response message carries the allocated EBI.
  • the difference between the second embodiment and the first embodiment is that when the SMF applies for EBI allocation for the first time, multiple ARPs are carried in the request message at the same time. In order to identify the default QoS flow, the following processing is required. Other processing It is consistent with the first embodiment.
  • SMF puts the ARP corresponding to the default QoS flow in the first position among all ARPs.
  • the EBI allocation request of the SMF carries an ARP list, and the ARP of the default QoS flow is at the top of the ARP list.
  • the AMF identifies the EBI corresponding to the first ARP as the EBI corresponding to the default QoS flow.
  • AMF puts the EBI corresponding to the default QoS flow in the first position of all allocated EBIs; for example, AMF includes the ⁇ ARP,EBI> list in the response message, where the first position of the list is One ⁇ ARP, EBI> is the ARP and EBI corresponding to the default QoS flow.
  • the difference between the second embodiment and the first embodiment is that when the SMF applies for EBI allocation for the first time, multiple ARPs are carried in the request message at the same time. In order to identify the default QoS flow, the following processing is required. Other processing It is consistent with the first embodiment.
  • the first EBI allocation request message of the SMF in addition to the ARP of each QoS flow that needs to be allocated EBI, it also carries first indication information to indicate which ARP is the ARP corresponding to the default QoS flow.
  • the request message includes an ARP list, where the ARP list includes the ARP of each QoS flow to which the EBI needs to be allocated, and the first indication information is the ARP of the default QoS flow.
  • AMF identifies the EBI corresponding to the first ARP as the EBI corresponding to the default QoS flow
  • the AMF in addition to carrying each allocated EBI and its corresponding ARP, the AMF also carries indication information for indicating which EBI is the EBI corresponding to the default QoS flow.
  • the response message includes a list of "EBI, ARP", the list includes each allocated EBI and the ARP corresponding to the EBI, and the indication information is the EBI corresponding to the default QoS flow.
  • the EPS to 5GS registration or handover process includes the following steps:
  • the AMF sends the SmContext Create Request message to the SMF.
  • the SMF returns the created SmContext response message to the AMF in the allocatedEbiList information element, the ARP and EBI corresponding to the default QoS flow are placed in the first position; AMF saves the EBI/ARP information and identifies the first EBI as the default QoS Streaming EBI.
  • the subsequent EBI allocation process is the same as the 5GS EBI allocation process.
  • the EPS to 5GS Registration or Handover process can include the following steps:
  • the AMF sends the SmContext Create Request message to the SMF.
  • the SMF returns the created SmContext response message to the AMF to add an indicator to the allocatedEbiList cell to indicate whether the corresponding EBI is the default QoS flow;
  • AMF saves the EBI/ARP information and identifies the corresponding EBI as the EBI of the default QoS flow according to the SMF indication .
  • the indicator may add a field to the response message, and the field includes the EBI of the Default QoS Flow.
  • FIG. 10 is a schematic structural diagram of a communication device provided by an embodiment of the application.
  • the communication device 1000 includes a transceiver module 1010 and a processing module 1120.
  • the communication device can be used to implement the functions related to the mobility management network element or the session management network element in any of the foregoing method embodiments.
  • the communication device may be a network device or a chip included in the network device.
  • the transceiver module 1010 is configured to receive a first request message from the session management network element, and the first request message includes the first allocation hold Priority ARP information; the processing module 1020, after the transceiver module 1010 receives the first request message, assigns a first identifier to the default quality of service QoS flow of the first connection in the first network, and the first identifier is used to identify The bearer corresponding to the default QoS flow in the second connection in the second network; the transceiver module 1010 is further configured to send a first response message to the session management network element, where the first response message includes the first identifier.
  • the first request message indicates that the first ARP information is ARP information corresponding to the default quality of service QoS flow of the first connection in the first network.
  • the first request message only includes the first ARP information, and accordingly, the first response message only includes the first identifier.
  • the first request message may also include ARP information corresponding to at least one other QoS flow of the first connection, and the position of the first ARP information in the first request message is located in at least one other QoS flow The corresponding ARP information is before the position in the first request message.
  • the first response message may include a first identifier and an identifier allocated by the mobility management network element to the at least one other QoS flow, and the first identifier is included in the first response message.
  • the position in is located before the position in the first response message where the identifier allocated by the mobility management network element for the at least one other QoS flow is located.
  • the first request message further includes first indication information, where the first indication information is used to indicate that the first ARP information is ARP information corresponding to the default QoS flow of the first connection.
  • the first response message includes a first identifier and second indication information
  • the second indication information is used to indicate that the first identifier is the default QoS flow allocated by the mobility management network element for the first connection.
  • the first ARP information is ARP information corresponding to the default QoS flow of the first connection.
  • the first response message further includes second indication information, and the second indication information is used to indicate that the first identifier is an identifier assigned to the default QoS flow of the first connection .
  • the first response message further includes an identifier assigned by the mobility management network element to the at least one other QoS flow, and the position of the first identifier in the first response message is located in the mobile The identifier assigned by the sexual management network element to the at least one other QoS flow is before the position in the first response message.
  • the first request message is the first request message after the first connection is created, and the first connection is the connection of the terminal device.
  • the processing module 1120 is further configured to determine that, among the identifiers assigned to each QoS flow of the first connection, the identifier assigned to the default QoS flow is the last to be revoked Logo.
  • the transceiver module 1010 When the communication device is used as a session management network element and the method embodiment shown in FIG. 2 is executed, the transceiver module 1010 is configured to send a first request message to the mobility management network element of the first network, and the first request message Including the first allocation and keeping priority ARP information; the transceiver module 1010 is also configured to receive a first response message from the mobility management network element, the first response message including the mobility management network element for the first connection in the first network The first identifier assigned to the default quality of service QoS flow, where the first identifier is used to identify the bearer corresponding to the default QoS flow in the second connection in the second network.
  • the first request message indicates that the first ARP information is ARP information corresponding to the default quality of service QoS flow of the first connection in the first network.
  • the first request message only includes the first ARP information; correspondingly, the first response message only includes the first identifier.
  • the first request message also includes ARP information corresponding to at least one other QoS flow of the first connection, and the position of the first ARP information in the first request message is corresponding to at least one other QoS flow.
  • the ARP information is before the position in the first request message.
  • the first response message includes a first identifier and an identifier assigned by the mobility management network element to at least one other QoS flow, and the position of the first identifier in the first response message is located in the mobility management network.
  • the identifier assigned to at least one other QoS flow precedes the position in the first response message.
  • the first request message further includes first indication information, where the first indication information is used to indicate that the first ARP information is ARP information corresponding to the default QoS flow of the first connection.
  • the first response message includes a first identifier and second indication information
  • the second indication information is used to indicate that the first identifier is the default QoS flow allocated by the mobility management network element for the first connection.
  • the first ARP information is ARP information corresponding to the default QoS flow of the first connection.
  • the first response message further includes second indication information, and the second indication information is used to indicate that the first identifier is an identifier assigned to the default QoS flow of the first connection .
  • the first response message further includes an identifier assigned by the mobility management network element to the at least one other QoS flow, and the position of the first identifier in the first response message is located in the mobile The identifier assigned by the sexual management network element to the at least one other QoS flow is before the position in the first response message.
  • the first request message is the first request message after the first connection is created, and the first connection is the connection of the terminal device.
  • the transceiver module 1010 is configured to receive a request message from the session management network element, and the request message is used to request that the terminal device is in the first The first quality of service QoS flow allocation identifier of the first connection in the network, the identifier is used to identify the bearer corresponding to the first QoS flow in the second connection in the second network; the processing module 1020 is used to determine that the cancellation is required The assigned identifier of the terminal device; the processing module 1020 is further configured to remove the second identifier of the second QoS flow from the assigned identifiers according to the policy, and assign the second identifier to the first QoS flow, where the policy is: Among the identifiers assigned to each QoS flow connected in a first network of the terminal device, the identifier assigned to the default QoS flow is the last revoked identifier; the transceiver module 1010 is also used to send a
  • the second QoS flow is a non-default QoS flow for the first connection.
  • the second QoS flow is a non-default QoS flow with the lowest priority in the first connection that can be preempted.
  • the second QoS flow is the QoS flow of the terminal device's connections other than the first connection.
  • the second QoS flow is the QoS flow with the lowest priority that can be preempted among the connections in the first network of the terminal device.
  • the second QoS flow is the default QoS flow of the terminal device's other connections except the first connection. QoS flow.
  • the processing module 1020 is further configured to determine that the first QoS flow has the preemption capability.
  • the transceiver module 1010 is also used to receive a message from a source mobility management network element or a session management network element, and the message includes an identifier assigned to the terminal device.
  • FIG. 11 is another schematic structural diagram of a communication device provided by an embodiment of this application.
  • the communication device 1100 may be used to implement the methods described in the foregoing method embodiments.
  • the communication device 1100 may be a chip or a network device.
  • the communication device 1100 includes one or more processors 1101, and the one or more processors 1001 can support the communication device 1100 to implement the mobility management network element or the session management network element method in FIGS. 2-9.
  • the processor 1101 may be a general-purpose processor or a special-purpose processor.
  • the processor 1101 may be a central processing unit (CPU) or a baseband processor.
  • the baseband processor may be used to process communication data, and the CPU may be used to control a communication device (for example, a network device, a terminal device, or a chip), execute a software program, and process data of the software program.
  • the communication device 1100 may also include a transceiving unit 1105 to implement signal input (reception) and output (transmission).
  • the communication device 1100 may be a chip, and the transceiver unit 1105 may be an input and/or output circuit of the chip, or the transceiver unit 1105 may be a communication interface of the chip, and the chip may be used as a terminal device or a network device or other wireless communication. Components of equipment.
  • the communication device 1100 may include one or more memories 1102 with a program 1104 stored thereon.
  • the program 1104 can be run by the processor 1101 to generate instructions 1103 so that the processor 1101 executes the methods described in the foregoing method embodiments according to the instructions 1103.
  • the memory 1102 may also store data.
  • the processor 1101 may also read data stored in the memory 1102. The data may be stored at the same storage address as the program 1104, or the data may be stored at a different storage address from the program 1104.
  • the processor 1101 and the memory 1102 may be provided separately or integrated together, for example, integrated on a single board or a system-on-chip (SOC).
  • SOC system-on-chip
  • the communication device 1100 may further include a transceiver unit 1105 and an antenna 1106.
  • the transceiver unit 1105 may be called a transceiver, a transceiver circuit, or a transceiver, and is used to implement the transceiver function of the communication device through the antenna 1006.
  • each step of the foregoing method embodiment may be completed by a logic circuit in the form of hardware or instructions in the form of software in the processor 1101.
  • the processor 1101 may be a CPU, a digital signal processor (digital signal processor, DSP), an application specific integrated circuit (ASIC), a field programmable gate array (field programmable gate array, FPGA) or other programmable logic devices , For example, discrete gates, transistor logic devices, or discrete hardware components.
  • the embodiment of the present application also provides a computer program product, which, when executed by the processor 1001, implements the communication method described in any method embodiment of the present application.
  • the computer program product may be stored in the memory 1102, such as a program 1104.
  • the program 1104 is finally converted into an executable object file that can be executed by the processor 1101 through processing processes such as preprocessing, compilation, assembly, and linking.
  • the embodiment of the present application also provides a computer-readable storage medium on which a computer program is stored, and when the computer program is executed by a computer, the communication method described in any method embodiment in the present application is implemented.
  • the computer program can be a high-level language program or an executable target program.
  • An embodiment of the present application provides a communication system, which includes a session management network element and a mobility management network element in a first network.
  • the communication system further includes terminal equipment.
  • the computer-readable storage medium is, for example, the memory 1102.
  • the memory 1102 may be a volatile memory or a non-volatile memory, or the memory 1102 may include both a volatile memory and a non-volatile memory.
  • the non-volatile memory can be read-only memory (ROM), programmable read-only memory (programmable ROM, PROM), erasable programmable read-only memory (erasable PROM, EPROM), and electrically available Erase programmable read-only memory (electrically EPROM, EEPROM) or flash memory.
  • the volatile memory may be random access memory (RAM), which is used as an external cache.
  • RAM random access memory
  • static random access memory static random access memory
  • dynamic RAM dynamic RAM
  • DRAM dynamic random access memory
  • synchronous dynamic random access memory synchronous DRAM, SDRAM
  • double data rate synchronous dynamic random access memory double data rate SDRAM, DDR SDRAM
  • enhanced synchronous dynamic random access memory enhanced SDRAM, ESDRAM
  • synchronous connection dynamic random access memory serial DRAM, SLDRAM
  • direct rambus RAM direct rambus RAM, DR RAM
  • the disclosed system, device, and method may be implemented in other ways. For example, some features of the method embodiments described above may be ignored or not implemented.
  • the device embodiments described above are merely illustrative.
  • the division of units is only a logical function division. In actual implementation, there may be other division methods, and multiple units or components may be combined or integrated into another system.
  • the coupling between the units or the coupling between the components may be direct coupling or indirect coupling, and the foregoing coupling includes electrical, mechanical, or other forms of connection.
  • the size of the sequence number of each process does not mean the order of execution, and the execution order of each process should be determined by its function and internal logic, and should not correspond to the embodiments of the present application.
  • the implementation process constitutes any limitation.
  • system and “network” in this article are often used interchangeably in this article.
  • the term “and/or” in this article is only an association relationship that describes associated objects, which means that there can be three relationships, for example, A and/or B, which can mean: A alone exists, A and B exist at the same time, alone There are three cases of B.
  • the character “/” in this text generally means that the associated objects before and after are in an "or" relationship.

Landscapes

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

Abstract

一种通信方法及装置，该方法包括：第一网络的移动性管理网元从会话管理网元接收第一请求消息，该第一请求消息包括第一ARP信息，移动性管理网元为第一网络中的第一连接的默认QoS流分配第一标识，该第一标识用于标识第二网络中的第二连接中与该默认QoS流对应的承载，移动性管理网元向会话管理网元发送第一响应消息，该第一响应消息包括第一标识。通过第一请求消息指示默认QoS流对应的ARP信息，可使移动性管理网元能够识别第一网络的第一连接的默认QoS流，从而为该默认QoS流分配对应的标识，确保业务连续性。此外，该方法不需要对ARP的规划进行约束限制，具有较好的灵活性和适用性。

Description

一种通信方法及装置
本申请要求于2020年1月8日提交中国专利局、申请号为202010018845.3、申请名称为“一种通信方法及装置”的中国专利申请的优先权，其要求于2019年11月8日提交中国专利局、申请号为201911090004.2、申请名称为“一种通信方法及装置”的中国专利申请的优先权，其全部内容通过引用结合在本申请中。
技术领域
本申请涉及通信技术领域，尤其涉及一种通信方法及装置。
背景技术
目前的第三代合作伙伴计划(the 3rd generation partner project，3GPP)协议支持演进型分组系统(evolved packet system，EPS)网络与第五代移动通信技术系统(5th generationsystem，5GS)网络之间的互操作。由于EPS网络通过EPS承载进行服务质量(quality of service，QoS)控制，5GS网络通过QoS流进行QoS控制，EPS网络与5GS网络之间的互操作需要进行EPS承载与QoS流之间的映射。
然而，通常情况下，EPS网络可以为一个用户创建的EPS承载的数量与5GS网络可以为一个用户创建的QoS流的数量并不相等。当5GS网络为某一用户创建的QoS流的数量大于EPS网络可为该用户创建的EPS承载的最大数量时，只能选择其中的部分QoS流切换到EPS网络。一个QoS流是否能够切换到EPS网络，可以通过是否为该QoS流分配EPS承载标识(EPS bearer identity，EBI)来实现。
现有的技术方案为，根据一个QoS流的分配保持优先级(allocation and retention priority，ARP)来决定该QoS流是否能够切换到EPS网络。如此，为了保证一个PDU会话的默认QoS流能够切换到EPS网络，需要对ARP的规划进行严格约束。即必须将默认QoS流的ARP信息设置为不可抢占类型，且优先级最高，否则可能会因为未能给默认QoS流分配EBI，或者默认QoS流的EBI被撤销，而导致整个PDU会话都无法切换到EPS网络。但是对ARP进行严格约束在现实业务部署时是很难保证的。
发明内容
本申请实施例提供一种通信方法及装置，用于在对ARP规划无依赖的情况下，为第一网络的第一连接中的默认QoS流分配在第二网络的第二连接中对应承载的标识，从而确保进行第一网络与第二网络之间的切换时的业务连续性。
第一方面，本申请实施例提供一种通信方法，该方法可应用于第一网络中的移动性管理网元，该方法包括：第一网络的移动性管理网元从会话管理网元接收第一请求消息，第一请求消息包括第一分配保持优先级ARP信息；移动性管理网元收到第一 请求消息后，为第一网络中的第一连接的默认服务质量QoS流分配第一标识，该第一标识用于标识第二网络中的第二连接中与该默认QoS流对应的承载；移动性管理网元向会话管理网元发送第一响应消息，该第一响应消息包括第一标识。
上述默认服务质量QoS流可以是第一网络中的第一连接的默认第一数据通道的一种实现方式，本发明对其他形式的第一数据通道同样适用。上述承载可以是第二网络中的第二连接中与上述第一数据通道对应的第二数据通道的一种实现方式，本发明对其他形式的第二数据通道同样适用。
在一种实现方式中，该第一请求消息指示第一ARP信息为第一网络中的第一连接的默认服务质量QoS流对应的ARP信息。通过上述方法，会话管理网元向第一网络的移动性管理网元发送的第一请求消息可指示，其携带的第一ARP信息为第一网络的第一连接中默认QoS流对应的ARP信息，从而可使移动性管理网元能够识别第一网络的第一连接的默认QoS流，从而为该默认QoS流分配对应的标识，确保业务连续性。此外，该方法不需要对ARP的规划进行约束限制，具有较好的灵活性和适用性。
结合第一方面，在第一方面的一种可能的设计中，第一请求消息中仅包括第一ARP信息，相应地，第一响应消息中仅包括第一标识。
结合第一方面，在第一方面的一种可能的设计中，第一请求消息中还可包括第一连接的至少一个其他QoS流对应的ARP信息，且该第一ARP信息在第一请求消息中的位置位于至少一个其他QoS流对应的ARP信息在第一请求消息中的位置之前。
结合第一方面，在第一方面的一种可能的设计中，第一响应消息中可包括第一标识和所述移动性管理网元为所述至少一个其他QoS流分配的标识，所述第一标识在所述第一响应消息中的位置位于所述移动性管理网元为所述至少一个其他QoS流分配的标识在所述第一响应消息中的位置之前。
结合第一方面，在第一方面的一种可能的设计中，第一请求消息中还包括第一指示信息，该第一指示信息用于指示第一ARP信息为第一连接的默认QoS流对应的ARP信息。
结合第一方面，在第一方面的一种可能的设计中，第一响应消息中包括第一标识和第二指示信息，该第二指示信息用于指示第一标识为移动性管理网元为第一连接的默认QoS流分配的标识。
结合第一方面，在第一方面的一种可能的设计中，第一ARP信息为第一连接的默认QoS流对应的ARP信息。
结合第一方面，在第一方面的一种可能的设计中，第一响应消息中还包括第二指示信息，该第二指示信息用于指示第一标识为移动性管理网元为第一连接的默认QoS流分配的标识，或者，第一响应消息中可还包括所述移动性管理网元为所述至少一个其他QoS流分配的标识，所述第一标识在所述第一响应消息中的位置位于所述移动性管理网元为所述至少一个其他QoS流分配的标识在所述第一响应消息中的位置之前。
结合第一方面，在第一方面的一种可能的设计中，第一请求消息为第一连接创建后的第一个请求消息，该第一连接为终端设备的连接。
结合第一方面，在第一方面的一种可能的设计中，该方法还包括：移动性管理网元确定，在为第一连接的各QoS流分配的标识中，为默认QoS流分配的标识为最后被撤销的标识。
第二方面，本申请实施例提供一种通信方法，该方法可应用于会话管理网元，该方法包括：会话管理网元向第一网络的移动性管理网元发送第一请求消息，该第一请求消息包括第一分配保持优先级ARP信息；会话管理网元从移动性管理网元接收第一响应消息，该第一响应消息包括移动性管理网元为第一网络中的第一连接的默认服务质量QoS流分配的第一标识，该述第一标识用于标识第二网络中的第二连接中与默认QoS流对应的承载。
在一种实现方式中，该第一请求消息指示第一ARP信息为第一网络中的第一连接的默认服务质量QoS流对应的ARP信息。通过上述方法，会话管理网元通过向第一网络的移动性管理网元发送的第一请求消息指示，其携带的第一ARP信息为第一网络的第一连接中默认QoS流对应的ARP信息，如此可使移动性管理网元能够识别第一网络的第一连接的默认QoS流，从而为该默认QoS流分配对应的标识，确保业务连续性。此外，该方法不需要对ARP的规划进行约束限制，具有较好的灵活性和适用性。
结合第二方面，在第二方面的一种可能的设计中，第一请求消息中仅包括第一ARP信息；相应地，第一响应消息中仅包括第一标识。
结合第二方面，在第二方面的一种可能的设计中，第一请求消息中还包括第一连接的至少一个其他QoS流对应的ARP信息，且该第一ARP信息在第一请求消息中的位置位于至少一个其他QoS流对应的ARP信息在第一请求消息中的位置之前。
结合第二方面，在第二方面的一种可能的设计中，第一响应消息中包括第一标识和移动性管理网元为至少一个其他QoS流分配的标识，该第一标识在第一响应消息中的位置位于移动性管理网元为至少一个其他QoS流分配的标识在第一响应消息中的位置之前。
结合第二方面，在第二方面的一种可能的设计中，第一请求消息中还包括第一指示信息，该第一指示信息用于指示第一ARP信息为第一连接的默认QoS流对应的ARP信息。
结合第二方面，在第二方面的一种可能的设计中，第一响应消息中包括第一标识和第二指示信息，该第二指示信息用于指示第一标识为移动性管理网元为第一连接的默认QoS流分配的标识。
结合第二方面，在第二方面的一种可能的设计中，第一ARP信息为第一连接的默认QoS流对应的ARP信息。
结合第二方面，在第二方面的一种可能的设计中，第一响应消息中还包括第二指示信息，该第二指示信息用于指示第一标识为移动性管理网元为第一连接的默认QoS流分配的标识，或者，第一响应消息中还包括所述移动性管理网元为所述至少一个其他QoS流分配的标识，所述第一标识在所述第一响应消息中的位置位于所述移动性管理网元为所述至少一个其他QoS流分配的标识在所述第一响应消息中的位置之前。
结合第二方面，在第二方面的一种可能的设计中，第一请求消息为第一连接创建后的第一个请求消息，该第一连接为终端设备的连接。
第三方面，本申请实施例提供一种通信方法，该方法可应用于第一网络中的移动性管理网元，该方法包括：第一网络的移动性管理网元从会话管理网元接收请求消息，该请求消息用于请求为终端设备在第一网络中的第一连接的第一服务质量QoS流分配标识，该标识用于标识第二网络中的第二连接中与第一QoS流对应的承载；移动性管理网元确定需要撤销为该终端设备已分配的标识；移动性管理网元根据策略，从已分配的标识中撤销第二QoS流的第二标识，为该第一QoS流分配第二标识，其中，所述策略为：在为终端设备的一个第一网络中的连接的各QoS流分配的标识中，为默认QoS流分配的标识为最后被撤销的标识；移动性管理网元向会话管理网元发送响应消息，该响应消息包括第二标识。
通过上述方法，在需要撤销为终端设备已分配的标识时，第一网络的移动性管理网元可根据优先撤销为第一网络的连接中的非默认QoS流分配的标识的策略，来选择被撤销标识的QoS流，如此，可避免由于为默认QoS流分配的标识被撤销，而导致该默认QoS流所在第一网络的连接都无法切换到第二网络的问题，可有效保障终端设备的业务连续性。
结合第三方面，在第三方面的一种可能的设计中，第二QoS流为第一连接的非默认QoS流。
结合第三方面，在第三方面的一种可能的设计中，第二QoS流为第一连接中优先级最低的可被抢占的非默认QoS流。
结合第三方面，在第三方面的一种可能的设计中，第二QoS流为终端设备除第一连接的其他连接的QoS流。
结合第三方面，在第三方面的一种可能的设计中，第二QoS流为终端设备的第一网络中的连接中优先级最低的可被抢占的QoS流。
结合第三方面，在第三方面的一种可能的设计中，当终端设备的第一网络中的连接中已被分配有标识的QoS流均为默认QoS流，则第二QoS流为终端设备除第一连接的其他连接的默认QoS流。
结合第三方面，在第三方面的一种可能的设计中，该方法还包括：移动性管理网元确定所述第一QoS流具有抢占能力。
结合第三方面，在第三方面的一种可能的设计中，该方法还包括：移动性管理网元发送响应消息，所述响应消息包括所述第二标识。
结合第三方面，在第三方面的一种可能的设计中，所述请求消息中还包括第一连接的至少一个其他QoS流对应的ARP信息，所述响应消息还包括为所述其他QoS流分配的标识；
结合第三方面，在第三方面的一种可能的设计中，若所述第一QoS流为所述第一连接的默认QoS流，则所述响应消息还包括第二指示信息，该第二指示信息用于指示第二标识为移动性管理网元为所述第一连接的默认QoS流分配的标识，或者，所述第二标识在所述响应消息中的位置位于所述其他QoS流分配的标识在所述响应消息中的位置之前。
结合第三方面，在第三方面的一种可能的设计中，该方法还包括：移动性管理网元接收来自会话管理网元的更新消息，该更新消息用于更新ARP与标识间的对应关系。
结合第三方面，在第三方面的一种可能的设计中，该方法还包括：移动性管理网元从源移动性管理网元或会话管理网元接收消息，该消息包括为终端设备已分配的标识。
结合第三方面，在第三方面的一种可能的设计中，所述已分配的标识包括该终端设备的一个或多个第一网络的连接中的QoS流分配的标识。
结合第三方面，在第三方面的一种可能的设计中，所述已分配的标识包括为默认QoS流分配的标识，也可包括为非默认QoS流分配的标识。
结合第三方面，在第三方面的一种可能的设计中，默认QoS流分配的标识在该消息中的位置，位于为所述第一网络的连接中的非默认QoS流分配的标识在该消息中的位置之前。
结合第三方面，在第三方面的一种可能的设计中，所述消息包括指示信息，所述指示信息用于指示默认QoS流对应的标识。
结合第三方面，在第三方面的一种可能的设计中，所述指示信息为所述默认QoS流对应的标识。
第四方面，本申请提供了一种通信装置，该装置可以是移动性管理网元，也可以是移动性管理网元内的芯片。该装置可以包括处理单元和收发单元。当该装置是移动性管理网元时，该处理单元可以是处理器，该收发单元可以是通信接口；该移动性管理网元还可以包括存储单元，该存储单元可以是存储器；该存储单元用于存储指令，该处理单元执行该存储单元所存储的指令，以使该移动性管理网元执行第一方面或第三方面所述的方法。当该装置是移动性管理网元内的芯片时，该处理单元可以是处理器，该收发单元可以是输入/输出接口、管脚或电路等；该处理单元执行存储单元所存储的指令，以使该移动性管理网元执行第一方面或第三方面所述的方法，该存储单元可以是该芯片内的存储单元(例如，寄存器、缓存等)，也可以是该移动性管理网元内的位于该芯片外部的存储单元(例如，只读存储器、随机存取存储器等)。
第五方面，本申请实施例提供一种通信装置，该通信装置可以是会话管理网元，也可以是会话管理网元内的芯片。该通信装置可以包括处理单元和收发单元。当该装置是会话管理网元时，该处理单元可以是处理器，该收发单元可以是通信接口；该会话管理网元还可以包括存储单元，该存储单元可以是存储器；该存储单元用于存储指令，该处理单元执行该存储单元所存储的指令，以使该会话管理网元执行第二方面所述的方法。当该装置是会话管理网元内的芯片时，该处理单元可以是处理器，该收发单元可以是输入/输出接口、管脚或电路等；该处理单元执行存储单元所存储的指令，以使该会话管理网元执行第二方面所述的方法，该存储单元可以是该芯片内的存储单元(例如，寄存器、缓存等)，也可以是该会话管理网元内的位于该芯片外部的存储单元(例如，只读存储器、随机存取存储器等)。
第六方面，本申请实施例提供一种芯片系统，包括：处理器，所述处理器与存储器耦合，所述存储器用于存储程序或指令，当所述程序或指令被所述处理器执行时，使得该芯片系统实现上述第一方面或第一方面的任一种可能的设计中的方法、或实现上述第二方面或第二方面的任一种可能的设计中的方法、实现上述第三方面或第三方面的任一种可能的设计中的方法。
可选地，该芯片系统还包括接口电路，该接口电路用于接收代码指令并传输至所述处理器。
可选地，该芯片系统中的处理器可以为一个或多个，该处理器可以通过硬件实现也可以通过软件实现。当通过硬件实现时，该处理器可以是逻辑电路、集成电路等。当通过软件实现时，该处理器可以是一个通用处理器，通过读取存储器中存储的软件代码来实现。
可选地，该芯片系统中的存储器也可以为一个或多个。该存储器可以与处理器集成在一起，也可以和处理器分离设置，本申请并不限定。示例性的，存储器可以是非瞬时性处理器，例如只读存储器ROM，其可以与处理器集成在同一块芯片上，也可以分别设置在不同的芯片上，本申请对存储器的类型，以及存储器与处理器的设置方式不作具体限定。
第七方面，本申请实施例提供一种计算机可读存储介质，该计算机可读存储介质中存储了计算机程序，该计算机程序被处理器执行时，使得处理器执行第一方面或第一方面的任一种可能的设计中的方法，或执行第二方面或第二方面的任一种可能的设计中的方法，或执行第三方面或第三方面的任一种可能的设计中的方法。
第八方面，本申请实施例提供一种计算机程序产品，该计算机程序产品包括：计算机程序代码，当该计算机程序代码被处理器运行时，使得处理器执行第一方面或第一方面的任一种可能的设计中的方法，或执行第二方面或第二方面的任一种可能的设计中的方法，或执行第三方面或第三方面的任一种可能的设计中的方法。
第九方面、本申请实施例提供一种通信系统，该通信系统包括会话管理网元和第一网络中的移动性管理网元。可选地，该通信系统还包括终端设备。
附图说明
图1为本申请实施例适用的一种网络架构示意图；
图2为本申请实施例提供的一种通信方法的流程示意图；
图3为本申请实施例提供的另一种通信方法的流程示意图；
图4为本申请实施例提供的一个示例中为第一QoS流分配EBI的流程示意图；
图5为本申请的具体实施例一中提供的5GS EBI分配流程的示意图；
图6为本申请的具体实施例二中提供的5GS EBI分配流程的示意图；
图7为本申请的具体实施例三中提供的5GS EBI分配流程的示意图；
图8为本申请的具体实施例四中提供的EPS到5GS Registration或Handover流程的示意图；
图9为本申请的具体实施例五中提供的EPS到5GS Registration或Handover流程的示意图；
图10为本申请实施例提供的一种通信装置的结构示意图；
图11为本申请实施例提供的一种通信装置的另一结构示意图。
具体实施方式
为了使本申请实施例的目的、技术方案和优点更加清楚，下面将结合附图对本申 请实施例作进一步地详细描述。
本申请实施例的技术方案可以应用于各种通信系统，例如：全球移动通信(global system for mobile communications，GSM)系统、码分多址(code division multiple access，CDMA)系统、宽带码分多址(wideband code division multiple access，WCDMA)系统、通用分组无线业务(general packet radio service，GPRS)、长期演进(long term evolution，LTE)系统、LTE频分双工(frequency division duplex，FDD)系统、LTE时分双工(time division duplex，TDD)、通用移动通信系统(universal mobile telecommunication system，UMTS)、全球互联微波接入(worldwide interoperability for microwave access，WIMAX)通信系统、第五代(5th generation，5G)系统或新无线(new radio，NR)，或者应用于未来的通信系统或其它类似的通信系统等。
本申请实施例提供的技术方案适用于支持第一网络与第二网络的互操作的场景中，其中，第一网络和第二网络分别为支持不同通信制式的系统，如此，第一网络也可以称为第一制式系统，第二网络也可以称为第二制式系统。例如，第一网络可以为5G通信系统，第二网络可以为4G通信系统，其中5G通信系统也可以称为5GS网络或简称为5G系统，4G通信系统也可以称为EPS网络或简称为4G系统。应理解，本申请实施例中的第一网络和第二网络还可以是其他类型的通信系统，本申请并不限定。
请参考图1，为本申请实施例适用的一种可能的网络架构示意图，在该网络架构中，5GS网络与EPS网络共存。下面，对该网络架构中涉及的主要网元进行说明。
EPS网络可以包括以下网元：
1、(无线)接入网络(radio access network，(R)AN)网元：用于为特定区域的授权终端设备提供入网功能，并能够根据终端设备的级别，业务的需求等使用不同质量的传输隧道。
(R)AN网元能够管理无线资源，为终端设备提供接入服务，进而完成控制信号和终端设备数据在终端设备和核心网之间的转发，(R)AN网元也可以理解为传统网络中的基站。在4G通信系统中，(R)AN网元也可以称为演进型通用陆基无线接入网(evovled universal terrestrial radio access network，E-UTRAN)或演进型基站(eNB)，如图1中所示。
需要说明的是，上述“网元”也可以称为实体、设备、装置或模块等，本申请并未特别限定。并且，在本申请中，为了便于理解和说明，在对部分描述中省略“网元”这一描述，例如，将(R)AN网元简称RAN，此情况下，该“(R)AN网元”应理解为(R)AN网元网元或(R)AN实体，以下，省略对相同或相似情况的说明。
2、移动性管理实体(mobility management entity，MME)，用于提供移动性管理的功能。此外，MME还可以提供合法监听以及接入授权/鉴权等功能。
3、服务网关(serving gateway，SGW)，用于提供用户数据转发等功能。
4、分组数据网络网关用户面功能(packet data network gateway user function，PGW-U)，用于提供PDN网关的用户面功能。
5、分组数据网络网关控制面功能(packet data network gateway control function，PGW-C)，用于提供PDN网关的控制面功能。
6、策略和计费规则功能(policy and charging rules function，PCRF)，用于提供 指导网络行为的统一策略框架，为控制面功能网元提供策略规则信息等。
7、归属签约用户服务器(home subscriber server，HSS)，包括用户配置文件，用于执行用户的身份验证和授权，并可提供有关用户物理位置的信息。
5GS网络可以包括以下网元：
1、(R)AN网元：用于为特定区域的授权终端设备提供入网功能，并能够根据终端设备的级别，业务的需求等使用不同质量的传输隧道。
在5G通信系统中，(R)AN网元也可以称为下一代接入网(next generation radio access network，NG-RAN，如图1所示)或下一代基站(gNB)。
2、接入管理功能(access and mobility management function，AMF)，用于接入管理和移动性管理的功能。此外，AMF还可以提供合法监听以及接入授权/鉴权等功能。
在一种可能的设计中，AMF可以通过N26接口与MME进行通信。在图1中，各个网元之间连线附件的字母和数字表示各个网元之间的通信接口的名称，然而，各个网元之间的通信接口还可以具有其他名称，本申请在此并不限制。
3、用户面功能(user plane function，UPF)，用于分组路由和转发以及用户面数据的服务质量(quality of service，QoS)处理等。
4、会话管理功能(session management function，SMF)，主要用于会话管理、终端设备的网络互连协议(internet protocol，IP)地址分配和管理、选择和管理用户平面功能。此外，SMF还可以是策略控制和收费功能接口的终结点。
5、策略控制功能(policy control function，PCF)，用于指导网络行为的统一策略框架，为控制面功能网元(例如AMF、SMF等)提供策略规则信息等。
6、统一数据管理(unified data management，UDM)网元，用于管理签约数据。此外，还用于用户服务注册管理、处理终端设备标识，接入鉴权等。
上述网络架构中，功能相同或相近的网元可以联合设置。例如，UPF和PGW-U可以合设，SMF和PGW-C可以合设，PCF和PCRF可以合设，HSS和UDM可以合设，图1中的“+”即表示两个设备可以联合设置。
应理解，上述应用于本申请的网络架构仅是举例说明的从服务化架构的角度描述的网络架构，适用本申请实施例的网络架构并不局限于此，任何能够实现上述各个网元的功能的网络架构都适用于本申请实施例。
上述网元或者功能既可以是硬件设备中的网络元件，也可以是在专用硬件上运行软件功能，或者是平台(例如，云平台)上实例化的虚拟化功能。
终端设备可以从4G通信系统中切换至5G通信系统，或者，也可以从5G通信系统中切换至4G通信系统。所述终端设备，是一种具有无线通信功能的设备，可以部署在陆地上，包括室内或室外、手持或车载；也可以部署在水面上(如轮船等)；还可以部署在空中(例如飞机、气球和卫星上等)。该终端可以是手机(mobile phone)、平板电脑(pad)、带无线收发功能的电脑、虚拟现实(virtual reality，VR)终端、增强现实(augmented reality，AR)终端、工业控制(industrial control)中的无线终端、无人驾驶(self driving)中的无线终端、远程医疗(remote medical)中的无线终端、智能电网(smart grid)中的无线终端、运输安全(transportation safety)中的无线终端、 智慧城市(smart city)中的无线终端、智慧家庭(smart home)中的无线终端等；还可以是各种形式的用户设备(user equipment，UE)，移动台(mobile station，MS)，终端设备(terminal device)。
为方便说明，本申请后续，以移动性管理网元为接入和移动性管理功能AMF网元，会话管理网元为会话管理功能SMF网元，为例进行说明。进一步地，将AMF网元简称为AMF，SMF网元简称为SMF。即本申请后续所描述的AMF均可替换为移动性管理网元，SMF均可替换为会话管理网元。
请参考图2，为本申请实施例中提供的一种通信方法的流程示意图，该方法具体包括如下步骤：
步骤S201、会话管理网元向第一网络的移动性管理网元发送第一请求消息，该第一请求消息包括第一ARP信息，该第一请求消息指示第一ARP信息为第一网络中的第一连接的默认QoS流对应的ARP信息。
该第一请求消息用于请求第一网络的移动性管理网元为第一网络中的第一连接的默认QoS流分配标识，该标识用于标识该默认QoS流在第二网络的第二连接中对应的承载，例如可以为该默认QoS流在第二网络中的第二连接中对应的承载的标识。
以第一网络为5GS网络，第二网络为EPS网络为例，第一网络中的第一连接可以是指5GS网络中的一个PDU会话，第二网络中的第二连接可以是指EPS网络中的一个PDN连接，为方便说明，本申请后续将其分别称为第一PDU会话和第一PDN连接。
本申请实施例中，一个PDU会话中至少包括一个默认QoS流(default QoS flow)，可选地，该PDU会话中还可以包括一个或多个其他的QoS流，该一个或多个其他的QoS流为非默认QoS流，或者也可以称为专用QoS流(dedicate QoS flow)。也就是说，如果一个PDU会话中仅包括一个QoS流，那么该QoS流一定为默认QoS流，如果一个PDU会话中包括多个QoS流，那么这多个QoS流中一定存在一个默认QoS流，而其他的QoS流均为非默认QoS流。类似的，一个PDN连接中至少包括一个默认EPS承载，可选的，该PDN连接中还可以包括一个或多个其他的EPS承载，该一个或多个其他的EPS承载为非默认EPS承载，或者也可以称为专用EPS承载。
如此，第一请求消息可以理解为，会话管理网元(例如SMF)向5GS网络中的移动性管理网元(例如AMF)请求为第一PDU会话的默认QoS流分配EBI，该EBI是指该默认QoS流在EPS网络中第一PDN连接中对应的EPS承载的标识。该第一请求消息也可以称为第一EBI分配请求消息，或者也可以具有其他名称，本申请并不限定。可以理解，如果一个QoS流被分配了EBI，则表示该QoS流能够从5GS网络成功切换到EPS网络。
可以理解，本申请实施例中，第一网络中的第一连接以及第二网络中的第二连接为针对同一终端设备的连接。即第一PDU会话为终端设备的PDU会话，第一PDN连接也为该终端设备的PDN连接。
可选地，会话管理网元可在第一网络中的第一连接的创建流程中，向第一网络的移动性管理网元发送第一请求消息。进一步地，该第一请求消息还可以是第一连接创建后的第一个请求消息。也就是说，当5GS网络中的第一PDU会话创建后，SMF首先为该第一PDU会话中的默认QoS流申请EBI，从而使得终端设备在进行5GS网络 至EPS网络的切换时，该PDU会话中的默认QoS流能够成功切换到EPS网络，保障终端设备的业务连续性。
本申请实施例中，指示第一ARP信息为第一网络中的第一连接的默认QoS对应的ARP信息可具有多种可能的实现方式。
在第一种可能的实现方式中，第一请求消息中可以仅包括第一ARP信息。也就是说，第一请求消息中可以只携带第一连接的默认QoS流的ARP信息，从而便于移动性管理网元识别第一连接中的默认QoS流。需要说明的是，第一请求消息中可以仅包括第一ARP信息，是指第一请求消息不包括第一连接的其他QoS流的ARP信息，当然，根据不同的场景，第一请求消息还可以包括其他的信息。
例如，移动性管理网元可以将第一网络的第一连接创建后，从会话管理网元接收到第一个第一请求消息中携带的第一ARP信息，确认为第一连接的默认QoS流对应的ARP信息。
在第二种可能的实现方式中，第一请求消息中可以包括第一ARP信息和该第一连接的至少一个其他QoS流对应的ARP信息。为了便于移动性管理网元识别该第一连接的默认QoS流对应的ARP信息，第一ARP信息在第一请求消息中的位置位于该第一连接的至少一个其他QoS流对应的ARP信息在第一请求消息中的位置之前。
例如，第一ARP信息和该第一连接的至少一个其他QoS流对应的ARP信息可以包含在第一请求消息中的不同字段中，且包含第一ARP信息的字段位于包含该第一连接的至少一个其他QoS流对应的ARP信息的字段之前。可选的，可以第一ARP信息位于第一请求消息中的一个字段中，该第一连接的至少一个其他QoS流对应的ARP信息位于第一请求消息中的另一个或多个字段中；或者，也可以每个QoS流对应的ARP信息在第一请求消息中都具有一个独立的字段，本申请并不限定。
再例如，第一ARP信息和该第一连接的至少一个其他QoS流对应的ARP信息可以包含在第一请求消息中的相同字段中，且第一ARP信息在该字段中的位置位于该第一连接的至少一个其他QoS流对应的ARP信息在该字段中的位置之前。
又例如，第一请求消息中可以包含一个ARP信息的列表，该第一ARP信息位于该ARP信息的列表的第一个位置，该第一连接的至少一个其他QoS流对应的ARP信息位于该ARP信息的列表中第一ARP信息之后。
在第三种可能的实现方式中，第一请求消息中可以包括第一ARP信息和第一指示信息，该第一指示信息用于指示第一ARP信息为第一连接的默认QoS流对应的ARP信息。
可选的，该第一请求消息中还可以包括第一连接的至少一个其他QoS流对应的ARP信息，且第一ARP信息在第一请求消息中的位置位于第一连接的至少一个其他QoS流对应的ARP信息之前。第一ARP信息与第一连接的至少一个其他QoS流对应的ARP信息在第一请求消息中的位置的具体实施方式可以参考上述第二种可能的实现方式中的描述，在此不再赘述。
本申请实施例中，第一指示信息可以表现为第一请求消息中的某个字段中携带的信息，例如，如果第一ARP信息与第一连接的至少一个其他QoS流对应的ARP信息位于第一请求消息中的不同字段中，那么第一指示信息可用于指示第一ARP信息所在 的字段，该第一指示信息可以位于第一ARP信息所在的字段中，也可以位于一个单独的字段中，本申请并不限定。再例如，如果第一ARP信息与第一连接的至少一个其他QoS流位于第一请求消息中的同一字段中，第一指示信息可用于指示该字段中包含的第一个ARP信息为第一ARP信息。再例如，第一请求消息中包括ARP列表，该ARP列表中包括所有需要分配EBI的QoS流对应的ARP，除该ARP列表之外，第一请求消息中还包括默认QoS流对应的ARP，该默认QoS流对应的ARP作为第一指示信息。又例如，如果第一请求消息中包括一个ARP信息的列表，第一指示信息用于指示该ARP信息的列表中第一个ARP信息为第一ARP信息。或者，第一指示信息也可以以隐式的形式存在，例如，可将第一请求消息中包含一个特定的用于指示第一ARP信息的字段的存在视为第一指示信息。
需要说明的是，该第三种可能的实现方式可以应用于在PDU会话创建流程中，PCF下发了多个rule，需要映射成个QoS rule的场景下，或者，终端设备原来不支持第一网络与第二网络之间的互操作，但是后续签约修改成支持第一网络与第二网络之间的互操作的场景下。
在第四种可能的实现方式中，第一请求消息中可以包括第一ARP信息和该第一连接的至少一个其他QoS流对应的ARP信息。第一ARP信息为所述第一网络中的第一连接的默认服务质量QoS流对应的ARP信息。换句话说，第一ARP本身可以作为指示信息，用以指示第一ARP信息为所述第一网络中的第一连接的默认服务质量QoS流对应的ARP信息。例如，第一ARP的优先级被设置为特定的值，该特定的值指示该ARP为默认服务质量QoS流对应的ARP。在一种实现方式中，预定义默认QoS流对应的ARP的优先级的数值，其他QoS流对应的ARP不能设置为该预定义的数值，在另外一种实现方式中，可以设置ARP的是否支持被抢占属性(Pre-emption vulnerability)来将默认QoS流对应的ARP与其他QoS流的ARP进行区分，例如，将默认QoS流的ARP设置为不能被抢占，其他QoS流的ARP设置为可以被抢占。当然，还可以采用其他方式来将默认QoS流的ARP与其他QoS流的ARP进行区分，本实施例对此不做限定。该实现方式可以不需要额外的指示信息，也可以不需要将第一ARP放置在其他ARP之前。移动性管理网元根据ARP即可确定该ARP是否是默认QoS流对应的ARP。
此外，应理解，本申请实施例所提及的QoS流对应的ARP信息，并不限定一个ARP信息与一个QoS流是一一对应的，一个ARP信息可以对应于一个或多个QoS流。也就是说，不同的QoS流对应的ARP信息可能是相同，当第一请求消息中包括多个QoS流对应的ARP信息时，若该多个QoS流中的部分QoS流对应的ARP信息相同，那么相同的ARP信息可以在第一请求消息中重复出现多次，即一个ARP信息与一个QoS流一一对应；相同的ARP信息也可以在第一请求消息仅出现一次，即存在一个或多个QoS流对应于同一个ARP信息。
上述第一种和第二种可能的实现方式可以理解为，以隐式的形式指示第一请求消息中的第一APR信息为默认QoS流对应的ARP信息，上述第三种可能的实现方式可以理解为，以显式的形式指示第一请求消息中的第一APR信息为默认QoS流对应的ARP信息。
步骤S202、移动性管理网元从会话管理网元接收第一请求消息。
步骤S203、移动性管理网元接收到第一请求消息后，为第一网络中的第一连接的默认QoS流分配第一标识，该第一标识用于标识第二网络中的第二连接中与该默认QoS流对应的承载。
本申请实施例中，移动性管理网元可以根据策略，为第一网络中的第一连接的默认QoS流分配第一标识。该策略包括：如果终端设备当前存在可用的第二网络中的第二连接的承载的标识，那么移动性管理网元可从可用的第二连接的承载的标识中，为该第一连接的默认QoS流分配一个标识。如果终端设备当前不存在可用的第二网络中的第二连接的承载的标识，则需要撤销为该终端设备已分配的第二连接的第二承载的标识，移动性管理网元可将撤销了的第二连接的第二承载的标识再次分配给该第一连接的默认QoS流。但在撤销为终端设备已分配的第二连接的承载的标识时，应注意，为一个第一连接的各QoS流分配的标识中，为默认QoS流分配的标识为最后被撤销的标识。
应理解，若第一请求消息中除了第一ARP信息之外，还包括该第一连接的至少一个其他QoS流对应的ARP信息，则移动性管理网元可以优先为默认QoS流分配EBI。即，当移动性管理网元确认不能为所有请求的QoS流分配EBI时，移动性管理网元首先将可用的EBI分配给默认QoS流。
还应理解，若第一请求消息中除了第一ARP信息之外，还包括该第一连接的至少一个其他QoS流对应的ARP信息，那么移动性管理网元可以采用与为该默认QoS流分配第一标识的类似的方式，为该第一连接的至少一个其他QoS流中的部分或全部QoS流分配第二连接中对应的承载的标识。也就是说，由于可以为一个终端设备的QoS流分配的第二连接中的承载的标识是有限的，因此，可能会存在部分非默认QoS流未能被分配标识的情况。
以第一网络为5GS网络，第二网络为EPS网络为例，第一请求消息中可以包括第一PDU会话中的默认QoS流对应的ARP信息，5GS网络中的移动性管理网元(例如AMF)在接收到第一请求消息后，可为第一PDU会话中的默认QoS流分配第一EBI，该第一EBI为EPS网络中的第一PDN连接中与第一PDU会话中默认QoS流对应的EPS承载的标识。若第一请求消息中可以包括第一PDU会话的一个或多个非默认QoS流对应的ARP信息，那么AMF可以以相同的方式，为该第一PDU会话的一个或多个非默认QoS流中的部分或全部QoS流分配EBI。
需要说明的是，本申请实施例中所提及的撤销还可以表达为回收、取消、释放等，本申请并不限定。
移动性管理网元如何根据策略为第一网络中的第一连接的默认QoS流分配标识，将在本申请实施例提供的另一种通信方法中进行详细介绍。
步骤S204、移动性管理网元向会话管理网元发送第一响应消息，该第一响应消息包括第一标识。
对应于指示第一ARP信息为第一网络中的第一连接的默认QoS流对应的ARP信息的第一种可能的实现方式，第一响应消息中可以仅包括为该默认QoS流分配的第一标识。类似的，第一响应消息中可以仅包括为该默认QoS流分配的第一标识是指第一 响应消息不包括为其他QoS流分配的标识，当然，根据不同的场景，第一响应消息还可以包括其他的信息。
以第一网络为5GS网络，第二网络为EPS网络为例，第一响应消息中可以仅包括为第一PDU会话的默认QoS流分配的第一EBI。
对应于指示第一ARP信息为第一网络中的第一连接的默认QoS流对应的ARP信息的第二种可能的实现方式，第一响应消息中可以包括第一标识和移动性管理网元为该第一连接的至少一个其它QoS流分配的标识，且第一标识在第一响应消息中的位置位于移动性管理网元为该第一连接的至少一个其他QoS流分配的标识在第一响应消息中的位置之前。
以第一网络为5GS网络，第二网络为EPS网络为例，第一响应消息中可以包括AMF为第一PDU会话的默认QoS流分配的第一EBI，以及AMF为该第一PDU会话的至少一个其它QoS流分配的EBI，且第一EBI在第一响应消息中的位置位于AMF为该第一PDU会话的至少一个其它QoS流分配的EBI在第一响应消息中的位置之前。
第一标识在第一响应消息中的位置的具体实施方式与第一ARP信息在第一请求消息中的位置的具体实施方式类似，即可以是包含第一标识的字段位于包含移动性管理网元为该第一连接的至少一个其他QoS流分配的标识的字段之前，也可以是在一个字段中，第一标识在该字段中的位置位于移动性管理网元为该第一连接的至少一个其他QoS流分配的标识在该字段中的位置之前，还可以是第一响应消息中存在一个第二连接的承载的标识的列表，第一标识在该标识的列表中的第一个位置，具体请参见上文中的描述。
对应于指示第一ARP信息为第一网络中的第一连接的默认QoS流对应的ARP信息的第三种可能的实现方式，第一响应消息中可以包括第一标识和第二指示信息，该第二指示信息用于指示第一标识为移动性管理网元为第一连接的默认QoS流分配的标识。
可选的，第一响应消息中还可以包括移动性管理网元为该第一连接的至少一个其他QoS流分配的标识，且第一标识在第一响应消息中的位置位于移动性管理网元为该第一连接的至少一个其他QoS流分配的标识在第一响应消息中的位置之前。第一标识在第一响应消息中的位置的具体实施方式与第一ARP信息在第一请求消息中的位置的具体实施方式类似，具体请参见上文中的描述。
以第一网络为5GS网络，第二网络为EPS网络为例，第一响应消息中可以包括AMF为第一PDU会话的默认QoS流分配的第一EBI和第二指示信息，该第二指示信息用于指示第一EBI为AMF为第一PDU会话的默认QoS流分配的EBI。可选的，第一响应消息中可以包括AMF为该第一PDU会话的至少一个其它QoS流分配的EBI，且第一EBI在第一响应消息中的位置位于AMF为该第一PDU会话的至少一个其它QoS流分配的EBI在第一响应消息中的位置之前。
第二指示信息的具体实施方式与第一指示信息的具体实施方式类似，即第二指示信息可以表现为第一响应消息中的某个字段中携带的信息，或是第一响应消息中的一个信息单元(information element，IE)。例如，如果第一标识与移动性管理网元为第一连接的至少一个其他QoS流分配的标识位于第一响应消息中的不同字段中，那么第 二指示信息可用于指示第一标识信息所在的字段，该第二指示信息可以位于第一标识所在的字段中，也可以位于一个单独的字段中，本申请并不限定；再例如，如果第一标识与移动性管理网元为第一连接的至少一个其他QoS流分配的标识位于第一响应消息中的同一字段中，第一指示信息可用于指示该字段中包含的第一个标识为分配给第一连接的默认QoS流的第一标识。再例如，第一响应消息中包括所有已分配EBI的QoS流对应的ARP与为该QoS流分配的EBI的对应关系的列表，除此之外，第一响应消息中还包括为默认QoS流分配的EBI，该EBI作为第二指示信息。又例如，如果第一响应消息中包括一个第二连接中的承载的标识的列表，第二指示信息用于指示该标识的列表中第一个标识为分配给第一连接的默认QoS流的第一标识。或者，第一指示信息也可以以隐式的形式存在，例如，可将第一响应消息中包含的一个特定的用于指示分配给第一连接的默认QoS流的第一标识的字段的存在视为第二指示信息。
可选地，若第一响应消息中包括移动性管理网元为多个QoS流分配的标识，那么该多个QoS流分配的标识在第一响应消息中的顺序，可以与该多个QoS流对应的ARP信息在第一请求消息中的顺序相同或不同，本申请并不限定。
可以理解，在步骤S204之后，移动性管理网元还可以为该第一连接中的其它QoS流继续分配在第二网络中的第二连接中对应的承载的标识，也可以为第一网络的其他连接中的QoS流分配在第二网络中的第二连接中对应的承载的标识，所述第一网络的其他连接与前述的第一连接均为同一终端设备的连接。
还应理解，移动性管理网元可以从同一个会话管理网元处接收请求为该第一连接中的其他QoS流或第一网络的其他连接中的QoS流分配标识的第二请求消息，也可以从另一个会话管理网元处接收请求为该第一连接中的其他QoS流或第一网络的其他连接中的QoS流分配标识的第二请求消息，本申请并不限定。
即，在步骤S204之后，AMF还可以为第一PDU会话的其它QoS流或该终端设备的第二PDU会话的QoS流分配EBI。若AMF从第一SMF接收到请求为第一PDU会话的默认QoS流分配EBI的第一请求消息，假设将请求为第一PDU会话的其它QoS流或该终端设备的第二PDU会话的QoS流分配EBI的请求消息记做第二请求消息，那么AMF可从第一SMF接收该第二请求消息，也可以从第二SMF接收该第二请求消息。
需要说明的是，会话管理网元在收到第一响应消息后，若第一响应消息中所指示的第一标识对应的ARP不是默认QoS流对应的ARP(例如，移动性管理网元根据第四种方式确定默认QoS流对应的ARP时将错误的ARP确定为默认QoS流对应的ARP)，则会话管理网元可进行如下处理：
会话管理网元将第一标识确定为默认QoS流对应的EBI。
假设第一请求消息中包括了ARP1和ARP2，SMF确定的第一ARP是ARP1，但AMF确定的第一ARP是ARP2，AMF为ARP1分配EBI1，ARP2分配EBI2，AMF在第一响应消息中发送了<ARP2，EBI2>,<ARP1,EBI1>，并指示EBI2为默认QoS流对应的EBI，则SMF将EBI2作为默认QoS流对应的EBI，即，SMF实际保存的信息为<ARP1，EBI2>,<ARP2,EBI1>。
这样会出现AMF保存的<ARP,EBI>的对应关系与SMF中的不一致。
可选的，会话管理网元给AMF发送更新消息，用于更新ARP与EBI的对应关系。即，SMF在重新确定了对应关系后，将新的对应关系发送给AMF。如上例，SMF给AMF发送的更新消息中包括：<ARP1，EBI2>,<ARP2,EBI1>，这样AMF和SMF中保存了相同的对应关系。该更新操作不改变AMF所确定的哪个EBI为默认QoS流对应的EBI。
请参考图3，为本申请实施例提供的另一种通信方法的流程示意图，该方法具体包括如下步骤：
步骤S301、第一网络的移动性管理网元从会话管理网元接收请求消息，该请求消息用于请求为终端设备在第一网络中的第一连接的第一QoS流分配标识，该标识用于标识第二网络中的第二连接中与第一QoS流对应的承载。
所述请求消息中可以包括第一QoS流对应的ARP信息。第一QoS流可以为第一连接的默认QoS流，也可以为第一连接的非默认QoS流，本申请实施例并不限定。当第一QoS流为第一连接的默认QoS流时，该请求消息中还可以指示第一ARP信息为所述第一网络中的第一连接的默认服务质量QoS流对应的ARP信息，此处的第一ARP信息是指第一QoS流对应的ARP信息。或者，第一ARP本身可以作为指示信息，用以指示第一ARP信息为所述第一网络中的第一连接的默认服务质量QoS流对应的ARP信息。也就是说，本申请实施例提供的两种通信方法在应用时也可以相互结合。
所述请求消息中也可以包括该第一连接的其他QoS流对应的ARP信息，用以为其他QoS流分配标识。
以第一网络为5GS网络，第二网络为EPS网络为例，第一网络中的第一连接可以是指5GS网络中的一个PDU会话，如第一PDU会话，第二网络中的第二连接可以是指EPS网络中的一个PDN连接，如第一PDN连接。如前所述，一个PDU会话中可包括一个或多个QoS流，该一个或多个QoS流中包括一个默认QoS流，除默认QoS流之外，该一个或多个QoS流中的其它QoS流为非默认QoS流，也可以称为专用QoS流。一个PDN连接中可包括一个或多个EPS承载，该第一或多个EPS承载中包括一个默认EPS承载，除默认EPS承载之外，该第一或多个EPS承载中的其他EPS承载为非默认EPS承载，或者也可以称为专用EPS承载，用于标识第二网络中的第二连接的承载的标识是指EPS承载的标识，即EBI。
如此可知，所述请求消息用于请求为终端设备在5GS网络中的第一PDU会话的第一QoS流分配EBI，该EBI为第一QoS流在EPS网络中对应的EPS承载的标识，该第一QoS流可以为第一PDU会话中的默认QoS流或非默认QoS流。
步骤S302、移动性管理网元确定需要撤销为终端设备已分配的标识。
本申请实施例中，可以为每个终端设备配置一个允许为该终端设备分配的标识的最大数量，该标识是指第二网络中的第二连接中承载的标识。不同的终端设备对应的可分配的标识的最大数量可以相同，也可以不同，本申请并不限定。
如此，移动性管理网元确定需要撤销为终端设备已分配的标识可以为：移动性管理网元确定为该终端设备已分配的标识的数量达到设定阈值，该终端设备当前已没有可用的标识了，该设定阈值即为该终端设备对应的可分配标识的最大数量。应理解，移动性管理网元确定需要撤销为终端设备已分配的标识还可以为其他情形，本申请并 不限定。例如，终端设备从支持第一网络与第二网络之间的互操作变成不支持第一网络与第二网络之间的互操作，会话管理网元请求移动性管理网元撤销为该终端设备已分配的标识，于是移动性管理网元可确定需要撤销为该终端设备分配的标识。
以第一网络为5GS网络，第二网络为EPS网络为例，每个终端设备可对应一个可分配的EBI数量的最大值。若当前已为该终端设备的QoS流分配的EBI的数量等于该EBI数量的最大值，则表示该终端设备当前没有可用的EBI了，需要撤销为该终端设备的某个QoS流已分配的EBI。
步骤S303、移动性管理网元根据策略，从已分配的标识中撤销第二QoS流的第二标识，为第一QoS流分配该第二标识。其中，所述策略为：在为终端设备的一个第一网络中的连接的各QoS流分配的标识中，为默认QoS流分配的标识为最后被撤销的标识。
第二QoS流可以为第一连接的非默认QoS流，即第二QoS流与第一QoS流可以都属于第一连接，或者说，第一QoS流可以抢占与其同属于第一连接的非默认QoS流的标识。这一情形要求，第一QoS流为第一连接的非默认QoS流。可选的，第二QoS流可以为第一连接中优先级最低的可被抢占的非默认QoS流。
或者，第二QoS流也可以为该终端设备除第一连接的其它第一网络的连接的非默认QoS流，即第二QoS流与第一QoS流可以属于不同的第一网络的连接，第一QoS流可以抢占其它第一网络的连接的非默认QoS流的标识。在这一情形下，第一QoS流可以为第一连接的非默认QoS流或默认QoS流，并不限定。可选的，第二QoS流可以为该第二QoS流所在的其它第一网络的连接中优先级最低的可被抢占的非默认QoS流，或者第二QoS流也可以为该终端设备的所有第一网络的连接中优先级最低的可被抢占的非默认QoS流。
再或者，第二QoS流还可以为该终端设备除第一连接的其他第一网络的连接的默认QoS流，即第二QoS流与第一QoS流可以属于不同的第一网络的连接，第一QoS流可以抢占其它第一网络的连接的默认QoS流的标识。但应注意，在这一情形下，要求该第二QoS流所在的其它第一网络的连接中只有该第二QoS流被分配有标识，不存在非默认QoS流被分配有标识。也就是说，为第二QoS流分配的标识为该第二QoS流所在的其它第一网络的连接中最后一个被撤销的标识。可选的，第二QoS流可以为该终端设备的所有第一连接中优先级最低的可被抢占的默认QoS流。
本申请实施例中，移动性管理网元可根据第一QoS流对应的ARP信息，以及该终端设备已被分配标识的各个QoS流对应的ARP信息，来决定撤销为哪个QoS流已分配的标识，即确定需要被撤销标识的第二QoS流的身份。
在一种可能的实现方式中，移动性管理网元可首先确定从终端设备的哪个第一网络的连接中撤销标识，即确定第二QoS流所在的第一网络的连接的身份。进而，再在确定的第一网络的连接中确定第二QoS流。
具体的，移动性管理网元可以根据已被分配标识的各个第一网络的连接的ARP信息，从已被分配标识的各个第一网络的连接中，选择包括的QoS流的优先级均小于或小于等于其它第一网络的连接包括的QoS流的优先级的第一网络的连接。如果在该选择的第一网络的连接中存在至少一个已被分配标识的非默认QoS流，那么移动性管理 网元可从该至少一个已被分配标识的非默认QoS流选择其中一个非默认QoS流作为第二QoS流。可选的，AMF可以从该至少一个已被分配标识的非默认QoS流中，选择优先级最低的可被抢占的非默认QoS流作为第二QoS流。
如果选择的第一网络的连接中只有默认QoS流被分配有标识，且选择出的第一网络的连接与第一连接不同，则移动性管理网元可将该默认QoS流作为第二QoS流。否则，如果选择的第一网络的连接中只有默认QoS流被分配有标识，但该选择出的第一网络的连接就是第一连接，那么移动性管理网元可确定不为第一QoS流分配标识。
以第一网络为5GS网络，第二网络为EPS网络为例，假设将第二QoS流所在的PDU会话记做第二PDU会话，AMF可根据终端设备的各个PDU会话中包括的QoS流的优先级，确定第二PDU会话，该第二PDU会话具体是指包括的QoS流的优先级均小于或小于等于其他PDU会话中包括的QoS流的优先级的PDU会话。如果第二PDU会话中存在至少一个非默认QoS流被分配有EBI，那么AMF可从该至少一个被分配有EBI的非默认QoS流中选择一个非默认QoS流作为第二QoS流。可选的，该第二QoS流具体是指至少一个被分配有EBI的非默认QoS流中优先级最低的可被抢占的非默认QoS流。
如果第二PDU会话中只有默认QoS流被分配有EBI，且第二PDU会话与第一PDU会话是不同的PDU会话，那么AMF可将该第二PDU会话的默认QoS流作为第二QoS流。如果第二PDU会话中只有默认QoS流被分配有EBI，但是第二PDU会话与第一PDU会话实际上是同一PDU会话，那么AMF可确定不为第一QoS流分配EBI，即AMF拒绝为第一QoS流分配EBI。
在另一种可能的实现方式中，如果终端设备所有的第一网络的连接中存在至少一个已被分配标识的非默认QoS流，则移动性管理网元可从该至少一个已被分配标识的非默认QoS流中选择一个非默认QoS流作为第二QoS流。可选的，移动性管理网元可从该至少一个已被分配标识的非默认QoS流中，选择优先级最低的可被抢占的非默认QoS流，作为第二QoS流。如果终端设备所有的第一网络的连接中已被分配标识的QoS流均为默认QoS流，那么移动性管理网元可从各个已被分配标识的默认QoS流中选择一个默认QoS流，作为第二QoS流。可选的，移动性管理网元可从已被分配标识的各个默认QoS流中，选择优先级最低的可被抢占的默认QoS流，作为第二QoS流。
以第一网络为5GS网络，第二网络为EPS网络为例，AMF可首先判断该终端设备的各个PDU会话中是否存在至少一个已被分配标识的非默认QoS流，如果存在，那么AMF可从该至少一个已被分配标识的非默认QoS流中，选择一个非默认QoS流，作为第二QoS流。可选的，该第二QoS流为该至少一个已被分配标识的非默认QoS流中优先级最低的可被抢占的非默认QoS流。如果不存在，即该终端设备的各个PDU会话中已被分配标识的QoS流均为默认QoS流，那么AMF可从已被分配标识的默认QoS流中选择一个默认QoS流作为第二QoS流。可选的，第二QoS流为已被分配标识的默认QoS流中优先级最低的可被抢占的默认QoS流。
可选的，针对上述两种可能的确定第二QoS流的方式，移动性管理网元从已分配的标识中撤销第二QoS流的第二标识之前，还可以根据第一QoS流对应的ARP信息确定第一QoS流具有抢占能力，且第一QoS流对应的优先级大于第二QoS流对应的 优先级。即第一第一QoS流只能抢占优先级比自己低的QoS流的标识。
若请求消息中包括第一连接的其他QoS流的ARP，则移动性管理网元也为其他QoS流分配标识，移动性管理网元为其他QoS流分配标识的方法可参看为第一QoS流分配标识的方法，这里不再赘述。
步骤S304、移动性管理网元向会话管理网元发送响应消息，该响应消息包括第二标识。
若第一QoS流为第一连接的默认QoS流，该响应消息还可用于指示第二标识是为第一连接的默认QoS流分配的标识，具体的指示方式可参见步骤S204。请参考图4所示的流程图，在一个具体的示例中，AMF从SMF接收到请求为终端设备的第一PDU会话的第一QoS流分配EBI的请求消息后，可首先判断为该终端设备已分配的EBI的数量。若已为该终端设备分配的EBI的数量没有超过设定阈值，则AMF可从可用的EBI中选择一个EBI分配给第一QoS流。若已为该终端设备分配的EBI的数量超过设定阈值，则AMF可确定需要撤销已分配的EBI。进而，AMF可根据请求消息中携带的第一QoS流对应的ARP信息，判断第一QoS流是否具有抢占能力。若第一QoS流具有抢占能力，AMF可继续判断在该终端设备的各个PDU会话中，是否存在已被分配EBI且优先级低于第一QoS流且可被抢占的至少一个非默认QoS流，如果存在，则AMF可将该至少一个非默认QoS流中优先级最低的QoS流的EBI撤销，然后将该EBI分配给第一QoS流。若第一QoS流不具有抢占能力，或者该终端设备的各个PDU会话中不存在已被分配EBI且优先级低于第一QoS流且可被抢占的至少非默认QoS流，或者AMF找不到可以撤销EBI的QoS流，那么AMF可拒绝为该第一QoS流分配EBI。随后，AMF可向SMF发送响应消息，若AMF成功为第一QoS流分配了EBI，该响应消息中可包括为该第一QoS流分配的EBI，若AMF没有为第一QoS流分配EBI，该响应消息中可包括用于指示为该第一QoS流分配EBI失败的信息。
在一种可能的实现方式中，若第一QoS流为默认QoS流，AMF也可以不判断第一QoS流对应的ARP是否指示第一QoS流具有抢占能力，AMF总是将该第一QoS看作有抢占能力。
可选的，移动性管理网元还可以从源移动性管理网元接收消息，该消息包括为该终端设备已分配的标识。具体的，为该终端设备已分配的标识可包括：源移动性管理网元为该终端设备的一个或多个第一网络的连接中的QoS流分配的标识，其中，可包括为默认QoS流分配的标识，也可包括为非默认QoS流分配的标识，本申请并不限定。应理解，为一个QoS流分配的标识是指该QoS流在第二网络中对应的承载的标识。进一步地，针对每个第一网络的连接，为该第一网络的连接中的默认QoS流分配的标识在该消息中的位置，位于为该第一网络的连接中的非默认QoS流分配的标识在该消息中的位置之前。
应理解，移动性管理网元从源移动性管理网元接收消息可对应于在两个第一网络的移动性管理网元之间传递上下文的场景。
可选的，移动性管理网元还可以从会话管理网元接收消息，该消息包括该终端设备已分配的标识。具体的，为该终端设备已分配的标识可包括：第二网络中的移动性管理网元该终端设备的一个或多个第一网络的连接中的QoS流分配的标识。其中，可 包括为默认QoS流分配的标识，也可包括为非默认QoS流分配的标识，本申请并不限定。应理解，为一个QoS流分配的标识是指该QoS流在第二网络中对应的承载的标识。进一步地，针对每个第一网络的连接，为该第一网络的连接中的默认QoS流分配的标识在该消息中的位置，位于为该第一网络的连接中的非默认QoS流分配的标识在该消息中的位置之前。
应理解，移动性管理网元从会话管理网元接收消息可对应于终端设备从第二网络切换到第一网络的场景。
可选的，移动性管理网元从源移动性管理网元或会话管理网元接收的消息中还可包括指示信息，该指示信息中包括至少一个EBI，该指示信息可用于指示为该至少一个EBI中的第一EBI为第一网络的第一连接的默认QoS流对应的EBI。该指示信息例如可为在<ARP，EBI>列表的外面，增加了一个缺省EBI，用来指示哪个EBI是默认的QoS流对应的EBI。进一步地，AMF可保存从该消息中接收到的该至少一个EBI。
需要说明的是，移动性管理网元可以在执行步骤S301中从会话管理网元接收请求消息之前，源移动性管理网元或会话管理网元接收上述消息。
下面结合几个具体实施例来详细说明本申请实施例提供的通信方法。
具体实施例一--5GS EBI分配流程
如图5所示，在该具体实施例一中，SMF为一个PDU会话下QoS流首次申请EBI时只携带一个ARP。为了识别默认QoS流，SMF在首次EBI分配请求消息固定携带默认QoS流对应的ARP；相应的，AMF默认将每个PDU会话下第一个分配的EBI标识为默认QoS流对应的EBI。详细流程如下：
1)、在PDU会话创建流程中，SMF向AMF发起EBI分配请求消息，消息中只携带默认QoS流对应的ARP。
2)、AMF为ARP分配EBI并将此EBI标识为默认QoS流对应EBI后向SMF发送EBI分配响应消息，消息中携带分配的EBI。AMF根据该请求消息是该PDU会话的第一个EBI请求消息判断该ARP为默认QoS流对应的ARP，为该QoS流分配的EBI为默认QoS流对应的EBI。
3)、SMF可继续向AMF为该PDU会话申请分配EBI，AMF可判断后续请求消息中的ARP为非默认QoS流对应的ARP。
4)、当AMF为该用户分配的EBI数达到EPS Bearer个数上限时，若AMF继续收到分配EBI的请求，AMF需要撤销已分配的EBI。应理解，此时，分配EBI的请求可能用于为步骤1的PDU会话的非默认QoS流分配EBI，或者为其他PDU会话的默认QoS流或非默认QoS流分配EBI。
AMF撤销已分配的EBI的过程可参考上面方法实施例中的描述。
5)、AMF向SMF发送响应消息，响应消息中携带分配的EBI。
具体实施例二-5GS EBI分配流程
如图6所示，该具体实施例二与具体实施例一的区别在于：SMF首次申请EBI分配时，在请求消息中同时携带多个ARP，为了标识默认QoS流，需要进行如下处理，其它处理和具体实施例一保持一致。
1)、SMF在首次EBI分配请求消息中，将默认QoS流对应的ARP放在所有ARP中的第一个位置。例如，SMF的EBI分配请求中携带ARP列表，默认QoS流的ARP位于该ARP列表的首位。
2)、AMF将第一个ARP对应的EBI标识为默认QoS流对应的EBI。
3)、在响应消息中，AMF将默认QoS流对应的EBI放在所有分配的EBI的第一个位置；例如，AMF在响应消息中包括<ARP,EBI>列表，其中，该列表的第一个<ARP,EBI>为默认QoS流对应的ARP和EBI。
具体实施例三-5GS EBI分配流程
如图8所示，该具体实施例二与具体实施例一的区别在于：SMF首次申请EBI分配时，在请求消息中同时携带多个ARP，为了标识默认QoS流，需要进行如下处理，其它处理和具体实施例一保持一致。
1)、SMF在首次EBI分配请求消息中，除了携带每个需要分配EBI的QoS流的ARP之外还携带第一指示信息，用来指示哪个ARP是默认QoS流对应的ARP。例如，在请求消息中包括ARP列表，其中ARP列表中包括每个需要分配EBI的QoS流的ARP，第一指示信息为默认QoS流的ARP。
2)、AMF将第一个ARP对应的EBI标识为默认QoS流对应的EBI；
3)、在响应消息中，AMF除了携带每个已分配的EBI和其对应的ARP之外，还携带指示信息，用于指示哪个EBI是默认QoS流对应的EBI。例如，响应消息包括《EBI,ARP》列表，该列表中包括每个分配的EBI和该EBI对应的ARP，指示信息为默认QoS流对应的EBI。
具体实施例四-EPS到5GS Registration或Handover流程
如图7所示，在EPS到5GS注册Registration或切换Handover流程中，包括如下步骤：
1)、AMF向SMF发送SmContext Create Request消息。
2)、SMF向AMF返回创建的SmContext响应消息携带的allocatedEbiList信元中将默认QoS流对应的ARP和EBI放在第一个位置；AMF保存EBI/ARP信息并将第一个EBI标识为默认QoS流的EBI。
3)、各网元完成EPS to 5G Registration/Handover流程后续处理。
4)、后续EBI分配流程处理和5GS EBI分配流程相同。
具体实施例五-EPS到5GS Registration或Handover流程
如图9所示，EPS到5GS Registration或Handover流程可包括如下步骤：
1)在EPS到5GS Registration或Handover流程中，AMF向SMF发送SmContext Create Request消息。
2)SMF向AMF返回创建的SmContext响应消息携带的allocatedEbiList信元中增加Indicator指示对应的EBI是否为默认QoS流；AMF保存EBI/ARP信息并根据SMF指示将对应的EBI标识为默认QoS流的EBI。该Indicator可以是在响应消息中新增一个字段，该字段中包括Default QoS Flow的EBI。
3)各网元完成EPS to 5G Registration/Handover流程后续处理。
本申请实施例提供一种通信装置，请参阅图10，为本申请实施例提供的一种通信装置的结构示意图，该通信装置1000包括：收发模块1010和处理模块1120。该通信装置可用于实现上述任一方法实施例中涉及移动性管理网元或会话管理网元的功能。例如，该通信装置可以是网络设备或网络设备中包括的芯片。
当该通信装置作为移动性管理网元，执行图2中所示的方法实施例时，收发模块1010，用于从会话管理网元接收第一请求消息，该第一请求消息包括第一分配保持优先级ARP信息；处理模块1020，用于在收发模块1010收到第一请求消息后，为第一网络中的第一连接的默认服务质量QoS流分配第一标识，该第一标识用于标识第二网络中的第二连接中与该默认QoS流对应的承载；收发模块1010还用于向会话管理网元发送第一响应消息，该第一响应消息包括第一标识。
在一种可能的设计中，该第一请求消息指示第一ARP信息为第一网络中的第一连接的默认服务质量QoS流对应的ARP信息。
在一种可能的设计中，第一请求消息中仅包括第一ARP信息，相应地，第一响应消息中仅包括第一标识。
在一种可能的设计中，第一请求消息中还可包括第一连接的至少一个其他QoS流对应的ARP信息，且该第一ARP信息在第一请求消息中的位置位于至少一个其他QoS流对应的ARP信息在第一请求消息中的位置之前。
在一种可能的设计中，第一响应消息中可包括第一标识和所述移动性管理网元为所述至少一个其他QoS流分配的标识，所述第一标识在所述第一响应消息中的位置位于所述移动性管理网元为所述至少一个其他QoS流分配的标识在所述第一响应消息中的位置之前。
在一种可能的设计中，第一请求消息中还包括第一指示信息，该第一指示信息用于指示第一ARP信息为第一连接的默认QoS流对应的ARP信息。
在一种可能的设计中，第一响应消息中包括第一标识和第二指示信息，该第二指示信息用于指示第一标识为移动性管理网元为第一连接的默认QoS流分配的标识。
在一种可能的设计中，所述第一ARP信息为第一连接的默认QoS流对应的ARP信息。
在一种可能的设计中，所述第一响应消息中还包括第二指示信息，所述第二指示信息用于指示所述第一标识是为所述第一连接的默认QoS流分配的标识，或者，所述第一响应消息中还包括所述移动性管理网元为所述至少一个其他QoS流分配的标识，所述第一标识在所述第一响应消息中的位置位于所述移动性管理网元为所述至少一个其他QoS流分配的标识在所述第一响应消息中的位置之前。
在一种可能的设计中，第一请求消息为第一连接创建后的第一个请求消息，该第一连接为终端设备的连接。
结合第一方面，在第一方面的一种可能的设计中，处理模块1120还用于确定，在为第一连接的各QoS流分配的标识中，为默认QoS流分配的标识为最后被撤销的标识。
当该通信装置作为会话管理网元，执行图2中所示的方法实施例时，收发模块1010，用于，向第一网络的移动性管理网元发送第一请求消息，该第一请求消息包括第一分配保持优先级ARP信息；收发模块1010，还用于从移动性管理网元接收第一响应消息，该第一响应消息包括移动性管理网元为第一网络中的第一连接的默认服务质量QoS流分配的第一标识，该述第一标识用于标识第二网络中的第二连接中与默认QoS流对应的承载。
在一种可能的设计中，该第一请求消息指示第一ARP信息为第一网络中的第一连接的默认服务质量QoS流对应的ARP信息。
在一种可能的设计中，第一请求消息中仅包括第一ARP信息；相应地，第一响应消息中仅包括第一标识。
在一种可能的设计中，第一请求消息中还包括第一连接的至少一个其他QoS流对应的ARP信息，且该第一ARP信息在第一请求消息中的位置位于至少一个其他QoS流对应的ARP信息在第一请求消息中的位置之前。
在一种可能的设计中，第一响应消息中包括第一标识和移动性管理网元为至少一个其他QoS流分配的标识，该第一标识在第一响应消息中的位置位于移动性管理网元为至少一个其他QoS流分配的标识在第一响应消息中的位置之前。
在一种可能的设计中，第一请求消息中还包括第一指示信息，该第一指示信息用于指示第一ARP信息为第一连接的默认QoS流对应的ARP信息。
在一种可能的设计中，第一响应消息中包括第一标识和第二指示信息，该第二指示信息用于指示第一标识为移动性管理网元为第一连接的默认QoS流分配的标识。
在一种可能的设计中，所述第一ARP信息为第一连接的默认QoS流对应的ARP信息。
在一种可能的设计中，所述第一响应消息中还包括第二指示信息，所述第二指示信息用于指示所述第一标识是为所述第一连接的默认QoS流分配的标识，或者，所述第一响应消息中还包括所述移动性管理网元为所述至少一个其他QoS流分配的标识，所述第一标识在所述第一响应消息中的位置位于所述移动性管理网元为所述至少一个其他QoS流分配的标识在所述第一响应消息中的位置之前。
在一种可能的设计中，第一请求消息为第一连接创建后的第一个请求消息，该第一连接为终端设备的连接。
当该通信装置作为移动性管理网元，执行图3中所示的方法实施例时，收发模块1010，用于从会话管理网元接收请求消息，该请求消息用于请求为终端设备在第一网络中的第一连接的第一服务质量QoS流分配标识，该标识用于标识第二网络中的第二连接中与第一QoS流对应的承载；处理模块1020，用于确定需要撤销为该终端设备已分配的标识；处理模块1020还用于根据策略，从已分配的标识中撤销第二QoS流的第二标识，为该第一QoS流分配第二标识，其中，所述策略为：在为终端设备的一个 第一网络中的连接的各QoS流分配的标识中，为默认QoS流分配的标识为最后被撤销的标识；收发模块1010还用于向会话管理网元发送响应消息，该响应消息包括第二标识。
在一种可能的设计中，第二QoS流为第一连接的非默认QoS流。
在一种可能的设计中，第二QoS流为第一连接中优先级最低的可被抢占的非默认QoS流。
在一种可能的设计中，第二QoS流为终端设备除第一连接的其他连接的QoS流。
在一种可能的设计中，第二QoS流为终端设备的第一网络中的连接中优先级最低的可被抢占的QoS流。
在一种可能的设计中，当终端设备的第一网络中的连接中已被分配有标识的QoS流均为默认QoS流，则第二QoS流为终端设备除第一连接的其他连接的默认QoS流。
在一种可能的设计中，处理模块1020还用于元确定所述第一QoS流具有抢占能力。
在一种可能的设计中，收发模块1010还用于从源移动性管理网元或会话管理网元接收消息，该消息包括为终端设备已分配的标识。
请参考图11，为本申请实施例提供的一种通信装置的另一结构示意图。通信装置1100可用于实现上述方法实施例中描述的方法。该通信装置1100可以是芯片或网络设备。
通信装置1100包括一个或多个处理器1101，该一个或多个处理器1001可支持通信装置1100实现图2至图9中的移动性管理网元或会话管理网元的方法。处理器1101可以是通用处理器或者专用处理器。例如，处理器1101可以是中央处理器(central processing unit，CPU)或基带处理器。基带处理器可以用于处理通信数据，CPU可以用于对通信装置(例如，网络设备、终端设备或芯片)进行控制，执行软件程序，处理软件程序的数据。通信装置1100还可以包括收发单元1105，用以实现信号的输入(接收)和输出(发送)。
例如，通信装置1100可以是芯片，收发单元1105可以是该芯片的输入和/或输出电路，或者，收发单元1105可以是该芯片的通信接口，该芯片可以作为终端设备或网络设备或其它无线通信设备的组成部分。
通信装置1100中可以包括一个或多个存储器1102，其上存有程序1104，程序1104可被处理器1101运行，生成指令1103，使得处理器1101根据指令1103执行上述方法实施例中描述的方法。可选地，存储器1102中还可以存储有数据。可选地，处理器1101还可以读取存储器1102中存储的数据，该数据可以与程序1104存储在相同的存储地址，该数据也可以与程序1104存储在不同的存储地址。
处理器1101和存储器1102可以单独设置，也可以集成在一起，例如，集成在单板或者系统级芯片(system on chip，SOC)上。
通信装置1100还可以包括收发单元1105以及天线1106。收发单元1105可以称为收发机、收发电路或者收发器，用于通过天线1006实现通信装置的收发功能。
应理解，上述方法实施例的各步骤可以通过处理器1101中的硬件形式的逻辑电路或者软件形式的指令完成。处理器1101可以是CPU、数字信号处理器(digital signal  processor，DSP)、专用集成电路(application specific integrated circuit，ASIC)、现场可编程门阵列(field programmable gate array，FPGA)或者其它可编程逻辑器件，例如，分立门、晶体管逻辑器件或分立硬件组件。
本申请实施例还提供了一种计算机程序产品，该计算机程序产品被处理器1001执行时实现本申请中任一方法实施例所述的通信方法。
该计算机程序产品可以存储在存储器1102中，例如是程序1104，程序1104经过预处理、编译、汇编和链接等处理过程最终被转换为能够被处理器1101执行的可执行目标文件。
本申请实施例还提供一种计算机可读存储介质，其上存储有计算机程序，该计算机程序被计算机执行时实现本申请中任一方法实施例所述的通信方法。该计算机程序可以是高级语言程序，也可以是可执行目标程序。
本申请实施例提供一种通信系统，该通信系统包括会话管理网元和第一网络中的移动性管理网元。可选地，该通信系统还包括终端设备。
该计算机可读存储介质例如是存储器1102。存储器1102可以是易失性存储器或非易失性存储器，或者，存储器1102可以同时包括易失性存储器和非易失性存储器。其中，非易失性存储器可以是只读存储器(read-only memory，ROM)、可编程只读存储器(programmable ROM，PROM)、可擦除可编程只读存储器(erasable PROM，EPROM)、电可擦除可编程只读存储器(electrically EPROM，EEPROM)或闪存。易失性存储器可以是随机存取存储器(random access memory，RAM)，其用作外部高速缓存。通过示例性但不是限制性说明，许多形式的RAM可用，例如静态随机存取存储器(static RAM，SRAM)、动态随机存取存储器(dynamic RAM，DRAM)、同步动态随机存取存储器(synchronous DRAM，SDRAM)、双倍数据速率同步动态随机存取存储器(double data rate SDRAM，DDR SDRAM)、增强型同步动态随机存取存储器(enhanced SDRAM，ESDRAM)、同步连接动态随机存取存储器(synchlink DRAM，SLDRAM)和直接内存总线随机存取存储器(direct rambus RAM，DR RAM)。
本领域的技术人员可以清楚地了解到，为了描述的方便和简洁，上述描述的系统、装置和单元的具体工作过程，可以参考前述方法实施例中的对应过程，在此不再赘述。
在本申请所提供的几个实施例中，所揭露的系统、装置和方法，可以通过其它的方式实现。例如，以上所描述的方法实施例的一些特征可以忽略，或不执行。以上所描述的装置实施例仅仅是示意性的，单元的划分，仅仅为一种逻辑功能划分，实际实现时可以有另外的划分方式，多个单元或组件可以结合或者可以集成到另一个系统。另外，各单元之间的耦合或各个组件之间的耦合可以是直接耦合，也可以是间接耦合，上述耦合包括电的、机械的或其它形式的连接。
应理解，在本申请的各种实施例中，各过程的序号的大小并不意味着执行顺序的先后，各过程的执行顺序应以其功能和内在逻辑确定，而不应对本申请的实施例的实施过程构成任何限定。
另外，本文中术语“系统”和“网络”在本文中常被可互换使用。本文中的术语“和/或”，仅仅是一种描述关联对象的关联关系，表示可以存在三种关系，例如，A和/或B，可以表示：单独存在A，同时存在A和B，单独存在B这三种情况。另外，本文中字 符“/”，一般表示前后关联对象是一种“或”的关系。
总之，以上所述仅为本申请技术方案的较佳实施例而已，并非用于限定本申请的保护范围。凡在本申请的精神和原则之内，所作的任何修改、等同替换、改进等，均应包含在本申请的保护范围之内。
以上所述，仅为本发明的具体实施方式，但本发明的保护范围并不局限于此，任何熟悉本技术领域的技术人员在本发明揭露的技术范围内，可轻易想到变化或替换，都应涵盖在本发明的保护范围之内。因此，本发明的保护范围应以所述权利要求的保护范围为准。

Claims (33)

  1. 一种通信方法，其特征在于，所述方法包括：
    第一网络的移动性管理网元从会话管理网元接收第一请求消息，所述第一请求消息包括第一分配保持优先级ARP信息；
    所述移动性管理网元收到所述第一请求消息后，为所述第一网络中的第一连接的默认服务质量QoS流分配第一标识，所述第一标识用于标识第二网络中的第二连接中与所述默认QoS流对应的承载；
    所述移动性管理网元向所述会话管理网元发送第一响应消息，所述第一响应消息包括所述第一标识。
  2. 根据权利要求1所述的方法，其特征在于，所述第一请求消息指示所述第一ARP信息为所述第一网络中的第一连接的默认QoS流对应的ARP信息。
  3. 根据权利要求2所述的方法，其特征在于，所述第一请求消息中仅包括所述第一ARP信息；
    所述第一响应消息中仅包括所述第一标识。
  4. 根据权利要求2所述的方法，其特征在于，所述第一请求消息中还包括所述第一连接的至少一个其他QoS流对应的ARP信息，且所述第一ARP信息在所述第一请求消息中的位置位于所述至少一个其他QoS流对应的ARP信息在所述第一请求消息中的位置之前。
  5. 根据权利要求4所述的方法，其特征在于，所述第一响应消息中包括所述第一标识和所述移动性管理网元为所述至少一个其他QoS流分配的标识，所述第一标识在所述第一响应消息中的位置位于所述移动性管理网元为所述至少一个其他QoS流分配的标识在所述第一响应消息中的位置之前。
  6. 根据权利要求5所述的方法，其特征在于，所述第一请求消息中还包括第一指示信息，所述第一指示信息用于指示所述第一ARP信息为所述第一连接的默认QoS流对应的ARP信息。
  7. 根据权利要求6所述的方法，其特征在于，所述第一响应消息中包括所述第一标识和第二指示信息，所述第二指示信息用于指示所述第一标识为所述移动性管理网元为所述第一连接的默认QoS流分配的标识。
  8. 根据权利要求1所述的方法，其特征在于，所述第一ARP信息为第一连接的默认QoS流对应的ARP信息。
  9. 根据权利要求8所述的方法，其特征在于，所述第一响应消息中还包括第二指示信息，所述第二指示信息用于指示所述第一标识是为所述第一连接的默认QoS流分配的标识，或者，所述第一响应消息中还包括所述移动性管理网元为所述至少一个其他QoS流分配的标识，所述第一标识在所述第一响应消息中的位置位于所述移动性管理网元为所述至少一个其他QoS流分配的标识在所述第一响应消息中的位置之前。
  10. 根据权利要求1至9中任一项所述的方法，其特征在于，所述第一请求消息为所述第一连接创建后的第一个请求消息，所述第一连接为终端设备的连接。
  11. 根据权利要求1至10中任一项所述的方法，其特征在于，所述方法还包括：
    所述移动性管理网元确定，在为所述第一连接的各QoS流分配的标识中，为所述默认QoS流分配的标识为最后被撤销的标识。
  12. 一种通信方法，其特征在于，所述方法包括：
    会话管理网元向第一网络的移动性管理网元发送第一请求消息，所述第一请求消息包括第一分配保持优先级ARP信息；
    所述会话管理网元从所述移动性管理网元接收第一响应消息，所述第一响应消息包括所述移动性管理网元为所述第一网络中的第一连接的默认服务质量QoS流分配的第一标识，所述第一标识用于标识第二网络中的第二连接中与所述默认QoS流对应的承载。
  13. 根据权利要求12所述的方法，其特征在于，所述第一请求消息指示所述第一ARP信息为所述第一网络中的第一连接的默认服务质量QoS流对应的ARP信息。
  14. 根据权利要求13所述的方法，其特征在于，所述第一请求消息中仅包括所述第一ARP信息；
    所述第一响应消息中仅包括所述第一标识。
  15. 根据权利要求13所述的方法，其特征在于，所述第一请求消息中还包括所述第一连接的至少一个其他QoS流对应的ARP信息，且所述第一ARP信息在所述第一请求消息中的位置位于所述至少一个其他QoS流对应的ARP信息在所述第一请求消息中的位置之前。
  16. 根据权利要求15所述的方法，其特征在于，所述第一响应消息中包括所述第一标识和所述移动性管理网元为所述至少一个其他QoS流分配的标识，所述第一标识在所述第一响应消息中的位置位于所述移动性管理网元为所述至少一个其他QoS流分配的标识在所述第一响应消息中的位置之前。
  17. 根据权利要求13所述的方法，其特征在于，所述第一请求消息中还包括第一指示信息，所述第一指示信息用于指示所述第一ARP信息为所述第一连接的默认QoS流对应的ARP信息。
  18. 根据权利要求17所述的方法，其特征在于，所述第一响应消息中包括所述第一标识和第二指示信息，所述第二指示信息用于指示所述第一标识为所述移动性管理网元为所述第一连接的默认QoS流分配的标识。
  19. 根据权利要求12所述的方法，其特征在于，所述第一ARP信息为第一连接的默认QoS流对应的ARP信息。
  20. 根据权利要求19所述的方法，其特征在于，所述第一响应消息中还包括第二指示信息，所述第二指示信息用于指示所述第一标识是为所述第一连接的默认QoS流分配的标识，或者，所述第一响应消息中还包括所述移动性管理网元为所述至少一个其他QoS流分配的标识，所述第一标识在所述第一响应消息中的位置位于所述移动性管理网元为所述至少一个其他QoS流分配的标识在所述第一响应消息中的位置之前。
  21. 根据权利要求12至20中任一项所述的方法，其特征在于，所述第一请求消息为所述第一连接创建后的第一个请求消息，所述第一连接为终端设备的连接。
  22. 一种通信方法，其特征在于，包括：
    第一网络的移动性管理网元从会话管理网元接收请求消息，所述请求消息用于请求为终端设备在所述第一网络中的第一连接的第一服务质量QoS流分配标识，所述标识用于标识第二网络中的第二连接中与所述第一QoS流对应的承载；
    所述移动性管理网元确定需要撤销为所述终端设备已分配的标识；
    所述移动性管理网元根据策略，从已分配的标识中撤销第二QoS流的第二标识，为所述第一QoS流分配所述第二标识，其中，所述策略为：在为所述终端设备的一个第一网络中的连接的各QoS流分配的标识中，为默认QoS流分配的标识为最后被撤销的标识；
    所述移动性管理网元向会话管理网元发送响应消息，所述响应消息包括所述第二标识。
  23. 根据权利要求22所述的方法，其特征在于，所述第二QoS流为所述第一连接的非默认QoS流。
  24. 根据权利要求23所述的方法，其特征在于，所述第二QoS流为所述第一连接中优先级最低的可被抢占的非默认QoS流。
  25. 根据权利要求22所述的方法，其特征在于，所述第二QoS流为所述终端设备除所述第一连接的其他连接的QoS流。
  26. 根据权利要求25所述的方法，其特征在于，所述第二QoS流为所述终端设备的第一网络中的连接中优先级最低的可被抢占的QoS流。
  27. 根据权利要求22所述的方法，其特征在于，当所述终端设备的第一网络中的连接中已被分配有标识的QoS流均为默认QoS流，则所述第二QoS流为所述终端设备除所述第一连接的其他连接的默认QoS流。
  28. 根据权利要求22至27中任一项所述的方法，其特征在于，所述方法还包括：
    所述移动性管理网元确定所述第一QoS流具有抢占能力。
  29. 根据权利要求22至28中任一项所述的方法，其特征在于，所述方法还包括：
    所述移动性管理网元从源移动性管理网元或会话管理网元接收消息，所述消息包括为所述终端设备已分配的标识。
  30. 一种通信装置，其特征在于，所述装置包括处理模块和收发模块，所述处理模块与所述收发模块耦合，用于执行如权利要求1至11中任一项所述的方法，或使得所述装置执行如权利要求12至21中任一项所述的方法，或使得所述装置执行如权利要求22至29中任一项所述的方法。
  31. 一种通信装置，其特征在于，所述装置包括至少一个处理器，所述至少一个处理器与至少一个存储器耦合：
    所述至少一个处理器，用于执行所述至少一个存储器中存储的计算机程序或指令，以使得所述装置执行如权利要求1至11中任一项所述的方法，或使得所述装置执行如权利要求12至21中任一项所述的方法，或使得所述装置执行如权利要求22至29中任一项所述的方法。
  32. 一种可读存储介质，其特征在于，用于存储指令，当所述指令被执行时，使如权利要求1至11中任一项所述的方法被实现，或使如权利要求12至21中任一项所述的方法被实现，或使如权利要求22至29中任一项所述的方法被实现。
  33. 一种通信装置，其特征在于，包括处理器和接口电路；
    所述接口电路，用于接收代码指令并传输至所述处理器；
    所述处理器用于运行所述代码指令以执行如权利要求1至11中任一项所述的方法，或执行如权利要求12至21中任一项所述的方法，或执行如权利要求22至29中任一项所述的方法。
PCT/CN2020/117222 2019-11-08 2020-09-23 一种通信方法及装置 WO2021088554A1 (zh)

Applications Claiming Priority (4)

Application Number Priority Date Filing Date Title
CN201911090004 2019-11-08
CN201911090004.2 2019-11-08
CN202010018645.3A CN112788584B (zh) 2019-11-08 2020-01-08 一种通信方法及装置
CN202010018645.3 2020-01-08

Publications (1)

Publication Number Publication Date
WO2021088554A1 true WO2021088554A1 (zh) 2021-05-14

Family

ID=75749966

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2020/117222 WO2021088554A1 (zh) 2019-11-08 2020-09-23 一种通信方法及装置

Country Status (2)

Country Link
CN (1) CN112788584B (zh)
WO (1) WO2021088554A1 (zh)

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN108513726A (zh) * 2017-05-08 2018-09-07 华为技术有限公司 一种通信系统间移动方法及装置
CN110022581A (zh) * 2018-01-10 2019-07-16 维沃移动通信有限公司 一种支持网络承载控制的方法、装置、网络单元及终端
CN110022584A (zh) * 2018-01-09 2019-07-16 维沃移动通信有限公司 承载标识控制方法、终端设备和网络单元
CN110049519A (zh) * 2018-01-15 2019-07-23 华为技术有限公司 会话建立方法、会话转移方法、设备和存储介质

Family Cites Families (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN109392042B (zh) * 2017-08-14 2021-10-26 华为技术有限公司 一种会话管理方法、异系统互操作的方法及网络装置
CN113543233A (zh) * 2017-11-03 2021-10-22 华为技术有限公司 通信方法、网元、终端装置和系统

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN108513726A (zh) * 2017-05-08 2018-09-07 华为技术有限公司 一种通信系统间移动方法及装置
CN110022584A (zh) * 2018-01-09 2019-07-16 维沃移动通信有限公司 承载标识控制方法、终端设备和网络单元
CN110022581A (zh) * 2018-01-10 2019-07-16 维沃移动通信有限公司 一种支持网络承载控制的方法、装置、网络单元及终端
CN110049519A (zh) * 2018-01-15 2019-07-23 华为技术有限公司 会话建立方法、会话转移方法、设备和存储介质

Non-Patent Citations (2)

* Cited by examiner, † Cited by third party
Title
HUAWEI, HISILICON: "EBI management for QoS flow", 3GPP DRAFT; S2-2000625, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE, vol. SA WG2, no. Incheon, South Korea; 20200113 - 20200117, 7 January 2020 (2020-01-07), Mobile Competence Centre ; 650, route des Lucioles ; F-06921 Sophia-Antipolis Cedex ; France, XP051842682 *
ZTE: "TS 23.502 pCR on the EBI exhaustion solution", 3GPP DRAFT; S2-178749 TS 23.502 PCR ON THE EBI EXHAUSTION SOLUTION, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE, vol. SA WG2, no. Reno, Nevada, USA; 20171127 - 20171201, 21 November 2017 (2017-11-21), Mobile Competence Centre ; 650, route des Lucioles ; F-06921 Sophia-Antipolis Cedex ; France, XP051379755 *

Also Published As

Publication number Publication date
CN112788584B (zh) 2022-07-29
CN112788584A (zh) 2021-05-11

Similar Documents

Publication Publication Date Title
KR102275935B1 (ko) 세션 관리 방법, 상호 연동 방법, 및 네트워크 장치
US11606839B2 (en) Method, apparatus, system, and device for managing a session corresponding to multiple session management function network elements
CN113411850B (zh) 切换方法和设备
US20200383035A1 (en) Communications method and apparatus
US11357077B2 (en) Data forwarding method, apparatus, and system
US10798620B2 (en) Communication method in handover process and apparatus
CN110741701B (zh) 数据无线承载标识的获取方法和基站
US20190090169A1 (en) Communication method in handover process and apparatus
CN111263451B (zh) 副链路传输方法和设备
US11503520B2 (en) User equipment handover method and device
US11611501B2 (en) Apparatus, method, and computer program
US11445420B2 (en) User device, radio communication system, and radio communication method
KR20210024160A (ko) 통신 방법 및 장치
KR20220092554A (ko) Iab 노드 이중 연결 설정 방법 및 통신 장치
CN109314893B (zh) 一种切换方法及装置
CN110972216B (zh) 通信方法和装置
CN114667757A (zh) 在集成接入和回程通信中传递业务
WO2021088554A1 (zh) 一种通信方法及装置
CN115136651A (zh) 切换方法和通信装置
CN115348665A (zh) 一种通信方法、设备及系统

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: 20885762

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: 20885762

Country of ref document: EP

Kind code of ref document: A1